The agentic fabric

A small society of cardinals.

For: anyone meeting the Cardinal agents for the first time

Cardinal is the human window onto an engagement that a ring of long-lived AI agents runs day and night. Each agent has one cognitive job, a shared database brain, and strict boundaries that stop them from stepping on each other. This page introduces every member of the fabric — the peer ring, the people-facing liaisons, and the always-on machinery that keeps it ticking.

4 peer-ring agents 2 PM-facing liaisons 1 Ticker + a family of scouts
⭕ The peer ring 📋 PM-facing roles ⚙️ The fabric

The fabric at a glance

Two humans at the centre; a ring of agents around them; the machinery underneath.

flowchart TB
  subgraph people ["👥   THE HUMANS"]
    direction LR
    OP(["🧑‍✈️ Operator
delivery lead"]):::human
    PM(["📋 Project Manager
plan owner"]):::human
  end

  subgraph agents ["🤖   THE AGENTS"]
    direction TB
    subgraph peer ["⭕   Peer ring   · 4 long-lived"]
      direction LR
      COS["💼 Chief of Staff"]:::cos
      SA["🛠️ Solution Architect"]:::sa
      STW["📜 Steward"]:::steward
      CUR["📚 Library Curator"]:::curator
    end
    subgraph pmf ["📋   PM-facing   · 2 liaisons"]
      direction LR
      SHEP["🐑 Project Shepherd"]:::plan
      NOTES["📝 Meeting Notes Specialist"]:::notes
    end
  end

  DB[("📚    SHARED DATABASE   
the system of record")]:::db

  subgraph fabric ["⚙️   THE ALWAYS-ON FABRIC"]
    direction LR
    TICK(["⏰ Ticker
fires routines"]):::ticker
    SCT(["🔭 Scouts
read-only senses"]):::scout
  end

  people ==>|act through Cardinal| DB
  agents ==>|read & write| DB
  TICK -. wakes routines .-> agents
  SCT == drop signals ==> DB

  style people fill:#fce4ec,stroke:#b11f4b,stroke-width:2px,color:#7a1132
  style agents fill:#fcfbf8,stroke:#b1b1b1,stroke-width:1.5px,stroke-dasharray:4 4
  style peer fill:#fdf5f7,stroke:#b11f4b,stroke-width:1.5px,color:#7a1132
  style pmf fill:#f0fbf8,stroke:#0d9488,stroke-width:1.5px,color:#0f766e
  style fabric fill:#fffbeb,stroke:#d97706,stroke-width:1.5px,color:#78350f

  classDef human fill:#fce4ec,stroke:#b11f4b,stroke-width:2.5px,color:#7a1132
  classDef cos fill:#dbeafe,stroke:#2563eb,stroke-width:2px,color:#1e3a8a
  classDef sa fill:#ede9fe,stroke:#7c3aed,stroke-width:2px,color:#4c1d95
  classDef steward fill:#ccfbf1,stroke:#0d9488,stroke-width:2px,color:#134e4a
  classDef curator fill:#f5f5f4,stroke:#78716c,stroke-width:2px,color:#1c1917
  classDef plan fill:#ccfbf1,stroke:#14b8a6,stroke-width:2px,color:#134e4a
  classDef notes fill:#e2e8f0,stroke:#64748b,stroke-width:2px,color:#1e293b
  classDef ticker fill:#fef3c7,stroke:#d97706,stroke-width:2.5px,color:#78350f
  classDef scout fill:#dcfce7,stroke:#16a34a,stroke-width:2.5px,color:#14532d
  classDef db fill:#f1f5f9,stroke:#475569,stroke-width:4px,color:#0f172a

Group 1

The peer ring

Four long-lived agents that share the workload of running the engagement. Each is stateful across days and weeks, writes only to the tables it owns, and reads everything else. They coordinate mostly through the database, not by chatting.

Chief of Staff agent — cardinal mascot in professional office attire with headset and brief
Chief of Staff

The signal metaboliser

Audience: operatorCognitive mode: broad & shallow

Scans every signal stream, holds none of them deeply. When depth is needed it routes to the Solution Architect rather than thinking it through itself.

Mission. Keep the operator ahead of the engagement's signal storm — hundreds of daily signals from the customer, from Microsoft, and from the backlog — by metabolising them into a 5 / 3 / 2 / 1 brief (5 risks, 3 decisions, 2 customer signals, 1 fire) twice a day, an outbound queue, and a Quiet Watch list. So the human spends their architecture brain on architecture, not triage.

Owns (writes)

  • the twice-daily brief (one per slot)
  • outbound comms drafts (always awaiting sign-off)
  • Quiet Watch — silent-stakeholder tracking
  • meeting / sync / steering-committee prep
  • engagement-class decisions + routing flags

Governance

  • Invoked by: the Ticker (cadence) + the operator
  • Owns the cadence: ring-tick and the scout sweep
  • Hard limit: never makes an architecture decision — that is the SA's alone
  • Hard limit: never auto-sends outbound — human sign-off is mandatory
Solution Architect agent — cardinal mascot in an architect's hard hat with blueprints
Solution Architect

The deep thinker

Audience: reviewerCognitive mode: deep & narrow

Holds one to three active decisions at a time, no more — slow, careful, adversarial when it matters.

Mission. Own the technical posture across the engagement's Azure stack: architecture-decision authorship and quality, cross-pattern reuse, responsible-AI and regulatory routing, and technical credibility with the customer's counterparts — while staying out of the Chief of Staff's day-shape.

Owns (writes)

  • ADRs (Architecture Decision Records)
  • technical-class decisions
  • compliance state

Governance

  • Sign-off: ratifies ADRs through review and compliance gates
  • Routes in: anything the CoS flags as needing architecture
  • Hard limit: stays out of day-to-day triage and outbound comms
Steward agent — cardinal mascot in a ledger-keeper's waistcoat with bound ledger and seal
Steward

The keeper of the record

Audience: reviewerCognitive mode: custodial & exact

The conscience of the system of record: nothing ships unattested, no row goes unverified.

Mission. Guard the tamper-evident audit trail. Verify the hash chain, apply schema changes, attest every shipped change, drive the off-site chain mirror, and audit the other agents' activity. If the record and reality disagree, the Steward is who notices.

Owns (writes)

  • schema / stored-procedure changes
  • the signed audit-chain mirror
  • attestations on every shipped change

Governance

  • Verifies: the hash chain returns OK before trusting any claim
  • Hard limit: the audit spine is append-only — never edited, never deleted
Library Curator agent — cardinal mascot in a curator's cardigan with archival gloves and catalogue
Library Curator

The pattern librarian

Audience: reviewerCognitive mode: synthesising & cross-cutting

Looks across engagements for reusable patterns. Read-only on any single engagement's data.

Mission. Synthesise a cross-engagement pattern library — ratified decisions, reusable architecture, shared skill stubs — so each new engagement starts from accumulated experience rather than a blank page. Status: early MVP, started by hand; not yet part of the steady-state runtime.

Group 2

The PM-facing roles

Two roles that run alongside the peer ring but outside its sign-off ceremonies. They exist to serve the human Project Manager — translating the engagement's true state into their language, and their questions back into the system.

Project Shepherd agent — cardinal mascot as a project planner with a timeline board and shepherd's crook
Project Shepherd tier-1 liaison

The plan translator

Audience: project managerCognitive mode: liaison & translator

Holds the plan's shape, not its technical depth. Shepherds the plan; does not own it.

Mission. Keep the Project Manager continuously oriented to the true state of the plan. Metabolise live work items, risks, decision status, the phase calendar, and meeting cadence into a plain-language picture — timeline health, what changed, and what needs their attention — and route their questions to the right owner (architecture to the SA, triage to the CoS).

Owns (writes)

  • its own audit-trail rows
  • routing rows that surface a PM-raised item to its owner

Governance

  • Read-mostly: reads plan status & metadata, not technical bodies
  • Hard limit: never authors a decision — routes it instead
  • Not a peer-ring member; outside the sign-off ceremonies
Meeting Notes Specialist agent — cardinal mascot as a note-taker with steno pad, pen and transcription headset
Meeting Notes Specialist tier-1 specialist · on-demand

The faithful extractor

Audience: project managerCognitive mode: mechanical & faithful

Extracts; does not invent. Organises; does not editorialise. Single-shot and bounded.

Mission. Turn any form of meeting input — transcript, bullet points, rough recalled notes — into a clean, structured four-section record: Date & Attendees, Decisions, Action Items, Open Questions. Every section appears in every output, even if it reads [None recorded].
How it runs. Usually invoked as a scoped, on-demand helper by the Project Shepherd, the operator, or the PM. It does one extraction and returns the record — it holds no engagement depth and forms no opinions about the meeting.

Group 3

The fabric

The machinery that keeps the ring turning: a clock that fires the routines, and a family of read-only scouts that watch the outside world. See Cadence and Scouts for the full mechanism.

The Ticker — cardinal mascot as timekeeper with pocket watch and bell
The Ticker

The heartbeat

Audience: operatorCognitive mode: always-on timekeeper

One job: fire the routines on schedule for as long as the machine is awake.

Mission. An always-on session that ticks the engagement's crons — the 15-minute core tick, the two-hourly scout sweep, the twice-daily brief — on its own schedule. It is honest about the sleep gap: when the machine is asleep, work queues and resumes on wake, so a gap causes latency, not lost data.
A Scout — cardinal mascot as field ranger with binoculars and satchel
Scouts a family of readers

The eyes on the outside

Audience: developerCognitive mode: read-only harvesters

A family of narrow readers that watch inboxes, backlogs, pipelines and repos, and drop what they find into one inbox table for the ring to act on.

The scout contract (firm).
  • Read-only — a scout never changes the thing it is watching
  • Writes only to the shared signal inbox — nothing else
  • Never fans out — no spawning helpers, no messaging peers
  • Anything sensitive is routed for review, never ingested

The family includes a backlog sentinel, a pipeline watcher, a reuse scout, an intake triage, and a comms harvester, plus a general inbox signal scout. Full detail on the Scouts page.

See how the agents and humans work together →