This is the filed review document, copied at 09:19 EDT. Its dated claims remain historical. See the current update before acting on an old sign-in request or delivery status. Reply in chat with decisions or feedback.
These are proposed seeds, and production memory remains off under Toberton's 20 October instruction. Nothing in this work changed a memory flag or wrote to Honcho. The older activation-readiness note records an empty admitted JA session list; that historical snapshot is not a fresh production readback. Seed writes remain a separate later step, with the final batch and count reviewed under the existing ledger decision.
The sidecar, 2026-10-20-seeds.json, holds each exact string with its sources, dates, audience and rationale. The counts below come from that file.
Once a batch is approved, written, and a later decision enables the JA read, the justanother peer would give JA-facing replies a short identity card and a set of stable conclusions. The mechanism shapes what belongs in it. Honcho puts the card into every chat call, and the memory guidance caps it at 40 strings and cuts anything past that without warning. Conclusions are the searchable body: a read returns about 25 by default, chosen by semantic match and frequency. Those figures come from the October 3 guidance, which I read but did not re-check live.
That is why the proposal keeps to stable identity and relationships. Ben's recorded role in door decisions is more durable than whether a particular brunch venue is still open. The latter can change tomorrow, and a later memory read would not by itself verify the current venue decision. Current tasks therefore stay in their owning records. Slack Lists hold owners, dates and completion, and repo records hold decisions. The seed names no current task status.
Derived material is a separate concern, and it is not part of this batch. Honcho's dreaming can delete facts it judges outdated, add derived conclusions and rewrite the peer card, and the deriver adds conclusions from ordinary sessions. The 3 October guidance records these behaviors, with dreaming on by default. Before activation, every JR read must filter derived and seeded items alike by requester and audience, because the labels in this file say nothing about derived items. This memo did not read the justanother peer's current settings, and the activation step decides them.
A single justanother peer does not enforce per-conclusion audience labels, so the labels in the sidecar are proposal metadata and protect nothing by themselves. The proposal therefore has two parts, and only the first is a candidate for writing.
| Batch | Card | Conclusions | Total | Status |
|---|---|---|---|---|
Team-safe proposed batch (all team) |
10 | 9 | 19 | Proposed; write held |
Restricted candidates (all toberton_only) |
0 | 0 | 0 proposed, 5 held | Held; no write until retrieval isolation is proven |
| Inferences | n/a | n/a | 2 | Not written |
The restricted candidates need a separate implementation check that proves retrieval isolation, such as a separate peer or an enforced reader filter. The team batch does not depend on that check, because every item in it is visible to the team. Nothing here is a numerical target. The team batch has 19 strings because the sources support that many stable identity and relationship facts.
P01 Name: JustAnother (JA), an event business
P02 Legal entity: Just Another Holdings LLC (New York)
P03 Founder: Toberton (team.md writes Tobi O.)
P04 Co-Founder, Community & Vibe Curation: Tobi A., a different person from Toberton
P05 Name note: 'Tobi' alone does not identify Toberton or Tobi A.
P06 Regional Lead, JA DC (team.md marks the role '(forward)'): Ben (Slack: Big Ben)
P07 Sound + Resident DJ: Osa (Slack: Mudia)
P08 Brand Partnerships & Guest Experience (co-lead): Deja (Slack: Wynndee)
P09 Brand Partnerships & Guest Experience (co-lead): Chrissy
P10 Creative, Brand & Content (listed as incoming): Makala
P02 is a proposed team seed. Its exact source is the filed Articles of Organization (page 1, item FIRST, New York filing stamp 27 March 2026), with the prose name at STATUS.md line 521. The AGENTS legal gate reserves legal decisions to Toberton, but it does not by itself make the entity name restricted. The team audience is a proposal, not an approved write, and the batch write waits for Toberton's word under ledger row 62.
| ID | Conclusion |
|---|---|
| E01 | justanother runs one-off events, recurring classes (Pilates, spin, run club and dance), merch and social content |
| E02 | Toberton's lane is strategy and go/no-go decisions, economics, finance, venue terms and contracts, creative direction and final visual output, merch, LLC and compliance |
| E03 | Tobi A.'s lane is community and hospitality, audience growth and engagement, partner and host touchpoints, event calendar coordination, and live mic and DJ transitions |
| E04 | Osa's lane is sound curation, AV and gear, DJ screening and scorecard, run-of-show sound, and resident DJ work |
| E05 | Deja's lane is sponsor and partner touchpoints, guest experience and the door, and day-of capture coordination |
| E06 | Chrissy's lane is sponsor and brand-partnership sourcing and activation, and guest experience and the door |
| E07 | Ben runs the JA DC standup and has the final say on door comp exceptions and live door-price changes at events Ben attends |
| E08 | Makala's listed lane is creative direction with Toberton, visual identity consistency, social and content creation, non-party creative initiatives, and systems hygiene |
| E09 | JustAnother™ is the outward name, JA the internal shorthand, and JARD the historical name of the rooftop series |
The card carries names, Slack aliases and roster titles. The conclusions carry the scope of each lane. No fact appears in both places.
toberton_only)| ID | Candidate | Why it is held |
|---|---|---|
| R01 | Naeem, the former partner and creative lead, departed in June 2026 and is no longer on the JA team | Personnel. The closed separation record is not referenced. |
| R02 | Patrice (Pat) is no longer on the JA team; Toberton confirmed this on 8 September 2026, and no departure date is recorded | Personnel. |
| R03 | Kevin is no longer part of the JA team; Toberton confirmed this on 27 September 2026 | Personnel. The dated roster claim is kept; later STATUS mentions are not used as evidence of a current role. |
| R04 | Chrissy's work reaches Toberton through his Messages thread with her rather than through Slack | Describes Toberton's private channel. |
| R05 | Toberton treats finance, reconciliation, legal, governance, personnel, partner-sensitive work, early ideas and personal operations as private-by-default records | Personal overlay. Its default stays with him. |
I-MAKALA. Makala probably holds active social and creative work now. playbooks/slack.md names #socialmedia as Makala's lane, and STATUS records an October 8 kit packaged for that work. The roster still says incoming, so P10 keeps that status exactly, and the active-work reading stays out of the batch.
I-WOB72-TOBI. The "teammate Tobi" in the WOB-72 scope is inferred to be Tobi A. WOB-72 names Toberton and Ben as the core and keeps "teammate Tobi" distinct from both. The roster's only other Tobi is Tobi A. The local huddle record lists "Tobz", which the ja-meetings skill gives as one of Tobi A.'s names. I made no live Slack lookup. Before any permission path matches "teammate Tobi", it must resolve to Tobi A.'s immutable Slack user ID, not a display name. That is an implementation check, not a new permission choice.
.biz address (verified 12 October) and Toberton's .nyc account can both exist. Email addresses are excluded from memory whatever their domain, so no address is written.Legal name, resolved. The articles of organization say JUST ANOTHER HOLDINGS LLC, with a New York filing stamp of 27 March 2026. The JA Holdings LLC filenames are shorthand. I read the first page of the PDF as an image, since it has no extractable text.
"Tobi", handled rather than resolved by the sources. Three uses of the bare name collide. P05 states the naming fact. The WOB-72 mapping is the inference above, and its implementation check decides it.
The sidecar lists 23 exclusions. The groups are below.
| Group | Examples | Why it stays out |
|---|---|---|
| Dated event and venue material | The November brunch, venue outreach, event finance rules | Time-bound. Another worker owns venue extraction, and finance is limited by WOB-72. |
| Money, access and credentials | Revenue, payouts, bank details, who may see what, phone numbers, street addresses | Not needed for memory. WOB-72 governs access. These are named exclusions. |
| Email addresses | Ben's verified address, Toberton's account addresses | Not memory, whatever the domain. |
| Agent permissions and operating rules | Banking write authority, Instagram, Square and Partiful write authority, the go/no-go gate list, "hold outward sends for a yes", "read AGENTS.md first" | Runtime rules for agents. They stay in AGENTS.md and the access records, and they are not facts about the business. |
| Tool, channel and workflow inventories | Repo paths, bot identities, channel IDs, the room kit, readback format, Slack List placement, the playbook index | Infrastructure that goes stale, and rule-like routing that is read at the point of use from the owning document. |
| Meeting content | Minutes, debriefs, transcripts | Discussion is not a stable fact, and the transcripts carry mis-hearings. |
| Personnel and legal detail beyond roster claims | The separation record, departure circumstances | The closed legal record is not referenced. Only the dated roster claims are held. |
| System and personal material | Memory-architecture decisions, Claude auto-memory entries, personal peer examples from the October 3 guidance, JR implementation | Not facts about JA, or not source records. |
The proposed collectors read existing sources and emit candidates with their provenance; a person approves anything that reaches Honcho. A first local collector is now implemented and merged through PR79. It extracts one explicitly selected file or section and roster rows. The broader update, deletion and correction behavior below remains proposed; the current script does not track those changes or write memory.
| Seam | What it can emit | On update | On deletion | On correction |
|---|---|---|---|---|
team.md rows |
One roster fact per row | A new candidate with the new commit date; the old one is superseded | Marked retired by source; no delete proposed | Both versions cited until the replacement is approved |
| Playbooks and event READMEs | Identity and lane facts only | As above | As above | As above |
AGENTS.md and the overlay |
Identity and naming facts only | As above | As above | As above |
| Meeting minutes ("What was decided") | A decision, keyed to the meeting date | As above | As above | As above |
| STATUS dated entries | Decisions only; status lines are dropped | As above | As above | As above |
| Transcripts | Evidence only | Not seeded | Not seeded | Not seeded |
| Personal debriefs | Candidates that carry an account field | Held at toberton_only |
Same | Same |
Attribution is where transcripts and debriefs must stay apart. A transcript records what was said, but its speaker labels are machine guesses, and the raw version has none. A debrief is Toberton's own account. Ledger row 57 bars recording any capture turn as either peer's words, so every candidate carries an account_of field and a mentioned field. A speaker is recorded only when a transcript or a direct quote supports it. Suppose a debrief says "Ben thought the date was wrong". The candidate would read account_of: Toberton, mentioned: Ben, and it would never state what Ben believes. That candidate is toberton_only by default, and it broadens only when its source explicitly permits.
Two later dependencies belong to the build, not to this proposal. A deletion from Honcho needs an export first (ledger row 58), and the scope of ledger row 60, which covers memories about Toberton, must be confirmed for the justanother peer before any correction is written.
jq, counted the figures from the file, checked every cited path in this checkout, and pinned line numbers by search. The overlay is cited by its real path outside the checkout. I read the formation PDF's first page only.--model claude-haiku-5-5 --effort xhigh. That shows the requested flags, not the effort applied to each call.