Portal Transparency — Harper Guild K533 Tests#
“We can all know what’s appropriate to know, when it’s appropriate to know it.” — Founder direct, BP041#
This section documents K533 tests #9 through #12 — the reproducibility pack for Liana Banyan’s
Law Enforcement Search Portal and Harper Guild mediation layer.
These tests verify that:
- Test #9 — Portal usage is logged and member-visible
- Test #10 — Packet Briefing Case unlocks require IP Ledger touchback (every time)
- Test #11 — Triple-Stamp access flow: all 3 stamps required; any missing stamp = Portal refuses
- Test #12 — Harper Guild disclosure rules govern what’s visible and when
Why this matters#
The BLOOD RULE binds: No law enforcement or external party gets direct access to member data. Ever.
Instead, Liana Banyan operates a Law Enforcement Search Portal — a transparent, accountable interface
where every access is Brand-Stamped, Triple-Stamp verified, and IP-Ledger logged.
This isn’t obstruction. It’s Higher Standards Class — holding those who interact with our substrate
to the same accountability we hold ourselves.
The cabinet runs in plain view. The portal logs run in plain view. Every access is traceable.
Every Harper decision is recorded. The substrate films the surveilors.
Composing canon#
FOR THE KEEP × 19.
K533 Test #10 — Packet Briefing Case Verification Claim: Data returned through the Portal is delivered as a Packet Briefing Case — a signed bundle with embedded Python scribe. The scribe requires IP Ledger touchback to unlock. Every subsequent re-open is also logged. Metadata watermarks enable tracing if data appears in unauthorized locations.
Founder direct: “The data will be encoded with metadata so that we can track it to any unauthorized use, with packet briefing cases that have a python scribe that requires touching back to the IP ledger in order to unlock so that EVERY USE is logged.” — BP041
...
K533 Test #11 — Triple-Stamp Access Flow Verification Claim: Every Portal access requires THREE cryptographically-verified stamps stacked + ledger-recorded. Missing or expired any stamp → Portal refuses. Every stamp issuance + verification + use is ledger-recorded.
Founder direct: “If a law enforcement wants to see something, they log in with a personal brand stamp, then apply the agency brand stamp that gives them access, then the warrant or judge order or whatnot… all automated except for the signing it legally, AND the harper who monitors.” — BP041
...
K533 Test #12 — Harper Guild Disclosure Rule Verification Claim: Portal access information is private by default. Harper Guild rules (HG-101 through HG-301) govern when and whether external disclosure occurs. Members can browse their own Portal exposure and verify the rule-base is published, versioned, and AGPL-forkable.
Founder direct: “Yes, some things are private. So, we have rules — the Harper Guild decides.” — BP041
Privacy-by-Default + Rule-Based Disclosure The substrate logs everything internally (Federal Body Cam doctrine; tamper-evidence intact always). But what’s publicly disclosed depends on which Harper Guild rule applies:
...
K533 Test #9 — Portal Usage Logs Verification Claim: Every Law Enforcement Portal access is Brand-Stamped, append-only IP-Ledger logged, and visible to the affected member (when not under a court-ordered seal).
Pre-conditions:
Mnemosyne installed and running (AMPLIFY substrate-api on :11480) Member has their cooperative-substrate member_id Test Steps Step 1 — Query the IP Ledger for portal_search entries # Check IP Ledger stats (total entries, portal_search count) Invoke-WebRequest -Uri 'http://127.0.0.1:11480/yoke/ip_ledger/stats' -UseBasicParsing | Select-Object -ExpandProperty Content | ConvertFrom-Json Expected:
...