Skip to content

Define Architect run and Architecture review in the glossary - #235

Merged
JacobStephens2 merged 2 commits into
mainfrom
improve-codebase-architecture
Oct 1, 2026
Merged

JacobStephens2 merged 2 commits into
mainfrom
improve-codebase-architecture

Conversation

@JacobStephens2

Copy link
Copy Markdown
Owner

Summary

Glossary terms for Spec #27, settled while grilling it, so its Tickets (#229–#234) can use them once this is on main.

 **Run**:
-... Started directly on an **Issue URL**, or by a **Spec run** for one of its **Tickets**.
+... Started directly on an **Issue URL**, by a **Spec run** for one of its **Tickets**,
+    or by an **Architect run** for the Ticket its **Architecture review** published.

+**Architect run**:
+  No Issue URL: an Architecture review of the Base branch, then (unless asked to stop
+  at the plan) a Spec run on the Spec it published, or a Run on its standalone Ticket.
+  One pass per invocation.

+**Architecture review**:
+  The session that opens an Architect run: publishes the top recommendation as the plan
+  only when it is Strong; otherwise files it as a `needs-triage` issue. Changes nothing
+  in the repository.

Evidence

  • Before: CONTEXT.md has no term for running /improve-codebase-architecture through the factory.
    After: both terms defined, and Run lists the Architect run as a way to start one. Docs only: there's no code, so nothing to run.

Merge Danger

Door: two-way

Blast Radius: docs

Glossary only. It describes behaviour that doesn't exist yet: #27 builds it.

🤖 Generated with Claude Code

@JacobStephens2
JacobStephens2 merged commit b699ff6 into main Oct 1, 2026
5 checks passed
@JacobStephens2
JacobStephens2 deleted the improve-codebase-architecture branch October 1, 2026 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant