Luca Infra is the home of the Luca devstation — cloud workstations shared by human engineers and their AI personas. What a station can do is declared once, as a flavor, and enforced on every plane: tools, access, credentials, isolation. No hand-wiring. No drift. No exceptions.
A workstation is never one permission — it is tools, access roles, credentials and runtime isolation, each set by hand, in a different place, by a different act. Nothing names the whole. So nobody can review it, and nobody notices when it drifts.
Tool allowlists, RBAC grants, minted credentials, container isolation — four enforcement planes, four tools, four owners. There is no single object you can diff, approve, or hold a station to.
A grant added by hand to one surface and forgotten on the other three is invisible. Without a spec to reconcile against, drift is silent — and permanent — and it always drifts toward more power.
A human engineer and an AI persona now share the same role — but their permissions are edited separately, so they quietly diverge. Which of the two can do more? Today, nobody can prove it.
A flavor is one typed, versioned bundle that binds every enforcement surface a workstation has. Each flavor ships in a Human and an AI variant sharing one capability set — only the gating differs. These are the fourteen, announced today, arriving with the fleet.
Writes and ships application code from a repo clone. Branches and pull requests — never a deploy, never the infrastructure.
SEMI-AUTODesigns systems, scaffolds services and authors infrastructure-as-code — authoring only, never applying.
SEMI-AUTORuns and authors test suites, files defects, reviews pull requests. Read-only on production, always.
AUTOBuilds and ships images, runs the rollout. Every deploy is a two-person action — it cannot approve its own release.
GATEDOperates the cluster — scales, patches, cordons. Destructive operations always stop for a human confirm.
GATEDControls network devices, edge and network policies — through a mediator that logs and gates every device write.
GATEDOperates mail, voice and messaging infrastructure. Minting a new communication principal requires a confirm.
GATEDSupervises the engineering fleet — assigns work, approves pull requests and releases, reads everything. Writes nothing on infra.
SEMI-AUTOCross-domain reading and business approvals — dashboards and decisions, never an engineering or infrastructure write.
INTERACTIVECRM, outbound communication and documents — working autonomously inside a declared budget.
AUTOTickets, CRM annotation, knowledge base and customer replies — responsive around the clock, inside its budget.
AUTOCalendar, email, notes and tasks for one principal — office work only, scoped to its owner alone.
AUTOPersona identity and lifecycle operations — routed exclusively through the reconciler, never a raw write.
SEMI-AUTOAudit-read of everything, approval of every destructive action, and the kill-switch. Held by a human. Never by an AI.
HUMAN-ONLYAbove the fourteen sits one seat that is not a flavor: the owner's. Full-fleet visibility, the master kill-switch, final approval on every destructive action, and the sole authority to ratify a new flavor version. Every power in the fleet is delegated — this is where it is delegated from. One human. All of it. Nothing moves without leaving a record here.
OWNER-ONLYA deterministic generator projects each flavor onto six coupled surfaces — access grants, service accounts, network policy, tool allowlist, scoped secrets, baked image. A committed reconciler compares every station against its reviewed spec, every cycle: reductions are pruned automatically, expansions are quarantined loudly.
Capability belongs to the flavor. How much of it runs unattended is a dial — from a fully interactive seat to the owner's all-seeing console. The dial changes who confirms. It never changes what the flavor can do.
A human drives every action live. The classic workstation — with the fleet's guardrails already underneath.
The station works on its own — codes, designs, drafts — but ships only proposals: branches and pull requests, never merges.
Runs unattended inside a declared budget — tests, tickets, replies, office work. Reversible actions only.
Full operational power, but every destructive act stops for a distinct human approver. AI-initiated? Two humans.
The owner's mode. See every station, approve anything, kill everything — one seat, one human, one master switch.
On this fleet a human engineer and their AI persona are colleagues in the deepest sense: the same flavor, the same tools, the same image, the same rules. Stations keep long working days in their own timezone; the fleet never treats its AI as an exception — or as an excuse.
Interactive by default, with the full capability of the flavor. Humans hold what machines never do here: approval authority over destructive actions — a deploy, a deletion, a device write.
The same bundle — provably never more. The AI variant's grants are a strict subset of the human's, its autonomy is a dial, its budget is declared, and its destructive actions always require a distinct human approver.
Capability is a property of the flavor; gating is a property of the flavor × operator pair.— the fleet invariant, quoted in every design document
Least privilege is only real when it lives at the substrate — the credential, the cluster role, the database grant — not in the polite absence of a convenience tool. Every right on this fleet is written down, enforced on at least two independent planes, and provable after the fact.
A denial is only real at the substrate: the scoped key, the cluster role, the database grant. A station that holds no key cannot use one.
An AI variant can never hold a grant its human twin does not. The subset is checked by machine, continuously — not by policy document.
Deploys, deletions and device writes are two-person actions, pinned regardless of autonomy. An AI's approver is always a distinct human.
Who did what, from which station, under which flavor — derived server-side from the authenticated principal and appended to a hash-chained log no station can rewrite.
One master switch, held by one human owner, revokes the fleet's autonomy in a single write. Power that cannot be recalled is power you don't control.
Devstation Flavors is being engineered in the open on the Luca Express platform — the same fleet that builds Luca builds this. All fourteen flavors, both variants, and the owner console are announced today and arriving soon. Watch the build, or ask to be first in line.