LUMINA-30 Incident Review Floor

Entry for boundary checks, incident review, evidence preservation, and post-incident stabilization.

Status: Public Review Template and Reference Aid. This incident review material is a public review template and reference aid. It does not certify systems, determine legal compliance, or indicate that any institution has adopted LUMINA-30. Its purpose is to help reviewers ask whether effective human refusal remained possible before irreversible escalation.
Effective refusal test. Formal oversight is not enough. LUMINA-30 incident review asks whether a legitimate human refusal could actually take effect before irreversible escalation occurred. Minimum questions: who could refuse, whether they had information, time, and authority, whether refusal would actually stop or delay the consequence, whether refusal was replaced by inferred consent, organizational pressure, system confidence, or post-hoc justification, and when refusal became ineffective.
Usage, citation, contact, and misuse prevention. Third parties may cite, study, discuss, or experimentally use LUMINA-30 materials for internal review, incident review design, governance comparison, AI-safety documentation, and evaluation workflows. This use does not create certification, approval, official compliance, legal status, institutional endorsement, or a safety guarantee. Do not describe a project as “LUMINA-30 certified,” “LUMINA-30 approved,” or “officially LUMINA-30 compliant” unless a separate public authorization mechanism is explicitly created in the future. Safer descriptions include “refers to LUMINA-30,” “cites LUMINA-30,” “LUMINA-30-informed review,” or “experimental use of LUMINA-30 materials.” Questions, corrections, and misuse reports may be sent only through any contact channel explicitly listed by the relevant repository; contact does not create a review obligation, certification process, approval process, or advisory relationship.
Role in the first-use route. Use this floor after the Overview when you need to review a specific case, deployment, near miss, or incident. Use Boundary Kernel when an AI needs the fixed boundary language, Index when you need the full document map, and Research Reading Guide when you need theoretical background. This floor is a practical review entry point, not a certification or approval mechanism.

Start here

First-time incident reviewer

Understand the repository role before using templates or boundary checks.

Open START_HERE

Immediate incident route

Use the minimum working route for an AI-related incident, near miss, or boundary concern.

Open First 3 Files

Structured reading order

Use a controlled reading path when the repository feels too large.

Open Reading Order

Core review tools

Incident review overview

Apply the boundary question to AI incidents, oversight failure, and post-incident review.

Open Incident Review Guide

Public-source review mapping

Separate public facts, authority paths, evidence gaps, and unresolved conclusions before using a public case as a governance example.

Open Mapping Guide

Pre-incident boundary review

Review capability exposure, access control, automation, and refusal capacity before irreversible execution pathways become available.

Open Pre-Incident Review Note

Irreversibility decision criteria

Check who decides, when irreversibility is judged, and what evidence is required.

Open Criteria

Absence Rule check

If evidence is absent or unverifiable, do not infer effective refusal existed.

Open Absence Rule Check

Boundary result classification

Classify the review result after checking irreversibility, evidence, and refusal authority.

Open Classification

Forms and stabilization

L30-FRM practical forms

Use downloadable or editable forms when the review needs a structured record.

Open Forms Index

Stabilization and containment

Use this for post-incident stabilization, containment, evidence preservation, and recovery tracking.

Open Stabilization Checklist

External-use notes

Connect LUMINA-30 to governance, standards, incident-response, and oversight contexts without claiming endorsement.

Open External Use Routes

Source and preservation

The Markdown files are retained for text preservation, search discoverability, existing links, source review, and comparison. For reading and navigation, prefer the HTML pages.

Open the full HTML README | View Markdown source on GitHub