Rules
Nothing ships outside your rules
A missing or invalid policy blocks every ship action. Thirteen kernel rules cannot be disabled.
Platform
A platform team gets agents that work on day one, built on six blocks that are code and configuration you can read, review and program. This page says how each block works.
Rules
A missing or invalid policy blocks every ship action. Thirteen kernel rules cannot be disabled.
Record
State is derived from the policy at the base commit plus a journal, so each requirement traces to a line of YAML.
Context
The catalogue records, the code graph suggests, the source shows. Only the pinned source confirms.
Isolation
The agent loop and its credentials stay outside. Each run gets a fresh microVM.
01 · Rubbr Workflows v0.3 · active development
A workflow runtime that records, beside what ran, what each result depends on. When a result is refuted later, it repairs only what rested on it.
Version 0.3, in active development. The research paper is under review. Open-source release expected mid-December 2026.
Why now
Build systems
Terraform
Rubbr Workflows
The difference: a build invalidates from file hashes. Here the invalidation is late evidence from the world, and side effects are corrected, not recomputed.
The case
A diagnosis and a patch are predictions. Tests pass, the deploy succeeds, and fifteen minutes later the metrics say no. That verdict says the diagnosis and the fix are not both right; it does not say which. This is one executed run.
predictionfact
What you write
The workflow is ordinary code, one line per step. A second file declares what the code cannot say: what to watch after a side effect, and who decides when a result proves wrong. Each number links a note to the lines it is about.
The deployment is watched for 15 minutes. Its result is known only then, and correct is how it is undone if it must be replaced.
When the outcome is refuted, a handler takes over. It may restart the run at two declared points only, the patch or the diagnosis, and at most twice.
An agent is mandated to weigh the new evidence and decide. It reads the run so far and the prediction that failed, then says where the mistake lies: in the patch or in the diagnosis.
Then the runtime takes control back. The advice names one of the declared entries, and the runtime calls it: there is no dispatch code to write. It replaces that step and everything that rested on it, corrects the deployment through its receipt, and watches the new outcome.
Side effects are never run twice: a replay reuses the receipt, a replaced one gets its declared correction, and an uncertain delivery is looked up, never retried blind.
Beyond Temporal
Temporal gives durable replay, retries, timers and sagas you write by hand. None of that is new here, and a Temporal workflow could host this runtime. The difference is what is recorded: a saga log records what happened; a dependency graph records what depended on what.
| Temporal | Rubbr Workflows | |
|---|---|---|
| A step that succeeded, refuted later | Branches and loops in your code. | The outcome is refuted, and repair restarts at a declared point, within limits. |
| Undoing a side effect | A saga you write. | A declared correction, tied to the original receipt. |
| "What depended on what?" | Read the code. | Query it: it is recorded state. |
The runtime enforces the checks you write; it does not decide by itself that a result is true.
Research paper
Under review
The full model, its guarantees and the comparison with build systems and durable execution. Published here when the review is complete.
Open source
Mid-December 2026
The runtime, its language and a set of example scenarios, as runnable source.
02 · Rules as code
.rubbr/policy.yaml is plain YAML under a strict schema, with no expression language. It declares areas, an acyclic graph of ship actions, and one rule engine of when and require.
The kernel
Thirteen rules cannot be disabled by any policy. Four of them:
htdocs/langs/en_US/bills.lang…/facture/class/invoice.class.php and its testhtdocs/compta/paiement/The product manager.
The product manager, a developer, QA.
The support lead.
The product manager, a developer, the finance owner, QA.
Approvals go stale
Host rules make an approval stale first: higher risk, a newly touched area, a different patch outside the approved files. Otherwise an independent reviewer, never the coding agent, judges whether the new revision is structural.
Receipts
A performer acts and returns a receipt for one revision: a provider the operator installed, or a result observed through your source control, CI and monitoring. The receipt never comes from the coding agent.
Decision replay
Decisions are pure functions of the policy at the base commit and the journal, so a past decision is replayed from its record and gives the same result.
03 · Sandboxes
Each run gets its own microVM, cloned copy-on-write from a template built from your Dockerfile. The application, the tests and a browser run there, and nowhere else.
Measured on our test project, on a Mac with Apple's hypervisor.
Sleep and warm wake
A sandbox sleeps while nothing runs in it, and wakes warm for the next tool call.
Checkpoints
A run's sandbox can be checkpointed, and restored from that point.
Where it runs
MicroVMs run on Apple's hypervisor on a Mac, and on Firecracker in the cloud.
The security idea: the agent loop and its credentials live outside the sandbox, and the tool call is the security boundary. The computer where code runs then holds no secrets. A computer with no secrets can be disposable.
04 · Product context
Agents and people ask about the product in business words. Answers draw on three sources of different authority, and the host enforces how each may be quoted.
Functional catalogue
Code graph
Source at a pinned commit
The phrasing rule, enforced by the host: the catalogue records, the code graph suggests, the source shows.
The catalogue records a feature "Invoice due date": the due date is computed from the invoice date and the payment terms. 1
The code graph suggests two callers of the computation: saving the invoice card and changing the payment terms. 2
The source shows that changing the terms recomputes the due date without checking whether it was edited by hand. 3
Questions
People and agents ask over all three sources, and each statement in the answer cites the one it rests on.
Versions
A catalogue version belongs to one Git commit of your repository. A new commit updates the catalogue for what changed, and an answer reads the catalogue and the source at the same commit.
05 · Extensibility
Everything is a plugin: the agent loop, the model adapter, the rules engine, each card on screen. A plugin provides or consumes a service, registers a tool, intercepts an event, or adds an interface component.
Contracts, not vendors
Agents depend on a contract: model, coding agent, shell, tickets, documents, messages, source control. Each has interchangeable providers, chosen in configuration.
Bring your coding agent
The implementation step runs the built-in agent, Codex or Claude Code. Whichever runs, the receipt comes from the host or an integration, never from the agent.
Your tools
Jira, Confluence, Slack, GitHub and CI are providers. Every write keeps a receipt and is never retried when uncertain. MCP connects approved read tools.
The trust split
Only the operator installs executable plugins. A repository supplies typed YAML, in layers that can only tighten. It cannot grant itself a permission.
06 · Background agents
Background work comes in two forms. Both are bounded by policy, budget and access rights, and neither has a private path to production.
Workflows
Declared steps, checks you write and a ledger. When a result turns out wrong, repair restarts at a declared point, a limited number of times. Use them when the path is known.
Free agents
A goal, an owner and a budget. The agent chooses its own path, for exploratory work: triage, investigation, watching for drift.
How a long-running agent works
What bounds it. The repository's policy, a budget per run, and the access rights of its owner. A background agent proposes. Anything that ships goes through the same gates as a person's change.