G.4:4.0 - Practitioner authoring path C1–C9
Complete these actions in order. Extend a step only when the task needs the additional input named there.
- C1 — Charter the scope. Name the exact
CG‑Frame,EntityOfConcern,ReferencePlane, task,CNSpecRef.edition, andCGSpecRef.edition. State the assumption envelope in ordinary language. - C2 — Declare one typed operator. Give it a stable id, CHR-typed signature, preconditions, result kind, and failure behavior. The card declares the operation under
A.6.1. Evidence for an application comes from its execution (§4.4a). - C3 — Declare one acceptance clause. Name the exact Characteristic and the A.6.1 argument declaration that admits the corresponding C.16 measurement-result episteme. Declare the predicate or threshold,
ClaimScope, any evaluation window required by the predicate or receiving use, any separate qualification window that limits use, unknown handling, and the stated stop, degrade, or abstain behavior. Keep the exact current result episteme for the later application. If the clause claims statistical risk or coverage control, also name the loss, target, calibration population and window, sampling or exchangeability assumptions, declared treatment of shift, and the exact policy that states the guarantee. - C4 — Compose only a legal flow. Cite the operators and gating clauses, preserve the lawful result kind, and keep a selected set when no lawful scalarization exists. A declared DAG is possible composition, not performed work.
- C5 — Name the minimum evidence/currentness need. Cite the exact A.10 source/provenance anchors and G.11 currentness conditions needed to judge the clause. Do not turn an evidence profile, citation, or graph membership into a verdict or actual reliance.
- C6 — Add an extension only when the task needs one. Select its current subject pattern first, then pin only the descriptor, distance, insertion, exploration, branch, or path records that change the present CAL action. Otherwise omit the extension.
- C7 — Record proof or an explicit gap. For every operator, flow, or clause, cite each required justification for legality, monotonicity or boundedness. If any required justification is missing, publish the gap and the consequent degrade/abstain behavior.
- C8 — Exercise declaration behavior. Provide one worked authoring example and focused conformance tests for illegal operations,
pass | fail | unknown, currentness conditions when they are part of admissibility, and failure behavior. The example and test remain declarations/test records unless separately grounded dated work is named. - C9 — Publish and hand off. Mint stable ids and continuity notes, then emit the smallest immutable
TaskMapedition. It cites the exact charter edition, the already constituted C.22TaskSignatureRef, the task, and edition-bearing operator, flow, gating-clause, and evidence-profile refs; the cited evidence profiles carry the needed currentness pins. It neither constructs the TaskSignature nor copies clause thresholds. Use G.11 for change refs; G.4 defines no refresh rule or runtime occurrence or result.
The path is complete when a reader unfamiliar with the author’s work can reconstruct the acceptance statement from the published ids and identify what must happen at runtime. The manifests, schemas, interfaces and optional extensions below make that same pack machine-citable. The order of work is C1–C9.