- Core Deadbolt CLI, guardrail validation, typed records, and witness-trace outputs for golden-path demos. The current GitHub repository slug is
deadbolt; some legacy local identifiers still usecogitator-harness. - Phase 3H codelet scaffold and sandbox profile wiring.
- Phase 4 typed transaction/rollback scaffolding and Hyprland keyword allowlist validation (scaffolded safety logic).
- Phase 5.3 canonical observation witnessing: canonicalized witness manifest commitments, deterministic witness-root recomputation, artifact-graph completeness checks, and recursive forbidden-channel scanning for model-visible observation artifacts.
- Phase 5.4 shared canonicalization boundary:
cog-canonicalcentralizes Phase 5 interim canonical JSON bytes and SHA-256 witness-root hashing for reuse by witness-bearing crates. - Phase 5.5 malformed-bundle and mixed-version verification coverage: the observation verifier now fails closed on malformed witness, evidence, hash-report, and trace artifacts; unsupported witness schema/profile/algorithm/bundle variants; invalid SHA-256 formats; duplicate/inconsistent artifact entries; and partial committed graphs.
- Phase 6D audit remediation: memory/context truncation is character-boundary safe, recall ingest is idempotent for repeated runs, codelet write roots use resolved path containment, and sandbox conformance reports distinguish exercised availability checks from scaffold checks.
- Phase 7A shared evidence substrate:
cog-evidencedefines low-level artifact name, digest, role, bundle-kind, witness-profile, verification issue/report, and evidence error primitives for future bundle convergence. - Phase 7B internal observation adoption:
cog-observationusescog-evidenceartifact-name and digest validation primitives internally while preserving every external Phase 5 bundle file, JSON shape, witness root, and CLI surface. - Phase 7C codelet evidence bundles:
codelet validateandcodelet runnow emit fixture/mock/native-fixture evidence bundles usingcog-evidenceprimitives and the explicitcodelet-interim-jcs-like-v1profile.verify codelet --run <dir>checks internal graph consistency for those scaffold bundles. - Phase 7C.1 codelet verifier graph closure:
verify codelet --run <dir>now binds witness profile/semantics, committed artifact hashes, artifact hash report projection, evidence manifest fields and artifact set, a single deterministic trace event, produced-artifact linkage, andwitness_root.txtinto a closed internal graph. - Phase 7D desktop transaction dry-run evidence bundles: the fake Hyprland theme target writes deterministic transaction request, plan, snapshot, rollback, dry-run report, evidence manifest, artifact hash report, trace, witness manifest, and witness root artifacts using
cog-evidenceprimitives anddesktop-transaction-interim-jcs-like-v1. The current CLI entry point fortransaction dry-run --target hyprland-theme-fakeis lease-required under Phase 9C, while the domain-level bundle writer remains a deterministic test/bench helper.verify transaction --run <dir>checks internal graph consistency and writestransaction_verify_report.jsonas verifier output only. - Phase 7E evidence graph inspection and verifier-bench seed:
graph inspect --kind observation|codelet|transaction --run <dir>emits read-only graph reports using sharedcog-evidencegraph vocabulary, andeval verifier-bench --out <dir>generates a deterministic local clean/tamper corpus checked by existing verifiers. - Phase 8A.1 RFC 8785 candidate gap closure:
cog-canonicalreports known profile capabilities, adds profile-specific canonicalization APIs, keeps interim profiles unchanged, implements UTF-16 property ordering and I-JSON safe-integer validation forcogitator-rfc8785-jcs-v1, and expands exact-byte fixture tests.cogitator-rfc8785-jcs-v1remains a candidate profile, not conformant. - Phase 8Q systems-engineering audit: architecture, onboarding, command, risk, ADR, and acceptance documentation now records the current evidence/canonicalization truth after the rapid Phase 7/8 sequence without adding capabilities or changing witness roots.
- Phase 8R explicit profile migration plan:
cog-evidencedefines profile migration plan/report vocabulary with schema markerphase8r-profile-migration-plan-v1, andcanonical migration-planprints a read-only diagnostic plan for moving current interim profiles towardcogitator-rfc8785-jcs-v1later. It does not migrate bundles or change roots. - Phase 8R.1 bundle profile compatibility inspector:
cog-evidencedefines diagnostic compatibility report vocabulary with schema markerphase8r1-profile-compatibility-report-v1, andcanonical compare-profile --kind observation|codelet|transaction --run <dir> --target-profile <profile> [--out <path>]runs the current verifier before computing hypothetical target roots. It does not migrate bundles, update witness manifests, updatewitness_root.txt, or change verifier acceptance semantics. - Phase 8S local DSSE/in-toto attestation export:
cog-attestationdefines in-toto witness predicates, DSSE envelopes, deterministic payload bytes, local Ed25519 signing/verification helpers, and dev/test key fixtures.attest dsse signruns the current verifier first and refuses failed bundles;attest dsse verifychecks the envelope and can cross-check a local bundle. DSSE envelopes are export artifacts, not witness evidence. - Phase 8S.1 DSSE attestation boundary closure: DSSE verification reports now use schema marker
phase8s1-dsse-verification-report-v1and explicitly report predicate validity, trusted-key policy application, and transparency receipt verification. Verifier-bench now covers clean DSSE exports plus payload/signature/key/envelope/predicate/local-bundle mismatch boundaries. - Phase 8G verifier pass catalog:
cog-evidencedefines the diagnosticphase8g-verifier-pass-summary-v1vocabulary.verify passes --kind observation|codelet|transaction --run <dir>and the DSSE pass projection run existing verifiers and map their reports into named pass categories without changing verifier acceptance semantics. Graph inspection includes an additive pass summary, and verifier-bench records failed pass categories while keeping existing verifiers authoritative. - Phase 9A signed capability leases:
cog-leasesdefines local signed capability lease, request, and decision-report schemas.lease issue,lease verify, andlease checkcreate and verify deterministic local control-plane constraints only; they do not execute operations, add live authority, change witnesses, or provide production trust. - Phase 9A.1 lease authorizer remediation:
lease checkrefuses empty requested capability lists and enforces grant-level read/write path roots in addition to global lease path ceilings. This is fail-closed authorization hardening only; it does not gate existing commands or add live authority. - Phase 9B opt-in lease-gated dry-run command integration:
transaction dry-run,codelet validate, andcodelet run --backend native-fixtureaccept local lease preflight flags. When supplied, the command checks a signed lease at an explicit evaluation time and refuses before writing the output bundle if authorization fails. Existing ungated command syntax remained available in Phase 9B; Phase 9C narrows that for the fake-target transaction dry-run only. - Phase 9B.1 lease-gated command remediation: leased
codelet runfails closed for any backend other thannative-fixture, and gated commands reject--lease-decision-outpaths inside the command--outdirectory before creating command output or lease decision parent directories. Lease decision reports remain diagnostic/control-plane material, not witness evidence. - Phase 9B.2 lease decision path remediation: gated commands normalize command
--outand--lease-decision-outpaths to absolute lexical paths before comparing containment, so relative/absolute aliases under command output fail closed before any output or decision-report parent directory is created. This remains CLI control-plane hardening only. - Phase 9C lease-required dry-run policy pilot:
transaction dry-run --target hyprland-theme-fakenow requires a signed capability lease at the CLI boundary and refuses missing or failed leases before writing output. Codelet lease gates remain opt-in. This is still dry-run-only and adds no live authority. - Phase 9D lease-required local DSSE export policy:
attest dsse signnow requires a signed capability lease forattestation.dsse.local_exportat the CLI boundary and refuses missing, malformed, or failed leases before writing DSSE envelope output.attest dsse verifyremains ungated/read-only. Existing source-bundle verifiers remain authoritative; a valid lease authorizes only the signing attempt. - Phase 9E lease policy/request compiler consolidation:
cog-clinow has one deterministic command lease policy matrix and request compiler for the existing lease-aware command paths. It preserves Phase 9C required fake-target transaction dry-run, Phase 9D required DSSE signing/export, Phase 9B opt-in codelet validation/native-fixture gates, fail-closed leased mock codelet runs, and ungated DSSE verification. It does not move authorization out ofcog-leasesand does not add authority. - Phase 9E.1 codelet fixture hash portability remediation: the
count_json_rowscodelet fixture is LF-normalized via a narrow.gitattributesrule and its source hash now matches checked-in bytes across platforms. This changed fixture portability only, not verifier or lease semantics. - Phase 10A read-only live-adapter lease design:
cog-leasesnow names future live-read capabilities for screenshots, AT-SPI, and Hyprland state and includes deterministic request/refusal fixtures. They remain refused under current no-live-authority constraints and no live adapter or command was implemented. - Phase 10C read-only Hyprland-state adapter preflight: the future real Hyprland-state target is modeled as
hyprland-state-live-session, distinct from the Phase 10B fixture target. The request remains refused by default, fake-live leases do not authorize it, and docs define the fixed-argv allowlist, forbidden mutation commands, consent/config gate, timeout/bounded-output requirement, and minimization/redaction expectations. Nohyprctl, Hyprland socket, compositor IPC, screenshot, AT-SPI, portal, keyboard/mouse, app launch, network, shell/model, MCP/AG-UI, or sandbox path was added. - Phase 10D real Hyprland monitors live-read, with Phase 10H.1 minimization:
desktop live-read --kind hyprland-monitorscan call exactlyhyprctl -j monitorsonly after explicit local consent/config and a valid signedlive-hyprland-monitors-readlease. The command uses fixed argv, timeout, bounded output, minimizes raw monitor output before writing, and writes minimizedhyprland_monitors.jsonpluslive_read_report.json; rawhyprctloutput is not written.verify live-read --run <dir>checks report flags, fixed argv, output hash, privacy scope, minimization policy, raw-output flags, and the minimized monitor geometry/state schema. Title/window/client/app/process identifiers, workspace objects, nested unknown fields, and unknown fields are not valid written output and are rejected byverify live-readif present inhyprland_monitors.json. It does not read clients, activewindow, workspaces as a command surface, titles, app classes, screenshots, AT-SPI, portals, process info, keyboard/mouse, app launch, network, shell/model, MCP/AG-UI, sandbox, or mutation paths. - Phase 10E real Hyprland workspaces live-read, with Phase 10E.1 minimization:
desktop live-read --kind hyprland-workspacescan call exactlyhyprctl -j workspacesonly after explicit local consent/config and a valid signedlive-hyprland-workspaces-readlease. The command uses fixed argv, timeout, bounded output, minimizes raw workspace output before writing, and writes minimizedhyprland_workspaces.jsonpluslive_read_report.json; rawhyprctloutput is not written.verify live-read --run <dir>checks report flags, fixed argv, output hash, privacy scope, monitor/workspace labeling, minimization policy, raw-output flags, and the minimized workspace schema. Because the fixed raw response may include fields such aslastwindoworlastwindowtitle, Phase 10E receives that fixed output only to drop forbidden/raw-sensitive fields before hashing or writing; title/window fields are not valid written output and are rejected byverify live-readif present inhyprland_workspaces.json. It does not call clients or activewindow command surfaces, screenshots, AT-SPI, portals, process info, keyboard/mouse, app launch, network, shell/model, MCP/AG-UI, sandbox, arbitrary hyprctl args, or mutation paths. Workspace names are treated as potentially sensitive diagnostic metadata. - Phase 10F real Hyprland activeworkspace live-read:
desktop live-read --kind hyprland-activeworkspacecan call exactlyhyprctl -j activeworkspaceonly after explicit local consent/config and a valid signedlive-hyprland-activeworkspace-readlease. The command uses fixed argv, timeout, bounded output, minimizes raw activeworkspace output before writing, and writes minimizedhyprland_activeworkspace.jsonpluslive_read_report.json; rawhyprctloutput is not written.verify live-read --run <dir>checks report flags, fixed argv, output hash, privacy scope, minimization policy, raw-output flags, and the minimized activeworkspace schema. Because the fixed raw response may include fields such aslastwindoworlastwindowtitle, Phase 10F receives that fixed output only to drop forbidden/raw-sensitive fields before hashing or writing; title/window fields are not valid written output and are rejected byverify live-readif present inhyprland_activeworkspace.json. It does not call clients or activewindow command surfaces, screenshots, AT-SPI, portals, process info, keyboard/mouse, app launch, network, shell/model, MCP/AG-UI, sandbox, arbitrary hyprctl args, or mutation paths. Workspace names are treated as potentially sensitive diagnostic metadata. - Phase 10G/10G.1/10G.2/10G.3 typed CLI parity hardening: priority authority-bearing command families pass through a typed
clapparser before legacy handler dispatch while remaining CLI families migrate incrementally. Phase 10G.2 enforcesverify passesconditional required arguments, requires explicitobserve fixture --out <dir>, and routes unknown nested priority subcommands to typed parser failures instead of generic help fallback. Phase 10G.3 constrains intentional legacy priority-route bypasses to documented exact shapes so malformed trailing tokens fail before hand-routed handlers run. - Phase 10H live-read negative fixture catalog and verifier regression hardening:
fixtures/live_read_negative/enumerates deterministic negativeverify live-readcases for the three existing live-read surfaces only. Tests materialize valid local runs, tamper reports or written artifacts, and exerciseverify live-readso report flags, output hashes, output-file/kind swaps, monitor artifact schema checks, workspace minimization, activeworkspace minimization, lease target isolation, and refusal-before-output behavior fail closed. This adds no live-read surface, no new Hyprland command, no reviewer authority, and no witness-root/profile/canonicalization changes. - Phase 10H.1 monitor live-read output schema hardening: monitor live-read now follows the same refusal-before-exposure pattern as the other live-read surfaces by writing only allowlisted monitor geometry/state fields and independently verifying that
hyprland_monitors.jsoncontains no forbidden title/client/window/process/workspace-like fields, nested unknown objects, arrays outside allowlisted mode lists, unknown fields, or invalid field types. This is a remediation only; it adds no live-read surface, no new Hyprland command, no reviewer authority, and no witness-root/profile/canonicalization changes. - Phase 10J raw JSON ingress audit and hardening: security-relevant verifier, evidence, authority, diagnostic, IPC, kernel, DSSE, lease, trace, and strict proposal parsing paths reject duplicate-key ambiguity at raw JSON ingress where the boundary can see raw bytes/text.
- Phase 10K/10K.1 release readiness and claim-boundary tightening: release docs now state that verifiers check internal artifact consistency and reported boundary flags, not independent proof that consent, lease preflight, host preflight, fixed argv execution, or other real-world control-plane steps occurred.
- Phase 11A planner provider boundary design:
docs/phases/phase11a-planner-provider-boundary.mddocuments a future planner/model-provider seam. It is design-only and adds no live provider calls, network authority, model-provider runtime authority, tool execution, desktop mutation, lease semantic changes, verifier-status changes, DSSE trust changes, or witness-root changes. - Phase 11B fixture-only provider envelope ingestion:
cog-modelparses checked-in OpenAI-compatible Chat Completions subset response fixtures with duplicate-key rejection, normalizes exactly one candidate/refusal, andpropose provider-fixturecompiles candidate text through strict proposal parsing while writing diagnostic/control-plane reports only. Phase 11B.1 hardens this path with a strict four-flag CLI allowlist, fixture size checks before full read/allocation, and fail-closed finish-reason allowlisting. It adds no live provider runtime, HTTP client, network authority, credentials, provider-side tools, execution, evidence, verifier-status changes, leases, DSSE trust, or witness-root changes. - Phase 11C resolved-loopback provider smoke path:
propose provider-loopback-smokeperforms one OpenAI-compatible Chat Completions subset POST only to an endpoint that validates and resolves wholly to loopback. The command is credential-free, proxy-refusing, redirect-refusing, non-streaming,n = 1, and provider-side-tool-free. Phase 11C.1/11C.2 hardens the path so known/common provider credential env vars fail before endpoint resolution/network/output, concrete report artifact paths are preflighted before the loopback POST, and reused output directories drop stale regularaction_proposal.jsonor refuse stale symlinked/non-regular proposal paths before refusal, HTTP rejection, envelope rejection, or proposal parse failure can leave a current action proposal. Phase 11C.2 closes concrete report-path and symlink preflight gaps and has a clean hostile review result: "No P0/P1/P2 findings. Phase 11C.2 closes the concrete provider-loopback output preflight gaps." It bounds request/response bodies, reuses the Phase 11B provider envelope parser, compiles candidate text throughparse_action_proposal_strict, and writes diagnostic/control-plane reports only. It adds no cloud/remote provider support, credentials, proxy influence, redirects, provider-side tools, execution, mutation, evidence, verifier-status changes, leases, DSSE trust, witness material, or witness-root changes. - Phase 12A mutation boundary design:
docs/phases/phase12a-mutation-boundary.mddefines future mutation as a distinct authority class with refusal-before-side-effect, dry-run-first, fake-target-first, typed macro-actions, mutation-specific leases, optional human approval hooks, execution receipt doctrine, rollback doctrine, stale-artifact refusal, and failure rules. It is design-only and adds no mutation code, CLI mutation command, real desktop mutation, provider expansion, live authority, evidence semantic change, witness change, verifier semantic change, lease semantic change, DSSE semantic change, or Phase 5 behavior change. - Phase 12B fake reversible mutation pilot:
mutate fake-workspace-tagimplements exactly one fake file-backed macro-action,fake.workspace_tag.set, under the explicit run directory. Dry-run writes request/compile/dry-run/rollback-plan artifacts without changingfake_target_state.json. Commit requires the matching dry-run plan and a signedmutation.fake.workspace_tag.setlease bound to the exact action/workspace/run/dry-run-plan target and shared logical run directory before writing onlyfake_target_state.jsonplus fake execution receipt artifacts. Rollback requires the commit receipt and rollback plan, restores only the fake state file, and writes a distinct rollback receipt.verify mutation-fake --run <dir>checks internal fake-chain consistency only. Phase 12B adds no real desktop mutation, Hyprland mutation, arbitraryhyprctl, shell, keyboard/mouse, browser, screenshot, AT-SPI, portal, app launch, network, provider expansion, witness change, evidence semantic change, DSSE semantic change, or production trust claim. - Phase 12C fake mutation hardening: the Phase 12B fake-only control plane now uses one shared logical run binding for dry-run, commit, rollback, verify, and mutation lease issue/request binding. The dry-run plan is bound to that run binding; stale authority-adjacent artifacts refuse before reuse; mutation commit leases require exact fake capability/action/workspace/run/dry-run-plan/run-binding semantics with no wildcard or broad grants; run/artifact containment rejects symlink ancestors and Windows reparse-point ancestors where filesystem metadata exposes them; and
verify mutation-fakechecks schema, action, target, run, run binding, policy, lease, execution, rollback, request-hash, and status semantics rather than hashes alone. Phase 12C adds no real desktop mutation, Hyprland mutation, NixOS mutation, generichyprctl, shell/network/provider/MCP/AG-UI authority, witness/evidence/DSSE semantic changes, or production trust claim. - Phase 13A userspace kernel protocol seed:
cog-kernelnow defines strict typed protocol records and pure verifier/check functions for observation epochs, action bindings, adapter manifests, effect classifications, authority budgets, foreground invariants, raw trajectory boundaries, MCP boundary vocabulary, approval boundary vocabulary, and diagnostic protocol verifier reports. Clean and hostile fixtures live underfixtures/kernel/phase13a/. Phase 13A adds no real mutation, no generic computer-use driver, no screenshot/accessibility/Set-of-Mark capture, no keyboard/mouse/browser/portal/app-launch/window-control/process-info authority, no arbitraryhyprctl, no shell/network/provider-tool/MCP/AG-UI runtime, and no witness/evidence/lease/DSSE/provider/Phase 5 semantic changes. - Phase 13A.1 kernel protocol verifier boundary hardening:
cog-kernelnow fails closed when untrusted protocol records claim foreground-change authorization,runnable_future_refusedstatus, future-refused adapter support, unsupported manifest semantics, stale or unrelated budget decisions, or future human approval mode. This is verifier-only remediation and adds no live authority, new adapter, runtime execution, real mutation, computer-use driver, MCP runtime, screenshot/accessibility capture, shell/network/provider expansion, or witness/evidence/lease/DSSE semantic change. - Phase 13B kernel protocol conformance bench:
cog-kernelnow defines strict conformance case/manifest/report records, fixture-relative path confinement, deterministic expected issue-code matching, diagnostic kernel pass-summary projection, and a manifest-driven clean/hostile corpus underfixtures/kernel/phase13b/.eval verifier-benchincludes the additivekernel_protocol_phase13bgroup and writeskernel_protocol_phase13b_conformance_report.json; a deterministic golden snapshot lives atgoldens/phase13b_kernel_conformance_report.json. This reads fixtures and writes diagnostic reports only. It adds no runtime executor, adapter runner, live-read surface, real mutation, generic computer-use driver, MCP runtime, screenshot/accessibility/Set-of-Mark capture, shell/network/provider authority, or witness/evidence/lease/DSSE semantic change. - Phase 13C noop/replay kernel decision runner:
cog-kernelnow defines strict decision bundle/report records and a pure decision evaluator for local protocol bundles. `kernel decide --mode noop|replay --bundle --out ` writes only `kernel_decision_report.json`. AcceptedNoop and AcceptedReplay are non-actuating internal decision states only. The runner verifies loaded artifacts independently, refuses missing paired artifacts without hiding loaded invalid artifacts, uses canonical JSON semantic hashes, and rejects platform-dependent path escapes. It adds no adapter runner, live authority, fake or real mutation, generic computer-use driver, MCP runtime, provider/network/shell authority, or witness/evidence/lease/DSSE semantic change. - Phase 13D synthetic/fake-world adapter runner:
cog-kernelnow defines strict synthetic world state/action/run/report/receipt/transcript records, a static fake adapter manifest, deterministicSyntheticWorldSetCelltransition semantics, and a diagnostic verifier.kernel synthetic simulate --bundle <dir> --out <dir>reads local synthetic bundles and writes synthetic reports, receipts, transcripts, after-state, and rollback-plan artifacts under--out; refused runs write only refused diagnostics.verify synthetic-adapter --run <dir>checks that diagnostic output graph. The runner never calls a live adapter, never mutates input bundles orfake_target_state.json, never mutates real state, and adds no Hyprland, NixOS, shell, network, provider, MCP/AG-UI, screenshot, AT-SPI, Set-of-Mark, keyboard/mouse, browser, portal, app-launch, window-control, process-info, witness/evidence/lease/DSSE, or Phase 5 semantic change. - Phase 13E diagnostic kernel transcript and phantom event profile:
cog-kernelnow defines strict transcript, transcript-entry, verify-report, and drift-report records.kernel transcript build --source decision|synthetic --run <dir> --out <dir>projects existing Phase 13C decision reports or verified Phase 13D synthetic outputs into deterministic diagnostic transcripts.verify kernel-transcript --run <dir>recomputes entry, chain, and transcript hashes, andkernel transcript diffreports deterministic diagnostic drift.PhantomRefusalmakes local refusal explicit without proving real attempted execution. Transcript hashes and drift reports are internal-consistency diagnostics only and add no adapter execution, live authority, host mutation, synthetic state mutation, witness/evidence/lease/ DSSE semantics, or Phase 5 behavior change. - Phase 13F transcript conformance / verifier-bench integration:
cog-kernelnow defines a strict Phase 13F transcript conformance manifest and report runner.fixtures/kernel/phase13fcontains clean and hostile transcript cases for Phase 13E projection, verification, drift, PhantomRefusal material, hash/path/sequence tampering, non-canonical issue-code ordering, and invalid drift inputs.eval verifier-benchwriteskernel_transcript_phase13f_conformance_report.jsonand appendskernel_transcript_phase13f.*diagnostic cases. These reports and pass summaries are diagnostic only and add no adapter execution, live authority, mutation, transcript root, witness/evidence/lease/DSSE semantics, or Phase 5 behavior change. - Phase 14B minimal kernel decision witness profile:
cog-kernelnow defines a separatekernel-decision-witness-v1profile for selected local Phase 13C decision facts only.kernel witness build --run <dir>writeskernel_witness_manifest.jsonandkernel_witness_root.txt;verify kernel-witness --run <dir>recomputes fromkernel_decision_report.jsonand writeskernel_witness_verify_report.json. The profile does not replace Phase 5, does not overwritewitness_root.txt, does not witness transcripts, verifier-bench outputs, conformance reports, DSSE envelopes, leases, synthetic effects, PhantomRefusal, provider-loopback material, or real adapter attempts, and adds no live authority. - Phase 14C kernel witness conformance bench:
cog-kernelnow defines a strict diagnostic conformance runner for the existing Phase 14B witness verifier, with 2 clean and 12 hostile fixtures underfixtures/kernel/phase14c/.eval verifier-benchwriteskernel_witness_phase14c_conformance_report.jsonand appendskernel_witness_phase14c.*diagnostic cases. The runner delegates to the real verifier, does not change witness events or roots, does not change Phase 5 or evidence semantics, and does not make conformance reports, verifier-bench reports, pass summaries, fixture manifests, or stale verify reports authority-bearing. - Phase 15A authority modes design:
docs/phases/phase15a-authority-modes.mddefines the futurelocked,observe,propose,confirm,trusted-local, andfull-controlauthority-mode ladder as design-only material. It adds no config, parser, CLI, runtime gate, provider support, adapter registry, real adapter, real mutation, witness event, evidence semantic, lease semantic, DSSE semantic, verifier-bench, or Phase 5 behavior change. - Phase 15B mode-aware local policy config:
cog-modelnow parses strict local authority policy configs with schemacogitator.authority_policy.v1, exact mode strings, duplicate-key rejection, and unknown-field rejection.authority statusreports the default locked posture or an explicit policy as diagnostic/control-plane material, andpropose provider-localrequires explicit modeproposewithallow_provider_local: truebefore its live provider-local network path can run. This adds no adapters, leases, confirmation prompts, real mutation, shell execution, provider-side tools, cloud/private-LAN support, witness event, evidence semantic, DSSE semantic, verifier-bench semantic, Phase 14, or Phase 5 behavior change. - Phase 15C authority lease diagnostics:
cog-modelparses strict local authority lease records with schemacogitator.authority_lease.v1, exact Phase 15B mode strings, strict target binding, strict shared identifier grammar, duplicate-key rejection, unknown-field rejection, explicit requiredrevoked, explicit evaluation time, and deterministic context matching.authority lease inspectwrites diagnostic reports only. See Phase 15C authority lease binding. Leases are parse/inspect/evaluate records in this phase; they are not signed production authority, do not gate provider-local, do not execute adapters, do not authorize mutation, and do not change witness/evidence/DSSE/verifier-bench/Phase 5 semantics. - Phase 15D authority brake diagnostics:
cog-modelparses strict local authority brake records with schemacogitator.authority_brake.v1, exactinactive,locked, andpanicstate values, positive generation, strict UTC timestamps, duplicate-key rejection, unknown-field rejection, and exact lease-id/nonce revocation diagnostics.authority brake inspectwrites diagnostic reports only. Brake records are parse/inspect/evaluate material in this phase; they are not signed production authority, do not create a mutating lock/unlock/panic CLI, do not gate provider-local or leases, do not execute adapters, do not authorize mutation, and do not change witness/evidence/DSSE/verifier-bench/ Phase 5 semantics. Inactive brake state is not an unlock, and missing brake state is not permission to execute. - Phase 15E authority preflight composer:
cog-modelcomposes a parsed Phase 15B authority policy, Phase 15C authority lease, Phase 15D authority brake state, explicit requested context, and explicit inspection time into a deterministic diagnostic result.authority preflight inspectwritesauthority_preflight_report.jsononly. The composer supports diagnostic matching for future-adapter modesconfirmandtrusted-local, refuses policy/lease/brake/request mismatches, refuses locked or panic brake states, and refuses exact lease-id/nonce brake revocations. Matched preflight does not authorize execution, refused preflight does not prove real adapter blocking, provider-local is not routed through preflight, and reports do not change witness/evidence/DSSE/ verifier-bench/Phase 5 semantics. - Phase 15P-A local provider boundary:
docs/phases/phase15p-a-local-provider-boundary.mddefines future local-first provider and endpoint classes as design-only material. It adds no provider implementation, network implementation, CLI command, mode-aware provider gate, config parser, local provider adapter, cloud provider adapter, credential support, provider-loopback semantic broadening, witness/evidence semantic change, lease semantic change, DSSE semantic change, verifier-bench semantic change, real adapter, real mutation, or Phase 5 behavior change. - Phase 15P-B local provider proposal path:
propose provider-localadds a proposal-only local OpenAI-compatible Chat Completions subset path for local inference servers. It supports loopback and the narrow VM-host literals192.168.122.1and10.0.2.2, rejects arbitrary private LAN, public, DNS, cloud, credentialed, proxied, redirected, streaming, tool, custom-header, and arbitrary-path provider shapes, normalizes provider kind aslocal-openai-compatible, and writes diagnostic reports only. Provider output remains untrusted planner input and cannot execute actions, mutate state, write evidence/witness material, grant leases, sign DSSE, change verifier-bench, change authority modes, change Phase 5, or broadenprovider-loopback-smoke. - Phase 15P-C/15P-D provider-local diagnostics: Phase 15P-C adds a deterministic fixture-backed conformance corpus for the existing provider-local response boundary, and Phase 15P-D pins report and artifact invariants for success, provider refusal, HTTP/transport refusal, envelope refusal, proposal parse refusal, stale proposals, and raw-body non-persistence. These phases are diagnostic-only and add no provider capability, verifier-bench integration, endpoint class, credential/header path, tool path, adapter execution, mutation, witness/evidence/lease/DSSE semantic change, or Phase 5 behavior change.
- Phase 16A adapter registry design:
docs/phases/phase16a-adapter-registry-design.mddocuments a future disabled-by-default adapter registry contract, descriptor shape, future adapter classes, platform sequencing, and authority composition. It is docs-only: no Rust code, schemas, parsers, fixtures, CLI commands, runtime registry, adapter execution, real mutation, provider-local broadening, witness/evidence/DSSE/verifier-bench semantic change, or Phase 5 behavior change is added. - Phase 16B adapter descriptor inspect:
cog-modelparses one strict localcogitator.adapter_descriptor.v1descriptor shape, fixtures cover clean and hostile descriptors, andadapter descriptor inspect --descriptor <json> --out <dir>writes fixedadapter_descriptor_inspect_report.jsondiagnostics only. Descriptor files and reports are diagnostic/control-plane material; they are not runtime registry entries, evidence, witness material, leases, preflight reports, receipts, execution plans, provider-local inputs, DSSE trust, verifier-bench material, or authorization by existence. No runtime registry, registry loading, adapter routing, adapter execution, real mutation, Home Manager/NixOS/Hyprland operation, containment runner, shell, network, provider-side tool, MCP/AG-UI, or Phase 5 semantic change is added. Phase 16B.1 hardens the inspect output path by rejecting symlink or exposed Windows reparse-point components in the output/report path, removing stale fixed reports only under safe output paths, and writing the fixed report with create-new semantics rather than overwriting a preexisting final path. - Phase 16C descriptor-aware preflight diagnostics:
cog-modelcomposes one strict Phase 16B descriptor, one Phase 15B authority policy, one Phase 15C authority lease, one Phase 15D authority brake state, one explicit requested adapter context, and one explicit evaluation time into a diagnostic result.adapter preflight inspectwrites fixedadapter_preflight_report.jsonreports only. Exact descriptor action, target grammar, and mode checks are additive diagnostics; even a matched result isdiagnostic_matched_no_runtime_authority. Descriptor-aware preflight reports are not runtime registry entries, registry loading, adapter routing, adapter execution, provider-local inputs, leases, receipts, evidence, witness material, DSSE trust, mutation authority, or authorization by existence. No Home Manager/NixOS/Hyprland operation, containment runner, shell, network, provider-side tool, MCP/AG-UI, verifier-bench semantic change, or Phase 5 semantic change is added. - Phase 16D diagnostic fake adapter chain:
cog-modelcomposes a static diagnostic fake-call result from explicit source descriptor, policy, lease, brake, requested context, and time inputs, reusing the Phase 16B strict descriptor parser and Phase 16C descriptor-aware preflight composer.adapter fake-call inspectwrites fixedadapter_fake_call_report.jsonreports and, only on matched diagnostic fake-call,adapter_fake_diagnostic_receipt.json. The only accepted fake binding isdiagnostic-fake/diagnostic.fake_echowithdiagnostic-target:<id>. The fake adapter does not touch the host, inspect environment variables, spawn processes, call shell, call network, call Hyprland, call Nix/Home Manager, or mutate state. It adds no runtime registry, registry loading, registry lookup, real adapter execution, provider-local broadening, real receipts, real mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 16E execution containment design:
docs/phases/phase16e-execution-containment-design.mddocuments the future containment contract required before any real local adapter operation can run. It is docs-only and defines separate authority, execution, evidence, and context planes plus future runner requirements for fixed command templates, working-directory containment, explicit read/write roots, minimal environment, default no-network posture, process isolation options, timeouts, bounded output, receipt non-claims, manual confirmation binding, brake rechecks, provider-local separation, context minimization, and platform sequencing. It adds no Rust code, schemas, parsers, fixtures, CLI commands, containment runner, runtime registry, adapter execution, fake adapter expansion, real mutation, Home Manager/NixOS/Hyprland operation, shell/process/network execution, provider-local broadening, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 16F maintainability / architecture audit:
docs/phases/phase16f-maintainability-architecture-audit.mddocuments a docs-only audit of parser strictness, identifier and target grammar, path-safety/stale cleanup, report writing, CLI grammar, fixture organization, docs/status drift, naming, test maintainability, and future architecture seams after the Phase 15/16 authority-stack work. It implements no fixes, refactors, Rust code, schemas, parsers, fixtures, CLI commands, runtime registry, containment runner, adapter execution, real mutation, provider-local broadening, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 16F.1 legacy diagnostic output hardening:
docs/phases/phase16f1-legacy-diagnostic-output-hardening.mdremediates the Phase 16F P1 for older authority and provider-local fixed diagnostic output helpers. Authority reports and provider-local proposal/report artifacts now reject traversal, non-directory ancestors, symlink/reparse components visible throughstd::fs::symlink_metadata, symlinked or non-regular final fixed artifacts, and ambiguous raw--outcleanup recovery. Stale cleanup removes only fixed artifact names, preserves unrelated files, never recursively deletes, and report/proposal writes use create-new fixed paths. This changes no authority, lease, brake, preflight, provider-local endpoint/network, witness/evidence/DSSE/verifier-bench, or Phase 5 semantics and adds no runtime registry, containment runner, adapter execution, or real mutation. - Phase 16G model context renderer / observation budget design:
docs/phases/phase16g-model-context-renderer-design.mddocuments the future context-plane boundary for what local observations may become model-visible context. It is docs-only and defines the evidence/context split, context pack contract, freshness/task-specificity requirements, redaction classes, hostile-text quarantine, observation budget posture, local/cloud model-client distinctions, and no-authority context wording. It adds no Rust code, schemas, parsers, fixtures, CLI commands, context renderer, provider-local context integration, cloud provider support, broker, runtime registry, containment runner, adapter execution, real mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 16H inference provider broker design:
docs/phases/phase16h-inference-provider-broker-design.mddocuments the future local/cloud inference provider broker boundary for named clients and named model/provider backends. It is docs-only and defines future routing, client/model identity, context-pack and observation-budget references, prompt/response hashes, priority, timeout, cancellation, resource budget, local/cloud, redaction-policy, provenance, and no-authority vocabulary. It adds no Rust code, schemas, parsers, fixtures, CLI commands, broker implementation, provider runtime, cloud provider support, credentials, provider-local broadening, context renderer, observation budget implementation, memory system, runtime registry, containment runner, adapter execution, real mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 16I real adapter readiness gate:
docs/phases/phase16i-real-adapter-readiness-gate.mddocuments the mandatory readiness gates that must exist before any future Phase 16 authority-stack real adapter implementation can merge. It is docs-only and covers descriptor identity and authority class, explicit policy, exact lease binding, brake/panic/revocation state, descriptor-aware preflight, context-pack minimization, observation budgets, inference-broker non-authority, containment, manual confirmation, stale-artifact and output safety, receipt shape, rollback/reversibility, witness/verifier non-claims, and hostile review. It adds no Rust code, schemas, parsers, fixtures, CLI commands, runtime gate implementation, runtime registry, registry loading, containment runner, context renderer, observation budget implementation, broker implementation, provider runtime, cloud provider support, provider-local broadening, adapter execution, real mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17A Home Manager adapter design:
docs/phases/phase17a-home-manager-adapter-design.mddocuments Home Manager as a future user-level, declarative, reviewable, generation-oriented target family under Phase 16I. It is docs-only and defines the target boundary, command classification, future descriptor sketch, future target grammar sketch, future policy/lease/brake/preflight requirements, future containment requirements, future context requirements, receipt/rollback/ witness posture, and the stricter Home Manager roadmap after Phase 17A. It adds no Rust code, Cargo manifest changes, schemas, parsers, fixtures, CLI commands, tests, Home Manager descriptor implementation, runtime registry, registry loading, containment runner, context renderer, observation budget, broker implementation, provider runtime, provider-local broadening, Home Manager command execution, Nix command execution, build, switch/apply, rollback, uninstall, generation removal, generation expiry, NixOS rebuild, adapter execution, real mutation, or witness/evidence/DSSE/verifier-bench/ Phase 5 semantic change. - Phase 17B Home Manager diagnostic/fake rehearsal:
docs/phases/phase17b-home-manager-diagnostic-fake-rehearsal.mdadds one Home Manager target-family diagnostic/fake binding to the existingadapter fake-call inspectpath, plus checked-in fake descriptor, policy, lease, and brake fixtures underfixtures/adapter_registry/phase17b/. It is diagnostic/fake only. The fake report and fake diagnostic receipt explicitly state that Home Manager was not invoked, Nix was not invoked, no build, switch/apply, rollback, context visibility, host mutation, adapter execution, evidence, witness material, DSSE material, or runtime authority occurred. It adds no Home Manager command execution, Nix command execution, live observation, real config reads,$HOMEreads, environment capture, process spawn, shell execution, network access, runtime registry, registry loading, containment runner, context renderer, observation budget, broker, provider runtime, provider-local broadening, real adapter execution, real mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. Phase 17B.1 preserves Home Manager phase/family metadata on refusal reports for clear Home Manager fake descriptors without broadening exact fake-call acceptance or writing fake diagnostic receipts on refusal. - Phase 17C Home Manager observe/read-only diagnostics design:
docs/phases/phase17c-home-manager-observe-design.mddocuments the future Home Manager observe/read-only boundary only. It classifies upstream Home Manager command surfaces, recommends a conservative future first-observe candidate, and defines future descriptor, target grammar, report, context, containment, policy, lease, brake, preflight, stale-artifact, roadmap, and hostile-review requirements. It adds no Rust code, Cargo manifest changes, schemas, parsers, fixtures, CLI commands, tests, live Home Manager observation,home-manager generations,home-manager --version,home-manager option,home-manager packages, Home Manager command execution, Nix command execution, real config reads,$HOMEreads, environment capture, process spawn, shell execution, network access, context renderer, observation budget, containment runner, runtime registry, registry loading, provider-local broadening, dry-run/build adapter, confirm-mode apply adapter, real adapter execution, real mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17C.1 Home Manager static observe target descriptor inspect:
docs/phases/phase17c1-home-manager-static-observe-target-inspect.mdadds a strict staticHomeManagerObserveTargetDescriptorparser, one checked-in valid fixture, and the diagnostic commandadapter home-manager observe target inspect. It writeshome_manager_observe_target_inspect_report.jsononly. It accepts onlydiagnostic-onlystatus, treats descriptor notes as a fixed safe literal rather than freeform text, and redacts the raw input descriptor path from the persisted report while retaining the descriptor SHA-256. It is static target descriptor inspect only: no live observe adapter exists, no Home Manager or Nix command execution exists, no process spawn, shell,which, network,$HOMEread, real config read, generation/version/option/package read, context renderer, observation budget, containment runner, dry-run/build adapter, confirm-mode apply adapter, runtime registry, registry loading, adapter execution, real mutation, or witness/evidence/DSSE/verifier-bench/ Phase 5 semantic change is added. - Phase 17C.2 Home Manager read-only process containment contract:
docs/phases/phase17c2-home-manager-readonly-process-contract.mdis docs/design/contract only. It defines the mandatory fixed-command process contract before any future process-based Home Manager observe implementation can be considered, including operator-configured command identity, exact argv, sanitized environment, controlled cwd, stdin/stdout/stderr limits, timeout, exit-code handling, report shape, raw-output handling, model-context exclusion, privacy posture, and the future roadmap toward a possible separately reviewedhome-manager --versionphase. It adds no Rust code, Cargo manifest changes, schemas, parsers, fixtures, CLI commands, tests, process runner, containment runner,home-manager --version, live observation, Home Manager command execution, Nix command execution, real config reads,$HOMEreads, generation/version/option/package reads, environment capture, shell execution,which, network access, context renderer, observation budget, runtime registry, registry loading, provider-local broadening, dry-run/build adapter, confirm-mode apply adapter, real adapter execution, real mutation, or witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. - Phase 17C.3 Home Manager version observe:
docs/phases/phase17c3-home-manager-version-observe.mdadds exactly one read-only process observation route:adapter home-manager observe version inspect. It accepts one strict command descriptor fixture underfixtures/home_manager_observe/phase17c3/, reuses the Phase 17C.1 static target descriptor as non-authority binding, and invokes only an absolute local operator-provided executable path with exact argv[<absolute local operator path>, "--version"]. It writes deterministichome_manager_version_observe_report.jsononly. It sets the child cwd to the preflighted output directory while redacting the raw cwd path. Stdout and stderr are discarded through null stdio, not captured or persisted, and the report marks Home Manager binary identity as unverified. The operator-provided executable path must be absolute and local; relative executable paths are refused because the child cwd is controlled and PATH/search or cwd-relative executable resolution is out of scope. On Windows, explicit UNC, verbatim, and device namespace executable path syntax is refused; ordinary drive-letter backing storage is not attested. It adds no Home Manager build, switch/apply, rollback, uninstall, generation cleanup,generations,option,packages, config read, Nix invocation, shell,which, PATH search, cwd-relative executable resolution, model-supplied executable/args/env/cwd, inherited full environment, raw cwd persistence, raw stdout/stderr persistence by default, model-visible context, generic process runner, containment runner, context renderer, observation budget, provider broker, adapter registry/runtime registry, real adapter execution, real mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17C.4 Home Manager generations observe redaction design:
docs/phases/phase17c4-home-manager-generations-observe-redaction-design.mdis docs/design only. It designshome-manager generationsobserve/redaction boundaries before a live route can use host output. It defines raw output policy, machine/report versus model-visible context separation, redaction classes and normalized tokens, output bounds, refusal policy, freshness/provenance fields, hostile-text handling, and report/context non-authority. It adds no Rust code, Cargo manifest changes, schemas, parsers, fixtures, CLI command, process spawn, Home Manager invocation, Nix invocation,$HOMEread, config read, live generation read, raw generation output capture, model-visible generation context, context renderer, observation budget, provider broker, provider-local broadening, build, switch/apply, rollback, uninstall, generation cleanup, real adapter execution, real mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17C.5 Home Manager generations fixture rehearsal:
docs/phases/phase17c5-home-manager-generations-fixture-rehearsal.mdadds one diagnostic fixture-only route:adapter home-manager observe generations fixture inspect. It parses a strict checked-in synthetic generations fixture and the Phase 17C.1 static target descriptor, then writeshome_manager_generations_fixture_inspect_report.json. Synthetic raw-like fixture values exercise redaction but are not persisted in the report. It adds no livehome-manager generationsroute, process spawn, Home Manager invocation, Nix invocation,$HOMEread, config read, live generation read, raw host output capture, model-visible generation context, context renderer, observation budget, provider broker, provider-local broadening, build, switch/apply, rollback, uninstall, generation cleanup, real adapter execution, real mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17C.6 Home Manager generations live observe process contract:
docs/phases/phase17c6-home-manager-generations-live-observe-process-contract.mdis docs/design/contract only. It defines the exact process, capture, parser, redaction, refusal, report, and model-visible context boundary that a fixed livehome-manager generationsobserve route must satisfy. It adds no command, process spawn, Home Manager invocation, Nix invocation,$HOMEread, config read, live generation read, stdout/stderr capture, host-output parser/report implementation, raw host output persistence, model-visible generation context, context renderer, observation budget, provider broker, provider-local broadening, build, switch/apply, rollback, uninstall, generation cleanup, real adapter execution, real mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17C.7 Home Manager generations observe:
docs/phases/phase17c7-home-manager-generations-observe.mdadds exactly one fixed read-only live observe route:adapter home-manager observe generations inspect. It parses a strict Phase 17C.7 command descriptor and a Phase 17C.1 static target descriptor, invokes exactly the absolute local operator-provided executable path with one fixed argument,generations, captures bounded stdout/stderr only through in-memory pipes, parses strict upstream-shaped presentation output, redacts and discards raw buffers before writinghome_manager_generations_observe_report.json, and emits no model-visible generation context. It does not prove Home Manager identity or child-internal behavior. It adds no shell execution, PATH search,which, command discovery, model-supplied executable/args/env, inherited environment, raw stdout/stderr persistence, raw executable/cwd/store/profile/generation path persistence, raw store hash persistence, context renderer, observation budget, provider broker, provider-local broadening, direct Nix invocation by Cogitator, Home Manager build, switch/apply, rollback, uninstall, generation cleanup, option/package/config read, arbitrary Nix command, NixOS rebuild, generic process runner, real mutation, or witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. - Phase 17C.8 Home Manager observe boundary hardening:
docs/phases/phase17c8-home-manager-observe-boundary-hardening.mdconsolidates the two existing fixed Home Manager observe routes with a shared conformance fixture, shared report invariant tests, parser/redaction regressions, stale-artifact boundary coverage, and docs wording only. It adds no command, no live route, no process runner, no raw output persistence, no model-visible context, no provider-local behavior, no build, no switch/apply, no rollback, no cleanup, no real mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D Home Manager build boundary design:
docs/phases/phase17d-home-manager-build-boundary-design.mdis docs/design only. It records that future build/dry-run-class work is separate from the existing fixed observe routes becausehome-manager buildmay evaluate user config, realize/build store paths, interact with caches or builders under a future policy, create result-like outputs if unconstrained, and surface sensitive configuration/package/path data. It adds no command, no command descriptor, no live route, no Home Manager build, no switch/apply, no rollback, no cleanup, no generation removal or expiry, no arbitrary Nix invocation, no generic process runner, no shell/which/PATH lookup, no model-supplied argv, no model-visible Home Manager/Nix context, no raw output persistence, no provider/cloud behavior, no real mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.1 Home Manager build boundary contract rehearsal:
docs/phases/phase17d1-home-manager-build-boundary-contract-rehearsal.mdadds strict parsing and tests for a synthetic checked-in build-boundary contract fixture plus hostile refusal fixtures only. It is conformance material, not runtime behavior. It adds no command, no command descriptor, no live route, no process execution, no Home Manager or Nix invocation, no Home Manager build, no switch/apply, no rollback, no cleanup, no generation removal or expiry, no generic process runner, no shell/which/PATH lookup, no model-supplied argv, no model-visible Home Manager/Nix context, no raw output persistence, no provider/cloud behavior, no real mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.2 Home Manager build authorization/preflight design:
docs/phases/phase17d2-home-manager-build-authority-preflight-design.mdrecords the future build/dry-run-class authority model before any executable build route exists. It classifies build-class behavior as separate from observe authority, treats store realization as non-activation but still build-class authority, forbids ambient./resultlinks by default, requires explicit output/no-link and network/cache/substituter policy, and requires minimized reports with raw Home Manager/Nix output not persisted or made model-visible by default. It adds nohome-manager build, no dry-run/build CLI route, no Home Manager/Nix invocation, no process execution, no shell, no PATH search, nowhich, no model-supplied argv, no build/switch/apply/ rollback/cleanup behavior, no provider/cloud behavior, no model-visible Home Manager/Nix context, no real mutation, and no witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. - Phase 17D.3 Home Manager build preflight report rehearsal:
docs/phases/phase17d3-home-manager-build-preflight-report-rehearsal.mdadds strict parsing and tests for one checked-in refused build-class preflight report-shape fixture plus hostile refusal fixtures only. It is synthetic parser/tests/fixtures/docs material, not runtime behavior. It adds no command, no live route, no build preflight runtime, no process execution, no Home Manager or Nix invocation, no Home Manager build, no dry-run/build route, no result symlink creation/inspection/deletion, no switch/apply, no rollback, no cleanup, no generation removal or expiry, no generic process runner, no shell/which/PATH lookup, no model-supplied argv, no model-visible Home Manager/Nix context, no raw output persistence, no provider/cloud behavior, no real mutation, and no witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. - Phase 17D.4 Home Manager build preflight composer rehearsal:
docs/phases/phase17d4-home-manager-build-preflight-composer-rehearsal.mdadds deterministic in-memorycog-modelcomposition of the locked Phase 17D.3 refused build-class preflight report shape plus parser round-trip tests against the existing valid fixture only. The composed report still hasphase: "17D.3". It is synthetic composer/tests/docs material, not runtime behavior. It adds no command, no adapter route, no report writer, no live route, no build preflight runtime, no process execution, no Home Manager or Nix invocation, no Home Manager build, no dry-run/build route, no result symlink creation/inspection/deletion, no switch/apply, no rollback, no cleanup, no generation removal or expiry, no generic process runner, no shell/which/PATH lookup, no model-supplied argv, no model-visible Home Manager/Nix context, no raw output persistence, no provider/cloud behavior, no real mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.5 Home Manager build preflight writer rehearsal:
docs/phases/phase17d5-home-manager-build-preflight-writer-rehearsal.mdadds exactly one synthetic diagnostic writer command:adapter home-manager build-preflight report rehearse --out <dir>. The command writes only the locked Phase 17D.3 refusal-shaped inner report and a Phase 17D.5 outer writer receipt, both validated through strict parsers. It is a writer rehearsal, not a live build preflight. It adds no live build route, no runtime preflight, no Home Manager or Nix invocation, no process execution, no Home Manager build, no dry-run/build route, no switch/apply, no rollback, no cleanup route, no result symlink behavior, no descriptor/ executable/config/flake input, no model-visible Home Manager/Nix context, no raw output/log persistence, no provider/cloud behavior, no real mutation beyond fixed diagnostic artifacts under--out, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.6 Home Manager build preflight request contract rehearsal:
docs/phases/phase17d6-home-manager-build-preflight-request-contract-rehearsal.mdadds a strict syntheticcog-modelparser/composer/tests/fixtures/docs request/authority input contract for a future Home Manager build-preflight. It is contract rehearsal only, not runtime behavior. It adds no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no Home Manager or Nix invocation, no process execution, no Home Manager build, no dry-run/build route, no switch/apply, no rollback, no cleanup route, no descriptor/executable/config/flake input acceptance, no result symlink behavior, no model-visible Home Manager/Nix context, no raw output/log persistence, no provider/cloud behavior, no real mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.7 Home Manager build preflight request-to-refusal rehearsal:
docs/phases/phase17d7-home-manager-build-preflight-request-to-refusal-rehearsal.mdadds a strict syntheticcog-modelparser/composer/tests/fixtures/docs request-to-refusal rehearsal. It validates a Phase 17D.6 request contract through the existing strict parser, composes the locked Phase 17D.3 no-runtime-authority refusal report, and validates the composed inner report through the existing strict parser before producing a Phase 17D.7 report. It is composition rehearsal only, not runtime behavior. It adds no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no Home Manager or Nix invocation, no process execution, no Home Manager build, no dry-run/build route, no switch/apply, no rollback, no cleanup route, no descriptor/executable/config/flake input acceptance, no result symlink behavior, no model-visible Home Manager/Nix context, no raw output/log persistence, no provider/cloud behavior, no real mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.8 Home Manager build preflight architecture checkpoint:
docs/phases/phase17d8-home-manager-build-preflight-architecture-checkpoint.mdadds a docs-only architecture checkpoint and live-build readiness gate design. It summarizes what the Phase 17D.1-17D.7 synthetic chain proves and does not prove, then defines mandatory future gates before any live Home Manager build-preflight candidate. It is design/checkpoint material only, not runtime behavior. It adds no Rust code, no fixtures, no tests, no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no Home Manager or Nix invocation, no process execution, no Home Manager build, no dry-run/build route, no switch/apply, no rollback, no cleanup route, no descriptor/executable/config/flake input acceptance, no result symlink behavior, no model-visible Home Manager/Nix context, no raw output/log persistence, no provider/cloud behavior, no real mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.9 live Home Manager build preflight process contract:
docs/phases/phase17d9-live-home-manager-build-preflight-process-contract.mdadds a docs-only runtime/process-execution gate design. It defines the future fixed-argv, no-shell, no-PATH, no-ambient-environment, bounded-output, timeout, kill/reap/drain, no-result-link, raw-log-disclosure, and explicit network/cache/substituter contract required before any future implementation may invokehome-manager build. It is process-contract material only, not runtime behavior. It adds no Rust code, no fixtures, no tests, no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no Home Manager or Nix invocation, no process execution, no Home Manager build, no dry-run/build route, no switch/apply, no rollback, no cleanup route, no descriptor/executable/config/flake/path input acceptance, no result symlink behavior, no model-visible Home Manager/Nix context, no raw output/log persistence, no provider/cloud behavior, no real mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.10 Home Manager build preflight process transcript rehearsal:
docs/phases/phase17d10-home-manager-build-preflight-process-transcript-rehearsal.mdadds syntheticcog-modelparser/composer/tests/fixtures/docs material only. It records the future build-preflight process gate as a strict typed synthetic transcript with duplicate-key rejecting parser coverage and hostile fixtures. It is not runtime behavior. It adds no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no process runner, no fake process runner, no Home Manager or Nix invocation, nohome-manager build, no descriptor/executable/config/flake/path input acceptance, no result symlink behavior, no model-visible context, no raw output/log persistence, no provider/cloud behavior, no mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.11 Home Manager build preflight fake process harness rehearsal:
docs/phases/phase17d11-home-manager-build-preflight-fake-process-harness-rehearsal.mdadds a fake/test-onlycog-modelprocess mechanics harness only. It uses a harness-false integration test executable as its own fake child to exercise exact fixed argv, no shell, no PATH search, nowhich, controlled cwd, closed stdin, cleared/allowlisted environment, sentinel secret non-inheritance, bounded stdout/stderr summaries, timeout kill/reap/drain, deterministic classification, no raw output persistence by default, and no result-link behavior. It is not a command, not an adapter route, not a report writer command, not a live route, not runtime preflight, not a generic process runner, not Home Manager/Nix execution, nothome-manager build, not descriptor/executable/config/flake/path input acceptance, not provider/cloud behavior, not model-visible context, not mutation, and not witness/evidence/ DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.12 Home Manager build preflight fake process harness hardening:
docs/phases/phase17d12-home-manager-build-preflight-fake-process-harness-hardening.mdadds fake/test-only hardening to the sealed Phase 17D.11cog-modelharness. It covers fake descendant pipe-holder behavior, bounded drain-join deadline, near-timeout child exit, large-output timeout, stale result/raw-log pre-spawn refusal, no-recursive-cleanup behavior, and cwd symlink/reparse hazard refusal or platform skip. It is not a command, not an adapter route, not a report writer command, not a live route, not runtime preflight, not a reusable subprocess API, not Home Manager/Nix execution, nothome-manager build, not descriptor/executable/config/flake/path input acceptance, not result symlink behavior, not raw output persistence, not provider/cloud behavior, not model-visible context, not mutation, and not witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.13 live Home Manager build preflight readiness gate:
docs/phases/phase17d13-live-home-manager-build-preflight-readiness-gate.mdis docs-only readiness gate material. It defines mandatory go/no-go questions, no-go conditions, a future PR checklist, and hostile-review severity framing before any later phase may propose a live Home Manager build-preflight candidate. It adds no Rust code, no fixtures, no tests, no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no process runner, no fake process runner, no Home Manager/Nix invocation, nohome-manager build, no descriptor/executable/ config/flake/path input acceptance, no result symlink behavior, no raw output persistence, no provider/cloud behavior, no model-visible context, no mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.14 live Home Manager build preflight no-go:
docs/phases/phase17d14-live-home-manager-build-preflight-no-go.mdis docs-only no-go material. Outcome B was chosen because the Phase 17D.13 gate is not completely satisfied: route-specific authority/lease/brake, network/cache/substituter, and exact result-link suppression gates remain unresolved. It adds no Rust code, no fixtures, no tests, no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no subprocess API, no Home Manager/Nix invocation, nohome-manager build, no descriptor/executable/config/flake/path input acceptance, no result symlink behavior, no raw output persistence, no provider/cloud behavior, no model-visible context, no mutation, and no witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. - Phase 17D.15 Home Manager build preflight authority gate contract rehearsal:
crates/cog-model/src/home_manager_build_preflight_authority_gate_contract.rsadds a strict synthetic parser/composer plus checked-in fixtures underfixtures/home_manager_build_boundary/phase17d15/. It resolves only the Phase 17D.14 route-specific authority-gate design blocker by requiring existingconfirmmode plus exact policy, lease, brake, host, session, run, action-kind, target, timestamp, and request matching in a no-runtime-authority contract. It does not resolve network/cache/substituter policy or exact argv/result-link proof. It adds no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no process runner, no fake process runner, no subprocess API, no Home Manager/Nix invocation, nohome-manager build, no descriptor/executable/config/flake/path input acceptance, no result-link behavior, no raw output persistence, no provider/cloud behavior, no model-visible context, no mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.16 Home Manager build preflight network policy contract rehearsal:
crates/cog-model/src/home_manager_build_preflight_network_policy_contract.rsadds a strict synthetic parser/composer plus checked-in fixtures underfixtures/home_manager_build_boundary/phase17d16/. It resolves only the Phase 17D.14 network/cache/substituter policy design/rehearsal blocker by defining fail-closed handling for ambient Nix config, NIX_CONFIG, NIX_USER_CONF_FILES, NIX_CONF_DIR, NIX_PATH, XDG config, proxy environment, credentials, tokens, netrc, signing keys, SSH/GPG agents, builders, remote builders, substituters, trusted substituters, trusted public keys, registries, flake config acceptance, offline mode, fixed reviewed Nix option overrides, unknown Nix config behavior, raw policy material persistence, model/provider/cloud visibility, runtime/live/process claims, witness/ evidence/DSSE/Phase 5 drift, and mutation claims. It does not implement enforcement and does not resolve exact argv/result-link suppression proof. It adds no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no process runner, no fake process runner, no subprocess API, no Home Manager/Nix invocation, nohome-manager build, no descriptor/executable/config/flake/path input acceptance, no result-link behavior, no raw output persistence, no raw config/token/proxy/substituter/ builder material persistence, no provider/cloud behavior change, no model-visible context, no mutation, and no witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. - Phase 17D.17 Home Manager build preflight argv result-link contract
rehearsal:
crates/cog-model/src/home_manager_build_preflight_argv_result_link_contract.rsadds a strict synthetic parser/composer plus checked-in fixtures underfixtures/home_manager_build_boundary/phase17d17/. It resolves only the Phase 17D.14 exact argv/result-link proof design/rehearsal blocker by fixing the Home Manager argv template, recording both expected flake and legacy internal Nix result-link suppression mappings, requiring future exact single-mode selection, refusing--out-link, arbitrary args, shell/PATH/which, config/flake/path inputs, false proof sources, result-path access drift, raw output persistence, model/provider/cloud visibility, runtime/live/ process claims, authority-gate alteration, network/cache/substituter policy alteration, witness/evidence/DSSE/Phase 5 drift, and mutation claims. It does not implement enforcement. It adds no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no process runner, no fake process runner, no subprocess API, no Home Manager/Nix invocation, nohome-manager build, nonix build, nonix-build, no descriptor/executable/config/flake/path input acceptance, no result-link behavior, no raw output persistence, no provider/cloud behavior change, no model-visible context, no mutation, and no witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. - Phase 17D.18 Home Manager build preflight readiness bundle contract
rehearsal:
crates/cog-model/src/home_manager_build_preflight_readiness_bundle_contract.rsadds a strict synthetic parser/composer plus checked-in fixtures underfixtures/home_manager_build_boundary/phase17d18/. It binds the Phase 17D.15 authority-gate contract, Phase 17D.16 network/cache/substituter policy contract, and Phase 17D.17 argv/result-link contract into one no-runtime-authority bundle. It proves only local internal consistency of those synthetic contracts and does not implement enforcement. It adds no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no process runner, no fake process runner, no subprocess API, no process execution, no Home Manager/Nix invocation, no Home Manager build invocation, nonix build, nonix-build, no descriptor/executable/config/ flake/path input acceptance, no result-link behavior, no result path creation/inspection/follow/read/delete/cleanup/interpretation, no raw output persistence, no provider/cloud behavior change, no model-visible context, no authority-gate semantic change, no network/cache/substituter policy semantic change, no argv/result-link contract semantic change, no mutation, and no witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.19 Home Manager build preflight live candidate pre-review:
docs/phases/phase17d19-home-manager-build-preflight-live-candidate-pre-review.mdadds docs-only design material for a future live candidate. It consumes the Phase 17D.15 authority-gate contract, Phase 17D.16 network/cache/substituter policy contract, Phase 17D.17 argv/result-link contract, and Phase 17D.18 readiness bundle as synthetic prerequisites. Design Outcome B keeps the future live candidate blocked by unresolved HOME/XDG environment policy, network/cache/substituter policy enforcement, and child-internal route-mode proof. It adds no Rust code, fixtures, tests, CLI command, adapter route, report writer command, live route, runtime preflight, process runner, fake process runner, subprocess API, process execution, Home Manager/Nix invocation, result-link behavior, result path behavior, raw output persistence, provider/cloud behavior change, model-visible context, mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 17D.21 Home Manager build preflight environment-inclusive readiness
bundle contract:
crates/cog-model/src/home_manager_build_preflight_environment_inclusive_readiness_bundle_contract.rsadds a strict synthetic parser/composer plus checked-in fixtures underfixtures/home_manager_build_boundary/phase17d21/. It keeps Phase 17D.18 as the earlier three-prerequisite readiness bundle and adds a separate schema requiring Phase 17D.15, Phase 17D.16, Phase 17D.17, and the Phase 17D.20 HOME/XDG/environment policy contract to be present and internally valid synthetic material. It records that live build-preflight remains no-go and that bundle success authorizes nothing by existence. It adds no CLI command, no adapter route, no report writer command, no live route, no runtime preflight, no process runner, no fake process runner, no subprocess API, no process execution, no Home Manager/Nix invocation, no Home Manager build invocation, nonix build, nonix-build, no shell/PATH/which, no descriptor/executable/config/flake/path input acceptance, no environment inheritance enforcement, no network/cache/substituter enforcement, no argv/result-link runtime enforcement, no result-link behavior, no raw output or HOME/XDG/env/path/log persistence, no provider/cloud behavior change, no model-visible raw host context, no mutation, and no witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. - Phase 17D.22 Home Manager build preflight integrated fake gate rehearsal:
crates/cog-model/tests/phase17d11_home_manager_build_preflight_fake_process_harness.rsadds fake/test-only gate-ordering coverage inside the existing sealed Phase 17D.11/17D.12 harness. It parses the Phase 17D.21 environment- inclusive readiness bundle before the fake harness closure may run, refuses stale/mutated/incomplete readiness before fake child spawn, and then exercises the existing fixed fake child/descendant path. It adds no CLI command, adapter route, report writer command, live route, runtime preflight, runtime gate implementation, production process execution, process runner, new fake process runner outside the sealed integration-test harness, generic subprocess API, Home Manager/Nix invocation, Home Manager build invocation,nix build,nix-build, shell/PATH/which, descriptor/ executable/config/flake/path input acceptance, production environment inheritance enforcement, network/cache/substituter enforcement, argv/result- link runtime enforcement, result-link behavior, raw output or HOME/XDG/env/ path/log persistence, provider/cloud behavior change, model-visible raw host context, mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. Live build-preflight remains no-go. - Phase 17D.23 Home Manager build preflight closeout live-vs-synthetic map:
docs/phases/phase17d23-home-manager-build-preflight-closeout-live-vs-synthetic-map.mdadds docs-only closeout material for the Phase 17D workstream. It separates docs-only design material, syntheticcog-modelcontracts, the existing fixed synthetic diagnostic writer, fake/test-only harness material, and nonexistent live runtime authority after Phase 17D.22. It adds no Rust code, tests, fixtures, parser/composer/schema changes, CLI command, adapter route, report writer command, live route, runtime preflight, process execution, process runner, fake process runner, generic subprocess API, Home Manager/Nix invocation, Home Manager build invocation,nix build,nix-build, shell/PATH/which, descriptor/executable/config/flake/path input acceptance, environment inheritance enforcement, network/cache/substituter enforcement, argv/result-link runtime enforcement, result-link behavior, raw output or HOME/XDG/env/path/log persistence, provider/cloud behavior change, model-visible raw host context, mutation, or witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. It closes out the current synthetic/fake stack and live build-preflight remains no-go. - Phase 17D.24 Home Manager build preflight live runtime gate design:
docs/phases/phase17d24-home-manager-build-preflight-live-runtime-gate-design.mdadds docs-only design material for a possible future live runtime gate and no-go implementation checklist. It documents future reviewed inputs, ordered gate stages, pre-spawn rejection, process construction invariants, HOME/XDG/ env design, Nix/network/cache/substituter design, result-path design, output/report boundaries, and hostile-test requirements. It adds no Rust code, tests, fixtures, parser/composer/schema changes, CLI command, adapter route, report writer command, live route, runtime preflight, runtime gate implementation, process execution, process runner, fake process runner, generic subprocess API, Home Manager/Nix invocation, Home Manager build invocation,nix build,nix-build, shell/PATH/which, descriptor/ executable/config/flake/path input acceptance, environment inheritance enforcement, network/cache/substituter enforcement, output capture implementation, argv/result-link runtime enforcement, result-link behavior, raw output or HOME/XDG/env/path/log persistence, provider/cloud behavior change, model-visible raw host context, mutation, or witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. It preserves live build-preflight no-go. - Phase 17D.25 Home Manager build preflight runtime-gate report-shape
contract:
crates/cog-model/src/home_manager_build_preflight_runtime_gate_report_shape.rsadds a strict synthetic parser/composer plus checked-in fixtures underfixtures/home_manager_build_boundary/phase17d25/. It records the Phase 17D.21 environment-inclusive readiness bundle marker and the Phase 17D.20 HOME/XDG/environment policy marker, references Phase 17D.24 as design-only material, requires dangerous booleans, fixes allowed and forbidden report material lists, and refuses raw path/env/output/credential/provider-looking string material. It adds no CLI command, adapter route, report writer command, live route, runtime preflight, runtime gate implementation, process execution, process runner, fake process runner, generic subprocess API, Home Manager/Nix invocation, Home Manager build invocation,nix build,nix-build, shell/PATH/which, descriptor/executable/config/flake/path input acceptance, environment inheritance enforcement, network/cache/ substituter enforcement, output capture implementation, argv/result-link runtime enforcement, result-link behavior, raw output or HOME/XDG/env/path/ log/result/store persistence, provider/cloud behavior change, model-visible raw host context, mutation, or witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. It preserves live build-preflight no-go and authorizes nothing by existence. - Phase 17D.26 Home Manager build preflight runtime-gate report writer
rehearsal:
crates/cog-model/src/home_manager_build_preflight_runtime_gate_report_writer_rehearsal.rsadds a strict synthetic writer-rehearsal parser/composer/helper plus checked-in fixtures underfixtures/home_manager_build_boundary/phase17d26/. It composes the Phase 17D.25 report shape, validates it through the Phase 17D.25 parser, and writes only two fixed synthetic JSON artifacts under tests/helpers with no-overwrite stale-artifact refusal, output-directory metadata checks, symlink/reparse-like output-directory refusal where metadata exposes it, no recursive cleanup, and unrelated-file preservation. It adds no CLI command, adapter route, report writer command, live route, runtime preflight, runtime gate implementation, process execution, process runner, fake process runner, generic subprocess API, Home Manager/Nix invocation, Home Manager build invocation,nix build,nix-build, shell/PATH/which, descriptor/ executable/config/flake/path input acceptance, environment inheritance enforcement, network/cache/substituter enforcement, output capture implementation, argv/result-link runtime enforcement, result-link behavior, raw output or HOME/XDG/env/path/log/result/store persistence, provider/cloud behavior change, model-visible raw host context, mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. It preserves live build-preflight no-go and authorizes nothing by existence. - Phase 17D.27 Home Manager build preflight pre-spawn gate decision rehearsal:
crates/cog-model/src/home_manager_build_preflight_pre_spawn_gate_decision_rehearsal.rsadds a strict synthetic input/evaluator/report parser/composer plus checked-in fixtures underfixtures/home_manager_build_boundary/phase17d27/. It consumes only synthetic prerequisite and policy booleans, records Phase 17D.21, Phase 17D.25, and Phase 17D.26 markers plus the Phase 17D.24 design-only reference, preserves deterministic first-failure ordering, and returns matched/no-process-authority or refused/no-spawn diagnostics. The evaluator performs no filesystem writes and does not call the Phase 17D.26 writer helper. It adds no CLI command, adapter route, report writer command, live route, runtime preflight, runtime gate implementation, process construction, process execution, process runner, fake process runner, generic subprocess API, Home Manager/Nix invocation, Home Manager build invocation,nix build,nix-build, shell/PATH/which, descriptor/executable/config/ flake/path input acceptance, environment inheritance enforcement, network/ cache/substituter enforcement, output capture implementation, argv/ result-link runtime enforcement, result-link behavior, raw output or HOME/ XDG/env/path/log/result/store persistence, provider/cloud behavior change, model-visible raw host context, mutation, or witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change. It preserves live build-preflight no-go and authorizes nothing by existence. - Phase 18A Home Manager build preflight architecture consolidation audit:
docs/phases/phase18a-home-manager-build-preflight-architecture-consolidation-audit.mdadds a docs-only audit note for the Phase 17D stack after Phase 17D.27. It inventories docs-only, syntheticcog-modelcontract/parser/composer, fixed synthetic writer/helper, fake/test-only harness, synthetic evaluator, and nonexistent live runtime material. It adds no Rust code, tests, fixtures, parser/composer/schema/evaluator changes, helper extraction, refactor, CLI command, adapter route, report writer command, live route, runtime preflight, runtime gate implementation, process construction, process execution, Home Manager/Nix invocation, output capture implementation, result-link behavior, provider/cloud behavior, mutation, or witness/evidence/DSSE/verifier-bench/ Phase 5 semantic change. It preserves live build-preflight no-go and authorizes nothing by existence. - Phase 18B Home Manager build preflight index and fixture map:
docs/home-manager-build-preflight-index.mdanddocs/phases/phase18b-home-manager-build-preflight-index-and-fixture-map.mdadd docs-only navigation material for the current Home Manager build-preflight workstream. They map visible phases, modules/tests, fixture directories, valid fixture examples, hostile fixture classes, navigation risks, and remaining live no-go blockers. They add no Rust code, tests, fixtures, parser/composer/schema/evaluator changes, helper extraction, refactor, CLI command, adapter route, report writer command, live route, runtime preflight, runtime gate implementation, process construction, process execution, Home Manager/Nix invocation, output capture implementation, result-link behavior, provider/cloud behavior, mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. They preserve live build-preflight no-go and authorize nothing by existence. - Phase 18C Home Manager build preflight helper-extraction pre-review:
docs/phases/phase18c-home-manager-build-preflight-helper-extraction-pre-review.mdadds docs-only risk analysis for repeated parser/composer guard patterns in the Home Manager build-preflight stack. It classifies candidate-only helper mechanics, unsafe consolidation areas, needs-design areas, future 18D constraints, and remaining live no-go blockers. It adds no Rust code, tests, fixtures, parser/composer/schema/evaluator changes, helper extraction, refactor, macro/template extraction, CLI command, adapter route, report writer command, live route, runtime preflight, runtime gate implementation, process construction, process execution, Home Manager/Nix invocation, output capture implementation, result-link behavior, provider/cloud behavior, mutation, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. It preserves live build-preflight no-go and authorizes no helper extraction or future authority by existence. - Phase 18D Home Manager build preflight tiny synthetic parse helper:
crates/cog-model/src/home_manager_build_preflight_synthetic_parse_helpers.rsadds one private internal synthetic parser-mechanics helper used narrowly by the D25 runtime-gate report-shape parser and D27 pre-spawn decision parser. It preserves caller-owned issue codes, accepted JSON shapes, fixtures, schemas, reports, composers, evaluators, writer behavior, command/route/ runtime/process behavior, Home Manager/Nix no-go, provider/cloud no-go, witness/evidence/DSSE boundaries, Phase 5 semantics, and mutation no-go. It adds no public API, CLI command, adapter route, report writer command, live route, runtime preflight, runtime gate implementation, process construction, process execution, process runner, fake process runner, generic subprocess API, Home Manager/Nix invocation, output capture implementation, result-link behavior, fixture change, schema change, accepted JSON shape change, issue-code change, raw-material scanner extraction, dangerous-boolean semantic extraction, writer helper extraction, fake harness extraction, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. Helper success authorizes no runtime, build, execution, live readiness, or future authority by existence. - Phase 19A governance provenance replay roadmap:
docs/phases/phase19a-governance-provenance-replay-roadmap.mdadds a docs-only governance/provenance/replay roadmap and classification of future ideas such as replay sidecars, negative-space provenance, AI BOM, attestation, graph export, capability-router pre-review, synthetic rehearsal, and semantic consent UI. It adds no Rust code, tests, fixtures, schemas, parser/composer/schema/evaluator changes, helper extraction, command, route, runtime gate, process construction, process execution, Home Manager/Nix invocation, provider/cloud behavior, witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change, mutation, standards-compliance claim, standards-conformance claim, certification claim, production-trust claim, or attestation claim. Roadmap success authorizes no execution, build, replay sidecar, capability router, AI BOM, attestation, graph export, consent UI, live readiness, or future authority by existence. - Phase 19B doctrine schema inventory pre-review:
docs/phases/phase19b-doctrine-schema-inventory-pre-review.mdadds a docs-only doctrine/schema-inventory pre-review. It inventories current doctrine, contract-like records, report artifacts, fixture families, witness material, and public-ish command outputs, then classifies stability and public-contract risk before any future schema registry or replay/provenance sidecar work. It adds no Rust code, tests, fixtures, schema files, schema registry, parser/composer/schema/evaluator changes, helper extraction, command, route, runtime gate, process construction, process execution, Home Manager/Nix invocation, provider/cloud behavior, witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change, mutation, standards-compliance claim, standards-conformance claim, certification claim, production-trust claim, or attestation claim. Inventory success authorizes no schema creation, public API declaration, execution, live readiness, or future authority by existence. - Phase 20A Home Manager live runtime gate pre-review:
docs/phases/phase20a-home-manager-live-runtime-gate-pre-review.mdadds a docs-only hostile pre-review for future Home Manager live-runtime-gate implementation boundaries. It keeps live Home Manager build-preflight no-go and adds no code, tests, fixtures, schemas, command, route, runtime gate implementation, process construction, Home Manager/Nix invocation, output capture, provider/cloud behavior, witness/evidence/DSSE/Phase 5 semantic change, mutation, live readiness, or future authority. - Phase 20B Home Manager build preflight runtime gate refusal contract:
crates/cog-model/src/home_manager_build_preflight_runtime_gate_refusal_contract.rsadds a phase-local synthetic refusal-only contract/parser/composer with checked-in fixtures underfixtures/home_manager_build_boundary/phase20b/and docs atdocs/phases/phase20b-home-manager-build-preflight-runtime-gate-refusal-contract.md. It keeps live Home Manager build-preflight no-go and adds no CLI command, adapter route, live route, runtime gate implementation, process construction, Home Manager/Nix invocation, output capture, result-link behavior, provider/cloud raw host context, schema registry, public API, witness/evidence/DSSE/verifier-bench/Phase 5 semantic change, mutation, live readiness, or future authority. - Phase 20C Home Manager build preflight process-construction pre-review:
docs/phases/phase20c-home-manager-build-preflight-process-construction-pre-review.mdadds docs-only hostile pre-review mapping the invariants required before any later reviewed phase may even attempt process construction. It adds no implementation, command, route, process construction,Command::new, process runner, Home Manager/Nix invocation, output capture, result-link behavior, mutation, schema/public API, live readiness, or future authority. Live Home Manager build-preflight remains no-go. - Phase 20D Home Manager build preflight process-construction invariant
contract:
crates/cog-model/src/home_manager_build_preflight_process_construction_invariant_contract.rsadds a phase-local synthetic refusal-only contract/parser/composer with checked-in fixtures underfixtures/home_manager_build_boundary/phase20d/and docs atdocs/phases/phase20d-home-manager-build-preflight-process-construction-invariant-contract.md. It encodes Phase 20C invariants as unresolved and keeps live Home Manager build-preflight no-go. It adds no CLI command, adapter route, live route, runtime gate implementation, process construction,Command::new, process builder, process spawn, process runner, Home Manager/Nix invocation, output capture, result-link behavior, raw host persistence/disclosure, provider/cloud raw host context, schema registry, public API, witness/evidence/DSSE/verifier-bench/Phase 5 semantic change, mutation, compliance/conformance/attestation/production-trust claim, live readiness, future implementation approval, or future authority. - Phase 20E Home Manager build preflight refusal-before-process-construction
ordering rehearsal:
crates/cog-model/src/home_manager_build_preflight_refusal_before_process_construction_ordering_rehearsal.rsadds phase-local synthetic input/report/evaluator/parser/composer material with checked-in fixtures underfixtures/home_manager_build_boundary/phase20e/and docs atdocs/phases/phase20e-home-manager-build-preflight-refusal-before-process-construction-ordering-rehearsal.md. It consumes Phase 20D markers synthetically and records that unresolved process-construction prerequisites produce refusal before construction. It keeps live Home Manager build-preflight no-go and adds no CLI command, adapter route, live route, runtime gate implementation, process construction,Command::new, process builder, process spawn, process runner, Home Manager/Nix invocation, output capture, timeout/kill/reap/drain behavior, result-link behavior, raw host persistence/disclosure, provider/cloud raw host context, schema registry, public API, witness/evidence/DSSE/ verifier-bench/Phase 5 semantic change, mutation, compliance/conformance/attestation/production-trust claim, live readiness, future implementation approval, or future authority. - Phase 20F Home Manager build preflight executable identity and child-route
proof pre-review:
docs/phases/phase20f-home-manager-build-preflight-executable-identity-and-child-route-proof-pre-review.mdadds docs-only hostile pre-review material mapping the exact invariants required before any later phase may claim it knows whichhome-managerexecutable is targeted and which child route it will take. It keeps live Home Manager build-preflight no-go and adds no Rust code, tests, fixtures, schemas, parser/composer/evaluator/writer changes, CLI command, adapter route, live route, runtime gate implementation, executable identity implementation, executable descriptor contract, child-route proof implementation, process construction,Command::new, process builder, process spawn, process runner, Home Manager/Nix invocation, output capture, timeout/kill/reap/drain behavior, result-link behavior, raw host persistence/disclosure, provider/cloud raw host context, schema registry, public API, witness/evidence/DSSE/verifier-bench/Phase 5 semantic change, mutation, compliance/conformance/attestation/production-trust claim, live readiness, future implementation approval, or future authority. - Phase 20G Home Manager build preflight executable identity route-proof
contract:
crates/cog-model/src/home_manager_build_preflight_executable_identity_route_proof_contract.rs,fixtures/home_manager_build_boundary/phase20g/, anddocs/phases/phase20g-home-manager-build-preflight-executable-identity-route-proof-contract.mdadd phase-local synthetic refusal-only contract/parser/composer/fixtures/tests material encoding executable identity and child-route proof as unresolved. Valid parse/composition means no executable is accepted, no child route is proven, no descriptor exists, and no process construction is allowed. It keeps live Home Manager build-preflight no-go and adds no CLI command, adapter route, live route, runtime gate implementation, executable identity implementation, executable descriptor implementation, runtime executable descriptor, child-route proof implementation, process construction,Command::new, process builder, process spawn, process runner, fake process runner, subprocess API, Home Manager/Nix invocation, output capture, timeout/kill/reap/drain implementation, result-link behavior, result-path touching, raw host persistence/disclosure, provider/cloud raw host context, schema registry, public API, witness/evidence/DSSE/verifier-bench/Phase 5 semantic change, mutation, compliance/conformance/attestation/production trust claim, live readiness, future implementation approval, or future authority. - Phase 20H Home Manager build preflight exact argv / no-link / result-path
pre-review:
docs/phases/phase20h-home-manager-build-preflight-exact-argv-no-link-result-path-pre-review.mdadds docs-only hostile pre-review material mapping exact argv, no-link/no-out-link, stale result-path, and raw output/result-path disclosure risks before any later synthetic contract or implementation. It keeps live Home Manager build-preflight no-go and adds no Rust code, tests, fixtures, schemas, parser/composer/evaluator/writer changes, CLI command, adapter route, live route, runtime gate, process construction,Command::new, process builder/spawn/runner/subprocess API, Home Manager/Nix invocation, output capture, timeout/kill/reap/drain behavior, result-link behavior, result-path touching, filesystem writer route, mutation, schema registry/public API, witness/evidence/DSSE/verifier-bench/ Phase 5 semantic change, compliance/conformance/attestation/production/live- readiness claim, future implementation approval, or future authority. - Phase 20I Home Manager build preflight exact argv / no-link / result-path
contract:
crates/cog-model/src/home_manager_build_preflight_exact_argv_no_link_result_path_contract.rs,fixtures/home_manager_build_boundary/phase20i/, anddocs/phases/phase20i-home-manager-build-preflight-exact-argv-no-link-result-path-contract.mdadd phase-local synthetic refusal-only contract/parser/composer/fixtures/tests material encoding Phase 20H exact argv, no-link/no-out-link, result-path, and output/report hazards as unresolved. Valid parse/composition authorizes no exact argv, no runtime argv enforcement, no result-link behavior, no result-path touching, no output capture, no process construction, and no live Home Manager/Nix authority. It keeps live Home Manager build-preflight no-go and adds no CLI command, adapter route, live route, runtime gate, executable identity implementation, executable descriptor implementation, child-route proof implementation,Command::new, process builder/spawn/runner/ subprocess API, Home Manager/Nix invocation, filesystem writer route, mutation, schema registry/public API, witness/evidence/DSSE/verifier-bench/ Phase 5 semantic change, compliance/conformance/attestation/production/live- readiness claim, future implementation approval, or future authority. - Phase 20J Home Manager build preflight bounded output / timeout / kill / reap
/ drain pre-review:
docs/phases/phase20j-home-manager-build-preflight-bounded-output-timeout-kill-reap-drain-pre-review.mdadds docs-only hostile pre-review material mapping bounded output, stdout/stderr/log handling, pipe deadlock risk, timeout semantics, kill/reap/drain behavior, process-tree/descendant hazards, and raw-output disclosure boundaries before any later synthetic contract or implementation. It keeps live Home Manager build-preflight no-go and adds no Rust code, tests, fixtures, schemas, parser/composer/evaluator/writer changes, CLI command, adapter route, live route, runtime gate, exact argv implementation, runtime argv enforcement, output capture, timeout implementation, kill/reap/drain implementation, process construction,Command::new, process builder/spawn/runner/subprocess API, Home Manager/Nix invocation, result-link behavior, result-path touching, filesystem writer route, mutation, schema registry/public API, witness/evidence/DSSE/verifier-bench/ Phase 5 semantic change, compliance/conformance/attestation/production/live- readiness claim, future implementation approval, or future authority. - Phase 21A route and authority inventory snapshot:
docs/phases/phase21a-route-authority-inventory-snapshot.mdadds a docs-only inventory of current command families, routes, diagnostics, fixture/synthetic surfaces, live-read diagnostics, legacy-quarantined helpers, Home Manager build-preflight no-go/live-disabled status, sandbox availability checks, and governance/CI review surfaces. It adds no Rust code, tests, fixtures, schemas, parser/composer behavior, CLI route behavior, adapter route behavior, workflow, provider/cloud behavior, process construction, Home Manager/Nix invocation, witness/evidence/DSSE/verifier/ Phase 5 semantic change, mutation, filesystem writer route, production/live- readiness claim, future implementation approval, or future authority. - Phase 21F docs/status drift guard:
scripts/check-docs-status-drift.shadds a narrow phrase-based guard for high-value authority-boundary anchors, Phase 21A discoverability, Phase 5 root visibility in the inventory, Home Manager build-preflight no-go/live- disabled status, no-authority-by-existence wording, CI/build/check success non-authority, and legacy Hyprland quarantine visibility. It is wired into the existing minimal CI workflow and standard local check docs. It adds no Rust code, tests, fixtures, schemas, parser/composer behavior, CLI route behavior, adapter route behavior, new workflow, workflow permission/event change, provider/cloud behavior, process construction, Home Manager/Nix invocation, witness/evidence/DSSE/verifier/Phase 5 semantic change, mutation, filesystem writer route, production/live-readiness claim, future implementation approval, or future authority. - Phase 22A Home Manager build-preflight blocker ledger:
docs/phases/phase22a-home-manager-build-preflight-blocker-ledger.mdadds docs-only ledger material that enumerates remaining blockers before a live Home Manager build-preflight candidate pre-review could even be proposed. It keeps live build-preflight no-go/live-disabled and records docs-only, synthetic-only, fake/test-only, missing-live-implementation, later-contract, hostile-corpus, and out-of-scope blocker states. It adds no Rust code, tests, fixtures, schemas, parser/composer behavior, CLI route behavior, adapter route behavior, workflow, provider/cloud behavior, runtime gate, process construction,Command::new, Home Manager/Nix invocation, output capture, timeout/kill/reap/drain implementation, result-link behavior, result-path touching, witness/evidence/DSSE/verifier/Phase 5 semantic change, mutation, filesystem writer route, production/live-readiness claim, future implementation approval, or future authority. - Phase 22B Home Manager build-preflight exact argv / no-link / result-path
closure:
docs/phases/phase22b-home-manager-build-preflight-exact-argv-no-link-result-path-closure.mdadds docs-only closure/gap-review material for the first Phase 22A follow-up. It records that current Phase 20I refusal-only parser/composer/fixtures/tests already cover the exact argv, no-link/no-out-link, out-link, result-path, stale-artifact, raw output/result-path, dry-run/build-success, passthrough, shell/PATH/which, environment/cwd/HOME/XDG/Nix-config, process, invocation, Phase 5, schema/public-API, live-readiness, future-implementation, and future-authority drift classes sufficiently for docs/synthetic closure. It adds no Rust code, tests, fixtures, schemas, parser/composer behavior, CLI route behavior, adapter route behavior, workflow, provider/cloud behavior, runtime gate, process construction,Command::new, Home Manager/Nix invocation, output capture, timeout/kill/reap/drain implementation, result-link behavior, result-path touching, witness/evidence/DSSE/verifier/ Phase 5 semantic change, mutation, filesystem writer route, production/live-readiness claim, future implementation approval, or future authority. - Phase 22C Home Manager build-preflight bounded output / timeout / kill /
reap / drain contract:
crates/cog-model/src/home_manager_build_preflight_bounded_output_timeout_kill_reap_drain_contract.rs,fixtures/home_manager_build_boundary/phase22c/, anddocs/phases/phase22c-home-manager-build-preflight-bounded-output-timeout-kill-reap-drain-contract.mdadd one strict phase-local synthetic refusal-only contract/parser/composer/ fixture/test set encoding Phase 20J output, stdio, timeout, kill, reap, drain, process-tree, raw-output, and authority-confusion hazards as unresolved. It keeps live Home Manager build-preflight no-go/live-disabled and adds no CLI command, adapter route, live route, runtime gate implementation, process construction,Command::new, process builder/spawn/ runner/subprocess API, Home Manager/Nix invocation, output capture, stdout/stderr/log capture, timeout implementation, kill/reap/drain implementation, stdio piping/inheritance safety proof, result-link behavior, result-path touching, mutation, filesystem writer route, schema registry, public API, witness/evidence/DSSE/verifier/Phase 5 semantic change, production/live-readiness/compliance/conformance/attestation claim, future implementation approval, or future authority. - Phase 22D Home Manager build-preflight executable identity / child-route
proof closure:
docs/phases/phase22d-home-manager-build-preflight-executable-identity-child-route-proof-closure.mdadds docs-only Mode A closure/gap-review material for the Phase 22A executable identity / child-route proof follow-up. It records that current Phase 20G refusal-only parser/composer/fixtures/tests already cover the executable identity acceptance, executable descriptor authority, runtime descriptor acceptance, child-route proof acceptance, path/hash/store/version proof, interpreter/sourced-library/wrapper/delegated-Nix proof, daemon/global Nix config proof, branch proof, HOME/XDG/user/hostname discovery, process construction,Command::new, Home Manager/Nix invocation, raw host/provider material, Phase 5, schema/public-API, live-readiness, future-implementation, and future-authority drift classes sufficiently for docs/synthetic closure. It adds no Rust code, tests, fixtures, schemas, parser/composer behavior, CLI route behavior, adapter route behavior, workflow, provider/cloud behavior, runtime gate, process construction,Command::new, Home Manager/Nix invocation, output capture, timeout/kill/reap/drain implementation, result-link behavior, result-path touching, witness/evidence/DSSE/verifier/Phase 5 semantic change, mutation, filesystem writer route, production/live-readiness claim, future implementation approval, or future authority. - Phase 22E Home Manager build-preflight combined hostile corpus:
docs/phases/phase22e-home-manager-build-preflight-combined-hostile-corpus.md,crates/cog-model/src/home_manager_build_preflight_combined_hostile_corpus_contract.rs, andfixtures/home_manager_build_boundary/phase22e/add Mode B targeted rejection-only synthetic contract/parser/composer/tests/fixtures for the cross-axis authority-collapse surface. The only accepted decision isrefused_combined_home_manager_build_preflight_authority_collapse. Valid parse success authorizes nothing. The contract rejects claims that runtime-gate, process-construction, executable-identity, child-route proof, exact argv/no-link/result-path, bounded output/timeout/kill/reap/drain, docs-only closure, parser/fixture/test/check/CI success, upstream citations, provider/cloud output, witness/evidence/DSSE, or Phase 5 material imply live Home Manager build-preflight readiness, process construction, Home Manager/Nix invocation, implementation approval, future implementation, or future authority. It adds no live route, CLI command, adapter route, runtime gate implementation, executable identity acceptance, executable descriptor acceptance, runtime descriptor acceptance, child-route proof acceptance, exact argv acceptance, no-link/no-out-link live proof, result-path safety, bounded output implementation, output capture, timeout/kill/reap/drain behavior, result-path touching, process construction,Command::new, process builder/spawn/runner/subprocess API, Home Manager/Nix invocation, provider/cloud behavior, witness/evidence/DSSE/verifier/Phase 5 semantic change, mutation, schema registry, public API, compliance/conformance/ certification/attestation/production-trust/live-readiness claim, future implementation approval, or future authority. - Phase 22F Home Manager build-preflight synthetic closure map:
docs/phases/phase22f-home-manager-build-preflight-synthetic-closure-map.mdadds Mode A docs-only closeout / interpretation-map material for the Phase 22A-22E synthetic closure stack. It freezes the interpretation that Phase 22A-22E improved refusal discipline, navigation, hostile coverage, and no-go accounting only. The closure stack remains evidence of refusal discipline and local synthetic consistency only, not readiness evidence, implementation approval, authorization, compliance evidence, production trust, or proof of safe host behavior. Phase 22F closes no live blocker and adds no Rust code, tests, fixtures, schemas, parser/composer behavior, CLI command, adapter route, live route, runtime gate, live candidate, process construction,Command::new, process builder/spawn/runner/subprocess API, fake process runner, executable identity acceptance, executable descriptor acceptance, runtime descriptor acceptance, child-route proof acceptance, exact argv implementation/enforcement, no-link/no-out-link enforcement, result-link or result-path behavior, output capture, timeout/kill/reap/drain behavior, Home Manager/Nix invocation, provider/cloud behavior, witness/evidence/DSSE/ verifier/Phase 5 semantic change, mutation/switch/apply/rollback/cleanup, schema registry, public API, production/live-readiness/compliance/ conformance/certification/attestation claim, future implementation approval, or future authority. - Phase 23A Home Manager build-preflight live-candidate pre-review:
docs/phases/phase23a-home-manager-build-preflight-live-candidate-pre-review.mdadds docs-only pre-review material and records Design Outcome B: live Home Manager build-preflight remains no-go. It keeps Phase 22F as the synthetic closure-map input and does not convert Phase 22A-22F, PR #233, CI success, parser/test success, fixtures, docs, drift guards, upstream citations, or governance files into runtime authority. It adds no Rust code, tests, fixtures, schemas, parser/composer behavior, CLI command, adapter route, live route, runtime gate, process construction,Command::new, process builder, process spawn, process runner, subprocess API, Home Manager/Nix invocation, output capture, stdout/stderr/log capture, timeout/kill/reap/drain behavior, result-link behavior, result-path touching/read/follow/delete/cleanup, provider/cloud behavior, raw Home Manager/Nix context pack, witness/evidence/ DSSE/verifier/Phase 5 semantic change, mutation/switch/apply/rollback/ cleanup, live readiness, future implementation approval, or future authority. - Phase 24A doctrine / contract registry design gate:
docs/phases/phase24a-doctrine-contract-registry-design.mdadds docs-only design rules for a possible future doctrine / contract registry. It defines public/private/phase-local/internal classification boundaries, required future policy areas, accepted-shape policy, duplicate-key policy, unknown-field policy, canonicalization/witness policy, issue-code stability, fixture expectations, migration policy, and non-authority preservation before any registry implementation exists. It adds no schemas, registry files, JSON schema files, parser/composer/schema behavior, accepted-shape broadening, public API declaration, CLI command, adapter route, live route, runtime, process construction, Home Manager/Nix invocation, provider/cloud behavior, witness/evidence/DSSE/verifier/Phase 5 semantic change, mutation, compliance claim, attestation claim, production/live-readiness claim, future implementation approval, or authority. - Phase 24B contract registry index-shape pre-review:
docs/phases/phase24b-contract-registry-index-shape-pre-review.mdadds docs-only index-row shape rules for a possible future doctrine / contract registry index before any index exists. It defines mandatory future row fields, field semantics, design-only vocabulary, forbidden fields, safe documentation-only examples, rejected row examples, and a future review checklist. It adds no registry files, no index files, no JSON files, no JSON schema files, no machine-readable registry, no machine-readable index, no parser/composer/schema behavior, no accepted-shape broadening, no public API declaration, no CLI command, no adapter route, no live route, no runtime, no process construction, no Home Manager/Nix invocation, no provider/cloud behavior, no witness/evidence/DSSE/verifier/Phase 5 semantic change, no mutation, no compliance/conformance/certification/attestation claim, no production/live-readiness claim, no future implementation approval, and no authority. - Phase 24C contract registry index ADR:
docs/adr/0008-contract-registry-index-is-non-authority-classification.mdanddocs/phases/phase24c-contract-registry-index-adr.mdadd docs-only ADR material recording that any future doctrine / contract registry index is a non-authorizing classification/navigation layer only. It creates no registry, index, schema, machine-readable registry, machine-readable index, public API, runtime, route, parser/composer/schema behavior, accepted-shape broadening, Home Manager/Nix invocation, provider/cloud behavior, witness/evidence/DSSE/ verifier/Phase 5 semantic change, future implementation approval, or authority. - Phase 24D public/private contract policy checklist:
docs/phases/phase24d-public-private-contract-policy-checklist.mdadds docs-only public/private/phase-local classification checklist material before any registry/index/schema work. It creates no registry, index, schema, machine-readable registry/index, public API, parser/composer/schema behavior, accepted-shape broadening, runtime, route, Home Manager/Nix invocation, provider/cloud behavior, witness/evidence/DSSE/verifier/Phase 5 semantic change, future implementation approval, or authority. - Phase 24E issue-code stability audit:
docs/phases/phase24e-issue-code-stability-audit.mdadds docs-only issue-code stability audit material before any registry/index/schema work. It creates no issue-code behavior change, no issue-code rename, no issue-code stabilization by listing, no registry, no index, no schema, no machine-readable registry/index, no public API, no parser/composer/schema behavior, no accepted-shape broadening, no runtime, no route, no Home Manager/Nix invocation, no provider/cloud behavior, no witness/evidence/DSSE/ verifier/Phase 5 semantic change, no future implementation approval, and no authority. - Phase 24F fixture/golden classification audit:
docs/phases/phase24f-fixture-golden-classification-audit.mdadds docs-only fixture/golden classification audit material before any registry/index/schema work. It creates no fixture/golden behavior change, no fixture/golden rename, no fixture/golden stabilization by listing, no registry, no index, no schema, no machine-readable registry/index, no public API, no parser/composer/schema behavior, no verifier behavior change, no issue-code behavior change, no accepted-shape broadening, no runtime, no route, no Home Manager/Nix invocation, no provider/cloud behavior, no witness/evidence/DSSE/verifier/ Phase 5 semantic change, no future implementation approval, and no authority. - Phase 24G future index review checklist:
docs/phases/phase24g-future-index-review-checklist.mdadds docs-only future index review checklist material before any registry/index/schema work. It creates no registry/index/schema/machine-readable material, no rows, no row examples, no row vocabulary migration, no public API, no parser/composer/ schema behavior, no verifier behavior change, no fixture/golden behavior change, no issue-code behavior change, no accepted-shape broadening, no runtime, no route, no Home Manager/Nix invocation, no provider/cloud behavior, no witness/evidence/DSSE/verifier/Phase 5 semantic change, no future implementation approval, and no authority. - Phase 24H row vocabulary refinement:
docs/phases/phase24h-row-vocabulary-refinement.mdadds docs-only row vocabulary refinement that reconciles the Phase 24B row-shape vocabulary, Phase 24D public/private/phase-local labels, Phase 24E issue-code stability labels, Phase 24F fixture/golden labels, and Phase 24G review-mode/reviewer outcome vocabulary. It adds no registry/index/schema rows or files, no machine-readable material, no row examples, no public API/plugin ABI, no accepted-shape/parser/verifier/issue-code/fixture/golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no Phase 5/witness/DSSE semantic change, no implementation approval, and no future authority. - Phase 24I closeout synthesis map:
docs/phases/phase24i-phase24-closeout-synthesis-map.mdadds docs-only Phase 24 closeout/synthesis material that summarizes Phase 24A-H as a design wall around possible future registry/index/schema work. It adds no registry/ index/schema rows or files, no machine-readable material, no row examples, no public API/plugin ABI, no accepted-shape/parser/verifier/issue-code/fixture/ golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no Phase 5/witness/DSSE semantic change, no implementation approval, and no future authority. - Phase 25A post-Phase-24 readiness audit:
docs/phases/phase25a-post-phase24-readiness-audit.mdadds docs-only post-Phase-24 readiness audit and next-workstream selection material. It recommends a safe next workstream but implements none. It adds no registry/ index/schema rows or files, no machine-readable material, no row examples, no public API/plugin ABI, no accepted-shape/parser/verifier/issue-code/fixture/ golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no Phase 5/witness/DSSE semantic change, no implementation approval, and no future authority. - Phase 25B docs/status/navigation consolidation audit:
docs/phases/phase25b-docs-status-navigation-consolidation-audit.mdadds docs-only docs/status/navigation consolidation audit material. It audits current-facing navigation/status coherence and recommends narrow future cleanup only if needed. It implements no cleanup beyond the scoped status/navigation entries in this PR. It adds no registry/index/schema rows or files, no machine-readable material, no row examples, no public API/plugin ABI, no accepted-shape/parser/verifier/issue-code/fixture/golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no Phase 5/witness/DSSE semantic change, no implementation approval, and no future authority. - Phase 25C authority-boundary hostile wording audit:
docs/phases/phase25c-authority-boundary-hostile-wording-audit.mdadds docs-only authority-boundary hostile wording audit material. It searches current-facing docs for wording that could imply execution, disclosure, adapter routing, provider behavior, mutation, build/switch/apply, cleanup, rollback, public API, accepted-shape migration, evidence/witness/DSSE trust, compliance, production trust, implementation approval, or authority by docs/ checks/reports/fixtures/goldens. It implements no cleanup unless explicitly scoped in this PR. It adds no registry/index/schema rows or files, no machine-readable material, no row examples, no public API/plugin ABI, no accepted-shape/parser/verifier/issue-code/fixture/golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no Phase 5/witness/DSSE semantic change, no implementation approval, and no future authority. - Phase 25D implementation-readiness pre-review template:
docs/phases/phase25d-implementation-readiness-pre-review-template.mdadds docs-only implementation-readiness pre-review template material. It defines required questions and checklist sections for future implementation-adjacent proposals. It does not choose, approve, or implement any future proposal, and completing the template in a future PR will not itself authorize implementation. It adds no registry/index/schema rows or files, no machine-readable material, no row examples, no public API/plugin ABI, no accepted-shape/parser/verifier/issue-code/fixture/golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no Phase 5/witness/DSSE semantic change, no implementation approval, and no future authority. - Phase 25E first implementation-candidate selection audit:
docs/phases/phase25e-first-implementation-candidate-selection-audit.mdadds docs-only first implementation-candidate selection audit material. It compares candidate implementation-adjacent workstreams using Phase 25D as a rubric and selects a candidate for later Phase 26A pre-review only. It does not create Phase 26A, approve Phase 26A, or implement anything. Selection does not authorize implementation. It adds no registry/index/schema rows or files, no machine-readable material, no row examples, no public API/plugin ABI, no accepted-shape/parser/verifier/issue-code/fixture/golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no Phase 5/witness/DSSE semantic change, no implementation approval, and no future authority. - Phase 26A authority trace viewer pre-review:
docs/phases/phase26a-authority-trace-viewer-pre-review.mdadds docs-only authority trace viewer pre-review material. It pre-reviews a possible future human-facing, read-only viewer over existing authority/evidence/witness/report concepts. It does not implement a viewer, UI, TUI, web UI, CLI, renderer, report parser, schema, route, runtime, public API, plugin ABI, machine-readable contract, or authority. It does not create Phase 26B or approve implementation. It adds no registry/index/schema rows or files, no machine-readable material, no row examples, no public API/plugin ABI, no accepted-shape/parser/verifier/issue-code/fixture/golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no Phase 5/witness/DSSE semantic change, no implementation approval, and no future authority. - Phase 26B authority trace viewer readiness packet:
docs/phases/phase26b-authority-trace-viewer-readiness-packet.mdadds docs-only authority trace viewer implementation-readiness packet material. It fills out readiness questions for a possible future tiny authority trace viewer implementation. It does not implement a viewer, UI, TUI, web UI, CLI, renderer, parser, schema, route, runtime, public API, plugin ABI, machine-readable contract, or authority. It does not create Phase 26C or approve implementation. Packet completion does not authorize implementation. It adds no registry/index/schema rows or files, no machine-readable material, no row examples, no public API/plugin ABI, no accepted-shape/parser/verifier/ issue-code/fixture/golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no Phase 5/witness/DSSE semantic change, no implementation approval, and no future authority. - Phase 26C authority trace source-of-truth map:
docs/phases/phase26c-authority-trace-source-of-truth-map.mdadds docs-only authority trace source-of-truth map material. It maps current source-of-truth boundaries for possible later authority trace inspection. It does not implement a viewer, UI, TUI, web UI, CLI, renderer, parser, schema, route, runtime, public API, plugin ABI, machine-readable contract, or authority. It does not create Phase 26D or approve implementation. Mapping concepts does not authorize implementation or make them accepted viewer input. It adds no registry/index/schema rows or files, no machine-readable material, no row examples, no public API/plugin ABI, no accepted-shape/parser/verifier/ issue-code/fixture/golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no Phase 5/witness/DSSE semantic change, no implementation approval, and no future authority. - Phase 26D doc-link-only authority trace navigator pre-review:
docs/phases/phase26d-doc-link-only-authority-trace-navigator-pre-review.mdadds docs-only doc-link-only authority trace navigator pre-review material. It pre-reviews whether a possible future tiny navigator can be limited to exact current-facing doc links. It does not implement a navigator, viewer, UI, TUI, web UI, CLI, renderer, parser, schema, route, runtime, report parser, artifact parser, machine-readable contract, public API/plugin ABI, accepted viewer input, or authority. It does not create Phase 26E or approve implementation. Candidate links remain navigation only and do not become accepted viewer input, stable output/API, source of truth, or implementation approval. It adds no registry/index/schema rows or files, no machine-readable material, no row examples, no accepted-shape/parser/composer/verifier/ issue-code/fixture/golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no Phase 5/witness/DSSE semantic change, no process construction, noCommand::new, no output capture, no timeout/kill/reap/drain behavior, no result-link/result-path touching, no mutation, no implementation approval, and no future authority. - Phase 26E tiny doc-link-only authority trace navigator implementation
pre-review:
docs/phases/phase26e-tiny-doc-link-only-authority-trace-navigator-implementation-pre-review.mdadds docs-only tiny doc-link-only authority trace navigator implementation pre-review material. It selects a possible future Phase 26F static markdown navigator page as the only bounded implementation shape and rejects CLI, code-table, parser, schema, route, runtime, public API/plugin ABI, and machine-readable shapes. It does not createdocs/authority-trace-navigator.mdand does not implement a navigator, viewer, UI, TUI, web UI, CLI, renderer, parser, schema, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, machine-readable contract, public API/plugin ABI, accepted viewer input, or authority. It does not create Phase 26F or directly approve implementation. It adds no registry/index/schema rows or files, no machine-readable material, no row examples, no accepted-shape/parser/composer/verifier/issue-code/ fixture/golden behavior change, no runtime authority, no Home Manager/Nix behavior, no provider/cloud behavior, no raw-context exposure, no Phase 5/witness/DSSE semantic change, no process construction, noCommand::new, no output capture, no timeout/kill/reap/drain behavior, no result-link/ result-path touching, no mutation, no implementation approval, and no future authority. - Phase 26F static doc-link-only authority trace navigator page:
docs/authority-trace-navigator.mdadds a static markdown human navigation page that links only to existing current-facing docs and the Phase 24I/25D/25E/26A/26B/26C/26D/26E authority trace trail. It is static human navigation only. Links remain navigation only and do not make linked docs accepted viewer input, accepted machine input, source-of-truth upgrades, stable output/API, registry rows, schema rows, route rows, capability rows, implementation approval, proof, trust material, or authority. Phase 26F adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, public API/plugin ABI, machine-readable contract, accepted viewer input, accepted-shape/parser/composer/verifier/ issue-code/fixture/golden behavior change, provider/cloud behavior, raw host context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, process construction,Command::new, output capture, timeout/kill/ reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval beyond the exact static docs page, or future authority. - Phase 26G authority trace navigator hostile wording regression audit:
docs/phases/phase26g-authority-trace-navigator-hostile-wording-regression-audit.mdadds docs-only hostile wording / regression audit material for the landed static authority trace navigator page and its status/navigation entries. It auditsdocs/authority-trace-navigator.md,docs/start-here.md, anddocs/implementation-status.mdagainst the Phase 26E/26F boundaries and records no P0/P1/P2 drift. It recommends a later docs-only Phase 27A next-workstream selection audit but does not create it. Phase 26G adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, public API/plugin ABI, machine-readable contract, accepted viewer input, accepted input, accepted-shape/parser/composer/verifier/issue-code/fixture/golden behavior change, provider/cloud behavior, raw host context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, process construction,Command::new, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, or future authority. - Phase 27A post-static-navigator next implementation-candidate selection
audit:
docs/phases/phase27a-post-static-navigator-next-implementation-candidate-selection-audit.mdadds docs-only next-workstream selection audit material after the Phase 26F/26G static navigator closeout. It compares plausible next workstreams and selects a later docs-only Phase 27B privacy / redacted context-pack boundary audit as the next recommended phase, without creating Phase 27B. Phase 27A adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, context-pack format, redactor, exporter, provider/cloud behavior, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted input, accepted-shape/parser/composer/verifier/issue-code/fixture/ golden behavior change, process construction,Command::new, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/certification/attestation/production trust/ live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 27B creation, or future authority. Links and candidate selection remain navigation/audit material only and authorize nothing by existence. - Phase 27B privacy / redacted context-pack boundary audit:
docs/phases/phase27b-privacy-redacted-context-pack-boundary-audit.mdadds docs-only privacy/raw-context/provider/cloud boundary audit material before any context-pack format exists. It classifies forbidden-by-default raw host context, records local-only and provider/cloud exclusion boundaries, introduces reviewer-only refusal vocabulary, and recommends a later docs-only Phase 27C redacted context-pack requirements pre-review without creating Phase 27C. Phase 27B adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, context-pack format, context-pack example, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted input, accepted-shape/parser/composer/verifier/ issue-code/fixture/golden behavior change, process construction,Command::new, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/ certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 27C creation, or future authority. The audit, its refusal vocabulary, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 27C redacted context-pack requirements pre-review:
docs/phases/phase27c-redacted-context-pack-requirements-pre-review.mdadds docs-only prose requirements pre-review material for any future redacted context-pack concept before any format is considered. It records minimization, redaction, provenance, hostile-text labelling, operator approval, local-only handling, provider/cloud exclusion, cloud/provider output limits, and authority-separation requirements; carries forward Phase 27B reviewer-only refusal vocabulary; and recommends a later docs-only Phase 27D hostile wording audit without creating Phase 27D. Phase 27C adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, context-pack format, context-pack schema, context-pack example, accepted context-pack input, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted input, accepted-shape/parser/ composer/verifier/issue-code/fixture/golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/ conformance/certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 27D creation, or future authority. The pre-review, its refusal vocabulary, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 27D redacted context-pack requirements hostile wording audit:
docs/phases/phase27d-redacted-context-pack-requirements-hostile-wording-audit.mdadds docs-only hostile wording audit material for the landed Phase 27C requirements pre-review. It records no P0/P1/P2 drift, no blocking P3 drift, and confirms Phase 27C remained prose-only, non-format, and non-authorizing. Phase 27D recommends a later docs-only Phase 27E format-readiness decision audit without creating Phase 27E. Phase 27D adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, context-pack format, context-pack schema, context-pack example, accepted context-pack input, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted input, accepted-shape/parser/composer/verifier/ issue-code/fixture/golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/ certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 27E creation, or future authority. The audit, its findings, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 27E context-pack format-readiness decision audit:
docs/phases/phase27e-context-pack-format-readiness-decision-audit.mdadds docs-only readiness decision audit material for whether the Phase 27B/27C/27D privacy/refusal foundation is clean enough to consider a later docs-only format pre-review constraints phase. It selects Outcome A narrowly, recommends a later docs-only Phase 27F context-pack format pre-review constraints packet, and does not create Phase 27F. Phase 27E adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, context-pack format, context-pack schema, context-pack example, accepted context-pack input, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted input, accepted-shape/parser/ composer/verifier/issue-code/fixture/golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/ conformance/certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 27F creation, or future authority. The audit, its selected outcome, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 27F context-pack format pre-review constraints packet:
docs/phases/phase27f-context-pack-format-pre-review-constraints-packet.mdadds docs-only constraints material for any later format-description pre-review. It defines the raw-context, no-example, no-schema/no-field-list, provider/cloud, redactor/exporter, no-authority, reviewer-only vocabulary, and stop-condition constraints a later Phase 27G would have to obey. It selects Outcome A narrowly, recommends a later docs-only Phase 27G context-pack format description pre-review, and does not create Phase 27G. Phase 27F adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, context-pack format, context-pack schema, context-pack example, accepted context-pack input, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted input, accepted-shape/parser/composer/verifier/issue-code/fixture/ golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/certification/attestation/production trust/ live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 27G creation, or future authority. The packet, its selected outcome, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 27G context-pack format description pre-review:
docs/phases/phase27g-context-pack-format-description-pre-review.mdadds docs-only description pre-review material for whether any tiny non-accepted, non-machine-readable, non-authorizing context-pack shape description can be safely considered. It selects Outcome A narrowly, recommends a later docs-only Phase 27H context-pack non-accepted shape description pre-review, and does not create Phase 27H. Phase 27G itself describes no shape and adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, context-pack format, context-pack schema, context-pack example, accepted context-pack input, stable context-pack output, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted input, accepted-shape/parser/composer/verifier/issue-code/fixture/ golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/certification/attestation/production trust/ live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 27H creation, or future authority. The pre-review, its selected outcome, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 27H context-pack non-accepted shape description pre-review:
docs/phases/phase27h-context-pack-non-accepted-shape-description-pre-review.mdadds docs-only pre-review material for whether any non-accepted human context-pack shape description can be safely written now. It selects Outcome B, requires more constraints/remediation audit before any shape description is attempted, recommends a later docs-only Phase 27I context-pack shape-description constraints remediation audit, and does not create Phase 27I. Phase 27H itself describes no shape and adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, context-pack format, context-pack schema, context-pack example, accepted context-pack input, stable context-pack output, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted input, accepted-shape/parser/composer/verifier/issue-code/fixture/golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 27I creation, or future authority. The pre-review, its selected outcome, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 27I context-pack shape-description constraints remediation audit:
docs/phases/phase27i-context-pack-shape-description-constraints-remediation-audit.mdadds docs-only remediation audit material for the field-list/schema/ accepted-input/example/provider-cloud/raw-context/reviewer-vocabulary/ implementation-readiness hazards Phase 27H preserved before any shape-description attempt. It selects Outcome B, requires a later closeout audit before any shape description is attempted, recommends a later docs-only Phase 27J context-pack shape-description remediation closeout audit, and does not create Phase 27J. Phase 27I itself describes no shape and adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, context-pack format, context-pack schema, context-pack example, accepted context-pack input, stable context-pack output, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted input, accepted-shape/parser/composer/verifier/issue-code/fixture/ golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/certification/attestation/production trust/ live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 27J creation, or future authority. It also corrects one current-facing identity phrase in the static authority trace navigator from governance-kernel wording to the governed-execution-harness formulation. The audit, its selected outcome, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 27J context-pack shape-description remediation closeout audit:
docs/phases/phase27j-context-pack-shape-description-remediation-closeout-audit.mdadds docs-only closeout audit material for the unresolved Phase 27H/27I field-list/schema/accepted-input/example/provider-cloud/raw-context/ reviewer-vocabulary/implementation-readiness hazards. It selects Outcome A, closes/defers the current context-pack shape-description lane, recommends a later docs-only Phase 28A post-context-pack-lane next workstream selection audit, and does not create Phase 28A. Phase 27J itself describes no shape and adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, context-pack format, context-pack schema, context-pack example, accepted context-pack input, stable context-pack output, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted input, accepted-shape/parser/composer/verifier/ issue-code/fixture/golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/ certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 28A creation, or future authority. The closeout audit, its selected outcome, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 28A post-context-pack-lane next workstream selection audit:
docs/phases/phase28a-post-context-pack-lane-next-workstream-selection-audit.mdadds docs-only next-workstream selection audit material after Phase 27J closed/deferred the context-pack shape-description lane. It carries forward Phase 27 privacy/refusal doctrine as human review guidance only, compares lower-risk workstreams, selects Candidate A for a later docs-only Phase 28B command-matrix / current-authority-boundary drift audit, and does not create Phase 28B. Phase 28A itself adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, command behavior change, accepted input, issue-code behavior, context-pack format, context-pack schema, context-pack example, accepted context-pack input, stable context-pack output, machine-readable context-pack shape, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted-shape/parser/composer/verifier/fixture/golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 28B creation, or future authority. The selection audit, its selected workstream, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 28B command-matrix / current-authority-boundary drift audit:
docs/phases/phase28b-command-matrix-current-authority-boundary-drift-audit.mdadds docs-only hostile drift audit material for current-facing command/status/ authority-boundary docs after Phase 26, Phase 27, and Phase 28A. It records no P0/P1/P2 drift, confirms thatdocs/command-matrix.md,docs/current-authority-boundary.md,docs/implementation-status.md,docs/start-here.md,README.md, andAGENTS.mdremain aligned for Phase 28B purposes, and recommends a later docs-only Phase 28C non-authorizing adapter-readiness template selection audit without creating Phase 28C. Phase 28B itself adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, command behavior change, accepted input, issue-code behavior, context-pack format, context-pack schema, context-pack example, accepted context-pack input, stable context-pack output, machine-readable context-pack shape, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted-shape/parser/composer/verifier/fixture/golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 28C creation, or future authority. The audit, its findings table, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 28C non-authorizing adapter-readiness template selection audit:
docs/phases/phase28c-non-authorizing-adapter-readiness-template-selection-audit.mdadds docs-only selection audit material for the next adapter-readiness lane after Phase 28B found no command-boundary remediation need. It compares a generic non-authorizing adapter-readiness template pre-review against privacy/refusal vocabulary mapping, Home Manager adapter-readiness, MCP/local-agent gateway readiness, evidence/witness/verifier adapter-boundary audit, static navigation consolidation, and context-pack continuation candidates. It selects a later docs-only Phase 28D non-authorizing adapter-readiness template pre-review and does not create Phase 28D. Phase 28C itself adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, adapter-readiness template, adapter capability table, adapter registry, adapter manifest, command behavior change, accepted input, issue-code behavior, context-pack format, context-pack schema, context-pack example, accepted context-pack input, stable context-pack output, machine-readable context-pack shape, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted-shape/parser/composer/verifier/fixture/golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 28D creation, or future authority. The selection audit, its selected candidate, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 28D non-authorizing adapter-readiness template pre-review:
docs/phases/phase28d-non-authorizing-adapter-readiness-template-pre-review.mdadds docs-only pre-review material for whether a later non-authorizing adapter-readiness template can be safely created. It carries forward Phase 28C's selected Candidate A, Phase 28B's command-boundary no-remediation result, and Phase 27 privacy/refusal doctrine as human review guidance only. It selects Outcome A,template-pre-review-complete-template-next, and recommends a later docs-only Phase 28E non-authorizing adapter-readiness template while Phase 28D itself creates no final template and does not create Phase 28E. Phase 28D adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, final adapter-readiness template, adapter-readiness checklist as executable/accepted material, adapter capability table, adapter registry, adapter manifest, adapter route table, command behavior change, accepted input, issue-code behavior, context-pack format, context-pack schema, context-pack example, accepted context-pack input, stable context-pack output, machine-readable context-pack shape, context-pack fields, context-pack serialization, redactor, exporter, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, Home Manager/Nix behavior, Phase 5/witness/DSSE semantic change, machine-readable contract, public API/plugin ABI, accepted viewer input, accepted-shape/parser/composer/verifier/fixture/golden behavior change, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, compliance/conformance/certification/attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 28E creation, or future authority. The pre-review, its selected outcome, its verdict, its recommended next phase, links, local validation, CI success, review, and merge authorize nothing by existence. - Phase 28E non-authorizing adapter-readiness template:
docs/adapter-readiness-template.mdanddocs/phases/phase28e-non-authorizing-adapter-readiness-template.mdadd human-facing prose-only non-authorizing review guidance for future adapter proposal memos. The template is not a form, checklist, schema, manifest, registry row, route table, capability table, accepted input, stable output, issue-code vocabulary, public API, plugin ABI, provider payload, fixture, golden, verifier input, implementation approval, expansion approval, or authority source. Phase 28E adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, report parser, artifact parser, arbitrary report reader, arbitrary path reader, arbitrary repo file reader, adapter behavior, adapter approval, adapter capability table, adapter registry, adapter manifest, adapter route table, command behavior change, command matrix behavior change, accepted input, issue-code behavior, context-pack work, context-pack format/schema/fields/examples, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, raw-context handling, Home Manager/Nix behavior, Home Manager build-preflight behavior, Phase 5/witness/DSSE semantic change, verifier semantic change, machine-readable contract, public API/plugin ABI, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, mutation, disclosure, compliance/conformance/certification/ attestation/production trust/live readiness, source-of-truth upgrade, implementation approval, expansion approval, Phase 28F creation, or future authority. The template, its sections, its guidance, the Phase 28E phase doc, local validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 28F adapter-readiness template hostile wording / regression audit:
docs/phases/phase28f-adapter-readiness-template-hostile-wording-regression-audit.mdrecords a docs-only hostile wording / regression audit ofdocs/adapter-readiness-template.md, the Phase 28E phase document, and the Phase 28E status/navigation entries. It found no P0/P1/P2 drift in the landed adapter-readiness template lane and recommends a later docs-only Phase 28G post-adapter-readiness-template next workstream selection audit. Phase 28F adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, public API/plugin ABI, machine-readable rows/examples, accepted input, stable output, issue-code behavior, command behavior change, command matrix behavior change, context-pack work, context-pack format/schema/fields/examples, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, raw-context handling, Home Manager/Nix behavior, Home Manager build-preflight behavior, Phase 5/witness/DSSE semantic change, verifier semantic change, source-of-truth upgrade, implementation approval, expansion approval, Phase 28G creation, or future authority. The audit, findings, verdict, recommended next phase, links, local validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 28G post-adapter-readiness-template next workstream selection audit:
docs/phases/phase28g-post-adapter-readiness-template-next-workstream-selection-audit.mdrecords a docs-only next-workstream selection audit after the clean Phase 28F template audit and recommends a later docs-only Phase 28H Home Manager tiny live-read candidate selection audit. Phase 28G itself adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, public API/plugin ABI, machine-readable rows/examples, accepted input, stable output, issue-code behavior, command behavior change, command matrix behavior change, context-pack work, context-pack format/schema/fields/examples, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, raw-context handling, Home Manager/Nix behavior, Home Manager build-preflight behavior, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, build/switch/apply behavior, mutation, disclosure, Phase 5/witness/DSSE semantic change, verifier semantic change, source-of-truth upgrade, implementation approval, expansion approval, Phase 28H creation, or future authority. The audit, candidate labels, selected candidate, verdict, recommended next phase, links, local validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 28H Home Manager tiny live-read candidate selection audit:
docs/phases/phase28h-home-manager-tiny-live-read-candidate-selection-audit.mdrecords docs-only candidate selection material for a possible tiny Home Manager read-only observation pre-review after Phase 28G. It selects a later docs-only Phase 28I Home Manager version-family hardening implementation pre-review and does not create Phase 28I. Phase 28H adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, public API/plugin ABI, machine-readable rows/examples, accepted input, stable output, issue-code behavior, command behavior change, command matrix behavior change, context-pack work, context-pack format/schema/fields/examples, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, raw-context handling, Home Manager/Nix behavior, Home Manager build-preflight behavior, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, build/switch/apply behavior, rollback, cleanup, mutation, disclosure, Phase 5/witness/DSSE semantic change, verifier semantic change, source-of-truth upgrade, implementation approval, expansion approval, Phase 28I creation, or future authority. The audit, candidate labels, selected candidate, verdict, recommended next phase, links, local validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 28I Home Manager version-family hardening implementation pre-review:
docs/phases/phase28i-home-manager-version-family-hardening-implementation-pre-review.mdrecords docs-only implementation pre-review material for the selected Home Manager version-family hardening candidate after Phase 28H. Verdict:version-family-hardening-pre-review-complete-implementation-next. It recommends a later separately created Phase 28J Home Manager version-family hardening implementation only under strict guardrails, while Phase 28I itself adds no code, tests, CLI, UI, TUI, web UI, renderer, parser, schema, registry, index, route, runtime, public API/plugin ABI, machine-readable rows/examples, accepted input, stable output, issue-code behavior, command behavior change, command matrix behavior change, context-pack work, context-pack format/schema/fields/examples, provider/cloud behavior, provider/cloud configuration, provider/cloud opt-in UX, provider payload, raw-context inspection, raw-context handling, Home Manager/Nix behavior, Home Manager build-preflight behavior, process construction,Command::newusage, output capture, timeout/kill/reap/drain behavior, result-link/result-path behavior, build/switch/apply behavior, rollback, cleanup, mutation, disclosure, Phase 5/witness/DSSE semantic change, verifier semantic change, source-of-truth upgrade, implementation approval, expansion approval, Phase 28J creation, or future authority. The pre-review, candidate label, verdict, recommended next phase, links, local validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 28J Home Manager version-family hardening implementation:
docs/phases/phase28j-home-manager-version-family-hardening-implementation.mdrecords minimal implementation hardening after Phase 28I. Phase 28J adds in-memory parser regression tests incrates/cog-model/src/home_manager_version_observe.rsfor command-template broadening, argv-template broadening, and runtime/approval/trust-sounding status labels. The hardening preserves the existing fixedhome-manager --versionobserve boundary: exact argv remains the operator executable placeholder plus--version, no shell/PATH/which behavior is added, no inherited environment is added, no raw stdout/stderr/path/cwd persistence is added, no provider/cloud or model-visible context behavior is added, and no Home Manager build-preflight, build/switch/apply, rollback/cleanup, result-link/result-path, generic process runner, route, schema, registry, capability, public API, plugin ABI, accepted input, context-pack, Phase 5/witness/DSSE semantic, mutation, production trust, compliance/conformance/certification/attestation, implementation approval beyond the landed narrow hardening patch, expansion approval, Phase 28K creation, or future authority is added. Phase 28J, the hardening tests, docs, validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 28K Home Manager version-family hardening hostile regression audit:
docs/phases/phase28k-home-manager-version-family-hardening-hostile-regression-audit.mdrecords a docs-only hostile regression audit of the merged Phase 28J hardening. Verdict:version-family-hardening-hostile-audit-clean. The audit found no P0/P1/P2 drift in Phase 28J's test-only Home Manager version-family hardening and records that exacthome-manager --versionremains the only accepted command template. Phase 28K adds no code, tests, CLI, route, parser, schema, registry, capability, accepted input, command behavior change, provider/cloud behavior, raw-context inspection, Home Manager/Nix behavior, Home Manager build-preflight behavior, build/switch/apply, rollback, cleanup, result-link/result-path behavior, generic process runner, context-pack work, Phase 5/witness/DSSE semantic change, implementation approval, expansion approval, Phase 28L creation, or future authority. Phase 28K, the audit, findings, verdict, recommended next phase, links, local validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 28L post-version-family-hardening next workstream selection audit:
docs/phases/phase28l-post-version-family-hardening-next-workstream-selection-audit.mdrecords a docs-only selection audit after the clean Phase 28J/28K version-family hardening cycle. Selected candidate: Candidate C - broader Home Manager observe-lane audit. Verdict:post-version-hardening-selection-complete-observe-lane-audit-next. Phase 28L recommends a later docs-only Phase 28M Home Manager observe-lane post-hardening boundary audit before selecting another implementation candidate. Phase 28L adds no code, tests, CLI, route, parser, schema, registry, capability, accepted input, command behavior change, provider/cloud behavior, raw-context inspection, Home Manager/Nix behavior, Home Manager build-preflight behavior, build/switch/apply, rollback, cleanup, result-link/result-path behavior, generic process runner, context-pack work, Phase 5/witness/DSSE semantic change, implementation approval, expansion approval, Phase 28M creation, or future authority. Phase 28L, the audit, candidate labels, selected candidate, verdict, recommended next phase, links, local validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 28M Home Manager observe-lane post-hardening boundary audit:
docs/phases/phase28m-home-manager-observe-lane-post-hardening-boundary-audit.mdrecords a docs-only audit of the Home Manager observe/read-only lane after Phase 28J/28K/28L. It checked Phase 17C.3 fixed version observe, Phase 17C.7 fixed generations observe, Phase 17C.8 observe hardening, build-preflight separation, current authority/status/navigation wording, and authority-by-existence risks. Selected outcome and verdict: Outcome B -observe-lane-audit-clean-generations-family-pre-review-next. It recommends a later docs-only Phase 28N Home Manager generations-family hardening implementation-boundary pre-review without creating that phase. If clean, Phase 28N should lead to one narrow Tier 1 implementation PR with a PR-body hostile audit, not another standalone selection phase. Phase 28M adds no code, tests, CLI, route, parser, schema, registry, capability, accepted input, command behavior change, provider/cloud behavior, raw-context inspection, Home Manager/Nix behavior, Home Manager build-preflight behavior, build/switch/apply, rollback, cleanup, result-link/result-path behavior, generic process runner, context-pack work, Phase 5/witness/DSSE semantic change, implementation approval, expansion approval, Phase 28N creation, or future authority. Phase 28M, the audit, findings, selected outcome, verdict, recommended next phase, links, local validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 28N Home Manager generations-family hardening implementation-boundary
pre-review:
docs/phases/phase28n-home-manager-generations-family-hardening-implementation-boundary-pre-review.mdrecords a short docs-only go/no-go pre-review after clean Phase 28M. Selected outcome: Outcome A -generations-hardening-pre-review-clean-tier1-implementation-next. It recommends Phase 28O - Home Manager generations-family parser/redaction hardening implementation - as one narrow Tier 1 implementation PR with a PR-body hostile audit rather than another standalone selection phase. Phase 28N adds no code, tests, CLI, route, parser, schema, accepted input, command behavior change, provider/cloud behavior, raw-context inspection, Home Manager/Nix behavior, Home Manager build-preflight behavior, build/switch/ apply, rollback, cleanup, result-link/result-path behavior, generic process runner, context-pack work, Phase 5/witness/DSSE semantic change, implementation approval by existence, expansion approval, or future authority. Phase 28N, the pre-review, findings, selected outcome, recommended next PR, links, local validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 28O Home Manager generations-family parser/redaction hardening
implementation:
docs/phases/phase28o-home-manager-generations-family-parser-redaction-hardening-implementation.mdrecords one narrow Tier 1 implementation after clean Phase 28N. Implementation type: tests-only parser/redaction/refusal/report-invariant hardening inside the existing Phase 17C.7 fixedhome-manager generationsobserve boundary. Files/modules touched:crates/cog-model/src/home_manager_generations_observe.rs,crates/cog-cli/src/commands/adapter.rs,docs/phases/phase28o-home-manager-generations-family-parser-redaction-hardening-implementation.md,docs/start-here.md, and this status file. Hardening categories added: descriptor command-template drift, argv-template drift, runtime/approval/ trust/live-readiness status labels, hostile synthetic raw stdout material for home/profile/store/user/host/flake/freeform fragments, parser refusal no-raw-fragment echo checks, and existing report invariants for no raw username/hostname/sensitive/raw-context/model-visible context persistence. No code fix was needed. Phase 28O adds no new route, CLI grammar change, command behavior broadening, accepted-input broadening, schema/report-shape change, output artifact name change, process/argv/env/timeout/capture broadening, provider/cloud behavior, raw-context behavior, Home Manager build-preflight behavior, build/switch/apply, rollback, cleanup, result-link/result-path behavior, generic process runner, mutation, witness/evidence/DSSE/verifier/ Phase 5 semantic change, trust/compliance/conformance/certification/ attestation/live-readiness claim, or future authority. Phase 28O, its tests, hardening, docs, hostile audit, validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 29A demo visual mutation lane design:
docs/phases/phase29a-demo-visual-mutation-lane-design.mdrecords a short docs-only design packet for a futuredemo.visual_cosmetic_mutationlane. It separates the future visual demo path from Home Manager/Nix/build/switch/apply, keeps user input entering the Deadbolt TUI rather than Hermes, treats Hermes/local planner output as planner material only, names candidate Hyprland cosmetic endpoints for later implementation-boundary review, recommendsretro_1995.applyfirst as a fake/file-backed transform, and points to Phase 29B for typed style-plan grammar / safe primitive vocabulary. Phase 29A adds no code, tests, CLI, route, parser, schema, accepted input, fixture, golden, command-matrix row, command behavior, runtime behavior, real mutation, Hermes/provider authority, provider/cloud behavior, raw-context handling, Home Manager/Nix behavior, build/switch/apply, rollback/cleanup, result-link/result-path behavior, generic process runner, production/trust/compliance/conformance/ certification/attestation/live-readiness claim, implementation approval, or future authority. Phase 29A, its design, candidate endpoint names, upstream links, docs/status/navigation entries, validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 29B typed style-plan grammar vocabulary:
docs/phases/phase29b-typed-style-plan-grammar-vocabulary.mdrecords a docs-only human-readable grammar/vocabulary packet for the future visual demo lane. It definesretro_1995,retro_1995.apply, thedemo.visual_cosmetic_mutationtarget class, future style-plan field vocabulary, fake/file-backed primitive labels, Hermes/local-planner boundaries, static no-model phrase-mapping intent, and Phase 29C as the next fake/file-backed retro transform + receipt/rollback candidate. Phase 29B also performs surface display-title polish: Deadbolt Permission Engine is display/product title language only, and the current GitHub repository slug remainsdeadbolt. Phase 29B adds no code, tests, CLI, route, parser, Rust type, schema, accepted input, fixture, golden, command-matrix row, command behavior, runtime behavior, real mutation, Hermes/provider authority, provider/cloud behavior, raw-context handling, Home Manager/Nix behavior, build/switch/apply, rollback/cleanup, result-link/result-path behavior, generic process runner, production/trust/compliance/conformance/ certification/attestation/live-readiness claim, implementation approval, or future authority. Phase 29B, its examples, vocabulary labels, docs/status/navigation entries, validation, CI success, review, merge, and existence authorize nothing by existence. - Phase 29C fake retro style transform:
docs/phases/phase29c-fake-retro-style-transform.mdimplements exactly one fake/file-backed macro-action,retro_1995.apply, throughmutate fake-retro-style. Dry-run writesretro_style_request.json,retro_style_compile_report.json,retro_style_dry_run_report.json, andretro_style_rollback_plan.jsonwithout changingfake_retro_style_state.json. Commit requires the matching dry-run plan and a signedmutation.demo.retro_1995.applylease bound toretro_1995.apply:fake_visual_state:<run-id>:<dry-run-plan-hash>plus the shared logical run directory before writing only the fake state, policy, lease, and execution receipt artifacts. Rollback restores only the fake state file and writesretro_style_rollback_receipt.json.verify mutation-fake-retro --run <dir>checks internal fake-retro consistency only. Phase 29C adds no real Hyprland mutation, nohyprctl, no Home Manager/Nix behavior, no build/switch/apply, no Hermes/provider/cloud behavior, no raw-context handling, no screenshots/OCR, no clipboard, no browser/window/client/process inspection, no shell, no generic process runner, no arbitrary filesystem target, no dotfile/user config rewrite, no package install/remove, no witness/evidence/DSSE semantic change, no production/trust/compliance/conformance/certification/attestation/ live-readiness claim, and no authority by existence. - Phase 29D basic retro cockpit:
docs/phases/phase29d-basic-retro-cockpit.mdadds the scriptabledemo retro-cockpitfront door over the existing Phase 29C fake transform. It maps only four normalized exact phrases toretro_1995.apply, writes the fixedretro_cockpit_action.jsonaction artifact when needed, reuses Phase 29C dry-run/commit/rollback/verifier paths, requires explicit--confirmplus the existing exact fake-retro mutation lease before fake state commit, and rejects rollback planner/confirmation/lease flags. It mutates onlyfake_retro_style_state.jsonthrough the existing Phase 29C commit path. Phase 29D adds no Hermes/provider/cloud behavior, no raw-context handling, no real Hyprland mutation, nohyprctl, no Home Manager/Nix behavior, no build/switch/apply, no screenshots/OCR, no clipboard, no browser/window/client/process inspection, no shell, no generic process runner, no arbitrary natural-language authority, no arbitrary filesystem target, no witness/evidence/DSSE semantic change, no production/trust/ compliance/conformance/certification/attestation/live-readiness claim, and no authority by existence. - Phase 29D.1 fake-retro integrity hardening:
docs/phases/phase29d1-fake-retro-integrity-hardening.mdhardens the existing Phase 29C/29D fake-retro commit and verifier chain. It adds no new route, no new accepted input, no new macro-action, and no machine-readable public schema. Commit recomputes the expectedretro_1995.applyfake after-state from the compiled action before writingfake_retro_style_state.json. The verifier now fails closed when execution receipt pre/post state hashes do not link to dry-run and rollback-plan state hashes, adapter id/version are wrong, execution receipt errors are non-empty, or a rollback receipt exists without an execution receipt. Phase 29D.1 remains fake/file-backed only and adds no Hermes/provider/cloud behavior, no raw-context handling, no real Hyprland mutation, nohyprctl, no Home Manager/Nix/build/switch/apply, no shell/generic runner behavior, no arbitrary filesystem target, no production/trust/compliance/conformance/certification/attestation/live-readiness claim, and no authority by existence. - Phase 29E real Hyprland cosmetic mutation boundary pre-review:
docs/phases/phase29e-real-hyprland-cosmetic-mutation-boundary-pre-review.mdadds docs-only implementation-boundary review material for the first future real Hyprland runtime cosmetic mutation after the fake-retro lane. It recommends Outcome A: Phase 29F may be one narrow implementation PR for exactlydecoration:rounding, with dry-run snapshot, commit setting the value to0, minimized receipt, rollback restoring the exact previous runtime value, verifier, and hostile tests. Phase 29E adds no code, tests, CLI, route, parser, schema, accepted input, fixture, golden, command-matrix runnable row, runtime behavior, real mutation,hyprctlinvocation, Hermes/provider authority, provider/cloud behavior, raw-context handling, Home Manager/Nix behavior, build/switch/apply, shell/generic runner behavior, arbitrary natural-language authority, arbitrary filesystem target, production/trust/compliance/conformance/certification/attestation/ live-readiness claim, implementation approval, or future authority. Phase 29E existence authorizes nothing by existence. - Phase 29F real Hyprland rounding implementation:
docs/phases/phase29f-real-hyprland-rounding-implementation.mdadds the first real runtime cosmetic mutation route:mutate hyprland-cosmetic. The route accepts only dry-run, commit, rollback, and verify modes over one target,decoration:rounding. Dry-run executes onlygetoption decoration:rounding, parses one bounded integer, and writes minimized snapshot/dry-run/rollback-plan artifacts. Commit requires strict local consent config, explicit--confirm, exact policy, exact signedmutation.demo.hyprland_cosmetic.decoration_roundinglease bound tohyprland.cosmetic.decoration_rounding:<run-id>:<dry-run-plan-hash>, dry-run/config/run consistency, and an immediate current-value recheck before executing onlykeyword decoration:rounding 0; if the current value differs, it refuses before keyword. If the keyword call is attempted but its bounded output cannot be validated, the route writes only a minimized unverified rollback-capable attempt receipt and returns an error. Rollback now requires explicit--confirm, a complete chain, and a fresh exact lease recheck before executing onlykeyword decoration:rounding <previous-minimized-int>. The system executor uses an operator-provided absolutehyprctl_exe, exact argv, closed stdin, controlled cwd, bounded capture, timeout/kill/reap/drain behavior, and an env-cleared child with onlyXDG_RUNTIME_DIRandHYPRLAND_INSTANCE_SIGNATUREpassed after local checks. Reports and receipts persist no raw stdout, stderr, executable path, cwd, environment values, host/user/session identifiers, model/provider context, screenshots, clipboard, browser, window, client, or process material. Phase 29F adds no arbitrary Hyprland mutation, arbitraryhyprctl,hyprctl --batch,hyprctl notify, general gaps/borders/colors, generic Hyprland adapter, generic process runner, shell, inherited full environment, Hermes/provider/ cloud behavior, Home Manager/Nix/build/switch/apply, package/dotfile/config mutation, screenshot/OCR/clipboard/browser/window/client/process inspection, witness/evidence/DSSE semantic change, production/trust/compliance/ conformance/certification/attestation/live-readiness claim, or authority by existence. The verifier checks boundary booleans/redaction fields and does not call Hyprland or prove final live state. - Phase 29G Hyprland cosmetic manual smoke closeout:
docs/phases/phase29g-hyprland-cosmetic-smoke-closeout.mdrecords a docs/status/runbook-only closeout for the existing Phase 29F route. One operator manually smoke-passed the first real Hyprland cosmetic route on one local session: exact targetdecoration:rounding, observed live sequence18 -> 0 -> 18. Phase 29G adds no runtime behavior, no new endpoint, no second primitive, no arbitrary value support, no broad Hyprland mutation, no arbitraryhyprctl, no Hermes/provider/cloud behavior, no Home Manager/Nix/build/switch/apply behavior, no shell/generic runner behavior, no production/trust/compliance/conformance/certification/attestation/ live-readiness claim, and no authority by existence. The closeout records two manual runbook/UX findings: runningverify hyprland-cosmeticafter dry-run but before commit writeshyprland_cosmetic_verify_report.json, which the commit path correctly treats as stale authority-adjacent material and refuses before side effect; and standalonelease check --request hyprland_cosmetic_request.jsonis not currently a valid runbook step because the route-local request action wording differs from the generic capability request action variant. Commit and rollback still perform their own exact lease gates. - Phase 30A real Hyprland cockpit handoff:
docs/phases/phase30a-real-hyprland-cockpit-handoff.mdadds a deterministic terminal cockpit view/handoff for the existing Phase 29Fhyprland-cosmeticroute. It extendsdemo retro-cockpitonly behind the explicit--real-hyprlandflag, accepts the same four static demo phrases, renders compactoverview,request,plan,boundary,lease,action,receipts,rollback,audit, andallviews, and delegates dry-run, commit, and rollback to the existing Phase 29F route. Dry-run remains lease-free and writes no execution receipt. Commit and rollback still require strict local config, explicit--confirm,--lease,--lease-pubkey, and--lease-at-unix; the cockpit does not auto-mint leases, auto-discover keys, call standalonelease checkagainst route-local request artifacts, or runverify hyprland-cosmeticbetween dry-run and commit. Phase 30A adds no cockpit-specific persisted artifact, no second primitive, no arbitrary value support, no arbitraryhyprctl, no shell/generic runner, no inherited full environment, no Hermes/MCP/provider/cloud behavior, no Home Manager/Nix/ build/switch/apply behavior, no package/dotfile/config mutation, no screenshots/OCR/clipboard/browser/window/client/process inspection, no raw local context rendering, no production/trust/compliance/conformance/ certification/attestation/live-readiness claim, and no authority by cockpit rendering, command existence, artifact existence, review, CI, or phase existence. - Phase 30B cockpit capability registry polish:
docs/phases/phase30b-cockpit-capability-registry-polish.mdadds a deterministicregistryview, withcapabilitiesas an alias, to the existing Phase 30A real Hyprland cockpit. The registry is a static in-code display/status table with an authority summary. The optional--skin plain|paneland--color auto|always|neverflags are visual-only terminal rendering controls; plain deterministic output remains supported,autoremains conservative/no-color in this phase, and risk colors are cockpit display labels only rather than formal scores, certification, compliance, or trust claims. It lists the existing fixed Hyprland read-only live-read surfaces, the current boundedhyprland.cosmetic.decoration_roundingcockpit route, fake-retro demo status, fixed Home Manager generations observe status, and future/forbidden surfaces such as Home Manager build/apply, NixOS rebuild, arbitrary Hyprland control, shell execution, provider/cloud authority, MCP, Hermes, screenshots/OCR, clipboard, browser/window/client/process inspection, and keyboard/mouse input. It adds no registry loading, accepted endpoint names, cockpit-specific persisted artifact, endpoint, adapter, primitive, mutation, live read, process execution, shell/generic runner, Home Manager/Nix invocation, provider/cloud behavior, Hermes/MCP behavior, raw context rendering, production/trust/compliance/conformance/certification/ attestation/live-readiness claim, or authority by registry row, command, artifact, review, CI, merge, or phase existence. - Phase 30C demo walkthrough runbook:
docs/phases/phase30c-demo-walkthrough-runbook.mdanddocs/demo-hyprland-cockpit-walkthrough.mdpackage the existing Phase 29F/29G/30A/30B cockpit route into a repeatable local operator sequence for dry-run, run-id/hash extraction, exact local dev lease issuance, commit, manual live check, rollback, post-chain verifier, final manual live check, and recording hygiene. The real cockpit now accepts deterministic--view walkthrough;allincludes it afterregistry. The walkthrough is display/instruction only and adds no execute-all mode, automatic lease issuance, automatic dev-key use, automatic commit or rollback, verifier run, endpoint, adapter, primitive, mutation, live read, process execution, shell/generic runner, Home Manager/Nix behavior, MCP/Hermes/provider/cloud behavior, recording-tool invocation, raw context renderer, persisted cockpit artifact, raw local artifact rendering, private-key disclosure, raw lease rendering, raw plan-hash rendering, production/trust/compliance/conformance/ certification/attestation/live-readiness claim, or authority by walkthrough, command, artifact, review, CI, merge, or phase existence. - Phase 30D MCP boundary stdio skeleton:
docs/phases/phase30d-mcp-boundary-stdio-skeleton.mdanddocs/mcp-deadbolt-stdio.mdaddcargo run -p cog-cli -- mcp serve, a synchronous local stdio MCP server implementing the minimum2025-06-18JSON-RPC lifecycle forinitialize,notifications/initialized,ping,tools/list, andtools/call. It declares only the static tools capability and exposes exactly three review/status tools:deadbolt_status,deadbolt_capability_registry, anddeadbolt_cockpit_summary. Tool results are static/minimized status material only. The server adds no HTTP, Streamable HTTP, SSE, OAuth, network listener, resources, prompts, sampling, elicitation, roots, mutation, live read, dry-run, verifier over run dirs, lease issuance, dev-key use, arbitrary file read,hyprctl, shell/generic runner, Home Manager/Nix behavior, Hermes/provider/cloud authority, raw context renderer, raw local artifact output, production/ trust/compliance/conformance/certification/attestation/live-readiness claim, or authority by MCP tool, command, artifact, review, CI, merge, or phase existence. The actual real mutation route remains local cockpit plus exact lease plus explicit confirmation only. - Phase 30E MCP client / Hermes smoke docs:
docs/phases/phase30e-mcp-client-hermes-smoke-docs.mdextendsdocs/mcp-deadbolt-stdio.mdwith concise local MCP client smoke commands, expected short markers, built-binary smoke notes, Hermes-style documentation config examples, troubleshooting, and recording hygiene for the existing Phase 30D server. It also refreshes the README opening so external readers can quickly see the current project shape: local cockpit, the single Phase 29F Hyprland cosmetic mutation route, the internal verifier, and the status-only MCP server. Phase 30E is docs-only and adds no MCP method, MCP tool, MCP mutation, dry-run, commit, rollback, lease issue, dev-key use, verifier over run directories, run-dir/config/lease path input, HTTP/network listener, resources/prompts/sampling/elicitation/roots, Hermes runtime dependency, provider/cloud behavior, raw context access, raw smoke logs, or authority by client config, smoke result, docs, review, CI, merge, or phase existence. - Phase 30F public-readiness, license, and README voice polish:
docs/phases/phase30f-public-readiness-license-readme-polish.mdadds Apache-2.0 repo licensing, lightweight security and contribution guidance, a public-readiness checklist, README opening polish, and navigation updates. Phase 30F is docs/repo hygiene only and adds no Rust implementation behavior, CLI route, MCP surface, accepted input, adapter behavior, provider/cloud behavior, Home Manager/Nix behavior, shell/process behavior, raw context handling, new Hyprland mutation, or production trust/live-readiness/ compliance/conformance/certification/attestation claim. - Phase 31A AI-created style-plan boundary pre-review:
docs/style-plan-boundary.mdanddocs/phases/phase31a-ai-style-plan-boundary-pre-review.mddocument the future natural-language desktop style-plan boundary: user request, planner material, future Deadbolt-owned grammar, exact cockpit preview, local operator approval, reviewed local primitives, receipts, and rollback. Phase 31A is docs-only and adds no accepted input, parser/schema, fixture/golden, CLI route, MCP surface, runtime behavior, new Hyprland mutation, provider/cloud/Hermes/MCP authority, raw-context handling, wallpaper/panel endpoint, file writer, process runner, Home Manager/Nix behavior, or production trust/live-readiness/compliance/conformance/certification/ attestation claim. Current real mutation remains limited to exact Hyprland runtime cosmetic primitives: Phase 29Fdecoration:rounding -> 0and Phase 31Jgeneral:border_size -> 3, each with rollback to the previously parsed integer. - Phase 31B style-plan preview validator:
style-plan preview --input <path>accepts one explicit local style-plan JSON file as preview/review input only, validates it against a strict Deadbolt-owned preview grammar, and prints a deterministic stdout summary. The checked-in synthetic example isexamples/style-plans/haunted-win95.json. Preview acceptance is not mutation authority: no OS mutation, nohyprctl, no shell/process spawning, no Home Manager/Nix behavior, no provider/model/Hermes call, no MCP surface, no lease acceptance or issuance, no receipt/verifier artifact, no wallpaper/panel implementation, no raw host context, and no production trust/live-readiness/compliance/conformance/certification/ attestation claim are added. Wallpaper, panel, and cockpit surfaces are future-only/deferred. Current real mutation remains limited to Phase 29Fdecoration:rounding -> 0and Phase 31Jgeneral:border_size -> 3. - Phase 31C style-plan rounding compile:
style-plan compile --input <path> --out <dir>accepts one explicit local style-plan JSON file as compile/report input only, reuses the Phase 31B strict preview grammar and 32 KiB size bound, and writes exactly onestyle_plan_compile_report.jsonartifact under the explicit output directory. It identifies onlyhyprland_runtime.rounding = 0as eligible for the existing Phase 29Fmutate hyprland-cosmetic/decoration:rounding -> 0primitive. Compile acceptance is not mutation authority, not live dry-run authority, and not lease authority. The report is not a Phase 29F or Phase 31J request, is not consumed bymutate hyprland-cosmeticormutate hyprland-border-size, and creates no Phase 29F or Phase 31J artifacts, receipts, rollback receipts, or verifier reports. - Phase 31D style-plan Hyprland candidate catalog:
style-plan compile --input <path> --out <dir>now enrichesstyle_plan_compile_report.jsonwithfuture_hyprland_candidate_primitivesfor valid non-rounding Hyprland preview values. It normalizes those values to exact Hyprland keyword/value candidates such asgeneral:border_size,general:gaps_in,general:gaps_out,decoration:blur:enabled,decoration:shadow:enabled,animations:enabled,general:col.active_border, andgeneral:col.inactive_border.hyprland_runtime.rounding = 0remains the only style-plan compile correspondence to an existing Phase 29F primitive.hyprland_runtime.rounding = 1..20remains valid preview grammar and is not eligible for the existing route. Candidate rows are not executable through style-plan, are not dry-run/live state, are not lease authority, and are not consumed bymutate hyprland-cosmeticormutate hyprland-border-size. Phase 31J implements onlygeneral:border_size -> 3through a separate route. Wallpaper, panel, and cockpit surfaces remain future-only/deferred. No OS mutation, live read,hyprctl, shell/process spawning, Home Manager/Nix behavior, provider/model/Hermes call, MCP surface, lease acceptance or issuance, wallpaper/panel implementation, raw host context, or production trust/live-readiness/ compliance/conformance/certification/attestation claim is added. - Phase 31E style-plan Hyprland snapshot boundary pre-review:
docs/style-plan-hyprland-snapshot-boundary.mdanddocs/phases/phase31e-style-plan-hyprland-snapshot-boundary-pre-review.mddocument a future read-only multi-key Hyprland style snapshot boundary. A later route may read only exactgetoptionkeys for the Phase 31D cataloged options, require strict local consent/config, parse minimized values, and fail closed on partial read/parse failure. Phase 31E is docs-only: no implementation, no CLI route, no accepted config/report/schema/input, no live read, nohyprctlcall, no mutation, no live dry-run, no lease, no verifier, no MCP/provider/Hermes behavior, no Phase 29F artifact creation, and no authority by docs/example/command-shape existence is added. - Phase 31F style-plan Hyprland snapshot read-only:
style-plan snapshot --input <path> --out <dir> --config <path>accepts one explicit local style-plan JSON file and one explicit strict local consent/config JSON file. It reuses the Phase 31B parser and Phase 31D candidate catalog in memory, performs exact allowlistedhyprctl getoption <key>reads only, and writes exactly one minimizedstyle_plan_snapshot_report.jsonartifact. Snapshot reports are not mutation authority, not live dry-run authority, not lease authority, not verifier authority, not Phase 29F artifacts, not Phase 31J artifacts, and not consumed bymutate hyprland-cosmeticormutate hyprland-border-size. Partial/refused reports are diagnostic only and account for failed plus unattempted canonical keys without continuing live reads after the first refusal. Phase 31F adds no OS mutation,hyprctl keyword, arbitraryhyprctl,hyprctl --batch, dispatch, kill, setcursor, output, monitors, clients, activewindow, devices, binds, rollinglog, shell/generic process runner, Home Manager/Nix behavior, provider/model/Hermes call, MCP surface, lease acceptance or issuance, verifier behavior, wallpaper/panel implementation, Phase 29F artifact creation, Phase 31J artifact creation, raw host-context disclosure, or production trust/live-readiness/compliance/conformance/ certification/attestation claim. - Phase 31G style-plan snapshot demo closeout:
docs/phases/phase31g-style-plan-snapshot-demo-closeout.mddocuments the preview -> compile -> snapshot demo flow andstyle-plan snapshotnow prints a more demo-readable terminal summary after writingstyle_plan_snapshot_report.json. The summary shows minimized report fields only: report kind, authority, status,mutation_performed: false, style name, eligible/future counts, parsed option rows, deferred/failed option rows, and non-authority notes. Phase 31G adds no new command, accepted grammar, config field, live read, mutation,hyprctl keyword, arbitraryhyprctl,hyprctl --batch, dispatch, shell/generic process runner, PATH lookup, Home Manager/Nix behavior, provider/model/Hermes call, MCP surface, lease acceptance or issuance, verifier behavior, Phase 29F artifact creation or consumption, report artifact, raw process context persistence, raw Hyprland output persistence, or production trust/live-readiness/ compliance/conformance/certification/attestation claim. - Phase 31H style-plan existing primitive handoff closeout:
docs/phases/phase31h-style-plan-existing-primitive-handoff.mddocuments the human/operator runbook relationship between style-plan review material and the already existing Phase 29F route. The only style-plan compile correspondence to an existing mutation route remainshyprland_runtime.rounding = 0tomutate hyprland-cosmetic/decoration:rounding -> 0. Compile reports, snapshot reports, summaries, command rows, docs, CI, review, and merge are not mutation authority and are not accepted as Phase 29F or Phase 31J input. The operator must separately run the existing Phase 29F or Phase 31J dry-run/commit/rollback/verifier sequence with that route's own strict config, explicit confirmation, exact signed lease, policy gates, receipts, and rollback chain. Phase 31H changes no implementation authority: no new command, accepted input, style-plan grammar, config field, live read, mutation, lease behavior, verifier behavior, MCP/provider/Hermes authority, Phase 29F or Phase 31J artifact creation or consumption, report bridge, report artifact, raw context persistence, production trust, live-readiness, compliance, conformance, certification, or attestation claim. - Phase 31I border-size mutation boundary pre-review:
docs/phases/phase31i-border-size-mutation-boundary-pre-review.mddocuments a docs-only boundary pre-review for the second exact Hyprland runtime cosmetic primitive,general:border_size -> 3, with rollback to the previously parsed integer. Phase 31I itself did not makeborder_sizeexecutable: no command, accepted input, style-plan grammar, config field, report artifact, live read, mutation, dry-run, commit, rollback, lease behavior, verifier behavior, MCP/provider/Hermes authority, Phase 29F behavior change, Phase 29F artifact creation or consumption, compile/snapshot report authority, report bridge, raw process-context persistence, production trust, live-readiness, compliance, conformance, certification, or attestation claim. Phase 31J is the separate implementation PR for that exact primitive. - Phase 31J border-size exact mutation:
docs/phases/phase31j-border-size-exact-mutation.mdimplementsmutate hyprland-border-sizeandverify hyprland-border-sizefor exactlygeneral:border_size -> 3, with rollback to the previous parsed integer. The route uses separatehyprland_border_size_*artifacts, a separate strict consent/config schema, separate policy and lease identity, exacthyprctl getoption general:border_sizedry-run/current reads, exacthyprctl keyword general:border_size 3commit, and exacthyprctl keyword general:border_size <previous-parsed-int>rollback. Commit requires strict config, explicit confirmation, dry-run chain linkage, current-value recheck, policy gate, and exact signed lease bound tohyprland.border_size.general_border_size:<run-id>:<dry-run-plan-hash>. Rollback requires a complete committed chain, explicit confirmation, and a fresh exact lease. The verifier is internal-consistency only and does not call Hyprland or authorize execution. Phase 31J adds no style-plan report consumption, automatic style-plan bridge, arbitrary value input, multi-key style apply, gaps/blur/shadow/animation/color/wallpaper/panel/cockpit implementation,hyprctl --batch,hyprctl -j, dispatch/kill/setcursor/ output/monitors/clients/activewindow/devices/binds/rollinglog, shell/generic process runner, PATH/which lookup, Home Manager/Nix, provider/model/Hermes authority, MCP authority, raw stdout/stderr/env/cwd/path persistence, host safety proof, final-live-state proof, production trust, live-readiness, compliance, conformance, certification, or attestation claim. - Phase 31K multi-primitive cosmetic apply route design:
docs/phases/phase31k-multi-primitive-cosmetic-apply-route-design.mdis a docs-only design pre-review for a future operator-confirmed route that would apply multiple already-reviewed Hyprland cosmetic primitives in one run by composing a closed vocabulary (initially the proven Phase 29Fdecoration:rounding -> 0and Phase 31Jgeneral:border_size -> 3). It adds no command, accepted input, style-plan grammar, config field, report artifact, live read, mutation, dry-run, commit, rollback, lease behavior, verifier behavior, MCP/provider/Hermes authority, Phase 29F or Phase 31J behavior change, Phase 29F or Phase 31J artifact creation or consumption, automatic style-plan-to-mutation bridge, compile/snapshot report authority, production trust, live-readiness, compliance, conformance, certification, or attestation claim. The only currently executable real mutation primitives remain Phase 29Fdecoration:rounding -> 0and Phase 31Jgeneral:border_size -> 3, each through its own separate route. - Mythos hostile architecture audit and Phase 32A remediation:
docs/audits/mythos-hostile-architecture-audit.mdrecords the eight-finding hostile review of 2026-06-09 with severities and falsification criteria;docs/phases/phase32a-mythos-audit-remediation.mdtriages the findings into tracks and lands Track A: doctrine-status honesty notes in README.md, AGENTS.md, SECURITY.md, anddocs/current-authority-boundary.md(the accept/refuse decision on the real mutation routes iscog-leaseslease verification plus typed route handlers inside the CLI process;cog-kernelevaluates synthetic noop/replay bundles only), demotion of the kernel hostile-text scan to a lexical tripwire, a SECURITY.md stale single-route correction, the unwiredcog-leasesclock-drift mechanism (evaluate_clock_drift,ClockDriftCheck,CLOCK_DRIFT_REFUSE_SECONDS) with unit tests, and thescripts/check-gate-invariants.shgate-logic CI guard pinning the live-authority acceptance chain to its refusal message and the commit-stage preflight overwrite flags. The pinned lease trust anchor, shared Hyprland primitive engine implementation, kernel routing, single-command ceremony UX, clock-drift route wiring, second blocking reviewer, and external witness relying party remain design/flagged material only. It adds no command, accepted input, mutation route, lease shape change, Phase 29F or Phase 31J behavior change, or witness/evidence/DSSE/Phase 5 semantic change; audit text, remediation docs, guard success, and CI success authorize nothing by existence. - Phase 13 kernel seed:
docs/phases/phase13-kernel-seed.mdrecords the broader kernel architecture seed for a userspace governance layer for AI-operated systems. Phase 13A implements diagnostic protocol records only; authority-bearing kernel pilots remain future work.
- Real mutation support remains intentionally narrow. The current real
mutation routes are Phase 29F
mutate hyprland-cosmetic, limited exactly to Hyprland runtime cosmeticdecoration:roundingset to0, and Phase 31Jmutate hyprland-border-size, limited exactly to Hyprland runtime cosmeticgeneral:border_sizeset to3. Both rollback only to the previously parsed integer after explicit config, confirmation, exact lease, policy gates, commit-time current-value recheck, and rollback-time exact lease recheck. The Phase 12B/12C fake workspace-tag pilot and Phase 29C fake retro style transform remain fake/file-backed only. There is no broad real desktop mutation, arbitrary Hyprland mutation, arbitraryhyprctl, shell/network/desktop-control mutation runtime, provider mutation path, Home Manager/Nix/build/switch/apply path, package/dotfile/config mutation, or broad real-target execution/rollback receipt support. - The intended future path is governed real adapters that stay disabled by
default until explicit authority modes, typed adapter registry entries,
policy gates, leases where appropriate, manual confirmation or unlock
semantics, receipt/witness boundaries, and verifier/conformance coverage are
reviewed. Phase 15B implements only local config/status parsing and the
provider-local proposal gate. Phase 16A documents the future registry
contract only. Phase 16B parses and inspects descriptor files as
diagnostic/control-plane material only. Phase 16C composes one explicit
descriptor with policy, lease, brake, requested context, and time as
diagnostic/control-plane material only. Phase 16D records a static
diagnostic fake-call chain as fake-only diagnostic/control-plane material
only. Phase 16E documents the containment contract as a design gate only.
Phase 16F documents maintainability and architecture audit findings only.
Phase 16G documents model-visible context rendering and observation budgets
only. Phase 16H documents inference provider broker routing design only.
Phase 16I documents the mandatory readiness gate before future real adapter
implementation only. Phase 17A documents the Home Manager target-family
design only. Phase 17B adds a Home Manager target-family diagnostic/fake
rehearsal only. Phase 17C documents the Home Manager observe/read-only
diagnostics boundary only. Phase 17C.1 adds static target descriptor inspect
only. Phase 17C.2 adds a fixed-command read-only process contract only.
Phase 17C.3 adds one fixed
home-manager --versionprocess observation only. Phase 17C.4 adds generations observe/redaction design only. Phase 17C.5 adds diagnostic synthetic generations fixture parsing/report rehearsal only. Phase 17C.6 adds live generations process/capture/redaction contract text only. Phase 17C.7 adds one fixed livehome-manager generationsobserve route only. Phase 17C.8 hardens the two fixed Home Manager observe routes with shared conformance fixture/tests, parser/redaction regressions, and docs wording only. Phase 17D documents the future build/dry-run boundary only and adds no command or runtime behavior. Phase 17D.1 adds only synthetic build-boundary contract fixtures, parser checks, hostile refusal cases, tests, and docs; it remains non-executable and non-authoritative. Phase 17D.2 adds build-class authority/preflight design text only. Phase 17D.3 adds synthetic build-class preflight report-shape fixtures, parser checks, hostile refusal cases, tests, and docs only; it remains non-executable and non-authoritative. Phase 17D.4 adds only deterministiccog-modelcomposition and parser round-trip tests for the locked Phase 17D.3 refusal-shaped report; it remains non-executable and non-authoritative. Phase 17D.5 adds one synthetic diagnostic writer command that writes the locked Phase 17D.3 refusal report and a Phase 17D.5 writer receipt only; it is not a live build preflight and authorizes no build. Phase 17D.6 adds only a syntheticcog-modelrequest/authority input contract parser/composer/tests/fixtures/docs rehearsal; it adds no command or runtime preflight and authorizes no build. Phase 17D.7 adds only a syntheticcog-modelrequest-to-refusal composition rehearsal from that valid request contract to the locked Phase 17D.3 refusal; it adds no command or runtime preflight and authorizes no build. Phase 17D.8 adds only a docs-only architecture checkpoint and live-build readiness gate design; it adds no code, fixture, command, route, runtime preflight, or build authorization. Phase 17D.9 adds only a docs-only live build-preflight process contract; it adds no code, fixture, test, command, route, runtime preflight, process execution, or build authorization. Phase 17D.10 adds only syntheticcog-modelparser/composer/tests/fixtures/docs process-transcript material; it adds no command, route, runtime preflight, process runner, fake process runner, process execution, Home Manager/Nix invocation, raw log persistence, model-visible context, provider/cloud behavior, or build authorization. Phase 17D.11 adds only fake/test-onlycog-modelprocess mechanics harness tests; it adds no command, route, runtime preflight, generic process runner, Home Manager/Nix invocation, raw output persistence, model-visible context, provider/cloud behavior, mutation, or build authorization. Phase 17D.12 adds only fake/test-only hardening tests for that sealed harness; it adds no command, route, runtime preflight, reusable subprocess API, Home Manager/Nix invocation, result symlink behavior, raw output persistence, model-visible context, provider/cloud behavior, mutation, or build authorization. Phase 17D.13 adds only docs-only live build-preflight readiness gate material; it adds no command, route, runtime preflight, process execution, Home Manager/Nix invocation, raw output persistence, model-visible context, provider/cloud behavior, mutation, or build authorization. Phase 17D.14 adds only docs-only live build-preflight no-go material; it adds no command, route, runtime preflight, process execution, Home Manager/Nix invocation, raw output persistence, model-visible context, provider/cloud behavior, mutation, or build authorization. Phase 17D.15 adds only syntheticcog-modelroute-specific authority gate contract parser/composer/tests/fixtures/docs material; it resolves only the authority-gate design blocker and does not resolve network/cache/substituter policy or exact argv/result-link proof. It adds no command, route, runtime preflight, process execution, Home Manager/Nix invocation, raw output persistence, model-visible context, provider/cloud behavior, mutation, or build authorization. Phase 17D.16 adds only syntheticcog-modelnetwork/cache/substituter policy contract parser/composer/tests/fixtures/docs material; it resolves only the policy design/rehearsal blocker, does not implement enforcement, and does not resolve exact argv/result-link suppression proof. It adds no command, route, runtime preflight, process execution, Home Manager/Nix invocation, raw output persistence, raw config/token/proxy/substituter/builder material persistence, model-visible context, provider/cloud behavior change, mutation, or build authorization. Phase 17D.17 adds only syntheticcog-modelexact argv/result-link proof contract parser/composer/tests/fixtures/docs material; it resolves only the proof design/rehearsal blocker, does not implement enforcement, and adds no command, route, runtime preflight, process execution, Home Manager/Nix invocation, result-link behavior, raw output persistence, authority-gate alteration, network/cache/substituter policy alteration, model-visible context, provider/cloud behavior change, mutation, or build authorization. Phase 17D.18 adds only syntheticcog-modelreadiness bundle contract parser/composer/tests/fixtures/docs material; it bundles only the Phase 17D.15, Phase 17D.16, and Phase 17D.17 synthetic contracts, proves only local internal consistency, does not implement enforcement, and adds no command, route, runtime preflight, process execution, Home Manager/Nix invocation, result-link behavior, result path access, raw output persistence, prerequisite contract semantic change, model-visible context, provider/cloud behavior change, mutation, or build authorization. Phase 17D.19 adds only docs-only live candidate pre-review material; Design Outcome B records unresolved HOME/XDG environment policy, network/cache/substituter policy enforcement, and child-internal route-mode proof blockers, and adds no command, route, runtime preflight, process execution, Home Manager/Nix invocation, result path behavior, raw output persistence, model-visible context, provider/cloud behavior change, mutation, or build authorization. Phase 17D.20 adds only synthetic HOME/XDG/environment policy contract parser/composer/tests/fixtures/docs material and records live HOME/XDG policy unresolved. Phase 17D.21 adds only synthetic environment-inclusive readiness bundle parser/composer/tests/fixtures/docs material, keeps live build-preflight no-go, and adds no command, route, runtime preflight, execution, enforcement, raw context persistence, provider/ cloud behavior change, mutation, or build authorization. This is roadmap framing, local inspection, checked-in fake/static/synthetic/conformance fixture material, diagnostic report material, one fixed version observe report, one fixed generations observe report, Home Manager observe conformance fixture material, build-boundary contract material, build authority/preflight design text, build preflight report-shape rehearsal material, build preflight composer rehearsal material, synthetic build preflight writer material, build preflight request contract rehearsal material, build preflight request-to-refusal rehearsal material, Home Manager build preflight architecture checkpoint material, Home Manager build preflight process contract material, Home Manager build preflight process transcript rehearsal material, Home Manager build preflight fake process harness rehearsal/hardening material, live build-preflight readiness gate material, live build-preflight no-go material, synthetic authority gate contract rehearsal material, synthetic network/cache/substituter policy contract rehearsal material, and synthetic exact argv/result-link proof contract rehearsal material only, not implemented build/dry-run or adapter authority. - A Home Manager target-family fake rehearsal exists through the existing
adapter fake-call inspectdiagnostic path and checked-in fake fixtures only. Phase 17C.1 adds a static target descriptor parser and static inspect report only. Phase 17C.2 adds a fixed-command process contract only. Phase 17C.3 adds only a fixedhome-manager --versionobserve route. Phase 17C.4 adds generations observe/redaction design only. Phase 17C.5 adds only checked-in synthetic generations fixture inspection. Phase 17C.6 adds only live generations process/capture/redaction contract text. Phase 17C.7 adds one fixed livehome-manager generationsobserve route. Phase 17C.8 adds only shared hardening/conformance coverage for the fixed--versionand fixedgenerationsobserve routes. Phase 17D adds only design text for a future Home Manager build/dry-run boundary. Phase 17D.1 adds only synthetic contract fixture/parser/test rehearsal for that boundary. Phase 17D.2 adds only future build-class authority/preflight design text. Phase 17D.3 adds only synthetic build-class preflight report-shape fixture/parser/test rehearsal. Phase 17D.4 adds only synthetic build-class preflight report composer/parser round-trip tests. Phase 17D.5 adds only one synthetic diagnostic writer command for those locked refusal artifacts. Phase 17D.6 adds only synthetic build-preflight request/authority input contract parser/composer/tests/fixtures/docs material and no command. Phase 17D.7 adds only synthetic build-preflight request-to-refusal composition parser/composer/tests/fixtures/docs material and no command. Phase 17D.8 adds only docs-only build-preflight architecture checkpoint and live-build readiness gate design material and no command. Phase 17D.9 adds only docs-only live build-preflight process contract material and no command. Phase 17D.10 adds only synthetic build-preflight process transcript parser/composer/tests/fixtures/docs material and no command. Phase 17D.11 adds only fake/test-only build-preflight process mechanics harness tests and no command. Phase 17D.12 adds only fake/test-only hardening tests for that harness and no command. Phase 17D.13 adds only docs-only live build-preflight readiness gate material and no command. Phase 17D.14 adds only docs-only live build-preflight no-go material and no command. Phase 17D.15 adds only synthetic route-specific authority gate contract parser/composer/tests/ fixtures/docs material and no command. Phase 17D.16 adds only synthetic network/cache/substituter policy contract parser/composer/tests/fixtures/docs material and no command. Phase 17D.17 adds only synthetic exact argv/ result-link proof contract parser/composer/tests/fixtures/docs material and no command. Phase 17D.18 adds only synthetic readiness bundle contract parser/composer/tests/fixtures/docs material and no command. Phase 17D.19 adds only docs-only live candidate pre-review material and no command. Phase 17D.20 adds only synthetic HOME/XDG/environment policy contract parser/ composer/tests/fixtures/docs material and no command. Phase 17D.21 adds only synthetic environment-inclusive readiness bundle contract parser/composer/ tests/fixtures/docs material and no command. Phase 17D.22 adds only fake/ test-only integrated gate rehearsal coverage inside the sealed fake harness and no command. Phase 17D.23 adds only docs-only closeout mapping for the current synthetic/fake stack and no command. Phase 17D.24 adds only docs-only future live runtime gate design/no-go checklist material and no command. Phase 17D.25 adds only synthetic runtime-gate report-shape parser/composer/ tests/fixtures/docs material and no command. Phase 17D.26 adds only synthetic runtime-gate report writer-rehearsal parser/composer/helper/ tests/fixtures/docs material and no command. Phase 17D.27 adds only synthetic pre-spawn gate decision input/evaluator/parser/composer/tests/ fixtures/docs material and no command. Phase 18A adds only docs-only architecture consolidation audit material and no command. Phase 18B adds only docs-only build-preflight index/map material and no command. Phase 18C adds only docs-only helper-extraction pre-review/risk analysis material and no command. Phase 18D adds only one privatecog-modelsynthetic parser mechanics helper used by D25/D27 parser code and no command. No mutating Home Manager adapter exists. No Home Manager descriptor/parser/schema for mutating real execution exists. No registry loading exists. The observe/read-only design exists, but no live observe Home Manager adapter exists beyond the two fixed process observe routes. No process runner, containment runner, context renderer, or observation budget exists for Home Manager. No dry-run/build Home Manager adapter exists. No confirm-mode apply Home Manager adapter exists. Deadbolt cannot invoke Home Manager beyond the fixed Phase 17C.3home-manager --versionobserve route and the fixed Phase 17C.7home-manager generationsobserve route. The Phase 17C.5 generations fixture command is not Home Manager execution, Phase 17C.6 is not a command, Phase 17C.8 is not a command, Phase 17D is not a command, Phase 17D.1 is not a command, Phase 17D.2 is not a command, Phase 17D.3 is not a command, Phase 17D.4 is not a command, and Phase 17D.5 is a synthetic writer command only, not Home Manager/Nix/process execution. Phase 17D.6 is not a command and is parser/tests/fixtures/docs only. Phase 17D.7 is not a command and is parser/composer/tests/fixtures/docs only. Phase 17D.8 is not a command and is docs-only architecture checkpoint/readiness-gate design only. Phase 17D.9 is not a command and is docs-only process-contract design only. Phase 17D.10 is not a command and is synthetic parser/composer/tests/fixtures/docs process-transcript material only. It cannot run any live build preflight. Phase 17D.11 is not a command and is fake/test-only process mechanics harness material only; it can spawn only the current test executable in fake child mode undercargo testand cannot run any non-17C.7home-manager generationsshape,home-manager option,home-manager packages,home-manager build,home-manager switch, rollback, uninstall, generation removal, generation expiry, Nix commands, or NixOS rebuild. Phase 17D.12 is not a command and is fake/test-only hardening material only; it can spawn only sealed fake modes of the current test executable and cannot invoke Home Manager or Nix. Phase 17D.13 is not a command and is docs-only readiness gate material only; it cannot spawn a process or invoke Home Manager or Nix. Phase 17D.14 is not a command and is docs-only no-go material only; it cannot spawn a process or invoke Home Manager or Nix. Phase 17D.15 is not a command and is synthetic no-runtime-authority contract material only; it cannot spawn a process or invoke Home Manager or Nix. Phase 17D.16 is not a command and is synthetic no-runtime-authority policy contract material only; it cannot spawn a process or invoke Home Manager or Nix. Phase 17D.17 is not a command and is synthetic no-runtime-authority proof contract material only; it cannot spawn a process, invoke Home Manager or Nix, or touch result-path state. Phase 17D.18 is not a command and is synthetic no-runtime-authority readiness bundle material only; it cannot spawn a process, invoke Home Manager or Nix, add enforcement, or touch result-path state. Phase 17D.19 is not a command and is docs-only Design Outcome B pre-review material only; it cannot spawn a process, invoke Home Manager or Nix, add enforcement, or touch result-path state. Phase 17D.20 is not a command and is synthetic HOME/XDG/environment policy material only. Phase 17D.21 is not a command and is synthetic environment-inclusive readiness bundle material only. Phase 17D.22 is not a command and is fake/test-only integrated gate rehearsal material only. Phase 17D.23 is not a command and is docs-only closeout material only. Phase 17D.24 is not a command and is docs-only future runtime gate design material only. Phase 17D.25 is not a command and is synthetic report-shape parser/composer/ fixture/test/doc material only; it cannot spawn a process, invoke Home Manager or Nix, capture output, create or inspect result links, add runtime enforcement, or make live build-preflight ready. Phase 17D.26 is not a command and is synthetic fixed-artifact writer-rehearsal material only; it cannot spawn a process, invoke Home Manager or Nix, capture output, create or inspect result links, add runtime enforcement, or make live build-preflight ready. Phase 17D.27 is not a command and is synthetic pre-spawn decision rehearsal material only; its evaluator performs no filesystem writes, does not call the Phase 17D.26 writer helper, cannot construct or spawn a process, invoke Home Manager or Nix, capture output, create or inspect result links, add runtime enforcement, or make live build-preflight ready. Phase 18A is not a command and is docs-only architecture audit material only; it cannot construct or spawn a process, invoke Home Manager or Nix, capture output, add runtime enforcement, or make live build-preflight ready. Phase 18B is not a command and is docs-only index/map material only; it cannot construct or spawn a process, invoke Home Manager or Nix, capture output, add runtime enforcement, or make live build-preflight ready. Phase 18C is not a command and is docs-only helper-extraction pre-review material only; it cannot extract helpers, refactor code, construct or spawn a process, invoke Home Manager or Nix, capture output, add runtime enforcement, or make live build-preflight ready. Phase 18D is not a command and is private synthetic parser-mechanics helper material only; it cannot construct or spawn a process, invoke Home Manager or Nix, capture output, create or inspect result links, add runtime enforcement, change accepted JSON shapes, change issue codes, change fixtures, change writer/fake harness behavior, or make live build-preflight ready. - Desktop transaction execution paths are partial; records, safety checks, and dry-run evidence bundles exist, but full live mutation pipeline remains intentionally constrained and unwired.
- Observation adapters beyond fixture mode are partial/stubbed (read-only targets planned, not required for current tests).
cog-evidenceis adopted internally by Phase 5 observation validation and by Phase 7C codelet and Phase 7D desktop transaction evidence bundles, but sandbox reports and policy-interception records have not migrated yet.- Legacy non-Phase-5 demo roots remain scaffold/non-protocol. Golden-path demo roots are deterministic scaffold line hashes, and older harness/compile routes use explicit
scaffold-non-protocol:*markers. The Phase 14B kernel decision witness profile is a separate local profile for selected Phase 13C decision facts, not a replacement for Phase 5. - Codelet evidence bundles are scaffold/interim bundles. They verify local artifact graph consistency, not real sandbox execution, deterministic replay, external originality, or original Cogitator protocol parity.
- Desktop transaction evidence bundles are scaffold/interim dry-run bundles. They verify local artifact graph consistency, not live desktop mutation, deterministic replay, external originality, or original Cogitator protocol parity.
- Evidence graph reports are diagnostic visibility artifacts. They are not witness evidence and are not alternate verifiers.
- Pass summaries are diagnostic projections from existing verifier reports. They are not witness evidence, not graph evidence, and not an independently re-executed verifier engine.
- Verifier-bench is a seed corpus for measuring existing verifier behavior and pass-category coverage, not a full conformance suite.
- RFC 8785/JCS conformance is closer but incomplete. The target profile is not active for existing bundles and is not marked conformant because ECMAScript number serialization and the full I-JSON validation claim are not complete.
- Profile migration is planned but not started. Current migration plans and compatibility reports are blocked until the target profile is conformant and expected-root updates are reviewed.
- Local DSSE export is offline only. It does not submit to Sigstore/Rekor, look up transparency logs, provide SCITT/COSE receipts, or prove external originality without trusted key policy or a future receipt. Phase 8S.1 reports
trusted_key_policy_applied: falseandtransparency_receipt_verified: falserather than implying those layers exist. Phase 9D/9E require a local signed lease for CLI signing/export, but that lease is authorization for an attempt only and does not make DSSE signatures production trust or transparency. - Local capability leases are offline only. They use explicit evaluation time, local Ed25519 signatures, explicit requested capabilities, grant-level path checks, and deterministic request checks. Phase 9B uses them as opt-in preflight gates for selected dry-run/fixture commands. Phase 9B.1 keeps leased
codelet runnative-fixture-only, Phase 9B.2 blocks relative/absolute decision-report aliases inside command output directories, Phase 9C requires leases only for the deterministic fake-target transaction dry-run command, and Phase 9D requires leases for local DSSE signing/export. Phase 9E centralizes only the CLI policy/request construction for those existing paths. Phase 10D adds thelive-hyprland-monitors-readlive-authority lease template scoped tohyprctl -j monitors; Phase 10E adds thelive-hyprland-workspaces-readlive-authority lease template scoped tohyprctl -j workspaces; Phase 10F adds thelive-hyprland-activeworkspace-readlive-authority lease template scoped tohyprctl -j activeworkspace. Phase 10A/10C screenshot, AT-SPI, generic Hyprland-state, and broad live-session requests remain refused. Leases still do not poll revocation state, discover keys over the network, grant production trust, or make lease decision reports witness evidence. - Sensorium replay remains a mock/scaffold replay path, not protocol-grade deterministic replay. The authoritative witness/replay standard is currently represented most strongly by the Phase 5 observation verifier.
- Live desktop capture beyond Phase 10D monitors, Phase 10E workspaces, and Phase 10F activeworkspace (real screenshots, live AT-SPI streams, clients, activewindow, titles, app classes, process info, arbitrary hyprctl args, portals, or broad Hyprland observation integration). Phase 10A/10C model future capability names and the broad Hyprland-state preflight boundary; those requests remain refused and non-executable.
- Real-target mutation artifacts, human approval hooks, and broader
macro-action syscalls remain future work. Phase 12B/12C implements and
hardens only fake workspace-tag receipts, mutation-specific lease decisions,
and
fake_target_state.json; Phase 29C implements only fake-retro receipts, mutation-specific lease decisions, andfake_retro_style_state.json. - Real model-dependent runtime loops for certain demos (mock/recorded modes preferred).
- Current status is fixture ingestion, a resolved-loopback-only smoke path, the Phase 15P-B proposal-only local provider path, Phase 15P-C/15P-D diagnostic conformance/report-invariant coverage for that path, and the Phase 15B explicit local policy gate for provider-local live network calls. Phase 11A documents the planner-provider boundary, Phase 11B implements checked-in provider envelope fixture parsing, Phase 11C implements a credential-free local smoke call, Phase 15P-B implements
propose provider-localfor local OpenAI-compatible proposal generation only, Phase 16H documents future inference broker routing only, and Phase 16I documents the broker boundary as one mandatory readiness gate before future real adapter work. These phases do not enable general model-provider integration. cog-modelhas provider vocabulary forOpenAiCompatible,LlamaCpp,Vllm,Ollama, andRecorded, plus typed request/response/config records. Only the recorded fixture path is implemented as a provider today.RecordedProvidercan read a deterministic local response file for proposal compilation. That does not imply live model support.propose provider-fixturecan read a checked-in raw provider response fixture, reject duplicate keys and unsupported envelope shapes before proposal parsing, normalize one candidate/refusal, and write diagnostic reports. Its accepted CLI surface is exactly--api-family,--provider-kind,--fixture, and--out; unknown flags, duplicate allowed flags, missing values, oversized fixture files, and unsafe finish reasons fail closed. It does not call providers, use endpoints, use credentials, write raw provider bodies by default, write evidence/witness material, grant leases, sign DSSE, change verifier status, or execute actions.propose provider-loopback-smokecan make one resolved-loopback-only OpenAI-compatible Chat Completions subset smoke call tohttp://127.0.0.1:<port>/v1/chat/completions,http://[::1]:<port>/v1/chat/completions, orhttp://localhost:<port>/v1/chat/completionsonly when all resolved addresses are loopback. Its accepted CLI surface is limited to--api-family,--provider-kind,--endpoint,--model,--request,--out, and bounded timeout/body/output options. It rejects credentials, known/common provider credential env vars, proxy env vars, redirects, custom headers, cookies, streaming, tools, execution, leases, query/fragment/userinfo endpoints, non-loopback resolution, and unknown flags before network/output where applicable. After endpoint/request validation it creates and write-preflights--out, rejects non-regular or symlinked concrete report paths, removes any stale regularaction_proposal.json, and fails before the provider POST if cleanup is impossible or the stale path is not a regular removable file. Reports are diagnostic/control-plane only and raw provider bodies are not written by default.propose provider-localcan call local OpenAI-compatible servers such as llama.cpp / llama-server, vLLM, Ollama, TensorRT-LLM-style servers, and generic local OpenAI-compatible servers only through the strict proposal-only subset and only after explicit Phase 15B policy withmode: "propose"andallow_provider_local: true. Missing config defaults to locked and refuses before network. Loopback accepts only127.0.0.1,[::1], orlocalhostwith all-loopback resolution. VM-host accepts only literal192.168.122.1and10.0.2.2with no DNS resolution. It writesprovider_local_report.json,provider_endpoint_report.json,provider_envelope_report.json,proposal_parse_report.json, andaction_proposal.jsononly after strict proposal parsing succeeds. Phase 15P-C/15P-D tests pin fixture coverage, refusal classes, artifact sets, stale proposal handling, report-boundary flags, and no raw provider body persistence. Reports and parsed proposals are diagnostic/control-plane material only.- OpenAI-compatible local serving is implemented only through
propose provider-local. Private LAN providers, arbitrary RFC1918/private IPs, public/cloud providers, OpenAI/ChatGPT cloud APIs, Claude/Anthropic APIs, DeepSeek cloud APIs, credentials, custom headers, proxies, redirects, streaming, provider-side tools, MCP/AG-UI, file upload, images/vision, embeddings, response APIs, arbitrary endpoint paths, execution, and mutation remain refused. - No inference provider broker exists. Future broker output remains design-only planner/diagnostic material and is not authority for disclosure, execution, mutation, adapter routing, preflight success, lease success, provider-local permission, cloud context transfer, or context expansion.
models/recorded.tomlis the real recorded-provider config.models/local-llama-cpp.toml,models/local-vllm.toml, andmodels/local-ollama.tomlare disabled examples/stubs/placeholders unless they are made runnable and tested in a later explicit phase.- No model-provider authority is enabled. Provider output and normalized provider records remain untrusted planner data and diagnostic/control-plane material only. They cannot become evidence, a lease, verifier authority, DSSE trust, tool execution, network authority, shell authority, or live mutation.
- Phase 12A does not expand provider authority. Provider output remains untrusted planner text and cannot create, sign, upgrade, or imply mutation leases, approval decisions, execution receipts, rollback receipts, evidence, witness material, DSSE trust, verifier authority, or execution permission.
- No known intentionally-shipped broken paths are tracked here; unsupported paths should fail closed.
cargo fmtcargo test -p cog-canonicalcargo test -p cog-evidencecargo test -p cog-observationcargo test -p cog-codeletscargo test -p cog-transactionscargo test -p cog-attestationcargo test -p cog-clicargo testcargo clippy --all-targets --all-features -- -D warningscargo run -p cog-cli -- lease issue --template transaction-dry-run --lease-id phase9e-transaction-dry-run-required --subject fixture-agent --audience cogitator-harness-local --not-before 1735689600 --not-after 1893456000 --key fixtures/attestation/dev_ed25519_private.json --out runs/leases/transaction-dry-run.lease.jsoncargo run -p cog-cli -- transaction dry-run --target hyprland-theme-fake --out runs/transaction-dry-run --lease runs/leases/transaction-dry-run.lease.json --lease-pubkey fixtures/attestation/dev_ed25519_public.json --lease-at-unix 1735689600 --lease-decision-out runs/lease-decisions/transaction-dry-run.decision.jsoncargo run -p cog-cli -- verify transaction --run runs/transaction-dry-runcargo run -p cog-cli -- graph inspect --kind observation --run runs/phase5-observecargo run -p cog-cli -- verify passes --kind observation --run runs/phase5-observecargo run -p cog-cli -- graph inspect --kind codelet --run runs/codelet-validatecargo run -p cog-cli -- verify passes --kind codelet --run runs/codelet-validatecargo run -p cog-cli -- graph inspect --kind codelet --run runs/codelet-democargo run -p cog-cli -- verify passes --kind codelet --run runs/codelet-democargo run -p cog-cli -- graph inspect --kind transaction --run runs/transaction-dry-runcargo run -p cog-cli -- verify passes --kind transaction --run runs/transaction-dry-runcargo run -p cog-cli -- eval verifier-bench --out runs/verifier-benchcargo run -p cog-cli -- canonical profilescargo run -p cog-cli -- canonical migration-plancargo run -p cog-cli -- canonical compare-profile --kind observation --run runs/phase5-observe --target-profile cogitator-rfc8785-jcs-v1cargo run -p cog-cli -- canonical compare-profile --kind codelet --run runs/codelet-validate --target-profile cogitator-rfc8785-jcs-v1cargo run -p cog-cli -- canonical compare-profile --kind codelet --run runs/codelet-demo --target-profile cogitator-rfc8785-jcs-v1cargo run -p cog-cli -- canonical compare-profile --kind transaction --run runs/transaction-dry-run --target-profile cogitator-rfc8785-jcs-v1cargo run -p cog-cli -- canonical compare-profile --kind transaction --run runs/transaction-dry-run --target-profile cogitator-rfc8785-jcs-v1 --out runs/profile-compat-transaction.jsoncargo run -p cog-cli -- canonical check --profile cogitator-rfc8785-jcs-v1 --input fixtures/canonicalization/jcs/valid/simple_object.jsoncargo run -p cog-cli -- canonical check --profile cogitator-rfc8785-jcs-v1 --input fixtures/canonicalization/jcs/invalid/duplicate_keys.json(expected failure)cargo run -p cog-cli -- lease issue --template dsse-local-export --lease-id phase9e-dsse-observation-export --subject fixture-agent --audience cogitator-harness-local --not-before 1735689600 --not-after 1893456000 --key fixtures/attestation/dev_ed25519_private.json --out runs/leases/dsse-local-export.lease.jsoncargo run -p cog-cli -- attest dsse sign --kind observation --run runs/phase5-observe --key fixtures/attestation/dev_ed25519_private.json --out runs/attestations/phase5-observe.dsse.json --lease runs/leases/dsse-local-export.lease.json --lease-pubkey fixtures/attestation/dev_ed25519_public.json --lease-at-unix 1735689600 --lease-decision-out runs/lease-decisions/dsse-observation-sign.decision.jsoncargo run -p cog-cli -- attest dsse verify --envelope runs/attestations/phase5-observe.dsse.json --pubkey fixtures/attestation/dev_ed25519_public.json --kind observation --run runs/phase5-observecargo run -p cog-cli -- verify passes --kind dsse --envelope runs/attestations/phase5-observe.dsse.json --pubkey fixtures/attestation/dev_ed25519_public.json --bundle-kind observation --run runs/phase5-observecargo run -p cog-cli -- attest dsse sign --kind codelet --run runs/codelet-validate --key fixtures/attestation/dev_ed25519_private.json --out runs/attestations/codelet-validate.dsse.json --lease runs/leases/dsse-local-export.lease.json --lease-pubkey fixtures/attestation/dev_ed25519_public.json --lease-at-unix 1735689600 --lease-decision-out runs/lease-decisions/dsse-codelet-validate-sign.decision.jsoncargo run -p cog-cli -- attest dsse verify --envelope runs/attestations/codelet-validate.dsse.json --pubkey fixtures/attestation/dev_ed25519_public.json --kind codelet --run runs/codelet-validatecargo run -p cog-cli -- attest dsse sign --kind codelet --run runs/codelet-demo --key fixtures/attestation/dev_ed25519_private.json --out runs/attestations/codelet-demo.dsse.json --lease runs/leases/dsse-local-export.lease.json --lease-pubkey fixtures/attestation/dev_ed25519_public.json --lease-at-unix 1735689600 --lease-decision-out runs/lease-decisions/dsse-codelet-demo-sign.decision.jsoncargo run -p cog-cli -- attest dsse verify --envelope runs/attestations/codelet-demo.dsse.json --pubkey fixtures/attestation/dev_ed25519_public.json --kind codelet --run runs/codelet-democargo run -p cog-cli -- attest dsse sign --kind transaction --run runs/transaction-dry-run --key fixtures/attestation/dev_ed25519_private.json --out runs/attestations/transaction-dry-run.dsse.json --lease runs/leases/dsse-local-export.lease.json --lease-pubkey fixtures/attestation/dev_ed25519_public.json --lease-at-unix 1735689600 --lease-decision-out runs/lease-decisions/dsse-transaction-sign.decision.jsoncargo run -p cog-cli -- attest dsse verify --envelope runs/attestations/transaction-dry-run.dsse.json --pubkey fixtures/attestation/dev_ed25519_public.json --kind transaction --run runs/transaction-dry-runcargo run -p cog-cli -- verify transaction --run runs/transaction-dry-runcargo run -p cog-cli -- codelet validate --manifest codelets/examples/count_json_rows/codelet.toml --out runs/codelet-validatecargo run -p cog-cli -- codelet run --manifest codelets/examples/count_json_rows/codelet.toml --out runs/codelet-demo --backend native-fixturecargo run -p cog-cli -- verify codelet --run runs/codelet-validatecargo run -p cog-cli -- verify codelet --run runs/codelet-democargo run -p cog-cli -- eval phase5cargo run -p cog-cli -- verify observation --run runs/phase5-observecargo run -p cog-cli -- eval golden-path
- Full sensorium vault workflows (
sensorium-cli init-vault/run/replay/print-state). - Live desktop adapter probes.
- Phase 5 remains recorded/fixture observation only.
- Phase 5 is currently the strongest verifier/witness subsystem in the harness. Do not generalize weaker non-Phase-5 witness outputs as equivalent roots of trust.
- No control channels are emitted in model-visible observation artifacts.
- No live desktop mutation authority is introduced.
- Witness commitments are deterministic and artifact-bound.
- Phase 5 uses the shared
cog-canonicalboundary. The active profile remainsphase5-interim-jcs-like-v1, is not full RFC 8785/JCS, rejects floats in witnessed material, sorts object/map keys deterministically, introduces no timestamps or nondeterministic fields, and produces stable bytes across repeated runs. - Phase 7B does not change Phase 5 artifact names,
observation_witness_manifest.json,evidence_manifest.json,artifact_hashes.json,trace.jsonl,witness_root.txt, orverify observationbehavior. - Phase 7C does not change Phase 5 output or witness roots. Codelet bundles use
codelet-interim-jcs-like-v1so they are not confused with the Phase 5 observation profile. - Phase 7C.1 strengthens codelet verification only. It preserves codelet command syntax, evidence file names, and the
codelet-interim-jcs-like-v1profile. - Phase 7D does not change Phase 5 output, Phase 5 witness roots, codelet command syntax, codelet evidence file names, or the
codelet-interim-jcs-like-v1profile. Desktop transaction bundles usedesktop-transaction-interim-jcs-like-v1so they are not confused with Phase 5 or codelet profiles. - Phase 7E does not change Phase 5 output, Phase 5 witness roots, codelet evidence file names, transaction evidence file names, or existing verifier pass/fail behavior. Graph reports and benchmark reports are diagnostic outputs only.
- Phase 8A.1 does not change Phase 5, codelet, transaction, graph, or verifier-bench profiles. It adds candidate-path UTF-16 property ordering, I-JSON safe-integer checks, profile-specific APIs, profile reports, and conformance fixtures only.
cogitator-rfc8785-jcs-v1remains a candidate until RFC 8785/JCS gaps are closed. - Phase 8Q does not add a new feature surface. It updates audit, onboarding, checklist, ADR, risk, acceptance, roadmap, and status documentation only.
- Phase 8R does not migrate Phase 5, codelet, transaction, graph, or verifier-bench profiles. It adds read-only migration planning vocabulary and CLI diagnostics only.
- Phase 8R.1 does not migrate Phase 5, codelet, transaction, graph, or verifier-bench profiles.
canonical compare-profileis a compatibility inspector only. It runs existing verifiers first, treats hypothetical target roots as diagnostic, and does not write witness manifests orwitness_root.txt. - Phase 8S/9D/9E does not migrate Phase 5, codelet, transaction, graph, or verifier-bench profiles.
attest dsse signis an export command only. It requires a valid local lease at the CLI boundary, runs existing verifiers before signing, refuses failed bundles, writes only the explicit authorized--outenvelope, and does not write witness manifests orwitness_root.txt. - Phase 9A/9B/9C/9D/9E do not migrate Phase 5, codelet, transaction, graph, verifier-bench, or canonical profiles. Lease reports are diagnostic/control-plane material and do not alter verifier semantics or witness roots.
- Phase 11C/11C.1/11C.2 does not migrate Phase 5, codelet, transaction, graph, verifier-bench, or canonical profiles. Provider loopback smoke reports, provider envelope reports, proposal parse reports, and parsed proposals are diagnostic/control-plane material only and do not alter verifier semantics, leases, DSSE, evidence, witness manifests, or witness roots.
- Phase 12A is design-only. It does not add mutation support, execution receipts, rollback receipts, real desktop mutation, provider expansion, live authority, witness-root changes, evidence semantic changes, verifier pass/fail semantic changes, lease semantic changes, DSSE semantic changes, or Phase 5 behavior changes.
- Phase 12B adds only a fake reversible mutation pilot. Its execution and rollback receipts are internal-consistency artifacts for the fake state file only; they are not evidence, witness material, DSSE trust, lease authority, external attestation, production trust, compliance proof, model-alignment proof, host-safety proof, or real-world mutation proof.
- Phase 12C hardens only that fake pilot. It tightens exact lease binding, shared run binding, stale-artifact refusal, symlink/reparse ancestor containment, and fake-chain verifier semantics without adding real desktop, Hyprland, NixOS, shell, network, provider, MCP/AG-UI, screenshot, AT-SPI, keyboard/mouse, app launch, browser, or portal authority.
- Phase 13A is implemented as protocol seed only. It checks internal protocol consistency for typed diagnostic/control-plane records and fixtures. It does not add runtime authority, real mutation, generic computer use, MCP runtime, witness-root changes, evidence semantic changes, lease semantic changes, DSSE semantic changes, provider semantic changes, or Phase 5 behavior changes.
- Phase 13A.1 hardens Phase 13A verifier boundaries only. Foreground-change authorization is absent, future-refused status/mode/action vocabulary cannot verify as clean in authority-relevant positions, adapter manifest support lists are checked, budget decisions are bound by schema/run/status/hash, and future human approval remains refused.
- Phase 13B adds regression coverage for those protocol boundaries only. Its conformance reports, pass summaries, and golden report are diagnostic internal-consistency outputs; they cannot authorize actions, hide unexpected issue codes, replace raw checks, or prove complete safety.
- Phase 13C evaluates noop/replay protocol bundles without actuation. Its decision reports, loaded-artifact hashes, pass summaries, AcceptedNoop, AcceptedReplay, and DiagnosticOnly states are diagnostic only and cannot authorize later execution or prove that historical actions happened.
- Phase 13D simulates deterministic fake-world transitions only inside
synthetic artifacts written under
--out. Synthetic after-state, diagnostic receipts, transcripts, rollback plans, verifier reports, and PhantomRefusal records are not evidence, witness material, leases, DSSE trust, external attestation, production trust, proof of real attempted execution, or future real-adapter authorization. - Phase 13E projects existing diagnostic decision and synthetic artifacts into typed diagnostic transcripts only. Kernel transcripts, transcript verify reports, drift reports, entry hashes, transcript hashes, entry-chain hashes, and PhantomRefusal records are not evidence, witness material, leases, DSSE trust, external attestation, production trust, proof of real-world occurrence, or runtime authorization.
- Phase 13F adds conformance diagnostics for those transcript paths only. Transcript conformance manifests, reports, fixtures, verifier-bench cases, and pass summaries are not evidence, witness material, leases, DSSE trust, transcript roots, proof of execution, or runtime authorization.
- Phase 14B adds a separate local kernel decision witness profile for selected
Phase 13C decision facts only.
kernel_witness_manifest.json,kernel_witness_root.txt, andkernel_witness_verify_report.jsonare not Phase 5witness_root.txt, do not alter Phase 5 evidence semantics, and do not make transcripts, verifier-bench outputs, conformance reports, DSSE envelopes, leases, synthetic effects, PhantomRefusal, provider-loopback material, or real adapter attempts into witness material, evidence, runtime authority, production trust, or proof of execution. - Phase 14C adds conformance diagnostics for the existing Phase 14B verifier only. Kernel witness conformance manifests, reports, fixtures, verifier-bench cases, and pass summaries are not evidence, witness material, leases, DSSE trust, production trust, proof of execution, or runtime authorization.
- Phase 15A is design-only. Authority modes are future runtime/config/policy gates, not evidence, witness material, leases, or authorization by existence. Phase 15A adds no mode-aware CLI, config, provider gate, adapter registry, real adapter, real mutation, witness event, evidence semantic, lease semantic, DSSE semantic, verifier-bench, or Phase 5 behavior change.
- Phase 15B implements strict local authority policy config parsing and
diagnostic status reporting only. No config means
locked. The only runtime gate added is the narrow provider-local proposal gate requiring explicit modeproposeplusallow_provider_local: true;confirm,trusted-local, andfull-controlare parsed/reportable only and do not unlock adapters, shell, desktop control, leases, provider tools, or mutation. - Phase 15C authority leases are strict local diagnostic records only. They do not authorize mutation, execute adapters, gate provider-local, become witness/evidence/DSSE material, or change verifier-bench or Phase 5 semantics.
- Phase 15D authority brake records are strict local diagnostic records only. They do not authorize mutation, execute adapters, gate provider-local or leases, create a mutating lock/unlock/panic CLI, become witness/evidence/DSSE material, or change verifier-bench or Phase 5 semantics. Inactive is not an unlock.
- Phase 15E preflight reports are strict local diagnostic compositions only. They do not execute adapters, authorize mutation, route provider-local, prove real adapter blocking, become witness/evidence/DSSE material, or change verifier-bench or Phase 5 semantics. Matched preflight has no runtime effect.
- Phase 16A is docs-only. Adapter descriptor examples and registry design text are not runtime registry entries, schemas, parsers, fixtures, CLI commands, evidence, witness material, leases, preflight reports, receipts, or authorization by existence.
- Phase 16B adapter descriptors and inspect reports are strict local diagnostic/control-plane material only. They do not load a runtime registry, route or execute adapters, authorize mutation, integrate provider-local, create real receipts, create a containment runner, become witness/evidence/DSSE/verifier-bench material, or change Phase 5 semantics.
- Phase 16C descriptor-aware preflight reports are strict local diagnostic/control-plane material only. They compose explicit descriptor, policy, lease, brake, requested context, and evaluation-time inputs without loading a runtime registry, routing or executing adapters, authorizing mutation, integrating provider-local, creating real receipts, becoming witness/evidence/DSSE/verifier-bench material, or changing Phase 5 semantics. Matched output has no runtime effect.
- Phase 16D fake-call reports and fake diagnostic receipts are strict local diagnostic/control-plane material only. They are not runtime registry entries, real adapter calls, real-operation receipts, evidence, witness material, DSSE, leases, preflight authority, provider-local inputs, execution plans, authorization, proof of execution, or mutation permission. The fake-call command recomputes preflight from source inputs and accepts only the static diagnostic fake binding.
- Phase 16E containment design text is strict docs-only future contract material. It is not a runner, not a runtime registry, not containment implementation, not adapter execution, not evidence, not witness material, not DSSE, not provider-local authority, not mutation authority, and not authorization by existence.
- Phase 16F maintainability / architecture audit text is strict docs-only audit material. It is not a fix, not a refactor, not a runner, not a runtime registry, not adapter execution, not evidence, not witness material, not DSSE, not provider-local authority, not mutation authority, and not authorization by existence.
- Phase 16F.1 fixed-output hardening is path hygiene only. It does not make
authority reports, provider-local reports, proposal parse reports, or
action_proposal.jsonauthoritative by existence; it adds no runner, runtime registry, adapter execution, real mutation, provider-local endpoint/network broadening, or witness/evidence/DSSE/verifier-bench/Phase 5 semantic change. - Phase 16G model context renderer design text is strict docs-only future context-plane material. It is not a renderer, not a schema, not a parser, not a fixture set, not a CLI surface, not provider-local context integration, not cloud provider support, not a broker, not a runtime registry, not a containment runner, not adapter execution, not raw OS telemetry disclosure, not evidence, not witness material, not DSSE, not execution authority, not mutation authority, and not authorization by existence.
- Phase 16H inference provider broker design text is strict docs-only future routing material. It is not a broker implementation, not a provider runtime, not cloud provider support, not credential support, not provider-local broadening, not a context renderer, not an observation budget implementation, not a memory system, not a runtime registry, not a containment runner, not adapter execution, not raw OS telemetry disclosure, not evidence, not witness material, not DSSE, not disclosure authority, not execution authority, not mutation authority, and not authorization by existence.
- Phase 16I real adapter readiness gate text is strict docs-only prerequisite material. It is not a runtime gate implementation, not a registry, not a runner, not a context renderer, not an observation budget implementation, not a broker, not a provider runtime, not adapter execution, not raw OS telemetry disclosure, not evidence, not witness material, not DSSE, not disclosure authority, not execution authority, not mutation authority, and not authorization by existence.
- Phase 17A Home Manager adapter design text is strict docs-only target-family material. It is not a Home Manager adapter, not a descriptor implementation, not a parser, not a schema, not a fixture corpus, not a CLI command, not registry loading, not a containment runner, not a context renderer, not an observation budget implementation, not a broker, not a provider runtime, not Home Manager command execution, not Nix command execution, not build, not switch/apply, not rollback, not uninstall, not generation cleanup, not NixOS rebuild, not evidence, not witness material, not DSSE, not execution authority, not mutation authority, and not authorization by existence.
- Phase 17B Home Manager diagnostic/fake rehearsal material is fake-only target-family material. The fake descriptor, fake policy, fake lease, fake brake, fake-call report, and fake diagnostic receipt are not Home Manager execution, not Nix execution, not live observation, not build output, not switch/apply output, not rollback output, not real config material, not model context disclosure, not a runtime registry, not a containment runner, not evidence, not witness material, not DSSE, not execution authority, not mutation authority, and not authorization by existence.
- Phase 17C Home Manager observe/read-only design text is strict docs-only
material. It is not a live Home Manager observe adapter, not
home-manager generations, nothome-manager --version, nothome-manager option, nothome-manager packages, not Home Manager command execution, not Nix command execution, not real config reads, not$HOMEreads, not context disclosure, not a runtime registry, not a containment runner, not a context renderer, not an observation budget implementation, not evidence, not witness material, not DSSE, not disclosure authority, not execution authority, not mutation authority, and not authorization by existence. - Phase 17C.1 Home Manager static observe target descriptor files and inspect
reports are strict diagnostic/control-plane material only. They are not Home
Manager execution, not Nix execution, not live observation, not real config
reads, not
$HOMEreads, not generation/version/option/package reads, not a runtime registry, not adapter execution, not a build, not switch/apply, not rollback, not uninstall, not generation cleanup, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not execution authority, not mutation authority, and not authorization by existence. - Phase 17C.2 Home Manager read-only process contract text is strict
docs/design/contract material only. It is not a process runner, not
containment implementation, not
home-manager --version, nothome-manager generations, not Home Manager execution, not Nix execution, not live observation, not raw output persistence, not model-visible context, not a build, not switch/apply, not rollback, not uninstall, not generation cleanup, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not execution authority, not mutation authority, and not authorization by existence. - Phase 17C.3 Home Manager version observe reports are strict diagnostic/control-plane material only. They are not generation observation, not option/package/config reads, not Nix execution, not relative executable path authority, not Windows UNC/verbatim/device namespace executable path authority, not raw cwd persistence, not raw stdout/stderr capture or persistence by default, not model-visible context, not a process runner, not containment implementation, not a build, not switch/apply, not rollback, not uninstall, not generation cleanup, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not mutation authority, and not authorization by existence.
- Phase 17C.8 Home Manager observe hardening is conformance/test/docs material
only for the existing fixed
home-manager --versionandhome-manager generationsobserve routes. It adds no command, no live route, no process runner, no raw output persistence, no model-visible context, no provider-local behavior, no build, no switch/apply, no rollback, no cleanup, no evidence, no witness material, no DSSE, no verifier-bench or Phase 5 semantic change, and no mutation authority. - Phase 17D Home Manager build boundary design is docs/design material only.
It records future build/dry-run authority requirements but adds no command,
no live route, no
home-manager build, no switch/apply, no rollback, no cleanup, no generation removal or expiry, no arbitrary Nix invocation, no generic process runner, no shell/which/PATH lookup, no model-supplied argv, no model-visible Home Manager/Nix context, no raw output persistence, no provider/cloud behavior, no evidence, no witness material, no DSSE, no verifier-bench or Phase 5 semantic change, and no mutation authority. - Phase 17D.1 Home Manager build boundary contract rehearsal is
parser/tests/fixtures/docs material only. It checks a synthetic contract
fixture and hostile refusal fixtures for explicit no-authority flags and
future build-gate requirements. It adds no command, no executable command
descriptor, no live route, no process execution, no Home Manager or Nix
invocation, no
home-manager build, no switch/apply, no rollback, no cleanup, no generation removal or expiry, no generic process runner, no shell/which/PATH lookup, no model-supplied argv, no model-visible Home Manager/Nix context, no raw output persistence, no provider/cloud behavior, no evidence, no witness material, no DSSE, no verifier-bench or Phase 5 semantic change, and no mutation authority. - Phase 17D.2 Home Manager build authorization/preflight design text is strict
docs/design material only. It is not
home-manager build, not a dry-run/build CLI route, not Home Manager execution, not Nix execution, not process execution, not a shell, not PATH search, notwhich, not model-supplied argv, not store realization, not ambient./resultlink creation, not raw output persistence, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not mutation authority, and not authorization by existence. - Phase 17D.3 Home Manager build preflight report-shape rehearsal is strict
parser/tests/fixtures/docs material only. It is not a command, not a live
route, not build preflight runtime, not
home-manager build, not a dry-run/build route, not Home Manager execution, not Nix execution, not process execution, not a shell, not PATH search, notwhich, not model-supplied argv, not store realization, not ambient./resultlink creation/inspection/deletion, not raw output persistence, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not mutation authority, and not authorization by report, parser, fixture, or test existence. - Phase 17D.4 Home Manager build preflight composer rehearsal is strict
cog-modelcomposer/tests/docs material only. It is not a command, not an adapter route, not a report writer, not a live route, not build preflight runtime, nothome-manager build, not a dry-run/build route, not Home Manager execution, not Nix execution, not process execution, not a shell, not PATH search, notwhich, not model-supplied argv, not store realization, not ambient./resultlink creation/inspection/deletion, not raw output persistence, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not mutation authority, and not authorization by report, parser, composer, fixture, test, or doc existence. - Phase 17D.5 Home Manager build preflight writer rehearsal is strict
synthetic CLI writer/model/parser/tests/docs material only. It adds one
diagnostic writer command that writes fixed artifacts under
--out; it is not a live route, not build preflight runtime, nothome-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not process execution, not a shell, not PATH search, notwhich, not model-supplied argv, not descriptor/executable/config/flake input acceptance, not store realization, not result symlink behavior, not raw output/log persistence, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not mutation authority beyond fixed diagnostic artifacts under--out, and not authorization by writer, report, receipt, parser, fixture, test, or doc existence. - Phase 17D.6 Home Manager build preflight request contract rehearsal is
strict synthetic
cog-modelparser/composer/tests/fixtures/docs material only. It is not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, nothome-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not process execution, not a shell, not PATH search, notwhich, not model-supplied argv, not command/target descriptor acceptance, not executable/config/flake input acceptance, not store realization, not result symlink behavior, not raw output/log persistence, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not mutation authority, and not authorization by request, contract, parser, composer, fixture, test, or doc existence. - Phase 17D.7 Home Manager build preflight request-to-refusal rehearsal is
strict synthetic
cog-modelparser/composer/tests/fixtures/docs material only. It is not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, nothome-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not process execution, not a shell, not PATH search, notwhich, not model-supplied argv, not command/target descriptor acceptance, not executable/config/flake input acceptance, not store realization, not result symlink behavior, not raw output/log persistence, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by request, contract, composition, parser, composer, fixture, test, or doc existence. - Phase 17D.8 Home Manager build preflight architecture checkpoint is
docs-only architecture checkpoint / live-build readiness gate design material
only. It is not code, not fixtures, not tests, not a command, not an adapter
route, not a report writer command, not a live route, not build preflight
runtime, not
home-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not process execution, not a shell, not PATH search, notwhich, not model-supplied argv, not command/ target descriptor acceptance, not executable/config/flake input acceptance, not store realization, not result symlink behavior, not raw output/log persistence, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by checkpoint, gate, or doc existence. - Phase 17D.9 live Home Manager build preflight process contract is docs-only
process-contract material only. It is not code, not fixtures, not tests, not a
command, not an adapter route, not a report writer command, not a live route,
not build preflight runtime, not
home-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not process execution, not a generic runner, not a shell, not PATH search, notwhich, not arbitrary argv, not model-supplied argv, not command/ target descriptor acceptance, not executable/config/flake/path input acceptance, not store realization, not result symlink behavior, not raw output/log persistence, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by process contract or doc existence. - Phase 17D.10 Home Manager build preflight process transcript rehearsal is
strict synthetic
cog-modelparser/composer/tests/fixtures/docs material only. It is not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, not a process runner, not a fake process runner, nothome-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not process execution, not a shell, not PATH search, notwhich, not arbitrary argv, not model-supplied argv, not command/target descriptor acceptance, not executable/config/flake/path input acceptance, not store realization, not result symlink behavior, not raw output/log persistence, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by transcript, parser, composer, fixture, test, or doc existence. - Phase 17D.11 Home Manager build preflight fake process harness rehearsal is
fake/test-only
cog-modelprocess mechanics material only. It is not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, not a generic process runner, not a reusable subprocess API, nothome-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not shell/PATH/which, not arbitrary command execution, not arbitrary argv, not model/provider-supplied argv, not Home Manager/Nix executable path acceptance, not descriptor/config/flake/path input acceptance, not ambient environment inheritance, not secret inheritance, not network/cache/substituter behavior, not store realization, not result symlink behavior, not raw stdout/stderr/log persistence by default, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by fake output, classification, test, or doc existence. - Phase 17D.12 Home Manager build preflight fake process harness hardening is
fake/test-only
cog-modelhardening material only. It is not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, not a generic process runner, not a reusable subprocess API, nothome-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not shell/PATH/which, not arbitrary command execution, not arbitrary argv, not model/provider-supplied argv, not Home Manager/Nix executable path acceptance, not descriptor/config/ flake/path input acceptance, not ambient environment inheritance, not secret inheritance, not network/cache/substituter behavior, not store realization, not result symlink behavior, not raw stdout/stderr/log persistence by default, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by fake descendant behavior, drain-deadline classification, output summary, test, or doc existence. - Phase 17D.13 live Home Manager build preflight readiness gate is docs-only
gate/checklist material only. It is not code, not fixtures, not tests, not a
command, not an adapter route, not a report writer command, not a live route,
not build preflight runtime, not a process runner, not a fake process runner,
not
home-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not shell/PATH/which, not arbitrary command execution, not arbitrary argv, not model/provider-supplied argv, not Home Manager/Nix executable path acceptance, not descriptor/config/ flake/path input acceptance, not ambient environment inheritance, not secret inheritance, not network/cache/substituter behavior, not store realization, not result symlink behavior, not raw stdout/stderr/log persistence by default, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by gate, checklist, PR template, hostile-review checklist, or doc existence. - Phase 17D.14 live Home Manager build preflight no-go is docs-only no-go
material only. It is not code, not fixtures, not tests, not a command, not an
adapter route, not a report writer command, not a live route, not build
preflight runtime, not a subprocess API, not
home-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not shell/PATH/which, not arbitrary command execution, not arbitrary argv, not model/provider-supplied argv, not Home Manager/Nix executable path acceptance, not descriptor/config/flake/path input acceptance, not ambient environment inheritance, not network/cache/substituter behavior, not store realization, not result symlink behavior, not raw stdout/stderr/log persistence by default, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by no-go doc, gate, report, or future PR text existence. - Phase 17D.15 Home Manager build preflight authority gate contract rehearsal
is strict synthetic
cog-modelparser/composer/tests/fixtures/docs material only. It is no-runtime-authority material, not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, not a process runner, not a fake process runner, not a subprocess API, nothome-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not shell/PATH/which, not arbitrary command execution, not arbitrary argv, not model/provider-supplied argv, not Home Manager/Nix executable path acceptance, not descriptor/config/ flake/path input acceptance, not ambient environment inheritance, not network/cache/substituter policy resolution, not exact argv/result-link proof, not store realization, not result-link behavior, not raw stdout/stderr/log persistence by default, not model-visible Home Manager/Nix context, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by contract, gate, parser, composer, fixture, test, or doc existence. - Phase 17D.16 Home Manager build preflight network policy contract rehearsal
is strict synthetic
cog-modelparser/composer/tests/fixtures/docs material only. It is no-runtime-authority material, not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, not a process runner, not a fake process runner, not a subprocess API, not enforcement, nothome-manager build, nothome-manager switch, notnix build, not Home Manager execution, not Nix execution, not shell/PATH/which, not arbitrary command execution, not arbitrary argv, not model/provider-supplied argv, not Home Manager/Nix executable path acceptance, not descriptor/config/flake/path input acceptance, not exact argv/result-link proof, not store realization, not result-link behavior, not raw stdout/stderr/log persistence by default, not raw config/token/proxy/ substituter/builder material persistence, not model/provider/cloud-visible raw material, not provider/cloud behavior change, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by contract, policy success, parser, composer, fixture, test, or doc existence. - Phase 17D.17 Home Manager build preflight argv result-link contract rehearsal
is strict synthetic
cog-modelparser/composer/tests/fixtures/docs material only. It is no-runtime-authority material, not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, not a process runner, not a fake process runner, not a subprocess API, not enforcement, nothome-manager build, nothome-manager switch, notnix build, notnix-build, not Home Manager execution, not Nix execution, not shell/PATH/which, not arbitrary command execution, not arbitrary argv, not model/provider-supplied argv, not Home Manager/Nix executable path acceptance, not descriptor/config/flake/path input acceptance, not result-link behavior, not raw stdout/stderr/log persistence by default, not result path creation/inspection/follow/read/delete/cleanup/ interpretation, not authority-gate alteration, not network/cache/substituter policy alteration, not model/provider/cloud-visible raw material, not provider/cloud behavior change, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by contract, proof success, parser, composer, fixture, test, or doc existence. - Phase 17D.18 Home Manager build preflight readiness bundle contract
rehearsal is strict synthetic
cog-modelparser/composer/tests/fixtures/docs material only. It is no-runtime-authority material, not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, not a process runner, not a fake process runner, not a subprocess API, not enforcement, not Home Manager execution, not Nix execution, not Home Manager build invocation, nothome-manager switch, notnix build, notnix-build, not shell/PATH/which, not arbitrary command execution, not arbitrary argv, not model/provider-supplied argv, not Home Manager/Nix executable path acceptance, not descriptor/config/flake/path input acceptance, not result-link behavior, not raw stdout/stderr/log persistence by default, not result path creation/inspection/follow/read/delete/cleanup/ interpretation, not authority-gate semantic change, not network/cache/ substituter policy semantic change, not argv/result-link contract semantic change, not model/provider/cloud-visible raw material, not provider/cloud behavior change, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by bundle success, parser, composer, fixture, test, or doc existence. - Phase 17D.19 Home Manager build preflight live candidate pre-review is
docs-only Design Outcome B material. It is no-runtime-authority material, not
code, not fixtures, not tests, not a command, not an adapter route, not a
report writer command, not a live route, not build preflight runtime, not a
process runner, not a fake process runner, not a subprocess API, not
enforcement, not Home Manager execution, not Nix execution, not Home Manager
build invocation, not
home-manager switch, notnix build, notnix-build, not shell/PATH/which, not arbitrary command execution, not arbitrary argv, not model/provider-supplied argv, not Home Manager/Nix executable path acceptance, not descriptor/config/flake/path input acceptance, not result-link behavior, not raw stdout/stderr/log persistence by default, not result path creation/inspection/follow/read/delete/cleanup/ interpretation, not model/provider/cloud-visible raw material, not provider/ cloud behavior change, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by design text, Outcome B, future prompt skeleton, checklist, parser, composer, fixture, test, or doc existence. - Phase 17D.20 Home Manager build preflight environment policy contract is
strict synthetic
cog-modelparser/composer/tests/fixtures/docs material only. It requires env clearing, refuses inherited HOME, XDG, PATH, Nix config env, proxy env, SSH/GPG/signing-agent env, secret-like env, raw env/path/log persistence, model/provider-visible raw host context, and runtime authority. It records that live HOME/XDG policy remains unresolved and requires no-go unless a future runtime gate proves exact safety. It is not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, not a process runner, not a subprocess API, not enforcement, not Home Manager execution, not Nix execution, not Home Manager build invocation, not shell/PATH/which, not result-link behavior, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by policy, parser, composer, fixture, test, or doc existence. - Phase 17D.21 Home Manager build preflight environment-inclusive readiness
bundle contract is strict synthetic
cog-modelparser/composer/tests/ fixtures/docs material only. It requires Phase 17D.15, Phase 17D.16, Phase 17D.17, and Phase 17D.20 prerequisite contracts to be present and internally valid synthetic material, while recording live build-preflight remains no-go. It is not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, not a process runner, not a fake process runner, not a subprocess API, not enforcement, not Home Manager execution, not Nix execution, not Home Manager build invocation, not shell/PATH/which, not result-link creation/access/cleanup/interpretation, not raw stdout/stderr or HOME/XDG/env/path/log persistence, not model/ provider/cloud-visible raw host material, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted preflight state, not build success state, not mutation authority, and not authorization by bundle, parser, composer, fixture, test, or doc existence. - Phase 17D.22 Home Manager build preflight integrated fake gate rehearsal is
fake/test-only coverage inside the sealed Phase 17D.11/17D.12 integration
test harness. It consumes the Phase 17D.21 environment-inclusive readiness
bundle before the fake harness path may run and proves invalid readiness is
refused before fake child spawn. It is not a command, not an adapter route,
not a report writer command, not a live route, not build preflight runtime,
not a runtime gate implementation, not production process execution, not a
process runner, not a new fake process runner, not a subprocess API, not
Home Manager execution, not Nix execution, not Home Manager build invocation,
not shell/PATH/
which, not production environment inheritance enforcement, not network/cache/substituter enforcement, not argv/result-link runtime enforcement, not result-link creation/access/follow/read/delete/cleanup/ interpretation, not raw stdout/stderr or HOME/XDG/env/path/log persistence, not model/provider/cloud-visible raw host material, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted live preflight state, not build success state, not mutation authority, and not authorization by fake-gate, harness, parser, composer, test, or doc existence. Live build-preflight remains no-go. - Phase 17D.23 Home Manager build preflight closeout live-vs-synthetic map is
docs-only closeout material. It maps existing Phase 17D docs-only design,
synthetic
cog-modelcontract, fixed synthetic diagnostic writer, and fake/test-only harness material against the live runtime surfaces that still do not exist. It is not Rust code, not tests, not fixtures, not a parser, not a composer, not a schema change, not a command, not an adapter route, not a report writer command, not a live route, not build preflight runtime, not process execution, not a process runner, not a fake process runner, not a subprocess API, not Home Manager execution, not Nix execution, not Home Manager build invocation, not shell/PATH/which, not environment/network/ argv runtime enforcement, not result-link behavior, not raw stdout/stderr or HOME/XDG/env/path/log persistence, not model/provider/cloud-visible raw host material, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted live preflight state, not build success state, not mutation authority, and not authorization by closeout-map or doc existence. Live build-preflight remains no-go. - Phase 17D.24 Home Manager build preflight live runtime gate design is
docs-only design material. It documents a possible future live gate input
model, ordered gate stages, pre-spawn refusal checklist, process construction
invariants, HOME/XDG/env design, Nix/network/cache/substituter design,
result-path design, output/report shape boundaries, and required hostile
tests. It is not Rust code, not tests, not fixtures, not a parser, not a
composer, not a schema change, not a command, not an adapter route, not a
report writer command, not a live route, not build preflight runtime, not a
runtime gate implementation, not process execution, not a process runner, not
a fake process runner, not a subprocess API, not Home Manager execution, not
Nix execution, not Home Manager build invocation, not shell/PATH/
which, not arbitrary executable/config/flake/path input acceptance, not model/provider- supplied argv, not environment/network/argv runtime enforcement, not output capture implementation, not result-link behavior, not raw stdout/stderr or HOME/XDG/env/path/log persistence, not model/provider/cloud-visible raw host material, not provider/cloud behavior, not switch/apply, not rollback, not cleanup, not disclosure authority, not evidence, not witness material, not DSSE, not lease authority, not preflight authority, not provider authority, not accepted live preflight state, not build success state, not mutation authority, and not authorization by design text or doc existence. Live build-preflight remains no-go. - Phase 15P-A itself is design-only. In that phase, local provider and endpoint classes were future design vocabulary, not implemented provider runtime. It adds no network implementation, local provider adapter, cloud provider adapter, credential support, mode-aware provider gate, provider-loopback semantic broadening, witness/evidence/lease/DSSE semantic change, verifier-bench semantic change, real adapter, real mutation, or Phase 5 behavior change.
- Phase 15P-B adds local OpenAI-compatible proposal generation only. It does not migrate Phase 5, codelet, transaction, graph, verifier-bench, leases, DSSE, or canonical profiles. Phase 15B gates its live network path behind an explicit propose-mode local authority policy. Provider-local reports, endpoint reports, envelope reports, proposal parse reports, and parsed proposals are diagnostic/control-plane material only and do not alter verifier semantics, leases, DSSE, evidence, witness manifests, witness roots, Phase 14B/14C kernel witness semantics, or provider-loopback-smoke behavior.
- Deadbolt remains a userspace governance architecture direction, not a Linux kernel, OS kernel, microkernel, kernel module, privileged-mode runtime, hypervisor, arbitrary computer-use system, production trust claim, compliance claim, model-alignment claim, or proof of host safety.
- Phase 8S.1 keeps DSSE as export/diagnostic output. It adds report fields and benchmark cases only; it does not make DSSE envelopes evidence, trusted key policy, transparency receipts, or profile migration artifacts.
- Phase 8G keeps pass summaries diagnostic. It does not add a verifier engine, change issue-code semantics, change witness roots, migrate profiles, or let graph inspection become an alternate verifier. Unmapped issue codes remain visible.
- The current raw JSON API rejects duplicate keys and invalid JSON. The candidate profile also rejects floats, negative zero, unsafe large integers, and unsupported numeric material fail-closed. Already parsed
serde_json::Valueinput cannot recover duplicate-key information. - Unknown fields are denied in witness-critical Phase 5 structs (
ObservationWitnessManifest,EvidenceManifest,ObservationArtifact, andObservationTraceEvent) so stale or mixed-version bundles fail clearly.verify_report.jsonremains ignored as verifier output, not evidence. verify_observation_bundle(run_dir)verifies internal graph consistency. It cannot prove a bundle is the original run if every semantic artifact, witness manifest, andwitness_root.txtare coherently regenerated without comparing the witness root to an external trusted record.verify_codelet_bundle(run_dir)verifies internal graph consistency for interim codelet evidence. It cannot prove originality if every semantic artifact,codelet_witness_manifest.json, trace, hash report, andwitness_root.txtare coherently regenerated without comparing the witness root to an external trusted record.verify_desktop_transaction_bundle(run_dir)verifies internal graph consistency for interim dry-run transaction evidence. It cannot prove originality if every semantic artifact,desktop_transaction_witness_manifest.json, trace, hash report, andwitness_root.txtare coherently regenerated without comparing the witness root to an external trusted record.- Graph inspectors call the existing verifiers and surface their status. They must not be used as looser replacement verifiers.
- Sandbox conformance reports now mark unexercised behavior cases as
scaffold/skipped rather than passed. A passing availability check only proves backend detection, not sandbox enforcement. - Symlink escape checks for codelet write roots are covered on Unix-like platforms. On Windows, symlink creation may require privileges; resolved path containment remains the validation strategy and should be expanded with Windows-specific symlink regression coverage when feasible.
- Implement remaining RFC 8785/I-JSON gaps, especially ECMAScript number serialization, before marking
cogitator-rfc8785-jcs-v1conformant. - Rerun
canonical compare-profileonce the target profile reaches conformance. - Pilot profile migration on codelet or transaction bundles only after compatibility reports are reviewed.
- Migrate Phase 5 last, with explicit expected-root updates and backward compatibility tests.
- Review Phase 9E's centralized lease policy/request compiler before expanding mandatory leases to another command family.
- Add optional Sigstore/Rekor export only after local DSSE, pass summaries, and lease checks remain boring and canonical profile stability is settled.
- Add SCITT/COSE transparency receipt support later.
- Add replay tiers and clean up Sensorium JSONL replay so typed events reconstruct committed state.
- Extend codelet verification toward deterministic replay semantics before any real sandbox backend authority.
- After Phase 19B, keep authority-mode config/status, leases, brake records, preflight reports, provider-local reports/proposals, adapter registry design material, descriptors, descriptor inspect reports, descriptor-aware preflight reports, fake-call reports, fake diagnostic receipts, containment design text, maintainability audit text, context-renderer design text, broker design text, readiness-gate design text, Home Manager design/fake/observe/build-preflight material, Phase 18A audit material, Phase 18B index/map material, Phase 18C helper-extraction pre-review material, Phase 18D private synthetic parse-helper material, Phase 19A governance/provenance/replay roadmap material, and Phase 19B doctrine/schema-inventory material diagnostic/design/audit/index/pre-review/internal-parser-only/docs-only and default locked. Do not implement schemas automatically after the inventory. The next schema-related work should be a separate schema-registry design PR or run-manifest/replay-sidecar pre-review only if explicitly chosen. Docs sprawl remains deferred debt. Live Home Manager no-go remains unchanged. Future Home Manager observation beyond fixed
home-manager --versionand fixedhome-manager generations, live process-runner implementation, broad process-runner implementation, fake process-runner implementation beyond this sealed Phase 17D.11/17D.12 test harness, context renderer implementation, context schemas, provider broker work, cloud provider support, credentials, provider-local integration, mutating lock/unlock/panic runtime state, confirmation prompts, adapter registry implementation, registry loading, registry entries, real adapters, readiness gate implementation, containment runner implementation, real receipts, Home Manager dry-run/plan/build implementation, Home Manager switch/apply, exact argv/result-link runtime implementation, live HOME/XDG/environment policy enforcement, live network/cache/substituter enforcement, live output capture implementation, live result-link enforcement, governance module implementation, replay sidecar implementation, schema registry implementation, capability router implementation, attestation implementation, AI BOM implementation, graph export implementation, semantic consent UI, NixOS VM harnesses, any further helper consolidation/refactor, and remaining audit remediation require separate reviewed phases. - After Phase 15P-B, keep custom VM-host allowlists, private LAN providers, cloud providers, credentials, proxies, redirects, streaming, provider-side tools, MCP/AG-UI, execution, and mutation refused until separately designed and reviewed.
- For future governed local adapters, treat NixOS + Hyprland + Home Manager as the primary reference platform and Arch + Hyprland as later compatibility. Under Phase 16I, Home Manager must progress through design-only, diagnostic/fake, observe/read-only, dry-run/plan/build with no apply, and only then a separate confirm-mode switch/apply candidate. NixOS system-level apply remains later and higher risk; NixOS apply should be staged as plan/build, then dry-activate/test, then switch only in a much later reviewed phase.
- Extend transaction evidence toward richer dry-run scenarios before any live mutation path exists.
- Optional ML/GNN anomaly detection should remain advisory-only research after the deterministic pass corpus matures.