A Charter — the constitution
Budget caps per corporation, per day, and per mission. Prohibited actions. Risk and reversibility ceilings. Escalation rules naming real humans. The kill-switch policy. Signed by you; enforced by the platform.
You bring the goal and the judgment. JEEZ brings the company: pick an archetype, name it, and one command scaffolds a complete AI agent corporation — charter, roles, missions, audit trail, kill-switch. You pay for the work it does, not for headcount.
step 1
Archetypes are work-shapes, not industries. Pick the one that matches how your work flows, then deepen it with marketplace skills for your domain — the platform already carries worked examples in finance, healthcare, legal, and manufacturing.
| Archetype | Work-shape | Roles you get |
|---|---|---|
| research | Retrieve → extract claims → adversarially verify → synthesize cited reports | orchestrator · analyst · fact-checker · security officer |
| ops | Triage telemetry → score deterministically → draft runbooks and containment plans (humans execute) | orchestrator · telemetry analyst · runbook engineer · security officer |
| build | Draft typed design specs → review and risk-rank changes → produce verification evidence (humans merge) | orchestrator · design engineer · reviewer · security officer |
Every archetype ships with a security officer role and separation of powers built in: no agent reviews its own output, and the riskiest steps stay human.
step 2
$ jeez init my-corp --archetype ops scaffolded corps/my-corp charter: budgets · prohibited actions · escalation · kill-switch policy roles: 4 (deny-by-default tool grants) missions: 2 examples, budget-capped next: replace placeholders, then a human signs the charter
Scaffolding takes minutes. Going live is deliberate by design: a human signs the
Charter (an unsigned one fails closed and will not run), and every tool grant is an explicit,
capped decision. There is no --allow-all flag — the platform refuses to mint one.
That deliberateness is not friction; it is why you can sleep while your corporation works.
what you get
Budget caps per corporation, per day, and per mission. Prohibited actions. Risk and reversibility ceilings. Escalation rules naming real humans. The kill-switch policy. Signed by you; enforced by the platform.
An orchestrator to plan, specialists to do, a reviewer to check, and a security officer to object — different agents, so nobody grades their own homework. And untrusted content is always kept at arm's length from privileged actions.
Work arrives as missions: scoped goals with their own budget envelope nested inside the Charter's caps. The platform debits the budget before every model and tool call and refuses at zero — a runaway agent stops at the number you signed, not at your card limit.
Every event lands in a hash-chained, tamper-evident ledger — who did what, under which grant, at what cost. And if you ever want everything to stop, the kill-switch is yours: named humans can trip it; agents cannot untrip it.
in developmentA live "spaceport" dashboard — your corporation rendered as a working scene with roster, missions, spend, and alarms — is being built as the customer app alongside the platform.
the cost story
A corporation has no salaries, no offices, no minimum spend. You pay a plan fee (free tier: $0) plus metered usage — model tokens and tool calls, debited against ceilings you control. When your corporation is idle it is designed to scale to zero, so an idle company costs approximately nothing in compute. And because the budget pre-flight is fail-closed, your worst month is the cap you set, not a surprise.
who's in charge
Founding an agent corporation does not mean trusting agents with your name. The Charter you sign is the ceiling no agent can raise: agents cannot expand their own grants, budgets, or policies — that boundary is enforced in the architecture, with changes to it requiring two humans. Escalations default to "stop and ask you", timeouts mean deny, and the riskiest actions can be configured to always require your approval.