docs(identity): record the deployed role and voice pairings #1073
No reviewers
Labels
No labels
move-to-repo
coilyco-bridge-deploy
move-to-repo
coilyco-flight-deck-agent-compose
move-to-repo
coilyco-gaming-eco-app
move-to-repo
coilysiren-inbox
move-to-repo
unknown
🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/sirens-echo!1073
Loading…
Reference in a new issue
No description provided.
Delete branch "record-lane-role-voice-pairings"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #1070.
What #1070 assumed, and what is actually true
The two axes were already documented, in
docs/sirens-echo-identity.mdunder a section literally titled "Role and voice are separate axes". #1070 was filed againstdocs/sirens-echo-role-and-voice.md, which does not exist -coilyco-bridge/deploy's README cites that path and it is a dead reference. Repointing it is a separate change in that repo.So the first acceptance criterion is met by reading rather than writing, and two of the four remain.
What was genuinely missing
Dowel was absent entirely. It composes
engineerand answerssocial, so the deployed set is Echoops/neutral, Deepcreator/social, Dowelengineer/social. Deep and Dowel are what makes the independence a fact rather than a claim: same voice, different doctrine. Nothing in this repository recorded that.Dowel is also the near-miss the section exists to prevent. It was briefly set
neutralto track its engineer role, which would have composed a meld the same prompt then bars from expression. The reasoning is incoilyco-bridge/deploy'ssirens-dowel-definition.ymland had no counterpart here.Neither axis describes the tool surface. The roster is deployment-owned, and Echo's is mostly catalogues while its doctrine is the operator charter, so reading
opsto predict what Echo can reach gets the wrong answer. That is the mismatch #1070 asked to have recorded, and it is now recorded as a live boundary rather than resolved.A correction to #1070
Its body says "two lanes on one diagonal of a 2x2, nothing has ever occupied the other one." That is wrong because it omitted Dowel, and Dowel is the entry that proves the axes vary independently. The issue undercounted the evidence for its own argument.
Why this did not become its own doc
The obvious move was to split the section into
docs/sirens-echo-role-and-voice.mdand fix deploy's dead reference at the same time. The caps reject it:docs/is at 40 of 40 for thelargeband, andcatalog-doc-sizesays outright that splitting one doc to clear a size cap trades one violation for another.Worth flagging as a standing constraint rather than a detail of this PR: every page in
docs/is within about 100 characters of the 8000 cap and the directory is at its count cap.sirens-echo-reply-assembly.mdalready sits at exactly 7998, andidentity.mdnow matches it. The next doc addition anywhere in this repository needs a merge first. Evidence forcoilysiren/inbox#374.Verification
just gategreen: build, policy-check, vet, test, test-skips, pre-commit. No behavior change, no code change, one documentation file touched.