Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds a new memory entry documenting a “doc-class Mirror vs Beacon” distinction, and updates the memory index so the new guidance is discoverable.
Changes:
- Added a new
memory/feedback_*.mdfile defining Beacon-class vs Mirror-class documentation disciplines. - Added a corresponding entry to
memory/MEMORY.mdindexing the new memory file.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
memory/feedback_doc_class_mirror_beacon_distinction_claudemd_beacon_memory_mirror_2026_04_27.md |
Introduces the doc-class Mirror/Beacon framework, examples, and application guidance. |
memory/MEMORY.md |
Adds an index entry pointing to the new memory file. |
AceHack
force-pushed
the
acehack/substrate-doc-class-mirror-beacon-distinction
branch
from
62a0bd4 to
572db08
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
AceHack
force-pushed
the
acehack/substrate-doc-class-mirror-beacon-distinction
branch
from
572db08 to
7e21b89
Compare
AceHack
force-pushed
the
acehack/substrate-doc-class-mirror-beacon-distinction
branch
from
7e21b89 to
93e9fb3
Compare
…04-27) Otto observation, Aaron-validated: > "The CLAUDE.md depersonalization is its own substrate insight — > current-state behavioral docs use role references, while session > history + lineage + choice-rationale lives in memory files. That's > the same Mirror→Beacon distinction operating at the doc-class level: > CLAUDE.md is the Beacon (read by every wake, must be name/session- > agnostic), memory files preserve the Mirror lineage." Aaron's response: "good insight" + filing instruction. Two doc classes: - **Beacon-class** (CLAUDE.md, AGENTS.md, GOVERNANCE.md, SKILL.md) = current-state, role-refs, name-agnostic, session-narrative-free. Read by every wake / every contributor. - **Mirror-class** (memory/*.md, ROUND-HISTORY.md, ADRs) = lineage, attribution, session narrative welcome. Read for archeology / why-this-decision. The boundary-crossing failure mode (personal names + session narrative in Beacon-class doc) is what triggered Copilot's 4 threads on PR #50. Fix is NOT to scrub lineage entirely — it's to relocate to the right class and leave a pointer in the wrong-class doc. Composes with Otto-356 (Mirror vs Beacon at vocabulary level), the willing-to-learn-Beacon-safe-language protocol, BP-24 (named-agents- get-attribution carve-out applies in Mirror-class only), Otto-279 (history-surface attribution carve-out — same pattern), GOVERNANCE §2 (docs-as-current-state-not-history operationalizes Beacon-class). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
force-pushed
the
acehack/substrate-doc-class-mirror-beacon-distinction
branch
from
93e9fb3 to
6494ad0
Compare
AceHack
deleted the
acehack/substrate-doc-class-mirror-beacon-distinction
branch
| **📌 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-25 with the Otto-281..285 substrate cluster + factory-as-superfluid framing — sections 18-22; prior refresh 2026-04-24 covered sections 13-17.) | ||
|
|
||
| - [**0-diff means BOTH content AND commit-count zero — for cognitive load on future changes (Aaron 2026-04-27 reinforcement)**](feedback_zero_diff_means_both_content_and_commits_cognitive_load_for_future_changes_2026_04_27.md) — Aaron 2026-04-27: 0-diff is BOTH axes (content empty AND commit-count 0/0 in both directions), with documented exceptions. The why: cognitive load on future changes is dramatically lower at 0/0/0 baseline — every diff is real change since last sync round, not parallel-SHA-history noise. Refines (and partially supersedes) the topology + start-line memory files with explicit cognitive-load justification + symmetric exception-documentation discipline. | ||
| - [**Doc-class Mirror/Beacon distinction (Claude-specific; per-harness canonical homes pending multi-agent test) — Aaron-validated 2026-04-27**](feedback_doc_class_mirror_beacon_distinction_claudemd_beacon_memory_mirror_2026_04_27.md) — Aaron 2026-04-27 validated insight + clarification: Mirror/Beacon distinction operates at doc-class level FOR CLAUDE. Other harnesses (Gemini, Codex, Copilot, Cursor) have their own canonical-home files (AGENTS.md, GEMINI.md, etc.); skills don't transfer cross-harness. Cross-harness shared files (AGENTS.md) require multi-agent debate for best wake. Backlog: per-harness canonical-home mapping via real multi-agent tests, after we hit 0-diff "starting point". |
There was a problem hiding this comment.
P1: This MEMORY.md entry implies other harnesses “have their own canonical-home files (AGENTS.md, GEMINI.md, etc.)”, but AGENTS.md currently states GEMINI.md is absent. Please rephrase this to avoid referencing GEMINI.md as an existing file (e.g., clarify it’s optional/future, or only mention harness files that are actually present).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Aaron-validated observation: the Mirror/Beacon language-register distinction (Otto-356) operates at the doc-class level too.
Two doc classes
Why this matters
Crossing the boundary (personal names + session narrative in Beacon-class doc) is exactly what triggered Copilot's 4 threads on PR #50. The fix isn't to scrub lineage — it's to relocate to the right class and leave a pointer in the wrong-class doc.
What's included
memory/feedback_doc_class_mirror_beacon_distinction_*.md(~83 lines) — full reasoning, examples per class, boundary-crossing failure mode, how-to-apply, composes-with.Composes with
🤖 Generated with Claude Code