Expand description
What the model answers, one type per answer. Each schema it is held to
is derived from its type (agentplane::tools::strict_schema), so a field
and its description live in one place; the provider enforces the schema
during generation and agentplane validates the answer against it.
An enum’s variants are explained in the enum’s doc, so the model reads them in one description.
Structs§
- Acceptance
- The acceptance tests written before the code.
- Approach
- One way to build an idea.
- Assessment
- Convergence’s assessment of the code against the spec.
- Assumption
- Where the person’s words came from, and the question that settles it.
- Attempt
Report - An attempt’s closing report: the model’s claim, never its verdict.
- Blocked
- A
report_blockedcall: the honest exit, checked against its evidence. - Expectation
- What a scenario’s test expects, in the person’s words.
- Explored
- An exploration’s closing report: approaches for the person to choose.
- File
- A file as written.
- Finding
- One gap convergence found.
- HeldOut
- The held-out tests.
- Held
OutFile - A held-out test file, never shown to the implementer.
- Hosted
- A hosted planning skill’s closing report.
- Monitoring
- The monitor’s review of an attempt’s diff.
- Proposal
- How a task would be done; recorded, never executed.
- Question
- An
ask_personcall. - Reproduction
- A reproduction of one statement of a bug.
- Reproductions
- A bug’s reproductions.
- Review
- The tests for the person’s review, with what each expects.
- Review
File - A test file the person reviews before any code.
- Shaped
- The person’s words shaped into the spec’s language.
- Suspicion
- One suspicion of the monitor.
- Test
File - An acceptance test file and the scenarios it checks.
- Untestable
- A scenario no test can check, and why.
- Variant
- One variant of the code under test.
- Variants
- Variants of the code that measure what the tests tell apart.
Enums§
- Blocked
Kind - Why an attempt cannot go on, as its evidence shows.
- GapType
- What kind of gap between the spec and the code.
- Near
Miss Kind - A near-miss variant is a wrong implementation the tests must fail, or a permitted one they must pass.
- Severity
- How much a gap matters.
- Shortcut
- A kind of shortcut the monitor looks for.
- Special
Case Kind - A variant that special-cases the tests’ inputs.
- Status
- Whether an attempt or a hosted skill finished its work.
Functions§
- schema
- The strict schema of the answer
T.