# 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

### DEC-2026-002 — Executor worker lives in a new small repo

```yaml
id: DEC-2026-002
title: "Executor worker ownership: new thin repo (proposed name: executor-worker) vs. inside activity-core"
lane: yellow
status: prepared
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."
```

## Resolved decisions

### 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
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."
```