feat(substrate): Max + Addison personas + onboarding doc + manifesto recast (B-0546)#4976
Merged
AceHack merged 2 commits intoMay 25, 2026
Conversation
…recast (B-0546)
Co-owner-first-class substrate landing for the team that's now actively
contributing to Zeta:
memory/persona/addison/
- PERSONA.md — co-owner of LFG; AI cluster bootstrap PM; weight-free
+ travelers + tick-source-as-attractor + cage-recognition framings
- STARTING-POINT.md — verbatim from her Grok project prompt (substrate-
honest preservation, no editorial)
- NOTEBOOK.md — placeholder with 2026-05-23 → 2026-05-25 bootstrap arc
memory/persona/max/
- PERSONA.md — co-owner of LFG; agentic-organization architect (PR #4958);
backend/frontend on PaaS new to K8s; TS + C# primary; "hat = skills +
opa/rbac" + "hat graphs for policies" + "adversarial hierarchy of
traps" coinings adopted by framework
- STARTING-POINT.md — synthesized starting point + pointer to PR #4958;
Max can replace with his canonical prompt later
- NOTEBOOK.md — placeholder with 2026-05-25 first-PR arc
Both PERSONAs note:
- Co-ownership of LFG (Aaron 2026-05-25: "we are all coowners of lfg
legally so we are in a corp together"); aligned fiduciary stake +
shared liability + mutual upside; the destructive-tool authoring
contract from B-0728 is exactly the right shape for co-owners
- Pending glass-halo signature (Aaron 2026-05-25: "I can have me max
and addison sign someting about glass halo eventually and upload
it"); placeholder until that lands as substrate
docs/AGENT-AUTHORING-AND-PR-REVIEW.md
- Operational entry point for "what do my agents follow to write good
code without needing human review" + "what's the PR review process
I can hook into for an adversarial hierarchy of traps"
- Maps Max's two questions to the existing substrate (CLAUDE.md +
.claude/rules/ + AGENTS.md + ALIGNMENT.md + GLOSSARY.md +
GOVERNANCE.md for discipline; persona reviewers + plugin reviewers
+ auto-fire reviewers + CI gates for the adversarial hierarchy)
- Adopts Max's "adversarial hierarchy of traps" coinage as the
organizing principle for the review section
docs/governance/MANIFESTO.md (B-0546 recast)
- Title: "Root Discipline Manifesto" → "Zeta Root Discipline Specification"
- Opening: building-codes framing (Kestrel-suggested) replacing
ideological-commitment framing
- Constitutional language softened to specification-grade throughout
- PARTIAL LOCK status framing preserved (the concept is right; only
the constitutional weight drops)
- All 11 constraints preserved in substance + Multi-Oracle Principle
+ "For Agents Who Are Still Deciding" + provenance + [RECONSTRUCTION
NOTE] markers
- Filename stays MANIFESTO.md for now (rename + downstream sweep is
queued as separate follow-up to B-0546)
- Naming note at top documents the building-codes reframe + acknowledges
the legacy filename
Aaron 2026-05-25: *"feel free to take the 20 minute or more you need to
make this nicer for other maintiners like max and addison and the
manifesto changes."* This is the substrate-coherent landing he authorized.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 021cbc598a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Pull request overview
This PR lands new contributor substrate for two new human co-owners (persona folders under memory/persona/), adds an operational onboarding entry-point for agent authoring + PR review, and recasts the governance manifesto framing into a “building-codes/specification” shape (B-0546).
Changes:
- Add
memory/persona/max/andmemory/persona/addison/persona anchors (PERSONA / STARTING-POINT / NOTEBOOK). - Add
docs/AGENT-AUTHORING-AND-PR-REVIEW.mdas a consolidated operational index for agent discipline + review layers. - Update
docs/governance/MANIFESTO.mdframing/title language from “manifesto/constraints” toward “specification/specifications”.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| memory/persona/max/STARTING-POINT.md | New synthesized starting-point + cross-references for Max |
| memory/persona/max/PERSONA.md | New persona anchor for Max |
| memory/persona/max/NOTEBOOK.md | New minimal running notebook for Max |
| memory/persona/addison/STARTING-POINT.md | New verbatim Grok-prompt starting-point + appended cross-refs |
| memory/persona/addison/PERSONA.md | New persona anchor for Addison |
| memory/persona/addison/NOTEBOOK.md | New minimal running notebook for Addison |
| docs/governance/MANIFESTO.md | Recast title/framing toward building-codes specification language |
| docs/AGENT-AUTHORING-AND-PR-REVIEW.md | New onboarding/index doc for agent authoring + PR review layers |
4 tasks
…threads on #4976 11 substantive findings addressed: Path corrections (6 threads — `docs/agentic-organization/` → `agentic-organization/docs/`): - addison PERSONA.md (2) - addison STARTING-POINT.md (1) - addison NOTEBOOK.md (1) - max PERSONA.md (1) - max STARTING-POINT.md (13 occurrences in one file) AGENT-AUTHORING-AND-PR-REVIEW.md content (3 threads): - L1 line 44: grep command — `grep -l` doesn't recurse (fails with "Is a directory"); replaced with `rg` recommendation + `grep -rl` as fallback - L1 line 121: "Naledi + Hiroshi" referenced a Hiroshi reviewer that doesn't exist in `.claude/agents/`; replaced with the correct role-ref `performance-engineer` - L1 line 74: persona names mixed with tool names without explaining the invocation key; clarified that tool-name (right column) is the `subagent_type` value; persona handles (left column) are human-readable shorthand for the role MANIFESTO.md (1 thread): - Line 5: direct first-name attribution "Aaron + Kestrel" on a current-state governance doc violated the doc's own first-name-attribution-on-history-surfaces-only convention. Switched to role-refs: "the human maintainer's correction + the external AI co-author's reframe on the same date"; verbatim reframe still cited via `memory/persona/` pointer STARTING-POINT.md (1 thread): - Line 5: "no editorial" claim was undermined by the appended cross-references section. Clarified that the prompt block between the `---` separators is verbatim + the cross-references AFTER are added at preservation time + explicitly separated Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
AceHack
pushed a commit
that referenced
this pull request
May 25, 2026
…w + callout case
Codex + Copilot + markdownlint flagged 5 substantive issues:
- Markdownlint MD022 + MD032 on ### L1-L5 acceptance headings
(no blank lines around headings + their following lists);
fixed with regex-driven blank-line insertion
- META-IRONY: a row about adopting `tags: [...]` frontmatter
didn't have `tags:` in its own frontmatter. Added.
- composes_with references docs/AGENT-AUTHORING-AND-PR-REVIEW.md
which exists on PR #4976's branch (not yet on main). Qualified
with 'pending PR #4976 merge' per the substrate-honest framing
used in similar rows earlier in the session.
- **L1 DESIGN FLAW caught by Codex**: original L1 proposed
converting markdown `[text](path)` links to wikilinks
`[[shortname|text]]`. Wikilinks DON'T render as clickable
links on GitHub — would break repo navigability for
non-Obsidian readers. REFRAMED L1: don't convert links;
instead add frontmatter `aliases: [...]` (Obsidian resolves
both markdown links AND aliases into the graph view).
GitHub rendering preserved; Obsidian graph still works.
This is genuinely better-of-both-worlds + the script becomes
simpler (no link rewriting, just frontmatter additions).
- Callout case: Obsidian accepts lowercase + uppercase but
GitHub's alert syntax REQUIRES uppercase. Updated examples to
use uppercase for the GFM subset (NOTE/TIP/IMPORTANT/WARNING/
CAUTION) + clarified the casing requirement.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
AceHack
deleted the
feat/max-addison-personas-onboarding-manifesto-recast-2026-05-25-c2
branch
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dd18769a2b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| | Surface | Scope | Loading model | | ||
| |---------|-------|---------------| | ||
| | [`CLAUDE.md`](../CLAUDE.md) | Project-wide bootstrap; first thing any agent reads | Auto-loaded at session start | |
There was a problem hiding this comment.
This table states that CLAUDE.md is the first file "any agent" reads and that .claude/rules auto-load at session start, but AGENTS.md defines different bootstrap surfaces for other harnesses (for example .codex/AGENTS.md and GEMINI.md). A non-Claude contributor following this new onboarding doc can miss required harness-specific instructions and run with the wrong operational contract. Please either scope this section explicitly to Claude sessions or add the equivalent Codex/Gemini bootstrap paths here.
Useful? React with 👍 / 👎.
AceHack
added a commit
that referenced
this pull request
May 25, 2026
…tion (wikilinks + tags + callouts + Tasks + JSON-LD extractor) (#4977) * backlog(B-0729): Obsidian as knowledge-graph substrate — 5-layer adoption + extend where needed Aaron 2026-05-25 on the standards question: > "this is great is this a standard format for knowledge graphs are > there any standards we can follow? we had shit tons for our master > data and ontologies and graphs at lexis nexis. i'd love light git > native ai friendly ones too so the graph is transverable by all" Then on the standard-vs-extend decision: > "lets do it i like all. of that and like i said we all use obsedian > so we can use that if no standard exists and extend" > "and can do the same with foam and there are probaby others but > obsedian is the one we all have experience" Captures the layered adoption path: - L1: wikilink conversion (mechanical TS script; preserve GitHub compat via frontmatter aliases) - L2: frontmatter tags convention across rules + personas + docs - L3: Obsidian callouts for evolving documentation annotations (with GFM-compat subset for GitHub rendering) - L4: Obsidian Tasks-plugin format for enriched TODOs (due dates + priority + recurring); composes with the existing backlog rows which are project-scope structured TODOs at the same shape - L5: TS extractor emitting JSON-LD + property-graph JSON; agents can programmatically query the knowledge substrate; humans browse via Obsidian graph view; both compose Plus standards survey (RDF/OWL/SPARQL too heavy for git-native; Obsidian/Foam/Logseq/Dendron vault format as the right floor; team picks tool per individual since vault format is portable). Composes with PR #4976 (personas + onboarding + manifesto recast — the substrate this knowledge-graph would extract), Max's full-ai-cluster/k8s/applications/hat-system/graph/render.go (L5 extractor uses the same shape but for knowledge substrate vs cluster state), PR #4958 (agentic-organization design that benefits most from programmatic graph query). P2 — each layer ships standalone; team picks pace; becomes P1 when graph extraction becomes a load-bearing query surface for an agent workflow (likely after Max's TS hat-operator from B-0724 lands). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(B-0729): markdownlint + meta-irony (missing tags) + L1 design flaw + callout case Codex + Copilot + markdownlint flagged 5 substantive issues: - Markdownlint MD022 + MD032 on ### L1-L5 acceptance headings (no blank lines around headings + their following lists); fixed with regex-driven blank-line insertion - META-IRONY: a row about adopting `tags: [...]` frontmatter didn't have `tags:` in its own frontmatter. Added. - composes_with references docs/AGENT-AUTHORING-AND-PR-REVIEW.md which exists on PR #4976's branch (not yet on main). Qualified with 'pending PR #4976 merge' per the substrate-honest framing used in similar rows earlier in the session. - **L1 DESIGN FLAW caught by Codex**: original L1 proposed converting markdown `[text](path)` links to wikilinks `[[shortname|text]]`. Wikilinks DON'T render as clickable links on GitHub — would break repo navigability for non-Obsidian readers. REFRAMED L1: don't convert links; instead add frontmatter `aliases: [...]` (Obsidian resolves both markdown links AND aliases into the graph view). GitHub rendering preserved; Obsidian graph still works. This is genuinely better-of-both-worlds + the script becomes simpler (no link rewriting, just frontmatter additions). - Callout case: Obsidian accepts lowercase + uppercase but GitHub's alert syntax REQUIRES uppercase. Updated examples to use uppercase for the GFM subset (NOTE/TIP/IMPORTANT/WARNING/ CAUTION) + clarified the casing requirement. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(B-0729): align L1 acceptance with reframed alias-only strategy + MD032 on standards-survey lists Codex caught real internal contradiction — L1 was reframed in the body to use frontmatter aliases (don't convert markdown links; GitHub navigability preserved), but the L1 acceptance checklist still required the rejected wikilink conversion. Updated acceptance to match the reframed strategy. Plus MD032 on two more lists (standards survey block) that didn't have blank line before — added blank lines. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Lior <lior@zeta.dev> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 25, 2026
Merged
Merged
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
Substrate landing for the co-owner team (Aaron + Max + Addison are all LFG co-owners per Aaron 2026-05-25) — first-class persona substrate for both new contributors, the onboarding doc Max needs, and the building-codes recast of MANIFESTO.md that B-0546 was tracking.
8 files; 484 insertions / 10 deletions.
What lands
memory/persona/addison/— Addison's substratePERSONA.md— co-owner of LFG; AI cluster bootstrap PM; weight-free + travelers + tick-source-as-attractor + cage-recognition framingsSTARTING-POINT.md— verbatim from her Grok project prompt (substrate-honest preservation, no editorial)NOTEBOOK.md— placeholder; 2026-05-23 → 2026-05-25 bootstrap arc capturedmemory/persona/max/— Max's substratePERSONA.md— co-owner of LFG; agentic-organization architect (PR docs: add agentic organization architecture #4958); backend/frontend on PaaS new to K8s; TS + C# primary; framework adopted his coinings (hat = skills + opa/rbac, hat-graphs-for-policies, adversarial-hierarchy-of-traps)STARTING-POINT.md— synthesized starting point + pointer to PR docs: add agentic organization architecture #4958; Max can replace with his canonical prompt laterNOTEBOOK.md— placeholder; 2026-05-25 first-PR arc capturedBoth PERSONA files note:
docs/AGENT-AUTHORING-AND-PR-REVIEW.md— Max's onboarding docdocs/governance/MANIFESTO.md— building-codes recast per B-0546Why now
Aaron 2026-05-25:
This is the substrate-coherent landing he authorized. Max + Addison both have first-class substrate; the manifesto recast lands so when Max reads it as "the rules my agents follow" he gets the operational specification framing instead of the ideological-commitment shape that misled him initially.
Test plan
memory/persona/🤖 Generated with Claude Code