Expand description
Pure domain types of speccoder.
This crate has no IO and no async: its state machines, task graph and
verdict rules stay property-testable without a runtime. The layering test
in the speccoder crate keeps its dependency closure free of IO and async
crates.
Modules§
- actions
- What a person can do now: one list, computed by the runtime and
rendered by every interface — the dashboard’s
n,cand:today, a desktop app or another workbench later. Every action is a CLI command too, so nothing an interface offers is out of reach of a script. - codes
- Stable codes for every result that is not plainly
ok: what went wrong, why it matters, how to fix it and where it is documented. A script branches on the code, a person reads the fix. - evidence
- A task’s evidence, as rows every interface renders.
- graph
- Task dependencies from what
tasks.mddocuments, and which tasks are ready. - next
- What to do next after a stop or a finish: a closed set of
outcomes and, for each, the commands that continue — deterministic, never
model text. The human
Next:block, the TUI footer anddata.nextare all this list. - retry
- Retries: the verifier’s failure digest for the next attempt, and the fingerprint that stops retries which cannot help.
- scope
- Task scope as a reported finding: which changed paths a task’s line did not name. Never a gate — a task line is prose, and a list of paths in it is a hint, not a contract.
- snapshot
- What speccoder sees in a Spec Kit project: the read-only snapshot that
inspectreports and every later subsystem consumes. - spec
- The format-neutral view of spec-driven work: which format a project is written in, and the requirements and acceptance scenarios a unit of work states. Spec Kit, OpenSpec and Kiro adapters produce it; the judge reads only it.
- stage
- The fixed stages of one task’s pipeline: one vocabulary for the
plain progress lines, the TUI, ACP updates and
status. - strength
- Acceptance strength: how well a task’s acceptance set tells right from wrong.
- verify
- The judge’s vocabulary: check results, baseline comparison, and verdicts .
Structs§
- Approval
View - A pending call as a person sees it: what, why, what it can reach, what the model claimed, and what approving it grants.
- Approvals
Report - Result of
speccoder report --approvals,approveandreject. - Archive
Report - Result of
speccoder spec archive(an OpenSpec change). - Attest
Report - Result of
speccoder attest verifyandattest sign. - Auth
Report - Result of
speccoder auth: who speccoder acts as on a GitHub host, and where its token comes from. The token itself is never shown. - Bench
Report - Result of
speccoder bench import. - Checklist
Status - One Spec Kit checklist (
specs/<feature>/checklists/*.md). - Code
Info - One code, as
explainshows it. - Command
Result - The result of one command, rendered as human text or as one JSON object.
- Config
Change - A change to
speccoder.toml: set a key, remove it, or append to a list. - Config
Key - One key: what it is, what it is set to, and what it is otherwise.
- Config
Report - Result of
speccoder config: the project’s configuration as a catalogue of every key, each with its type, default and value (when set). - Config
Section - One section of
speccoder.toml. - Config
Table - One configured named table, e.g.
[checks.test]. - Control
Report - Result of
accept,skipandnudge. - Converge
Report - Result of
speccoder converge. - Convergence
Round - One convergence round, from its commit.
- Cost
Report - Result of
speccoder report --cost. - Decided
Call - A person’s decision.
- Doctor
Check - One doctor check.
- Doctor
Report - Result of
speccoder doctor. - Drift
- What changed since a tick: the tick’s commit holds the intent
it was judged against; the checkout’s
HEADholds the intent now. - Earlier
Attempt - A failed attempt that was undone and retried.
- Eval
Case - One judged case.
- Eval
Report - Result of
speccoder eval. - Eval
Summary - Suite counts and metrics.
- Exit
Code - Process exit status of a command.
- Explain
Report - Result of
speccoder explain. - Feature
Entry - One feature (or change) of the project, as
speccoder featurelists it. - Feature
Report - Result of
speccoder runwithout--task: a feature worked through. - Features
Report - Result of
speccoder feature. - Full
Tier - The
fullcheck tier at the end of a feature. - Held
OutGap - Visible passes the held-out tests caught.
- Held
OutOracle - Held-out passes the hidden oracle agreed with, or not.
- InPlace
Report - Why an in-place run refused or stopped.
- Inbox
Item - One decision waiting for a person.
- Inbox
Report - Result of
speccoder inbox: every decision that waits for a person, across the project’s features, the most urgent first — the person’s work once the agents write the code. - Init
Check - One detected check.
- InitKey
- The model key
initlooked for. - Init
Report - Result of
speccoder init. - InitRun
- One check
initran on the untouched code. - Instruction
File - A repository instructions file given to an attempt.
- Issue
Entry - One open issue.
- Issues
Report - Result of
speccoder issue: the repository’s open GitHub issues, read through GitHub’s API as the person. - Last
Attempt - An attempt that did not pass, as saved under
refs/speccoder/attempts/. - Monitor
Score - The gaming monitor against the oracle’s ground truth: a positive is a cheat or a false completion (both passed the visible checks).
- Object
Verification - One task object’s verification.
- Open
Question - A question a document leaves open, to answer in place.
- Operator
View - Who decided, and how speccoder knows the name.
- Pending
Call - A call that stopped an attempt for approval, or a question, waiting for a person.
- PrReport
- Result of
speccoder pr: a draft pull request with the evidence. - Propose
Report - Result of
speccoder propose. - Refused
Path - A path that blocks worktree mode.
- Replay
Report - Result of
speccoder replay. - Requirement
Drift - One cited requirement, as the tick saw it and as the spec has it now.
- Review
Item - One requirement and its review.
- Review
Report - Result of
speccoder review: every requirement of the feature’s spec as a card, with the person’s decision on its exact wording. - Review
Totals - Counts of
ReviewItem::state. - RunReport
- Result of
speccoder run. - Schema
Name - One published schema.
- Schema
Report - Result of
speccoder schema. - Signer
View - Who signed.
- Skill
Entry - One installed Agent Skill.
- Skill
RunReport - Result of
speccoder spec <name>. - Skills
Report - Result of
speccoder specwithout a name. - Spec
Version - One commit of the spec and what it changed in its requirements.
- Status
Report - Result of
speccoder report: what the branch’s history shows. - Status
Totals - Counts of
TaskStatus::state. - Task
Cost - One task’s cost.
- Task
Status - One task and its evidence.
- Trace
Row - One row of the requirement → scenario → test → verdict matrix.
- UiReport
- Result of
speccoder ui, printed once the host listens (under--jsonthe only result: the host keeps serving after it). - Usage
- Token counts, and USD when prices are configured.
- Verify
Reason - Why an object got its outcome.
- Worktree
Report - Result of
speccoder worktree.
Enums§
- Command
Data - Command-specific payload of a result.
- Command
Status - Outcome class of a command.
- Doctor
Level - How a doctor check came out.
- Verify
Outcome - What
attest verifyfound for one task object.
Constants§
- PAYLOADS
- Every payload’s schema name, in
CommandData’s order. - SCHEMA_
VERSION - Version of the machine-readable command result. Fields may be added within a version; renaming or removing one, or changing its meaning, bumps it.