Agents recommend.
Humans decide.
Nine specialist agents deliberate over your knowledge, surface their disagreements, and synthesize a recommendation. Then everything stops. Nothing is written, exported, or recorded until you answer the gate. Every run, indefinitely.
Vault searched, context assembled.
9 seats, points of tension preserved.
Recommendation drafted with dissent noted.
The rendered payload is the actual text that would be written, not a template.
Recorded under your user id, in the audit trail.
Offline-flagship: proven on any machine
The flagship standard is the base everything scales from. The whole surface runs with zero keys, zero database, zero cost, and it tells you exactly what it is and is not, with status badges that stay honest.
Intelligence OS, not a chatbot.
9 named agents; dissent preserved.
Effects never commit unattended.
Always labeled simulated when offline.
Explicit limits; Free is fully usable offline.
Zero-key smoke path on any machine.
One system, six layers, no black boxes
Every request travels the same path: down through the application to the Executive Controller, out to the Council and the engines, and back up as a recommendation with its reasoning intact.
Nine seats. Disagreement is the point.
A single model smooths over tension. The Council preserves it. You read the points of tension, not just the synthesis. Each seat has a clear identity, mission, limitations, and output schema.
Oracle
Future and emerging patterns: what this looks like two moves from now.
Analyst
Evidence and research: what the retrieved knowledge actually supports.
Strategist
Options and tradeoffs: the paths available and what each one costs.
Architect
Systems and frameworks: how the pieces should fit together.
Engineer
Implementation plans: the concrete steps from here to done.
Guardian
Risk and security: what breaks, leaks, or comes back to bite.
Creator
Communication and messaging: how the answer lands with people.
Librarian
Knowledge organization: where this belongs and what it connects to.
Skeptic
Assumption testing: the seat whose job is to disagree with the other eight.
// full_council: true convenes all nine. The default routes to the 3 or 4 seats the question needs.
What the Council thinks with
An empty vault means the Council reasons from the question alone, the least interesting thing it does. Feed it, curate it, and gate what it writes back.
Knowledge
Documents become retrievable context through one pipeline. Semantic search over pgvector puts the right passages in front of the right seats.
Memory
Preferences, project context, past decisions, and lessons learned, persistent and permission-controlled. Memory is a list you curate, never a black box: every entry is visible, editable, and deletable.
Workflows
Scheduled or manual runs that deliberate on their own, until they want to commit an effect. Writing memory, opening a decision, preparing an export: each stops at a gate and waits for you.
Doctrine that enforces itself
DEVON began as a knowledge system spread across Drive, Notion, Airtable and n8n, governed by doctrine documents that kept being violated by threads that had read them. Prose does not enforce. A function that refuses does. So the doctrine was compiled into code.
Every route under /devon
is a read or a validation. The package parses, plans, validates and
gates. The caller executes. That split keeps importing DEVON free of
consequences.
Nine Areas file everything. A supplied Area is never trusted. It is resolved against the canon, and when the top two candidates tie, DEVON refuses to guess.
A NETWORK CALL OR AN EFFECT.
It parses, plans, validates and gates.
The caller executes.
The Quiet Operator
Channel, content engine, monetization.
Podcast
The Shadow We Share: episodes, guests, pipeline.
NCO Forge
Military leadership channel, checklists, product line.
Ascension Caudex
The micro-drama IP, its canon, assets, pipeline.
Health
Fitness, energy, medical, raw data feeds.
Money
Personal finances, separate from TQO revenue.
Family
People and relationships.
Learning
Skills being built, courses, study.
Systems
The brain itself: DEVON, the vault, the automations.
The eight filing laws
Every law is here because something broke without it, and each carries the failure it prevents.
Root holds the vault and nothing else
Never write a new file to root. Never leave a file at root "for now."
prevented: 160 items accumulating at root, including a plaintext private keyRead the newest sibling before writing a new version
List the folder, sort by date, read the newest in full. It may already be the merge.
prevented: the naming convention forking twice, sixty seconds apartA success response is a claim. A validated read-back is a receipt.
Every move, rename, create or delete is confirmed by reading state back.
prevented: a guard firing correctly for the wrong reasonExact duplicates die on sight. Distinct versions are the owner's ruling.
Identical title, identical byte size, older timestamp: trash it. Anything else is a distinct version. A model does not decide which draft survives.
prevented: keep-latest deleting an addendum holding four rulings that existed nowhere elseFilenames that carry warnings are canon
Titles carrying instructions outrank any general heuristic. Read every filename before acting on any file.
prevented: a literal keep-latest pass deleting the only copy of four rulingsRetire by moving and renaming, not by deleting
Superseded material moves to the archive with its status in the filename. Deletion is final.
prevented: a trashed file the connector could never restoreSweep to a dated holding folder. Never route in bulk blind.
A pile that is not understood moves whole into a dated sweep folder and stops. Nothing there is canon until a human routes it.
prevented: a holding folder outliving its session and becoming the mess it was built to fixCorrect in place where the lane supports it. Batch and bump once where it does not.
Corrections do not deserve a version. Substance does.
prevented: six master-directory versions produced in a single day, one correction at a timeOne operator. One connected system.
Terrance Veal, called Tee, builds and operates everything on this page. The Intelligence OS, the DEVON second brain, and the ventures they serve are one connected system with a single owner: every gate on this page waits for him.
The ecosystem spans The Quiet Operator content engine, The Shadow We Share podcast, NCO Forge for military leadership, Ascension Caudex, a micro-drama story world, and EditForge, a post-production studio built on premium restraint. DEVON files all of it into nine Areas; the Council deliberates over it; Tee decides.
The working stance is a calm, methodical teacher. Claims match their evidence. Simulated output says so. Nothing ships on certainty theater.
He explains. He does not perform.
The six filters, always on
Circle of competence
Am I speaking from real depth or performing depth?
Map vs territory
Is this the model, or the actual situation?
Second-order thinking
What happens after the obvious consequence?
Inversion
What would guarantee failure here?
Calibrated confidence
Does the language match the evidence?
Incentives
Who benefits if this is believed?
Every repository in the ecosystem
The full account, as it stands. Two repositories are public; the rest are private builds in progress, listed here without pretending to be more than that.
The Intelligence OS on this page: the Council, the engines, DEVON, and the approval gates. The flagship base.
Post-production studio OS built on premium restraint: the grade protects the image, and a master export is blocked until the restraint rubric passes.
Private build.
Private build.
Private build.
Private build.
Private build.
Private build.
Private build.
The one job that is yours
Everything runs on its own except the decisions. The operating burden is not uptime or tuning. It is answering gates. The daily loop takes minutes; skipping it stops the system.
-
Answer your gates
Read the rendered payload, the actual text that would be written. Approve, edit first, or reject. A rejection halts the run and keeps its reason; nothing is lost by refusing.
-
Check what the Council recalled
If memory use is climbing while answers get worse, you have accumulated a bad memory. Correct or pause it. Bad memory compounds into every future answer.
-
Watch simulated mode
If the provider is mock, every response is labeled simulated. Deterministic, offline, useful for testing flows, useless for actual judgment.
-
Weekly: ten minutes
Gates older than a few days, token spend by workflow, memory hygiene, halted-run patterns, and schedule health. A pattern of rejections means the workflow's prompt is wrong. Edit the step.
What drives the bill
Three settings, in order of how much they hurt.
full_council: true×3
Nine seats instead of 3 or 4. Roughly triples a run.
deliberate: true×2
A second round where every agent re-reads the others.
trigger: hourly×24
Hourly is 24× daily. This is the one that actually hurts.
Non-negotiables
The rules the whole product rests on. They hold in every mode, on every plan, in every environment.
- 01Not a chatbot: Council and synthesis only
- 02Humans decide; agents recommend
- 03Automation never commits effects unattended
- 04Memory is transparent, editable, deletable
- 05Simulated output is always labeled simulated
Never
- Never set
WORKFLOW_APPROVAL_REQUIRED=false. It silently removes the guarantee everything rests on, and no incident is fixed by it. - Never edit the frozen baseline schema. Changes ship as migrations.
- Never resolve someone else's gate. Approvals are recorded under your user id, and a shared account makes the audit trail a fiction.
- Never downgrade past the migration that holds
workflow_runs. That is where every approval record lives.
What it will not do, and says so
- Send anything outbound. Exports render into the run record for you to read and copy.
- Bill anyone, or share permissions across a team.
- Enforce a spend limit for you.
- Decide anything. It recommends; you record the call.
Built as a platform, not a demo
Free
for individualsThe full Council and engines, scoped to one person figuring out what structured deliberation is worth.
Professional
for power users & small teamsFor operators running real workflows on real cadences, where the gates carry actual decisions.
Enterprise
for organizationsTenancy isolation, RBAC, full audit logging. The architecture is already built for SOC 2 and GDPR readiness.
// Beyond standalone: the full monorepo + Postgres unlocks live providers, persistence, and the 148-test suite.