Repository navigation
docs(spec): G3 acceptance scenarios for engineering-stage-enforcement (#238) - #242
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
🟡 Changes recommended
The scenarios lack explicit assertions for required classifications, provider blocking, and passing adequacy checks, while the publication reference leaves conflicting source digests unreconciled.
4 open issues
What changed in this PR
Adds draft acceptance scenarios for engineering-stage enforcement, supporting issue #238’s staged, spec-first BDD rollout. This documentation-only PR does not authorize tests, implementation, or deployment.
Changes:
- Adds Gherkin examples for ESE-1 through ESE-14, including V1–V6 controls.
- Adds a requirement coverage matrix.
- Records draft provenance and the separate G3 approval boundary.
| File | Description |
|---|---|
specs/engineering-stage-enforcement/scenarios.md |
Adds acceptance scenarios, coverage mapping, and owner-review boundaries for G0–G6 enforcement. |
Review effort: Balanced
| > Canonical inputs: issue #238 and the merged ESE `requirements.md`, | ||
| > `design.md`, and `tasks.md` at repository revision | ||
| > `9b189908bbb08540d066a53c1841a883d6beb5ac`. |
| Given the inventory includes private, empty, archived, learner, external, and forked repositories | ||
| When coverage is classified with owner review | ||
| Then every repository is recorded as "GOVERNED", "QUARANTINED", "NOT_APPLICABLE_BY_AUTHORIZED_SCOPE", or "BLOCKED_UNAVAILABLE" | ||
| And an unowned repository's own controls are never overridden |
| Scenario: Platform limitations are reported honestly | ||
| Given a provider cannot meet the isolation bar or an unmanaged host is outside technical enforcement | ||
| When coverage is reported | ||
| Then that lane is "BLOCKED" or "OUTSIDE ENFORCED BOUNDARY / NOT PROVEN" | ||
| And unprotected-branch code remains untrusted and unmergeable |
| Given one existing scoped synthetic feature has authenticated receipts from G0 through G3 | ||
| And its fixture, policy version, actor, inputs, preconditions, and observations are recorded | ||
| When genuine RED is accepted at G4 | ||
| And bounded GREEN plus preserved and contrast evidence is accepted at G5 |
Adds specs/engineering-stage-enforcement/scenarios.md: acceptance scenarios mapping to every requirement ID ESE-1 through ESE-14, including the V1-V6 control scenarios from the design.
Provenance: MARKED AI DRAFT prepared by Codex. Content unchanged from issue #238 comment 6558973960 (SHA-256 68ac0c767cf202a367f2c8caf425912951be3199869f2af23c591d4af6975333). Published via owner override at Ky's direction. Publication is not evidence of personal review or approval.
Scope: G3 acceptance scenarios only. This PR authorizes no tests, step definitions, implementation, or deployment. Owner merges personally.