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 — MUST distinguish ConstructorSignature (episteme), a constructor-operation description, the A.6.2 arrow used to state its effect-free episteme relation, and the admitted System that applies the described constructor operation and performs any separately admitted construction Work. State any local system-role classification and obtaining assignment separately. If the physics term is intended, spell Constructor Theory explicitly.
• target — avoid bare “target” in Tech clauses; use TargetSignature or qualify the target (for example, “F.9 target cell” or “target holon”).
• 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 usually TargetSignature; promises, duties, and gates are classified under A.6.B and A.6.C.