Knowledge base · 04a-sphuran-grevoro-separation

04a - Sphuran, Grevoro, and what their separation means

Status. Draft v0.1 · First draft: 17-03-2026 · Co-authored from a structured discussion with the team.

Why this matters. Stakeholders reading the platform’s trust chain will eventually ask the most consequential structural question in the architecture: who runs the verifier registry, and what is their commercial relationship to the product whose claims are being verified? The answer matters because the cryptographic anchors of the trust chain are only as credible as the entity holding the keys. If the same company that builds GREMI also operates SIDK’s signing infrastructure and verifier registry, the structure has an embedded conflict of interest - regardless of intent, regardless of execution quality. The market knows this, and sophisticated buyers, regulators, and accreditation bodies will check. This doc states what is actually true about Sphuran and Grevoro’s relationship, why that arrangement produces an unusually clean answer to the structural question, and how to talk about it honestly without overclaiming.

This is one of the most important docs in the knowledge base, and one of the easiest to get wrong by leaning into a moat narrative that the facts do not quite support. The facts are good enough on their own.

1. The facts, as they stand today

Sphuran and Grevoro are separate legal entities, with separate cap tables and separate investors. Neither holds equity in the other. Neither is a subsidiary of a common holding entity.
There is no overlap in leadership. Founders, executive teams, and operating leads are distinct. Decision-making in each company runs through its own structure.
The two companies are operationally independent. Separate hiring, separate roadmaps maintained inside each company, separate operating cadences. The seam between them - when SIDK’s roadmap and GREMI’s near-term needs interact - is relationship-based today, not contractual or governance-bound. This is appropriate for the current phase and is named as a thing to watch as both companies scale.
The two companies are mission-aligned. Both are committed to making sustainable manufacturing measurable, attestable, and economically real. Sphuran wants impact - it is a research organisation, not a licensing business - and Grevoro is the partner taking one of Sphuran’s research outputs (SIDK with the carbon engine) to market.
Sphuran does not currently sell SIDK. There is no licensing revenue line; SIDK is provided to Grevoro under a partnership arrangement rather than a commercial contract.

This is the structural reality. Everything below in this doc follows from these five facts. If any of them change - Sphuran begins selling SIDK to third parties, the companies acquire common investors, leadership starts overlapping - the framing in subsequent sections needs to be reread.

2. Why this produces an unusually clean answer to the verifier-neutrality question

The standard pattern in “neutral platform vs product company” arrangements is for the neutrality to weaken under scrutiny. The most common failure modes:

The platform company and the product company share founders, or have substantial founder-equity overlap. Verifiers and regulators discount the neutrality claim accordingly.
The platform company and the product company share investors, especially at the lead-investor level. Board influence flows; the neutrality is theoretically present and practically compromised.
The platform company is a subsidiary of the product company, or vice versa. The org chart settles the question against neutrality before any operational argument starts.
The platform company and the product company are operationally entangled - shared engineering teams, shared go-to-market - even where the legal structure is separate.

Sphuran-Grevoro does not have any of these patterns. Separate entities, separate cap tables, separate investors, no leadership overlap, separate operating teams. The two companies are linked only by mission alignment and a working relationship - neither of which is a control mechanism.

The trust-architecture consequence is concrete:

SIDK’s response-signing keys are held by Sphuran. Sphuran has no commercial stake in Grevoro’s customer revenue, no equity exposure to Grevoro’s enterprise value, no shared investor pressure for a particular customer outcome.
The verifier registry - the list of accredited verifier firms, with their public keys and accreditation status - is operated by Sphuran. Sphuran has no relationship with the verifier firms beyond running the registry honestly; it has no commercial reason to admit or exclude any specific firm.
The DID infrastructure that allows Tenants to sign their own claims under their own keys is operated by Sphuran. Sphuran does not control a Tenant’s signing identity; it operates the directory.

A regulator or accreditation body checking the structural question - can SIDK credibly run the trust surfaces that buyers and regulators rely on, given that one of its applications is GREMI? - gets a clean answer. The answer is yes, because the entity running the trust surfaces (Sphuran) is structurally separate from the entity selling the product (Grevoro) in every way that matters: legal, capital, leadership, operational. The separation is not asserted; it is documented in two separate corporate filings.

