Skip to content

docs(adr): T-036 §2.2 intake promotion gate vs artifact-driven phase gates#67

Merged
beyondnetPeru merged 1 commit into
developfrom
docs/t-036-intake-promotion-refinement
Jul 8, 2026
Merged

docs(adr): T-036 §2.2 intake promotion gate vs artifact-driven phase gates#67
beyondnetPeru merged 1 commit into
developfrom
docs/t-036-intake-promotion-refinement

Conversation

@beyondnetPeru

Copy link
Copy Markdown
Contributor

Refines T-036: intake = promotion gate (criteria on opportunity, no evidence); phase gates artifact-driven (Option 1). Criteria artifactType per phase; guard applies to phase gates only.

🤖 Generated with Claude Code

…ria), phase gates are artifact-driven

Refines T-036 per the tenant decision (Option 1 + intake clarification): opportunities/intake carry NO evidence or deliverable-artifact restrictions; the intake gate is the promotion gate (opportunity → initiative) whose only parametrization is tenant-defined criteria/rules over the opportunity record's fields. From initiative phases onward (discovery→release) gates are artifact-driven: evidence = the phase's Core deliverable artifacts, criteria evaluate those artifacts' fields. Criteria artifactType source is phase-dependent: intake→opportunity (guard does not apply), phase gates→the phase's Core artifacts (guard applies). Updated §2.2 + §3 point 5 (EN+ES).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@beyondnetPeru beyondnetPeru merged commit 89c15de into develop Jul 8, 2026
2 checks passed
@beyondnetPeru beyondnetPeru deleted the docs/t-036-intake-promotion-refinement branch July 8, 2026 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant