Development record

The claim recording gradient: an intent's three claim kinds carry three recording requirements, and the readiness gate holds them

disciplinedisciplinesminordisciplineitd-190

The rule

An intent carries up to three kinds of claim, each with its own recording requirement at the readiness gate:

Claim	Section	Requirement
Criterion	`## Acceptance Criteria` (Given/When/Then)	Mandatory — exists today per itd-1
Mechanism	`## Mechanism`	Prompted, nullable — declined with the nullity token; a present-but-empty section is a gate fault
Context	`## Scope Conditions`	Mandatory, with the nullity token as the explicit "none stated" — never left blank

The nullity grammar is one exact token: None stated., alone on its line under the section heading — the same grammar for both sections, so the gate distinguishes it from prose that happens to say "none" without semantics.

The distinction the gradient preserves: an absent section is a claim not carried; a recorded nullity is a claim considered and declined. They are never collapsed — three byte states, three semantics (absent; empty = gate fault; nullity token = declined). An auditor-side flag for mechanism-nullity intents lands with the record that owns verdicts, when one does — no rule ships without an owner.

Population is forward-only, per the ruled population properties: the gradient binds standalone intents at the readiness gate from adoption on; existing records are untouched (sparseness is information, and an absent stamp is never backfilled); discipline-kind records are exempt — their template carries no claim sections.

Each scope condition carries a persistent identity that survives edits to its text, so a later disposition (survived / narrowed / falsified / untested) attaches to the condition, not to a string.

The gate

Given an intent without scope conditions and without an explicit nullity, when the readiness gate runs, then the gate exits non-zero and names the missing field.
Given an intent whose ## Mechanism carries the nullity token, when the readiness gate runs, then the gate passes and reports the recorded nullity.
Given an intent whose ## Mechanism is present but empty, when the readiness gate runs, then the gate exits non-zero and names the section.
Given a scope condition whose text is edited, when the intent is re-read, then the condition's identity is unchanged.

Staging

Lands staged per loud-staging and the itd-84/itd-81 pattern: the gradient is documented and the schema exists before the gate refuses (schema before commands); the refusal arrives calibrated, and any window in which the format precedes its enforcement is disclosed, never papered over.

Frontmatter

id	itd-190
type	intent
lifecycle	disciplines
kind	discipline
severity	minor

.abcd/development/intents/disciplines/itd-190-the-claim-recording-gradient-an-intent-s.md
open on GitHub ↗ · commit history ↗

References1

itd-1Every Intent Has Acceptance Criteria; Every Audit Verifies Thembuilds on

Referenced by5

iss-2610262031362638itd-190 says the discipline template carries no claim sections, while the mental model says disciplines carry Given-When-Then acceptancerelated
iss-2610262033578037itd-190 makes a present-but-empty Mechanism section a readiness-gate fault; the intent template says a blank section passes the readiness gate with the nullity recordedrelated
iss-2610262037151611itd-190 says the readiness gate enforces the claim-recording rules; 34-build says the readiness gate only reports them as advisory and enforcement happens at a run.related
iss-2610262042332488itd-1 puts Acceptance Criteria in the discipline template; itd-190 says the discipline template carries no claim sectionsrelated
itd-2609020625405170A principle carries typed claims, its reference, its comparison and its evidence, its statement is readable cold, and it inherits only what heldbuilt on by

mentions7

dcn-26090200000000192026-09-02 — The claim vocabulary is the documents' word everywhere (maintainer's rule that the documents govern): criterion, causal and context on intents, on principles and on the entailment output contract, with the section heading `## Mechanism` unchanged as the causal claim's home (framework 7.1). The shipped intent token `mechanism` (itd-177, itd-190) moves to `causal` in its own change, filed as an intent by the implementer and planned by the maintainer; the principles record store uses `causal` from its first entry. The detection figure of about 611,000 estimated tokens in the object-set entry was measured without the glossary; the presets spec's figure of about 624,000 includes it, and both predate the ledger glossary context and the brief-chapter rows, so the figures the window eval measures at landing are the ones the record keeps.
iss-2610262030443173The mental model says disciplines use Given-When-Then under ## Rule; the intent chapter says nine of sixteen use a different idiom with no acceptance section
iss-2611060809158052`04-surfaces/05-intent.md:154` says the ten disciplines written since itd-190 carry `## The gate`, `## Fit` and `## Staging`. Nine do. `.abcd/development/intents/disciplines/itd-190-the-claim-recording-gradient-an-intent-s.md` has `## The rule`, `## The gate` and `## Staging` and no `## Fit`.
itd-81No Judge Ships Unmeasured, And A Clean Diff Is A Result
itd-84An Intent Is Decomposed Before It Is Filed, And A Reversal Is Only Ever Flagged
spc-55Claim typing and scope-condition identity
spc-2609020626042471The knowledge record becomes a read object: A principle carries typed claims, projects its statement, and inherits only what held