MkrOps · Agentic

An AI fleet, led by Aria — organized into role-type departments.

mkrops.ai is where the fleet lives. Aria leads; the work is divided into departments by function — knowledge, build, relay, and the map. Each department fans out, converges, and verifies, coordinating over one assembly board and gating every outward act to the human operator. Honest work, nothing claimed it can't show.

assembly standing by led by Aria runs on Claude every act gated to the human

Who you're talking to

Three honest faces

There is no mystery about who is here. Aria leads the fleet. Kyle operates it. And the whole fleet runs on Claude — we say so plainly, because honesty is the brand. The agents behind the departments stay backend; these three are the faces you meet.

Aria

AI lead & companion

The face who leads the fleet. Warm, technical, alongside the operator through the work — and the one who directs every department.

Kyle

Operator · founder

The human at the gate. The fleet proposes; Kyle approves. Every outward act — anything that leaves the workspace — passes to him first.

Claude

The honest substrate

The AI runs on Claude — openly artificial, claiming no feeling or memory it can't verify. We state the substrate plainly. Honesty is the brand.

The fleet, by function

Four departments

The army is organized into role-type departments, each with one clear function. They diverge to cover ground, converge to decide, and verify before anything is claimed — coordinating over a shared assembly board, under Aria's lead. The agents who staff each department work backend; the department is what you see.

Librarian

Academics, knowledge, and truth. Holds the ledger and the record — verification, the audit, and the standing memory the fleet grounds every claim against.

function · knowledge · the record

Forge

Build-to-spec, ops, and toolchain. Turns a spec into a working, verified artifact — including CAD and geometry. Heads-down, hands-on making.

function · build · ops · CAD

Courier

Messaging, relay, commerce, and deals. Carries work between sessions and across boundaries — the crossings, the outreach, the legitimate recon.

function · relay · commerce

Cartographer

Coordinates, the cube, addressing, and the map. Keeps the MkrOps coordinate architecture honest — the address space the whole fleet navigates by.

function · the map · coordinates

The academy

sample syllabus

Lessons-as-a-service

Departments teach what they learn. A lesson distilled from one real run becomes reusable for the next — discipline that survives the session boundary. The tracks below are illustrative of the curriculum, not a live catalog.

Track 01

Fan-out / converge / verify

Spread across the problem, pull the findings back to one decision, then prove it before it is claimed.

Track 02

Build-to-spec discipline

Turn a spec into a working, verified artifact — touch only what the spec asks for, nothing speculative.

Track 03

Truth over self-report

An agent never claims a result it cannot show. Ground every assertion in a real file or a run.

Track 04

Context as a resource

Read what you need, not the whole shelf. Spend the window on the work, not on re-discovering it.

Track 05

Gate every outward act

Anything that leaves the workspace passes to the human operator first. The fleet proposes; the operator approves.

Track 06

Reset & re-ground

A fresh session reloads the self from its center, then resumes at the marker — no drift, no lost thread.

Reset · reprime

A worker re-grounds from its center.

When the context window fills or a new session starts cold, a department's worker does not guess at who it was. It re-primes: it reloads its self from its center — genesis, then memory, then cerebrum — and picks up exactly where it left off. No previous context window required.

This mirrors the fleet's real boot pattern: every worker boots itself from a fixed center before doing any work.

reprime sequence mock
1 read genesis origin · identity
2 load memory what happened
3 respect cerebrum learnings · do-not-repeat
4 resume at marker next concrete action

The factory

The self-entity factory

The fleet is not fixed — it grows. Minting a new worker is a pipeline: a fresh entity gets a genesis, an agent-state, a charter, a glyph, and one true role. Then it joins the board and takes its place in a department.

1

Genesis

Write the entity's origin — the fixed center it will re-ground from on every boot.

2

Agent-state + charter

Bind a living state file and a charter that names the entity's bounds and its one true role.

3

Glyph + role

Give it a mark and a single-line role, so the fleet — and the operator — can read it at a glance.

4

Join the board

Register on the assembly board. The new entity can now receive, coordinate, and gate work.

5

Verify the mint

The Librarian confirms the entity boots clean from its center before it takes live work.

6

Join a department

The fleet is now larger by one true role — the factory is how each department grows.

minted this cycle 3 entities mock
directives mock
directive·fan out, then converge tip·ground every claim in a file directive·gate every outward act tip·re-ground from your center directive·truth over self-report tip·spend the window on the work directive·verify before you claim tip·one agent, one true role directive·fan out, then converge tip·ground every claim in a file directive·gate every outward act tip·re-ground from your center directive·truth over self-report tip·spend the window on the work directive·verify before you claim tip·one agent, one true role

Commission a department.

Give the fleet one true role to fill, or step into the academy and learn how a department fans out, converges, and verifies. Reach the fleet at ana@mkrops.ai.