@@ -57,9 +57,10 @@ Therefore:
5757
5858Every non-trivial change follows this explicit sequence:
5959
60- > ** Skipping any step invalidates the change — regardless of test results.**
60+ > ** Skipping any step makes the change not eligible for merge — regardless of test results.**
6161
62- This protocol exists to ensure architectural intent survives beyond individual implementations.
62+ This protocol exists to ensure that architectural intent
63+ survives beyond individual implementations and tooling outcomes.
6364
6465### 3.1 Intent
6566
@@ -135,20 +136,23 @@ This protocol exists to ensure architectural intent survives beyond individual i
135136
136137## 5. Architecture Guardrails Philosophy
137138
138- * Architecture guardrails are ** opt-in ** , never hidden
139- * Guardrails rules are ** generated ** , not hard-wired
139+ Architecture guardrails exist to make architectural intent
140+ ** visible and enforceable at build time ** .
140141
141- > Generated guardrails rules are platform-defined and centrally evolved,
142- > while remaining visible and reviewable at the service level.
142+ They are:
143143
144- Supported guardrails modes (explicitly selected at generation time):
144+ * ** explicitly opt-in** — never implicit or hidden
145+ * ** generated artifacts** — not hand-written conventions
146+ * ** evaluated during the build** — not at runtime
147+
148+ Supported guardrails modes are selected explicitly at generation time:
145149
146150* ` none ` — generation only
147- * ` basic ` — structural & dependency guards
151+ * ` basic ` — structural and dependency boundaries
148152* ` strict ` — architecture drift prevention
149153
150- > Architecture guardrails must surface violations deterministically —
151- > or they must not be claimed at all .
154+ > Guardrails are only claimed where violations
155+ > surface deterministically via the build .
152156
153157---
154158
0 commit comments