forge-workflow 0.0.10 → 0.1.0-beta.2

package/docs/PROJECT_DESIGN.md

@@ -0,0 +1,685 @@
+# Forge Project Design and Decision Registry
+
+**Status:** Canonical living registry for current Forge design direction  
+**Last reviewed:** 2026-06-08  
+**Update rule:** Current accepted design decisions live here. Rationale and evidence must link to ADRs and work artifacts.
+
+## How to read this file
+
+1. Start here for current Forge architecture and direction.
+2. Follow ADR links for immutable cross-cutting architectural decisions once they exist.
+3. Follow `docs/work/**` links for full discussion, spike evidence, evaluator notes, and local decisions.
+4. Treat work-folder decisions as evidence unless promoted here or accepted through a Kernel decision event.
+5. If this file conflicts with an unsuperseded ADR or accepted Kernel decision event, that is a decision-registry error and should block merge.
+
+## Current design snapshot
+
+Forge is moving toward a native Kernel/control-plane architecture:
+
+- **Authority:** SQLite WAL is the local single-machine Kernel authority; team/multi-machine authority requires a serialized server authority later. Routine issue, workflow, claim, run, and knowledge writes must not depend on committing repository metadata to the protected default branch.
+- **Beads/Dolt:** Beads and Dolt remain compatibility/projection/history/migration surfaces, not the core Kernel write path.
+- **Project Knowledge:** Project Knowledge is verbatim-first and rebuildable. Summaries, extracted facts, Context Mode output, Graphify output, and agent memories are derived/proposal material unless accepted by Kernel event.
+- **Knowledge storage:** Knowledge starts in the same local SQLite Kernel DB by default, but only behind a clean `KnowledgeStore` boundary so it can later move to `knowledge.sqlite`, server-side search, or another backend.
+- **Work model:** Forge uses a Work Graph plus Planning Buckets and an Agent Execution Ledger. Agile/Scrum/Kanban are views/presets, not the database ontology.
+- **CLI:** `forge` CLI becomes the canonical Kernel-first local command surface through incremental cutover.
+- **MCP:** Forge MCP starts read-only over the same service contracts as CLI; write tools come later with revision/idempotency/conflict guards.
+- **Observer:** Background observers record evidence/proposals/session events first; they do not silently mutate project truth.
+- **Architecture notes:** Architecture-significant observations, domain rules, subsystem behaviors, constraints, and open questions must be captured as scoped architecture records. `PROJECT_DESIGN.md` remains the top-level map; detailed records live under `docs/architecture/**` and work/ADR evidence.
+- **Hook policy:** Agent-native hooks are the preferred architecture-capture UX; Forge CLI checks own the policy; Lefthook is a Git adapter/fallback; CI is the non-bypassable gate. Agents must not use `--no-verify` or equivalent hook-disabling bypasses without explicit audited authorization.
+- **Portability:** Routine Beads runtime/export state under `.beads/` is local and non-versioned. Explicit Kernel exports may provide reviewable clone/bootstrap snapshots, but repository projection files are not the routine authority channel for close/verify state. Local-only state uses the local Kernel SQLite authority; cross-machine or team state uses serialized server authority.
+- **Work-item taxonomy:** 4 issue types (`epic`, `task`, `bug`, `decision`), 5 stored statuses; `ready`/`blocked` are derived read-model facts; a single numeric rank is authoritative for ordering.
+- **Agent interface:** Forge ships its own agent surface (`forge prime`, kernel-facing JSON-first CLI, skills as thin CLI wrappers); agent-interface parity gates Beads retirement.
+- **Supported harnesses:** Claude Code, Codex, and Cursor are the supported harness set; Hermes is the planned addition. Other previously-supported harness surfaces are removed.
+
+## Decision registry
+
+### PD-20260606-sqlite-local-authority
+
+```yaml
+id: PD-20260606-sqlite-local-authority
+topic: authority.local.storage
+status: accepted
+decision_date: 2026-06-06
+last_reviewed: 2026-06-08
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d1--sqlite-wal-is-local-authority-only
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d7--sqlite-is-the-first-kernel-authority-dolt-remains-first-class-projectionhistory
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/storage-decision.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Use SQLite WAL as the first Forge Kernel local authority. Do not present SQLite/git files as safe multi-machine/team authority.
+
+**Implications:**
+
+- Local broker writes go through Kernel transaction/CAS/idempotency rules.
+- Team writes require future serialized server authority.
+- Dolt is not part of the initial Kernel transaction contract.
+
+### PD-20260606-beads-dolt-projection
+
+```yaml
+id: PD-20260606-beads-dolt-projection
+topic: projection.beads-dolt
+status: accepted
+decision_date: 2026-06-06
+last_reviewed: 2026-06-08
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d2--beads-remains-migrationprojection-during-kernel-rollout
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d7--sqlite-is-the-first-kernel-authority-dolt-remains-first-class-projectionhistory
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/discussion-addendum.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Keep Beads/Dolt as import/export/projection/history compatibility while Kernel matures. Do not let Beads/Dolt shape the core Kernel write path.
+
+**Implications:**
+
+- Beads memory/comments/issues can be imported as source material or projections.
+- Beads content is not automatically accepted Forge truth.
+- New authority work should route through Forge Kernel contracts.
+
+### PD-20260606-verbatim-first-knowledge
+
+```yaml
+id: PD-20260606-verbatim-first-knowledge
+topic: knowledge.truth-model
+status: accepted
+decision_date: 2026-06-06
+last_reviewed: 2026-06-08
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d3--verbatim-first-project-knowledge-layer
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/agent-memory-federation.md
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/discussion-addendum.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Project Knowledge indexes verbatim artifacts/events first. Summaries, extracted facts, agent memories, Context Mode output, and Graphify output are derived/proposal material unless accepted by Kernel event.
+
+**Implications:**
+
+- Source links and provenance are mandatory for accepted/project-relevant knowledge.
+- `forge orient`, `forge recap`, and `forge knowledge search` should return authority/source/proposal labels.
+- Conflicting memory becomes a conflict/proposal, not silent truth.
+
+### PD-20260608-knowledge-store-boundary
+
+```yaml
+id: PD-20260608-knowledge-store-boundary
+topic: knowledge.storage.boundary
+status: accepted
+decision_date: 2026-06-08
+last_reviewed: 2026-06-08
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/discussion-addendum.md#1-memory--project-knowledge
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decision-registry-mechanism.md
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decision-options.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Start Knowledge in the same local SQLite Kernel DB by default, but behind a clean `KnowledgeStore` boundary so it can later move to `knowledge.sqlite`, a server/search backend, or another read-model store.
+
+**Boundary rule:**
+
+```text
+Kernel tables      = authority
+Knowledge tables   = rebuildable read model / source index / proposals
+Accepted facts     = Kernel events
+Derived summaries  = not authority
+```
+
+**Sidecar/server gates:** Move Knowledge out of the Kernel DB only when FTS/vector load, rebuild/compact behavior, team/server search, privacy, or operational isolation justifies the complexity.
+
+### PD-20260606-work-graph-planning-buckets
+
+```yaml
+id: PD-20260606-work-graph-planning-buckets
+topic: backlog.model
+status: accepted
+decision_date: 2026-06-06
+last_reviewed: 2026-06-08
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/backlog-frontend-model.md
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/discussion-addendum.md#2-backlog--issues--sprints--methodology
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decision-options.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Forge should use Work Graph + Planning Buckets + Agent Execution Ledger. Agile/Scrum/Kanban are presets/views, not the primary ontology.
+
+**Core model:**
+
+```text
+issues / work_items
+issue_relations
+planning_buckets
+issue_bucket_memberships
+claims
+sessions / runs
+stage_runs
+events
+readiness
+board_positions
+```
+
+**Implications:**
+
+- Multiple product/team backlogs are planning buckets or views.
+- Sprints/releases/milestones/queues share the planning bucket mechanism.
+- Claimable/schedulable work is an issue/work item.
+- Status, workflow stage, claim state, bucket state, and run status stay separate.
+
+### PD-20260606-cli-kernel-first
+
+```yaml
+id: PD-20260606-cli-kernel-first
+topic: cli.contract
+status: accepted
+decision_date: 2026-06-06
+last_reviewed: 2026-06-08
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/discussion-addendum.md#3-forge-cli
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decision-options.md#3-forge-cli
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Use canonical Kernel-first CLI with incremental cutover. CLI remains the universal local integration contract; MCP and observers use the same service contracts.
+
+### PD-20260606-readonly-mcp-first
+
+```yaml
+id: PD-20260606-readonly-mcp-first
+topic: mcp.contract
+status: accepted
+decision_date: 2026-06-06
+last_reviewed: 2026-06-08
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/discussion-addendum.md#4-forge-mcp-and-background-observer
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decision-options.md#4-forge-mcp
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Build Forge MCP read-only first over Kernel-backed status/orient/recap/issue/backlog/knowledge/graph queries. Write MCP comes later and must require expected revision, idempotency key, actor/session/worktree metadata, and conflict handling.
+
+### PD-20260606-observer-evidence-proposals
+
+```yaml
+id: PD-20260606-observer-evidence-proposals
+topic: observer.authority
+status: accepted
+decision_date: 2026-06-06
+last_reviewed: 2026-06-08
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/discussion-addendum.md#4-forge-mcp-and-background-observer
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Background observer adapters should initially record evidence, proposals, session events, files touched, commands/tests run, and recap candidates. They must not silently close issues, accept decisions, reassign claims, or mutate project truth.
+
+### PD-20260608-mandatory-architecture-note-capture
+
+```yaml
+id: PD-20260608-mandatory-architecture-note-capture
+topic: architecture.capture.mandate
+status: accepted
+decision_date: 2026-06-08
+last_reviewed: 2026-06-08
+adr: pending
+evidence:
+  - docs/architecture/index.md
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/architecture-note-governance.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Architecture-significant information must be captured when changed or discovered, but it does not all live inline in this file. `docs/PROJECT_DESIGN.md` is the top-level current map, while detailed scoped records live under `docs/architecture/**`, ADRs, and work-folder evidence.
+
+**Record types:**
+
+```text
+architecture_note      observed architectural fact, rule, constraint, or behavior
+architecture_decision  accepted direction after tradeoffs
+architecture_question  unresolved ambiguity or decision needed
+architecture_conflict  contradictory records or code/docs disagreement
+architecture_exception deliberate deviation with owner, reason, and review/expiry
+```
+
+**Mandatory rule:** If future users or agents would need the information to avoid breaking the system, capture it with source evidence.
+
+**Scale rule:** Large projects should organize architecture records by project/domain/bounded-context/subsystem/component/API instead of growing this file into a 10,000-line monolith.
+
+### PD-20260608-hook-backed-architecture-capture
+
+```yaml
+id: PD-20260608-hook-backed-architecture-capture
+topic: architecture.capture.hooks
+status: accepted
+decision_date: 2026-06-08
+last_reviewed: 2026-06-08
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/architecture-capture-hooks.md
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/architecture-note-governance.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Use hooks as a layered enforcement surface for mandatory architecture capture, but do not make Lefthook the center. Agent-native hooks are the preferred interactive experience; Forge CLI checks own the policy; Lefthook is a repo-local Git adapter/fallback; CI required checks and later Kernel authority validation plus KnowledgeStore indexing/proposal validation are the durable enforcement boundaries.
+
+**Boundary:** Hooks make missing architecture capture hard to miss, but they are not the source of truth. Lefthook depends on install/worktree state and can be bypassed; CI and future Kernel authority are the durable enforcement boundaries.
+
+**Rule:** Architecture-sensitive changes require an explicit architecture-impact declaration. If architecture changed or was discovered, the work must add/update an architecture record, open a question/conflict, or update/supersede accepted design direction. Agents must not use `git commit --no-verify`, `git push --no-verify`, `HUSKY=0`, `LEFTHOOK=0`, `git -c core.hooksPath=...`, script-mediated hook bypasses, or hook removal to bypass Forge checks unless explicitly authorized through an audited Forge bypass event.
+
+### PD-20260611-kernel-jsonl-portability
+
+```yaml
+id: PD-20260611-kernel-jsonl-portability
+topic: portability.projection
+status: accepted
+decision_date: 2026-06-11
+last_reviewed: 2026-06-11
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d16--kernel-jsonl-portability-projection
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/plan-evaluation.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** The Kernel may own deterministic JSONL export/import artifacts for clone/bootstrap and reviewable portability snapshots. These exports are explicit projections, not the normal write path and not the durability mechanism for routine close/verify state.
+
+**Implications:**
+
+- Acceptance: fresh machine, `git clone`, no Beads/Dolt installed can import an explicit Kernel projection when one is intentionally published.
+- Local-only work remains durable in local SQLite without requiring default-branch commits.
+- Team or cross-machine work requires server authority before writes are accepted as shared truth.
+- Retirement claims under PD-20260606-beads-dolt-projection cannot pass until portability works without putting every local state mutation on the Git hot path.
+
+### PD-20260613-authority-state-not-repo-metadata
+
+```yaml
+id: PD-20260613-authority-state-not-repo-metadata
+topic: authority.persistence.boundary
+status: accepted
+decision_date: 2026-06-13
+last_reviewed: 2026-06-13
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/workflow-friction-amendments.md
+  - docs/reference/FORGE_KERNEL_STORAGE_MODEL.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Routine issue, workflow, claim, run, and knowledge writes must not depend on committing repository metadata to the protected default branch. Local-only state uses the local Kernel SQLite authority. Cross-machine or team state uses serialized server authority. Repository files are project code/docs/config plus explicit projection artifacts, not the live database for normal close/verify work.
+
+**Implications:**
+
+- `/verify` closing an issue must not require a follow-up PR or direct push to persist tracker metadata.
+- When no server is configured, close/verify state is local-only and should be reported that way.
+- When team mode is configured, close/verify writes go to server authority, and server-side projection workers update GitHub/Linear/Beads compatibility state.
+- Beads/Dolt and Kernel JSONL exports remain explicit import/export/projection surfaces, not the hot-path authority.
+- Acceptance: fresh machine, `git clone`, no committed `.beads/` runtime state → `forge setup` initializes local Beads state without dirtying the repo; team/cross-machine status comes from server authority or an explicit projection import.
+- Retirement claims under PD-20260606-beads-dolt-projection cannot pass without a Beads-local setup path and explicit projection/import-export replacement.
+
+### PD-20260611-sqlite-builtin-driver
+
+```yaml
+id: PD-20260611-sqlite-builtin-driver
+topic: authority.local.driver
+status: accepted
+decision_date: 2026-06-11
+last_reviewed: 2026-06-11
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d17--sqlite-driver-builtin-no-native-compile
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Use builtin `node:sqlite` and/or `bun:sqlite`, selected by runtime feature detection, for the Kernel broker. No native-compile dependency in the default install.
+
+**Implications:**
+
+- `node:sqlite` is unflagged from Node.js ≥ 22.13.0 but is still Release Candidate / experimental; the broker probes for it at runtime and falls back to `bun:sqlite` rather than gating on Node major version alone.
+- Driver conformance tests (WAL, busy timeout, atomic event+CAS+outbox, backup/checkpoint, FTS5) and the detection/fallback path run against the chosen builtin drivers on all supported platforms.
+- This selection blocks all local-broker safety work and must land first.
+
+### PD-20260611-work-item-taxonomy
+
+```yaml
+id: PD-20260611-work-item-taxonomy
+topic: workgraph.taxonomy
+status: accepted
+decision_date: 2026-06-11
+last_reviewed: 2026-06-11
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d18--taxonomy-collapse-4-types-5-statuses-single-rank
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/beads/backlog-taxonomy.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Issue types are `epic`, `task`, `bug`, `decision` (`feature`/`story`/`chore`/`spike` are labels). Stored statuses are `open`, `in_progress`, `review`, `done`, `cancelled`; `ready`/`blocked` are derived read-model facts. A single numeric rank is authoritative for ordering; P0–P4 is a display projection.
+
+**Implications:**
+
+- Refines PD-20260606-work-graph-planning-buckets: the Work Graph ontology uses this narrow enum set.
+- Must land before the 0.0.20 Kernel schema freezes a wider version.
+
+### PD-20260611-local-filesystem-doctor-gate
+
+```yaml
+id: PD-20260611-local-filesystem-doctor-gate
+topic: authority.local.filesystem
+status: accepted
+decision_date: 2026-06-11
+last_reviewed: 2026-06-11
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d19--filesystem-doctor-is-a-default-on-gate
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Before placing `kernel.sqlite`, Forge detects network shares, cloud-sync folders (OneDrive/Dropbox/Google Drive), and WSL-crossing paths, and refuses or warns with remediation guidance. The doctor check is a prerequisite for kernel default-on, shipped with the broker driver work.
+
+### PD-20260611-bd-retirement-kill-list
+
+```yaml
+id: PD-20260611-bd-retirement-kill-list
+topic: migration.beads-retirement
+status: accepted
+decision_date: 2026-06-11
+last_reviewed: 2026-06-11
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d20--tracked-bd-call-site-kill-list
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/plan-evaluation.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Maintain the inventory of `bd` call sites (~125 across 40+ files) as a checked-off migration artifact with a defined hot-path order (sync → worktree dolt lifecycle → setup → status/preflight → team scripts → instruction surfaces). Beads retirement claims must reference the completed list.
+
+### PD-20260611-orient-recap-file-assembly
+
+```yaml
+id: PD-20260611-orient-recap-file-assembly
+topic: knowledge.orient-recap
+status: accepted
+decision_date: 2026-06-11
+last_reviewed: 2026-06-11
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d21--forge-orientrecap-v1-is-bounded-file-assembly-fts5-is-v2
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** `forge orient` (new) and issue-scoped `forge recap <issue>` (additive mode on the existing activity-recap command) ship first as deterministic bounded file assembly with explicit token budgets; the FTS5 verbatim knowledge index upgrades the same command contract later. The existing no-arg `forge recap` keeps its contract; its Beads JSONL data source migrates to the Kernel projection per the kill list.
+
+### PD-20260611-agent-interface-parity
+
+```yaml
+id: PD-20260611-agent-interface-parity
+topic: agent-interface.parity
+status: accepted
+decision_date: 2026-06-11
+last_reviewed: 2026-06-11
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/decisions.md#d22--forge-agent-interface-parity-layer-the-beads-plugin-equivalent
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/agent-interface-layer.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Forge ships a first-class agent interface layer for its own Kernel — session-priming hook (`forge prime`), kernel-facing JSON-first command set, skills as thin CLI wrappers, harness plugin packaging. Agent-interface parity is a named gate in Beads retirement criteria.
+
+### PD-20260611-supported-harness-set
+
+```yaml
+id: PD-20260611-supported-harness-set
+topic: agent-interface.harnesses
+status: accepted
+decision_date: 2026-06-11
+last_reviewed: 2026-06-11
+adr: pending
+evidence:
+  - docs/work/2026-06-06-kernel-backlog-memory-roadmap/agent-interface-layer.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** The supported harness set is Claude Code, Codex, and Cursor; Hermes is the planned addition. Support for other harnesses (Cline, Copilot/GitHub prompts, Kilocode, OpenCode, Roo) is removed — generated command directories, plugin catalogs, detection, and config generation are pruned, and the supported list becomes explicit configuration rather than a hardcoded directory walk.
+
+**Implications:**
+
+- Onboarding a new harness must require only an adapter (hook wiring + instruction block), zero Kernel changes.
+- Earlier multi-harness support (including the prior partial removal of Antigravity/Windsurf/Aider/Continue) is fully unwound rather than left half-wired.
+
+### PD-20260619-skills-canonical-surface
+
+```yaml
+id: PD-20260619-skills-canonical-surface
+topic: agent-interface.canonical-source
+status: accepted
+decision_date: 2026-06-19
+adr: pending
+evidence:
+  - docs/work/2026-06-19-kernel-completion-plan/kernel-skill-surface-design.md
+supersedes: []
+refines: [PD-20260611-agent-interface-parity]
+conflicts_with: []
+```
+
+**Current decision:** The agent surface's canonical source is the neutral `.skills/` registry, synced by the `@forge/skills` CLI to `.claude/.codex/.cursor/.hermes`. No harness is "main." Refines `PD-20260611-agent-interface-parity`, which originally implied a `.claude/`-canonical command surface.
+
+### PD-20260619-no-command-surface
+
+```yaml
+id: PD-20260619-no-command-surface
+topic: agent-interface.no-commands
+status: accepted
+decision_date: 2026-06-19
+adr: pending
+evidence:
+  - docs/work/2026-06-19-kernel-completion-plan/kernel-skill-surface-design.md
+supersedes: []
+conflicts_with: [forge-ny6j, forge-besw.9]
+```
+
+**Current decision:** Forge uses skills + agents only — **no command files**. The 7 stage commands migrate to skills; `.claude/commands/`, generated command outputs, and `scripts/sync-commands.js` are deleted. Open issues `forge-ny6j` (neutral command source) and `forge-besw.9` (sync-commands v2) contradict this and must be closed/rewritten.
+
+### PD-20260619-agent-sync-all-harnesses
+
+```yaml
+id: PD-20260619-agent-sync-all-harnesses
+topic: agent-interface.agent-sync
+status: accepted
+decision_date: 2026-06-19
+adr: pending
+evidence:
+  - docs/work/2026-06-19-kernel-completion-plan/kernel-skill-surface-design.md
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Extend the `@forge/skills` CLI to sync agent files (not just skills) from a neutral source to every present harness dir (`.claude/.codex/.cursor/.hermes`); Codex/Cursor with no agents concept are a logged no-op, not Claude-only by default.
+
+### PD-20260619-harness-neutral-hooks
+
+```yaml
+id: PD-20260619-harness-neutral-hooks
+topic: hooks.surface
+status: accepted
+decision_date: 2026-06-19
+adr: pending
+evidence:
+  - docs/work/2026-06-19-kernel-completion-plan/kernel-skill-surface-design.md#9
+refines: [PD-20260608-hook-backed-architecture-capture]
+conflicts_with: []
+```
+
+**Current decision:** Kernel hooks (SessionStart→`forge prime`, PreCompact→`forge recap`, Stop→`forge export`+sync reminder, PreToolUse guards) have a neutral source (`.skills/hooks.json`) synced per-harness by `skills sync-hooks` (format-aware writers). Git-lifecycle hooks install worktree-proof via `core.hooksPath` at the git-common-dir level (the Hermes/Codex/Cursor enforcement path). Hooks record evidence/proposals only — never silently mutate authority (observer rule).
+
+### PD-20260619-unique-feature-surface
+
+```yaml
+id: PD-20260619-unique-feature-surface
+topic: agent-interface.unique-features
+status: accepted
+decision_date: 2026-06-19
+adr: pending
+evidence:
+  - docs/work/2026-06-19-kernel-completion-plan/kernel-skill-surface-design.md#10
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Forge-unique capabilities (claim leases, JSONL portability, readiness, planning buckets, etc.) are surfaced via a 3-way split: **surface-now** (live CLI → thin skills), **must-build** (`remember`/`recall`/`buckets`), and **internal — do NOT surface** (quarantine/evaluators/taxonomy-validation/broker/command-contract). Avoids exposing plumbing that would invite agents to hand-generate revisions/idempotency keys.
+
+### PD-20260620-kernel-storage-model-a
+
+```yaml
+id: PD-20260620-kernel-storage-model-a
+topic: authority.local.storage.home
+status: accepted
+decision_date: 2026-06-20
+adr: pending
+evidence:
+  - docs/work/2026-06-20-kernel-agent-parity/design.md#1-storage--model-a-per-user-home--track-c-later
+extends:
+  - PD-20260606-sqlite-local-authority
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** The live kernel DB lives in a per-user home `~/.forge/projects/<uuid>/kernel.sqlite` with a central `~/.forge/registry.json`, a committed `<repo>/.forge/project.json` UUID marker for stable identity, and an opt-in committable JSONL projection (`issues.jsonl`) as the share-or-not knob. Chosen over in-repo `.forge/` (B) and today's `.git/forge/` (C) because only a central home makes a multi-project frontend natural. This is **track C** (own design + implementation later).
+
+**Implications:**
+
+- Live binary DB is never pushed; sharing is via the JSONL projection only.
+- Config splits: shared/team config committed in-repo; personal config + live data central.
+- Fresh clone registers on first `forge` run from the committed UUID marker, optionally seeding from `issues.jsonl`.
+- Enables a `forge serve` daemon + localhost web/desktop frontend over the same broker.
+
+### PD-20260620-cli-agent-first-rendering
+
+```yaml
+id: PD-20260620-cli-agent-first-rendering
+topic: cli.rendering
+status: accepted
+decision_date: 2026-06-20
+adr: pending
+evidence:
+  - docs/work/2026-06-20-kernel-agent-parity/design.md#2-cli-rendering--agent-first
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** The issue CLI is rendered **agent-first**, not human-first. Skip pretty human tables (agents read JSON + summarize; the future frontend covers direct visual use). Invest instead in making the CLI more agent-friendly — preserve the full contract envelope (`schema_version` + `next_commands`) through the CLI boundary, always-on.
+
+**Implications:**
+
+- No effort spent on CLI table/color formatting.
+- `normalizeIssueResult` must stop flattening the kernel envelope (KAP-1).
+- The frontend (track C) is the human-render layer.
+
+### PD-20260620-kernel-agent-parity-backlog
+
+```yaml
+id: PD-20260620-kernel-agent-parity-backlog
+topic: parity.kernel-beads
+status: accepted
+decision_date: 2026-06-20
+adr: pending
+evidence:
+  - docs/work/2026-06-20-kernel-agent-parity/design.md#3-dont-clone-beads-wholesale--kernel-agent-parity-kap-backlog
+extends:
+  - PD-20260611-agent-interface-parity
+supersedes: []
+conflicts_with: []
+```
+
+**Current decision:** Close agent-facing gaps vs Beads selectively (epic KAP-0, 12 tasks, 3 waves) rather than cloning Beads wholesale. Wave 1 = KAP-1,2,6,7,9 (envelope, projection enrichment, list filters, derived queries, batch close). Deferred: defer/supersede/human/doctor/remember/formula. Backlog is filed into the kernel itself (dogfood).
+
+**Implications:**
+
+- Output projection (`rowToIssueSummary`) and `ISSUE_SUMMARY_SCHEMA` gain parent_id/dependencies/labels/priority/created_at — projection additions, not new storage.
+- Wave 1 tasks share files (`sqlite-driver.js`, `issue-command-contract.js`, `_issue.js`) → implement sequentially, KAP-2 first.
+- Beads `dolt push/pull/sync` is not a parity gap — it is the JSONL-projection model (PD-20260620-kernel-storage-model-a).
+
+## Registry update rules
+
+### When to update this file
+
+Update this file when a decision:
+
+- affects multiple components,
+- changes authority/storage boundaries,
+- changes public CLI/MCP/API behavior,
+- changes backlog/workflow ontology,
+- changes agent/session/observer behavior,
+- supersedes a previous accepted project direction,
+- future agents or team members will need before starting work.
+
+### When to keep decision only in a work folder
+
+Keep it local to `docs/work/<date>-<slug>/decisions.md` when it is:
+
+- scoped to one implementation task,
+- temporary spike/evaluator output,
+- a low-risk local ambiguity resolution,
+- evidence for a larger decision but not itself global direction.
+
+### When to create an ADR
+
+Create an ADR under `docs/adr/` when a decision is cross-cutting, hard to reverse, or expected to govern future code/reviews. ADRs should be immutable after acceptance; supersede with a new ADR instead of rewriting history.
+
+## Conflict and supersession rules
+
+- New material decision: create a new `PD-*` entry.
+- Replacing old direction: mark old entry `superseded` and point to the new entry.
+- Conflict discovered: create a conflict/proposal record in Kernel/KnowledgeStore later; until then, record the conflict in the relevant work folder and link it here if accepted.
+- Two active accepted decisions with the same `topic` should fail future decision-registry validation.
+
+## Future Forge commands
+
+This registry should eventually be indexed by KnowledgeStore and surfaced by:
+
+```bash
+forge architecture check
+forge architecture impact
+forge design show
+forge design decisions
+forge design check
+forge knowledge search <query>
+forge orient --json
+forge recap <issue> --json
+```
+
+Agents should be taught:
+
+1. read `docs/PROJECT_DESIGN.md` first for current architecture;
+2. follow ADR/work-folder links for rationale;
+3. update or supersede decisions when changing architecture;
+4. never treat derived summaries as accepted truth without a registry/Kernel decision event.