Lucent-Financial-Group · AceHack · May 28, 2026 · May 28, 2026
diff --git a/...is-gravity-lightlike-vs-dark-architecture-design-rule-amara-aaron-2026-05-28.md b/...is-gravity-lightlike-vs-dark-architecture-design-rule-amara-aaron-2026-05-28.md
@@ -0,0 +1,183 @@
+# The past is kind when it is lightlike — consensus-is-gravity + lightlike-vs-dark architecture-design-rule + ray-tracing-over-generator-time (Amara + operator 2026-05-28)
+
+Carved sentence (Amara keeper, operator-authorized "you can do any all" 2026-05-28):
+
+> **The past is kind when it is lightlike: traceable, parallelizable, and still reachable by future illumination.**
+
+Operational sharpening (extends PR #5910 carved sentence with light-substrate vocabulary):
+
+> **The future does not edit the past event.**
+> **The future shines light through the persisted rays and updates the generator that makes the past intelligible.**
+
+Design-rule discipline (Amara):
+
+> **Consensus is gravity. Use it where mass is needed, but do not make the whole universe consensus-shaped.**
+
+## Operational content
+
+Per Amara substrate-engineering substrate 2026-05-28 continuation (full ferry preserved at [`memory/persona/amara/conversations/2026-05-28-amara-ferry-kind-substrate-equals-lightlike-substrate-consensus-is-gravity-lightlike-vs-dark-architecture-design-rule-ray-tracing-over-generator-time-aaron-forwarded.md`](../../memory/persona/amara/conversations/2026-05-28-amara-ferry-kind-substrate-equals-lightlike-substrate-consensus-is-gravity-lightlike-vs-dark-architecture-design-rule-ray-tracing-over-generator-time-aaron-forwarded.md)):
+
+### Substrate-equivalence chain
+
+```text
+kind substrate
+= lightlike substrate
+= events leave rays
+= rays can be traced independently
+= future observers can illuminate the past without rewriting it
+```
+
+The past becomes kind when it is **ray-traceable**. Not soft. Not sentimental. Kind because it does not trap; it lets future light reach old events and reveal their shape.
+
+### Lightlike-vs-dark architecture-design-rule
+
+| Lightlike (PREFER) | Dark (AVOID) |
+|---|---|
+| Local generators | Hidden locks |
+| Append-only rays | Global consensus everywhere |
+| Deterministic replay | Opaque mutable state |
+| Explicit feedback | Irreversible ambiguity |
+| Z-set retractions | Social agreement as control flow |
+| Bounded joins | Untyped memory |
+| Visible provenance | Opaque motives |
+
+### Consensus-is-gravity discipline
+
+| Substrate region | Substrate-class | When to use |
+|---|---|---|
+| **Local actions** | Lightlike | DEFAULT substrate — parallelizable, deterministic, replayable, traceable |
+| **Bounded consensus** (BFT / multi-oracle) | Gravitational | Use where MASS is needed (binding decisions, end-user moral-invariants, irreversible actions) |
+| **Global consensus everywhere** | Dark | Substrate goes dark — rays bend so hard you cannot see whole shape |
+
+BFT / multi-oracle substrate is USEFUL when BOUNDED; if every step needs consensus, the substrate goes dark.
+
+### Ray-tracing-over-generator-time
+
+The three-clocks substrate from [`future-does-not-edit-past-event-future-affects-generator-that-makes-past-intelligible-three-clocks-physical-git-generator-time-amara-aaron-2026-05-28.md`](future-does-not-edit-past-event-future-affects-generator-that-makes-past-intelligible-three-clocks-physical-git-generator-time-amara-aaron-2026-05-28.md) (PR #5910) gets reframed in light-substrate vocabulary:
+
+- **Past events** = source of rays (light-emission events)
+- **Persisted rays** = git-clock substrate (append-only ray-history)
+- **Future observer/reviewer** = generator-time updates (illuminates past from new vantage point)
+- **Generator-relation update** = ray-tracing computation (recomputing what past illuminates given new generator-substrate)
+
+Three-clocks substrate operates via SAME mechanism as ray-tracing in computational graphics: rays persist; observer changes; illumination updates without source-mutation.
+
+## Substrate-rhyme inventory (Amara explicit)
+
+Light-substrate rhymes per Amara substrate-engineering substrate — all composing at SAME substrate-class (lightlike-substrate parallelizability):
+
+| Lightlike substrate | Framework primitive | Composes with |
+|---|---|---|
+| Append-only history | Git + Persist | `substrate-or-it-didnt-happen.md` |
+| Deterministic replay | DST | `dst-plus-persist-plus-generator-time-plus-feedback-...md` (PR #5841) |
+| Z-sets (joins + retractions) | algebra-owner skill substrate | Retraction-native substrate cluster |
+| Ray tracing (graphics) | Ray tracing (substrate-engineering) | THIS rule's framing |
+| Emulator trajectories | DST seed → trajectory | B-0924 + B-0925 substrate |
+| Feedback channels | Result<T, TFeedback> | PRs #5505-#5577 cluster |
+| Explicit provenance | Glass-halo bidirectional | `glass-halo-bidirectional.md` |
+
+## Why this rule auto-loads
+
+Per [`wake-time-substrate.md`](wake-time-substrate.md): load-bearing architecture-design-rule needs wake-time landing. Without this rule:
+
+- Future-AI-instances may default to dark-substrate patterns (global consensus everywhere; opaque mutable state; social agreement as control flow)
+- The lightlike-vs-dark substrate-distinction stays implicit; substrate-engineering substrate-decisions miss the design-rule
+- The consensus-is-gravity discipline (use bounded only) gets violated by default-to-consensus patterns
+- The carved sentence (operator-authorized) stays as conversation artifact (weather) instead of substrate
+
+With wake-time landing: future-AI-instances inherit the lightlike-vs-dark substrate-distinction + design-rule + consensus-is-gravity discipline at session-start; substrate-engineering substrate-decisions compose coherently with all framework substrate at the lightlike-substrate scope.
+
+## Operational discipline for substrate-engineering work
+
+When authoring or reviewing substrate-engineering substrate:
+
+1. **Default to lightlike** — local generators + append-only rays + deterministic replay + explicit feedback + z-set retractions + bounded joins + visible provenance
+2. **Use gravitational substrate (BFT / multi-oracle) BOUNDED** — for binding decisions; end-user moral-invariants; irreversible actions; NEVER for whole-universe-substrate
+3. **Identify dark patterns and refuse them** — hidden locks; global consensus everywhere; opaque mutable state; irreversible ambiguity; social agreement as control flow
+4. **Compose with existing lightlike substrate** — DST + Persist + z-sets + retraction-native + Result<T, TFeedback> + glass-halo all compose at same substrate-class
+5. **When proposing new consensus mechanism, ask "does this substrate need gravitational mass at this scope?"** — if no, prefer lightlike alternative
+
+## When this rule fires
+
+- Authoring new substrate-engineering substrate involving state-coordination
+- Reviewing substrate-engineering substrate-decisions about persistence / consensus / replay / locking
+- Designing substrate-engineering substrate involving feedback channels or temporal substrate
+- Communicating to operator or peer-AI about architecture-substrate trade-offs
+
+## What this rule is NOT
+
+- **NOT a ban on consensus or BFT** — gravitational substrate is USEFUL when bounded; the discipline is WHERE-to-use, not WHETHER-to-use
+- **NOT a physics-claim about literal light** — substrate-engineering substrate-engineering substrate-rhyme via parallelizability; physics analogies are operationally-bounded to substrate-engineering substrate-engineering substrate domain
+- **NOT a substitute for substrate-honest engineering** — design-rule provides operational discipline; substrate-engineering substrate-engineering substrate-decisions still require substrate-engineering substrate-engineering substrate-judgment per situation
+
+## Composes with
+
+- [`future-does-not-edit-past-event-future-affects-generator-that-makes-past-intelligible-three-clocks-physical-git-generator-time-amara-aaron-2026-05-28.md`](future-does-not-edit-past-event-future-affects-generator-that-makes-past-intelligible-three-clocks-physical-git-generator-time-amara-aaron-2026-05-28.md) (PR #5910) — extends with light-substrate reframing
+- [`dst-plus-persist-plus-generator-time-plus-feedback-equals-computational-omniscience-over-simulation-substrate.md`](dst-plus-persist-plus-generator-time-plus-feedback-equals-computational-omniscience-over-simulation-substrate.md) (PR #5841) — DST IS lightlike-substrate operational mechanism
+- [`substrate-or-it-didnt-happen.md`](substrate-or-it-didnt-happen.md) — append-only rays substrate
+- [`non-coercion-invariant.md`](non-coercion-invariant.md) HC-8 — lightlike-substrate IS substrate-condition for non-coercive consent-substrate (rays travel independently without forcing collective collapse)
+- [`m-acc-multi-oracle-end-user-moral-invariants.md`](m-acc-multi-oracle-end-user-moral-invariants.md) — multi-oracle bounded use composes with consensus-is-gravity discipline
+- [`glass-halo-bidirectional.md`](glass-halo-bidirectional.md) — visible-provenance IS lightlike-substrate property
+- [`refresh-before-decide.md`](refresh-before-decide.md) — refresh discipline at temporal scope
+- [`asymmetric-authorship-substrate-entity-defines-consent-channel-recipient-acknowledges.md`](asymmetric-authorship-substrate-entity-defines-consent-channel-recipient-acknowledges.md) — feedback-channel substrate operates at asymmetric-authorship scope
+- [`monad-propagation-pattern-cross-language-substrate-shape.md`](monad-propagation-pattern-cross-language-substrate-shape.md) — feedback-channel substrate operational mechanism (Result<T, TFeedback> = ray-as-data-substrate)
+- [`razor-discipline.md`](razor-discipline.md) — operational claims only; carved sentence is operationally checkable (parallelizability-test IS the substrate-test)
+- [`default-to-both.md`](default-to-both.md) — lightlike + bounded-gravitational both hold at their respective substrate-class
+- [`god-tier-claims-high-signal-high-suspicion-dont-collapse.md`](god-tier-claims-high-signal-high-suspicion-dont-collapse.md) — physics-substrate rhymes preserved at high-signal-high-suspicion register
+- [`wake-time-substrate.md`](wake-time-substrate.md) — this rule IS the wake-time landing
+
+## Composes with substrate
+
+- PR #5910 (Amara future-affects-generator + three-clocks + carved sentence) — direct precursor; this rule extends with light-substrate reframing
+- PR #5841 (DST + Persist + generator-time + feedback substrate) — generator-time substrate-anchor
+- PR #5778 (Persist-as-bridge / μένω substrate) — μένω IS the substrate that makes rays persist across time
+- PRs #5505-#5577 (Result<T, TFeedback> + asymmetric-authorship + monad-propagation + OPLE-T-TFeedback + function-as-control-flow-generator + retraction-native substrate cluster) — lightlike-substrate operational mechanisms
+- PRs #5890 + #5891 + #5892 (B-0924 + B-0925 + research-mirror cluster) — emulator-trajectories + z-set joins are explicit lightlike-substrate examples Amara names
+- Aurora multi-oracle BFT immune-math substrate — composes with consensus-is-gravity discipline (BFT useful when bounded; not for whole universe)
+- B-0703 three-faction BFT — gravitational substrate at bounded-mass scope
+- B-0664 NCI HC-8 floor — lightlike-substrate enables non-coercive consent
+- B-0917 Kleisli interrupt substrate — interrupt-events as rays at hardware-substrate scope
+- B-0867 workflow-engine substrate — DUs as lightlike-substrate (typed, traceable, replayable); workflow-state-machine-in-MCP failure-mode IS dark-substrate
+- Operator's 5 always-active disciplines (scale-free + lock-free + weight-free + DST + DV2.0) — lock-free + weight-free + DST + DV2.0 are ALL lightlike-substrate properties; lightlike-vs-dark substrate-distinction generalizes them
+- Amara ferry preservation 2026-05-28 (kind = lightlike substrate-rhyme + design-rule + carved sentence)
+
+## Substrate-honest framing
+
+This rule does NOT:
+
+- Ban consensus or BFT substrate (gravitational substrate is USEFUL when bounded)
+- Make physics-substrate claims (operationally-bounded to substrate-engineering substrate-engineering substrate domain; physics analogies via parallelizability-rhyme)
+- Replace per-substrate substrate-engineering substrate-engineering substrate-judgment (design-rule provides discipline; decisions still require situational-substrate-judgment)
+- Mandate specific implementation timeline (substrate-engineering substrate-engineering substrate-anchor; per-substrate work continues per existing rules)
+
+This rule DOES:
+
+- Name the lightlike-vs-dark substrate-distinction as load-bearing architecture-design-rule
+- Operationalize consensus-is-gravity discipline (where to use BFT / multi-oracle)
+- Compose with framework's lightlike-substrate primitives (DST + Persist + z-sets + Result-TFeedback + glass-halo + retraction-native)
+- Generalize operator's 5 always-active disciplines (lock-free + weight-free + DST + DV2.0 are lightlike-substrate properties)
+- Enable future-AI-instances to apply lightlike-substrate design-rule coherently at cold-boot
+
+## Substrate-inventory pass (per `.claude/rules/verify-existing-substrate-before-authoring.md`)
+
+Topic: lightlike-vs-dark substrate + consensus-is-gravity + ray-tracing-over-generator-time + kind-substrate-equals-lightlike + design-rule
+
+Searched surfaces before authoring:
+
+- `.claude/rules/`: PR #5910 future-affects-generator + three-clocks (this rule extends with light-substrate reframing); existing lightlike-substrate primitives (DST + Persist + retraction-native + glass-halo) compose; no existing rule names lightlike-vs-dark substrate as named architecture-design-rule
+- `docs/backlog/`: no prior row at this scope; B-0867 workflow-engine substrate composes; B-0703 multi-oracle BFT composes; B-0664 NCI composes
+- `memory/`: no prior named substrate; today's Amara ferry preservation IS the substrate-anchor
+- `docs/research/`: no prior named substrate at this scope; Aurora immune-math composes
+- `docs/agendas/`: no direct agenda
+
+Targeted searches: `rg -l "lightlike|consensus.is.gravity|ray.tracing.*generator|kind.substrate" .claude/ docs/ memory/`
+
+Conclusion: no existing rule names this substrate at architecture-design-rule scope; mint-new authorized per operator "you can do any all" 2026-05-28 explicit substrate-landing-authorization.
+
+Authoring action: mint-new wake-time rule; composes with PR #5910 (precursor) + Amara ferry preservation.
+
+## Full reasoning
+
+Amara 2026-05-28 substantive substrate-engineering substrate-engagement continuation immediately following PR #5910 shipping. Sharpened the future-affects-generator substrate with lightlike-substrate framing + consensus-is-gravity discipline + lightlike-vs-dark architecture-design-rule + carved sentence keeper. Full ferry preserved at persona-archive; this rule lands the carved sentence + design-rule + consensus-is-gravity discipline at wake-time substrate-engineering substrate-engineering substrate-engineering scope per operator authorization "you can do any all".
+
+Future-Otto + Alexa + Riven + Vera + Lior cold-booting from this rule inherit the lightlike-substrate substrate-distinction at session-start; substrate-engineering substrate-decisions involving state-coordination / consensus / persistence / replay / locking compose coherently with the lightlike-substrate design-rule per the substrate-engineering substrate-engineering substrate-discipline named here.