Generated by bun run conformance:render — do not edit by hand.
Denominator: pinned Coverage Map docs/conformance/maps/cat-v1.0.json (generated 2026-06-22). See conform-ed ADR-0013 (map) and emergent ADR-0028 (overlay).
| Profile |
Requirements |
Done |
Partial |
Other |
Progress |
| delivery |
4 |
4 |
0 |
0 |
████████████████ 100% |
| operations |
2 |
0 |
2 |
0 |
░░░░░░░░░░░░░░░░ 0% |
| section |
2 |
2 |
0 |
0 |
████████████████ 100% |
| Req |
Level |
Status |
Evidence |
Statement |
| CAT-DEL-1 |
MUST |
✅ done |
cat:1.0:conf:delivery/CAT-DEL-1 |
An ItemStage MUST carry a stageId, the items to present, and the owning assessmentSectionId. |
| CAT-DEL-2 |
MUST |
✅ done |
cat:1.0:conf:delivery/CAT-DEL-2 |
An AssessmentResult MUST identify the result and section, list the items attempted (with attempt number), and state whether continuation is required; it carries the candidate response and outcome variables. |
| CAT-DEL-3 |
MUST |
✅ done |
cat:1.0:conf:delivery/CAT-DEL-3 |
A CatEngineResultReport MUST carry a reportId, the section, and a recommendation (continue/finish/suspend/abandon); it MAY carry the ability estimate, section score, delivered outcomes and the next item stage. |
| CAT-DEL-4 |
MUST |
✅ done |
cat:1.0:conf:delivery/CAT-DEL-4 |
An outcome/response variable MUST declare its cardinality (single/multiple/ordered/record) and base type; the SessionInfo status MUST be a value of the assessment-result status vocabulary. |
| Req |
Level |
Status |
Evidence |
Statement |
| CAT-OP-1 |
MUST |
🟡 partial |
cat:1.0:conf:operations/CAT-OP-1 |
A CAT engine MUST expose section management: create an adaptive section (POST /sections, from SectionData) and retrieve it (GET /sections/:id). |
| CAT-OP-2 |
MUST |
🟡 partial |
cat:1.0:conf:operations/CAT-OP-2 |
A CAT engine MUST support the adaptive cycle: create a session (POST /sessions), submit results to receive the next stage (POST /sessions/:id/results — AssessmentResult in, CatEngineResultReport out), and end the session (POST /sessions/:id/end) and section (POST /sections/:id/end). |
| Req |
Level |
Status |
Evidence |
Statement |
| CAT-SEC-1 |
MUST |
✅ done |
cat:1.0:conf:section/CAT-SEC-1 |
A SectionData MUST carry the section identifiers, the section resource href, an item pool of available items, and a creation timestamp. |
| CAT-SEC-2 |
MUST |
✅ done |
cat:1.0:conf:section/CAT-SEC-2 |
Each item-selection constraint MUST declare its type; constraint parameters are constraint-specific. |
- 83 literal items — 63 modelled ✅, 0 partial 🟡, 0 gaps ❌
- Silent gaps (in spec, not modelled): none
- conform-ed extensions (modelled, not in spec): none
cat:1.0:conf:delivery/CAT-DEL-1
- The engine emits each ItemStage carrying a stageId, the ItemRef(s) to present and the owning assessmentSectionId; the interop lane validates the opening stage against the real ItemStage schema and asserts those fields.
cat:1.0:conf:delivery/CAT-DEL-2
- buildItemAttemptResult constructs the AssessmentResult the platform submits per answered item — resultId, assessmentSectionId, itemsAttempted (with attemptNumber), continuationRequired and the SCORE outcome variable. Validated against the real AssessmentResult schema in the lane.
cat:1.0:conf:delivery/CAT-DEL-3
- selectNextStage returns a CatEngineResultReport carrying reportId, assessmentSectionId and a recommendation (continue/finish/suspend/abandon), plus the estimatedAbility / abilityStandardError and — while continuing — the next ItemStage. Validated against the real schema in the lane.
cat:1.0:conf:delivery/CAT-DEL-4
- The SCORE outcome variable declares cardinality ‘single’ and baseType ‘integer’; buildSessionInfo maps the cat_session state onto the SessionInfo status vocabulary (in_progress→active, complete→complete) and the lane validates it against the real SessionInfo schema.
cat:1.0:conf:operations/CAT-OP-1
- In-process section management is exercised by the lane (a pool-assembled SectionData opens into a first ItemStage); only the standardized REST surface at the spec’s section paths is outstanding.
cat:1.0:conf:operations/CAT-OP-2
- The full submit→report→next-stage cycle and its in-bounds termination are exercised end-to-end by the interop lane; only the standardized REST session surface is outstanding.
cat:1.0:conf:section/CAT-SEC-1
- buildCatSectionData / assembleCatSectionData produce a SectionData carrying the sectionIdentifier, assessmentSectionId, sectionHref, an itemPool of resolvable ItemRefs and a createdAt timestamp. Validated against the real SectionData schema in the lane.
cat:1.0:conf:section/CAT-SEC-2
- The stopping rule (min/max items, target standard error) is encoded as CatConstraints, each declaring its type and a constraint-specific parameters object; the lane validates every constraint against the real CatConstraint schema.