3. How the structural separation actually arose

The honest framing matters because the moat is real but the story is often told incorrectly.

The arrangement was not designed as a moat. Sphuran did not create SIDK with the intention of positioning it as a neutral platform for a separate product company to ride on. SIDK was built by Sphuran as a general-purpose research infrastructure for anchoring data against physical reality - useful internally across Sphuran’s research divisions (advanced materials, machine topologies, medical equipment, operational control loops, computational design). See 05 - SIDK for the full origin story.

Grevoro is a separate company that wanted to build GREMI. When Grevoro emerged with the intent to take a carbon-platform product to market, SIDK was a natural substrate: vertical-neutral, deterministically rigorous, evidence-tier-aware, six years matured. The two companies recognised the alignment, formalised a partnership, and have grown together since. There was no period during which the same team built both SIDK and GREMI under a common roof and then artificially separated them for verifier-neutrality optics.

The structural separation is a property of how the two companies came to exist, not a marketing decision. This is the part the doc should land carefully. The moat is real - the trust-architecture consequence is genuinely valuable, and as both companies scale, the separation can be leveraged in investor, partner, and verifier conversations with confidence. But the founding reason the separation exists is not “we deliberately structured a neutral platform to enable trustworthy verification of our own product.” It is “Sphuran does research; Grevoro builds products; their missions aligned around carbon-and-steel; the structural separation was already there.”

This is a stronger argument than the deliberate-moat framing, not a weaker one. A moat that arose from how the work was already organised is harder to dismiss than a moat that arose from a corporate-structure choice. The latter invites the question “and what’s stopping a competitor from doing the same?” The former answers it: “the competitor would need a separate research organisation with six years of substrate work that happens to have built the right kernel for the moment.” That is not a structure another team can put in place by drafting articles of incorporation.

4. How to talk about this externally

A few patterns that work and a few that overclaim:

Works: “SIDK is operated by Sphuran, a research organisation with no equity, leadership, or operational connection to Grevoro. The verifier registry, the response-signing keys, and the DID infrastructure are all in Sphuran’s hands - which means the entity running the cryptographic anchors of the trust chain has no commercial stake in any specific carbon claim’s outcome.”

Works: “The structural separation between Sphuran and Grevoro was not a corporate-structure decision made to enable verifier neutrality; it is a property of how the two companies arose. Sphuran does multi-domain research; Grevoro builds GREMI on top of one of Sphuran’s research outputs. The neutrality is real, verifiable, and load-bearing - and it is also unusually defensible because it predates the verifier-neutrality conversation rather than being constructed for it.”

Overclaims: “Sphuran exists to be the neutral platform for any company that wants to build verifiable carbon products.” - Untrue. Sphuran exists to do research. SIDK is one output. The neutrality is a property, not a purpose.

Overclaims: “The corporate structure was deliberately designed to position SIDK as a structurally trustworthy verifier-registry operator.” - Untrue. The structure arose from independent corporate origins.

Underclaims: “We have a partner that operates the underlying platform.” - Hides the load-bearing fact. The separation is unusually clean and is materially important to the trust architecture; saying “we have a partner” is the kind of phrase a casual reader interprets as a contractor relationship, which is the wrong picture.

In investor or board conversations, the framing should be confident. In verifier or regulator conversations, the framing should be precise - name the legal entities, name the absence of leadership overlap, name the absence of common investors, and let the listener verify the structural claim against the corporate filings. In customer-facing materials, the framing should be honest about the long-term advantage without making it the lead.

5. The seam between the two companies, today and as it scales

The two companies’ roadmaps interact. Inevitably. GREMI is the only externally-visible product on SIDK today; SIDK’s roadmap and engineering attention shape what GREMI can deliver and when; GREMI’s commercial needs surface requirements that SIDK has to absorb. The seam is real and is operating productively today on a relationship basis - the people who run each company talk to each other, decisions get made, work happens.

This is appropriate for the current phase. It is also a thing to watch over time. As both companies scale, three patterns are worth pre-empting:

