You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Safety] Exact-base worktree creation so every subagent shares a verified identity #126
Historical GitHub issue. This issue is closed and retained for provenance. Its original body may describe an older writ/worktrees-hives architecture; do not treat retired Python/lab, Research-Hive, Graph-MVP, hook-enforcement, managed-worktree, babysit, or blanket local-merge restrictions below as current requirements.
Current product direction: https://linear.app/rpd-34/issue/RM-116/epic-writ-parallel-subagent-collaboration-ownership-and-conflict
Linear is the required task tracker; GitHub keeps source/PR/review/check history.
Important
Product goal (2026-09-05):worktrees-hives exists so worktree subagents can coordinate on one Git repository. A manager assigns isolated worktrees; workers share a hard wh-core safety/identity boundary (exact base, no ambient HEAD, no auto-merge). Prefer work that strengthens that coordination loop over analyzer theater or frozen research-hive expansion.
Important
Active stabilization work. Finish through corrected PR #131 after #129 and #133. Keep this change inside the minimal Rust safety kernel.
Goal
A worker branch/worktree must be created from an explicit, verified commit rather than ambient controller HEAD, a stale checkout, or an existing branch with ambiguous identity.
Required contract
Resolve the requested start point to one canonical commit before mutation.
Create or validate the worker branch and worktree against that exact commit.
Return the canonical start commit, resulting worker HEAD, branch identity, path, and registration evidence.
Fail closed on an existing or mismatched branch; never silently adopt it.
Preserve structured postcondition/residual data across the Rust/Python bridge.
Treat postcondition identity failures as typed operational failures rather than generic policy prose.
Compare full symbolic refs, not ambiguous shortened branch names.
Normalize and validate full commit IDs consistently across Rust and Python.
changed the title [-][Safety] Require an explicit exact base for wh worktree creation[/-][+][Safety] Exact-base worktree creation so every subagent shares a verified identity[/+]on Sep 5, 2026
Note
Historical GitHub issue. This issue is closed and retained for provenance. Its original body may describe an older writ/worktrees-hives architecture; do not treat retired Python/lab, Research-Hive, Graph-MVP, hook-enforcement, managed-worktree, babysit, or blanket local-merge restrictions below as current requirements.
Current product direction: https://linear.app/rpd-34/issue/RM-116/epic-writ-parallel-subagent-collaboration-ownership-and-conflict
Linear is the required task tracker; GitHub keeps source/PR/review/check history.
Important
Product goal (2026-09-05):
worktrees-hivesexists so worktree subagents can coordinate on one Git repository. A manager assigns isolated worktrees; workers share a hardwh-coresafety/identity boundary (exact base, no ambient HEAD, no auto-merge). Prefer work that strengthens that coordination loop over analyzer theater or frozen research-hive expansion.Important
Active stabilization work. Finish through corrected PR #131 after #129 and #133. Keep this change inside the minimal Rust safety kernel.
Goal
A worker branch/worktree must be created from an explicit, verified commit rather than ambient controller
HEAD, a stale checkout, or an existing branch with ambiguous identity.Required contract
HEAD, branch identity, path, and registration evidence.Boundary compatibility — absorbed from #135
Adding a required
--start-pointchanges the published machine request grammar. PR #131 must not label that change as compatible schema v1.Use the smallest safe pre-1.0 migration:
Do not restore ambient-
HEADbehavior for compatibility. Once this acceptance is implemented, close #135 as absorbed.Out of scope for this PR
Those paths must continue to fail closed.
Acceptance criteria
HEADidentities are returned and verified.Relationships
Planning synthesis: OpenAI Codex, 2026-08-31.