substrate/substrate-without-inference-base-case

The Substrate-Without-Inference Base Case establishes that the Totebox Archive must remain fully operational and freely transferable even when service-slm cannot run any inference. AI inference is value-add. The deterministic substrate — the file ledger, the knowledge graph, the extraction pipeline, and the editorial services — is load-bearing.

[edit]What the base case requires

When all three compute tiers (local specialist, GPU burst, and external API) are simultaneously unavailable, the following must hold:

The WORM file ledger (service-fs) is operational: ingest, query, and checkpoint all work. The knowledge runtime (`service-content`) is operational: graph queries, vector search, and temporal queries work, with mutations from non-AI paths only. The input service, extraction service (at the deterministic parsing layer), egress service, people service, and email service are all operational. The Doorman is bound and listening, returning 503 to inference endpoints while keeping health and contract endpoints always responsive. The operator TUI operates in deterministic-only mode.

When marketplace and settlement services are enabled, those are also operational in the base case. Transactions may proceed without AI-assisted grounding; audit and consent records are still enforced.

[edit]What the base case does not require

It is not required that all three tiers be simultaneously unavailable to activate this mode. The base case is simply that at least one tier is down. If even one tier is available, AI-assisted operations resume normally. The deterministic-only mode activates only when every tier has failed simultaneously.

[edit]TUI in deterministic-only mode

When the operator TUI detects that no inference tier is available, it enters deterministic-only mode. The status bar shows that AI is disabled. Natural-language chat input is unavailable. Slash commands that depend on AI — verdict capture, brief submission, adapter listing — gracefully return no-ops or unavailability notices.

Deterministic slash commands remain fully operational: status and health queries, audit ledger queries, knowledge graph queries, keyword search, export, and the ownership transfer preparation flow.

[edit]Transfer of ownership

The "freely transferable" property is more than a philosophical statement. It is implemented through a structured transfer flow. The operator runs a transfer preparation command to produce a self-contained, cryptographically signed bundle: the per-tenant graph snapshot, the audit ledger, the trained adapter weights, the seed taxonomy, the pack manifest, and the tenant configuration. The bundle is signed by the operator's identity key and the integrity is anchored to a public transparency log. [^1]

The receiving party imports the bundle into a fresh Totebox. Deterministic operations work immediately on the imported state. AI-assisted operations become available once the new operator configures the compute tier.

[edit]Why this matters commercially

The freely transferable property distinguishes a sovereign asset from a service subscription. When a business is sold, the new owner imports the Totebox bundle and has the complete operational history available immediately — the knowledge graph, the audit ledger, and the workflow vocabulary — without re-subscribing to any platform or engaging migration consultants.

When a business dissolves or splits, each party receives their share of the graph as a portable, cryptographically-signed artefact. When the acquiring party in a corporate transaction imports the bundle, patient or client records, audit history, and operational patterns are available immediately with verifiable provenance.

If the platform itself ceases operations, the customer continues operating their Totebox indefinitely. The deterministic substrate works without the platform. The customer loses the ability to receive new vertical packs and to transact on the platform's marketplace, but their existing operations do not pause.

[edit]Implementation requirement

The base case constrains every service implementation. Every service must have a deterministic baseline that operates without AI. AI-enhanced operations are documented as requiring the AI tier and gracefully degrading when it is unavailable. Regression in the deterministic baseline — any service that fails when all tiers are down — is a doctrine-level signal that a load-bearing function has been made to depend on AI.

[edit]See also

• tier-zero-customer-side-sovereign-specialist — the Tier 0 deployment that this base case guarantees
• customer-owned-graph-ip — the ownership right that the transfer flow exercises
• single-boundary-compute-discipline — the Doorman's behavior in the base case (503 from inference endpoints; health endpoints always responsive)