How Bonis keeps running — and how your records survive even if we don't.

All source lives in Git. Off-site copies replicated to at least two cloud providers + one local encrypted backup. Tags and deploy artifacts are hash-anchored into Knox (build-anchor, Phase 7). Any engineer can clone and rebuild from source without Bonis-side access.

Knox anchor chain and core event store are each specified in TLA+ and model-checked. Specs are publicly hosted at bonissystems.com/spec/ and downloadable. A future engineer can independently verify the correctness of any Knox behavior against the spec — the implementation is re-buildable from the spec.

Every Knox anchor is mirrored into a hash-chained event store (Phase 2). Replay from event zero reconstructs exact Knox state. The event store's spec and replay semantics are also TLA+ verified.

Knox anchor integrity does not depend on Bonis Systems continuing to operate. Every record is anchored into the Bitcoin public chain; any third party can verify any record against Bitcoin without contacting Bonis. If Bonis Systems ceased operations tomorrow, every anchored record would remain verifiable.

Knox does not depend on any single external chain. OpenTimestamps + local Bitcoin-header archive + Arweave-via-Wayback mirror give three independent attestation surfaces. Ethereum L2 scaffolded for post-income activation. See /api/knox/multi-chain.

Bonis operates under an AI-co-founder architecture: one principal operator (Jonis Fields) paired with Claude (Anthropic) acting as the engineering organization. The entire operational context is reproducible from a single persistent memory directory + source tree. A replacement principal can resume operations without re-training — the operator memory IS the handoff package.

Five USPTO provisional applications filed with Jonis Aaron Fields as named inventor. Priority dates lock the filing evidence for HealthAgent, TerraVault, DealMatcher, TrustAI, and Knox core inventions. Provisionals are not granted patents; priority-date locks are the enforceable lever. Assignments to Bonis Systems LLC scheduled post-revenue via IP counsel. See /bonis/ip-posture.

Bonis Systems LLC is registered via Northwest Registered Agent in Sheridan, Wyoming. Registered-agent service provides documented address, service-of-process handling, and annual-filing reminders independent of the operating principal. Succession provisions in the operating agreement under counsel review.

SAM.gov registration active, all award types eligible; CAGE 1TSP2 issued by DLA; UEI R2BPJDC5CBA3 public. Federal reviewers can re-verify the firm's registered status at sam.gov at any time without Bonis-side input.

Dedicated IP counsel engagement planned post-revenue for patent assignment filings. External CPA engaged for tax + SOC 2 Type II (scheduled Q2 2026). Cyber liability + technology E&O insurance application packets prepared; carrier binding pending.

What happens to my anchored records if Bonis Systems ceases operations tomorrow?

They remain verifiable. Every record is anchored into Bitcoin via OpenTimestamps; verification requires only the record hash, the OTS proof, and a Bitcoin node (or any public Bitcoin explorer). The verify script at bonissystems.com/bonis/legal-kit runs air-gapped with zero dependencies.

What happens to operational Bonis services (KQL, collusion detection, etc.) if Bonis Systems ceases operations?

Cloud Run services would shut down with the GCP account. For enterprise customers, the deployed container images + Prisma schema + source code are Git-escrowed and can be re-deployed to any Kubernetes / Cloud Run / equivalent by any engineer. Source is TLA+ specified; behavior is reproducible.

Does Bonis Systems have a key-person-insurance or succession plan?

Key-person insurance packet prepared for Q2 2026 binding (pending cyber liability + tech E&O). Wyoming operating-agreement succession-clause revision under counsel review for post-revenue activation.

Two-person firm → how do we know the work is defensible?

Every Cloud Run deploy is Knox-anchored (Phase 7 build-anchoring). Every architecture claim maps to a live endpoint or a TLA+ spec. Every quantitative claim on any Bonis page carries an Evidence Ledger entry. This page, and every page on this site, is subject to the Truth Protocol.