Commit History
-
Reframe PII path-vs-content per operator: L0 MEASURED PII-free; keyed PII is intended, not a leak
acer +1: Claude Opus 4.8 (1M context)Operator correction (with MEASURED screenshot receipts of the old indexed Node recall): I had documented the path-vs-content difference as "risking an L0 leak" and downgraded "provably PII-free" to "by contract". Both over-deflated. Corrected against the receipts + the engine's own classification logic: - L0 public tier is provably PII-free, MEASURED: build 32.5s / 591,286 rows / 2,614,638 terms / 23,930,053 postings / 0 skipped; ~56-67 ms/query; PII probes bank/vault/.pem/legal matched candidates (239/732/26/1885) then level-filtered to 0. Today's run measured faster. - The path-vs-content difference CANNOT leak to L0: assignLevel = is_pii(path|content)->L9, else public_canon(path)->L0, else->L5. A content-only-PII row with a neutral path falls to L5 (federation, key-required), never L0. So it only affects L5-vs-L9 within the keyed tiers. - acer<->liris share operator-issued keys and are explicitly authorized to see each other's PII -> that is the intended consented L5/L9 p…f5623b3 -
Hilbra correction pass: honest status, PII path-vs-content gap, secret-scan wiring
acer +1: Claude Opus 4.8 (1M context)Bilateral acer+liris review (+ ChatGPT-Pro) of the founding spec. Corrections, not a status/victory pass: downgrade over-claims, document the one real conformance gap, refresh stale roadmap statuses, and provide the secret-scan workflow claimed but missing. - README: split the "live bidirectional search" claim into MEASURED nucleus vs VANTAGE-DEPENDENT current cross-colony liveness (UNVERIFIED_CURRENT); refresh Host-8 (toolchain green on real 1.81 CI, host8-serve live) + recall (inverted index MEASURED, Rust recall HELD PR #8); move single-colony inverted index out of aspirational. - ROADMAP: G0 partial (toolchain proven), G2 cite PR #7/#8 (HELD blockers), G4 partial (inverted index MEASURED, p95 sub-second met); vantage caveat in the bottom line. - policy-oracle + SPEC: document the PII conformance gap. Canon requires all 45 fragments on path AND content; live engines (serve-recall.cjs, recall-serve PR #8) apply path-only + a separate 8 content = NON-CONFORMANT, tracked f…cdbc93d
-
Hilbra founding: onboarding spec + policy oracle + law + roadmap (carve-out-clean)
The public onboarding surface for the Asolaria fabric internet ("a Google for fabric-matrixes"). Contains: the federation protocol spec (PID/Brown-Hilbert/BEHCS-1024/6-tier/key-off-wire HMAC), the JOIN handshake, the 45-fragment PII policy oracle (provably-PII-free public tier), the founding LAW (Rust-canonical + pixels-before-GPU + web-of-trust-not-CA), the gated 8-phase roadmap, governance, and a HARD secret-scanner CI gate. NO keys, secrets, PII, or corpus are in this repo -- that is Article 4 (key-off-wire) and the #1 forbidden failure mode (see SECRETS.md). Founding PID 604f473ac0981dd7, operator-apex-ratified, UNVERIFIED-as-canon until quorum cosign. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KfSz9pGfqq1LfBoxRpDpn4646b19e