INDIVISA

Indivisa LLC

Probabilistic output. Deterministic evidence.

A model estimates. A hash does not. Indivisa seals documents and AI outputs into deterministic CBOR envelopes whose identifiers anyone can recompute. Zero content leaves your device.

View the pipeline Status register

sha2-256 multihash

1220e63a43b74f7eb082c62689b487bf484fae73de6307d0cf469c699a3d2977d172

SHA-256 computed in this browser, shown as a multihash (prefix 1220). Change one character and the identifier changes. Nothing is sent anywhere.

The pipeline

Five stages. Each one is labelled with what exists today.

  1. Inspect docforensics

    Functional Core

    Reads a document before anything else does: file structure, embedded metadata, whether its text can be extracted, and anomalies. Metadata is inventoried, not stripped. Runs without a network connection.

    Python version in use. Rust version in development, not yet integrated with sealing.

  2. Seal Envelope v1

    Active

    Each file is hashed on your device. Layers are bound into a deterministic CBOR envelope with a 34-byte Core ID. Envelope v1 is frozen: its bytes and test vectors never change. Extensions live in sidecars.

    Time anchors

    Active

    Two RFC 3161 timestamp tokens from independent authorities. Fully time-anchored only when both validate; one valid token is reported as partially time-anchored.

    Signed statements

    Active

    Device and operator signatures over the seal, ES256. ML-DSA-87 is in development, not implemented yet. A signature shows that a specific key signed a specific Core ID. It does not show who held the key, or that the content is accurate.

  3. Isolate Registry

    Active

    We hold hashes. Seals carry no account link. Payment lives with Stripe. The hosted registry holds digests, seals, public keys and timestamp tokens; no file content, file names or matter names reach it. Row-level security on every exposed table, default deny.

    Local reference setup

    Experimental Profile

    An air-gapped workstation on Apple silicon running local language models (MLX), with no outbound connections. Used internally. Customer-run deployment is not offered at launch.

  4. Transport Portable envelopes

    Active

    Your files stay with you. The envelope, sidecars and timestamp receipts travel beside them by any channel you choose, and verify at the destination. Only the Core ID reaches the registry. No proprietary content is taken into any cloud.

  5. Connect Local MCP

    Functional Core

    A local Model Context Protocol router (stdio only, no network) with sandboxed servers. It exposes deterministic tools, including document forensic scans and hash verification, to agent runtimes without sending data off the machine.

Built on the pipeline

WITNESS witness.mobi

Sealing for legal evidence. Free to verify, with no account.

Technical specifications

Exact standards. Nothing here implies certification.

Hash
SHA-256, multihash 0x12 0x20, 34 bytes
Encoding
Deterministic CBOR, RFC 8949 §4.2.1
Envelope
v1, frozen; at most 256 KiB; 1 to 1000 layer entries
Signatures
COSE_Sign1, device and operator; ES256 in production. ML-DSA-87 in development, not implemented yet.
Time
RFC 3161, two independent timestamp authorities, imprint over the seal digest
Core language
Rust for every cryptographic path
Vector testing
Official vectors: NIST ACVP, Wycheproof, RFC test vectors. ACVP results are not CAVP validation.
Audit
No independent audit has been done yet.

Open standards

Specifications and the reference implementation will be published under Apache-2.0. Release date not set.

Verification is free and needs no account. Expired or unpaid licences stop new seals only; existing seals and verification are never withdrawn.

Deployment

Hosted, two tiers at launch: Solo (one seat, up to 100 seals per 28-day period) and Org (annual, unlimited seals). Prices on request.

Not offered at launch: per-seal pricing; customer-run or air-gapped deployment.

Company information: indivisa.llc.

privacy@indivisa.llc