Merit AC
Product spotlight Runs entirely on your machine -- source in this repo

Operator OS: the whole business, on your machine, in files you own.

Nine CSV files, an engine that does the money math the same way every time, an event log that makes every change reversible, real double-entry books, a query language, a cash simulation with the odds attached, eight import adapters, a plugin SDK, an agent layer that runs the whole thing on a schedule, thirty-five tools, eight encoded businesses to start from, and a workbook covering every step on Mac and Windows. No account, no server, no subscription, nothing to log into -- Python 3.9 and an optional git install are the entire dependency list, on purpose.

Five minutes to something real

bash scripts/install.sh          # Mac and Linux
./os doctor                      # check this machine
./os migrate                     # set up the books and the rest of the schema
./os use 01-field-service        # load a real business
./os brief                       # see it running
./os sim                         # the same question, with the odds
./os books post                  # derive the journal from your registries
./os books check                 # three proofs that the numbers tie

Then make it yours: ./os use 01-field-service --empty, ./os setup, ./os brief. That last command printing your own business name is the finish line for day one.

What it does

Forty-three commands in total (os help lists them, os help <group> narrows it). The core ones:

os brief

What needs you today

os cash 90

When you run out, and on what date

os sim

The same forecast, run 2,000 times, with the odds

os whatfirst

Which single collection changes those odds most

os aging

Who owes you and how late they are

os margin

What each job made after your own hours are paid

os anomalies

Statistical flags across the whole business

os query "..."

Ask the registries anything

os books check

Three proofs that the books tie to the reports

Architecture

Four sources feed the same command line, and it is the only thing that ever touches the data — always through the event log first:

Workbookwritten steps, Mac & Windows
Tools (35)SKILL.md, no code — composes commands
Adapters (8)bank, Stripe, PayPal, Square, QuickBooks…
Plugins (4)capability-gated extensions
os — the command linescripts/os.py
Engine — lib/osdata.pythe one place that reads or writes data
Event log — data/events.jsonlhash-chained, written before the file
Data — data/*.csv + business.yml9 plain registries, git-trackable, Excel-openable

Workspaces (8 encoded businesses) seed this data directly via os use — a shortcut into the same files, not a separate path.

Everything above the event log is replaceable — write your own tool, adapter, or plugin, or fork a workspace. What never changes is that a mutation is logged before it is saved, which is what makes os undo, os rebuild, and os drift trustworthy no matter what put the row there.

The eight workspaces

Encoded starting businesses, picked by the failure mode they teach, not by trade:

01-field-service

Money earned and never collected

02-fractional-consultant

Scope creep and revenue concentration

03-design-studio

Hours past estimate, revisions given away

04-maker-brand

Cash tied up in stock, wholesale priced off retail

05-coach-practice

The hours ceiling, and unpaid time between sessions

06-recurring-services

A signed price nobody revisits while real cost creeps up under it

07-event-production

Vendor cash out weeks before client cash in

08-agency-subcontractor

Subcontractor cost quietly eating a project's margin

Why files, not an account

Every registry opens in Excel. Git gives version history for free. Nothing proprietary means nothing to migrate away from later. The cost is no concurrency, which doesn't matter when the business is one person -- and if the project disappeared tomorrow, the business would keep running, because the business is the files, not the software.

What it will not do

How it's licensed

A permanent, per-business license, not a subscription -- install it on every machine you personally use, change any file including the engine, and keep using this version forever even if updates stop. It comes with a thirty-day no-questions refund, since every workbook module has a finish line you can check yourself: if module one doesn't end with your own business printing on your own screen, it didn't work.

The source lives in this repository, under operator-os/ -- this page describes what's actually in that build, sourced directly from its own README and manual, not marketing copy written ahead of the product.