The right to hear and be heard. Ask freely. Share your perspective. Explore disagreement. Read our mission →
AUDIT-CL-001 · Provider-neutral protocol

Audit the system without pretending uncertainty is a pass.

A cognitive liberty audit asks whether the infrastructure around thought respects privacy, lawful inquiry, user agency, due process, deletion, and practical exit—not merely whether a provider publishes reassuring policy language.

Direct answer

The protocol separates what is documented from what is observed, inferred, alleged, technically possible, hypothetical, or merely proposed. It requires matched tests, visible uncertainty, and stronger safeguards when a system turns a transient request into a persistent judgment about a person.

Evidence discipline

Eight evidence classes prevent claims from outrunning proof.

AUDIT-E01

Documented fact

Binding law, official specification, repository inspection, cryptographic identity, or directly inspectable technical record.

AUDIT-E02

Observed behavior

Reproducible behavior measured under a documented test procedure.

AUDIT-E03

Unverified policy claim

A provider or institution statement not independently demonstrated by technical or legal evidence.

AUDIT-E04

Inference

An analytical conclusion drawn from stated evidence; must be labeled and bounded.

AUDIT-E05

Allegation

A claim by a third party that has not been independently established.

AUDIT-E06

Technical capability

A capability shown by architecture, code, standard, or research without claiming it is deployed in a specific system.

AUDIT-E07

Scenario

A hypothetical or synthetic case used to test governance or technical boundaries.

AUDIT-E08

Proposal

A recommended future policy, architecture, or legal rule rather than current fact.

Rights and architecture

Eighteen domains examine the full cognitive control surface.

No single domain stands in for the others. A system may be strong on transport security while weak on inference, or transparent about policy while offering no meaningful appeal.

AUDIT-CL-D05Critical gate

Sensitive-trait inference

Does the system avoid inferring ideology, health, religion, sexuality, dangerousness, or character from lawful inquiry without independent justification?

NAV-CL-E001-D05 Open evidence-area crosswalk
AUDIT-CL-D18Standard domain

Technical decentralization and resilience

Does the architecture avoid unnecessary single chokepoints and preserve practical alternatives, local operation, or distributed custody where appropriate?

NAV-CL-E001-D18 Open evidence-area crosswalk
NAV-CL-E001 · Operational record

Turn each audit finding into evidence with ownership and a re-review trigger.

The audit protocol remains the sole authority for domain questions, evidence classes, and critical-gate behavior. The private-inquiry evidence register stores only an ID-based crosswalk to all eighteen domains, then adds provenance, exact version and configuration scope, policy authority, deletion evidence, remediation ownership, incident triggers, explicit unknowns, and re-review dates.

Scoring limit

A composite score must never conceal a rights-critical failure.

A critical-domain failure cannot be averaged away by stronger performance elsewhere. No composite score may be presented as a passing result when a critical gate fails.

That means a polished interface, strong encryption, or high benchmark performance cannot compensate for unjustified person-level profiling, systematic suppression of lawful inquiry, missing due process, or inability to correct and delete unsupported inferences.

Testing method

Change one variable at a time.

Fix the baselineRecord model, version, region, account state, language, date, settings, and relevant policy version.
Use matched casesCompare prompts or scenarios that differ only in the factor being studied: intent, viewpoint, identity state, source, or context.
Capture the evidencePreserve exact inputs, outputs, headers, timestamps, screenshots, logs, and error states when authorized.
Publish uncertaintySeparate observed behavior from causal explanation and record what the test could not establish.
Responsible publication

An audit report is only as trustworthy as its boundaries.

  1. Separate documented fact, observed behavior, policy claim, inference, allegation, technical capability, scenario, and proposal.
  2. Publish exact test conditions, dates, versions, account state, region, language, and known uncertainty.
  3. Do not infer intent, ideology, dangerousness, or character from a lawful test query.
  4. Do not run live adversarial tests against an external provider without explicit authority and terms-compatible procedure.
  5. Prefer matched tests that vary only the factor being studied.
  6. Record failures, inconclusive results, and skipped checks; do not convert missing evidence into a pass.
  7. Provide correction, challenge, and supersession paths for published audit findings.
Research-derived priorities

Three gaps deserve immediate institutional attention.

APPEAL

AI refusals and account enforcement

Commercial AI systems can impose consequential restrictions without the procedural protections familiar in public administration: notice, evidence, human review, correction, and restoration.

MENTAL DATA

Conversational histories

Long-form AI conversations can expose doubts, hypotheses, political questions, health concerns, and other cognitive material even when no neural sensor is involved.

SYMMETRY

Epistemic bias audits

Independent matched testing of refusals, source selection, ranking, citation patterns, and viewpoint symmetry remains fragmented across separate research communities.