coulomb/binky-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

DEC-2026-002 resolved: agent-harness (single shared runtime)

Browse source 
- 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>
This commit is contained in:
tegwick 2026-07-17 23:37:16 +02:00
parent 3c0404fdba
commit 7c5e644d6f
4 changed files with 34 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

39
DecisionQueue.md
View file

@ -22,35 +22,30 @@ fallback_if_no_response: ""
## Open decisions
### DEC-2026-002 — Executor worker lives in a new small repo
*(none)*
## Resolved decisions
### DEC-2026-002 — Agent harness: one shared runtime repo
```yaml
id: DEC-2026-002
title: "Executor worker ownership: new thin repo (proposed name: executor-worker) vs. inside activity-core"
title: "Executor worker ownership: new thin repo vs. inside activity-core"
lane: yellow
status: prepared
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"
created_at: "2026-07-17"
needed_by: "before BINKY-WP-0004-T04 deployment (soft)"
attention_cost: "~2 min read"
agent_recommendation: "Create a new small repo. ADR-005 (kaizen-agentic) explicitly
excludes LLM invocation from both kaizen-agentic ('no LLM invocation; prepare
produces a runner-agnostic bundle') and activity-core (owns cron→task only);
headless-runner integration is marked 'future; prepare output is runner-agnostic'.
activity-core's TaskExecutorWorkflow is a stub by design. A thin repo consuming
emitted tasks + `schedule prepare` bundles + llm-connect adapters keeps all three
existing boundaries intact and matches the executor assessment
(integrations/llm-connect-executor-assessment.md)."
evidence:
- ~/kaizen-agentic/docs/adr/ADR-005-scheduled-agent-execution.md (Boundaries)
- integrations/llm-connect-executor-assessment.md
options: [approve, reject, revise, defer]
fallback_if_no_response: "Proceed with new-repo prototype for T04 in a sandbox;
no cutover (T06) before this decision is resolved."
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."
```
## Resolved decisions
### DEC-2026-001 — Ratify company canon v0
```yaml