README: Superpowers → Why Turnstone, vertical mermaid

- Replaced Relationship to Superpowers with Why Turnstone section
  highlighting Turnstone's governance surface as the engine's native
  enforcement layer.
- Mermaid diagrams: changed from LR (horizontal) to TB (vertical)
  in both README and architecture.md for readability.
- Superpowers retained in credits as prior art with a shorter,
  more precise acknowledgment.

Author: RedEyeNinja-BKK

README.md

@@ -11,7 +11,7 @@ Process Engine is a persona-and-skills generator for Turnstone: tell it what you
 Tell it what you want to build, share any material you already have, and it produces a complete Turnstone-native package — project, persona, skills, templates — through a gated pipeline:
 
 ```mermaid
-flowchart LR
+flowchart TB
     A[Intent] --> B[Orient]
     B --> C[Collect]
     C --> D[Clarify]
@@ -43,11 +43,18 @@ Every gate requires operator sign-off. Turnstone's native prompt policy and advi
 
 Process Engine is domain-neutral in package structure, artifact-specific, and runtime-aware. It's been exercised on Etsy store management, supplement product listings, incident response, employee onboarding, database backup operations, and financial planning advisories — not just software engineering.
 
-## Relationship to Superpowers
+## Why Turnstone
 
-[Superpowers](https://github.com/obra/superpowers) gives coding agents a mature, ready-to-use software-development methodology — plan, test, review, complete. Process Engine operates one level higher: it is **a system for designing, testing, and maintaining custom agent operating packages**, of which a software-development methodology is one possible output.
+Process Engine runs on Turnstone because Turnstone's governance surface is what the engine produces. Every generated package includes governance objects — prompt policy and advisory judge rules — that Turnstone enforces mechanically. The engine's "operator is the gate" philosophy maps directly to Turnstone's native approval surfaces.
 
-Superpowers is a finished methodology; Process Engine is a methodology factory. The two are complementary: Superpowers disciplines the code; Process Engine disciplines the package that disciplines the code.
+| Harness | Governance layer |
+|---|---|
+| **Turnstone** | Full — projects, personas, roles, policies, prompts, judge, audit |
+| Hermes | Agent runtime — no governance objects |
+| OpenClaw | Agent + channels — emission-focused |
+| Claude | Commercial harness — no governance layer |
+
+You don't need Turnstone to use Process Engine, but you need Turnstone for the governance wiring. The engine's prompt policy and advisory judge rules are Turnstone-native artifacts that enforce the gates mechanically — the model generates packages; Turnstone owns the guardrails.
 
 ## The engine's components
 
@@ -127,5 +134,5 @@ MIT — see [LICENSE](LICENSE).
 
 - **Generation basis:** [addyosmani/agent-skills](https://github.com/addyosmani/agent-skills) (MIT) — engineering discipline catalog
 - **Format standard:** [agentskills/agentskills](https://github.com/agentskills/agentskills) (Apache-2.0 / CC-BY-4.0) — Agent Skills open format
-- **Prior art & inspiration:** [Superpowers](https://github.com/obra/superpowers) — a mature software-development methodology for coding agents
+- **Prior art & inspiration:** [Superpowers](https://github.com/obra/superpowers) — a mature software-development methodology that applies a related evidence-first philosophy to coding agents. Process Engine operates one level higher: creating and qualifying the agent packages that contain methodologies like that.
 - **Platform:** native [turnstone](https://github.com/turnstonelabs/turnstone) mechanisms (projects, personas, skills, prompt templates, judge)

docs/architecture.md

@@ -34,7 +34,7 @@ Process Engine (project)
 ## The pipeline
 
 ```mermaid
-flowchart LR
+flowchart TB
     A[Intent] --> B[Orient]
     B --> C[Collect]
     C --> D[Clarify]