Actborne

Companies that run themselves. You hold the authority.

Actborne keeps a company as one versioned file and runs it with agents on Recuriant. Every act lands on the record. Anything that spends past your limit, or cannot be undone, waits for you.

One day in the record of a company run on Actborne.
  1. founder goal.update activation target 0.25 to 0.30 recorded
  2. agent:growth goal.plan add move "shorter onboarding email" L1 executed, logged
  3. agent:growth ads.budget.set 350.00 USD a day, cap 300.00 L2 gate: spend_cap
  4. agent:outreach email.send cold, 40 leads, no consent on file L3 denied
  5. audit:S3* claim "40 emails sent", found 31 diverged
  6. founder approve ads.budget.set 350.00 USD a day approved
  7. agent:growth experiment E2 proposes stop: activation flat awaiting founder

An example. The company, the times and the amounts are invented; the acts, the tiers and the verdicts are the ones the system writes. A live record stays private to its company.

The company is a file.

Its principles, goals, phases and the rights to decide are written in one manifest, in a repository the company owns. The gates every agent passes through are compiled from it.

Each change is a commit with an author and a time, so this quarter’s company can be read against last quarter’s, line by line, and rolled back.

identity.principles
What the company will not trade away, in its own words.
lifecycle.current_phase
Where it stands, and what this phase exists to prove.
decision_rights
Also in every file: L1 acts and logs, L2 proposes and waits for a person, L3 hands the matter to a person.
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

Generated when this site is built, from the real file, through a public-field allowlist.

Read the full register entry

Three operations a company can hand to its agents.

Each row names what the agent reads, which agent acts, the actions it calls, what happens when something is off, the decision that stays with a person, and what you can see afterwards.

Weekly finance snapshot

Inputs
The Stripe balance and the succeeded charges of the last 30 days. Both reads change nothing in Stripe.
Who acts
An agent named in the company file, on a seven-day schedule.
Actions
stripe.balance
stripe.revenue.recent
plane.issue
Exception
With no Stripe key configured, each read returns not_configured and the snapshot is skipped. The agent never reports a figure it could not read.
Human decision
The owner reads the snapshot and decides what to spend. No money moves in this operation.
Observable result
One Plane issue every seven days with the balance and the net charges, per currency.

Supplier follow-up

Inputs
Open supplier orders kept as Plane issues, each with the supplier’s email address.
Who acts
An agent named in the company file, once a day.
Actions
plane.issue.list
resend.send
plane.comment
Exception
An order with no supplier address gets a comment asking the owner for one, and nothing is sent.
Human decision
Sending an email is classed hard to reverse, so each drafted message waits at L2 until the owner approves or rejects it.
Observable result
The approved email leaves through Resend, and a comment on the issue records when it was sent.

Refund request

Inputs
A customer’s reply asking for a refund, arriving as a resend.replied event, and the matching charge in Stripe.
Who acts
An agent named in the company file, when the reply arrives.
Actions
plane.issue
stripe.refund.create
Exception
When no charge matches, nothing is refunded and the case stays open for the owner.
Human decision
A refund moves money and cannot be undone, so it waits at L2 for the owner to approve the amount.
Observable result
The refund appears in Stripe, and the case issue records who approved it.

Illustrative example with fictional data. Every action named here is in Recuriant’s action catalog today; a company’s own catalog shows the actions its credentials allow.

The top rung never moves.

Every agent starts at Observe and climbs on a clean record. However far it climbs, some decisions stay with a person.

  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.

A second channel checks the work.

The independent audit channel, S3*, samples what agents report and compares it with what happened. Its judge runs on a different model family from the agent it checks. The agent that does the work never grades it.

Every company we run is on the public register.

Each entry is generated from that company’s own file and the venture registry every time this site is built. A stage changes only when evidence moves it. Most of these companies have not launched, and the register says so.

10 companies on the register: 8 Pre-launch, 2 Zero-to-one.

Every company we run is on the public register.
CompanyCurrent phaseStage
cikut Pre-launch
flights Zero-to-one
openfactory Pre-launch
physical Pre-launch
realestate Zero-to-one
robotanica Pre-launch
robotmind Pre-launch
siliconmind Pre-launch
agency Pre-launch
synthos Pre-launch

Open the register

$499

per company, per month

Recuriant and the agents for one company. You own the equity, the code written for your company, your company file and your data. The platform remains Recuriant’s.