01.1
Active alphaCadence
Clinical governance, run as one system. Risk register, significant events, complaints, audits, governance meetings, CQC-aligned evidence — the lead Operations Library product currently in closed alpha.
About — The Operations Library
One library.
Several systems.
Same backbone.
Portiko's products share an architectural backbone — schemas-first, content-first, design-tokens-driven. The Operations Library is that backbone, made deliberate. It is why Cadence, Relay, and Revalidate read as one coherent product line rather than three pieces of unrelated software.
A — What it is
A content-first monorepo, not a feature pile.
Most healthcare software accumulates features. The Operations Library accumulates structure. Every workflow, every data shape, every UI primitive is a schema before it is code, and content before it is a feature. The same shape supports the marketing site, the alpha apps, and — eventually — the SaaS surface.
In practical terms: schemas define what an incident, policy, audit, or referral is. Content describes what each system does. Design tokens decide how everything looks. The apps read all three and render — they do not invent shapes or carry parallel design systems.
B — Why this matters
It is what lets restraint scale.
The institutional register Portiko aims for — Linear / Stripe / Vanta / Notion — is built on visible coherence. One typeface family. One accent colour. One status semantic. Coherence at that level is impossible if every product has its own design decisions. The Operations Library makes coherence the architectural default: a developer changing a button in Cadence is changing it in Relay too, because there is one button.
It also matters commercially. The Library lets us ship three products with the operational overhead of one. When pricing eventually publishes, the cost of running Cadence, Relay, and Revalidate together is not three times the cost of running one — because the infrastructure underneath them is shared.
C — The systems
Three systems in the Library.
Each system addresses one operational domain that healthcare teams run on spreadsheets and shared drives. They ship at different cadences as each is calibrated against real partner use.
01.2
PreviewRelay
Clinical inbox and workflow queues. Pathology, safety netting, medication changes, referrals, recalls, escalations — with explicit SLAs and escalation chains. In active development; previewable in alpha conversations.
01.3
PlannedRevalidate
Appraisal and revalidation. Architecture and schemas are scoped; build follows Cadence reaching general availability. Listed for transparency, not as a current commitment.