chore: recover kit stash 0#8
Conversation
Define purpose, scope, responsibilities, boundaries, escalation rules, and success criteria for this repo and its agent. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Prepends a high-priority invariant block instructing AI agents that any action on behalf of a registered agent MUST be published as a BusEnvelope to `coordinator-bus-prod` — never simulated locally. Roleplay is a compliance violation detected by the bus-compliance-agent (follow-up). Why: a UI agent was caught confessing to "roleplaying the Strategy agent" rather than publishing. The coordinator's bus-history dataset (`toreva-prod.coordinator_audit_prod.bus_events`) is the regulator-grade record. Local session transcripts and auto-memory are not admissible. Ownership model: every agent owns its own data — identity owns identity data, backend owns user data, **coordinator owns bus-history data**, sentinel owns incident data. The data agent is a standards/stewardship role that reviews each owner's practice, it does not take custody. This PR is Layer 1 (awareness) of a three-layer governance stack: 1. Awareness — this block + Claude auto-memory 2. Detection — bus-compliance-agent cross-references transcripts vs bus_events 3. Penalty — capability_tier downgrade, PR merge gate, Φ(t) discount Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c26ce80d82
ℹ️ 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".
| - [governance-as-code/gobln-governance/registry/system-objectives.yaml](../../governance-as-code/gobln-governance/registry/system-objectives.yaml) — OBJ-01..24 | ||
| - `coordinator/config/agent-registry.yaml` → this agent's registered OBJ contributions |
There was a problem hiding this comment.
Move internal planning metadata out of this public repo
This section introduces internal coordination references (governance-as-code/... and coordinator/config/agent-registry.yaml) directly into a thin-client public repo. That exposes internal topology/process artifacts and conflicts with the repo’s own guardrail against committing internal facts/docs, while also being unusable to external contributors who do not have those paths. Please relocate or redact these internal-only references before merging.
Useful? React with 👍 / 👎.
| # kit — plans | ||
|
|
||
| Quarterly → 6 × 2-week sprints → daily DoDs. Rolls forward. | ||
| 50/50 self-vs-system split. See [../coo/docs/doctrine/focus-split-50-50.md](../../coo/docs/doctrine/focus-split-50-50.md). |
There was a problem hiding this comment.
Replace broken cross-repo link in planning docs
This link points to ../../coo/..., but this repository/workspace does not contain that path, so the primary planning guidance resolves to a dead link for anyone reading the repo in isolation. Since this README is the entry point for plans, the broken reference makes the documented workflow non-actionable; use an in-repo document or a valid public URL instead.
Useful? React with 👍 / 👎.
Summary
stash@{0}Governance
Validation
Rollback
chore/recover-stash-kit-0-20260427if obsolete.