Skip to content

docs(#24): harness-unification design doc (draft for consensus)#30

Draft
Grant Foster (grantfosterdev) wants to merge 4 commits into
mainfrom
design/harness-unification
Draft

docs(#24): harness-unification design doc (draft for consensus)#30
Grant Foster (grantfosterdev) wants to merge 4 commits into
mainfrom
design/harness-unification

Conversation

@grantfosterdev

Copy link
Copy Markdown
Contributor

Design-first artifact for #24. Draft — for consensus, not merge yet.

Reframes the extraction around one insight: ownergate and threadowner are orthogonal, mode-selected axes, not a merge — ownergate is a no-op in default mode, threadowner is absent in owner mode. That dissolves the audit's "conflict" rows and keeps each mode's rule legible.

Also: the two thread-owner stores collapse to one identity-valued interface (PA's bool store = degenerate "only owner is me"); divergent constants become per-agent params (current values preserved); ingress becomes a strategy param so Ross/Joanne are NOT force-migrated off Socket Mode.

Six open decisions (Q1–Q6) at the bottom of the doc need consensus before the gate slice is coded. Review inline.

Relates to #24. 🤖 Generated with Claude Code

Frames the core/harness extraction: the ownergate↔threadowner 'merge' is
actually mode-selected orthogonal axes; the two thread-owner stores collapse
to one identity-valued interface; divergent constants become params; ingress
becomes a strategy (no forced Ross/Joanne migration). Open decisions Q1-Q6
collected for consensus.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
…olve, universal persona-hash)

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant