Expand description
The oracle at review: per requirement, the visible acceptance tests the run would use — written on the person’s request, red-checked on the current tree, shaped by the person and frozen with the approval — and the review comments anchored to what the person reads. These are the shapes every interface shows; none of them has a field that could hold a held-out test’s path or content.
Structs§
- Ambiguity
- Two authors read a scenario differently.
- Approve
Sheet - What the approve sheet shows besides the requirements: who can approve and run now, and what autopilot would hold.
- Autopilot
Denial - One call an autopilot run refused instead of asking.
- BugTest
- One confirmed reproduction.
- BugTests
- A bug’s confirmed reproductions as a bug unit’s Tests tab shows them, read only: a bug’s tests are written and confirmed by its own pipeline.
- Code
Comment - One line comment of the Code view.
- Comment
Draft - One comment in the tray.
- Comments
View - Result of
speccoder review comments: the tray and the last turn. - Expectation
- What an author states it asserts for one scenario.
- Held
OutSummary - The held-out set of a requirement as anyone may see it: a count, a state and a digest — never a path or a line of it.
- Offered
Grant - A grant an autopilot run may hold, offered on the approve sheet: one object-bound grant a person decided earlier for this feature.
- Oracle
Discarded - A test the author wrote that is not part of the set.
- Oracle
Rejected - A test the person rejected.
- Oracle
Test - One visible test as the review shows it.
- Oracle
View - One requirement’s oracle in the review: everything the Tests card shows.
- Reading
Text - One reading of a scenario: what one author expects.
- Resolution
- The person’s choice on an ambiguous scenario.
- Review
Approval - The record of an approval that froze the oracle (in
review.json). - Revision
View - What a revision turn did.
- Section
Diff - One section a revision changed, before and after (each cut to 4000 characters).
- Untestable
- A scenario an author found untestable, and why.
Enums§
- Authored
By - Who wrote a shown test.
- Comment
Anchor - What an anchored comment points at.
- Draft
State - Where a draft comment is.
- Oracle
Op - What a change to a requirement’s tests does.
- Oracle
State - Where a requirement’s oracle is.
- Reading
- One of the two readings of an ambiguous scenario.
- RunMode
- How a run started from the review asks for a person.
Functions§
- compare
- Where two authors’ stated expectations disagree: for a scenario, the
same given (normalised) with a different expected outcome; or one
covers it and the other declares it untestable. Different givens are
different examples, not a disagreement. In scenario order of
a. - normalise
- The deterministic ambiguity rule: words compared after trimming, collapsing whitespace and lowercasing.