praxisops.life

Praxis: the doing.
Ops: never finished.

PraxisOps runs a life the way an ops team runs a service. It doesn't store what you meant to do — it tracks what's due, what's running low, what's coming up, and what needs a decision.

You've abandoned four systems.
They were all passive.

A spreadsheet, a task manager, a notes app you stopped opening. None of them acted. PraxisOps tracks what's due, what's running low, what's coming up, and what needs a decision.

The name is the thesis
Praxis

Greek. Action as opposed to mere knowing. The doing itself, not the record of it.

Ops

The continuous, never-finished work of keeping something running. There is no done state.

Together: the doing, ongoing. That is the whole argument, and it is why this is not another place to write things down.

What it handles

Four domains at launch. All of them literal.

Module 01 · shipping

Tasks & checklists

The To Done board: priority, backlog, done. Recurring checks come back on their own cadence — the quarterly filter change reappears whether or not you remembered it.

Module 02

Groceries & provisioning

Knows you're out of coffee before you do. Tracks what you keep stocked, how fast you go through it, and what belongs on the list this week.

Module 03

Financial planning

Bills, renewals, and the annual charges that arrive without warning. What's due, what changed, and what a decision costs before you make it.

Module 04

Health & appointments

Six-month dental recall, prescription refills, the referral that expires. Appointments tracked as recurring obligations, not one-off calendar entries.

Records and documents sit underneath all four — the receipts, warranties, and statements each one needs.

Proof of method

One module already runs.

To Done is the tasks-and-checklists module, and it is built. Priority, backlog, done — plus a parking lot for what shouldn't be on the board, and a full API so agents can act on it rather than just read it.

It sets the floor for everything else: keyboard-first, calm by default, and opinionated enough to make a decision for you. The remaining modules are being built on the same foundation.

Priority · Backlog · Done Parking lot REST API · MCP
The point of view

Ops work is continuous. It never reaches a done state, and it rewards systems over willpower — which is exactly the shape of running a household, a body, and a budget.

Every system you abandoned asked you to remember to check it. An ops layer inverts that: it holds the running state, surfaces what's due, and tells you when something needs a decision. You bring judgment; it brings the ledger.