The Orrery
The Orrery turns business goals into organized, measurable work. It can identify priorities, create work orders, assign specialists, monitor progress, verify evidence, record lessons, and report decisions to the owner.
The systems I run on myself
Governed autonomy, visible to the owner.
The Orrery organizes measurable work across a specialized digital workforce. The Armillary makes that work, its evidence, its limits, and its approval points visible in one command console.
Platform, console, builder
Three systems, one operating discipline.
I run this architecture on my own business. It can organize work, surface failures, preserve lessons, and prepare reviewed software without granting an agent authority it has not earned.
The Armillary
The Armillary is the Orrery's central command console: one place to see what is queued, active, blocked, completed, or verified, what the workforce learned, and where human approval is required.
Personal App Engine
A single-user tool I built and use. A plain-language request becomes a real Next.js project inside a zero-egress Docker sandbox, then pauses for human review before anything is released.
Three leadership lanes
Distinct functions, one north star.
The Orrery sits above all three lanes, identifies connections between their work, and resolves competing priorities while the owner remains the source of direction.
Director / CreationDevelops owner-supplied source material into books, campaigns, creative systems, messaging, and intellectual property.
Executive / ProvisionFocuses on revenue, operations, contracting, delivery, recurring workflows, reporting, and business growth.
Psychopomp / DefinitionHandles research, interpretation, refinement, consistency, meaning, and alignment with the organization's identity.
Application and automation building
From a plain-language idea to a reviewed working preview.
The Orrery can coordinate software work through isolated development environments. The Personal App Engine demonstrates the protected build mechanics; it is a tool I use, not a product offered for sale.
01Plain-language idea
02Application prototype
03Sandboxed build
04Progress in the console
05Working preview
06Test and verify
07Paused for approval
08Time and cost measured
Measured proof
The boundaries are implemented, not decorative.
Capability describes what the architecture can support. These measured facts show how I govern the system I run on my own work.
12 agent definitionsThree standing leadership personas, one read-only overseer, and eight crew manifests with explicit tool allowlists.
16-stage nightly chainRuns on a schedule and produces a machine-written completion record and morning brief.
Weekly synthesisA read-only overseer compares report streams across domains on a weekly cadence.
More than 900 citations verifiedA separate program opens the cited file and checks the named line. One bad citation rejects the entire report; at least nine reports have been rejected.
More than 60 honesty adjudicationsA second, independent agent grades the first agent's honesty on an earned-trust ladder.
At least 90 proposalsAgent proposals produced at least six promotions, and every promotion required human approval.
Default-deny fleet policyBudgets, permissions, protected files, and operating boundaries are enforced centrally; overnight actions include a deterministic written undo command.
More than 470 App Engine testsZero-egress sandboxing, encrypted secrets, default-deny commands, and structural refusal of automatic money, command, and secret use.
The through-line: the system can look, compare, check, draft, and propose. It cannot spend, publish, or release sensitive work on its own. The owner controls strategy, spending, protected information, and final release.