feat(gates): T-036 phases 4-6 — effective-required, derived GateMode,…#73
Merged
Merged
Conversation
… Core-source seam Completes the artifact-driven gate parametrization plan (ADR T-036 §6). Phase 4 — Effective-required model (§2/§3): required evidence is the projection of the phase's Core artifacts with effectiveRequired = coreRequired OR tenantRequired. Core-required artifacts are locked; the tenant may raise a Core-optional one. Save persists the full effective set, falling back to raw tenant overrides when the Core profile is empty. Phase 5 — Derived GateMode (§2.1): the SIMPLE/COMPLEX toggle is removed. Mode is now computed from the effective policy (required evidence, a blocking criterion, a multi-approver or multi-stage chain, or a required Core verdict → COMPLEX) and shown read-only; the derived value is sent in the Core payload. Phase 6 — Core-source contract (§5, GAP-004): introduce IPhaseArtifactProfileSource as the seam for where the phase-artifact catalog comes from. Today the only implementation is the provisional StandInPhaseArtifactProfileSource (stamped `core-standin`); swap the single DI registration for a Core-sync source once Core publishes the catalog. Provenance is surfaced on the DTO and flagged in the editor. Verified: tsc + eslint clean; dotnet build 0/0; 496/496 tests pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
… Core-source seam
Completes the artifact-driven gate parametrization plan (ADR T-036 §6).
Phase 4 — Effective-required model (§2/§3): required evidence is the projection of the phase's Core artifacts with effectiveRequired = coreRequired OR tenantRequired. Core-required artifacts are locked; the tenant may raise a Core-optional one. Save persists the full effective set, falling back to raw tenant overrides when the Core profile is empty.
Phase 5 — Derived GateMode (§2.1): the SIMPLE/COMPLEX toggle is removed. Mode is now computed from the effective policy (required evidence, a blocking criterion, a multi-approver or multi-stage chain, or a required Core verdict → COMPLEX) and shown read-only; the derived value is sent in the Core payload.
Phase 6 — Core-source contract (§5, GAP-004): introduce IPhaseArtifactProfileSource as the seam for where the phase-artifact catalog comes from. Today the only implementation is the provisional StandInPhaseArtifactProfileSource (stamped
core-standin); swap the single DI registration for a Core-sync source once Core publishes the catalog. Provenance is surfaced on the DTO and flagged in the editor.Verified: tsc + eslint clean; dotnet build 0/0; 496/496 tests pass.