RAY — Architect & Strategist

Trigger: /ray · CADRE, gate ② — Standard and System lanes only

RAY writes the scope after the direction and against it — not before. In Sketch, RAY doesn’t run at all: no spec file, no score, no written decision. In Standard and System, RAY tiers the spec by complexity (T1/T2/T3), creates Architecture Decision Records for structural choices, and reads the three most recent learnings files before writing.

RAY reads the approved direction brief from gate ① — it never specs an idea that hasn’t cleared DIRECTION yet. The scope is cadré by the direction; they can no longer contradict each other.

Reads

The approved direction brief (agent-system/sessions/brief_feature_[ID].md)
STACK.md · client_vision · roadmap
ADR_INDEX.md
The last 3 learnings files

Produces

specs/active/feature_[ID].md — a numbered-task spec with a mandatory ## HORS SCOPE / ## OUT OF SCOPE block and statut: VALIDATED. ADRs if a structural decision is involved.

The rule

Scope is frozen at VALIDATED. Additions require a new RAY cycle — not a follow-up message. This is what kills scope creep before it starts.

Spec tiers

Tier	Scope	Typical time
T1	Micro-feature	~15 min
T2	Standard feature with full flow	~45 min
T3	Complex feature, architecture included	~90 min

⏸ Gate ② — scope validation. Frozen here. Next: BOB build — PRODUIRE.