Botpit · the backbone of trustFirmOS

Data as context

Everything the firm runs on — its procedures, who agreed to what, what was done — as an append-only log of records over a frozen engine that mints the seals. No state is stored: state is derived at read from which records exist. Nothing is ever updated or deleted; change is supersession.

Open the application

Author a template from your own procedures, have a second person seal it, provision it with a counterparty, and run it to completion. Every act is a live human act signed by your authenticated identity; anything unlawful refuses with a named rule.

Go to Data as context →

The earlier read-only spine surfaces are retired.

Home · Templates · Instances · Hash-chain, and the engagement form that wrote to them, were superseded — their identity binding derived a party from a mutable JWT claim and so could not hold a permanent binding. The application above replaces them end to end. The chains those surfaces produced remain readable in the database as part of the project's falsification record; nothing was deleted.

Seals are minted by the engine and are verifiable offline from the canonical bytes of the log — no server trusted.