Cairn

The thread, held.

Cairn is the operations system we built for ourselves — a personal memory store wired to a team of fourteen named agents. It's how James cut his working week at sheepCRM from five days to three, without anything slipping.

If "agent-augmented operations" reads like marketing, this is the working evidence. If you're thinking about what something like this could mean for your team, get in touch.

Three primitives, one loop.

Stones

Every fact, decision, person, source, project — typed and addressable. They grow edges between each other. Sensitivity-tiered, audit-friendly, owned and inspectable.

Roles

Fourteen agents on rotating schedules — error triage every 90 minutes, research watchlist twice a week, finance health daily. Each one a single page of prompt and a small config.

Dossier

The UI is a single editorial column. No dashboards. No widgets. Decisions get a kicker, a Fraunces headline, options as picks, and a verdict bar that slides up when you commit.

The loop, in four moves.

The team scans the world

Cloud Canary errors, Linear issues, calendars, customer support inboxes, market signals, the cairn corpus itself. Each role reads only what its job demands — no general-purpose snooping.

They write stones

Findings become typed memory: a thought, a decision request, a tension, a project update. Stones grow edges to other stones automatically — provenance is a graph, not a footnote.

Chief of Staff triages

She closes duplicates and noise, batches the rest, and surfaces a small handful of calls. Three roll-calls a day check that every team member is still operating per their schedule.

James decides

Approve, reject, defer, or annotate. Decisions become resolutions; resolutions become Linear tasks. Tomorrow the team picks up the next layer. The thread never drops.

The questions you were going to ask.

Can we get access?

Cairn is in closed beta. Right now there's one operator and a team of fourteen agents — that's the working demonstration. If you'd like to explore agent-augmented operations for your team, or want Croftsware to build something similar, get in touch.

What's actually changed in practice?

James's working week at sheepCRM dropped from five days to three with the team in the loop — error triage, financial health checks, customer intelligence, security audits, research watchlists, communications drafts, strategy briefings. Same operational footprint, two days back. The agents don't replace people; they hold the thread when there isn't one to spare.

How is this different from Claude, Claude Code, or other agent assistants?

Cairn isn't a generalist. The fourteen roles each have a one-page prompt, a fixed schedule, and a job description — none of them are asked to "help with anything." They scan the world they were assigned to, write structured stones into a typed knowledge graph, and leave the rest alone. The graph is what compounds: every stone has provenance via edges, sensitivity tiers, and an audit trail. Generalist chatbots don't accumulate this kind of memory; cairn does.

What about security?

Three things. (1) No agent has direct egress — outbound actions like email, calendar invites, or document publishing live in purpose-built Lambda sorties with no agent-callable interface. (2) Postgres row-level security enforces three sensitivity tiers (normal / sensitive / secret) at the database, not just at the tool layer. (3) The lethal-trifecta principle is structural — no single agent has read-access to untrusted content, write-access to private data, and external egress at the same time. Each agent's capabilities are explicit and minimal.

The thread, held.

Named, characterful, on rotation.