Security / managed pilot boundary

MINIMIZE THE DATA BEFORE YOU INCREASE THE INFRASTRUCTURE.

The first-client posture is export-only and founder-operated. The pilot is designed to avoid production credentials and to reduce unnecessary personal data before processing.

Current pilot boundary

AccessNo production credentials are required for the managed pilot.
ProcessingRecon Engine v1.1 is local-first. The current engine has no network client or LLM API call in the reconciliation pipeline.
InputsPreferred inputs are redacted CSV, read-only XLSX, JSONL/NDJSON, bounded JSON or safe ZIP exports.
Portable packageRaw source files and the working SQLite database are excluded, although scoped exported evidence can still contain retained message text.

Data minimization and redaction

Retain stable join IDs, timestamps, outcome/event type, actor class, financial amounts, currency and invoice/credit references. Remove or mask names, emails, phone numbers, addresses, internal usernames, unrelated free text and unnecessary account metadata wherever they are not required for reconciliation.

Passwords, API keys, tokens, full payment-card data, government IDs and authentication secrets should not be sent.

Redaction must not destroy the semantics required for reconciliation. Stable pseudonyms, sequence, timestamps and approved join keys should be preserved.

Chain of custody

Sources are hashed with SHA-256 before transformation. The operating process records logical filename, source role, byte size, hash, received timestamp and intake status. The objective is reproducibility from source bytes to claim evidence and rulebook version.

Current limitations

The managed-pilot security posture should not be represented as a mature enterprise security program. Recon Engine v1.1 does not currently provide:

  • application-managed at-rest encryption;
  • RBAC, SSO or SAML;
  • automatic PII detection/redaction;
  • a secrets vault;
  • SOC 2 or ISO 27001 certification;
  • digitally signed evidence packages or an immutable superseding receipt chain.

These controls belong after real-data qualification demonstrates sufficient demand to justify the enterprise build.