For the partners at Extantia. About the audit layer beneath EPIC — how every Gigacorn math claim becomes queryable rather than narrated.
Flagship II is roughly eighteen months into deployment. Every signed portco's math defends to the published thresholds. SFDR 2.0 lands for entry in 2028, inside the cycle. Thirty percent of partner carry is contractually tied to the chain's integrity.
cases/extantia · audit_chain_v1 · methodology_overlay_v1
One published threshold. One coined ambition. One discipline named in the partner's bio. The audit layer between EPIC and source events is the wedge.
Extantia's published symbol is numerical: at least 100Mt CO2e/year per portco, Gigacorn tier at ≥1Gt CO2e/year — codified in the firm's SFDR disclosure. Yair Reem's published frame is the discipline over it: the carbon-math methodology quantifying gigaton-scale impact per portco. A 1Gt portco claims ~30% of EU annual emissions — a number that only survives auditable defence.
EPIC (Extantia Projected Impact Calculation) is the published calculation regime; Impact Carry KPIs tie 30% of GP carry to portco-level impact targets. What is not yet public is the audit layer between them — the chain that traces each Gigacorn math claim from EPIC output back to source events (LCA, pre-order, deployment, verification). Currently lives in IC memos as narrative.
- SFDR review proposal COM(2025) 841 final (20 Nov 2025) remaps Article 9 for 2028 entry — inside the Flagship II deployment window.
- Three new categories, each 70% threshold, product-level PAI.
- Yair has publicly framed SFDR compliance burden on LinkedIn. The substrate is the operational answer he already named.
Four archetype rows. Each carries a distinct impact-math architecture — direct displacement, direct capture, substitution, measurement-as-multiplier. The aggregate megatonne composes across them.
FIG. ── PER-PORTCO EVIDENCE REGIME · 4 GIGACORN ARCHETYPES × NATIVE UNIT · EPIC FIELD ANCHOR · AUDIT-SOURCE CLASS
What is new is the defence burden. Cross-row aggregation to the fund-level megatonne requires explicit boundary management to preserve the 100Mt floor on every row. EPIC names the field; the chain names what filled it.
Two primitives sit between EPIC and source — audit chain and methodology overlay. EPIC stays public. The internal layer makes every Gigacorn math claim reconstructable on demand.
Every event a portco produces that updates a Gigacorn math claim — a customer pre-order signed, a deployment site commissioned, an LCA certified, a capacity-factor telemetry batch logged, a third-party rating accuracy verified, an EPIC-field recalculation triggered — appends to a hash-chained log carrying six tags per event: portco, Gigacorn class, EPIC field updated, Impact Carry KPI mapping, SFDR 2.0 remap target, and source verification class. Append-only, never-deletable.
The Reverion pre-orders claim, the INERATEC deployment trajectory, the BeZero rating accuracy — each becomes a query against the chain rather than a narrative in an IC memo. SFDR 2.0 remap in 2028 inherits the chain without re-derivation; the tag is already there at event time.
Each portco gets an inspectable YAML regime — Gigacorn class, EPIC calculation instantiated for this portco, Impact Carry KPIs with target values and interim annual targets, SFDR remap target, verification class, audit-source baseline, time-to-impact trajectory, and a binary "Better, Faster, Cheaper & Green" status — Yair's discipline encoded as a field on the spec. Does this portco win without a green premium?
The EPIC methodology PDF becomes a generator template. Each portco's EPIC instance becomes a versioned YAML. The chain holds the events that update each field. Yair's carbon-math methodology — already operational — surfaces from IC memos into versioned artifacts that survive the next ten years of deployment, SFDR transitions, and team rotation.
Together, the AUDIT CHAIN names what evidence exists; the OVERLAY names what EPIC says it is supposed to mean. Same source of truth, two reading frames — one for the LP running the Impact Carry KPI test, one for the supervisor running the 70% Sustainable threshold.
FIG. ── AUDIT CHAIN · IMPACT-EVENT BLOCKS · SIX TAGS PER EVENT · APPEND-ONLY · NEVER-DELETABLE
FIG. ── GIGACORN COMPOSITION · ARCHETYPE LANES → EPIC ROLL-UP → SFDR 2.0 REMAP TARGETS
Every Gigacorn math claim defends to a number. Pressure-test the audit layer beneath it.
The substrate answers in its own voice — the same primitive we'd install on one Gigacorn class and one Flagship II portco. Not a demo. The actual reasoning surface.
STREAMING · κ ≥ 0.85 · ANONYMITY HOLDS · CITATIONS BY DEFAULT
One Gigacorn class. One Flagship II portco's math claim. Audit-chain stub. One overlay YAML the partners can mark up.
We pick one Gigacorn class — direct-impact energy generation, capture & removal, industrial decarbonisation, or measurement & second-life — and one real Flagship II portco from it. We deliver an audit-chain stub instrumented with the six event tags, plus one methodology-overlay YAML for that portco's EPIC instance and Impact Carry KPIs. The partners read it, mark it up, and decide whether the regime extends to the rest of the fund.
If relevant, I can send a short async questionnaire — no call needed — and build a no-charge synthetic-data Phase 0 PoC "Extantia AI OS". Within two weeks, replay one Flagship II portco's evidence chain against the EPIC Impact Carry KPI test and the SFDR 2.0 70% Sustainable threshold before the LP and the supervisor start citing it.
LCA methodology · evidence beneath the model · Article 9 climate-tech at scale.
AI OS for the Urban Stack at €500M · climate adaptation across the built environment.
Published impact-carry formula meets non-linear evidence-chain growth — and an SFDR 2.0 replay.