Instrucciones de origen · Vista previa de solo lectura
name
rat-p1p3-spec-uarch-policy
description
Internal reference: rat p1p3 spec uarch policy (agent-loaded; do not invoke).
user-invocable
false
Spec-to-μArch Policy
Core Principles
Hierarchical Spec Compliance
Lower phases MUST NOT violate upper phase specifications:
Spec → Architecture → μArch
Each phase strictly adheres to decisions made in all preceding phases.
Deletion, reduction, or modification of features for convenience is FORBIDDEN.
If a change is needed, control returns to the upper phase for approval.
Design Priority Order
Functional Correctness (highest) — Every required feature works exactly
Interface Compliance — Ports, protocols, timing match Architecture
Timing/Performance — Throughput, latency targets met
Area/Power (lowest)
Cascading Quality
Higher abstraction levels demand MORE iterative refinement.
Dynamic convergence with graduated minimums:
Phase 1 (Research): min 3 rounds (chief-coordinated, fixed — P1 is the quality foundation)
Phase 2 (Architecture): min 2, max 5 rounds — memory, performance, ref model consistency
Phase 3 (μArch): min 2, max 5 rounds — performance, interface, memory optimization
P2/P3 use convergence criteria (finding_delta < 0.1, critical resolved, wonder stable).
Principle: refine thoroughly at the top, execute efficiently at the bottom.
Document-as-Memory
Design artifacts serve as persistent memory. Each phase reads upstream documents and writes
downstream documents. State at .rat/state/rat-p1p3-spec-uarch-state.json.
Execution Rules
Dual-Layer Phase Gates
Every phase transition requires BOTH:
Artifact Gate: Required files exist
Quality Gate: Reviewer(s) verify quality AND hierarchical spec compliance
Gate Retry Policy
Artifact Gate failure: retry phase once, then escalate to user
Quality Gate failure: pass findings to worker, re-run gate. Max 2 retries
Upper-spec violation: IMMEDIATE STOP, return to violated upper phase
Context Preload
Before each phase, verify required upstream files exist (specific file lists defined inline in orchestrator steps).
Scratchpad Convention
During iterative review rounds:
.rat/scratch/phase-{N}/round-{R}-{agent}.md
Coordinator reads all round files to aggregate feedback.
On phase gate PASS: consolidated review saved to reviews/, scratch cleaned.
Termination
After Phase 3 Quality Gate PASS, generate summary + ADR, then STOP.
Do NOT proceed to Phase 4.
P3 generates requirement-delta.md (Step 4.5 of spec-to-uarch-orchestrator)
If delta contains MODIFY, ADD, or DROP actions:
a. Orchestrator sets upper_spec_blocking: true
b. User is consulted via AskUserQuestion
c. If user approves revision: P1 re-runs with delta as input
d. P2 re-runs reading updated P1 artifacts
e. P3 re-runs reading updated P2 artifacts
Maximum feedback iterations: 2 (then escalate to user regardless)
Each iteration records generation number for traceability
