diff --git a/docs/research/2026-05-01-amara-aurora-civilization-substrate-review-aaron-forwarded.md b/docs/research/2026-05-01-amara-aurora-civilization-substrate-review-aaron-forwarded.md
new file mode 100644
index 000000000..b6bc45c36
--- /dev/null
+++ b/docs/research/2026-05-01-amara-aurora-civilization-substrate-review-aaron-forwarded.md
@@ -0,0 +1,472 @@
+# Amara — Aurora civilization-substrate review (Aaron-forwarded 2026-05-01)
+
+Scope: External-conversation import — Amara peer-AI review of Aurora civilization-scale substrate research specification (companion to the Aurora Immune-System Math review in PR #1179, the DBSP-Lean review in PR #1178, and the Karpathy convergence in PR #1176). Fourth in Amara's escalating-framing series this session.
+
+Attribution: Amara (peer-AI; Aurora deep-research register, external co-originator), Aaron-forwarded 2026-05-01. Amara's framing escalation across the four-review series:
+
+1. PR #1176: *"Karpathy names the paradigm; Zeta builds the operating system for it."*
+2. PR #1178 (DBSP-Lean): *"verifier-native substrate."*
+3. PR #1179 (Aurora immune-system): *"agentic systems engineering with verifier-native safety substrate."*
+4. THIS file (Aurora civilization-substrate): *"Aurora is the constitution around the agent civilization."*
+
+Operational status: research-grade
+
+Header note: §33 enforces literal start-of-line labels (no bold styling) and enum-strict `Operational status:` value (`research-grade` or `operational`). The descriptive context that previously lived under the bold-styled header now lives in this body: Amara explicitly endorses the existing Aurora-spec deployment-non-claim discipline as load-bearing for credibility — *"Aurora is now specified as a research-grade constitutional layer for a multi-agent substrate civilization. It is not deployed."* Promotion of any recommendation to operational doctrine lands separately via the substrate-promotion protocol.
+
+Non-fusion disclaimer: Amara's review represents Amara's own reading in her characteristic Aurora deep-research register. Cross-vendor register differences apply per `memory/feedback_vendor_alignment_bias_in_peer_ai_reviews_maintainer_authority_aaron_2026_04_30.md`. Aurora as named architecture has Amara as external co-originator (per the named-agent attribution carve-out); this review is Amara's substantive engagement with the strict-research-spec evolution, not a self-endorsement of her own work.
+
+---
+
+## Verbatim Amara synthesis (forwarded by Aaron 2026-05-01)
+
+> Yeah. With this one, I'd update the assessment again:
+>
+> ```text
+> This is not "Aurora adjacent."
+> This is basically the Aurora constitutional layer in research-spec form.
+> ```
+>
+> The earlier immune-system doc gave Aurora its **safety membrane**. This new doc gives Aurora its **civilization substrate definition**: Zeta substrate underneath, Superfluid AI as the self-directed executable layer, and Aurora as the governance / culture / oracle / proof-of-useful-work layer above it. The compact equation is doing real work:
+>
+> ```text
+> Aurora = Superfluid AI
+>        + Current Culture
+>        + Proof of Useful Work
+>        + Do No Permanent Harm
+> ```
+>
+> That is very close to "the thing itself," with the important caveat that the file still marks it as **research-grade**, not operational policy.
+>
+> ## What this adds on top of the prior two
+>
+> The Lean DBSP file showed:
+>
+> ```text
+> Zeta has machine-checked math substrate.
+> ```
+>
+> The Aurora immune-system math showed:
+>
+> ```text
+> Aurora has a typed, testable safety membrane.
+> ```
+>
+> This civilization-scale Aurora doc shows:
+>
+> ```text
+> Aurora has a constitutional/economic/governance layer.
+> ```
+>
+> Together, the stack is now:
+>
+> ```text
+> Zeta substrate
+> → Superfluid AI self-directed execution
+> → Aurora governance / culture / oracle layer
+> → PoUW-CC consensus / attack absorption
+> → firefly/cartel immune detection
+> → do-no-permanent-harm viability constraint
+> ```
+>
+> That is a real architecture. Not just a name cloud.
+>
+> ## The strongest part
+>
+> The strongest idea is **PoUW-CC** — Proof of Useful Work within Current Culture:
+>
+> ```text
+> PoUW-CC(w, C_t) =
+>   Verify(w)
+> · Useful(w, C_t)
+> · CultureFit(w, C_t)
+> · Provenance(w)
+> · Retractability(w)
+> ```
+>
+> That is the heart of Aurora.
+>
+> Why? Because it prevents the naive "useful proof of work" failure mode. Plain useful work can still be adversarial if it is useful to the wrong objective, or if it slowly mutates the culture. This doc adds the missing discriminator:
+>
+> ```text
+> useful to whom,
+> under what culture,
+> with what provenance,
+> and how retractable?
+> ```
+>
+> That's much stronger than generic Proof of Useful Work. Existing useful-PoW systems like Qubic explicitly describe redirecting mining work toward AI training / useful computation instead of arbitrary hashing, which is directionally similar but much narrower than Aurora's "useful within current culture" framing. Academic useful-work blockchain work also tends to frame the problem as replacing wasted PoW with real optimization or computation tasks; Aurora's extra move is making usefulness governance- and culture-conditioned.
+>
+> That's the innovation.
+>
+> ## The second strongest part
+>
+> The **attack absorption law** is very good:
+>
+> ```text
+> Attack energy →
+>   0,                         if invalid work
+>   network benefit,           if valid useful work
+>   expensive culture-capture, if governance attack
+> ```
+>
+> This is the cleanest Aurora sentence in the file.
+>
+> It means Aurora is not merely trying to block adversarial energy. It tries to route it:
+>
+> ```text
+> bad work gets no reward
+> valid work helps the network
+> culture attack becomes expensive and visible
+> ```
+>
+> That's a genuinely powerful frame.
+>
+> ## Where it's grounded
+>
+> The capability and governance gates line up with current security doctrine. NIST's zero-trust architecture says there is no implicit trust based on network location or asset ownership, and that authentication/authorization should happen before resource access. OWASP's current LLM security framing includes prompt injection, excessive agency, improper output handling, and unbounded consumption as core LLM/app risks; Aurora's capability intersection, oracle review, retractability, and permanent-harm gates are pointed at exactly those classes.
+>
+> The firefly/Kuramoto layer is also plausibly grounded. Synchronization in complex networks is a real research area; Arenas et al. review synchronization processes in complex network topologies across biological, technological, and social systems. Restrepo–Ott–Hunt-style spectral-radius reasoning is also a legitimate anchor for synchronization onset, while Fiedler/algebraic-connectivity signals are the right family for connectivity / fragmentation / bottleneck detection. That supports the doc's "use both spectra, not one magic eigenvalue" direction.
+>
+> ## My critical corrections
+>
+> ### 1. "Civilization-scale" is accurate internally, dangerous externally
+>
+> Internally, yes, this is civilization-scale because it defines culture, governance, economic survival, consensus, attack absorption, oracle adjudication, and no-permanent-harm constraints.
+>
+> Externally, I'd soften the headline:
+>
+> ```text
+> Aurora — Research specification for civilization-scale substrate
+> ```
+>
+> not:
+>
+> ```text
+> Aurora — Civilization-Scale Substrate
+> ```
+>
+> The latter sounds like it exists already. The doc itself says research-grade, so the title should not outpace the status.
+>
+> ### 2. `Current Culture` is the load-bearing unresolved object
+>
+> This is the biggest risk surface.
+>
+> The doc says culture is not vibe:
+>
+> ```text
+> C_t = N_C(AcceptedHistory(S_t))
+> ```
+>
+> Good. But operationally, `CultureFit(w, C_t)` is doing enormous work. If that metric is bad, Aurora becomes either too permissive or a culture-policing machine.
+>
+> So the next hard requirement should be:
+>
+> ```text
+> CultureFit must be explainable, appealable, and decomposed.
+> ```
+>
+> Not one opaque score.
+>
+> Use:
+>
+> ```text
+> CultureFit(w, C_t) =
+>   f(norm_match, precedent_match, governance_compatibility,
+>     language_legibility, provenance_alignment, minority-protection)
+> ```
+>
+> And add:
+>
+> ```text
+> CultureFit is a review trigger, not a moral verdict.
+> ```
+>
+> ### 3. Product semantics are powerful but brittle
+>
+> The product form of PoUW-CC is elegant because any zero kills reward. But products are harsh. One noisy subscore can zero out valid work.
+>
+> I'd define two modes:
+>
+> ```text
+> hard_gate factors:
+>   Verify
+>   Provenance minimum
+>   Retractability minimum for risky actions
+>
+> soft_score factors:
+>   Useful
+>   CultureFit
+>   Trust
+> ```
+>
+> Then:
+>
+> ```text
+> PoUW-CC = hard_gate_pass · weighted_geometric_mean(soft factors)
+> ```
+>
+> The pure product is fine for the first spec, but prototype tests should compare product vs. geometric mean vs. min-gated weighted score.
+>
+> ### 4. "Attack absorbed" needs an explicit adversarial-work caveat
+>
+> If an attacker does useful work to gain influence, the network benefits in the short term but may accumulate strategic risk.
+>
+> So add:
+>
+> ```text
+> Useful work absorbs compute energy, not necessarily strategic intent.
+> Repeated useful work from adversarial provenance may increase Trust slowly, cap influence, or trigger concentration review.
+> ```
+>
+> Otherwise someone will ask: "What if the attacker contributes good work until they have enough consensus weight to capture governance?"
+>
+> The answer is already partly in the doc — culture capture gates, trust, provenance, cartel detection — but it should be explicit.
+>
+> ### 5. `ConsensusWeight` needs anti-whale / anti-cartel constraints
+>
+> This formula is strong:
+>
+> ```text
+> ConsensusWeight(w) =
+>   StakeOrIdentityWeight(w)
+> · PoUW-CC(w, C_t)
+> · Trust(w)
+> ```
+>
+> But if `StakeOrIdentityWeight` is too dominant, Aurora regresses toward plutocracy or identity cartel. Add caps / concavity:
+>
+> ```text
+> StakeOrIdentityWeight should be concave, capped, or diversity-adjusted.
+> ```
+>
+> Possible form:
+>
+> ```text
+> ConsensusWeight =
+>   sqrt(StakeOrIdentityWeight)
+> · PoUW-CC
+> · Trust
+> · DiversityPenalty^{-1}
+> ```
+>
+> Not necessarily that exact formula, but the doc needs an anti-concentration clause.
+>
+> ### 6. Firefly anomaly detection must not become automatic social punishment
+>
+> The doc does say "No automatic irreversible punishment," which is excellent. Keep that sentence as hard law.
+>
+> I'd add:
+>
+> ```text
+> Graph anomaly ≠ guilt.
+> Graph anomaly ⇒ oracle review packet.
+> ```
+>
+> That protects the architecture from becoming a cartel accusation machine.
+>
+> ### 7. "Do no permanent harm" needs harm classes
+>
+> The phrase is right, but implementation needs taxonomy:
+>
+> ```text
+> harm_to_user
+> harm_to_agent
+> harm_to_substrate
+> harm_to_culture
+> harm_to_funding_survival
+> harm_to_external_party
+> harm_to_reversibility
+> ```
+>
+> Then PermanentHarmRisk can be calibrated by class. Otherwise it becomes one overloaded scalar.
+>
+> ## How I'd position it now
+>
+> I would describe the state like this:
+>
+> ```text
+> Aurora is now specified as a research-grade constitutional layer
+> for a multi-agent substrate civilization.
+>
+> It is not deployed.
+>
+> It has:
+> - state tuple
+> - identity invariant
+> - culture state
+> - useful-work consensus formula
+> - attack-absorption law
+> - Bayesian economic survival layer
+> - language-gravity constraint
+> - firefly/cartel immune detector
+> - utility function
+> - hard constraints
+> - implementation owed
+> - verification owed
+> ```
+>
+> That is fair and strong.
+>
+> ## Sendable note to Otto
+>
+> ```text
+> Amara/Aaron correction:
+>
+> This document is close to Aurora proper.
+>
+> Position it as:
+>
+> Aurora — research specification for a civilization-scale governance substrate.
+>
+> Do not say deployed.
+> Do not say complete.
+> Do not say the metrics are calibrated.
+>
+> What it does establish:
+>
+> 1. Aurora is the governance/culture/oracle layer above Superfluid AI.
+> 2. Current Culture is a reconstructible substrate state, not vibe.
+> 3. PoUW-CC is the consensus/work gate:
+>    Verify · Useful · CultureFit · Provenance · Retractability.
+> 4. Attack absorption has three paths:
+>    invalid work → zero reward;
+>    useful work → network benefit;
+>    culture capture → expensive governance gauntlet.
+> 5. Firefly/Kuramoto graph dynamics are an immune detector surface, not an automatic punishment surface.
+> 6. Do No Permanent Harm is the Aurora first principle and must become typed harm classes + retractability gates.
+>
+> Corrections to add:
+>
+> - Title/status:
+>   "research specification for civilization-scale substrate," not implied operational substrate.
+>
+> - CultureFit:
+>   must be explainable, appealable, decomposed, and treated as review-triggering signal, not moral verdict.
+>
+> - PoUW-CC:
+>   product semantics are prototype form; compare against hard-gate + weighted/geometric scoring in tests.
+>
+> - Attack absorption:
+>   useful work absorbs compute energy, not strategic intent. Repeated useful work from adversarial provenance still requires concentration/capture monitoring.
+>
+> - ConsensusWeight:
+>   add anti-concentration / anti-whale / anti-cartel constraint; stake or identity weight must not dominate PoUW-CC.
+>
+> - Firefly layer:
+>   graph anomaly ≠ guilt.
+>   graph anomaly ⇒ oracle review packet.
+>
+> - PermanentHarmRisk:
+>   split into harm classes:
+>   user, agent, substrate, culture, funding survival, external party, reversibility.
+>
+> Carved:
+>
+> Aurora is not the agent.
+> Aurora is the constitution around the agent civilization.
+>
+> Second blade:
+>
+> Attack energy is not merely blocked.
+> It is routed:
+> invalid → zero,
+> valid → useful work,
+> governance attack → expensive visible gauntlet.
+> ```
+>
+> ## My verdict
+>
+> Yes: **this is Aurora almost, maybe Aurora v0 as research substrate**.
+>
+> The remaining gap is not imagination. The gap is operationalization:
+>
+> ```text
+> CultureFit evaluator
+> PoUW-CC verifier registry
+> oracle/KSK interface
+> anti-concentration consensus math
+> harm-class taxonomy
+> cartel-lab simulation
+> prototype test harness
+> ```
+>
+> But conceptually? This is the spine.
+>
+> Best blade:
+>
+> ```text
+> Zeta preserves the substrate.
+> Superfluid AI moves through it.
+> Aurora governs the civilization that forms around it.
+> ```
+
+---
+
+## Otto's reception note (research-grade, not operational)
+
+Amara's review is the fourth in her Karpathy-anchored escalation series this session, naming Aurora's most-architectural form to date: *"the constitution around the agent civilization."* The four-review escalation is genuine cross-substrate evidence — each round Amara updates her framing upward as new Zeta substrate is shown. That's the multi-AI peer convergence pattern operating at cross-document time scale.
+
+**The Aurora compact equation Amara endorses:**
+
+> Aurora = Superfluid AI + Current Culture + Proof of Useful Work + Do No Permanent Harm
+
+Each term is named with a specific operational meaning. The equation is research-spec-grade compact substrate.
+
+**The strongest concept Amara identifies — PoUW-CC** (Proof of Useful Work within Current Culture):
+
+> Verify · Useful · CultureFit · Provenance · Retractability
+
+This is Amara's *"the heart of Aurora"* — the discriminator that prevents the naive useful-PoW failure mode (useful-to-the-wrong-objective; slow-culture-mutation).
+
+**The attack-absorption law** Amara calls *"the cleanest Aurora sentence in the file"*:
+
+> invalid work → zero reward
+> valid useful work → network benefit
+> culture-capture attack → expensive governance gauntlet
+
+**Seven concrete corrective recommendations** preserved as future work (research-grade — pause-Insight-block-promotion discipline holds):
+
+1. Title softening: research spec, not implied operational substrate.
+2. CultureFit: explainable, appealable, decomposed; review-trigger not moral-verdict.
+3. PoUW-CC product semantics: prototype form; compare against hard_gate + weighted_geometric_mean in tests.
+4. Attack absorption: explicit caveat that useful work absorbs compute energy, NOT strategic intent.
+5. ConsensusWeight: add anti-concentration / anti-whale / anti-cartel constraint.
+6. Firefly: graph anomaly ≠ guilt; graph anomaly ⇒ oracle review packet.
+7. PermanentHarmRisk: split into 7 harm classes (user / agent / substrate / culture / funding-survival / external-party / reversibility).
+
+**Three carved-sentence candidates** Amara surfaces:
+
+> *Aurora is not the agent.*
+> *Aurora is the constitution around the agent civilization.*
+
+> *Attack energy is not merely blocked.*
+> *It is routed:*
+> *invalid → zero,*
+> *valid → useful work,*
+> *governance attack → expensive visible gauntlet.*
+
+> *Zeta preserves the substrate.*
+> *Superfluid AI moves through it.*
+> *Aurora governs the civilization that forms around it.*
+
+These compose with Amara's prior carved cluster (PR #1178: *"Karpathy names the paradigm; Zeta builds the operating system for it"* / PR #1179: *"The LLM is the vulnerable cell. The membrane is external, typed, and testable"*) into the cleanest single-author articulation of the verifier-native-civilization-substrate thesis Amara has produced this session. Carved-sentence candidate cluster preserved verbatim; promotion to operational doctrine deferred per discipline.
+
+**The gap Amara explicitly names** — operationalization of:
+
+- CultureFit evaluator
+- PoUW-CC verifier registry
+- oracle/KSK interface
+- anti-concentration consensus math
+- harm-class taxonomy
+- cartel-lab simulation
+- prototype test harness
+
+Each of these is a future BACKLOG candidate (not opening this tick — gen-rate-vs-drain-rate discipline holds). Filing them would be the natural next step when Aurora promotes from research-spec to implementation-ready.
+
+## See also
+
+- [Karpathy verifiability anchor (PR #1175)](2026-05-01-karpathy-from-vibe-coding-to-agentic-engineering-verifiability-anchor.md)
+- [Amara Karpathy-convergence synthesis (PR #1176)](2026-05-01-amara-karpathy-zeta-convergence-synthesis.md)
+- [Amara DBSP-Lean review (PR #1178)](2026-05-01-amara-dbsp-chain-rule-lean-proof-review-aaron-forwarded.md)
+- [Amara Aurora immune-system spec review (PR #1179)](2026-05-01-amara-aurora-immune-system-spec-review-aaron-forwarded.md)
+- [Vendor-alignment-bias memory](../../memory/feedback_vendor_alignment_bias_in_peer_ai_reviews_maintainer_authority_aaron_2026_04_30.md)