binky-control/DecisionQueue.md
tegwick 7c5e644d6f DEC-2026-002 resolved: agent-harness (single shared runtime)
- DecisionQueue: moved to resolved log with rescoped outcome (three-layer
  model; binky-control = tenant #1); hub decision resolved
- Secret lanes doc: identifiers renamed executor-worker → agent-harness
  before any provisioning happens
- Cutover runbook + WP-0004-T06: gate 1 done; deployment gate now points
  at HARNESS-WP-0001-T06/T07 in the agent-harness repo

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 23:37:16 +02:00

65 lines
2.1 KiB
Markdown

# Decision Queue
> Status: live document — decisions awaiting the founder, as prepared
> approval packages (`AutonomyPolicy.md`). Agents append; Bernd resolves.
> Resolved decisions move to the log below with outcome and date.
## Item template
```yaml
id: DEC-2026-NNN
title: ""
lane: yellow | orange | red
status: prepared | resolved | deferred
created_at: ""
needed_by: ""
attention_cost: ""
agent_recommendation: ""
evidence: []
options: [approve, reject, revise, defer]
fallback_if_no_response: ""
```
## Open decisions
*(none)*
## Resolved decisions
### DEC-2026-002 — Agent harness: one shared runtime repo
```yaml
id: DEC-2026-002
title: "Executor worker ownership: new thin repo vs. inside activity-core"
lane: yellow
status: resolved
outcome: "approved, rescoped: single shared `agent-harness` repo for ALL projects"
resolved_at: "2026-07-17"
resolved_by: Bernd
state_hub_decision_id: "63620255-59d0-4109-bdee-4d0644c450e5"
consequence: "Three-layer model: blueprints in kaizen-agentic; instances as
declarative manifests + .kaizen state in consuming repos (no code, no
credentials, named tool profiles, pinned harness major); agent-harness is
the single credential holder / policy enforcer, deployed once on Railiance,
multi-tenant — binky-control is tenant #1. executor-worker prototype
adopted as the harness seed. Recorded as agent-harness ADR-001 +
docs/architecture.md; foundation work in HARNESS-WP-0001."
```
### DEC-2026-001 — Ratify company canon v0
```yaml
id: DEC-2026-001
title: "Ratify company canon v0 (INTENT, AutonomyPolicy, and companion docs)"
lane: red
status: resolved
state_hub_decision_id: "14383059-7698-4566-a664-858e3d49ee8d"
outcome: approved with edits
resolved_at: "2026-07-16"
resolved_by: Bernd
edits: "Railiance role refined to reliable deployment & operations (code → SaaS ecosystems and products); Operational Knowledge added as fourth ecosystem pillar (value from experience). Edits propagated to EcosystemMap.md and DogfoodPolicy.md."
evidence:
- INTENT.md (v1.0)
- AutonomyPolicy.md
consequence: "Canon v1.0 in force; AutonomyPolicy lanes active; Green/Blue work may proceed unattended."
```