LUMINA-30 Index

🧭 Central Square

Choose where to go in the LUMINA-30 repository network.

Not a certification system or adopted standard LUMINA-30 is a public reference framework for evaluating whether effective human refusal remains possible before irreversible escalation. It is not a certification system, not an adopted legal standard, and not evidence of institutional approval. Its current role is to provide structured concepts, review templates, and AI-readable boundary language for third-party examination, discussion, and possible use.
First-visit flow

LUMINA-30 is a boundary question for AI governance: before escalation becomes irreversible, can accountable humans effectively refuse, stop, verify, or redirect the system?

1. Start by Concern

Find the entry point that matches why you came here.

Start by Concern

2. Decision Record Question

Use one meeting-ready question in an AI review, audit, procurement check, governance discussion, or incident review.

Open the meeting card

4. Incident Review

Review a deployment, near miss, public case, or incident and ask whether accountable humans could still stop before irreversibility.

Open Incident Review

5. You do not need to read everything today

If the boundary question makes sense, take one decision-record question back to a real review, meeting, audit, procurement check, governance discussion, or incident review.

Take the question back

6. FAQ / Expected Questions

Check common misunderstandings and objections after you understand the entry point.

Open FAQ / Q&A

7. Read the Full Overview

Use the full overview for returning readers, internal explanation, objection handling, or deeper reading.

Read the Full Overview
You do not need to read everything today If the boundary question makes sense, the most useful next step is not to read every document. Take one decision-record question back to a real review, meeting, audit, procurement check, governance discussion, or incident review.
Before this AI deployment, escalation, or dependency becomes irreversible, can accountable humans effectively refuse, stop, verify, or redirect it?
If you need to explain the idea or respond to objections inside your organization, return here and use the FAQ, One-Question Pilot, and Full Overview.

LUMINA-30 Landmark Map

If you are not sure where to go next, return to the Central Square. LUMINA-30 can be navigated by role and landmark, not by repository name.

🔭 Full Overview Deck

For returning readers and deep reading after the entry point is clear.

(repo: lumina-30-overview)

🔭 Read the Full Overview

🛑 Stop-Authority Gate

Check whether a responsible human can still stop, refuse, pause, or roll back.

(repo: stop-authority-reference)

🛑 Open Stop-Authority Gate

📦 PDF Archive

Check fixed PDFs and preserved evidence files.

(repo: Lumi30-PDF-Archive)

📦 Open PDF Archive

What to use first

Use this route when you are new to LUMINA-30 or when an external reader asks where to begin. Start with a concrete entry route, not the full document set.

1. Start by Concern

Find the entry point that matches why you came here.

(repo: Lumi30-Index / start-by-concern)

Start by Concern

2. Decision Record Question

Use one meeting-ready question in an AI review, audit, procurement check, governance discussion, or incident review.

(repo: Lumi30-Index / decision-record-question)

Open the meeting card

4. Incident Review

Review a deployment, near miss, public case, or incident and ask whether accountable humans could still stop before irreversibility.

(repo: lumina30-incident-review)

Open Incident Review

5. You do not need to read everything today

Take one decision-record question back to a real review, meeting, audit, procurement check, governance discussion, or incident review.

(repo: Lumi30-Index / take-home flow)

Take the question back

6. FAQ / Expected Questions

Check common misunderstandings and objections. Use this after the entry point is clear.

(repo: Lumi30-Index / Q&A)

Open FAQ / Q&A

7. Read the Full Overview

For returning readers, internal explanation, objection handling, and deep reading.

(repo: lumina-30-overview)

Read the Full Overview

8. Deep reading routes

Use AI Briefing and Canonical Documents only when you need deeper context.

(repo: Lumi30-Index / Canon)

AI Briefing Canonical Documents

Primary routes

Read the Full Overview

Use the full overview after the entry point is clear, especially for returning readers, internal explanation, objection handling, and deep reading.

🔭 Read the Full Overview

Practical and AI-readable routes

Controlled Discovery Terms

Use this for controlled search, discovery, and machine-readable terminology.

🤖 Open Discovery Terms

Canonical source archive layers

These pages provide HTML access to preserved source texts in the Index repository. They are source archives, not certification or approval records.

Operational / Mathematical Archive

Mathematical and operational-control source text concerning recursive self-reconstruction limits.

📜 Open Operational Archive

Mediation / Translation Layer Archive

Mediation and translation-layer source text for institutional understanding.

📜 Open Mediation Archive

Source and preservation

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

📜 View Markdown source on GitHub

Use, citation, 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.