One repo per organisation. Machines only ever hold deployed copies.
Skills are what an agent knows. Automations are what runs on a schedule or a trigger. Workflows are the graphs a run pins a version of. Three different things, three different contracts, one home: a repository named for the organisation, and the Hub as its window.
Skills, automations, workflows. Not synonyms.
Skills
Markdown capability definitions: SKILL.md plus scripts, references and assets. Each declares its authority tier in its frontmatter. The repo is home. Hub Docs renders them as a locked space; unlock a page, edit it, and the save writes a commit back. Git is the referee, and the round-trip is byte-faithful: a one-word edit is a one-word diff.
Automations
Routines, scripts and workflows registered from a manifest: identity, scope, schedule, category, owner, spend cap. Every one is born switched off and locked. A person reads what it will do and clicks approve before the first run. A missed heartbeat is an alarm, not a silence.
Workflows
A directed acyclic graph with a stable identity separate from its drafts and versions. Every run pins one immutable version before it materialises jobs. No loops, conditions or sub-workflows in version one, on purpose.
The birth certificate. An automation isn't registered until it has all four.
Code
Its own top-level folder in the repo, with its own test.
Readme
What it does, in plain English, in the folder.
Manifest
Identity, scope, schedule, category, owner, spend cap. Consumed by the Hub's Automations section.
Approval
Born switched off. A human reads what it will do and approves before the first run.
Where things live: one home per fact
- Code and testsThe organisation's repo
- Skills (agent knowledge)The same repo, under skills/. Hub Docs shows a window
- Identity, scope, healthHub, the Automations registry
- Run history and outputsHub, linked to Projects, Inbox and Reports. Outputs never live in Automations
- SecretsThe machine's keychain or env. Never the repo
- Models, sandboxes, run dataThe machine that runs them. Not the repo
The Automations section, as ruled on 31 August.
- 01
A Library: tiles under three dividers (routines, scripts, workflows), a fixed category rail matching the task categories plus Ops, search, health dots, a lock on anything locked.
- 02
A detail page per automation: readme, granted scope, steps, review-by date (overdue goes amber), change history, activity log, outputs browser, and an Ask-AI menu.
- 03
An Activity tab: one feed over heartbeats, executor audit and run events, with an alerts filter and a badge count.
- 04
A silence alarm: no heartbeat inside twice the expected cadence writes an alarm row and turns the feed red. This is the fix for things breaking quietly.
- 05
Rehearsal mode: run with zero side effects, output staged for review.
- 06
Everything ships. The proposed trims were rejected. Iterate to working.
The registry is live behind its flag with the first automation ingested and awaiting a human's approve click. The Library still draws fixtures until the tables are registered in the store, and nothing yet receives the heartbeat POST. Both are open rows on the board.
One chain, end to end.
Transitory (a research digest) → transitory (copy in brand voice) → transitory (a page draft) → gate, reversible (a pull request approved, then published) → gate, fixed (a spend recommendation a human executes). The chain flows freely through the drafts and pauses exactly twice.
More docs
Architecture
The topology: four zones wired around one record, where agents run, and the four ways a worker is started.
Security
Row-level security as the whole authorisation story, the credential broker, the ten-check gate chain, and what has actually been made to fire.
The stack
Next.js, TypeScript, Supabase, Nango, Airbyte, n8n and Vercel: what each does, what's being rebuilt, and what a stranger needs to run it.
Data plane
How client data reaches Hub: Airbyte into a fenced landing zone, thin transforms, a freshness stamp on every number.
Automations & skills
The split: one repo per organisation, a birth certificate for every automation, skills whose home is git.
Status
The capability matrix, five labels, no hedging. What you could use this afternoon versus what needs a switch or a sitting.
Self-hosting
The clone manifest and the transfer sequence: what you stand up, what moves, what never leaves our custody.