A new way to think about physical practice.

OPG-L is computational, not merely descriptive: a project is a program, an event is its execution: the doing and the record of the doing are one artifact. That is what separates it from the provenance formats it interoperates with, which only serialize what already happened.

HideSync is the reference implementation: a locally-hosted, three-service realization of OPG-L 0.6 in production-grade software: content-addressed storage, immutable lineage, amendment-Event corrections, provable upstream commitments at visibility boundaries. The same model serves a hobbyist's wallet and a pharmaceutical batch record from one spine: the standard's, not a shared codebase. Rillmark's commercial backend will be a separate, ground-up build; the bridge is the wire format, so records made in HideSync export into it without lock-in.

The architecture is CQRS-centric and content-addressing-centric. Every projection (graph, analytics, search, the commons plane) is a consumer of the same write log. This is what makes the commons plane physically separable onto Foundation-owned infrastructure: a deployment change, not a data-model migration.

This inverts the usual SaaS assumption. The product is a view over an open standard. The strategic consequence: Rillmark's durability depends on being useful, not on being sticky. The commons is the asset: not the code, but the accumulated attributed knowledge and the governance structure that keeps it neutral.

Bridging-as-business-model. A bridging standard is credible only when bridges exist that use it. Rillmark's own multi-head architecture is the running demonstration. Every head is a production proof point for OPG-L: SaaS PM/ERP for SMEs, an Alias & Licensing Service for cross-jurisdictional provenance, a Gated Academia Portal for citation-grade reproducibility, an Audit & Validation layer for regulatory neutrality, a Search & Rescue head for multi-agency emergency coordination. Competitors selling an alternative standard would have to build all of these themselves to match the proof. Defensibility is structural, not feature-based.

The OPG-L Node — not Rillmark Inc., not the Foundation — is the federation primitive. Any organization-operated implementation of OPG-L is a Node. Nodes emit OPG-L records, consume OPG-L records, and federate via the standard. Three operator categories carry the load:

Operator 03 · Independent Sovereign Nodes. Operated by entities that are neither Rillmark Inc. nor the Foundation: First Nations communities, academic institutions, regulators, NGOs, sectoral consortia. Each independent Node is governed by its operator on its own terms. The Foundation facilitates independents (technical scaffolding, legal templates, federation-protocol coordination) but never owns or operates them. Sovereignty is preserved by construction, not by policy. Analog: country-code TLDs in DNS.

Allocation follows function, and phase. A head lives with the Foundation when its operator-shape would otherwise compromise it: neutral registry, academic legitimacy, regulatory neutrality, multi-agency trust. A head with clean commercial economics lives with Rillmark Inc. And a head can run under one operator on its way to the other: the Alias & Licensing Service can launch under Rillmark Inc. on explicit Foundation license and migrate at activation. Two things do not move: Rillmark Inc. builds the infrastructure, including the Foundation's; the Foundation provides the standard, including to Rillmark Inc.

Operates vs. facilitates is the legal hinge. The Foundation operates head infrastructure under eIDAS-class posture. The Foundation facilitates the substantive work that uses those heads (research projects, SAR operations, indigenous-data work) without carrying operational liability for it. Conflating the two exposes the Foundation to liability it cannot insure against.

The fork clause is not ornamental. Once the Foundation holds the specification and the data, and because the application is only a view over that data, any sufficiently motivated group of practitioners can reconstitute Rillmark around a new client without losing the accumulated commons. This is what "no data hostage" means structurally. Today the export, the running software, and the public commons are already checkable; the specification, the Foundation charter, and the licensing schedule become checkable as the Foundation forms. By design, everything Rillmark commits to is built to be independently verifiable.

The funding flows in a circle that keeps both sides honest. Rillmark Inc. licenses OPG-L from the Foundation, the same shape as Red Hat's dues to the Linux Foundation, and a commercial operator paying for the standard is the clearest proof of its value. The capital pools stay separate: equity investors cannot push the Foundation to commercialize, and grant funders cannot push the company off-commercial.

Defensibility is the running demonstration. A bridging standard is credible only when bridges exist that use it. Rillmark will address four distinct surfaces with the same primitives, the same specification, and the same Headless backend, entered in deliberate sequence. Compliance falls out as a by-product, not a separate product line.

The deeper reason for the portfolio: standards win slowly, and each head shortens the curve. Every head onboards a specific cohort straight into the federation: SMEs, customs and insurers, researchers, regulators, emergency agencies. Commercial traction and standard adoption become the same motion seen from two layers. Two clocks run at once, the commercial layer on startup cycles and the standard on the category horizon, and they compound in one direction: every subscription is an emitter joining the federation. One head is a proof point; the whole portfolio is what makes the long horizon tractable, not aspirational.

The sequence matters. The long tail does the infrastructure work that makes the premium end of the market possible. The enterprise customer does not build the commons; the solopreneur does. By the time a brand wants to make verifiable claims about its supply chain, the records are already there, contributed by the producers they buy from. That is the asset.

Early makers are also welcome. If you practise a craft and want to seed the commons and document your techniques in OPG-L, write to [email protected]. Founding-contributor credit will carry into the Foundation when it forms.