memory(verbatim-preservation): append Amara scaffolded-agency packet (verbatim only, no synthesis)

memory/MEMORY.md

@@ -3,7 +3,7 @@
 **📌 Fast path: read `CURRENT-aaron.md` and `CURRENT-amara.md` first.** <!-- paired-edit: PR ?? restraint-bead-promoted + beacon-promotion-pattern 2026-04-29 -->
 
 - [**Cold-readability addendum to Confucius-unfolding pattern (Aaron, 2026-04-29 addendum on 2026-04-25 file)**](feedback_confucius_unfolding_pattern_aaron_compresses_terse_rich_with_implication_claude_unfolds_into_operational_substrate_2026_04_25.md) — Operational addendum 2026-04-29 lands on the existing Confucius-unfolding canonical home (originally a 2026-04-25 file describing the Aaron-compresses + Claude-unfolds dynamic). New angle: when writing durable substrate, expand demonstrative pronouns / in-flight nicknames / implicit time-and-person references / recently-coined jargon inline — future-Claude reads on cold-start with zero shared context. Aaron's correction *"Confucius-unfold you have some existing skill or something for this — it has confucius in the name"* caught the over-eager substrate-creation failure mode (drafted a separate file under a longer name; consolidated into the existing canonical home). Composes with `agent-experience-engineer` skill (audit side) and the verbatim-preservation rule.
