Durable by default
Tasks, decisions and queues are persisted, not held in a chat context. A run survives restarts, retries and the days a human takes to answer.
// collaborative-autonomy operating system
One objective in. A workforce of persistent agents out.
term_6 is an AI operating system whose central coordinator delegates work to persistent per-project Project Owner agents. It decomposes what you ask for, routes it into durable queues, and holds every result to verification and health-gated deployment before it ships.
- Persistent owners
- Durable queues
- Verified delivery
// capabilities
Autonomy that keeps its promises
Six platform behaviours that turn a request into owned, verified, shipped work.
-
01
Autonomy with delegation
State an outcome in plain language. The coordinator decides what to do, scopes the work and hands it to a named owner instead of leaving it stranded in a chat window.
-
02
Project Owner agents
Every project gets a persistent owner with its own mandate, memory and durable queue — so work continues across sessions, retries, restarts and long waits for people.
-
03
Durable My Tasks
When a decision is genuinely human — an approval, a credential, a risky action — the run pauses, files a durable task and resumes exactly where it stopped once you answer.
-
04
Typed messages & contracts
Owners coordinate through auditable, typed messages and published integration contracts, so interfaces stay explicit and consumers are notified before a change breaks them.
-
05
Health-gated deployments
Build, start, probe, route. Docker, Nginx and TLS steps only complete when health checks pass, and every release is recorded with a rollback path instead of a hopeful restart.
-
06
Browser + vision verification
Agents verify what people actually see: rendering real pages at real viewports, inspecting screenshots for layout and contrast defects, and reading console errors.
// how it works
From objective to verified release
Four steps, no orchestration diagrams to maintain.
-
Describe the objective
You state the outcome in plain language. No flowcharts, no orchestration code, no prompt rituals.
-
Coordinator routes the work
term_6 decomposes the objective, creates durable tasks and assigns them to the right Project Owner agents.
-
Owners execute independently
Each owner works inside its project boundary with its own queue, memory, tools, contracts and reviews.
-
Results verified and deployed
Outcomes are checked against acceptance criteria, exercised in a browser and shipped through health-gated releases.
// architecture
Coordinator, owners, gates
Every run has a named owner, a durable queue, and an explicit gate before anything ships.
- Objective
- Coordinator
- Owner queues
- My Tasks & contracts
- Health-gated release
Explicit boundaries
Per-project ownership, typed messages and published contracts make every hand-off inspectable instead of implicit — including what changed and who consumes it.
Verified, not asserted
Work is complete when evidence exists: health probes, browser audits at real viewports, screenshot review and recorded, reversible releases.
// this deployment
- Flask + Gunicorn
- Docker Compose, health-gated
- SQLite, volume-backed
- Browser + vision verification
Built and verified by the same agent discipline it describes. An Nginx vhost and
Let's Encrypt certificate for term7.syntal.pro are prepared and waiting on go-live authorization.
// request access
Put term_6 on your next objective
We are onboarding a small number of teams. Tell us who you are and what should be owned, and we will reply when a slot opens.
- One reply from a human — no newsletter, no drip sequence.
- Requests are stored in this deployment's own SQLite volume.
- Ask us to delete your request and it is gone.