decision-canon/workplans/DECISION-WP-0002-schema-probe.md

id	type	title	domain	repo	status	flavor	depends_on	owner	topic_slug	lane	created	updated	reviewed_at	reviewed_against_commit	quality_dor	quality_dor_at	quality_dor_by	quality_dor_note	state_hub_workstream_id
DECISION-WP-0002	workplan	Probe the schema draft with a diverse decision set	infotech	decision-canon	finished	planning		codex	canon	green	2026-10-04	2026-10-04	2026-10-04	ac58582	DoR-Ok	2026-10-04	grok	Bounded documentation probe. Verification is the review note. No production lane.	71d141a3-696f-500a-923c-e9c4428a9772

Probe the schema draft with a diverse decision set

Opened from DECISION-WP-0001-T03.

Milestone M0 is already in the tree. ResearchProgram.md collects comparative examples (M1) before any kernel freeze (M2). This workplan starts that probe with six situations and a written account of where DecisionObjectSchemaDraft.md is awkward. It does not freeze field names, publish a JSON Schema, or write the rest of the 25-decision corpus.

Scope

In scope: an example convention, six Markdown examples, and one review note.

Out of scope: a normative schema, application code, mappings to DMN or policy engines, kernel freeze, and the remaining M1 situations (hiring, procurement, investment, budget allocation, and public-style policy). Those wait on what the six examples show.

Dependencies: none. The seed documents reviewed at ac58582 are sufficient.

Lane: green. Documentation in this repository only. No production change and no credential use.

Verification: each example file exists and uses only the schema-draft sections the situation needs. reviews/schema-pressure.md names, for every example, the sections that were necessary, the sections that were awkward, and any question from ResearchProgram section 7 that the example raises. No automated test applies. The repository has no test command.

Define the example convention

id: DECISION-WP-0002-T01
status: done
priority: high
state_hub_task_id: "ed427f4f-ddd1-535b-9c48-b4f4636a2ba9"

Add examples/README.md stating the file shape: one Markdown decision per file, an identity id of the form DEC-EX-NNN, and only the schema-draft sections the situation needs. Name the six situations this workplan covers, taken from ResearchProgram M1: a trivial engineering choice, an architecture decision, an incident-response decision, a security exception, a deployment policy, and a constitutional governance rule. Do not add a JSON Schema.

Done. The convention is in examples/README.md. DEC-EX-001 is the D1 shape and does not repeat its id inside the YAML. The other five carry identity.id.

Write the six examples

id: DECISION-WP-0002-T02
status: done
priority: high
state_hub_task_id: "3f325298-6d04-5913-8100-a7d8dd37ca88"

Write one example file for each situation named in T01. Keep the trivial choice to the question, the choice, and the reason. Let the constitutional example carry governance and effects on later decisions. Leave unknown fields absent.

Done. The six files are under examples/. DEC-EX-001 is question, choice, and reason. DEC-EX-006 carries governance and two effects on later decisions.

Record schema pressure

id: DECISION-WP-0002-T03
status: done
priority: medium
state_hub_task_id: "18808c39-4b81-57df-892b-c3b2fddbb0bb"

Write reviews/schema-pressure.md. For each example, record which schema sections were necessary, which were awkward, and which questions from ResearchProgram section 7 the example raises. Stop when that note exists. Leave the schema draft unchanged unless an example cannot be written without one named clarification, and record that clarification in the note.

Done. The note is reviews/schema-pressure.md. DecisionObjectSchemaDraft.md is unchanged. No example needed a new field in order to be written. The D1 shape of DEC-EX-001 uses keys the draft does not name, and that is recorded rather than patched into the draft.

Evidence and handoff

The probe is finished. The successor is DECISION-WP-0003, which proposes the kernel cut from the note and does not edit the schema draft. The remaining M1 situations stay named there as deferred. They are not a second workplan yet, because more examples before that cut would repeat this probe.

Definition of Done is unassessed. This repository has no automated test suite.