Most software begins with workflows. We begin with reality.

The software is not the system. Reality exists before any interface names it, any workflow moves it, or any model explains it.

A workflow may be wrong. A dashboard may be wrong. A report may be wrong. The book still has to be right.

The software is not the system

Screens can look settled before the book is.

Evidence beats stories

Reality does not need evidence. Truth does. A claim becomes usable only when the evidence survives.

Projections are not truth

Dashboards, reports, timelines, status lights, and AI explanations are views. When views become authority, drift becomes hard to find.

Operating rules

When authority is ambiguous, systems fail.
Hidden state is where operational truth goes to die.
Two truths are not redundancy. They are a warning.
A workflow is a projection, not a source of truth.
If you cannot reconstruct the change, you do not have a book.

Public artifacts

asof123 As-of decision infrastructure

Most Wall Street bugs are secretly as-of bugs.

frontier123 Authority crossing framework

Framework for managing authority crossings in open systems. Most state-management systems assume events are trusted; frontier123 assumes observations arrive from partially trusted external systems.

pm-decision-os Portfolio decision stack

Portfolio decisions are changes in reality, not buttons in a workflow.

trading-cli Pairs trading risk overlay

Risk must be explicit before action.

Method

Reality: Reality exists before the system is built and after the system fails.
Evidence: A dashboard does not make something true. Evidence makes reality observable.
Authority: If nobody can say which source won, the book is already broken.
Truth: Evidence and authority decide what can be trusted.
Decision: A decision is not commentary. It changes what happens next.
Projection: When the chain breaks, nobody can explain the decision.

Engineering doctrine

Ontology first: Name the objects before building the workflow.
Substrate first: Decide where reality lives before deciding how people move through it.
Authority before action: Define which source wins before anything acts.
Lineage before confidence: Preserve the path or lose the right to trust the result.
Screens last: Workflow is derived. Screens are projections.

Where reality breaks

Wrong views become expensive actions.

Research: Assumptions become conclusions after everyone forgets they were assumptions.
Portfolio decisions: Recommendations become executions. Executions become reality.
Spreadsheets: Workbooks cross boundaries with more authority than anyone admits.
Execution graphs: Replay matters when memory, meetings, and dashboards disagree.
AI systems: An explanation is only a projection. Evidence and lineage decide whether it deserves attention.

Proof

Retail trading calendars are fragile. We made them deterministic.
Deterministic LLM execution is not the default. We made it governed.
Networked agent systems lose authority quickly. We made authority explicit.
Spreadsheet systems are opaque. We made them replayable.
Day-state operating systems drift. We made state explicit.
PM operating systems turn judgment into hidden state. We made decisions reconstructable.
Knowledge substrates decay without authority. We made lineage survive.
Timeline navigation is usually presentation. We made it operational.
As-of decisions are easy to corrupt. We made them reconstructable.

Who we are

We are obsessed with reality, not consensus.

We become uncomfortable when two truths exist, ownership is unclear, authority is ambiguous, lineage disappears, or projections become reality.

Contact

If this is how you already see systems, email reckoningmachines@gmail.com.