Four cores, one contract

Each implementation lives in its own isolated core to avoid cross-language mixing. Pick one language and deploy it standalone — all four pass the same contract test suite and produce byte-identical output.

core-go
reference
Go reference implementation. The behaviour authority lives at the repository root (cmd/hushline, pkg/hushline).
core-rust
v0.1.5 · fastest
Rust implementation (regex + serde), built as the hushline binary. Fastest measured core at 204.7 MB/s.
core-python
v0.1.5 · stdlib
hushline_core, published to PyPI as hushline. Standard library only, no third-party runtime dependencies.
core-node
v0.1.5 · stdlib
Node/TypeScript implementation, hushline bin target. Runs on the Node standard library.
Command contract

All four cores implement the same command surface. A deployment points to exactly one core folder.

hushline mute -- <command> [args...]  # run and shape output
hushline manifest init [--global|--local] # create a redaction manifest
hushline manifest show           # print active rules
hushline permit [status|allow] [path] # the local permit gate
hushline version
Hardening constraints (all cores)
◈No telemetry — nothing is reported anywhere.
◈No network reporting — filtering happens entirely on the machine running the command.
◈Deterministic output shaping — the same input produces the same shaped output across every core.
◈Permit gate behavior — an optional local marker gates execution in a working directory.
Isolation rule

Never import or mix runtime artefacts across core folders. A deployment must point to exactly one core folder, and the build target, package config, and operational docs must reference one core explicitly.