Complete routes and handoffs Historical route snapshot at 9496cff6332fe0b97195b7ebe67b73f62f30e5b3. Current assistive source bindings identify inspected implementation bytes, with 3549ed56f5d5849116aef8d5e946423d8ee677fc as the committed source base. Live host qualification and release are separate evidence. Curated current-source workflow contracts and selected context-delivery implementation; not a release, installed-host qualification, or exhaustive runtime call graph. Original source links and spatial positions retained; task labels show the selected work owner. Source compatibility revalidated at 25980c292b529fca90c39f5f26d69a1c0674de44. Unittest collector compatibility bound to reviewed blob 76a2998f4bd5b6f441f5fd162bbe810b2de2ee93.
Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md Plans preserve agreed criteria, useful tasks, dependency ancestry, bounded shared inputs and observable checks. Stable source identities and typed maintenance keep changes within the selected outcome. A design-drift guard routes an undecided material solution choice back to brainstorming instead of scoring it during planning. core/surface/skills/writing-plans/SKILL.md The pinned native bridge enables task-context as a bounded informational read and does not require future reviewer/approval producers simply to author a structurally valid draft. Context requests route to ordinary context-preview, context-finalize-preview and exact-reference context-apply; historical receipt input stays a separate compatibility path. Installed host qualification is separate. Native Pi writer admission does not establish a complete live Pi workflow. On NO_LOCAL_STORE the client runs init-store once and retries the request once; a refused initialization keeps NO_LOCAL_STORE. On Windows the binary's architecture comes from the kernel (IsWow64Process2), never WMI or PROCESSOR_* environment. Index and outline pages are now fully checked before rows are yielded, including continuation identity and row shape. core/pysrc/_artifactlib.py A new explicit batch review can select a passing rerun of still-reviewed work without replacing the original task review. The selected run must match its own recorded workspace; changed source or supporting evidence still requires reassessment. core/artifacts/internal/evidence/completion.go The user-facing route table points feature and sprint work at useful planned execution and selected context refresh at its existing owner. Existing authorization covers ordinary work; actual host, destructive-action and commit controls remain. core/surface/includes/routing-table.md The skill index connects planning, direct or delegated implementation, proportional verification and selected context maintenance to their owning workflows. core/surface/skills/INDEX.md The sprint caller performs an index-first recorded-intent read, preserves actual owner decisions and ADR conflicts, then proceeds with authorized work without a second artifact approval system. A SMARTS Unknown names its missing observation and cannot bypass a hard gate or manufacture authority. core/surface/SPRINT.md The sprint entry now routes to the assistive implementation body instead of requiring a fresh user approval and two reviews per task. core/surface/commands/sprint.md The feature entry now resumes a maintained spec/plan and task progress without another artifact certification prompt; independent commit and test controls remain. The small lane runs an inline SMARTS scan only for a material solution choice. core/surface/commands/feature.md Source refinement respects recorded deferrals and accepted ADR conflicts without turning each ordinary method adjustment into a separate authorization interview. SMARTS compares approaches only when two or more are materially plausible; a single approach gets one line and no table. core/surface/skills/brainstorming/SKILL.md Attended feature execution now treats checkpoints as progress groups, not compulsory approval stops; it forwards real failures and continues independent work. core/surface/skills/executing-plans/SKILL.md Implementation works directly or delegates a coherent unit when useful. Bounded task context, applicable dependency advice and observed checks support progress while preserving actual user stops and host permissions. Verification checks the change against a recorded SMARTS rationale for material invalidation only. core/surface/skills/subagent-driven-development/SKILL.md Confirmed fixes require regression RED/GREEN. Features use current criterion-focused checks and meaningful negative controls where needed; refactors preserve passing characterization baselines. Coverage, lint and applicable security requirements remain explicit. core/surface/skills/tdd/SKILL.md The commit owner checks authorization, the staged diff, secrets and the verification approach appropriate to the change. Current criterion checks, genuine fix regressions and refactor parity retain their distinct evidence requirements. Reuse applicable observed checks and reviews across phases. Managed v2 maintenance selects affected claims and uses native paired writes; unknown evidence defers that document. core/surface/skills/commit-gate/SKILL.md PR readiness uses the explicit base-to-HEAD subject for current checks, secrets scanning and applicable specialized review. Existing evidence is reused only while its source and inputs match. Merge requires authorization and exact-head hosted CI. core/surface/skills/finishing-a-development-branch/SKILL.md Read-only task-context reports direct dependencies and unresolved ancestors, scoped_changed, scoped_unchanged or unassessed inputs, and actual check observations. Missing broader context remains explicit; the packet does not certify verification. core/artifacts/internal/operations/task_context.go An unanswered legacy reconciliation can be superseded only when route and pending state agree and no durable attempt or matching observed reply exists. Captured replies recover through their original immutable source and receipt; in-flight mutations retain exact replay and real user stops. core/pysrc/_reconciliationlib.py The installed recover command finishes a captured original reply or replays an in-flight mutation without asking for a new user answer. core/pysrc/artifact-reconcile.py Task-check observations now retain directly referenced criterion identity and an optional bounded source-input fingerprint or an explicit unassessed reason, without executing tests or minting approval receipts. core/artifacts/internal/operations/task_check.go New checks bind the selected criterion and applicable constraint bodies, including explicit references and scope applicability. Unrelated constraints remain outside the digest; old observations never gain unassessed constraint coverage. core/artifacts/internal/model/assistive.go Exact and batch symbol retrieval exposes reported check history without an approval ticket. Outline paging now accounts for encoded rows incrementally while retaining response budgets and continuation behavior. core/artifacts/internal/read/read.go Human HTML presents reported command checks in an escaped, explicitly unverified section; implementation state and source validation remain distinct. core/artifacts/internal/render/render.go The closed task-check request accepts bounded command observations matched to plan definitions. Ordinary context-preview and context-finalize-preview omit prompt identity; context-apply accepts an exact preview reference and digest. Invalid requests, changed preimages and stale CAS writes remain rejected. The historical smarts-apply request accepts the 0.2.0 SMARTS decision record. init-store takes a protocol-only request. core/artifacts/internal/operations/protocol.go The unpublished 0.3.2 native schema adds optional shared_inputs and scoped task-check fields without silently relabeling old records. core/artifacts/schemas/common.schema.json The bounded source-fingerprint reader hashes actual declared task/shared paths, directory membership and known build-control files; unsafe, missing and over-limit scopes are explicitly unassessed rather than blocking work or proving a full dependency graph. core/artifacts/internal/operations/input_scope.go The candidate-only runbook distinguishes 0.3.1/0.3.2 mixed-schema readers, exact replay and forward recovery while preserving recorded user stops. The paired prompt retirement scans immutable observed replies before calling a request unanswered; submitted or uncertain decisions are never erased. Older-client downgrade after modern edits remains unsupported. docs/artifacts/ASSISTIVE-UPGRADE.md Ordinary approval and sprint instructions bypass legacy capture without changing pending history or inventing authority. Explicit legacy replies retain exact matching. The paired adapter can retire a genuinely unanswered 0.2 sprint-pair request using its serialized cancellation lock and submission check; submitted decisions must replay, while standalone approval 0.1 refuses automatic retirement. core/pysrc/_approvallib.py Ordinary prerequisite instructions bypass legacy capture. The existing adapter can retire only a validated ARMED pending question under its original per-plan OS lock. Confirmed or captured decisions are not disposable; no authority receipt or new native permission API is created. core/pysrc/_prerequisitelib.py The old paired approval producer publishes a content-addressed observed reply before its durable submission. Cancellation checks the matching observation, content hash, prompt and frozen context under its existing lock, with a strict scan bound. A matching or uncertain pre-submission reply blocks automatic retirement; normal tasks and context reads have no added cost. core/pysrc/_sprintapprovallib.py The optional reference retains strict historical evidence inputs without replacing ordinary work. Explicit draft source refresh preserves progressed plans and history with both CAS bindings; initial approval restrictions remain on historical paired attestation. Its verify command requires literal absolute paths; linked agent subdirectories remain unsupported for strict authority review. These limitations apply to requested attestation, not ordinary task start. core/surface/includes/artifacts-attestation.md The command catalog starts from the agreed outcome and maintained plan; SMARTS is useful for difficult tradeoffs and does not authorize a changed outcome. core/surface/COMMANDS.md Resident instructions preserve existing work authorization and actual owner decisions without another spec approval or a SMARTS record for every routine step. core/surface/arbiter.md Status separates reported DONE from independently ACCEPTED work, shows actual blocked decisions, and does not infer an approval request from draft governance state. core/surface/commands/status.md Delegated authors preserve the caller-selected verification approach: genuine regression RED/GREEN for fixes, current criterion-focused feature checks and passing characterization baselines for refactors. Actual results and pending checks return to the caller; staging requires assigned scope and authorization. core/surface/includes/author-tdd-workflow.md Codex dispatch requires attestation only for explicitly claimed host proof; an unavailable requested farm backend is reported without silently switching provider or model. Ordinary context inspection can proceed inline within actual host permissions; an agent label supplies no containment or semantic verification. core/surface/includes/codex-host-notes.md Historical sprint approval and SMARTS proof instructions remain available only for existing explicit attestation, outside the ordinary execution path. core/surface/includes/sprint-authority.md The public Codex farm boundary matches its caller: report the unavailable backend and use another provider or model only within existing authorization. docs/parity.md The preparation helper binds bounded drafts and retained sources to exact document/provenance preimages. Finalization preparation hashes all thirteen required outputs and retains missing output failures without modifying files. core/pysrc/_contextwriterlib.py The installed context-draft command prepares a paired document preview; context-finalize prepares initial finalization. context-apply commits the exact selected preview and digest. Context modes preserve scaffold and initialized refresh boundaries. core/pysrc/init-codearbiter.py Ordinary context-preview retains an inert proposal and exact preimages without approval or review claims. context-apply revalidates the digest, closed request and preview binding before the native paired transaction; context-finalize-preview uses the same exact-reference path for initial population. No approve-context reply is required. core/artifacts/internal/operations/context_assistive.go The finite context contract permits a whole-document Markdown entry only as the sole entry for one of five named content targets. Explicit typed field entries remain available; the writer does not expose arbitrary repository-file writes. core/artifacts/internal/contextdocument/contract.go Whole-document replacement requires the explicit document selection and exact existing bytes. It preserves CONTEXT frontmatter and initialization state, checks the named document identity and Markdown structure, and retains the code-map size limit. Human content outside the authorized change remains the caller's preservation obligation. core/artifacts/internal/contextdocument/document_selection.go Ordinary create/adopt/update preserves the same source-evidence, selection and compare-and-swap checks as the native transaction. Missing or matching v1 provenance can be adopted; existing v2 ownership can transition through explicit whole-document selection. Original document/provenance preimages remain in transaction history for exact recovery. core/artifacts/internal/contextdocument/operations.go Initial finalization binds thirteen output identities, rechecks supporting source evidence, and changes the initialization marker with its paired provenance digest. Ordinary finalization requires no artifact approval receipt and does not certify semantic correctness. Already initialized repositories refuse a new finalization. core/artifacts/internal/contextdocument/finalization.go The context schema describes both finite field entries and the explicit whole-document entry for the five supported content documents. Its typed structure records evidence references; schema validity does not establish that the claims were independently reviewed. core/artifacts/schemas/context.schema.json Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md Initial brownfield setup checks the intended repository and actual host permissions, then uses bounded inspection and the installed safe context writer. Ordinary Windows work needs no special scout profile or per-document artifact approval. An existing initialized repository routes to selected refresh instead of another scaffold or population cycle. core/surface/commands/init.md Optional context scouts report only their assigned scope, source identities, coverage, conflicts and unknowns. Six logical categories do not require six child agents. A role label or read-only instruction proves neither sandbox containment nor independent semantic verification; actual host permissions and excluded paths still apply. core/surface/agents/scout.md Release preparation inserts a new version below the entire Unreleased section and above prior versions, preserving pending notes. This guidance correction does not grant publication authority or replace the existing release-PR and hosted qualification boundaries. core/surface/skills/release/SKILL.md The lazy reference map routes provenance drift or requested initialized refresh to context-check after reading selected documents, provenance and the code map. The owner reuses selected scope and existing authorization. core/surface/includes/reference-map.md Authors and reviewers share task-critical reference and constraint checks. Missing or stale provenance remains advisory. Two delivery attempts end with an advisory unknown observation, without another retry or an invented receipt. core/pysrc/_contextselectlib.py Feature actors receive scoped requirements, named critical references and observed evidence. Applicable conflicts or missing required inputs stop dependent work; provenance warnings remain visible and advisory. core/pysrc/_artifactpromptlib.py Confirmed fixes preserve causal evidence and a named regression. Delegated input retains critical requirements; advisory delivery exhaustion ends retries while actual missing inputs and conflicts retain their dependent-work boundary. Distinct remediation strategies are compared with SMARTS only after the root cause is confirmed. core/surface/commands/fix.md A review binds one resolved diff and supplies scoped inputs to each reviewer. Missing critical references or applicable conflicts prevent a substantive verdict; provenance and unobserved delivery diagnostics remain advisory. core/surface/commands/review.md Characterization tests can pass against existing correct behavior. Preserve behavioral assertions against the post-backfill baseline; mechanical import or symbol-reference updates retain the same oracle. Coverage and parity checks remain required. A precise surface table proceeds under existing user authorization; only material expansion or a changed outcome needs another decision. Distinct restructuring strategies are compared with SMARTS only after surface and parity are settled. core/surface/skills/refactor/SKILL.md Greenfield interviews persist under plans/decomposition and retain actual decisions. Five document/v2-provenance pairs use context-draft and context-apply; context-finalize binds all thirteen outputs. ADRs and task rows use their owners, and retained interview evidence survives finalization. core/surface/skills/decompose/SKILL.md Scheduling follows the full dependency ancestry and exposes unresolved ancestor IDs and reasons. Reconciled progress remains advisory; blocked ancestors prevent premature downstream readiness while independent tasks remain available. Response-budget omissions are explicit, retain the global scheduling decision and direct callers to supported detail reads. core/artifacts/internal/operations/assistive.go Explicit draft source refresh retains both source CAS components and same-pair identity without requiring an unstarted plan. Existing progress, approvals and evidence are preserved without asserting current authority. Dependency invalidation preserves an independently BLOCKED task and its reason. Verification summaries disclose conflicting caller reports separately from receipt freshness; later successful verification covers only reports present when its context was issued. core/artifacts/internal/operations/lifecycle.go A checkpoint retains the reviewed commit, UTC review-start time and worktree dirty state, then writes the report through its aggregator. last-checkpoint holds only the override count. core/surface/commands/checkpoint.md Checkpoint reports persist observed source_commit, recorded_at and worktree_dirty values together with every review finding. Missing anchors remain unknown. core/surface/agents/checkpoint-aggregator.md Checkpoint audit windows use the report timestamp and an ancestor commit. Invalid or missing anchors require an explicit ref/date window; dirty review scope remains a stated limitation. core/surface/commands/audit.md Bounded read-time pointers include ordinary draft and ready HTML specs as advisory context. Rejected or withdrawn specs stay excluded; no pointer confers approval. core/pysrc/_readinjectlib.py Routine maintenance selects changed v2 claims intersecting staged sources using a current bounded snapshot. Unknown evidence defers the affected document; native paired writes preserve owned fields and current identities. core/pysrc/_provenancelib.py Ordinary uppercase words such as Approve DATA migration remain ordinary input. All-letter capture codes require a matching retained request; real armed replies, mismatches and user stops preserve their original handling. core/pysrc/_replylib.py Only an actual verifier wrapper executable/script prefix selects authority handling. Inert PowerShell data mentioning the filename is not a verifier call; malformed real verifier invocations still fail closed. Fresh legacy context approval arming is refused; historical pending routes remain readable. core/pysrc/_artifactauthoritylib.py Bounded isolated Python stdin diagnostics may read literal protected paths or git show HEAD objects. Unknown code, mutable calls, shell expansion and extra commands retain the guard checks; ordinary commands avoid AST parsing. core/pysrc/_bashguardlib.py /add-dep /adr /adr-status /audit /btw /checkpoint /chore /cleanup /commands /commit /conflict /context-check /create-context /debug /decompose /doctor /feature /fix /init /metrics /override /pr /preview /prune /reconcile /refactor /release /review /spike /sprint /standup /status /statusline /task /threat-model /tribunal /watch Operate / alias
/context-check context-check
Canonical entry: status drift
Route to outcome Default status and initial drift report are read-only Assess legacy v1 drift and each enrolled v2 identity/coverage state separately; unknown is not fresh Wait for explicit selected documents and affected scope, or explicit full refresh; defer changes nothing Re-scout only the selected assignments through qualified containment and a bounded current join For v2, approve the exact owned-field document/provenance preview and apply only its native receipt Read back committed pairs; retain the initialized marker, unselected human content and separate task/question/audit history; do not stage or commit Selected context Current bounded source/target snapshots and action-boundary checks
v1 drift separately from v2 current/stale/unknown coverage; identity matching is not semantic proof
Explicit document selection, actual field ownership, qualified scouts and native writer capability
Output Read-only state/drift report, or explicitly selected native context updates with declared full/incremental coverage.
Report alone is not refresh consent. No reinitialization or marker removal. No legacy raw rebaseline fallback for v2, no unsupported human-layout overwrite, no staging or commit.
Host / scope Claude Code / Codex / Pi; admission and runtime capabilities still apply
claude /ca:context-check
codex $ca-context-check
pi /ca-context-checkRead the exact procedure
Related entries Pinned evidence S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S23 · core/surface/commands/init.mdCurrent init owner: activation/scaffold versus initial population; initialized refresh belongs to status drift, not reinitialization. Knowledge / alias
/create-context context-creation
Canonical entry: init --brownfield
Route to outcome Uninitialized project with meaningful source → bounded brownfield initial population Brownfield: qualified read-only scout profile → closed reports → scoped synthesis and relevant gap decisions Approve each native document/provenance preview; receipt-only apply, then separately approved finalization Finalize the 13 required identities through its own native preview/receipt; recover uncertain operations by the same operation ID Selected context Same bounded brownfield source, containment, report, ownership and provenance contract as init --brownfield
Output Five current content/provenance pairs and separately finalized initialized state, or a precise capability/evidence conflict.
Initial population only; existing initialized state routes to status drift. Generic scout role or a source-only preparation fixture does not establish qualified containment or writer admission.
Host / scope Claude Code / Codex / Pi; admission and runtime capabilities still apply
claude /ca:create-context
codex $ca-create-context
pi /ca-create-contextRead the exact procedure
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S23 · core/surface/commands/init.mdCurrent init owner: activation/scaffold versus initial population; initialized refresh belongs to status drift, not reinitialization. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Change / advanced
/debug debug
Route to outcome Capture the cited symptom, expectation, reproduction state and actual request scope Test evidence-backed mechanisms using safe discriminators; preserve inconclusive observations and capture limits Choose exactly one disposition: confirmed_code_defect, confirmed_noncode_cause, design_question, no_action or unresolved For transfer, validate the bounded transient debug-handoff/1.0.0 packet with the installed helper Return the diagnosis and truthful continuation; only an already-authorized fix caller can continue a qualifying code-defect handoff Selected context Available project instructions and scoped source evidence, not compulsory new onboarding
Observed versus expected behavior, reproduction status, supported causes and regression oracle
Relevant worktree, source/build/runtime identity, dirty state, limitations and independent caller authority
Output One evidence-backed disposition and a bounded summary; transient validated handoff when available. No default persistent case store, task or ADR.
Diagnosis never authorizes repair. Invalid/unavailable handoff validation stops transfer; recheck current evidence. No-action requires positive closure evidence. A design question is not an automatic ADR.
Host / scope Claude Code / Codex / Pi; admission and runtime capabilities still apply
claude /ca:debug
codex $ca-debug
pi /ca-debugRead the exact procedure
Related entries Pinned evidence S25 · core/surface/skills/debug/SKILL.mdFive-disposition diagnostic owner; transient validated handoff, freshness and authority boundaries. Full owner read. S19 · core/surface/commands/fix.mdCurrent full fix owner: validated handoff, independent caller authority, evidence revalidation, selected actor input and genuine target-red gate. S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. S04 · core/surface/includes/routing-table.mdAuthoritative intent-to-owner table, scope-touch routes and stop/return semantics. Change / core
/feature brainstorming → writing-plans → executing-plans
Route to outcome Discover an existing exact-format pair and resume before new triage Small: confirm 1–3 criteria and log triage, then TDD Full: approve specification, bind/approve plan, then attended batches Fresh task authors, spec proof, scope-quality acceptance Before each author or independent reviewer acts, compose its own current scoped input and perform bounded actor delivery; a coordinator read is not receipt Current acceptance → authorized commit → selected PR disposition Selected context Project purpose, stage and code-map
Scope-specific rules and recorded ADR intent
Approved criteria and exact plan binding
Task paths, dependencies, verification and complete context ticket
Current actor-scoped selection: map/provenance, command cwd and observed evidence, constraints and host-effective instructions
Actual author and independent reviewer delivery bound to task/worktree/source/host epochs; reselect after resume, compaction or scope change
Use exact engine-returned IDs, not assumed SPEC-/PLAN- prefixes. Approved prerequisites use one visible 24-hour request/reply deadline.
Output Full lane: typed spec + plan, accepted code/tests, evidence and selected PR outcome. Small lane: inline mini-spec, no spec artifact.
No guessed unknowns; no implementation before red; batch checkpoints; no mixed-format resume; installed HTML admission required. Selected context is orientation, not task admission. Small features retain their confirmed inline mini-spec without invented artifact IDs.
Host / scope Claude Code / Codex: admitted installed typed workflow only. Pi 1.0.2 is the current runtime target, but its native approval adapter remains unimplemented (DEGRADED); legacy Markdown pairs and inline small-feature work have separate contracts.
claude /ca:feature
codex $ca-feature
pi /ca-featureRead the exact procedure
Related entries Pinned evidence S06 · core/surface/commands/feature.mdCurrent feature owner: same-format resume and full/small gates; adds actual per-actor context composition. S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S09 · core/surface/skills/tdd/SKILL.mdCurrent TDD context preflight and obligation derivation re-read. Six-phase gate sequence also confirmed by current skill index; fix and test-only paths do not fabricate feature artifacts. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. S11 · core/surface/skills/commit-gate/SKILL.mdCurrent Phase 5.5 through terminal commit rules re-read. Legacy heal vocabulary must not be generalized to v2 paired native writes. S12 · core/surface/skills/finishing-a-development-branch/SKILL.mdWatch/cleanup early routing; commit and acceptance preflight; PR and merge authority. S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. S31 · docs/parity.mdCurrent Pi 1.0.2 target, separate host counts, DEGRADED typed approval and Codex farm exception. S32 · core/pysrc/_artifactauthoritylib.pyNative artifact ID grammar, producer states, Claude join lock, UTF-8/UTF-16-key-order observation binding. Change / core
/fix tdd — bug variant
Route to outcome Establish the confirmed defect from current reproduction or supported source/contract causal evidence If needed, use one bounded internal debug prerequisite and return to this same authorized fix caller Validate any available handoff; independently recheck caller authority and actual worktree/source/runtime applicability Select and deliver bounded current context to the actual fix author Observe the named regression red for the correct defect, then implement the minimum fix and complete TDD Return proof; commit, PR and other follow-ups retain their separate authority Selected context Current expectation, causal evidence, reproduction limits and named regression oracle
Task paths; scoped map/provenance; command cwd and current collector evidence
Applicable constraints and native effective instructions; actor/worktree/source/host epoch binding
Output Minimal authorized correction with genuine failing-before / passing-after regression evidence.
No repair from packet intent alone. Only a validated confirmed_code_defect → fix handoff can resume an authorized repair. Setup/import/unrelated red is not target-red proof. No feature artifact is invented.
Host / scope Claude Code / Codex / Pi; admission and runtime capabilities still apply
claude /ca:fix
codex $ca-fix
pi /ca-fixRead the exact procedure
Related entries Pinned evidence S19 · core/surface/commands/fix.mdCurrent full fix owner: validated handoff, independent caller authority, evidence revalidation, selected actor input and genuine target-red gate. S25 · core/surface/skills/debug/SKILL.mdFive-disposition diagnostic owner; transient validated handoff, freshness and authority boundaries. Full owner read. S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. S09 · core/surface/skills/tdd/SKILL.mdCurrent TDD context preflight and obligation derivation re-read. Six-phase gate sequence also confirmed by current skill index; fix and test-only paths do not fabricate feature artifacts. Knowledge / core
/init init-codearbiter.py → context-creation / decompose
Route to outcome --check reports only; activation/scaffold is a separate action Uninitialized project with meaningful source → bounded brownfield initial population Brownfield: qualified read-only scout profile → closed reports → scoped synthesis and relevant gap decisions Approve each native document/provenance preview; receipt-only apply, then separately approved finalization No meaningful source → retain the separate six-layer greenfield interview and persisted drafts Already initialized → normal operation; a selected refresh belongs to status drift, not init Selected context Source shape and maturity; existing file ownership and initialization state
Qualified scout reports and current source snapshots for brownfield, persisted interview answers for greenfield
Output Initialized project knowledge after the selected owner completes its real gates; a stub alone is not ready.
Brownfield profile or qualified native writer unavailable → block that dependent step. Five document/provenance pairs have independent approvals; finalization has its own 13-identity preview and receipt. Never clear the marker to refresh.
Host / scope Claude Code / Codex / Pi; admission and runtime capabilities still apply
claude /ca:init
codex $ca-init
pi /ca-initModes --check · --stage N · --brownfield · --greenfield
Read the exact procedure
Related entries Pinned evidence S23 · core/surface/commands/init.mdCurrent init owner: activation/scaffold versus initial population; initialized refresh belongs to status drift, not reinitialization. S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S14 · core/surface/skills/decompose/SKILL.mdCurrent greenfield interview and completion contract re-read. Its persisted six-layer draft flow remains separate from the brownfield writer lifecycle. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Operate / advanced
/metrics read-only trend report
Route to outcome Read selected and prior windows Summarize overrides, small lanes and low-confidence choices Return comparison Selected context Override, triage and sprint decision logs
Output Trend report against prior window.
Reporting is not state mutation or workflow approval.
Host / scope Claude Code / Codex / Pi; admission and runtime capabilities still apply
claude Not exposed on this host
codex Not exposed on this host
pi Not exposed on this host Modes --window N
Removed on 2026-10-23; no host exposes this route.
Related entries Pinned evidence S02 · core/surface/COMMANDS.mdCatalog, modes, host-limited commands and purpose of each public route. Ship / core
/release release
Route to outcome Resolve the declared target, version policy, payload and reviewed executable inputs; dry-run reports only and skips writes and execution. Prepare version/changelog and declared release surfaces through the ordinary commit gate on a non-default branch. Report the exact assets and publisher, open the release PR and STOP. Interactive preparation does not compose a local tag. Only after the PR merges may a qualifying hosted publisher continue at the exact merged, fetched and verified default-branch commit. Compose and validate the exact tag/cohort only through that publisher. Apply the existing one-cohort publication authority; CI success alone is not publication permission. Read back the exact non-draft release and declared inventory. A declared provenance closeout uses its own receipt PR; an already-published receipt-only path never publishes again. Selected context Declared target row, exact manifest/changelog/payload ownership
Exact release-surface commit, fetched default branch and current hosted evidence
Existing publication authority for this cohort, exact assets and any declared provenance requirement
Output A release-preparation PR; separately, an authorized hosted publication and its exact readback. Declared receipt closeout remains a separate PR.
Mandatory release-PR stop. No local tag fallback, red/stale-head publication or implicit consent. Dry-run does not fetch, execute checks, commit or publish.
Host / scope Claude Code / Codex / Pi; admission and runtime capabilities still apply
claude /ca:release
codex $ca-release
pi /ca-releaseModes --dry-run
Read the exact procedure
Related entries Pinned evidence S33 · core/surface/skills/release/SKILL.mdInteractive release preparation and mandatory release-PR boundary; qualified hosted tag composition. S34 · site/src/content/docs/concepts/workflow-routes.mdxExisting public route-comparison owner; distinct release/initialization endpoints and source-only explanation boundary. Change / core
/sprint SPRINT.md → subagent-driven-development
Route to outcome Resolve same-format artifacts; retain existing approved intent Prepare spec and draft plan for one real user approval of the pair Execute the full plan without attended batch pauses SMARTS governs delegated in-scope choices; correction must rerun failed gates Before each author or independent reviewer acts, compose its own current scoped input and perform bounded actor delivery; a coordinator read is not receipt Current acceptance → authorized commit → open PR only Selected context Project rules and recorded intent
Approved spec/plan and explicit delegation terms
Task-specific contextual reads
Actual review, verification and authority receipts
Current actor-scoped selection: map/provenance, command cwd and observed evidence, constraints and host-effective instructions
Actual author and independent reviewer delivery bound to task/worktree/source/host epochs; reselect after resume, compaction or scope change
Use exact engine-returned IDs, not assumed SPEC-/PLAN- prefixes. Approved prerequisites use one visible 24-hour request/reply deadline.
Output Accepted plan and implementation, sprint decision log, open PR and summary. No autonomous merge.
Initial approval never self-issued. Security/authority/irreversible-action stops remain. HTML --farm blocked; legacy farm is opt-in preview. Selected context is orientation, not task admission.
Host / scope Claude Code / Codex: admitted installed typed workflow only. Pi 1.0.2 is the current runtime target, but its native approval adapter remains unimplemented (DEGRADED); legacy Markdown pairs and inline small-feature work have separate contracts.
claude /ca:sprint
codex $ca-sprint
pi /ca-sprintModes --farm
Read the exact procedure
Related entries Pinned evidence S07 · core/surface/SPRINT.mdInitial paired approval; full-plan execution; delegated methods; recovery and farm boundaries. S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. S12 · core/surface/skills/finishing-a-development-branch/SKILL.mdWatch/cleanup early routing; commit and acceptance preflight; PR and merge authority. S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. S09 · core/surface/skills/tdd/SKILL.mdCurrent TDD context preflight and obligation derivation re-read. Six-phase gate sequence also confirmed by current skill index; fix and test-only paths do not fabricate feature artifacts. S31 · docs/parity.mdCurrent Pi 1.0.2 target, separate host counts, DEGRADED typed approval and Codex farm exception. S32 · core/pysrc/_artifactauthoritylib.pyNative artifact ID grammar, producer states, Claude join lock, UTF-8/UTF-16-key-order observation binding. Operate / core
/status status / context-check
Route to outcome Default status and initial drift report are read-only Assess legacy v1 drift and each enrolled v2 identity/coverage state separately; unknown is not fresh Wait for explicit selected documents and affected scope, or explicit full refresh; defer changes nothing Re-scout only the selected assignments through qualified containment and a bounded current join For v2, approve the exact owned-field document/provenance preview and apply only its native receipt Read back committed pairs; retain the initialized marker, unselected human content and separate task/question/audit history; do not stage or commit Selected context Current bounded source/target snapshots and action-boundary checks
v1 drift separately from v2 current/stale/unknown coverage; identity matching is not semantic proof
Explicit document selection, actual field ownership, qualified scouts and native writer capability
Output Read-only state/drift report, or explicitly selected native context updates with declared full/incremental coverage.
Report alone is not refresh consent. No reinitialization or marker removal. No legacy raw rebaseline fallback for v2, no unsupported human-layout overwrite, no staging or commit.
Host / scope Claude Code / Codex / Pi; admission and runtime capabilities still apply
claude /ca:status
codex $ca-status
pi /ca-statusModes drift
Read the exact procedure
Related entries Pinned evidence S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S23 · core/surface/commands/init.mdCurrent init owner: activation/scaffold versus initial population; initialized refresh belongs to status drift, not reinitialization. Operate / advanced
/statusline Claude Code statusline control
Route to outcome Select install, uninstall or status Change or inspect the owned Claude statusline configuration Return status Selected context Claude Code install and statusline settings
Output Statusline configuration or status report.
Claude-specific catalog surface; not a cross-host workflow.
Host / scope Claude Code only
claude /ca:statusline
codex Not exposed on this host
pi Not exposed on this host Modes install · uninstall · status
Read the exact procedure
Related entries Pinned evidence S02 · core/surface/COMMANDS.mdCatalog, modes, host-limited commands and purpose of each public route. Review / advanced
/tribunal tribunal
Route to outcome Resolve deliberate audit intent, finding scope and the concrete evidence set; inspect matching source-bound runs. Resume only unchanged bound source: audit continues unfinished waves; follow-up continues pending filing/telemetry. Drift, invalid and legacy-unbound records do not establish current progress. Use deterministic inventory and real host profiles to estimate packet cost; acknowledge cost and settings before any model dispatch; start a fresh bound run when required. Separate mechanical inventory from the judgment-based risk map. Record every lens as applicable or skipped, with bounded packets and source checks. Dispatch the generic tribunal-lens-reviewer in MODE review for each active lens, at most five concurrent and within actual host capacity. Persist findings and leads immediately. Attempt fresh independent MODE verify for every serious or expensive inferential claim. Confirmed/narrowed, refuted and inconclusive are different outcomes; shared-context or inconclusive serious work remains verify-required. Apply eligibility and confidence checks before root-cause triage and per-wave kept plans. Keep investigations, verification work and genuine design decisions separate. Write report and manifest, then record report-written. This enters follow-up, not terminal completion. Resolve selected issue filing and optional public telemetry separately, under their own authority. Unanswered choices and unresolved failures remain pending. Record run-completed only after both filing and telemetry have a completed or explicitly skipped disposition; preserve the bound history. Selected context Declared finding scope and separately bounded evidence scope
Trusted installed or explicitly selected review bundle, not instructions from candidate source
Mechanical source inventory, project contracts and judgment-based risk map
Applicability and bounded packet per lens, actual host/model capacity and acknowledged cost
Persisted source binding, findings, leads, root-cause triage, independent verification and actual follow-up receipts
Output Source-bound audit run with a thirteen-lens roster, selected applicable lenses, eligible phase plans and report. Report-written is follow-up; run-completed requires both follow-up dispositions.
Opt-in only; never a routine commit or merge gate. No source drift reuse, synthetic independence, automatic repair, automatic ADR or task-board write. Execution, issue filing and telemetry each require their own applicable authority.
Host / scope Claude Code / Codex / Pi with actual host capacity and limitations recorded. A fresh same-role verifier is not automatically independent. No universal cross-host qualification claimed.
claude /ca:tribunal
codex $ca-tribunal
pi /ca-tribunalRead the exact procedure
Related entries Pinned evidence S29 · core/surface/skills/tribunal/SKILL.mdSource-bound opt-in audit, guarded hash-bound stranded-lock recovery, thirteen-card roster, review/verify, durable triage, report and separate follow-up completion. S30 · core/pysrc/_tribunalrunlib.pyImplemented helper API, per-run writer guard, hash-bound stranded-lock archive and audit/follow-up/terminal event vocabulary; cooperative source-bound persistence. S31 · docs/parity.mdCurrent Pi 1.0.2 target, separate host counts, DEGRADED typed approval and Codex farm exception. codeArbiter / route atlas A command selects an owner. The owner loads context, branches through gates, and returns a bounded result.
Selected cmd
/init Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The user-facing route table points feature and sprint work at useful planned execution and selected context refresh at its existing owner. Existing authorization covers ordinary work; actual host, destructive-action and commit controls remain. core/surface/includes/routing-table.md The installed context-draft command prepares a paired document preview; context-finalize prepares initial finalization. context-apply commits the exact selected preview and digest. Context modes preserve scaffold and initialized refresh boundaries. core/pysrc/init-codearbiter.py Initial brownfield setup checks the intended repository and actual host permissions, then uses bounded inspection and the installed safe context writer. Ordinary Windows work needs no special scout profile or per-document artifact approval. An existing initialized repository routes to selected refresh instead of another scaffold or population cycle. core/surface/commands/init.md --check: report only Otherwise scaffold, then populate
Related entries Pinned evidence S23 · core/surface/commands/init.mdCurrent init owner: activation/scaffold versus initial population; initialized refresh belongs to status drift, not reinitialization. Selected skill
decompose Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Greenfield interviews persist under plans/decomposition and retain actual decisions. Five document/v2-provenance pairs use context-draft and context-apply; context-finalize binds all thirteen outputs. ADRs and task rows use their owners, and retained interview evidence survives finalization. core/surface/skills/decompose/SKILL.md Greenfield: six persisted interview layers
Related entries Pinned evidence S14 · core/surface/skills/decompose/SKILL.mdCurrent greenfield interview and completion contract re-read. Its persisted six-layer draft flow remains separate from the brownfield writer lifecycle. Selected skill
context-creation Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The skill index connects planning, direct or delegated implementation, proportional verification and selected context maintenance to their owning workflows. core/surface/skills/INDEX.md Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md Initial brownfield setup checks the intended repository and actual host permissions, then uses bounded inspection and the installed safe context writer. Ordinary Windows work needs no special scout profile or per-document artifact approval. An existing initialized repository routes to selected refresh instead of another scaffold or population cycle. core/surface/commands/init.md Six full logical assignments require observed read-only containment. Generated plugins alone do not qualify that profile. Each of five content/provenance pairs needs its own native approval, then initialization is a separately approved transaction.
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected state
Initialized project knowledge Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Initial finalization binds thirteen output identities, rechecks supporting source evidence, and changes the initialization marker with its paired provenance digest. Ordinary finalization requires no artifact approval receipt and does not certify semantic correctness. Already initialized repositories refuse a new finalization. core/artifacts/internal/contextdocument/finalization.go Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md Greenfield interviews persist under plans/decomposition and retain actual decisions. Five document/v2-provenance pairs use context-draft and context-apply; context-finalize binds all thirteen outputs. ADRs and task rows use their owners, and retained interview evidence survives finalization. core/surface/skills/decompose/SKILL.md CONTEXT • stack • standards • security ADRs • plans • questions • code-map Provenance supports freshness checks
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S14 · core/surface/skills/decompose/SKILL.mdCurrent greenfield interview and completion contract re-read. Its persisted six-layer draft flow remains separate from the brownfield writer lifecycle. S23 · core/surface/commands/init.mdCurrent init owner: activation/scaffold versus initial population; initialized refresh belongs to status drift, not reinitialization. Selected state
Runtime + on-demand context Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md The user-facing route table points feature and sprint work at useful planned execution and selected context refresh at its existing owner. Existing authorization covers ordinary work; actual host, destructive-action and commit controls remain. core/surface/includes/routing-table.md The commit owner checks authorization, the staged diff, secrets and the verification approach appropriate to the change. Current criterion checks, genuine fix regressions and refactor parity retain their distinct evidence requirements. Reuse applicable observed checks and reviews across phases. Managed v2 maintenance selects affected claims and uses native paired writes; unknown evidence defers that document. core/surface/skills/commit-gate/SKILL.md PR readiness uses the explicit base-to-HEAD subject for current checks, secrets scanning and applicable specialized review. Existing evidence is reused only while its source and inputs match. Merge requires authorization and exact-head hosted CI. core/surface/skills/finishing-a-development-branch/SKILL.md The command catalog starts from the agreed outcome and maintained plan; SMARTS is useful for difficult tradeoffs and does not authorize a changed outcome. core/surface/COMMANDS.md Resident instructions preserve existing work authorization and actual owner decisions without another spec approval or a SMARTS record for every routine step. core/surface/arbiter.md The lazy reference map routes provenance drift or requested initialized refresh to context-check after reading selected documents, provenance and the code map. The owner reuses selected scope and existing authorization. core/surface/includes/reference-map.md Startup state; safety-core + active persona On-demand rules + complete typed task reads Task-scoped packets delivered to each actual actor Context is not approval, admission or consumption proof
Related entries Pinned evidence S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. S15 · core/pysrc/prompt-submit.pyCurrent persona composition and session/mode/compaction injection comments read; not actor-delivery proof. S16 · core/pysrc/_readinjectlib.pyCurrent file-read pointer and dedup implementation interface read; advisory hints remain separate from task-time selected input. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. Selected skill
brainstorming → writing-plans Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md Plans preserve agreed criteria, useful tasks, dependency ancestry, bounded shared inputs and observable checks. Stable source identities and typed maintenance keep changes within the selected outcome. A design-drift guard routes an undecided material solution choice back to brainstorming instead of scoring it during planning. core/surface/skills/writing-plans/SKILL.md The feature entry now resumes a maintained spec/plan and task progress without another artifact certification prompt; independent commit and test controls remain. The small lane runs an inline SMARTS scan only for a material solution choice. core/surface/commands/feature.md Source refinement respects recorded deferrals and accepted ADR conflicts without turning each ordinary method adjustment into a separate authorization interview. SMARTS compares approaches only when two or more are materially plausible; a single approach gets one line and no table. core/surface/skills/brainstorming/SKILL.md Full: approved spec, then bound plan
Related entries Pinned evidence S06 · core/surface/commands/feature.mdCurrent feature owner: same-format resume and full/small gates; adds actual per-actor context composition. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. Selected gate
Spec + plan pair approval Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md The sprint caller performs an index-first recorded-intent read, preserves actual owner decisions and ADR conflicts, then proceeds with authorized work without a second artifact approval system. A SMARTS Unknown names its missing observation and cannot bypass a hard gate or manufacture authority. core/surface/SPRINT.md The sprint entry now routes to the assistive implementation body instead of requiring a fresh user approval and two reviews per task. core/surface/commands/sprint.md Source refinement respects recorded deferrals and accepted ADR conflicts without turning each ordinary method adjustment into a separate authorization interview. SMARTS compares approaches only when two or more are materially plausible; a single approach gets one line and no table. core/surface/skills/brainstorming/SKILL.md One real user reply before execution
Related entries Pinned evidence S07 · core/surface/SPRINT.mdInitial paired approval; full-plan execution; delegated methods; recovery and farm boundaries. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. Selected cmd
/status · /context-check Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The user-facing route table points feature and sprint work at useful planned execution and selected context refresh at its existing owner. Existing authorization covers ordinary work; actual host, destructive-action and commit controls remain. core/surface/includes/routing-table.md A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md v1/v2 state and drift report Explicit scoped/full refresh selection Native v2 pairs; preserve history
Related entries Pinned evidence S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. Handoffs, branches and returns Feature + sprint / execution paths Follow the split at approval, the join at task execution, and the split again when control returns to the caller.
Selected cmd
/feature or /sprint Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md The pinned native bridge enables task-context as a bounded informational read and does not require future reviewer/approval producers simply to author a structurally valid draft. Context requests route to ordinary context-preview, context-finalize-preview and exact-reference context-apply; historical receipt input stays a separate compatibility path. Installed host qualification is separate. Native Pi writer admission does not establish a complete live Pi workflow. On NO_LOCAL_STORE the client runs init-store once and retries the request once; a refused initialization keeps NO_LOCAL_STORE. On Windows the binary's architecture comes from the kernel (IsWow64Process2), never WMI or PROCESSOR_* environment. Index and outline pages are now fully checked before rows are yielded, including continuation identity and row shape. core/pysrc/_artifactlib.py The user-facing route table points feature and sprint work at useful planned execution and selected context refresh at its existing owner. Existing authorization covers ordinary work; actual host, destructive-action and commit controls remain. core/surface/includes/routing-table.md The sprint entry now routes to the assistive implementation body instead of requiring a fresh user approval and two reviews per task. core/surface/commands/sprint.md The feature entry now resumes a maintained spec/plan and task progress without another artifact certification prompt; independent commit and test controls remain. The small lane runs an inline SMARTS scan only for a material solution choice. core/surface/commands/feature.md The command catalog starts from the agreed outcome and maintained plan; SMARTS is useful for difficult tradeoffs and does not authorize a changed outcome. core/surface/COMMANDS.md Resolve same-slug artifacts Mixed / duplicate matches: STOP Exact pair or lone spec keeps format
Related entries Pinned evidence S06 · core/surface/commands/feature.mdCurrent feature owner: same-format resume and full/small gates; adds actual per-actor context composition. S07 · core/surface/SPRINT.mdInitial paired approval; full-plan execution; delegated methods; recovery and farm boundaries. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. Selected skill
brainstorming Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md The skill index connects planning, direct or delegated implementation, proportional verification and selected context maintenance to their owning workflows. core/surface/skills/INDEX.md The feature entry now resumes a maintained spec/plan and task progress without another artifact certification prompt; independent commit and test controls remain. The small lane runs an inline SMARTS scan only for a material solution choice. core/surface/commands/feature.md Source refinement respects recorded deferrals and accepted ADR conflicts without turning each ordinary method adjustment into a separate authorization interview. SMARTS compares approaches only when two or more are materially plausible; a single approach gets one line and no table. core/surface/skills/brainstorming/SKILL.md Confirmed fixes require regression RED/GREEN. Features use current criterion-focused checks and meaningful negative controls where needed; refactors preserve passing characterization baselines. Coverage, lint and applicable security requirements remain explicit. core/surface/skills/tdd/SKILL.md Recorded intent + user criteria Unknowns → open-questions No guessed product decisions
Related entries Pinned evidence S06 · core/surface/commands/feature.mdCurrent feature owner: same-format resume and full/small gates; adds actual per-actor context composition. S07 · core/surface/SPRINT.mdInitial paired approval; full-plan execution; delegated methods; recovery and farm boundaries. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. Selected skill
writing-plans Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md Plans preserve agreed criteria, useful tasks, dependency ancestry, bounded shared inputs and observable checks. Stable source identities and typed maintenance keep changes within the selected outcome. A design-drift guard routes an undecided material solution choice back to brainstorming instead of scoring it during planning. core/surface/skills/writing-plans/SKILL.md The pinned native bridge enables task-context as a bounded informational read and does not require future reviewer/approval producers simply to author a structurally valid draft. Context requests route to ordinary context-preview, context-finalize-preview and exact-reference context-apply; historical receipt input stays a separate compatibility path. Installed host qualification is separate. Native Pi writer admission does not establish a complete live Pi workflow. On NO_LOCAL_STORE the client runs init-store once and retries the request once; a refused initialization keeps NO_LOCAL_STORE. On Windows the binary's architecture comes from the kernel (IsWow64Process2), never WMI or PROCESSOR_* environment. Index and outline pages are now fully checked before rows are yielded, including continuation identity and row shape. core/pysrc/_artifactlib.py The skill index connects planning, direct or delegated implementation, proportional verification and selected context maintenance to their owning workflows. core/surface/skills/INDEX.md The feature entry now resumes a maintained spec/plan and task progress without another artifact certification prompt; independent commit and test controls remain. The small lane runs an inline SMARTS scan only for a material solution choice. core/surface/commands/feature.md Ordinary approval and sprint instructions bypass legacy capture without changing pending history or inventing authority. Explicit legacy replies retain exact matching. The paired adapter can retire a genuinely unanswered 0.2 sprint-pair request using its serialized cancellation lock and submission check; submitted decisions must replay, while standalone approval 0.1 refuses automatic retirement. core/pysrc/_approvallib.py Ordinary prerequisite instructions bypass legacy capture. The existing adapter can retire only a validated ARMED pending question under its original per-plan OS lock. Confirmed or captured decisions are not disposable; no authority receipt or new native permission API is created. core/pysrc/_prerequisitelib.py Exact criterion IDs → tasks Paths • tests • dependencies Checkpoints • prerequisites
Related entries Pinned evidence S06 · core/surface/commands/feature.mdCurrent feature owner: same-format resume and full/small gates; adds actual per-actor context composition. S07 · core/surface/SPRINT.mdInitial paired approval; full-plan execution; delegated methods; recovery and farm boundaries. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. S21 · core/surface/skills/INDEX.mdCurrent routine-owner index: five debug dispositions, bounded workflow owners and unchanged six-phase TDD / nine-phase commit sequence. Selected gate
Approval is observed Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md The pinned native bridge enables task-context as a bounded informational read and does not require future reviewer/approval producers simply to author a structurally valid draft. Context requests route to ordinary context-preview, context-finalize-preview and exact-reference context-apply; historical receipt input stays a separate compatibility path. Installed host qualification is separate. Native Pi writer admission does not establish a complete live Pi workflow. On NO_LOCAL_STORE the client runs init-store once and retries the request once; a refused initialization keeps NO_LOCAL_STORE. On Windows the binary's architecture comes from the kernel (IsWow64Process2), never WMI or PROCESSOR_* environment. Index and outline pages are now fully checked before rows are yielded, including continuation identity and row shape. core/pysrc/_artifactlib.py The sprint caller performs an index-first recorded-intent read, preserves actual owner decisions and ADR conflicts, then proceeds with authorized work without a second artifact approval system. A SMARTS Unknown names its missing observation and cannot bypass a hard gate or manufacture authority. core/surface/SPRINT.md Source refinement respects recorded deferrals and accepted ADR conflicts without turning each ordinary method adjustment into a separate authorization interview. SMARTS compares approaches only when two or more are materially plausible; a single approach gets one line and no table. core/surface/skills/brainstorming/SKILL.md Ordinary approval and sprint instructions bypass legacy capture without changing pending history or inventing authority. Explicit legacy replies retain exact matching. The paired adapter can retire a genuinely unanswered 0.2 sprint-pair request using its serialized cancellation lock and submission check; submitted decisions must replay, while standalone approval 0.1 refuses automatic retirement. core/pysrc/_approvallib.py The old paired approval producer publishes a content-addressed observed reply before its durable submission. Cancellation checks the matching observation, content hash, prompt and frozen context under its existing lock, with a strict scan bound. A matching or uncertain pre-submission reply blocks automatic retirement; normal tasks and context reads have no added cost. core/pysrc/_sprintapprovallib.py The optional reference retains strict historical evidence inputs without replacing ordinary work. Explicit draft source refresh preserves progressed plans and history with both CAS bindings; initial approval restrictions remain on historical paired attestation. Its verify command requires literal absolute paths; linked agent subdirectories remain unsupported for strict authority review. These limitations apply to requested attestation, not ordinary task start. core/surface/includes/artifacts-attestation.md Historical sprint approval and SMARTS proof instructions remain available only for existing explicit attestation, outside the ordinary execution path. core/surface/includes/sprint-authority.md Ordinary uppercase words such as Approve DATA migration remain ordinary input. All-letter capture codes require a matching retained request; real armed replies, mismatches and user stops preserve their original handling. core/pysrc/_replylib.py Only actual host-observed approval over the current armed identity confers the corresponding authority. Pi 1.0.2 has the runtime input seam but codeArbiter has no implemented Pi-native producer; typed admission remains blocked. For prerequisites, show the packet digest and the shared 24-hour request/reply deadline. Cancellation does not create approval.
Related entries Pinned evidence S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. S31 · docs/parity.mdCurrent Pi 1.0.2 target, separate host counts, DEGRADED typed approval and Codex farm exception. Selected gate
Installed admission is required Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md The pinned native bridge enables task-context as a bounded informational read and does not require future reviewer/approval producers simply to author a structurally valid draft. Context requests route to ordinary context-preview, context-finalize-preview and exact-reference context-apply; historical receipt input stays a separate compatibility path. Installed host qualification is separate. Native Pi writer admission does not establish a complete live Pi workflow. On NO_LOCAL_STORE the client runs init-store once and retries the request once; a refused initialization keeps NO_LOCAL_STORE. On Windows the binary's architecture comes from the kernel (IsWow64Process2), never WMI or PROCESSOR_* environment. Index and outline pages are now fully checked before rows are yielded, including continuation identity and row shape. core/pysrc/_artifactlib.py Pi HTML admission unavailable; legacy Markdown and inline small lane stay distinct. HTML farm remains blocked.
Related entries Pinned evidence S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. Selected skill
subagent-driven-development Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md The user-facing route table points feature and sprint work at useful planned execution and selected context refresh at its existing owner. Existing authorization covers ordinary work; actual host, destructive-action and commit controls remain. core/surface/includes/routing-table.md The skill index connects planning, direct or delegated implementation, proportional verification and selected context maintenance to their owning workflows. core/surface/skills/INDEX.md The sprint caller performs an index-first recorded-intent read, preserves actual owner decisions and ADR conflicts, then proceeds with authorized work without a second artifact approval system. A SMARTS Unknown names its missing observation and cannot bypass a hard gate or manufacture authority. core/surface/SPRINT.md The sprint entry now routes to the assistive implementation body instead of requiring a fresh user approval and two reviews per task. core/surface/commands/sprint.md The feature entry now resumes a maintained spec/plan and task progress without another artifact certification prompt; independent commit and test controls remain. The small lane runs an inline SMARTS scan only for a material solution choice. core/surface/commands/feature.md Attended feature execution now treats checkpoints as progress groups, not compulsory approval stops; it forwards real failures and continues independent work. core/surface/skills/executing-plans/SKILL.md Implementation works directly or delegates a coherent unit when useful. Bounded task context, applicable dependency advice and observed checks support progress while preserving actual user stops and host permissions. Verification checks the change against a recorded SMARTS rationale for material invalidation only. core/surface/skills/subagent-driven-development/SKILL.md Read-only task-context reports direct dependencies and unresolved ancestors, scoped_changed, scoped_unchanged or unassessed inputs, and actual check observations. Missing broader context remains explicit; the packet does not certify verification. core/artifacts/internal/operations/task_context.go Exact and batch symbol retrieval exposes reported check history without an approval ticket. Outline paging now accounts for encoded rows incrementally while retaining response budgets and continuation behavior. core/artifacts/internal/read/read.go Ordinary prerequisite instructions bypass legacy capture. The existing adapter can retire only a validated ARMED pending question under its original per-plan OS lock. Confirmed or captured decisions are not disposable; no authority receipt or new native permission API is created. core/pysrc/_prerequisitelib.py Resident instructions preserve existing work authorization and actual owner decisions without another spec approval or a SMARTS record for every routine step. core/surface/arbiter.md Codex dispatch requires attestation only for explicitly claimed host proof; an unavailable requested farm backend is reported without silently switching provider or model. Ordinary context inspection can proceed inline within actual host permissions; an agent label supplies no containment or semantic verification. core/surface/includes/codex-host-notes.md The public Codex farm boundary matches its caller: report the unavailable backend and use another provider or model only within existing authorization. docs/parity.md Authors and reviewers share task-critical reference and constraint checks. Missing or stale provenance remains advisory. Two delivery attempts end with an advisory unknown observation, without another retry or an invented receipt. core/pysrc/_contextselectlib.py Feature actors receive scoped requirements, named critical references and observed evidence. Applicable conflicts or missing required inputs stop dependent work; provenance warnings remain visible and advisory. core/pysrc/_artifactpromptlib.py Scheduling follows the full dependency ancestry and exposes unresolved ancestor IDs and reasons. Reconciled progress remains advisory; blocked ancestors prevent premature downstream readiness while independent tasks remain available. Response-budget omissions are explicit, retain the global scheduling decision and direct callers to supported detail reads. core/artifacts/internal/operations/assistive.go Resolve current identities → eligible tasks only HTML: complete contextual read ticket → task-start Then separately compose and deliver each actor’s scoped input Legacy Markdown keeps its own dependency/state rules
Related entries Pinned evidence S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. Selected agent
Spec-compliance review Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes A new explicit batch review can select a passing rerun of still-reviewed work without replacing the original task review. The selected run must match its own recorded workspace; changed source or supporting evidence still requires reassessment. core/artifacts/internal/evidence/completion.go Implementation works directly or delegates a coherent unit when useful. Bounded task context, applicable dependency advice and observed checks support progress while preserving actual user stops and host permissions. Verification checks the change against a recorded SMARTS rationale for material invalidation only. core/surface/skills/subagent-driven-development/SKILL.md Read-only task-context reports direct dependencies and unresolved ancestors, scoped_changed, scoped_unchanged or unassessed inputs, and actual check observations. Missing broader context remains explicit; the packet does not certify verification. core/artifacts/internal/operations/task_context.go Independent task-spec review and actual source-bound observations still precede acceptance. The current source repairs Claude launch/child correlation and native Unicode observation hashing; neither repair substitutes an author’s report for a reviewer receipt. Re-arm requests made stale by the applicable engine upgrade rather than relabeling old evidence.
Related entries Pinned evidence S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S32 · core/pysrc/_artifactauthoritylib.pyNative artifact ID grammar, producer states, Claude join lock, UTF-8/UTF-16-key-order observation binding. S40 · CHANGELOG.mdMerge-scope record for review-join, marker, ID/reorder, Unicode, prerequisite and engine-wait repairs. Selected gate
Fresh task verification Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md A new explicit batch review can select a passing rerun of still-reviewed work without replacing the original task review. The selected run must match its own recorded workspace; changed source or supporting evidence still requires reassessment. core/artifacts/internal/evidence/completion.go The skill index connects planning, direct or delegated implementation, proportional verification and selected context maintenance to their owning workflows. core/surface/skills/INDEX.md Implementation works directly or delegates a coherent unit when useful. Bounded task context, applicable dependency advice and observed checks support progress while preserving actual user stops and host permissions. Verification checks the change against a recorded SMARTS rationale for material invalidation only. core/surface/skills/subagent-driven-development/SKILL.md Confirmed fixes require regression RED/GREEN. Features use current criterion-focused checks and meaningful negative controls where needed; refactors preserve passing characterization baselines. Coverage, lint and applicable security requirements remain explicit. core/surface/skills/tdd/SKILL.md Read-only task-context reports direct dependencies and unresolved ancestors, scoped_changed, scoped_unchanged or unassessed inputs, and actual check observations. Missing broader context remains explicit; the packet does not certify verification. core/artifacts/internal/operations/task_context.go Task-check observations now retain directly referenced criterion identity and an optional bounded source-input fingerprint or an explicit unassessed reason, without executing tests or minting approval receipts. core/artifacts/internal/operations/task_check.go New checks bind the selected criterion and applicable constraint bodies, including explicit references and scope applicability. Unrelated constraints remain outside the digest; old observations never gain unassessed constraint coverage. core/artifacts/internal/model/assistive.go The closed task-check request accepts bounded command observations matched to plan definitions. Ordinary context-preview and context-finalize-preview omit prompt identity; context-apply accepts an exact preview reference and digest. Invalid requests, changed preimages and stale CAS writes remain rejected. The historical smarts-apply request accepts the 0.2.0 SMARTS decision record. init-store takes a protocol-only request. core/artifacts/internal/operations/protocol.go The unpublished 0.3.2 native schema adds optional shared_inputs and scoped task-check fields without silently relabeling old records. core/artifacts/schemas/common.schema.json The bounded source-fingerprint reader hashes actual declared task/shared paths, directory membership and known build-control files; unsafe, missing and over-limit scopes are explicitly unassessed rather than blocking work or proving a full dependency graph. core/artifacts/internal/operations/input_scope.go Delegated authors preserve the caller-selected verification approach: genuine regression RED/GREEN for fixes, current criterion-focused feature checks and passing characterization baselines for refactors. Actual results and pending checks return to the caller; staging requires assigned scope and authorization. core/surface/includes/author-tdd-workflow.md Characterization tests can pass against existing correct behavior. Preserve behavioral assertions against the post-backfill baseline; mechanical import or symbol-reference updates retain the same oracle. Coverage and parity checks remain required. A precise surface table proceeds under existing user authorization; only material expansion or a changed outcome needs another decision. Distinct restructuring strategies are compared with SMARTS only after surface and parity are settled. core/surface/skills/refactor/SKILL.md Only an actual verifier wrapper executable/script prefix selects authority handling. Inert PowerShell data mentioning the filename is not a verifier call; malformed real verifier invocations still fail closed. Fresh legacy context approval arming is refused; historical pending routes remain readable. core/pysrc/_artifactauthoritylib.py Run the plan’s proving command again Read output and exit code HTML: real producer-owned receipts
Related entries Pinned evidence S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. Selected gate
Correction is not permission to waive a gate Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md The sprint caller performs an index-first recorded-intent read, preserves actual owner decisions and ADR conflicts, then proceeds with authorized work without a second artifact approval system. A SMARTS Unknown names its missing observation and cannot bypass a hard gate or manufacture authority. core/surface/SPRINT.md Attended feature execution now treats checkpoints as progress groups, not compulsory approval stops; it forwards real failures and continues independent work. core/surface/skills/executing-plans/SKILL.md Implementation works directly or delegates a coherent unit when useful. Bounded task context, applicable dependency advice and observed checks support progress while preserving actual user stops and host permissions. Verification checks the change against a recorded SMARTS rationale for material invalidation only. core/surface/skills/subagent-driven-development/SKILL.md An unanswered legacy reconciliation can be superseded only when route and pending state agree and no durable attempt or matching observed reply exists. Captured replies recover through their original immutable source and receipt; in-flight mutations retain exact replay and real user stops. core/pysrc/_reconciliationlib.py The installed recover command finishes a captured original reply or replays an in-flight mutation without asking for a new user answer. core/pysrc/artifact-reconcile.py The closed task-check request accepts bounded command observations matched to plan definitions. Ordinary context-preview and context-finalize-preview omit prompt identity; context-apply accepts an exact preview reference and digest. Invalid requests, changed preimages and stale CAS writes remain rejected. The historical smarts-apply request accepts the 0.2.0 SMARTS decision record. init-store takes a protocol-only request. core/artifacts/internal/operations/protocol.go The candidate-only runbook distinguishes 0.3.1/0.3.2 mixed-schema readers, exact replay and forward recovery while preserving recorded user stops. The paired prompt retirement scans immutable observed replies before calling a request unanswered; submitted or uncertain decisions are never erased. Older-client downgrade after modern edits remains unsupported. docs/artifacts/ASSISTIVE-UPGRADE.md Ordinary approval and sprint instructions bypass legacy capture without changing pending history or inventing authority. Explicit legacy replies retain exact matching. The paired adapter can retire a genuinely unanswered 0.2 sprint-pair request using its serialized cancellation lock and submission check; submitted decisions must replay, while standalone approval 0.1 refuses automatic retirement. core/pysrc/_approvallib.py Ordinary prerequisite instructions bypass legacy capture. The existing adapter can retire only a validated ARMED pending question under its original per-plan OS lock. Confirmed or captured decisions are not disposable; no authority receipt or new native permission API is created. core/pysrc/_prerequisitelib.py The old paired approval producer publishes a content-addressed observed reply before its durable submission. Cancellation checks the matching observation, content hash, prompt and frozen context under its existing lock, with a strict scan bound. A matching or uncertain pre-submission reply blocks automatic retirement; normal tasks and context reads have no added cost. core/pysrc/_sprintapprovallib.py The optional reference retains strict historical evidence inputs without replacing ordinary work. Explicit draft source refresh preserves progressed plans and history with both CAS bindings; initial approval restrictions remain on historical paired attestation. Its verify command requires literal absolute paths; linked agent subdirectories remain unsupported for strict authority review. These limitations apply to requested attestation, not ordinary task start. core/surface/includes/artifacts-attestation.md Scheduling follows the full dependency ancestry and exposes unresolved ancestor IDs and reasons. Reconciled progress remains advisory; blocked ancestors prevent premature downstream readiness while independent tasks remain available. Response-budget omissions are explicit, retain the global scheduling decision and direct callers to supported detail reads. core/artifacts/internal/operations/assistive.go Explicit draft source refresh retains both source CAS components and same-pair identity without requiring an unstarted plan. Existing progress, approvals and evidence are preserved without asserting current authority. Dependency invalidation preserves an independently BLOCKED task and its reason. Verification summaries disclose conflicting caller reports separately from receipt freshness; later successful verification covers only reports present when its context was issued. core/artifacts/internal/operations/lifecycle.go Ordinary uppercase words such as Approve DATA migration remain ordinary input. All-letter capture codes require a matching retained request; real armed replies, mismatches and user stops preserve their original handling. core/pysrc/_replylib.py Only an actual verifier wrapper executable/script prefix selects authority handling. Inert PowerShell data mentioning the filename is not a verifier call; malformed real verifier invocations still fail closed. Fresh legacy context approval arming is refused; historical pending routes remain readable. core/pysrc/_artifactauthoritylib.py Bounded isolated Python stdin diagnostics may read literal protected paths or git show HEAD objects. Unknown code, mutable calls, shell expansion and extra commands retain the guard checks; ordinary commands avoid AST parsing. core/pysrc/_bashguardlib.py After interruption, resume through the existing exact identity and durable operation outcome. Correct stale context or missing authority at its own boundary. The newer engine wait defaults to 120 seconds, but this is not a latency objective or an extension of outer host deadlines. This atlas does not benchmark runtime responsiveness.
Related entries Pinned evidence S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. S40 · CHANGELOG.mdMerge-scope record for review-join, marker, ID/reorder, Unicode, prerequisite and engine-wait repairs. Selected agent
Combined quality review Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes A new explicit batch review can select a passing rerun of still-reviewed work without replacing the original task review. The selected run must match its own recorded workspace; changed source or supporting evidence still requires reassessment. core/artifacts/internal/evidence/completion.go Implementation works directly or delegates a coherent unit when useful. Bounded task context, applicable dependency advice and observed checks support progress while preserving actual user stops and host permissions. Verification checks the change against a recorded SMARTS rationale for material invalidation only. core/surface/skills/subagent-driven-development/SKILL.md Task-check observations now retain directly referenced criterion identity and an optional bounded source-input fingerprint or an explicit unassessed reason, without executing tests or minting approval receipts. core/artifacts/internal/operations/task_check.go Human HTML presents reported command checks in an escaped, explicitly unverified section; implementation state and source validation remain distinct. core/artifacts/internal/render/render.go The bounded source-fingerprint reader hashes actual declared task/shared paths, directory membership and known build-control files; unsafe, missing and over-limit scopes are explicitly unassessed rather than blocking work or proving a full dependency graph. core/artifacts/internal/operations/input_scope.go The optional reference retains strict historical evidence inputs without replacing ordinary work. Explicit draft source refresh preserves progressed plans and history with both CAS bindings; initial approval restrictions remain on historical paired attestation. Its verify command requires literal absolute paths; linked agent subdirectories remain unsupported for strict authority review. These limitations apply to requested attestation, not ordinary task start. core/surface/includes/artifacts-attestation.md Once per authored scope / checkpoint Actual combined diff + fresh reviewer inputs No CRITICAL/HIGH; rerun after corrections Scope of one uses the same rule
Related entries Pinned evidence S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. S18 · core/surface/includes/review-matrix.mdShared diff-path reviewer selection for review/checkpoint/preview; callers retain their own gates. Selected state
accept-scope / current proof Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md A new explicit batch review can select a passing rerun of still-reviewed work without replacing the original task review. The selected run must match its own recorded workspace; changed source or supporting evidence still requires reassessment. core/artifacts/internal/evidence/completion.go The sprint caller performs an index-first recorded-intent read, preserves actual owner decisions and ADR conflicts, then proceeds with authorized work without a second artifact approval system. A SMARTS Unknown names its missing observation and cannot bypass a hard gate or manufacture authority. core/surface/SPRINT.md Attended feature execution now treats checkpoints as progress groups, not compulsory approval stops; it forwards real failures and continues independent work. core/surface/skills/executing-plans/SKILL.md Implementation works directly or delegates a coherent unit when useful. Bounded task context, applicable dependency advice and observed checks support progress while preserving actual user stops and host permissions. Verification checks the change against a recorded SMARTS rationale for material invalidation only. core/surface/skills/subagent-driven-development/SKILL.md The commit owner checks authorization, the staged diff, secrets and the verification approach appropriate to the change. Current criterion checks, genuine fix regressions and refactor parity retain their distinct evidence requirements. Reuse applicable observed checks and reviews across phases. Managed v2 maintenance selects affected claims and uses native paired writes; unknown evidence defers that document. core/surface/skills/commit-gate/SKILL.md PR readiness uses the explicit base-to-HEAD subject for current checks, secrets scanning and applicable specialized review. Existing evidence is reused only while its source and inputs match. Merge requires authorization and exact-head hosted CI. core/surface/skills/finishing-a-development-branch/SKILL.md An unanswered legacy reconciliation can be superseded only when route and pending state agree and no durable attempt or matching observed reply exists. Captured replies recover through their original immutable source and receipt; in-flight mutations retain exact replay and real user stops. core/pysrc/_reconciliationlib.py The bounded source-fingerprint reader hashes actual declared task/shared paths, directory membership and known build-control files; unsafe, missing and over-limit scopes are explicitly unassessed rather than blocking work or proving a full dependency graph. core/artifacts/internal/operations/input_scope.go The candidate-only runbook distinguishes 0.3.1/0.3.2 mixed-schema readers, exact replay and forward recovery while preserving recorded user stops. The paired prompt retirement scans immutable observed replies before calling a request unanswered; submitted or uncertain decisions are never erased. Older-client downgrade after modern edits remains unsupported. docs/artifacts/ASSISTIVE-UPGRADE.md The optional reference retains strict historical evidence inputs without replacing ordinary work. Explicit draft source refresh preserves progressed plans and history with both CAS bindings; initial approval restrictions remain on historical paired attestation. Its verify command requires literal absolute paths; linked agent subdirectories remain unsupported for strict authority review. These limitations apply to requested attestation, not ordinary task start. core/surface/includes/artifacts-attestation.md Status separates reported DONE from independently ACCEPTED work, shows actual blocked decisions, and does not infer an approval request from draft governance state. core/surface/commands/status.md HTML: one whole-scope operation All required current receipts must agree Markdown: authoritative ledger transition No rendered labels as authority
Related entries Pinned evidence S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. Handoffs, branches and returns Context / how the layers are assembled Durable knowledge → selective task input → actual actor delivery → independent proof. These are different boundaries.
Selected skill
Greenfield / decompose Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Greenfield interviews persist under plans/decomposition and retain actual decisions. Five document/v2-provenance pairs use context-draft and context-apply; context-finalize binds all thirteen outputs. ADRs and task rows use their owners, and retained interview evidence survives finalization. core/surface/skills/decompose/SKILL.md Vision → users → scope → technical shape Integrations → risks, each persisted Architecture / phased plan / backlog User-reviewed decisions and context
Related entries Pinned evidence S14 · core/surface/skills/decompose/SKILL.mdCurrent greenfield interview and completion contract re-read. Its persisted six-layer draft flow remains separate from the brownfield writer lifecycle. Selected skill
Brownfield / context-creation Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The skill index connects planning, direct or delegated implementation, proportional verification and selected context maintenance to their owning workflows. core/surface/skills/INDEX.md Codex dispatch requires attestation only for explicitly claimed host proof; an unavailable requested farm backend is reported without silently switching provider or model. Ordinary context inspection can proceed inline within actual host permissions; an agent label supplies no containment or semantic verification. core/surface/includes/codex-host-notes.md Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md Optional context scouts report only their assigned scope, source identities, coverage, conflicts and unknowns. Six logical categories do not require six child agents. A role label or read-only instruction proves neither sandbox containment nor independent semantic verification; actual host permissions and excluded paths still apply. core/surface/agents/scout.md Qualified read-only scout profile first Six full / affected scoped assignments Bounded report-only synthesis Native content + provenance transactions
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected state
.codearbiter/ project knowledge Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The finite context contract permits a whole-document Markdown entry only as the sole entry for one of five named content targets. Explicit typed field entries remain available; the writer does not expose arbitrary repository-file writes. core/artifacts/internal/contextdocument/contract.go Whole-document replacement requires the explicit document selection and exact existing bytes. It preserves CONTEXT frontmatter and initialization state, checks the named document identity and Markdown structure, and retains the code-map size limit. Human content outside the authorized change remains the caller's preservation obligation. core/artifacts/internal/contextdocument/document_selection.go Initial finalization binds thirteen output identities, rechecks supporting source evidence, and changes the initialization marker with its paired provenance digest. Ordinary finalization requires no artifact approval receipt and does not certify semantic correctness. Already initialized repositories refuse a new finalization. core/artifacts/internal/contextdocument/finalization.go The context schema describes both finite field entries and the explicit whole-document entry for the five supported content documents. Its typed structure records evidence references; schema validity does not establish that the claims were independently reviewed. core/artifacts/schemas/context.schema.json Greenfield interviews persist under plans/decomposition and retain actual decisions. Five document/v2-provenance pairs use context-draft and context-apply; context-finalize binds all thirteen outputs. ADRs and task rows use their owners, and retained interview evidence survives finalization. core/surface/skills/decompose/SKILL.md Routine maintenance selects changed v2 claims intersecting staged sources using a current bounded snapshot. Unknown evidence defers the affected document; native paired writes preserve owned fields and current identities. core/pysrc/_provenancelib.py CONTEXT: purpose, vocabulary, stage and limits Stack: scoped test/build commands and author mapping Standards + security: rules with preserved human ownership Brownfield: five content docs + their v2 provenance pairs ADRs, boards and greenfield plans retain separate owners
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S14 · core/surface/skills/decompose/SKILL.mdCurrent greenfield interview and completion contract re-read. Its persisted six-layer draft flow remains separate from the brownfield writer lifecycle. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected state
L1 / startup state Enabled repo: stage, questions, tasks, overrides and hygiene briefing SessionStart carries live state, not the composed persona
Related entries Pinned evidence S17 · docs/hooks.mdDocumented host event differences and startup live-state injection; not blanket enforcement proof. Selected state
L3 / owner + scope rules Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The lazy reference map routes provenance drift or requested initialized refresh to context-check after reading selected documents, provenance and the code map. The owner reuses selected scope and existing authorization. core/surface/includes/reference-map.md Read the invoked command/skill body Scope touch → reference-map docs Read relevant ADR/deferral bodies Indexes first; no bulk directory reads
Related entries Pinned evidence S03 · core/surface/arbiter.mdIntent-to-owner routing, on-demand loading, caller extent and mode boundary. S04 · core/surface/includes/routing-table.mdAuthoritative intent-to-owner table, scope-touch routes and stop/return semantics. S05 · core/surface/includes/reference-map.mdScope-to-governing-document and specialist mapping. Selected state
L3a / read-time hints Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Bounded read-time pointers include ordinary draft and ready HTML specs as advisory context. Rejected or withdrawn specs stay excluded; no pointer confers approval. core/pysrc/_readinjectlib.py A bounded pointer, not a full document security > ADRs > specs > standards Freshness and dedup are advisory Host event surfaces differ
Related entries Pinned evidence S16 · core/pysrc/_readinjectlib.pyCurrent file-read pointer and dedup implementation interface read; advisory hints remain separate from task-time selected input. S17 · docs/hooks.mdDocumented host event differences and startup live-state injection; not blanket enforcement proof. S24 · core/pysrc/_readinjectlib.pyCurrent approved_spec_index implementation still filters *.md; do not infer typed-HTML read-hint parity. Selected state
L4 / approved specification Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md The pinned native bridge enables task-context as a bounded informational read and does not require future reviewer/approval producers simply to author a structurally valid draft. Context requests route to ordinary context-preview, context-finalize-preview and exact-reference context-apply; historical receipt input stays a separate compatibility path. Installed host qualification is separate. Native Pi writer admission does not establish a complete live Pi workflow. On NO_LOCAL_STORE the client runs init-store once and retries the request once; a refused initialization keeps NO_LOCAL_STORE. On Windows the binary's architecture comes from the kernel (IsWow64Process2), never WMI or PROCESSOR_* environment. Index and outline pages are now fully checked before rows are yielded, including continuation identity and row shape. core/pysrc/_artifactlib.py Bounded read-time pointers include ordinary draft and ready HTML specs as advisory context. Rejected or withdrawn specs stay excluded; no pointer confers approval. core/pysrc/_readinjectlib.py Stable artifact and criterion IDs Behavior • boundaries • non-goals Contracts and accepted intent Normative change invalidates approval
Related entries Pinned evidence S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. S06 · core/surface/commands/feature.mdCurrent feature owner: same-format resume and full/small gates; adds actual per-actor context composition. S07 · core/surface/SPRINT.mdInitial paired approval; full-plan execution; delegated methods; recovery and farm boundaries. Selected state
L5 / exactly bound plan Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md The pinned native bridge enables task-context as a bounded informational read and does not require future reviewer/approval producers simply to author a structurally valid draft. Context requests route to ordinary context-preview, context-finalize-preview and exact-reference context-apply; historical receipt input stays a separate compatibility path. Installed host qualification is separate. Native Pi writer admission does not establish a complete live Pi workflow. On NO_LOCAL_STORE the client runs init-store once and retries the request once; a refused initialization keeps NO_LOCAL_STORE. On Windows the binary's architecture comes from the kernel (IsWow64Process2), never WMI or PROCESSOR_* environment. Index and outline pages are now fully checked before rows are yielded, including continuation identity and row shape. core/pysrc/_artifactlib.py Keep spec criteria, plan tasks, prerequisites and exact engine-returned IDs. Valid native IDs need not start with SPEC- or PLAN-. A typed exact-permutation record reorder keeps identities/history but is a normative edit that invalidates approval; it does not silently authorize reexecution.
Related entries Pinned evidence S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. S32 · core/pysrc/_artifactauthoritylib.pyNative artifact ID grammar, producer states, Claude join lock, UTF-8/UTF-16-key-order observation binding. S40 · CHANGELOG.mdMerge-scope record for review-join, marker, ID/reorder, Unicode, prerequisite and engine-wait repairs. Selected gate
L6 / complete task-context read Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md Read-only task-context reports direct dependencies and unresolved ancestors, scoped_changed, scoped_unchanged or unassessed inputs, and actual check observations. Missing broader context remains explicit; the packet does not certify verification. core/artifacts/internal/operations/task_context.go Task-check observations now retain directly referenced criterion identity and an optional bounded source-input fingerprint or an explicit unassessed reason, without executing tests or minting approval receipts. core/artifacts/internal/operations/task_check.go New checks bind the selected criterion and applicable constraint bodies, including explicit references and scope applicability. Unrelated constraints remain outside the digest; old observations never gain unassessed constraint coverage. core/artifacts/internal/model/assistive.go Exact and batch symbol retrieval exposes reported check history without an approval ticket. Outline paging now accounts for encoded rows incrementally while retaining response budgets and continuation behavior. core/artifacts/internal/read/read.go Human HTML presents reported command checks in an escaped, explicitly unverified section; implementation state and source validation remain distinct. core/artifacts/internal/render/render.go The unpublished 0.3.2 native schema adds optional shared_inputs and scoped task-check fields without silently relabeling old records. core/artifacts/schemas/common.schema.json The bounded source-fingerprint reader hashes actual declared task/shared paths, directory membership and known build-control files; unsafe, missing and over-limit scopes are explicitly unassessed rather than blocking work or proving a full dependency graph. core/artifacts/internal/operations/input_scope.go Scheduling follows the full dependency ancestry and exposes unresolved ancestor IDs and reasons. Reconciled progress remains advisory; blocked ancestors prevent premature downstream readiness while independent tasks remain available. Response-budget omissions are explicit, retain the global scheduling decision and direct callers to supported detail reads. core/artifacts/internal/operations/assistive.go Explicit draft source refresh retains both source CAS components and same-pair identity without requiring an unstarted plan. Existing progress, approvals and evidence are preserved without asserting current authority. Dependency invalidation preserves an independently BLOCKED task and its reason. Verification summaries disclose conflicting caller reports separately from receipt freshness; later successful verification covers only reports present when its context was issued. core/artifacts/internal/operations/lifecycle.go Bounded isolated Python stdin diagnostics may read literal protected paths or git show HEAD objects. Unknown code, mutable calls, shell expansion and extra commands retain the guard checks; ordinary commands avoid AST parsing. core/pysrc/_bashguardlib.py identity → index → outline → scoped read Follow contextual pages to completion Retain the final engine context ticket Exact read alone is context-incomplete Stale cursor or ticket → read again
Related entries Pinned evidence S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. Selected state
A context ticket is neither a model memory nor a signature of semantic truth Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md Typed engine context tickets bind complete task reads. They do not establish actual actor delivery, semantic truth or fresh runtime evidence.
Related entries Pinned evidence S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. Selected agent
Author context Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Authors and reviewers share task-critical reference and constraint checks. Missing or stale provenance remains advisory. Two delivery attempts end with an advisory unknown observation, without another retry or an invented receipt. core/pysrc/_contextselectlib.py Feature actors receive scoped requirements, named critical references and observed evidence. Applicable conflicts or missing required inputs stop dependent work; provenance warnings remain visible and advisory. core/pysrc/_artifactpromptlib.py Fresh task obligation + delivered scoped input Check worktree, source and constraints TDD retains the original caller’s gates
Related entries Pinned evidence S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S09 · core/surface/skills/tdd/SKILL.mdCurrent TDD context preflight and obligation derivation re-read. Six-phase gate sequence also confirmed by current skill index; fix and test-only paths do not fabricate feature artifacts. S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. Selected agent
Reviewer context Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Authors and reviewers share task-critical reference and constraint checks. Missing or stale provenance remains advisory. Two delivery attempts end with an advisory unknown observation, without another retry or an invented receipt. core/pysrc/_contextselectlib.py Feature actors receive scoped requirements, named critical references and observed evidence. Applicable conflicts or missing required inputs stop dependent work; provenance warnings remain visible and advisory. core/pysrc/_artifactpromptlib.py A review binds one resolved diff and supplies scoped inputs to each reviewer. Missing critical references or applicable conflicts prevent a substantive verdict; provenance and unobserved delivery diagnostics remain advisory. core/surface/commands/review.md Own fresh packet; never reuse author input Required refs + independent source checks Reviewer delivery is separately tracked
Related entries Pinned evidence S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S28 · core/surface/commands/review.mdCurrent full review owner: stable diff resolution, selected context delivered independently to each reviewer, local verdict before separately authorized posting. S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. Selected gate
Runner + authority producers Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md A new explicit batch review can select a passing rerun of still-reviewed work without replacing the original task review. The selected run must match its own recorded workspace; changed source or supporting evidence still requires reassessment. core/artifacts/internal/evidence/completion.go Read-only task-context reports direct dependencies and unresolved ancestors, scoped_changed, scoped_unchanged or unassessed inputs, and actual check observations. Missing broader context remains explicit; the packet does not certify verification. core/artifacts/internal/operations/task_context.go An unanswered legacy reconciliation can be superseded only when route and pending state agree and no durable attempt or matching observed reply exists. Captured replies recover through their original immutable source and receipt; in-flight mutations retain exact replay and real user stops. core/pysrc/_reconciliationlib.py Task-check observations now retain directly referenced criterion identity and an optional bounded source-input fingerprint or an explicit unassessed reason, without executing tests or minting approval receipts. core/artifacts/internal/operations/task_check.go The closed task-check request accepts bounded command observations matched to plan definitions. Ordinary context-preview and context-finalize-preview omit prompt identity; context-apply accepts an exact preview reference and digest. Invalid requests, changed preimages and stale CAS writes remain rejected. The historical smarts-apply request accepts the 0.2.0 SMARTS decision record. init-store takes a protocol-only request. core/artifacts/internal/operations/protocol.go The bounded source-fingerprint reader hashes actual declared task/shared paths, directory membership and known build-control files; unsafe, missing and over-limit scopes are explicitly unassessed rather than blocking work or proving a full dependency graph. core/artifacts/internal/operations/input_scope.go The candidate-only runbook distinguishes 0.3.1/0.3.2 mixed-schema readers, exact replay and forward recovery while preserving recorded user stops. The paired prompt retirement scans immutable observed replies before calling a request unanswered; submitted or uncertain decisions are never erased. Older-client downgrade after modern edits remains unsupported. docs/artifacts/ASSISTIVE-UPGRADE.md Ordinary approval and sprint instructions bypass legacy capture without changing pending history or inventing authority. Explicit legacy replies retain exact matching. The paired adapter can retire a genuinely unanswered 0.2 sprint-pair request using its serialized cancellation lock and submission check; submitted decisions must replay, while standalone approval 0.1 refuses automatic retirement. core/pysrc/_approvallib.py The old paired approval producer publishes a content-addressed observed reply before its durable submission. Cancellation checks the matching observation, content hash, prompt and frozen context under its existing lock, with a strict scan bound. A matching or uncertain pre-submission reply blocks automatic retirement; normal tasks and context reads have no added cost. core/pysrc/_sprintapprovallib.py The optional reference retains strict historical evidence inputs without replacing ordinary work. Explicit draft source refresh preserves progressed plans and history with both CAS bindings; initial approval restrictions remain on historical paired attestation. Its verify command requires literal absolute paths; linked agent subdirectories remain unsupported for strict authority review. These limitations apply to requested attestation, not ordinary task start. core/surface/includes/artifacts-attestation.md Codex dispatch requires attestation only for explicitly claimed host proof; an unavailable requested farm backend is reported without silently switching provider or model. Ordinary context inspection can proceed inline within actual host permissions; an agent label supplies no containment or semantic verification. core/surface/includes/codex-host-notes.md Historical sprint approval and SMARTS proof instructions remain available only for existing explicit attestation, outside the ordinary execution path. core/surface/includes/sprint-authority.md Ordinary uppercase words such as Approve DATA migration remain ordinary input. All-letter capture codes require a matching retained request; real armed replies, mismatches and user stops preserve their original handling. core/pysrc/_replylib.py Only an actual verifier wrapper executable/script prefix selects authority handling. Inert PowerShell data mentioning the filename is not a verifier call; malformed real verifier invocations still fail closed. Fresh legacy context approval arming is refused; historical pending routes remain readable. core/pysrc/_artifactauthoritylib.py Bounded isolated Python stdin diagnostics may read literal protected paths or git show HEAD objects. Unknown code, mutable calls, shell expansion and extra commands retain the guard checks; ordinary commands avoid AST parsing. core/pysrc/_bashguardlib.py Receipts and current source identity are distinct from displayed status and semantic correctness. Current source uses native canonical Unicode hashing for observation binding. Host read-dedup markers are runtime state, not plan-authorized verification inputs; the marker repair must not be generalized into arbitrary .gitignore exclusions.
Related entries Pinned evidence S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. S32 · core/pysrc/_artifactauthoritylib.pyNative artifact ID grammar, producer states, Claude join lock, UTF-8/UTF-16-key-order observation binding. S40 · CHANGELOG.mdMerge-scope record for review-join, marker, ID/reorder, Unicode, prerequisite and engine-wait repairs. Selected state
L7 / acceptance evidence Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md A new explicit batch review can select a passing rerun of still-reviewed work without replacing the original task review. The selected run must match its own recorded workspace; changed source or supporting evidence still requires reassessment. core/artifacts/internal/evidence/completion.go Status separates reported DONE from independently ACCEPTED work, shows actual blocked decisions, and does not infer an approval request from draft governance state. core/surface/commands/status.md task-review → combined quality accept-scope → current acceptance Commit and finish query proof again
Related entries Pinned evidence S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. S11 · core/surface/skills/commit-gate/SKILL.mdCurrent Phase 5.5 through terminal commit rules re-read. Legacy heal vocabulary must not be generalized to v2 paired native writes. S12 · core/surface/skills/finishing-a-development-branch/SKILL.mdWatch/cleanup early routing; commit and acceptance preflight; PR and merge authority. Selected skill
Legacy v1 heal / native v2 refresh Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Ordinary create/adopt/update preserves the same source-evidence, selection and compare-and-swap checks as the native transaction. Missing or matching v1 provenance can be adopted; existing v2 ownership can transition through explicit whole-document selection. Original document/provenance preimages remain in transaction history for exact recovery. core/artifacts/internal/contextdocument/operations.go A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md The lazy reference map routes provenance drift or requested initialized refresh to context-check after reading selected documents, provenance and the code map. The owner reuses selected scope and existing authorization. core/surface/includes/reference-map.md v1: conditional staged-source auto-heal v2: selected owned-field preview + receipt Identity match is not semantic verification No raw v2 rebaseline fallback
Related entries Pinned evidence S11 · core/surface/skills/commit-gate/SKILL.mdCurrent Phase 5.5 through terminal commit rules re-read. Legacy heal vocabulary must not be generalized to v2 paired native writes. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected skill
Retained state / bounded recovery Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Ordinary create/adopt/update preserves the same source-evidence, selection and compare-and-swap checks as the native transaction. Missing or matching v1 provenance can be adopted; existing v2 ownership can transition through explicit whole-document selection. Original document/provenance preimages remain in transaction history for exact recovery. core/artifacts/internal/contextdocument/operations.go A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md Scheduling follows the full dependency ancestry and exposes unresolved ancestor IDs and reasons. Reconciled progress remains advisory; blocked ancestors prevent premature downstream readiness while independent tasks remain available. Response-budget omissions are explicit, retain the global scheduling decision and direct callers to supported detail reads. core/artifacts/internal/operations/assistive.go Explicit draft source refresh retains both source CAS components and same-pair identity without requiring an unstarted plan. Existing progress, approvals and evidence are preserved without asserting current authority. Dependency invalidation preserves an independently BLOCKED task and its reason. Verification summaries disclose conflicting caller reports separately from receipt freshness; later successful verification covers only reports present when its context was issued. core/artifacts/internal/operations/lifecycle.go Refresh keeps initialization and human history Recover native operations by the same ID Committed results are read back, not rewritten Decisions remain with their actual owner
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected state
Select task-relevant context Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Authors and reviewers share task-critical reference and constraint checks. Missing or stale provenance remains advisory. Two delivery attempts end with an advisory unknown observation, without another retry or an invented receipt. core/pysrc/_contextselectlib.py select_task_context is inert. The caller acquires current inputs and native instruction precedence. Copied upstream rules, source-scoped ADRs and declared commands do not gain authority or current verification from packet inclusion.
Related entries Pinned evidence S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. Selected skill
Compose for this lane and actor Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Authors and reviewers share task-critical reference and constraint checks. Missing or stale provenance remains advisory. Two delivery attempts end with an advisory unknown observation, without another retry or an invented receipt. core/pysrc/_contextselectlib.py Feature actors receive scoped requirements, named critical references and observed evidence. Applicable conflicts or missing required inputs stop dependent work; provenance warnings remain visible and advisory. core/pysrc/_artifactpromptlib.py Confirmed fixes preserve causal evidence and a named regression. Delegated input retains critical requirements; advisory delivery exhaustion ends retries while actual missing inputs and conflicts retain their dependent-work boundary. Distinct remediation strategies are compared with SMARTS only after the root cause is confirmed. core/surface/commands/fix.md compose_feature_actor_input is named by the current feature/TDD/SDD contracts. compose_fix_or_test_actor_input preserves bug origin and the existing route. prepare_review_input blocks missing critical references before a substantive verdict.
Related entries Pinned evidence S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. S09 · core/surface/skills/tdd/SKILL.mdCurrent TDD context preflight and obligation derivation re-read. Six-phase gate sequence also confirmed by current skill index; fix and test-only paths do not fabricate feature artifacts. S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. S28 · core/surface/commands/review.mdCurrent full review owner: stable diff resolution, selected context delivered independently to each reviewer, local verdict before separately authorized posting. Selected gate
Bound actual actor delivery Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Authors and reviewers share task-critical reference and constraint checks. Missing or stale provenance remains advisory. Two delivery attempts end with an advisory unknown observation, without another retry or an invented receipt. core/pysrc/_contextselectlib.py Confirmed fixes preserve causal evidence and a named regression. Delegated input retains critical requirements; advisory delivery exhaustion ends retries while actual missing inputs and conflicts retain their dependent-work boundary. Distinct remediation strategies are compared with SMARTS only after the root cause is confirmed. core/surface/commands/fix.md A review binds one resolved diff and supplies scoped inputs to each reviewer. Missing critical references or applicable conflicts prevent a substantive verdict; provenance and unobserved delivery diagnostics remain advisory. core/surface/commands/review.md prepare_actor_delivery binds the selected packet digest, actor/task, actual worktree and observable epochs. The caller sends delivery_text on deliver and retains the counted attempt. A reported host-load-event or child-input-capture is not a native task-admission certificate.
Related entries Pinned evidence S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. Selected warn
Reselect or stop Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Authors and reviewers share task-critical reference and constraint checks. Missing or stale provenance remains advisory. Two delivery attempts end with an advisory unknown observation, without another retry or an invented receipt. core/pysrc/_contextselectlib.py Two counted attempts apply to the same actor/task/worktree/epoch/packet binding. Unknown epochs cannot make a saved receipt current. No shared session marker or author receipt substitutes for a reviewer’s input delivery.
Related entries Pinned evidence S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. S08 · core/surface/skills/subagent-driven-development/SKILL.mdCurrent implementation-dispatch and independent spec-review sections re-read; remaining scope contract also checked against current skill index. Fresh actor input and bounded delivery are distinct from engine tickets. Handoffs, branches and returns Change lanes / alternate entries and exits Different starting evidence creates different obligations. A fix, a refactor, a docs edit and an experiment do not share identical ceremony.
Handoffs, branches and returns Review + delivery / evidence and authority Review, commit and branch disposition retain separate authority; release preparation stops at its PR.
Selected cmd
/review · /checkpoint Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes A review binds one resolved diff and supplies scoped inputs to each reviewer. Missing critical references or applicable conflicts prevent a substantive verdict; provenance and unobserved delivery diagnostics remain advisory. core/surface/commands/review.md A checkpoint retains the reviewed commit, UTC review-start time and worktree dirty state, then writes the report through its aggregator. last-checkpoint holds only the override count. core/surface/commands/checkpoint.md Checkpoint reports persist observed source_commit, recorded_at and worktree_dirty values together with every review finding. Missing anchors remain unknown. core/surface/agents/checkpoint-aggregator.md /review: current diff /checkpoint: periodic codebase sweep /preview predicts only; no verdict /tribunal and /threat-model are opt-in
Related entries Pinned evidence S04 · core/surface/includes/routing-table.mdAuthoritative intent-to-owner table, scope-touch routes and stop/return semantics. S18 · core/surface/includes/review-matrix.mdShared diff-path reviewer selection for review/checkpoint/preview; callers retain their own gates. S21 · core/surface/skills/INDEX.mdCurrent routine-owner index: five debug dispositions, bounded workflow owners and unchanged six-phase TDD / nine-phase commit sequence. Selected agent
Fresh inputs → scoped reviewer fleet Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Authors and reviewers share task-critical reference and constraint checks. Missing or stale provenance remains advisory. Two delivery attempts end with an advisory unknown observation, without another retry or an invented receipt. core/pysrc/_contextselectlib.py A review binds one resolved diff and supplies scoped inputs to each reviewer. Missing critical references or applicable conflicts prevent a substantive verdict; provenance and unobserved delivery diagnostics remain advisory. core/surface/commands/review.md Select current context for each reviewer Required refs + native instruction order Deliver to that actual child, not its parent Then dispatch by the actual diff paths Preserve capability and evidence gaps
Related entries Pinned evidence S28 · core/surface/commands/review.mdCurrent full review owner: stable diff resolution, selected context delivered independently to each reviewer, local verdict before separately authorized posting. S27 · core/pysrc/_contextselectlib.pyInert scoped selector and delivery implementation: commands/cwd/evidence, native instruction order, actor/worktree/epoch binding, two-attempt limit and reviewer preflight. S18 · core/surface/includes/review-matrix.mdShared diff-path reviewer selection for review/checkpoint/preview; callers retain their own gates. Selected cmd
/commit Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Routine artifact instructions now focus on the installed writer, typed plan, bounded task reads, factual prerequisites, actual checks and safe retry. The default leaf is about 7.3 KB and includes an executable stdin bootstrap with optional operation-schema discovery; explicit attestation remains available on demand without burdening ordinary task context. A spec's SMARTS design rationale lives in its approach, decisions and one SEC-SMARTS section. core/surface/includes/artifacts.md Current staged scope TDD complete where applicable Typed plans: current acceptance No status-label substitutes
Related entries Pinned evidence S11 · core/surface/skills/commit-gate/SKILL.mdCurrent Phase 5.5 through terminal commit rules re-read. Legacy heal vocabulary must not be generalized to v2 paired native writes. S10 · core/surface/includes/artifacts.mdInstalled admission, typed reads, context completion, authority receipts and format boundaries. Selected gate
Phases 4–6 / prove + inspect Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md 4 Focused tests, lint, secrets, scope gates 5 Fresh behavioral proof 5.5 Legacy v1 staged-source auto-heal 6 Complete diff review v2 pairs require native selected updates
Related entries Pinned evidence S11 · core/surface/skills/commit-gate/SKILL.mdCurrent Phase 5.5 through terminal commit rules re-read. Legacy heal vocabulary must not be generalized to v2 paired native writes. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected cmd
/release · selected target Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Release preparation inserts a new version below the entire Unreleased section and above prior versions, preserving pending notes. This guidance correction does not grant publication authority or replace the existing release-PR and hosted qualification boundaries. core/surface/skills/release/SKILL.md Resolve declared target + policy Prepare reviewed release surfaces Dry-run stops at its report
Related entries Pinned evidence S33 · core/surface/skills/release/SKILL.mdInteractive release preparation and mandatory release-PR boundary; qualified hosted tag composition. Handoffs, branches and returns Knowledge + operations / supporting routes These entries have bounded outputs: decisions, reports, board transitions, repair or runtime posture. They do not implicitly enter implementation.
Selected skill
context-check / selected refresh Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The user-facing route table points feature and sprint work at useful planned execution and selected context refresh at its existing owner. Existing authorization covers ordinary work; actual host, destructive-action and commit controls remain. core/surface/includes/routing-table.md The skill index connects planning, direct or delegated implementation, proportional verification and selected context maintenance to their owning workflows. core/surface/skills/INDEX.md The preparation helper binds bounded drafts and retained sources to exact document/provenance preimages. Finalization preparation hashes all thirteen required outputs and retains missing output failures without modifying files. core/pysrc/_contextwriterlib.py A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md Report v1 and v2 states separately Select affected docs or explicit full refresh Qualified scouts + native v2 pair writes
Related entries Pinned evidence S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. Selected out
Status / drift report Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md Read-only report, or selected native update Keep marker, unselected files and history No staging, commit or reinitialization
Related entries Pinned evidence S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. Selected cmd
/audit → dated governance packet Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes A checkpoint retains the reviewed commit, UTC review-start time and worktree dirty state, then writes the report through its aggregator. last-checkpoint holds only the override count. core/surface/commands/checkpoint.md Checkpoint reports persist observed source_commit, recorded_at and worktree_dirty values together with every review finding. Missing anchors remain unknown. core/surface/agents/checkpoint-aggregator.md Checkpoint audit windows use the report timestamp and an ancestor commit. Invalid or missing anchors require an explicit ref/date window; dirty review scope remains a stated limitation. core/surface/commands/audit.md Read source records for a selected window. Preserve audit lines. Write a new packet only; never overwrite the source or an older packet.
Related entries Pinned evidence S02 · core/surface/COMMANDS.mdCatalog, modes, host-limited commands and purpose of each public route. S04 · core/surface/includes/routing-table.mdAuthoritative intent-to-owner table, scope-touch routes and stop/return semantics. Selected cmd
/decompose · /create-context Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The installed context-draft command prepares a paired document preview; context-finalize prepares initial finalization. context-apply commits the exact selected preview and digest. Context modes preserve scaffold and initialized refresh boundaries. core/pysrc/init-codearbiter.py Initial brownfield setup checks the intended repository and actual host permissions, then uses bounded inspection and the installed safe context writer. Ordinary Windows work needs no special scout profile or per-document artifact approval. An existing initialized repository routes to selected refresh instead of another scaffold or population cycle. core/surface/commands/init.md Greenfield interviews persist under plans/decomposition and retain actual decisions. Five document/v2-provenance pairs use context-draft and context-apply; context-finalize binds all thirteen outputs. ADRs and task rows use their owners, and retained interview evidence survives finalization. core/surface/skills/decompose/SKILL.md Initial population only: /init --greenfield / --brownfield. Initialized refresh stays with /status drift and explicit selection.
Related entries Pinned evidence S23 · core/surface/commands/init.mdCurrent init owner: activation/scaffold versus initial population; initialized refresh belongs to status drift, not reinitialization. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Handoffs, branches and returns Brownfield context · create, refresh, recover One content/provenance pair per native transaction; initial finalization is separate. Existing human records retain their owners.
Selected cmd
Initial population Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The installed context-draft command prepares a paired document preview; context-finalize prepares initial finalization. context-apply commits the exact selected preview and digest. Context modes preserve scaffold and initialized refresh boundaries. core/pysrc/init-codearbiter.py Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md Initial brownfield setup checks the intended repository and actual host permissions, then uses bounded inspection and the installed safe context writer. Ordinary Windows work needs no special scout profile or per-document artifact approval. An existing initialized repository routes to selected refresh instead of another scaffold or population cycle. core/surface/commands/init.md /init --brownfield → context-creation Meaningful source; initialized marker absent A stub is not a completed project context
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S23 · core/surface/commands/init.mdCurrent init owner: activation/scaffold versus initial population; initialized refresh belongs to status drift, not reinitialization. Selected cmd
Initialized refresh Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The preparation helper binds bounded drafts and retained sources to exact document/provenance preimages. Finalization preparation hashes all thirteen required outputs and retains missing output failures without modifying files. core/pysrc/_contextwriterlib.py The installed context-draft command prepares a paired document preview; context-finalize prepares initial finalization. context-apply commits the exact selected preview and digest. Context modes preserve scaffold and initialized refresh boundaries. core/pysrc/init-codearbiter.py A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md The lazy reference map routes provenance drift or requested initialized refresh to context-check after reading selected documents, provenance and the code map. The owner reuses selected scope and existing authorization. core/surface/includes/reference-map.md Routine maintenance selects changed v2 claims intersecting staged sources using a current bounded snapshot. Unknown evidence defers the affected document; native paired writes preserve owned fields and current identities. core/pysrc/_provenancelib.py /status drift → context-check Read-only report, then explicit scoped/full choice Do not clear the marker or rerun initialization
Related entries Pinned evidence S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected cmd
Interrupted operation Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Ordinary context-preview retains an inert proposal and exact preimages without approval or review claims. context-apply revalidates the digest, closed request and preview binding before the native paired transaction; context-finalize-preview uses the same exact-reference path for initial population. No approve-context reply is required. core/artifacts/internal/operations/context_assistive.go Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md Inventory actual files, provenance and outcome Inspect the same operation ID and native journal Do not blindly repeat a possibly committed write
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. Selected gate
Qualified containment first Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Codex dispatch requires attestation only for explicitly claimed host proof; an unavailable requested farm backend is reported without silently switching provider or model. Ordinary context inspection can proceed inline within actual host permissions; an agent label supplies no containment or semantic verification. core/surface/includes/codex-host-notes.md Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md Initial brownfield setup checks the intended repository and actual host permissions, then uses bounded inspection and the installed safe context writer. Ordinary Windows work needs no special scout profile or per-document artifact approval. An existing initialized repository routes to selected refresh instead of another scaffold or population cycle. core/surface/commands/init.md Optional context scouts report only their assigned scope, source identities, coverage, conflicts and unknowns. Six logical categories do not require six child agents. A role label or read-only instruction proves neither sandbox containment nor independent semantic verification; actual host permissions and excluded paths still apply. core/surface/agents/scout.md The optional context-profile preparation helper is a repository-only CI fixture, not installed plugin capability. Caller-owned OS/tool containment, child binding, launch budgets and actual observations must be qualified before dispatch. Unknown host behavior keeps this step unavailable.
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. Selected agent
Bounded logical assignments Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Codex dispatch requires attestation only for explicitly claimed host proof; an unavailable requested farm backend is reported without silently switching provider or model. Ordinary context inspection can proceed inline within actual host permissions; an agent label supplies no containment or semantic verification. core/surface/includes/codex-host-notes.md Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md Optional context scouts report only their assigned scope, source identities, coverage, conflicts and unknowns. Six logical categories do not require six child agents. A role label or read-only instruction proves neither sandbox containment nor independent semantic verification; actual host permissions and excluded paths still apply. core/surface/agents/scout.md A–F cover stack, infrastructure, architecture, security, tests and data. Scope/subdivision/retries retain one run ledger and frozen source boundary. No missing or failed transport can be counted as complete coverage.
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected skill
Validate and join reports Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md Optional context scouts report only their assigned scope, source identities, coverage, conflicts and unknowns. Six logical categories do not require six child agents. A role label or read-only instruction proves neither sandbox containment nor independent semantic verification; actual host permissions and excluded paths still apply. core/surface/agents/scout.md Closed assignment/snapshot binding 48 KiB normalized join limit Missing / failed transport → block Recheck the source snapshot
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. Selected state
Five content targets Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The finite context contract permits a whole-document Markdown entry only as the sole entry for one of five named content targets. Explicit typed field entries remain available; the writer does not expose arbitrary repository-file writes. core/artifacts/internal/contextdocument/contract.go Whole-document replacement requires the explicit document selection and exact existing bytes. It preserves CONTEXT frontmatter and initialization state, checks the named document identity and Markdown structure, and retains the code-map size limit. Human content outside the authorized change remains the caller's preservation obligation. core/artifacts/internal/contextdocument/document_selection.go The context schema describes both finite field entries and the explicit whole-document entry for the five supported content documents. Its typed structure records evidence references; schema validity does not establish that the claims were independently reviewed. core/artifacts/schemas/context.schema.json Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md CONTEXT.md • tech-stack.md coding-standards.md security-controls.md • code-map.md Each with .provenance/<doc>.json
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected skill
Finite typed preview Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The pinned native bridge enables task-context as a bounded informational read and does not require future reviewer/approval producers simply to author a structurally valid draft. Context requests route to ordinary context-preview, context-finalize-preview and exact-reference context-apply; historical receipt input stays a separate compatibility path. Installed host qualification is separate. Native Pi writer admission does not establish a complete live Pi workflow. On NO_LOCAL_STORE the client runs init-store once and retries the request once; a refused initialization keeps NO_LOCAL_STORE. On Windows the binary's architecture comes from the kernel (IsWow64Process2), never WMI or PROCESSOR_* environment. Index and outline pages are now fully checked before rows are yielded, including continuation identity and row shape. core/pysrc/_artifactlib.py The closed task-check request accepts bounded command observations matched to plan definitions. Ordinary context-preview and context-finalize-preview omit prompt identity; context-apply accepts an exact preview reference and digest. Invalid requests, changed preimages and stale CAS writes remain rejected. The historical smarts-apply request accepts the 0.2.0 SMARTS decision record. init-store takes a protocol-only request. core/artifacts/internal/operations/protocol.go The preparation helper binds bounded drafts and retained sources to exact document/provenance preimages. Finalization preparation hashes all thirteen required outputs and retains missing output failures without modifying files. core/pysrc/_contextwriterlib.py The installed context-draft command prepares a paired document preview; context-finalize prepares initial finalization. context-apply commits the exact selected preview and digest. Context modes preserve scaffold and initialized refresh boundaries. core/pysrc/init-codearbiter.py Ordinary context-preview retains an inert proposal and exact preimages without approval or review claims. context-apply revalidates the digest, closed request and preview binding before the native paired transaction; context-finalize-preview uses the same exact-reference path for initial population. No approve-context reply is required. core/artifacts/internal/operations/context_assistive.go The finite context contract permits a whole-document Markdown entry only as the sole entry for one of five named content targets. Explicit typed field entries remain available; the writer does not expose arbitrary repository-file writes. core/artifacts/internal/contextdocument/contract.go Whole-document replacement requires the explicit document selection and exact existing bytes. It preserves CONTEXT frontmatter and initialization state, checks the named document identity and Markdown structure, and retains the code-map size limit. Human content outside the authorized change remains the caller's preservation obligation. core/artifacts/internal/contextdocument/document_selection.go The context schema describes both finite field entries and the explicit whole-document entry for the five supported content documents. Its typed structure records evidence references; schema validity does not establish that the claims were independently reviewed. core/artifacts/schemas/context.schema.json A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md The lazy reference map routes provenance drift or requested initialized refresh to context-check after reading selected documents, provenance and the code map. The owner reuses selected scope and existing authorization. core/surface/includes/reference-map.md New document or selected owned field Current source / target identities Exact proposed content + provenance Unsupported human layout → refuse
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected gate
Native approve-context reply Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The closed task-check request accepts bounded command observations matched to plan definitions. Ordinary context-preview and context-finalize-preview omit prompt identity; context-apply accepts an exact preview reference and digest. Invalid requests, changed preimages and stale CAS writes remain rejected. The historical smarts-apply request accepts the 0.2.0 SMARTS decision record. init-store takes a protocol-only request. core/artifacts/internal/operations/protocol.go The optional reference retains strict historical evidence inputs without replacing ordinary work. Explicit draft source refresh preserves progressed plans and history with both CAS bindings; initial approval restrictions remain on historical paired attestation. Its verify command requires literal absolute paths; linked agent subdirectories remain unsupported for strict authority review. These limitations apply to requested attestation, not ordinary task start. core/surface/includes/artifacts-attestation.md Ordinary context-preview retains an inert proposal and exact preimages without approval or review claims. context-apply revalidates the digest, closed request and preview binding before the native paired transaction; context-finalize-preview uses the same exact-reference path for initial population. No approve-context reply is required. core/artifacts/internal/operations/context_assistive.go Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md Review this exact proposed pair Capture actual host-observed consent No reused approval, hash-only consent or caller-supplied authority
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected out
Receipt-only native apply Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The pinned native bridge enables task-context as a bounded informational read and does not require future reviewer/approval producers simply to author a structurally valid draft. Context requests route to ordinary context-preview, context-finalize-preview and exact-reference context-apply; historical receipt input stays a separate compatibility path. Installed host qualification is separate. Native Pi writer admission does not establish a complete live Pi workflow. On NO_LOCAL_STORE the client runs init-store once and retries the request once; a refused initialization keeps NO_LOCAL_STORE. On Windows the binary's architecture comes from the kernel (IsWow64Process2), never WMI or PROCESSOR_* environment. Index and outline pages are now fully checked before rows are yielded, including continuation identity and row shape. core/pysrc/_artifactlib.py The closed task-check request accepts bounded command observations matched to plan definitions. Ordinary context-preview and context-finalize-preview omit prompt identity; context-apply accepts an exact preview reference and digest. Invalid requests, changed preimages and stale CAS writes remain rejected. The historical smarts-apply request accepts the 0.2.0 SMARTS decision record. init-store takes a protocol-only request. core/artifacts/internal/operations/protocol.go The installed context-draft command prepares a paired document preview; context-finalize prepares initial finalization. context-apply commits the exact selected preview and digest. Context modes preserve scaffold and initialized refresh boundaries. core/pysrc/init-codearbiter.py Ordinary context-preview retains an inert proposal and exact preimages without approval or review claims. context-apply revalidates the digest, closed request and preview binding before the native paired transaction; context-finalize-preview uses the same exact-reference path for initial population. No approve-context reply is required. core/artifacts/internal/operations/context_assistive.go Ordinary create/adopt/update preserves the same source-evidence, selection and compare-and-swap checks as the native transaction. Missing or matching v1 provenance can be adopted; existing v2 ownership can transition through explicit whole-document selection. Original document/provenance preimages remain in transaction history for exact recovery. core/artifacts/internal/contextdocument/operations.go The lazy reference map routes provenance drift or requested initialized refresh to context-check after reading selected documents, provenance and the code map. The owner reuses selected scope and existing authorization. core/surface/includes/reference-map.md The context-request bridge invokes the qualified installed writer. Source-only builds do not authorize native context writes. Paired per-document atomicity does not mean all documents become visible atomically as one set.
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected warn
Preserve other owners and human bytes Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The preparation helper binds bounded drafts and retained sources to exact document/provenance preimages. Finalization preparation hashes all thirteen required outputs and retains missing output failures without modifying files. core/pysrc/_contextwriterlib.py The finite context contract permits a whole-document Markdown entry only as the sole entry for one of five named content targets. Explicit typed field entries remain available; the writer does not expose arbitrary repository-file writes. core/artifacts/internal/contextdocument/contract.go Whole-document replacement requires the explicit document selection and exact existing bytes. It preserves CONTEXT frontmatter and initialization state, checks the named document identity and Markdown structure, and retains the code-map size limit. Human content outside the authorized change remains the caller's preservation obligation. core/artifacts/internal/contextdocument/document_selection.go Ordinary create/adopt/update preserves the same source-evidence, selection and compare-and-swap checks as the native transaction. Missing or matching v1 provenance can be adopted; existing v2 ownership can transition through explicit whole-document selection. Original document/provenance preimages remain in transaction history for exact recovery. core/artifacts/internal/contextdocument/operations.go A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md Task / question boards, append-only audit history, release targets and ADRs keep their own writers. No raw Write/Edit fallback on refusal.
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected out
Initial finalize: separate approval Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The pinned native bridge enables task-context as a bounded informational read and does not require future reviewer/approval producers simply to author a structurally valid draft. Context requests route to ordinary context-preview, context-finalize-preview and exact-reference context-apply; historical receipt input stays a separate compatibility path. Installed host qualification is separate. Native Pi writer admission does not establish a complete live Pi workflow. On NO_LOCAL_STORE the client runs init-store once and retries the request once; a refused initialization keeps NO_LOCAL_STORE. On Windows the binary's architecture comes from the kernel (IsWow64Process2), never WMI or PROCESSOR_* environment. Index and outline pages are now fully checked before rows are yielded, including continuation identity and row shape. core/pysrc/_artifactlib.py The closed task-check request accepts bounded command observations matched to plan definitions. Ordinary context-preview and context-finalize-preview omit prompt identity; context-apply accepts an exact preview reference and digest. Invalid requests, changed preimages and stale CAS writes remain rejected. The historical smarts-apply request accepts the 0.2.0 SMARTS decision record. init-store takes a protocol-only request. core/artifacts/internal/operations/protocol.go Ordinary context-preview retains an inert proposal and exact preimages without approval or review claims. context-apply revalidates the digest, closed request and preview binding before the native paired transaction; context-finalize-preview uses the same exact-reference path for initial population. No approve-context reply is required. core/artifacts/internal/operations/context_assistive.go Initial finalization binds thirteen output identities, rechecks supporting source evidence, and changes the initialization marker with its paired provenance digest. Ordinary finalization requires no artifact approval receipt and does not certify semantic correctness. Already initialized repositories refuse a new finalization. core/artifacts/internal/contextdocument/finalization.go Brownfield population covers six logical categories and five content documents through direct bounded inspection or optional scoped agents. The paired writer preserves source bindings and protected content; initial finalization checks all required outputs. core/surface/skills/context-creation/SKILL.md The finalized set includes exactly the five content documents, their five v2 provenance companions, open-tasks.md, open-questions.md and overrides.log. Valid empty boards and a zero-event audit header satisfy their actual contracts. A document-write receipt never substitutes for finalization.
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. Selected out
Refresh: retain initialized state Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes The installed context-draft command prepares a paired document preview; context-finalize prepares initial finalization. context-apply commits the exact selected preview and digest. Context modes preserve scaffold and initialized refresh boundaries. core/pysrc/init-codearbiter.py Whole-document replacement requires the explicit document selection and exact existing bytes. It preserves CONTEXT frontmatter and initialization state, checks the named document identity and Markdown structure, and retains the code-map size limit. Human content outside the authorized change remains the caller's preservation obligation. core/artifacts/internal/contextdocument/document_selection.go Initial finalization binds thirteen output identities, rechecks supporting source evidence, and changes the initialization marker with its paired provenance digest. Ordinary finalization requires no artifact approval receipt and does not certify semantic correctness. Already initialized repositories refuse a new finalization. core/artifacts/internal/contextdocument/finalization.go A drift audit stays read-only; an already authorized selected or full refresh proceeds without asking again per document. The installed draft/preview/apply example preserves source bindings and selected content. Matching hashes establish identity only; initialized refresh never reruns scaffolding, clears the marker or repeats finalization. core/surface/skills/context-check/SKILL.md Initial brownfield setup checks the intended repository and actual host permissions, then uses bounded inspection and the installed safe context writer. Ordinary Windows work needs no special scout profile or per-document artifact approval. An existing initialized repository routes to selected refresh instead of another scaffold or population cycle. core/surface/commands/init.md Routine maintenance selects changed v2 claims intersecting staged sources using a current bounded snapshot. Unknown evidence defers the affected document; native paired writes preserve owned fields and current identities. core/pysrc/_provenancelib.py Only selected pairs change Declare scoped versus full coverage Keep marker, human content and history No finalization, staging or commit here
Related entries Pinned evidence S26 · core/surface/skills/context-check/SKILL.mdInitialized refresh: read-only report, explicit selection, v1/v2 separation, native paired updates and preserved human history. Full owner read. Selected skill
Recover by the same operation ID Assistive workflow: source-bound implementation An agreed outcome becomes a maintained plan, direct or delegated implementation, proportional verification and an honest delivery report. Task context and dependency advice support progress; real user stops and host permissions remain effective. Greenfield and brownfield population use the paired native writer and exact finalization. Exact blob bindings identify inspected source bytes; the linked revision is the committed source base. Implementation, verification, live host qualification and release remain separate claims.
Current source changes Ordinary context-preview retains an inert proposal and exact preimages without approval or review claims. context-apply revalidates the digest, closed request and preview binding before the native paired transaction; context-finalize-preview uses the same exact-reference path for initial population. No approve-context reply is required. core/artifacts/internal/operations/context_assistive.go Ordinary create/adopt/update preserves the same source-evidence, selection and compare-and-swap checks as the native transaction. Missing or matching v1 provenance can be adopted; existing v2 ownership can transition through explicit whole-document selection. Original document/provenance preimages remain in transaction history for exact recovery. core/artifacts/internal/contextdocument/operations.go Initial finalization binds thirteen output identities, rechecks supporting source evidence, and changes the initialization marker with its paired provenance digest. Ordinary finalization requires no artifact approval receipt and does not certify semantic correctness. Already initialized repositories refuse a new finalization. core/artifacts/internal/contextdocument/finalization.go Do not reset the project directory, clear the marker, overwrite a human file, or retry an already committed write. Finalization recovery is checked separately. A genuinely absent output needs a fresh typed preview and its own approval.
Related entries Pinned evidence S13 · core/surface/skills/context-creation/SKILL.mdCurrent brownfield owner: qualified containment, bounded reports and join, scoped gaps, native document/provenance writes, separate 13-identity finalization and recovery. Handoffs, branches and returns Debug · evidence, dispositions and safe handoff Investigation is read-only. A validated packet carries evidence; the original caller still owns permission to act.
Handoffs, branches and returns Tribunal: source-bound audit to completed follow-up An opt-in review route, not a required gate. Candidate findings, verification, report and completion are distinct.
Handoffs, branches and returns