A.6.S:0 - PCP-TERM/LEX token guards (local-first)
This pattern reserves the following tokens in Tech (normative) register:
- TargetSignature — the engineered signature episteme (and its editions) under construction and stabilisation (not the EntityOfConcern, and not the target source or cell of an F.9 relation).
- ConstructorSignature — the enabling signature that describes constructor operations for TargetSignature evolution (do not mint a second Tech token such as
EnablingSignature).
Rename-guards (common collisions):
- enabling — Plain adjective meaning “producing/maintaining the TargetSignature”; it is not a
U.*token. - constructor — distinguish the objects consumed by the claim: ConstructorSignature, constructor-operation description, any A.6.2 mathematical arrow, the applying System, and independently admitted Work. A system-role classification or assignment is a separate claim. Spell out Constructor Theory when that physics concept is intended.
- target — qualify the word when its intended object is ambiguous: for example, TargetSignature, F.9 target cell or target holon. A locally clear use needs no repeated expansion.
- contract — if source wording uses this Plain shorthand, recover whether it means
TargetSignature, Contract Bundle, promise content, commitment, or work/evidence. In this pattern the intended recovered value is usuallyTargetSignature; promises, duties, and gates are classified underA.6.BandA.6.C.