Withdrawn Gate Implementations
The former StellaOps.Policy.Gates trust-lattice implementations were withdrawn by PCD-382 on 2026-10-05. No production host registered these classes. Their tests and source are frozen under mirrored paths in src/__Obsoleted/Policy/. TrustLatticeEngine and the unused IVexDecisionEmitter implementation are also frozen.
Current boundaries
- Promotion uses the Engine’s registered evaluation path and its tenant gate projection. See Policy architecture and the promotion ownership contract.
- VEX consensus uses issuer tiers and tenant overlays, not PCR vectors or the withdrawn trust-lattice gates. See consensus operations.
- The on-demand interop assessment API has seven separately implemented algorithms:
CvssThresholdGate,SignatureRequiredGate,EvidenceFreshnessGate,SbomPresenceGate,MinimumConfidenceGate,UnknownsBudgetGateandReachabilityRequirementGate. Their identifiers do not instantiate the withdrawn classes. Import and validation emitGATE_INTEROP_ONLYinformation explaining that promotion does not enforce these controls. They assess the caller’s supplied evidence fields; they are not independent evidence verification. - Other identifiers are refused with
GATE_TYPE_UNSUPPORTED, including a disabled gate in a pack. Evaluation returnsblockrather than silently allowing an unsupported gate. The Console builder identifies unavailable types and explains the interop-only boundary.
The generic gate context remains available for its existing callers. Its SubgraphSlice DTO was retained independently from the withdrawn reachability gate. Existing VEX signing/attestation models remain; only the emitter’s request/result contracts were removed.
History
- Gate implementations:
src/__Obsoleted/Policy/__Libraries/StellaOps.Policy/Gates/ - Trust engine:
src/__Obsoleted/Policy/__Libraries/StellaOps.Policy/TrustLattice/ - Decision emitter:
src/__Obsoleted/Policy/StellaOps.Policy.Engine/Vex/
These paths are historical source, not build inputs or extension points.