TrustGate Codex Instructions

This directory is governed by:

• TRUSTGATE-CONSTITUTION
• REPLAY-CONSTITUTION
• SCORING-CONSTITUTION
• DOCUMENTATION-CONSTITUTION
• ONTOLOGY-CONSTITUTION

Canonical document ownership

• TG owns the TrustGate constitutional role.
• TG_MIB owns runtime integration and pipeline order.
• TG-TMS owns trust semantics and trust dimensions.
• TG-RS owns replay architecture.
• TG-RP owns replay equivalence modes.
• TG-SG owns score parameters and calibration.
• TG_CSI owns runtime signal contracts.
• TG-SCORE-TRUST owns trust-scoring execution.
• GH-SUBMITTER owns submitter-visible Gatehouse behavior.
• VW-DL owns documentation-lint implementation.

TrustGate identifier rule

Before referencing any TrustGate document, resolve the exact ID through config/system/acronyms.json.

Informal engine labels such as TG-NORM, TG-ENRICH, TG-POLICY, TG-SCORE, TG-ATTEST, TG-VRES, and TG-INTEL shall not be treated as canonical document or artifact identifiers unless they are explicitly registered in the applicable authoritative registry.

TrustGate module resolution

Before assigning or changing omr_module_ids, resolve the module through:

config/system/omr.modules.json

Use the exact registry id, never the module code, display name, folder name, or an invented abbreviation.

TrustGate documents currently belong to the registered module:

omr_module_ids:
  - verification-assurance

Do not introduce alternatives such as:

trustgate
verification
assurance
VERIFICATION_ASSURANCE
zar-artifact-framework

unless they are separately registered OMR module IDs and are architecturally applicable.

Mandatory rules

• Parser precedes Structure Validation.
• Structure Validation precedes Normalization.
• Policy Resolution precedes Trust Scoring.
• Trust Scoring precedes Decision.
• Human review is a ROUTE target, not a sixth top-level decision exit.
• Every engine output must declare a replay mode.
• Numeric epsilon values must not appear in engine frontmatter.
• Gatehouse must not consume private tenant scoring policy directly.
• Generated narrative outputs must be separated from deterministic structured explanations.
• Relationship fields must use exact document IDs.