Actborne

How a company file becomes the acts it permits.

A management structure taken from cybernetics, an authority model that keeps the irreversible with a person, and a ladder agents climb on their record.

From the file to the act.

One company on Actborne, drawn with the names the system uses. Each numbered arrow matches one sentence in the numbered list.

How a company file reaches external systems through Recuriant The company file company.yaml Goals lifecycle.current_phase, metrics Procedures workflows Decision rights decision_rights: L1, L2, L3 Recuriant External systems Stripe, Resend, Plane, GitHub 1 2 3 4 5 6
  1. 1

    The current phase states what the company is proving now, and its metrics say how that is measured.

  2. 2

    Each workflow entry names its purpose, its trigger and the agent that runs it.

  3. 3

    Every action a workflow calls is classed before it runs: L1 acts and logs, L2 waits for a person, L3 hands the matter to a person.

  4. 4

    Recuriant runs the workflow and compiles the decision rights into the gate on its dispatch path.

  5. 5

    Only acts that pass the gate reach Stripe, Resend, Plane or GitHub, and each one is written to the record.

  6. 6

    When a person overrides a decision, the change returns as a pull request against company.yaml.

Six functions run a company.

Stafford Beer's Viable System Model describes what any organization needs to stay viable. Actborne implements it as a wiring diagram: six systems, each with its own job and its own record.

S1 Operations
The work itself. Answering a customer, running the routing engine, watching the crawler. Bounded by written policy a person approved.
S2 Coordination
When two operating agents want the same resource at the same moment, coordination is the shared calendar and lock table that keeps them from thrashing.
S3 Control
Present-tense management. Allocates budget and attention across operations, and holds the standards operations meet today.
S3* Independent audit
A verification channel with its own line to policy. It samples reported work and checks it, with a judge from a different model family from the agent it audits.
S4 Intelligence
Outside and forward. Market shifts, competitive moves, what the company should become. It feeds policy, which decides.
S5 Policy
Identity, and the final balance between what control sees inside today and what intelligence sees outside tomorrow. In an Actborne company, you are policy.

Reversibility decides who acts.

Every action an agent can take is classified before it runs, on two axes: how reversible it is, and how far it reaches outside the company.

Reversibility decides who acts.
Class of action What happens
Reversible, low impact Executes directly. Logged and undoable.
Reversible, meaningful impact Executes directly and is flagged for the next audit pass.
Hard to reverse Waits for a person to approve it, and the approval is recorded as a decision you can point back to.
Irreversible Waits for a person every time, whichever agent asks, at whichever rung. Configuration cannot lift this.

Autonomy is a track record.

A new agent, or a new class of action, starts at the bottom and climbs. A configuration flag alone moves nobody up.

  1. 5Always human

    Spend above your threshold, legal commitments and deletions with no undo wait for you at every rung.

  2. 4Operate, approval-gated

    Executes higher-impact actions once you have approved that class of action.

  3. 3Operate, reversible

    Executes low-impact, reversible actions alone. Every one is logged.

  4. 2Advise

    Recommends one specific next action, with its reasoning on the record.

  5. 1Observe

    Reads the company and drafts proposals. A person decides.

Company as code.

Org structure, policy, goals and procedures live as versioned YAML and markdown in a repository your company owns. Every policy change, goal edit and new procedure is a commit, attributable and revertible.

Read the register

company/flights/company.yaml excerpt
  1. metadata:
  2. name: flights
  3. identity:
  4. principles:
  5. - The cheapest path is a graph problem,
  6. not a fare-class lookup. We compose
  7. itineraries airlines never sell as one
  8. ticket.
  9. - Self-transfer honesty is the product. We
  10. always tell the traveler the legs are
  11. separate tickets with no
  12. airline-guaranteed connection.
  13. lifecycle:
  14. current_phase: phase_0_prove_engine # Prove the engine

Connecting your current operation.

A company that already runs moves onto Actborne in four steps, in this order.

  1. 1

    Process inventory

    Every recurring process is written down with its owner, its inputs and the decision it produces. You agree the list before anything connects.

  2. 2

    Credentials and permissions

    Each connection runs on a key you issue, with the narrowest scope that system offers, and you can revoke it at any time. The company file lists the tools each agent role may call.

  3. 3

    Systems

    Email, payments, project tracking and code hosting connect through the connectors in Recuriant’s catalog. A system with no connector stays in people’s hands.

  4. 4

    The first agreed operation

    One operation moves first, with its agent at the Observe rung. It climbs on its record, and the next operation starts once you accept the first.

How a Business Engineering sprint delivers this

Built on Recuriant.

Actborne is the company layer. Recuriant is the operating system underneath: it runs agents, gates what they do and keeps the record. Recuriant is proprietary today. A deployment in your own cluster is arranged on Recuriant’s Enterprise plan.

recuriant.com Move an existing company onto it