Conformance and implementation matrix

September 19, 2026 ยท View on GitHub

This matrix describes the contents of this bundle, not every possible DGP implementation.

AreaNormative specSchema/examplesExercised executable behaviorReference server
Core frames/assessments/commitsYesYes50 original tests, including HTTP/SQLite/concurrencyThreadDesk
Assessment batching amendmentOptional profileSeparate schema and examplesSelected offline binding/partial-response checksNot implemented
Coding tools amendmentOptional profileSeparate schema and examplesSelected operation/effect/artifact checksNot implemented
Graph previews and speculative recordsYesYesOriginal testsThreadDesk
Text/service inputs and image evidenceYesYesFixture-based providers and image guardsThreadDesk
Rubric/probability judgmentsYesYesAdapter/result-contract testsAdapter support; app emits choice/input only
Partial coverage and interface catalogueYesYesCatalogue-reference/uniqueness testsNot implemented
Frame projections and assessment basisYesYesCanonical-binding, altered/missing evidence checksNot implemented
Prepared operation catalogueYesYesSchema/variables examplesNot implemented
Budgeted evaluation/admission/jobsYesYesBudget snapshots and job lifecycle contract testsNo scheduler/worker/ledger server
Resumable eventsYesYesPage order/stream/duplication checksNo live/replay event server
Cross-interface handoffYesYesRecord/result requirementsNo handoff executor
GraphQLOptional bindingSDL and example documentsJS validator script syntax only; parser dependency unavailableNo server
MCPMappingTool mapping documentationNo MCP transport testsNo server
Farm Energy CalculatorApplication profileTwo frames plus expanded profile examplesTwelve embedded-input cases; no numerical calculationsNot implemented

The new 41 profile tests are selected contract tests. They do not demonstrate distributed quota enforcement, actual evidence fetching, secure identity delegation, durable jobs, event replay, or numerical optimality. Those need an implementation and integration tests.

Native UI/API/CLI functions are allowed to bypass the DGP interaction sequence, but not underlying domain authorization, relevant revision updates, or shared accounting. They need not fabricate DGP assessments or receipts for native operations.

Conformance claims must enumerate supported features and bindings. A final specification is not a production certification or a claim that every optional feature is runnable.