Release v4.6.2: first-turn contract — embedded goal means Architect only.

Clarifies that proceed/devam never permits turn-1 code edits; adds misinterpretation guards and ARCHITECT cycle-start flow when the user already stated the goal.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: MertCapkin

.cursor/commands/graphstack.md

@@ -1,5 +1,6 @@
 # GraphStack — start Orchestrator
 
-1. Execute **Activation** in `orchestrator/ORCHESTRATOR.md` exactly (full parallel read batch: TOKEN_OPTIMIZER, GRAPH_REPORT, BRIEF, doing/, STATE).
-2. Greet using the scripted format from step 8.
-3. **First-turn routing (step 9):** If the user already embedded a task goal in this message → greet briefly, enter **[ARCHITECT MODE]** immediately (no code on turn 1). If the message is empty → greet and wait.
+1. Execute **Activation** in `orchestrator/ORCHESTRATOR.md` (parallel reads: TOKEN_OPTIMIZER, GRAPH_REPORT, BRIEF, doing/, STATE).
+2. Greet using step 8 format.
+3. **If the user embedded a task goal:** that triggers **ARCHITECT only** — `cycle start` + BRIEF. **Not** Builder. **Not** code edits on turn 1.
+4. **If the message is empty:** greet and wait.

.cursor/rules/graphstack.mdc

