01 · Recent releases13 entries
- 2026-06-07v0.15
ProofSeal — verifiable supplier credentials, running as a prototype.
- Issue a credential, verify it in a single scan, revoke it on demand — each one signed and chained into the same ledger everything else writes to.
- Filed into a federal testing stream as a working artifact, shown in live operation rather than described on a slide.
- No separate trust product — provenance the platform already carries, surfaced for procurement.
- 2026-06-05v0.14
Escalations that reach a real desk.
- Operator escalations now persist to a durable inbox and land in another account — not a session memory that forgets on reload.
- Step-up authentication tightened: protected surfaces stay dark until clearance is confirmed, never a flash before the gate.
- Page-by-page sweep across the platform — every action wired to a real path, the assistant rebuilt to answer instead of echo.
- 2026-06-02v0.13
Federal procurement — clarification round answered.
- Follow-up questions on the automation RFI we filed in May, returned inside the deadline window.
- Ontology framing and agent posture refined against evaluator language without losing the original voice.
- Substrate behaved exactly as documented through the round-trip.
- 2026-05-30v0.12
Deal-close kit — pricing surface and pilot SOW.
- ROI calculator on /pricing; inputs land in the same ledger a live tenant writes to.
- One-page pilot SOW for buyers who would rather read paper than a deck.
- Both surfaces sat under two live procurement conversations the week they shipped.
- 2026-05-25v0.11
Defence research call — full submission filed.
- Multi-modal proposal into a Canadian defence research program, submitted from the same ledger tenants run on.
- Every claim in the document came with its lineage attached — no separate evidence appendix.
- Taygeta surfaced as the working artifact, not a slide.
- 2026-05-23v0.10
Taygeta — TRL-7 sweep.
- Forty-six structural fixes landed across the defence stack in a single week.
- Authority checks, mutation idempotency, server-side hash-chain verifier — wired end to end.
- Audit replay can now reconstruct an entity body from the chain alone.
- 2026-05-20v0.9
Substrate sprint — entity persistence and connector ingest.
- Entities persist through the ledger, not just runtime memory.
- /api/connectors/ingest accepts envelopes from any registered source with content-hash verification.
- Vision and voice endpoints wired — image evidence in, Whisper transcription out.
- 2026-05-19v0.8
Two research papers published.
- Policy-by-Proof — every agent action carries its proof packet before execution.
- The Living Ontology — operational schemas that evolve under HITL governance, not frozen at release time.
- Both papers are in /research with full abstracts.
- 2026-05-15v0.7
Lineage Graph primitive shipped to homepage.
- Recurring visual primitive renders the full signal → reasoning → action → proof chain.
- Reused on /platform anatomy section and decision cards inside the app.
- Provenance metadata visible on hover, no extra page needed.
- 2026-05-12v0.6
SolutionShell rebuilt against the locked design system.
- All industry surfaces (defence, healthcare, energy, finance) now share one shell.
- Anchored eyebrows on every section, single ink, single signal cyan.
- Dark hero retired in favour of the off-white substrate look.
- 2026-05-08v0.5
Policy-by-Proof substrate ledger migration completed.
- Every action signed and chained — replayable forensics inherited end-to-end.
- Migration from prior decisions ledger preserved 100% of historical entries.
- Tenanted by jurisdiction and clearance level on day one.
- 2026-05-05v0.4
MAIA Intelligence Inc. filed in Ontario.
- Federal incorporation completed; Ontario-headquartered with Toronto registered office.
- Bid prime entity established for government contracts.
- Founder structure and ownership recorded — 100% Canadian-owned.
- 2026-04-28v0.3
Connectors page shipped — typed actions across five system classes.
- ITSM, ERP, operations, identity, and data-warehouse families wired.
- Quiet ink wordmarks, no native brand colours — replace none, cross all.
- Round-tripped state with the source systems, not a parallel write.
02 · How releases workSemantic · Signed · Replayable
Every release lands in the same ledger your tenant runs on.
Releases follow typed semantic versioning. Every entry above is signed in the cryptographic ledger that backs customer tenants — the same audit metadata, the same chain, the same replay path. Nothing about a release is informal.