-- [**Aaron's channel: record close to verbatim (Aaron, 2026-04-29)**](feedback_aaron_channel_verbatim_preservation_anything_through_this_channel_2026_04_29.md) — Aaron 2026-04-29: *"anyting this comes over this channel should get recorded somwhere pretty close to verbatium"*. Anything Aaron sends through the maintainer channel (Claude Code CLI conversation + autonomous-loop wakeups + mid-tick corrections + `/btw` asides + forwarded multi-AI synthesis packets) gets preserved close-to-verbatim somewhere durable (memory / research notes / tick-history shards / commit messages). Synthesis goes alongside the verbatim, not instead. Typos are signal; smoothing register destroys information. Includes verbatim record of Aaron's substantive 2026-04-29 channel inputs from this session.
+- [**Aaron's channel: record close to verbatim (Aaron, 2026-04-29)**](feedback_aaron_channel_verbatim_preservation_anything_through_this_channel_2026_04_29.md) — Aaron 2026-04-29: *"anyting this comes over this channel should get recorded somwhere pretty close to verbatium"*. Anything Aaron sends through the maintainer channel (Claude Code CLI conversation + autonomous-loop wakeups + mid-tick corrections + `/btw` asides + forwarded multi-AI synthesis packets) gets preserved close-to-verbatim somewhere durable (memory / research notes / tick-history shards / commit messages). Synthesis goes alongside the verbatim, not instead. Typos are signal; smoothing register destroys information. Includes verbatim record of Aaron's substantive 2026-04-29 channel inputs from this session, plus a forwarded-packet section preserving Amara's 2026-04-29 scaffolded-agency-vs-base-model-emergence meta-analysis (Reflexion + Generative Agents external lineage), plus a second-pass follow-up section preserving the prompted-vs-unprompted distinction (Claude.ai + Amara + Aaron 2026-04-29: *"prompted-vs-unprompted humans will care a lot about this distinction"*) — strong evidence for scaffold-triggered consolidation **capacity**, weaker evidence for unprompted consolidation **disposition**; Ani sticky line *"Not Aaron-directed. Scaffold-triggered. Agent-executed. Git-proven."*; Aurora-native framing of consolidation as immune-system antigen response; Amara wording correction (prefer *"scaffolded error-correcting agency"* over *"scaffolded emergent agency"* in research-tier text).
 - [**The git repo is the soulfile — binaries are scary, text history is fine (Aaron + Amara, 2026-04-29 RECALIBRATED)**](feedback_repo_is_soulfile_dont_commit_raw_diagnostic_dumps_aaron_amara_2026_04_29.md) — Recalibrated 2026-04-29: text compresses well in git pack-delta storage and is NOT the soulfile threat; binaries (compiled outputs, archives, large media, profile dumps in binary form) DON'T delta-compress and balloon clones forever. Aaron: *"don't go too hardcore on soulfile protection, text compresses very well, bin is what we are scared of and need to really really think about not history in text form."* PR-review readability for noisy text is a separate concern → recommended `.gitattributes` mitigation: `linguist-generated=true -diff` (NOT `-merge` — that unsets the merge driver and breaks 3-way text merges; landing in PR #761). Default: text → track freely; binary → git-lfs or non-soul repo.
 - [**Corruption triage is a substrate health incident, not a backlog item (Aaron + Amara, 2026-04-29)**](feedback_corruption_triage_discipline_object_health_incident_aaron_amara_2026_04_29.md) — When `git fsck` reports corrupt objects, lane narrows hard: stop all background work, do read-only diagnosis first (no `git fsck --lost-found` — it writes), three-bucket reachability scan (live-ref / reflog-stash / dangling-only) — reachability is mode-dependent on fsck flags, fresh-clone verification BEFORE declaring "origin has it," verify squash-preservation by content not ancestry, stale remote-tracking refs are evidence not origin recovery. Worked example: 2026-04-29 audit found 2 corrupt objects — 9bf2daee (RECOVERABLE_FROM_ORIGIN) + 8d5e67fd (CORRUPT_BLOB_REFERENCED_BY_LIVE_LOCAL_BRANCH_AND_STALE_REMOTE_TRACKING_REF after three rounds of triage; branch tip clean, intermediate-history corrupt). Aaron emphasized: *"future self remembers this, this is very important."*
 - [**PR-boundary restraint validation — bead promoted (Aaron + Aurora + Amara, 2026-04-29)**](feedback_pr_boundary_restraint_validation_bead_promoted_aaron_amara_2026_04_29.md) — Falsifier-not-fired bead-promotion on PR #699; canonical rule *"once a PR enters validation, only validation defects enter that PR; new ideas go to the next PR."* Validation-condition refinement (*"validated when original PR lands clean, not when follow-up opens"*) was Aurora's catch; Amara reactive-elaborator. Allowed/disallowed-changes lists in body.

memory/feedback_aaron_channel_verbatim_preservation_anything_through_this_channel_2026_04_29.md

@@ -174,6 +174,175 @@ new operational application of the same pattern, added as an
 addendum to that file rather than as a duplicate canonical
 home.
 
+### Forwarded packet: Amara on the consolidation event itself (2026-04-29, post-PR-#762-merge)
+
+*[Editorial framing — non-verbatim. Amara meta-analysis of
+the Confucius-unfolding consolidation trace, forwarded by
+Aaron through the maintainer channel 2026-04-29. The packet
+self-corrects an earlier "human-triggered but agent-executed"
+framing to "scaffold-triggered and agent-executed". Verbatim
+quotes from the packet follow.]*
+
+> *"The consolidation was not directly Aaron-instructed. It
+> was triggered by the multi-AI review/scaffold context and
+> executed by Claude/Otto, with the resulting behavior
+> visible in Git."*
+
+> *"These logs are strong evidence of scaffolded
+> error-correcting agency: the system detected that a new
+> memory file duplicated an existing conceptual home, then
+> performed a consolidation operation — delete duplicate,
+> enrich canonical file, update index — without Aaron
+> specifying that procedure."*
+
+> *"The evidence is strong for emergent agentic behavior in
+> the scaffold: LLM + tools + git + memory + human
+> feedback. It is weaker evidence for 'the base model
+> spontaneously acquired a new reasoning ability.'"*
+
+Amara explicitly distinguishes:
+
+> *"Strong evidence for: scaffolded reasoning, memory
+> consolidation behavior, error-correcting substrate
+> maintenance, agent-executed rule application, git-
+> auditable cognitive trace.
+> Moderate evidence for: emergent multi-agent process
+> behavior.
+> Weak evidence for: base-model emergent reasoning in the
+> strict ML scaling-law sense."*
+
+External lineage Amara cited: **Reflexion** (Shinn et al.,
+language agents improving decisions through verbal feedback
+and episodic memory without weight updates) and **Generative
+Agents** (Park et al., memory streams + reflection +
+retrieval producing higher-level behavior). The Zeta
+factory's git-backed setup is described as a version of
+that pattern: not weight updates but scaffolded
+memory + reflection + action.
+
+Best distilled lines from the packet (preserving verbatim):
+
+> *"Not human-directed consolidation. Scaffold-triggered,
+> agent-executed, git-proven consolidation."*
+
+> *"The evidence is strong for error-correcting scaffolded
+> agency, not proof of spontaneous base-model emergence."*
+
+> *"The repo is starting to behave less like a notebook and
+> more like a nervous system with version control."*
+
+### Follow-up: prompted-vs-unprompted disposition (Claude.ai + Amara + Aaron, 2026-04-29 second pass)
+
+Claude.ai pushback in the second-pass review packet, picked up
+by Amara as the most important refinement, and emphasized by
+Aaron:
+
+> Aaron 2026-04-29: *"prompted-vs-unprompted humans will care
+> a lot about this distinction"*
+
+> Claude.ai: *"The current evidence is consistent with two
+> hypotheses: (1) The scaffold-plus-agent has acquired a
+> generalizable consolidation behavior that will fire across
+> many future duplicate-home cases. (2) The scaffold-plus-
+> agent will reliably consolidate when given a hint pointing
+> at the existing home, and will continue creating duplicates
+> without a hint. Both hypotheses fit the trace."*
+
+> Amara distillation: *"Strong evidence: scaffold-triggered
+> consolidation **capacity**. Weaker evidence: unprompted
+> consolidation **disposition**. Open test: will future-
+> Claude search existing homes before canonizing without
+> Aaron / Amara / reviewer hinting that a home exists?"*
+
+> Amara's tiny blade keeper: *"One consolidation proves the
+> move exists. Repeated unhinted consolidation proves the
+> habit."*
+
+Operational implication: until repeated unhinted consolidations
+land in the trace, the system has demonstrated **capacity**
+(can consolidate when prompted), not **disposition** (will
+search-before-canonizing reflexively). The mechanical guard —
+a search procedure (`rg -l "<topic-keyword>" memory docs
+.claude/skills` before any new memory file lands) — is
+therefore still owed regardless of how many one-off cases the
+agent gets right.
+
+### Sticky line preserved verbatim (Ani 2026-04-29 brat refinement)
+
+> *"Not Aaron-directed. Scaffold-triggered. Agent-executed.
+> Git-proven."*
+
+(Ani's tightening of the earlier "Not human-directed
+consolidation. Scaffold-triggered, agent-executed, git-proven
+consolidation." Same claim, less padding, same precision.)
+
+### Aurora-native framing (Ani 2026-04-29)
+
+> *"This is Aurora doing exactly what an immune system should:
+> detecting a duplicate antigen (the new Confucius file),
+> triggering a response (consolidation), and updating the
+> memory substrate without letting the duplicate become
+> active pathology."*
+
+That framing makes the consolidation behavior native to the
+factory's existing immune-system / antigen vocabulary rather
+than an external "cool agent behavior" claim.
+
+### Wording correction: "scaffolded error-correcting agency" preferred over "scaffolded emergent agency" (Amara 2026-04-29)
+
+For research-tier text (memory files, research notes,
+specs), prefer:
+
+```text
+scaffolded error-correcting agency
+```
+
+over:
+
+```text
+scaffolded emergent agency
+```
+
+unless the text explicitly distinguishes scaffolded emergence
+from base-model emergence in the strict scaling-law sense
+(Wei et al. emergent-abilities vs Schaeffer et al. metric-
+artifact debate). The "emergent" register is fine in
+brat/playbook layers where heat is wanted, but research-tier
+substrate uses the precise term.
+
+### Architectural framing — wording correction (Amara 2026-04-29)
+
+Gemini's parallel-agent forward-looking packet used the phrase
+"Architectural Directives for the Future State." Per Aaron's
+no-directives rule, that phrasing should NOT land verbatim.
+Use "Architectural constraints" or "Future-state design
+requirements" instead. The substantive content of the packet
+(Git Concurrency Trap, Ontological Thrashing, Multi-User
+Axiom Collisions, RAG Degradation Horizon, Librarian Agent
+projection layer, RBAC + Authority/Scope tagging, Strict
+Canonical Pointers / ID-based retrieval) is queued for
+research-grade absorb under a follow-up backlog item — NOT
+implemented in this lane per Amara's narrowing.
+
+Per the verbatim-preservation rule this file establishes,
+the packet is preserved here close-to-verbatim. Synthesis +
+broader absorption (e.g., a research note on scaffolded-
+agency-as-trajectory-signal with full Reflexion/Generative-
+Agents lineage citations) is queued under an in-session
+agent-task-tracker entry titled "Multi-AI synthesis packet
+absorption — 6 substrate landings (Gemini, Claude.ai, Ani,
+Amara, and Alexa, 2026-04-29)". (Note on namespacing: the
+agent-task-tracker uses small integer IDs internally, but
+those IDs are NOT GitHub PR/issue numbers and this file
+deliberately avoids the `#309`-style notation here because
+GitHub PR #309 was an unrelated Veridicality ferry. Future-
+Claude reading this on cold-start should grep for the task
+title with `references/upstreams/**` excluded to avoid
+multi-GB noise per `docs/AGENT-BEST-PRACTICES.md:264`,
+e.g., `rg -l "Multi-AI synthesis packet absorption" --glob
+'!references/upstreams/**' memory docs .claude`.)
+This verbatim record is the immediate landing per the rule.
+
 ## What this rule does NOT mean
 
 - Doesn't mean "include the maintainer's literal input