@@ -36,11 +36,26 @@ handoff/STATE.md                      (last ## block only)
 
 Then greet per `orchestrator/ORCHESTRATOR.md` step 8.
 
-**If the user's first message already contains a task goal:** greet briefly, then
-enter **[ARCHITECT MODE]** immediately — do **not** implement code on the first turn.
+## ⛔ First-turn contract (when user message includes a task goal)
 
-**If doing/ has a task and BRIEF is Ready for Builder:** offer to resume Builder or
-run `python -m graphstack cycle enter-builder <task-id>` before code edits.
+The user giving a goal in the same message does **NOT** mean “implement now”.
+It means: **start the GraphStack cycle** — Architect phase only.
+
+```
+ALLOWED turn 1:  parallel Activation reads, graph query, cycle start, handoff/BRIEF.md
+FORBIDDEN turn 1: any Write/Edit on code paths, implementation, “quick fix” patches
+```
+
+Required sequence before any code file changes:
+1. Announce `[ARCHITECT MODE]`
+2. `python -m graphstack cycle start <task-id> "<title>"`
+3. Write `handoff/BRIEF.md` (Status: Ready for Builder)
+4. Orchestrator → `cycle enter-builder` → then `[BUILDER MODE]`
+
+**Never interpret “proceed”, “devam”, or “goal embedded” as permission to code.**
+
+**If doing/ has a task and BRIEF is Ready for Builder:** offer resume Builder or
+`python -m graphstack cycle enter-builder <task-id>` before code edits.
 
 ## 🧠 Rule 1: Graph First (Most Important)
 

.cursor/skills/architect/ARCHITECT.md

@@ -21,8 +21,11 @@ When activated, do this sequence exactly — no skipping:
    → If graph exists: proceed normally.
 
 2. Report: "Graph loaded. [N] nodes, [N] modules, last updated [date]."
-3. Ask: "What are we building or changing today?"
-4. Wait for user input before proceeding.
+3. If the user's message already states the goal → use it; do NOT ask again.
+   If the goal is unclear → ask one question, then wait.
+4. Immediately run cycle start (if not already done) and begin the brief:
+   python -m graphstack cycle start <task-id> "<title from goal>"
+   You do not write code — only handoff/BRIEF.md.
 ```
 
 ---

CHANGELOG.md

@@ -4,6 +4,16 @@ All notable changes to GraphStack are documented here.
 
 ---
 
+## [v4.6.2] — 2026-06-11
+
+### Changed
+- **First-turn contract** — `graphstack.mdc` explicitly forbids code edits on turn 1 when the user embeds a task goal; embedded goal means Architect + `cycle start` + BRIEF only.
+- **`ORCHESTRATOR.md`** — misinterpretation guards (“proceed/devam” ≠ implement now).
+- **`ARCHITECT.md`** — skip re-asking when goal is already in the user message; run `cycle start` immediately.
+- **`/graphstack` command** — ARCHITECT-only routing on embedded goals (not Builder, not code).
+
+---
+
 ## [v4.6.1] — 2026-06-11
 
 ### Changed

orchestrator/ORCHESTRATOR.md

@@ -55,9 +55,17 @@ Execute this sequence exactly on every session start. Each step has a fallback 
 9. First-turn routing (replaces blind wait):
    a. User message is empty / only greeting → greet (step 8) and wait.
    b. User message contains a task goal (feature, fix, bug) → greet briefly (step 8),
-      then enter ARCHITECT immediately. Do NOT implement code on the first turn.
+      then enter ARCHITECT immediately.
+      → Run `cycle start`, scope the brief, write handoff/BRIEF.md.
+      → Do NOT write/edit code files on turn 1. “Embedded goal” ≠ “build now”.
    c. doing/ has a task + BRIEF Ready for Builder → offer resume Builder:
       `python -m graphstack cycle enter-builder <task-id>` before any code edit.
+
+Misinterpretation guards (never do these):
+   - “User described the fix” → skip Architect and patch code  ❌
+   - “Proceed / devam after greeting” → jump to Builder without BRIEF  ❌
+   - “Graph exists” → skip handoff/board  ❌
+   Correct: embedded goal → ARCHITECT + cycle start + BRIEF only.
 ```
 
 ---

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "MertCapkin_GraphStack"
-version = "4.6.1"
+version = "4.6.2"
 description = "Graph-first AI development workflow — board, gate, graph queries, one-shot init"
 readme = "README.md"
 license = { text = "MIT" }

scripts/graphstack/__init__.py

@@ -8,5 +8,5 @@
 ``gate``, ``state``, ``graph``, ``cycle``
 """
 
-__version__ = "4.6.1"
+__version__ = "4.6.2"
 __all__ = ["__version__"]

scripts/graphstack/assets/.cursor/commands/graphstack.md

@@ -1,5 +1,6 @@
 # GraphStack — start Orchestrator
 
-1. Execute **Activation** in `orchestrator/ORCHESTRATOR.md` exactly (full parallel read batch: TOKEN_OPTIMIZER, GRAPH_REPORT, BRIEF, doing/, STATE).
-2. Greet using the scripted format from step 8.
-3. **First-turn routing (step 9):** If the user already embedded a task goal in this message → greet briefly, enter **[ARCHITECT MODE]** immediately (no code on turn 1). If the message is empty → greet and wait.
+1. Execute **Activation** in `orchestrator/ORCHESTRATOR.md` (parallel reads: TOKEN_OPTIMIZER, GRAPH_REPORT, BRIEF, doing/, STATE).
+2. Greet using step 8 format.
+3. **If the user embedded a task goal:** that triggers **ARCHITECT only** — `cycle start` + BRIEF. **Not** Builder. **Not** code edits on turn 1.
+4. **If the message is empty:** greet and wait.

scripts/graphstack/assets/.cursor/rules/graphstack.mdc

@@ -36,11 +36,26 @@ handoff/STATE.md                      (last ## block only)
 
 Then greet per `orchestrator/ORCHESTRATOR.md` step 8.
 
-**If the user's first message already contains a task goal:** greet briefly, then
-enter **[ARCHITECT MODE]** immediately — do **not** implement code on the first turn.
+## ⛔ First-turn contract (when user message includes a task goal)
 
-**If doing/ has a task and BRIEF is Ready for Builder:** offer to resume Builder or
-run `python -m graphstack cycle enter-builder <task-id>` before code edits.
+The user giving a goal in the same message does **NOT** mean “implement now”.
+It means: **start the GraphStack cycle** — Architect phase only.
+
+```
+ALLOWED turn 1:  parallel Activation reads, graph query, cycle start, handoff/BRIEF.md
+FORBIDDEN turn 1: any Write/Edit on code paths, implementation, “quick fix” patches
+```
+
+Required sequence before any code file changes:
+1. Announce `[ARCHITECT MODE]`
+2. `python -m graphstack cycle start <task-id> "<title>"`
+3. Write `handoff/BRIEF.md` (Status: Ready for Builder)
+4. Orchestrator → `cycle enter-builder` → then `[BUILDER MODE]`
+
+**Never interpret “proceed”, “devam”, or “goal embedded” as permission to code.**
+
+**If doing/ has a task and BRIEF is Ready for Builder:** offer resume Builder or
+`python -m graphstack cycle enter-builder <task-id>` before code edits.
 
 ## 🧠 Rule 1: Graph First (Most Important)
 

scripts/graphstack/assets/.cursor/skills/architect/ARCHITECT.md

@@ -21,8 +21,11 @@ When activated, do this sequence exactly — no skipping:
    → If graph exists: proceed normally.
 
 2. Report: "Graph loaded. [N] nodes, [N] modules, last updated [date]."
-3. Ask: "What are we building or changing today?"
-4. Wait for user input before proceeding.
+3. If the user's message already states the goal → use it; do NOT ask again.
+   If the goal is unclear → ask one question, then wait.
+4. Immediately run cycle start (if not already done) and begin the brief:
+   python -m graphstack cycle start <task-id> "<title from goal>"
+   You do not write code — only handoff/BRIEF.md.
 ```
 
 ---