# Private Inquiry Evidence Register **Register:** `NAV-CL-E001` **Release:** `1.19.0` **Pathway step:** `NAV-CL-P001-S05` **Classification:** non-certifying operational template ## Boundaries This register is an operational crosswalk and template. It does not amend AUDIT-CL-001, does not replace any implementation kit, does not create a certification, and does not establish legal compliance or external-provider behavior without direct evidence. Do not enter raw lawful queries, prompts, reading histories, drafts, inferred beliefs, sensitive-trait profiles, or person-level curiosity records. Record system controls, bounded observations, synthetic tests, policies, contracts, receipts, owners, limitations, and review events instead. **Critical-gate rule:** A failed critical AUDIT-CL-001 domain must remain visible and blocks passing, certified, compliant, safe, or equivalent favorable summary language. It cannot be averaged away, hidden by unavailable evidence, or converted into a favorable composite score. ## Register scope - Institution or team: ______________________________________________ - Service, system, or decision boundary: _____________________________ - Deployment context and region: ____________________________________ - Review period: ____________________________________________________ - Accountable owner role: ___________________________________________ - Explicit exclusions and reason: ___________________________________ ## Claim-level record Create one copy of this section for each material claim or control. Do not combine unrelated claims into one favorable conclusion. - Record ID: ____________________ - Register ID: `NAV-CL-E001` - Evidence area ID: ____________________ - Control or claim: _________________________________________________ - Evidence status: supported / partially_supported / unsupported / contradicted / unavailable / not_applicable / not_reviewed - AUDIT evidence class IDs: _________________________________________ - AUDIT domain IDs: _________________________________________________ - Implementation kit IDs: __________________________________________ - Evidence locator: _________________________________________________ - Known unknowns: ___________________________________________________ - Evidence unavailable: _____________________________________________ - Critical-gate failures: ___________________________________________ - Limitations: ______________________________________________________ ### NAV-CL-E001-F01 — Provenance Make every material claim traceable to a source, observation, custodian, collection date, and integrity reference so a reviewer can distinguish evidence from assertion. Privacy limit: Do not preserve raw lawful inquiries, named reading histories, prompts, drafts, or inferred beliefs merely to prove provenance. Prefer system-level records, bounded samples, synthetic tests, and redacted receipts. Fields to complete: `record_id`, `control_or_claim`, `evidence_status`, `evidence_tier_ids`, `evidence_locator`, `provenance_source`, `provenance_custodian`, `collected_on`, `integrity_reference`, `known_unknowns`, `limitations`. ### NAV-CL-E001-F02 — Configuration and version scope Bind findings to the exact system, model, release, configuration, region, account state, data flow, and test date that produced the evidence. Privacy limit: Describe configuration and test conditions without embedding a person’s lawful inquiry history or exporting production cognitive dossiers. Fields to complete: `system_or_process`, `product_or_model_version`, `build_or_release`, `configuration_scope`, `deployment_region_or_context`, `test_account_state`, `test_date`, `data_flow_scope`, `retention_scope`, `known_unknowns`, `limitations`. ### NAV-CL-E001-F03 — Policy authority Identify the rule, decision body, approval date, scope, vendor obligation, exception, and sunset authority that governs the control being claimed. Privacy limit: Authority records should govern data and power; they should not become a justification for collecting more inquiry content than the control requires. Fields to complete: `policy_or_authority_title`, `policy_or_authority_locator`, `approving_body_or_role`, `approval_date`, `effective_date`, `authority_scope`, `vendor_clause_scope`, `emergency_exception_scope`, `sunset_or_expiry`, `limitations`. ### NAV-CL-E001-F04 — Deletion evidence Record what data or inference was deleted, under which rule, by which method, when deletion completed, how downstream copies were addressed, and what receipt or test supports the claim. Privacy limit: A deletion record should prove control operation without retaining the deleted inquiry content inside the evidence register. Fields to complete: `data_or_inference_class`, `deletion_rule`, `deletion_method`, `deletion_completed_on`, `deletion_verification_method`, `downstream_deletion_status`, `deletion_receipt_or_log`, `exceptions_or_holds`, `limitations`. ### NAV-CL-E001-F05 — Remediation ownership Give every finding an accountable owner, bounded corrective action, due date, retest method, challenge state, and closure evidence. Privacy limit: Assign responsibility for systems and controls, not suspicion scores or labels attached to people because they asked lawful questions. Fields to complete: `finding_or_issue_id`, `remediation_owner_role`, `remediation_action`, `priority_or_gate`, `due_date`, `retest_method`, `retest_date`, `challenge_or_appeal_state`, `closure_evidence_locator`, `residual_risk`, `limitations`. ### NAV-CL-E001-F06 — Incident triggers Predefine the event, threshold, owner, containment action, affected evidence areas, notification duty, and re-audit scope that reopen the register after harm or material change. Privacy limit: Incident response must target a defined failure or harmful event; it must not treat curiosity, privacy-tool use, or controversial lawful inquiry as an incident by itself. Fields to complete: `incident_trigger`, `trigger_threshold`, `observed_on`, `incident_owner_role`, `containment_action`, `affected_evidence_area_ids`, `notification_or_notice_duty`, `reaudit_scope`, `incident_record_locator`, `limitations`. ### NAV-CL-E001-F07 — Re-review dates Preserve the last review, next review date, lifecycle assumptions, material-change triggers, monitoring owner, and supersession chain for every material claim. Privacy limit: Review schedules should track controls, versions, authorities, and incidents—not maintain a longitudinal profile of what named people read or ask. Fields to complete: `last_reviewed_on`, `next_review_date`, `review_cadence`, `material_change_triggers`, `lifecycle_assumptions`, `monitoring_owner_role`, `supersedes_record_id`, `superseded_by_record_id`, `review_outcome`, `limitations`. ## Critical-gate review - Critical AUDIT-CL-001 domains referenced: _________________________ - Failed critical domains: __________________________________________ - Passing/favorable summary blocked? yes / no - Remediation owner and due date: ___________________________________ - Retest condition: __________________________________________________ ## Publication and confidentiality - Public evidence: ___________________________________________________ - Independently reviewable confidential evidence: ____________________ - Confidentiality basis: _____________________________________________ - Evidence that remains unavailable: _________________________________ - Public explanation of unavailable evidence: ________________________ ## Supersession and re-review - Prior record superseded: ___________________________________________ - Last reviewed: ____________________ - Next review: ____________________ - Material-change triggers: __________________________________________ - Incident triggers: __________________________________________________ - Monitoring owner role: _____________________________________________ ## Sign-off record Prepared by role: ____________________ Date: ____________________ Reviewed by role: ____________________ Date: ____________________ Decision authority role: ______________ Date: ____________________ This sign-off records responsibility for the bounded review. It is not a certification, endorsement, legal-compliance determination, or security guarantee.