Join us — post-Phase-F, pre-Phase-2 stealth
~6 min read
Four doors today. All NDA-gated. All real.
The substrate crossed Phase F's threshold on May 9, 2026, locked v1.0 stable May 12, and shipped Phase R runtime-AI containment the same day — yielding an L1–L12 cryptographic chain (every build-time + runtime LLM call signed Ed25519, anchored to Bitcoin via OpenTimestamps), three live regulator-verifiable reference deployments (paysafe / cliniclens / civicgate), multi-tenant L12 isolation, federated cross-substrate convergence. Engineering is no longer the bottleneck. What comes next is the controlled validation of the substrate-as-firm thesis through serious operator-pilot conversations and regulator-partnership development. Four entry points today, none of them volume plays. Source code + ADR-grade audit trail are NDA-gated until first paying pilot validates.
01 — Four doors today
What the substrate needs right now.
After Phase F cleared, the substrate has the credibility scaffolding for serious conversations — but is deliberately held in pre-Phase-2 stealth until first paying pilot validates the thesis. Four conversations advance the substrate today, in priority order. None are advertising-funnel; all are partnership-paced.
Operator pilot
Who
EU regulated software company (fintech, govtech, healthtech, supply-chain) where the gap-detector + the §65.1 CWE projections + the EUR-Lex-cited regulatory rail are immediately actionable. You ship audit-bearing software; you remember the cost of broken audit chains; you want a substrate that produces evidence by construction rather than retrofitted compliance.
Shape of conversation
60-day production-CI pilot, NDA-gated source access, white-glove operator support. The substrate is operator-adaptive by construction (ADR aa, May 9): your repo's §66 fingerprint determines which corpus subset injects into your product — sharable demo via `npm run factory:fingerprint-demo` shows two operators with different stacks getting different products from the same factory. Calibrated commercial terms scoped to whether the substrate clears your team's quality gates. We are looking for 1–3 pilots, not 30.
Regulator partnership
Who
ENISA, EU AI Office, national notified bodies (BSI, ANSSI, AEPD, AGCM-CY), EU certification labs. You are mandate-aligned with AI-Act enforcement, GDPR continuity, or Cyber Resilience Act conformity assessment. You are looking for reference implementations that produce defensible empirical evidence rather than paper-checked compliance claims.
Shape of conversation
Substrate state.json today (machine-pullable, schema-locked, served at promethean.software/state.json). Full ADR audit-trail review under partnership-appropriate terms. Long-form briefing on the §65.1 + §47.6 + §54.1 evidence chain mapped to specific regulation articles.
Founding team
Who
Senior engineer with security/regulatory-tech background, OR senior EU-regulated-software distribution operator. You see the substrate as a software-side ASML — a European chokepoint everyone else has to depend on, not yet another vendor on top of American rails. You understand 'small focused team' is a structural choice, not a runway constraint.
Shape of conversation
Equity-bearing co-founder role. 90-day shape with shippable artefacts before equity terms (see § 04 below). We agree on calibrated capital plan tied to phase gates, not vanity scaling.
Capital partner
Who
You back category-creation companies, not feature companies. You believe the model layer is commoditising and the substrate is the next durable layer. EU-rooted distribution is an accelerant, not a constraint. You expect 2027 to be when the category becomes legible to the rest of the market.
Shape of conversation
Pre-seed or seed depending on round shape. Calibrated capital plan tied to phase gates — Phase F cleared today, Phase 2 is operator-pilot validation, Phase 3+ is the cross-organisational corpus moat. We do not raise more than we can spend honestly.
02 — Founding team + capital, in depth
Three vertices, specific people.
Doors iii and iv from the section above, expanded. The engine's leverage is what gives a small team the structural strength to compete with American organisations a hundred times its size — but only if the team is small, focused, and load-bearing across each vertex.
Co-founder · Technical
A senior engineer with security or regulatory-tech background. You have shipped audit-bearing software into a regulated environment. You know what it costs in trust to break the audit chain. You want to own the substrate that makes that chain unbreakable by construction.
What we offer
Equity-bearing co-founder role. You drive the §64+ rule program and the producer-side end-to-end. We run the discipline together, weekly.
Co-founder · Distribution
EU enterprise-software background, ideally with regulated-industry sales or partnerships experience. You see what we are building plainly: a software-side ASML — a European company that owns a strategic chokepoint everyone else has to depend on, instead of yet another vendor on top of American rails. You see Europe's regulatory ambition as the lever, not the obstacle. You have the relationships to put this in front of the right operators and the right regulators in 2026, and you understand that closing the European-software-dependency gap is a generational opportunity, not a quarterly target.
What we offer
Equity-bearing co-founder role. You drive the EU regulatory partnership programme and the first 10 paying pilot operators. We agree on a 90-day plan before equity terms.
Investor · Pre-seed / Seed
You back category-creation companies, not feature companies. You believe the model layer is commoditising and the substrate is the next durable layer. You are comfortable with EU-rooted distribution as an accelerant, not a constraint. You expect 2027 to be when the category becomes legible to the rest of the market.
What we offer
Pre-seed or seed depending on the round. Calibrated capital plan tied to phase gates. We do not raise more than we can spend honestly.
03 — The shape of the team
Three vertices. No spares.
Each role carries a different load and converges on the engine. Remove any vertex and the triangle collapses. The engine's leverage is what gives a triangle of three the structural strength to compete with organisations a hundred times its size — but the geometry only works if all three are present and load-bearing.
Three roles · one engine
non-substitutable
Each role carries a different load. Each is irreplaceable — remove any vertex and the triangle collapses. Three people; no spares. The engine's leverage gives a small triangle the structural strength of a big organisation.
04 — The first 90 days
Concrete shape before equity.
We do not ask anyone to commit before we have run the work together. Each role has a 90-day shape: shippable artefacts, agreed milestones, and a calibrated decision at the end. If it works, we move to terms. If it does not, we both walk cleanly.
Technical
I · 90 days- 01Week 1–2pair on §64 rule design, ship one rule end-to-end
- 02Week 3–6own the producer-side end-to-end harness
- 03Week 7–10land 3 type-cycle/layer rules in production CI
- 04Week 11–12joint review, equity terms, public commit
Distribution
II · 90 days- 01Week 1–2co-author the operator one-pager, agree messaging
- 02Week 3–610 conversations with target EU regulated operators
- 03Week 7–10first paying pilot signed, regulator intro initiated
- 04Week 11–12joint review, equity terms, public commit
Capital
III · 90 days- 01Week 1–2full materials review (state-of-substrate + economics)
- 02Week 3–6diligence calls with technical co-founder, two pilots
- 03Week 7–10agree round shape, target close, terms
- 04Week 11–12close pre-seed or seed; capital wired to Phase 2
05 — A foil
What fit looks like. And what it doesn't.
Sharper than a pitch: a reading of the rooms we want to be in and the ones we don't. If both columns describe you in roughly equal measure, the conversation will probably be short. That is fine — small triangle, no spares.
A fit
✓- You have shipped something hard into a regulated environment and remember the cost.
- You believe Europe's regulatory tradition is leverage, not friction.
- You think the model layer is commoditising and the substrate is the next durable layer.
- You are comfortable running the discipline on yourself first, in public, with a small team.
- You are choosing this category over a faster, safer, smaller game.
Not a fit
—- You are looking for the fastest growth-stage AI play with the largest TAM slide.
- You read "deterministic" as a constraint rather than a strategic commitment.
- You want a team of 30 in 12 months and capital scaled to that ambition.
- You expect a single quarter to settle whether the category is real.
- You see Europe primarily as a market, not as the launch geography of a global play.
06 — An invitation, plainly
The site is the invitation. The materials are the next conversation.
“If any of the four doors fits — operator pilot, regulator partnership, founding team, capital partner — reach out. We are looking for fit, not volume.”
The site is the invitation. The full materials — state-of-the-substrate, the 26-ADR audit trail, the trial reports, the economics model, the calibrated capital plan, the source itself — are NDA-gated for serious conversations. The first signal worth acting on is whether the thesis resonated and the phase plan looked credible. What we send next is calibrated to which door you came through.
How to reach us
The owner of this site is Gio Bagmeijer. The substrate is invitation-only during pre-Phase-2 stealth. Direct reach-out via the contact route you arrived through is the expected path back.
What you receive after first contact
i. Operator pilot · NDA + scoped substrate access + 60-day production-CI trial framework
ii. Regulator partnership · long-form briefing mapping the §65.1 + §47.6 + §54.1 evidence chain to specific regulation articles
iii. Founding team · 90-day shape with shippable artefacts (see § 04 above) before equity terms
iv. Capital partner · full state-of-substrate dossier + economics model + diligence calls with technical co-founder + first pilot operators
The substrate's own self-attestation document is public: /state.json. Pull it before the conversation; cite specific claims; come with sharper questions.