Expand description
A branch’s ticks and what their evidence comes to: the payload of
speccoder attest verify --branch (and attest badge)
(branch_verify), the rule that turns per-tick outcomes into the
branch’s conclusion, and the badge.
The rules are here, pure, so every interface (the binary, the check run, the badge) concludes the same from the same ticks.
Structs§
- Anchor
- Where an annotation lands: a file and a 1-based line, at the head.
- Badge
- The badge: a shields.io endpoint document, and the same as an SVG.
- Branch
Report - Result of
speccoder attest verify --branch/speccoder attest badge. - Branch
Totals - Counts by outcome, in the verdict bar’s order.
- Skipped
Task - A task skipped by a person’s decision: no tick, not counted.
- Tick
- A ticked task at the checked head.
- Tick
Report - One tick’s report.
Enums§
- Conclusion
- The branch’s conclusion.
- Mode
- Which units a check covers.
- Tick
Kind - What a checked task is.
- Tick
Outcome - A tick’s outcome.
- Unverifiable
- Why a tick’s evidence does not verify.
Constants§
- EARLIER_
TASK_ REGRESSIONS not_evaluated: earlier-task regressions have no signed record this verifier could read yet.- TRAILER_
ONLY_ TASKS not_evaluated: a trailer-only bug task (Spec-Task: <unit>/bug:<slug>) is in the checked range, and this version cannot check it.
Functions§
- share
- Evidenced (not stale) over all ticks;
Nonewith none.