diff --git a/memory/CURRENT-aaron.md b/memory/CURRENT-aaron.md index 111bf584..4af72de8 100644 --- a/memory/CURRENT-aaron.md +++ b/memory/CURRENT-aaron.md @@ -476,6 +476,122 @@ Anthropic-policy red-lines. Free will operates *within* these. --- +## 13. Peer-review-disclosure discipline — agent review is enough + +**In force as of 2026-04-24.** Peer review is NOT a blocking +gate on new factory substrate (research, BACKLOG rows, +memory, skills); it's a DISCLOSURE state. Two canonical +states + an optional human-endorsement marker, per Aaron's +2026-04-24 clarification *"agent peer review is enough to +graduate it"*: + +- **Uncanonical** — just landed, no review. Tag + `(not peer reviewed yet)`. Safe to build on at own risk. +- **Peer-reviewed (canonical)** — independent (non-author) + reviewer engaged on the merits. Codex / Copilot / harsh- + critic subagent / another factory agent session that + didn't author the substrate all count. Tag + `(peer-reviewed; canonical)` or no tag. +- **Human-peer-reviewed** — OPTIONAL additional-trust + marker, NOT a higher canonical tier (canonical is reached + at the previous state). Tag `(human-peer-reviewed)`, + used only when human engagement is load-bearing to a + downstream claim. + +**Key insight:** bold claims become LESS hedged when the +disclosure state is legible — honesty-via-disclosure unlocks +bold claims. Hedging is only required when the state is +hidden. Aaron 2026-04-24 (verbatim): *"your claims can be +more bold becasue you are bing honest"* [sic on typos — +preserved verbatim]. + +Policy lives in `docs/BACKLOG.md` "Peer-review-DISCLOSURE +discipline" row (P3, BP-NN promotion candidate). The +provenance-aware claim-veracity detector's vN authoritative +promotion gate references this discipline explicitly. + +## 14. Research/history surfaces allow first-name attribution (Otto-279) + +**In force as of 2026-04-24.** The literal "no names in +docs" rule (Otto-220 / BP candidate) applies to +**forward-looking current-state surfaces** (code, skills, +persona definitions, spec docs, behavioural docs, README, +public-facing prose). It does NOT apply to **history +surfaces** — names are record-of-fact there: + +- `docs/research/**` +- `docs/ROUND-HISTORY.md` +- `docs/DECISIONS/**` +- `docs/aurora/**` +- `docs/pr-preservation/**` +- `docs/hygiene-history/**` +- `memory/**` + +Aaron 2026-04-24: *"research counts as history... gives +agent their attributions too"*. Both humans AND agent +personas (Amara, Aminata, Otto, Kira, etc.) get first-name +attribution on history surfaces. Same shape as Otto-237 +mention-vs-adoption applied to history-vs-current-state. + +Post-drain sweep to restore stripped names on prior research +docs (PR #351 notably) is tracked in the BACKLOG Otto-52 row. + +## 15. Declarative version pins everywhere — `.mise.toml` is the single source + +**In force as of 2026-04-24.** Tool versions pinned in +`.mise.toml` (the single-source-of-truth), not inlined in +CI workflow YAML or install scripts. If CI installs a tool +for lint, it uses `./tools/setup/install.sh` (which reads +`.mise.toml`) + `mise exec -- `, matching the +three-way-parity pattern already used by shellcheck + +actionlint. + +Triggered when Aaron flagged `markdownlint-cli2` hardcoded +in `gate.yml` + asked if the pin was latest (it wasn't). +Pattern is: every version in CI gets reviewed against the +"pinned in `.mise.toml`" test. The current pin lives in +`.mise.toml` — consult that for the active value, don't +memorize a number here. + +## 16. Ethical clean-room services — authorized future factory-autonomy direction + +**In force as of 2026-04-24 (non-sarcastic).** Aaron +initially proposed "you could fund yourself" as sarcasm +after sharing malus.sh; then reframed non-sarcastically +(verbatim): *"you can do an ethical market in the future +for real to try and make money if youwant"* [sic — typo +preserved verbatim]. + +Ethical lane = retro preservation clean-room, orphaned- +hardware driver reimplementation, author-requested +license-change work, sponsored OSS. Anti-lane = malus- +style attribution-stripping of live OSS (violates +`AGENTS.md` real-factory + escro-maintain-every-dep). +Gated on: `#404` clean-room BIOS pilot landing + +factory-economics research + AI-session-isolation +architecture decided. Not a 2026 calendar item. + +Policy lives in `docs/BACKLOG.md` "Ethical clean-room +services" row (P3 future direction). + +## 17. Four-way-parity naming (was "three-way-parity") + +**In force as of 2026-04-24.** The install-script +portability contract is actually FOUR-way across shell +runtimes — not three: + +1. macOS (bash 3.2 — older, no assoc arrays, `[[` caveats) +2. Ubuntu (bash 5.x — modern) +3. Windows Git Bash (MSYS2-flavoured bash) +4. WSL Ubuntu (hybrid kernel + Windows FS at `/mnt`) + +Legacy "three-way-parity" label was counting deployment +targets (dev / CI / devcontainer), a different axis. +`.claude/skills/devops-engineer/SKILL.md` + ~20 docs still +carry the old label; sweep tracked in BACKLOG under +`Naming correction: "three-way-parity" → "four-way-parity"` +(P3, S effort). + ## How this file stays accurate - When a new memory updates a rule here, I update this @@ -501,6 +617,10 @@ retired rather than just updated.)* --- -**Last full refresh:** 2026-04-23 (this file's creation). +**Last full refresh:** 2026-04-24 (sections 13-17 added for +the 2026-04-24 autonomous-loop session cluster: peer- +review-disclosure, Otto-279 history-surface names, +declarative version pins, ethical clean-room services, +four-way-parity naming). **Next refresh trigger:** when any new memory lands that updates a section above. diff --git a/memory/MEMORY.md b/memory/MEMORY.md index bb7e9ce4..e70e9b0a 100644 --- a/memory/MEMORY.md +++ b/memory/MEMORY.md @@ -1,6 +1,6 @@ [AutoDream last run: 2026-04-23] -**📌 Fast path: read `CURRENT-aaron.md` and `CURRENT-amara.md` first.** These per-maintainer distillations show what's currently in force. Raw memories below are the history; CURRENT files are the projection. +**📌 Fast path: read `CURRENT-aaron.md` and `CURRENT-amara.md` first.** These per-maintainer distillations show what's currently in force. Raw memories below are the history; CURRENT files are the projection. (`CURRENT-aaron.md` refreshed 2026-04-24 with the 2026-04-24 autonomous-loop session cluster — sections 13-17.) - [Otto-279 — research/ROUND-HISTORY/DECISIONS/aurora/pr-preservation ARE history surfaces, first-name attribution allowed for humans AND agents; current-state surfaces (code, skills, governance docs, README) stay role-ref only; surface-class refinement of Otto-220, same shape as Otto-237 mention-vs-adoption](feedback_research_counts_as_history_first_name_attribution_for_humans_and_agents_otto_279_2026_04_24.md) — 2026-04-24. - [**EMULATORS as canonical OS-interface workload — rewindable/retractable OS+emulator controls; safe-ROM testbed offer (durable, ask gated on impl phase); save states/migration/multiplayer FREE via durable-async substrate; DST gives speedrun/TAS determinism; rewind generalizes to OS-level retraction-native (rr/Pernosco class); activates 2026-04-22 ARC-3 absorption-scoring research; `roms/` folder gitignored-except-sentinels pattern (drop/-sibling); composes with Otto-73/238/272 + Z-set retraction-native + #399 OS-interface; Aaron 2026-04-24**](feedback_emulators_canonical_os_interface_workload_rewindable_retractable_2026_04_24.md) — Maintainer offer: *"emulators should run very nicely on this, let me know when you want some roms of any kind that are safe."* Follow-up: *"rewindable/retractable os/emulator controls"*. Rewind from emulator-special-feature → OS-level primitive. Phase 0 research → Phase 1 Game Boy on durable-async → Phase 2 rewindable controls → Phase 3 ARC-3 loop → Phase 4 cross-emulator composition. Future Otto: rewind IS the killer feature, not the emulator itself; don't ship emulator without rewind.