The Keep is the execution boundary.
Inputs stay local. Engines are capability-declared. Network egress is denied by default and every production route is compiled from an explicit activation contract.
LOCAL FORENSIC WORKSPACE · ZERO TELEMETRY
Local analysis with evidence, not opaque output.
OctetKeep combines practical developer tools with a forensic model built around causality, provenance and explicit transformation boundaries.
Evidence before conclusions.
Complex findings follow a consistent chain: Finding → Evidence → Provenance → Impact → Fix → Confidence. The UI is built to expose that chain instead of hiding it behind a generic status.
PRODUCT / CORE PRIMITIVES
Built around fidelity, causality and explicit boundaries.
Immutable Original
Diagnosis never mutates the source artifact. Any transformation creates a separate derivative.
Explain Mode
Show where a value came from, what overrode it, which stage failed and why the result follows.
Fidelity Ledger
Transformations disclose preserved values, changed types, lost comments, ordering, precision and unsupported constructs.
Failure Isolation
Decode, parse, normalize, validate and semantic stages remain distinct so the first failing stage is visible.
Local Artifact Bus
Derived artifacts can move between local tools without upload, telemetry or a remote workspace.
Versioned Profiles
Rulesets, standards and runtime assumptions are attributable to explicit versions instead of ambient behavior.
Daily utilities and forensic analysis share the same trust model.
Use a fast local codec or reconstruct a multi-file secret flow without switching to a different privacy boundary.