Offline operation.
Tools must function without network connectivity — not merely degrade gracefully. If the network is down, the tool still works. Full stop.
offline-first · not offline-tolerant
A commitments system for frontier-grade software. Business Assistance System — a practical standard for building business tools that can operate across unstable conditions, constrained devices, mixed operator skill levels, and long product lifecycles. Not what to build. What your tool must survive.
basics · evidence-backed assessorTools must function without network connectivity — not merely degrade gracefully. If the network is down, the tool still works. Full stop.
offline-first · not offline-tolerantTools must work on low-memory, low-power, small-screen hardware, including feature phones. The frontier does not run the latest MacBook.
low-memory · low-power · KaiOSTools must be operable by people who did not build them and may not read English. The operator learned the tool yesterday. It must still work.
non-technical · multilingualRecords must be exportable in open formats, never locked to a vendor. Your data outlives every product cycle, every funding round, every pivot.
open export · no vendor lockTools must be designed to operate for decades, not just until the next funding round. Century-capable is the design target.
decades · not quartersThe BASICS CLI examines code, configuration, documentation, and test coverage. It does not guess — it checks specific files, specific patterns, specific behaviors, and reports what it finds.
CLI assessor · not a checklistbasics CLI · evidence-backed reportsThe standard specifies obligations. The CLI assesses conformance. Both are public.