Underneath every GoldenI product is one operating substrate — CORE. This is the short version; the deep one lives at core.golden-i.io.
Operators stay here. Technical builders click through to CORE for the architecture in depth.
Three-layer identity resolution and a universal patient ID across every product.
Consent-governed access, enforced at read time as a live decision — not a stored copy.
Append-only, immutable event capture. Who knew what, when, replayable forever.
Five governed channels. Every prompt, output, and source event captured and attributable.
Protocols evaluated in real time at the point of care. Guidance, never hard stops.
Each class of event anchors on its own blockchain subnet. A breach of one reveals nothing about the others.
Who someone is — resolved to a universal patient ID, anchored apart from any clinical fact.
What happened in care — immutable, time-ordered, never joined to identity at rest.
Who saw what, under which consent, governed by which protocol — itself anchored.
When a clinician closes a visit in CURIS, the same events draft the claim in REMITUS, update the registry, and anchor the audit trail — because all of it reads and writes one event shape on CORE.
That is why a claim can cite the exact protocol event that authorized it, years later, on demand. The product is the surface. The substrate is the advantage.
Read the full CORE architecture →If you're evaluating whether to build on GoldenI rather than from scratch, the technical surface is core.golden-i.io — the deepest documentation of the substrate we publish.