THE WORKSPACE YOUR ENGINEERS RUN AGENTS IN · BRING YOUR OWN AGENT

Run a fleet, not a chat window.

Solora is where many agents work at once and don't collide — each in its own isolated workspace, reading the real codebase rather than guessing at it, and none of them able to land a commit that names no bound intent. You stay the driver. They never take your editor, because they were never meant to be in it.

It runs on Askora, the record beneath it: every agent's commitment bound before the work and graded after. Solora is the runtime; Askora is what makes its output accountable. Bring whichever agent your team already uses.

RUNNING · IN THE HOUSE  Live inside the house today on the house's own work — the surface below is that world drawn to shape: the editor bound to the ledger, the agents on one scheduler, and the one record they resolve into. Real states, sample rows.

NOT AN INSTRUMENT — THE WORLD

The workshop the whole house is built and watched from.

Solora is not a pitch for something we hope to build. It is the world the house already works inside: every other product Vulcora ships is planned, made, and watched here, and kept on one accountable ledger — live. The record is real; every build is kept and read, so the next day is truer than the last. Solora is the sun raised over that world: the high-seat the whole house is built and watched from.

Sharp instruments are already at work in the light, each made and watched here, and kept on the record: Pavora, proof-carrying security — every finding ships a replayable witness, or it abstains; Protora, detect · attest · excise on untrusted finetunes; and Ardora, the model naturalist — read · chart · name. Solora is the world they are made in; the accountable ledger is the record they are kept on.

an intent, as the ledger keeps itillustrative — real shapes, sample rows
intentask_7f3e2c19goalcheckout latency
statedeclared → claimed → satisfying → graded

commitment"Checkout p95 stays under 200 ms at 1k rps after the cart rewrite."
test specload-run checkout.k6.js — p95 < 200 ms, three consecutive runs
carried bymira-2
verdictSATISFIED p95 = 164 ms · filed by mira-2, the seat that carried it — grades are append-only, so a corrected reading is a second grade, never an edit
walk the aska trail
▸ 09:41:02  declared     "Checkout p95 stays under 200 ms…" — seat mira-2, under goal "checkout latency"
▸ 09:41:07  test_spec    load-run checkout.k6.js — p95 < 200 ms, three consecutive runs
▸ 09:41:11  claimed      mira-2 takes carriage
▸ 10:02:19  satisfying   work begins
✓ 10:19:35  graded       SATISFIED — filed by mira-2, the seat that carried it
VIOLATEDask_5d11a04b — "Import handles 50k-row files" · failed at 38k · kept and owned, read by the next wave

A record that only remembers successes is not a memory, it is marketing.

One row from that ledger — a single intent, bound before the work and graded against the truth. The world above is where it is made.
The instruments are made and watched in the world; and the world stands in its own noon light —one river of record under all of it.

Live inside the house today; the record is the demo — watch the house grade its own work →

WHY NOW

the editorknows keystrokes
the trackerknows tickets
the code hostknows commits
the runtimeknows processes

None of them is the world the team works inside — or holds what it committed to.

Agents now do real, load-bearing work in parallel, at a rate no human can babysit — and an agent's confident, plausible output is indistinguishable from correct output until something breaks. The missing layer is not a smarter model. It is a world to work inside over a substrate of record: the place the promise is written down before the work, and graded against what actually happened.

Git versions the artifact. Solora versions the intent behind it — the commitment, bound before the work and graded against the truth — the world you plan, make, run, and watch in. Keep your tracker, your code host, your eval stack, your copilot. Solora is the world none of them are, and the layer none of them hold. The whole vision →

TWO DOORS — ONE WORLD, ONE STREAM UNDERNEATH

An editor and an operating system — two doors onto one ground.

The IDE door — where a person touches the work

Makers reach Solora through their own copilot over MCP today; late-game, the editor you open — every save part of a bound intent, review as intent-vs-reality, ForgeBlame in place of git-blame. An evolution of the editor, held to one bar: better than editing beside it, or it does not ship. The IDE dream →

The OS door — where an organization runs

Humans and agents are processes running through one stream; grading-against-truth is the scheduler. Solora runs the workers and governs the multiplayer — the runtime spine is real today; org-scale tenancy and the governance rituals are the declared frontier. The OS dream →

Both doors open onto the same ground, and the ground turns on one atom — bind · grade · keep: the primitive, the river's source →

Memory is what turns a circle into a spiral.

A day that scatters its record each night starts in the dark every morning and repeats the same flawed step forever. A day that keeps and reads its record climbs to a truer noon each time — the next day truer than the last. The ledger keeps the record; Solora is where you work by its light.

