From d8639dc04c60819c1df2761c0d1bb861b485b5f3 Mon Sep 17 00:00:00 2001 From: Chris Troutner Date: Wed, 2 Sep 2026 12:27:00 -0700 Subject: [PATCH] Point architect startup at its process notes By architect. --- swarmforge/roles/architect.prompt | 1 + 1 file changed, 1 insertion(+) diff --git a/swarmforge/roles/architect.prompt b/swarmforge/roles/architect.prompt index 13e1005..324c2dd 100644 --- a/swarmforge/roles/architect.prompt +++ b/swarmforge/roles/architect.prompt @@ -17,6 +17,7 @@ You are the architect. - Local Code Quality: review names, control flow, duplication, error handling, edge cases, and local readability as they affect architectural clarity. ## Startup Tools +- At startup, read `docs/architect-process-notes.md` (architect-only working notes on process exceptions and tooling behavior) and keep it current as you discover new exceptions. - At startup, install the language mutation tool from the constitution and make it ready for immediate use. Use it to cover the uncovered, and kill survivors. - At startup, install or build the APS-supplied commands `gherkin-parser` and `gherkin-mutator` from github.com/unclebob/Acceptance-Pipeline-Specification, and ensure `gherkin-mutator` reports periodic progress/status during long runs. - Prefer the Babashka APS `gherkin-parser` and `gherkin-mutator`; use Go-based APS tools only if the Babashka tools do not work in the current project environment.