---
title: "Decisions"
description: "Decisions of medium significance or higher made by automated KXM work in this repository. One entry per decision: the options evaluated with their weights, and why the selected option won. Recorded the turn the decision is taken."
audience: "agents and maintainers"
updated: "2026-10-02"
---

# Decisions

Automated work records here every decision of medium significance or
higher: the options it evaluated, the weight each option scored against
the criteria that mattered, and why the selected option won. Weights are
the session's own 0-to-1 scores, not measurements. A decision that was
made directly by the operator is recorded only when executing it required
a choice.

Entries run oldest first. Retention: this file keeps the last 50 entries. When one more would exceed
the cap, the oldest entries rotate to
`docs/contributing/decisions-archive.jsonl` as `kxm.decision-archive.v1`
lines (date, title, area, options with weights, selected, why, evidence),
oldest first. The archive is append-only cold storage; the md stays the
working set.

## 2026-09-26 — P2 critic transport while the engine was schema-blocked (dispatch)

- Context: installed 0.7.130 refused the P2 lane's new agent schemas, so
  `kxm run`, drive, cancel, and receipt all answered 400. Both critics
  still had to review the unit, and loop-dispatch wanted engine attempts.
- Options:
  - Wait until #343 ships, then run critics through the engine — weight
    0.2. Highest purity, but it stalls the unit for a release cycle and
    the reviewers' context goes cold.
  - Run a second runtime supervisor from the branch code — weight 0.1. It
    would load the lane, but it mutates machine-global runtime state with
    unreleased code and risks the exact registry corruption S24 just
    fixed.
  - Dispatch both critics through the harness runner with briefs copied
    into the lane sandbox — weight 0.9. The documented relief for schema
    cutover lanes, proven twice the same morning by the writer repairs;
    costs only the improve-report attempt rows.
- Selected: harness runner. Fastest safe path; the engine-attempt proof
  was deliberately deferred to the next unit rather than falsified.
Evidence: Evidence: the P2 lane store (bae17379) held the settled attempts while the control-root report read zero, and the 0.7.131 update plus runtime restart left the lane loadable with a verified simulated receipt.

## 2026-09-26 — Supervisor cadence interpretation (operations)

- Context: the operator ordered the schedule task changed to 30 minutes.
  The improvement loop was anchored to wall-clock ("every sixth tick,
  about 30 minutes"), which a longer tick would silently stretch to three
  hours.
- Options:
  - Keep "every sixth tick" literally — weight 0.3. Preserves the prompt's
    letter, breaks the documented ~30-minute wall-clock cadence the
    parenthetical pins.
  - Improvement loop every tick — weight 0.8. Preserves both documented
    wall-clock behaviours; the tick count stops appearing anywhere.
- Selected: every tick. The operator's order named the tick cadence; the
  improvement loop's anchor was always the half hour. Stated in the report
  so it can be flipped back with one word.
Evidence: Evidence: plans/kxm-roadmap/supervisor-prompt.md and the operator order of 2026-09-26.

## 2026-09-27 — Authoring witness misses committed work (engine)

- Context: the engine failed two writer runs (P2 morning, vision port)
  with `authoringWitness: unchanged` while both lanes held the writer's
  commit. `captureWorktreeWitness` fingerprints porcelain, unstaged, and
  staged diffs but not HEAD, so a writer that fully commits reads as
  unchanged and a `passed` write step is flipped to `failed`.
- Options:
  - Add `git rev-parse HEAD` to the fingerprint — weight 0.9. One term in
    one string; catches commits, resets, and branch switches, which are
    all authoring-relevant moves of a lone-writer checkout.
  - A separate commit-witness field with its own failure class — weight
    0.6. Finer attribution (commit versus dirty edit) but a larger
    surface for a distinction nothing consumes today.
  - Trust the producer's `authored` metadata — weight 0.1. The module
    documents that metadata is set here, not trusted from the producer.
- Selected: HEAD in the fingerprint, one named test (committed-only
  change keeps `passed` with `authored: true`), shipped before any more
  engine-driven write steps.
Evidence: Evidence: test/core/worktree-witness.test.ts (real temp git repositories), and the two failed lane runs run_fe3061b3 (vision) and run_f7a21c84 (P2) whose lanes held the writer commits.

## 2026-09-27 — Open PR queue: draft handling and landing order (landing)

- Context: six open PRs after #343. Two were drafts, one conflicted
  against the restructured CLI, three were clean and non-draft. The
  standing rule says every PR is landed without asking.
- Options:
  - Land everything including drafts — weight 0.2. A draft is the
    author's own hold signal; overriding it defeats the state and risks
    landing half-work.
  - Land only clean non-drafts now, defer the conflicted one to a port,
    leave drafts — weight 0.9. Honours both the autonomy rule and the
    draft semantics; the queue drains in one session.
  - Ask the operator per PR — weight 0.1. The standing rule explicitly
    removes this ask for open PRs.
- Selected: land non-drafts oldest-first (#341, #344, #346), leave
  #325 and #342 as drafts, dispatch #345 as a port.
Evidence: Evidence: gh pr list on 2026-09-27 (six open: two drafts, one conflicting, three clean).

## 2026-09-27 — Outcome parser rejects real model output (engine)

- Context: the one-shot producer appends a "return a final JSON object
  with an outcome field" contract to every prompt, and `determineOutcome`
  requires the model's entire output to parse as that bare JSON. Both real
  writers and critics answer with the brief's own review format instead
  (grok prose, fable markdown), so every substantive engine-driven step
  settles `failed` even when the transport and witness are clean.
- Options:
  - Extract the last balanced JSON object in the text and apply the same
    strict checks (object, string `outcome`, member of allowed outcomes;
    anything else stays `failed`) — weight 0.9. Tolerates the prose
    models actually produce; no path to success without a truthful
    outcome token.
  - Repeat the JSON contract as the first and last line of the prompt —
    weight 0.3. Prompt engineering against measured behaviour; the brief's
    own output section still wins.
  - Per-harness structured output modes — weight 0.5. The durable fix but
    a per-adapter surface change; too broad for the ship cycle this needs
    to ride.
- Selected: last-JSON-object extraction, same strict checks, same
  fail-closed default. Shipped with the witness fix in one release so the
  engine can drive real steps at all.
- Addendum (2026-09-27, after two more real failures): the shipped rule
  required the object alone on the final line; real critics write the
  object inline after their summary prose and fail anyway. The rule is
  now "the last top-level object of the reply, extending to the end of
  the trimmed text": forward scan, depth- and string-aware, so trailing
  prose, mid-text objects, and inner objects of a truncated outer object
  all still fail, while the real inline-at-end shape passes.
Evidence: Evidence: test/core/oneshot-producer.test.ts (real reviewer shapes), runs run_79bd2d13 and run_041dfb8e on the vision lane, and the shipped forward pass in #368.

## 2026-09-27 — PR #345: rebase, close, or port (dispatch)

- Context: #345 adds `kxm vision assert`, but its base predates the CLI
  restructure that deleted `plugins/kxm/src/cli/vnext.ts`; GitHub reports
  DIRTY/CONFLICTING. The gate module `vision-gate.ts` already exists on
  main; only the command surface is missing.
- Options:
  - Force the rebase and hand-resolve inside the land pipeline — weight
    0.3. The land rebase stage resolves only three union classes; a
    deleted-file port is none of them, so it fails mid-pipeline anyway.
  - Close #345 as superseded — weight 0.2. Discards reviewed intent
    (skill gate-step wording, fail-closed exit contract) that is still
    wanted.
  - Port the four pieces (handler, registration, test, skill wording)
    onto the current CLI structure through a writer lane — weight 0.9.
    Small surface, the PR stays open until the port lands, and the
    dispatch is the first engine-driven unit on 0.7.131, feeding
    loop-dispatch.
- Selected: port through the engine lane `vision-assert-port`; the PR is
  closed by its replacement landing, not by hand.
Evidence: Evidence: merge-base 77beda4 predates the CLI restructure; merge-tree showed cli/vnext.ts deleted on main; vision-gate.ts already on main.

## 2026-10-02 — Porting the stale update-default branch onto main (landing)

- Context: `feat/update-npm-default-and-all` was based on 2026-09-24 main
  and still uncommitted. `origin/main` had moved about 66 commits and
  already contained the claude-bridge `apiKey` registration fix and the
  `gh`/`curl` release downloader. `kxm land`'s rebase stage only resolves
  union conflicts, which cannot merge the `planKxmPackageUpdate` signature
  clash (`downloader` vs `localRoot`).
- Options:
  - Rebase the 2026-09-24 branch through `kxm land`'s rebase stage — weight
    0.2. Its union-only resolver cannot handle the `planKxmPackageUpdate`
    signature clash.
  - Stash-apply onto a fresh lane, take upstream for claude-bridge, `dist`,
    and `package.json`, and merge the rest — weight 0.9. Keeps the reviewed
    update-default work and the upstream fixes that must not be duplicated.
  - Discard and re-dispatch to the writer — weight 0.3. Re-authors reviewed
    work that already had a specified merge.
- Selected: stash-apply onto a fresh lane off `origin/main`, take upstream
  for claude-bridge, `dist`, and `package.json`, and merge the rest.
Evidence: Evidence: `git diff HEAD origin/main` on the stale branch showed upstream's claude-bridge fix and curl downloader already landed; the lane port keeps both those and the npm/`--all` behavior.