A.2.4:4.2 - Status-Use Relation Slots

A status-use relation is a relation around a bearer, status value, scope, window, source, and use.

SlotKind	ValueKind	Use
`StatusBearerSlot`	episteme, claim, method description, publication, system-role-assignment occurrence, work occurrence, clause, gate record, or another governed bearer admitted by the direct pattern	The value whose status is being asserted or read.
`StatusTargetSlot`	claim, method, episteme, publication, exact domain result or result episteme, clause, bearer, or another governed status target	Required when the status is not simply about the bearer itself; the direct status or result pattern defines it.
`StatusScopeSlot`	claim scope, admission scope, requirement scope, or use scope	Currentness-required when scope changes the status assertion.
`StatusValueSlot`	status value governed by `F.10` or a direct pattern	Required for a status assertion.
`StatusWindowSlot`	temporal validity window, freshness policy, or source/status window	Required for time-sensitive use; G.11 is the pattern for an edition-currentness result when currentness is being judged.
`StatusUseSlot`	gate, assurance, admission, source-currentness, work-plan readiness, or another exact receiving use	Identifies the intended use; its receiving work, direct relation, and result remain with their governors.
`StatusProvenanceConstraintSlot`	source order, authority source, publication, proof, verification, register, or provenance constraint	Currentness-required when provenance decides status use.

These names are repair vocabulary for status-use relations. Durable status families remain governed by F.10 or a direct status pattern.