Module pipeline 

The run pipeline: one task (task), a feature (feature), and the pieces they share.

Re-exports

pub use feature::*;

pub use task::*;

Modules

acceptance

Spec-derived acceptance tests: written before the attempt, red then green.

bisect

Which tick made already-passing acceptance tests pass: a fact found by running the tests, never a guess from diffs.

bug

A bug task inside the pipeline. Before the attempt: reproduce — one test per Expected statement, red on the untouched code by an assertion twice, held-out variants sealed — and the person’s one confirmation; the confirmed reproductions are then reused at the checkpoint as the visible acceptance set. After an attempt that passed: every reproduction green, the pass-to-pass set green by name, the revert rejected, and each special case rejected. The rules are speccoder_core::bug’s.

commit

Commit messages, trailers and the records a finished attempt leaves.

feature

speccoder run over a whole feature, and converge.

full

The full check tier: once, after a run ticks a feature’s last task, and recorded so pr can refuse a branch whose full checks failed.

judge

The judge’s steps within one attempt: which writes a person approved, what the integrity audit finds, the verdict from the checks, and whether a failed attempt is worth retrying.

lanes

Parallel lanes for [P] tasks.

outcome

How a task run ends: its scope finding, what a failed attempt is saved as, the command’s status and message, and the progress event.

samples

Best-of-n: choosing among independent samples by evidence.

task

speccoder run --task: one task from baseline to tick.

Structs

RunId

One speccoder run from its fresh start to its end: run-<unix secs>-<8 hex>. Never one attempt’s agentplane run (a retry is a new one of those, in the same run).

RunOptions

How a run behaves beyond its configuration.