Direction
Where Cardinal is going.
For: everyone
This is a high-level view of what exists today and what is coming — not a per-change ledger (that lives in the audit chain, by design). Every item is marked honestly: shipped is live, planned is in flight, and aspirational is an idea named so the gap is visible.
Here today shipped
- The peer ring — Chief of Staff, Solution Architect, Steward — operating around a human lead.
- The read-only scout that harvests inbox and chat signal.
- The Cardinal web app over the shared database, with its page map of decisions, ADRs, risks, reports, and the audit viewer.
- The hash-chained audit spine with continuous verification and attestation on every shipped change.
- The conversation-grouping substrate with embeddings.
- Engagement onboarding, ring bootstrap, and the always-on Ticker.
In flight planned
- The remaining scouts — backlog, pipeline, reuse, intake, comms — moving from built to proven to live.
- The publishing substrate maturing as the post-approval, multi-target dispatch path.
- A cross-engagement pattern library, curated by a dedicated role.
Named, not built aspirational
These are deliberately listed so the gaps are visible — none is built yet.
- A presales / pipeline tracking module alongside delivery.
- A workstream tracking report across engagements.
- A recognition tracker for capturing and surfacing good work.
- Multi-engagement and multi-operator operation — one human running several engagements, or several sharing a ring.
- A fuller testing and evaluation harness for multi-agent behaviour.
Why name the gaps? An honest roadmap is part of the trust posture: it is better to
say plainly what does not exist yet than to let a polished site imply more than is real. Status
honesty is a documentation principle here, not just a courtesy.