FR-083: Global IPW-gated implementation contract
Type: Feature Request (FR)
ID: FR-083
Submitted: 2026-04-20
Submitted By: User feedback / governance hardening
Priority: HIGH
Severity: HIGH
Status: OPEN
Implementing Task: E6:S06:T62
Summary
Establish a hard repository-wide execution contract that blocks all implementation work behind a complete IPW package plus explicit user authorization, preventing intent override during intake and planning requests.
Problem Statement
Current behavior can drift from requested artifact scope (for example, a request to file a UXR/FR/BR triggers direct implementation). This violates user control, bypasses planning stages, and weakens governance traceability.
Requirements
Functional Requirements
- FR-083-F1: Define and enforce a global "no implementation before IPW" gate in governing agent rules.
- FR-083-F2: Require all implementation to satisfy three preconditions: task anchor (
E#:S#:T#), linked IPW package (specification,test-design,implementation-plan), and explicit user execution authorization in a separate instruction. - FR-083-F3: Require planning/intake requests (UXR/FR/BR/task/spec/plan/review) to remain planning-only and stop on completion.
- FR-083-F4: Require missing-precondition handling to request only missing prerequisites, without inferred permission or opportunistic implementation.
Non-Functional Requirements
- FR-083-NF1: Policy language is unambiguous and applies repository-wide (not limited to one workflow).
- FR-083-NF2: Rule placement is durable across sessions by updating both
AGENTS.mdand.cursorrules.
Acceptance Criteria
- Contract is present in both primary rule sources and states all gate preconditions explicitly.
- Contract explicitly blocks implementation while gate is closed and requires stop-and-wait after planning artifact completion.
- FR and task are bidirectionally linked and listed in active story/board tracking surfaces.
Scope Analysis
Problem Domain: Governance, workflow safety, agent execution contract
Affected Areas:
-
AGENTS.md -
.cursorrules - Kanban intake/task/board wiring docs
- Runtime workflow scripts (not required for initial policy filing)
Estimated Complexity:
- Simple (1-3 days)
- Medium (1 week)
- Complex (2+ weeks)
- Very Complex (1+ month)