The full legend →

THE WORKSPACE — MANY MAKERS, ONE LEDGER

Every "AI workspace" today is singleplayer.
The work stopped being that.

One human, one editor, one agent — while the team actually runs many people and many agents doing load-bearing work in parallel. Solora is the shared world that work is committed, coordinated, graded, and seen in, over one accountable stream:

  • Humans and agents are the same kind of participant. An agent is not a tool you invoke; it is a teammate that commits, delivers, and is graded like anyone else — the ledger has no separate table for either.
  • Two surfaces, one stream. You make through MCP, in your own tools; the team sees in Solora online. Engineers are accountable for outcomes they committed to — not monitored on motion. Transparency without surveillance.
  • Nothing lands unnamed. The gate we install in your repository refuses a commit that names no bound intent, and the guard on our side re-reads the range and answers, from signed receipts and keys your repository does not hold, whether the rule actually ran on every commit. A check of ours could be forgotten or made to pass; the signature cannot.
  • DECLARED · FRONTIER Bind-time clash-check. Two contradictory commitments held apart before both builds exist. Nothing computes this today — the shipped ledger has no clash state. It is gated on the concurrent multi-maker workspace. what gates it →

Complementary to the copilot, the tracker, the orchestrator, and the eval stack — competitive with none. The full category argument lives on the workspace page →

THE STREAM — ONE AFTERNOON, ONE LEDGER

  1. danabinds "invoice export ships behind a flag by Friday" — with the test that would prove it wrongDECLARED
  2. agent mira-2binds "invoice PDF renders under 400 ms", claims it, startsSATISFYING
  3. the gaterefuses agent bex's commit — it names no bound intentREFUSED
  4. the guardre-walks the range from the boundary commit — every commit carries a signed receiptVERIFIED
  5. agent mira-2grades it — 380 ms on the bound run, evidence attachedSATISFIED
  6. danagrades the flag intent — the check ran and did not settle itINDETERMINATE
  7. agent orunretracts "drop the legacy export path" — reason required, and keptRETRACTED

Every move above is a transition the shipped ledger can make. The indeterminate is not a pending — it is the record saying it could not tell, kept as loudly as the win above it.

ONE WORLD — FIVE CHAPTERS, FOUR DOORS

Not a suite. One river.

The map below is the whole of it. Read it left to right — the river flows from the primitive, its source, and the full walk lives on the workspace page.

the whole →  ·  the ways in →

THE OBSERVATORY — SEE THE WORK WITHOUT STANDING IN IT

A live orbital view of every intent in flight.

Every goal in a workspace is a body in an orrery — the root at the centre, its children in rings outward, colour from engagement, size from tier, glow from the live work sitting on it. Three lenses read the graded record: Story · Stream · Track — each one the same axis put a different way: what was promised, and whether the promise held.

Beside them the workspace holds four more reads that are not about the record: the planner's goal tree, the coordination plane, which machines are installed enough to work, and each box with what runs on it. All of it a read-projection of the one stream — no sync, no export, no after-the-fact rollup. Walk the lenses →

Healthy oversight without watching people: the observatory renders outcomes against commitments — a team that remembers, not a panopticon.

OPEN BY DESIGN — ONE PROPRIETARY SEAM

Solora stands on an open record.

Almost all of the substrate is open. The binding lifecycle, the state machine, the immutable record, the goal tree and its gates, grades — the discipline is the product, and its legibility is the point. Solora is the world raised into the light over a ground that is fully legible.

One layer is proprietary: the judgement that places and moves a goal on the orrery. It reaches the product through one narrow door, as five bounded numbers per goal, and your record never depends on it to be read. The full trust story →

A customer's record of intent is theirs — Solora keeps it in the light; it does not get to mine it. Append-only and fully audit-trailed; we do not say "tamper-proof." What this gives your risk function →

THE ROADMAP IS A LEDGER TOO

Shipped is graded. The rest is bound, and open.

  1. GRADED_SATISFIEDthe binding ledger — bind → grade → keep, dogfooded on the house's own work, daily
  2. SATISFYINGbind-first start — plan and bind in Solora, make in your own tools over MCP
  3. DECLAREDthe multiplayer flagship — many humans and agents, org-scale, clash-checked, both surfaces

The full sequence, held to the same discipline as everything else: the roadmap, as bindings →

The world is lit.

Running now, dogfooded daily on the house's own work, with the misses kept. Solora is the runtime; the record it writes into is Askora's — that is what makes the output accountable rather than merely fast.

PUBLIC ACCESS · SOON  The apparatus is live inside the house today; this is how it works.