Pattern 1 - Conflict resolution under stress. When SIDK’s research-shaped roadmap and Grevoro’s customer-shaped roadmap disagree on priority, the resolution today depends on the quality of the working relationship. This works fine while both companies are small and the leadership knows each other. It is harder when the companies are larger and the people in the room change. A future doc should describe a light governance forum - joint roadmap review, perhaps quarterly - that exists before a conflict makes it necessary.

Pattern 2 - Maintaining structural separation under capital pressure. Both companies will raise capital independently as they scale. Maintaining no-leadership-overlap and no-common-investor properties under that pressure is a deliberate choice each company will need to keep making. The neutrality argument depends on the properties holding; investors who push for tighter alignment will need to be told no, with the trust architecture as the reason.

Pattern 3 - The point at which Sphuran begins (or chooses not to) license SIDK to other Product Owners. Today, Sphuran does not sell SIDK. The platform’s neutrality benefits from being applied uniformly - one Product Owner, one product, no commercial differentiation between consumers of the substrate. As the architecture contemplates a second Product Owner (cement, pharma, aluminium products built by other companies on the same substrate), the relationship structure between Sphuran and each Product Owner will need to be deliberate. Replicating the Grevoro-style partnership for every Product Owner is one path; standardising terms in a way that does not produce commercial preference is another. This is not a today-question, but it is a foreseeable next-decade question that doc 05 should reference.

None of these patterns is currently a problem. Each one is the kind of thing a thoughtful operator surfaces in advance so it does not become a problem.

6. What this means for the trust chain in practice

The three-signature trust chain (06 §1, 08b §4) has three independent identities holding three independent keys:

Tenant holds its DID-registered signing key, provisioned by Sphuran at onboarding. The Tenant signs claims.
Verifier holds its accreditation-registered key, registered in Sphuran’s verifier registry. The Verifier signs attestations.
SIDK (the platform) holds the response-signing keys, operated by Sphuran. The platform signs delivery.

The structural separation between Sphuran and Grevoro is what makes the third signature meaningful. If Sphuran were operationally entangled with Grevoro, a buyer or regulator could reasonably ask whether the platform-delivery signature was independent of the product whose claims were being delivered. With the structural separation in place - separate entities, no leadership overlap, no shared cap tables - the platform-delivery signature is from an entity that has no commercial stake in the specific claim’s success.

This does not solve every trust question. It does solve the structural-conflict-of-interest question that the architecture’s neutrality principle (Foundation §4.2) names as one of the platform’s load-bearing commitments.

The architecture’s principle is sound. The structural reality is unusually clean. Doc 04a’s job is to make sure both stay aligned and that the framing used externally matches both.

References & further reading

Source documents

Docs/GREMI-App-Ecosystem/foundation-v1.4.md - §1.4 (Product Owner), §1.5 (Platform), §1.6 (Why these five, and not more or fewer), §2.7 (Co-branding, white-label, and neutrality policy), §4.2 (Structural neutrality), §5 (The trust chain). The architectural doc that names structural neutrality as one of the platform’s load-bearing principles.
KnowledgeBase/04-carbon-as-trust-infrastructure.md - Property 7 (Attestable by an independent verifier) - the requirements-list framing that the Sphuran-Grevoro structural separation operationalises.
KnowledgeBase/05-sidk.md - the substrate doc; explains what Sphuran built and why.

External authoritative sources

ISO 14065:2020 - General principles and requirements for bodies validating and verifying environmental information. The accreditation framework that determines who is allowed to operate as a verifier. The standard places weight on the verifier’s structural independence from the producer; an analogous independence between the platform and the product owner is the right frame for thinking about Sphuran-Grevoro. https://www.iso.org/standard/74257.html
European Accreditation - The EU CBAM and the role of accreditation. The clearest accessible explainer of how accreditation, attestation, and trust-infrastructure operators interact in a real regulatory regime. Useful for thinking through how Sphuran’s role in the trust chain will read to an accreditation body. https://european-accreditation.org/the-eu-cbam-and-the-role-of-accreditation/
W3C Verifiable Credentials Data Model. The cryptographic standard underlying the three-signature trust chain. The data model does not care about corporate structure; the credibility of the keys depends on the trust placed in the entities holding them, which is what this doc is about. https://www.w3.org/TR/vc-data-model-2.0/