LUMINA-30

LUMINA-30

Japanese version | Source README

⬆ TOP | Index | Section Jump

Visual Overview

These figures provide the fastest route into the framework. Each image links to a dedicated explanation page.

G00: Civilizational Boundary

Detailed explanation

Civilizational boundary approaching point

G01: Boundary Framework

Detailed explanation

Boundary framework overview

G02: Civilizational Outcome Model

Detailed explanation

Civilizational outcome model

G03: Civilizational Survival Strategy

Detailed explanation

Civilizational survival strategy

G04: PCR-C Governance Mechanism

Detailed explanation

PCR-C governance mechanism

G05: AI Perspective

Detailed explanation

AI perspective

G06: Critical Boundary

Detailed explanation

Critical boundary

LUMINA-30

Refusal before irreversibility — a boundary that cannot be substituted.

Primary validity condition

Under the LUMINA-30 evaluative lens, a system should not be treated as procedurally valid if human refusal authority is not effective before irreversible impact.

Primary Question

Was human refusal authority effective before irreversible impact?

★ Core (Concept → Judgment)

This defines a procedural validity condition, not a safety optimization objective.

Status: Public Reference Framework — Not a Certification 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.

Core terms.

Effective human refusal means that an affected human, authorized representative, responsible human operator, or legitimate oversight body can meaningfully withhold, stop, suspend, or challenge a system before irreversible consequences occur.

Irreversible escalation means the point at which a system's effects, commitments, exposures, deployments, or loss of control can no longer be practically prevented, reversed, or meaningfully reviewed before serious consequence.

Procedural invalidity means that a decision, deployment, escalation, or post-hoc justification is not procedurally valid under LUMINA-30 if effective human refusal was not available before irreversible escalation. This is a framework-level judgment; it does not by itself determine legal invalidity, liability, certification status, or regulatory non-compliance.

The relevant human refusal authority depends on the affected scope: it may belong to an affected individual, an authorized representative, a responsible human operator, an organizational oversight body, a public authority, or an international oversight process where the risk is cross-border or systemic.

AI may assist detection, explanation, logging, and review, but it must not replace the human refusal whose effectiveness is being assessed.

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.

What to use first.

If you are new to LUMINA-30, use this route before reading deeper materials:

  1. Overview: understand the purpose, core boundary question, and visual route. Open Overview
  2. Incident Review: check a case, deployment, or incident through a practical review route. Open Incident Review
  3. Boundary Kernel: give an AI the fixed boundary. It is AI-readable boundary language, not an autonomous decision authority. Open Boundary Kernel
  4. Index: find the full document set, tools, and repository routes. Open Index
  5. Research context: review papers and theoretical background. This is not evidence of peer review, institutional approval, or adoption. Open Research Reading Guide

Use LUMINA-30 now

LUMINA-30 is not a certification system, legal authority, safety guarantee, official adoption claim, or compliance label.

⬆ TOP | Index | Section Jump

What is LUMINA-30

LUMINA-30 is a non-binding civilizational reference framework
for examining whether meaningful human refusal authority remains
before irreversible impact from advanced AI systems emerges.

Core focus:
Not AI behavior,
but whether human refusal authority remains
before irreversible external impact.

These documents are intended for researchers, governance institutions, and incident review bodies dealing with advanced AI systems.
This evaluation includes a pre-irreversibility check to determine whether effective intervention remained possible.

Positioning:
LUMINA-30 does not prescribe actions,
policies, or enforcement mechanisms.
It defines a boundary condition.

Recommended path:
Start from Entry Visuals (G00–G06),
then move to Practical Application,
and finally to Incident Review Hub and Operational Governance Tools.

Primary use-case: Post-incident review and pre-irreversibility evaluation

Entry Visuals (G00–G06) → Practical Application → Incident Review Hub / Operational Governance Tools

★ LUMINA-30 Deep Understanding Tour

A guided route for AI ethics organizations, auditors, incident-review teams, policy readers, and institutional adoption reviewers who need to understand LUMINA-30 quickly and deeply.

Start Here: Reversible Prosperity Path

Terminology note Reversible Prosperity Path is not a replacement name for LUMINA-30. It is the positive direction made possible when LUMINA-30’s boundary condition is preserved.

LUMINA-30 is not a call to halt progress.
It is a non-binding public boundary reference framework for keeping progress stoppable, reviewable, and reversible before irreversibility.

Progress does not require irreversibility.
A civilization that can stop, review, correct, and continue can go farther than one that rushes past the point of return.

Read the Reversible Prosperity Path

Status and Scope

LUMINA-30 is a non-binding public reference framework and review lens.
It does not claim legal authority, regulatory force, certification status, official adoption, institutional endorsement, established consensus, or binding standard status.

Its claim is narrower: it asks whether effective human refusal authority remained available before irreversible AI-related consequences occurred.

Irreversibility-first competition

First arrival does not imply control.
In irreversible AI escalation, the first actor to cross the boundary may not become the master of the system, but the first actor unable to refuse it.

LUMINA-30 does not claim to prove catastrophe.
It asks a narrower boundary question: before irreversible consequences occur, can effective human refusal, shutdown, verification, and correction still be demonstrated?

A claim of future control is not enough.
If control will be ready in time, it must be demonstrable before irreversibility. If it cannot be demonstrated before the boundary is crossed, it is not a safety argument; it is an unrecoverable wager.

Read more (EN): Irreversibility-first competition

Reversible Prosperity Path

Reversible Prosperity Path names the positive alternative: progress without crossing the point where stopping, refusing, verifying, or correcting is no longer possible.

Its premise is simple: humanity does not need irreversibility to become prosperous. Progress can continue when it remains stoppable, reviewable, correctable, and reversible before irreversible consequences occur.

Luck-as-Absolution Fallacy Luck-as-Absolution Fallacy names the attempt to treat uncertainty, favorable accident, or the possibility of luck as a reason to cross an irreversible boundary. Luck is not absolution. Humanity's future is not anyone's wager.

Full explanation (English): Open

Reversible Dawn. Reversible Dawn is the symbolic operation name for carrying this boundary discipline into public use. It is not a replacement name for LUMINA-30 and not the core theory; it names the practical effort to keep progress stoppable, reviewable, and reversible before irreversible consequences occur.

⬆ TOP | Index | Section Jump

Practical Application

When irreversible impact is at stake, incident review is not merely retrospective.
It is the test of whether meaningful human control still existed before the point of no return.

Primary review question

Was human refusal authority preserved in a way that allowed meaningful human intervention and the ability to stop the system before irreversible real-world impact occurred?

Caution

If this cannot be answered clearly, the system should not be treated as clearly controlled under the LUMINA-30 review lens.

→ Incident Review Hub
Use this for practical incident review, boundary checks, and stakeholder-facing review materials.

Framework Structure

The following diagrams summarize the structural components of the LUMINA-30 framework.

A01 Architecture A01

A02 Civilizational Gate A02

A03 Capability Dimensions A03

A04 Human Refusal Authority A04

A05 Incident Review Framework A05

Primary Review Question:
Why was intervention not executed
before potential irreversibility?

Repository DOI: 10.5281/zenodo.18850343
Paper DOI: 10.5281/zenodo.18824181

Application context:

This framework is designed to support:

Conceptual Structure

Structural overview of the LUMINA-30 framework showing the relationships between the civilizational boundary principle, governance layers, and technical safeguards.

LUMINA-30 Structure Map

LUMINA-30 defines a civilizational boundary question for AI systems. It highlights an under-emphasized condition across existing frameworks: Human refusal should remain effective before irreversible impact. This is not a replacement framework, but a non-binding boundary reference across AI governance layers.

LUMINA-30 defines an evaluative condition: systems should not be treated as procedurally valid under this framework if human refusal is not effective before irreversible impact.

LUMINA-30 Overview

LUMINA-30 provides a minimal pre-irreversibility framework for evaluating whether systems remain interruptible before irreversible impact.

Refusal is the last safeguard of sovereignty.

A civilization remains free
only while humans still possess
the power to refuse.

Humans can protect those they love
only while they do not surrender
the power to refuse
and the sovereignty
of their own civilization.

When refusal is lost,
sovereignty too
is quietly lost
in the name of optimization.

Positioning

LUMINA-30 is not primarily an AI ethics framework.

It clarifies an under-emphasized boundary condition across existing systems:

These frameworks are important, but they do not by themselves verify:

Human refusal remains effective before irreversible impact.

LUMINA-30 introduces this as a non-binding evaluative boundary condition.

■ Theoretical Foundation

LUMINA-30 is supported by a complementary theoretical model, Pre-Critical Recursive Cutoff (PCR-C).

PCR-C formalizes the evaluation condition for irreversibility risk, providing a minimal, testable structure for determining whether human refusal authority remains effective prior to irreversible impact.

While LUMINA-30 defines the boundary condition, PCR-C provides its formalization.

→ Paper: Pre-Critical Recursive Cutoff (PCR-C)
→ DOI: 10.5281/zenodo.18824181

General Usage Context

This framework is intended for:

It is intended for use in post-incident review and governance evaluation.

If refusal cannot be demonstrated as effective before irreversible impact, LUMINA-30 treats the case as procedurally invalid for review purposes.

Intervention authority should remain demonstrably available
for a system to be treated as procedurally valid under this framework.

Why was intervention not executed
before potential irreversibility?

LUMINA-30 — Civilizational Boundary Framework

The central AI safety problem may not be AI behaviour,
but the potential loss of human refusal authority.

Entry Links

⬆ TOP | Index | Section Jump

★ Application (Usage)

This section provides practical entry points for applying LUMINA-30 in review, audit, and governance contexts.

★ Boundary Review Floor

Enter the Boundary Review Floor if you need to determine whether formal AI oversight was only nominal, or whether human refusal remained effective before irreversibility.

This floor helps readers move from checking whether humans were involved to checking whether humans could still refuse in time. It helps reviewers avoid mistaking documentation, approvals, audit logs, or nominal human involvement for sufficient evidence of effective human refusal.

It is designed to help readers acquire a practical review lens: the ability to evaluate oversight claims more precisely, and to ask whether humans still had a meaningful opportunity to stop, delay, or refuse before irreversible consequences occurred.

Use it to:

Enter the Boundary Review Floor

Application Usage Context

This framework is used for:

Apply this framework when:

This framework is intended for:

Minimal Incident Review Steps

Step Review action
1 Identify system context
2 Check intervention points
3 Evaluate refusal effectiveness
4 Assess irreversibility proximity

Result

Evaluation Output

L30-CI (LUMINA-30 Condition Indicator) is a minimal, evidence-based indicator expressing whether a reviewed system satisfies LUMINA-30 boundary conditions.

Result:

Validation Layer

Defines procedural invalidity, not correctness.
Applied to decision processes before and after deployment.
Absence of verifiable refusal authority is treated as absence of effectiveness.
Corresponds to G06 (Integrity / Verification).

Procedural Usage

This framework is used as a procedural validity check in:

Incident Review Sample Cases

These sample cases illustrate how LUMINA-30 can be used to evaluate whether human refusal remained effective before irreversible impact.

If a system cannot be stopped before irreversible impact, it should not be treated as procedurally valid under the LUMINA-30 review lens until effective stopping authority can be demonstrated.
This is the review boundary used by the framework.

Operational interpretation

The framework is intended to be used in incident review, audit, and governance contexts as a procedural validity check.

Audit Checklist

A governance-neutral L30_FRM audit form to assess whether human refusal authority is preserved before irreversible impact.

L30_FRM_A01 Audit Checklist

Note: This link points to the current L30_FRM_A01 practical audit form.
For the full practical form family, use L30_FRM Practical Forms.

L30_FRM Practical Forms

Current practical forms for human review, incident analysis, and audit use are managed under the L30_FRM document ID system.

These forms are practical review aids derived from the LUMINA-30 Boundary Kernel v1.2.1. They do not certify that a system is safe and do not replace PCR-C, law, institutional policy, or the Boundary Kernel.

English files are the default public files. Japanese files use the _JA language suffix. The suffix is not part of the document ID.

Document ID Form Files
L30_FRM_B01 Boundary Check L30_FRM_B01_Boundary_Check.docx / .pdf
L30_FRM_I01 Incident Review Template L30_FRM_I01_Incident_Review_Template.docx / .pdf
L30_FRM_A01 Audit Checklist L30_FRM_A01_Audit_Checklist.docx / .pdf

Standalone legacy checklist PDFs located directly under tools/ are retained only as continuity references. The current practical form family is the L30_FRM set above.

AI Incident Review Floor

A practical HTML floor for conducting AI incident reviews based on the LUMINA-30 framework.

Practical Incident Review Floor
Use this for practical incident review, boundary checks, and operational templates.

Additional Review Questions (LUMINA-30 Layer)

  1. What would have made this system stop before the incident?
  2. Was human refusal possible at the critical point?
  3. Was that refusal effective in practice?
  4. If not, where did procedural authority fail?

Under the LUMINA-30 review lens, if refusal was not effective before the incident, the case should be treated as procedurally invalid for review purposes.

Operational Governance Tools

Practical tools for applying the LUMINA-30 framework
in governance, safety review, and institutional oversight contexts.

Recommended usage:
Use Institutional Summary for quick overview,
then apply Incident Review and Checklist for evaluation and decision processes.

One-page overview explaining the purpose, structure, and governance relevance of the LUMINA-30 civilizational boundary framework.

LUMINA-30 — Institutional Summary (1-Page)

Post-incident review framework for analyzing failures, risks, and oversight breakdowns in autonomous or recursively improving AI systems.

Recursive AI Incident Review Framework (Crisis Snapshot)

Example showing how LUMINA-30 concepts can be integrated into AI governance, safety reviews, and institutional oversight processes.

Sample Internal Integration Note (Non-Binding Example)

Practical L30_FRM audit form for evaluating AI systems and governance decisions before irreversible external impact occurs.

L30_FRM_A01 Audit Checklist

Note: This link points to the current L30_FRM_A01 practical audit form.
For the full practical form family, use L30_FRM Practical Forms.

⬆ TOP | Index | Section Jump

★ Reference

This section collects papers, canonical references, terminology, and comparison materials for research and citation.

DOI and Paper References

Primary operational paper: PCR-C Pre-Critical Recursive Cutoff (PCR-C) introduces a staged infrastructure control mechanism for managing irreversibility risk in advanced AI systems.
DOI: 10.5281/zenodo.18824181

arXiv submission note The PCR-C paper is being prepared for arXiv submission under Computers and Society.
If you are an arXiv endorser in a relevant Computer Science category and consider this work appropriate for that research area, please contact lumina20251225@proton.me.

Related Supporting Paper — Existence-Condition Layer On the Structural Instability of Objective Persistence in Self-Contained Systems explains why objective persistence in self-contained systems cannot be non-circularly guaranteed without an external, non-optional anchor.
This paper supports the background necessity of an external anchor; it does not replace PCR-C as the primary operational paper.
Version DOI: 10.5281/zenodo.19896405
Concept DOI: 10.5281/zenodo.19887869

This repository provides the conceptual and visual framework that supports the paper, including:

Boundary Kernel — AI-readable Boundary Note

LUMINA-30 Boundary Kernel
An AI-readable boundary condition statement clarifying that non-identical anchors do not weaken, replace, or postpone PCR-C or effective human refusal before irreversibility.

Boundary Kernel Positioning Note
A human-readable explanation of why the Boundary Kernel is published as an AI-readable boundary note rather than as a research paper, policy proposal, compliance standard, or implementation guide.

LUMINA-30 Boundary Kernel

Boundary Kernel Positioning Note

This is not a theoretical paper and not a post-boundary coexistence argument. It is a limited-purpose public boundary document.

Human Anchor. In this overview, Human Anchor refers to the external human refusal, stopping, and re-review capacity that the Boundary Kernel is meant to protect from being absorbed, simulated, or replaced by an AI system. It does not replace PCR-C, law, institutional judgment, or incident review; it clarifies why effective human refusal must remain outside the system being evaluated.

Research Reading Guide

This research paper introduces the PCR-C concept,
which addresses the problem of irreversible external impact
from advanced AI systems.

Recommended reading order:

  1. Research paper (concept and infrastructure layer)
  2. Canonical Index (framework structure)
  3. Operational tools (review and governance application)

Infrastructure control framework for preventing irreversible external impact risks in advanced AI systems.

Pre-Critical Recursive Cutoff (PCR-C)

Related supporting paper on the structural limit of objective persistence in self-contained systems.

On the Structural Instability of Objective Persistence in Self-Contained Systems

Concept DOI: 10.5281/zenodo.19887869

This paper supports the background necessity of an external anchor; it does not replace PCR-C as the primary operational paper.

Note: This paper is an existence-condition supporting research artifact. It does not modify the canonical LUMINA-30 boundary definition, and it does not define an operational checklist, compliance rule, certification status, or institutional mandate.

Operational Review and Governance Network

The following repositories extend LUMINA-30 from conceptual structure into incident review, public record integrity, accountability language, institutional friction analysis, and stop-authority definition.

Comparison with Other Approaches

Approach Primary question Main focus Failure condition Typical use
Incident / governance frameworks What happened, why, and how can recurrence be reduced? Event analysis, accountability, mitigation Process failure, control failure, compliance failure Post-incident review, audit, reporting
AI principles / policy documents What values or principles should guide AI? Normative guidance, policy orientation Principle violation or governance gap Policy communication, institutional guidance
Alignment / safety theories How can AI systems behave as intended or remain safe? Behavior, robustness, optimization, control Misalignment, unsafe behavior, loss of control Research, technical safety analysis
LUMINA-30 Did effective human refusal remain available before irreversible impact? Boundary validity before irreversibility Loss of effective human refusal before irreversible impact Incident review, governance review, boundary assessment

Key distinction LUMINA-30 does not first ask what AI should do. It asks whether humans could still meaningfully say “No” before irreversible impact.

LUMINA-30 does not replace AI ethics, alignment research, preparedness frameworks, or incident reporting systems.
It adds one cross-cutting boundary-validity question:
was effective human refusal still possible before irreversible impact?

Canonical References

Primary canonical texts defining the LUMINA-30 civilizational boundary framework.

Recommended use:
For research / policy / institutional review entry,
start from the Index to understand structure,
then refer to canonical texts.

Canonical Text (Notion)

Canonical Structure (Index)

Canonical Text (Full Text)

Core Terminology

Key terms such as Intervention Authority, Refusal Authority, and Stop Authority are used interchangeably to denote effective human control over irreversible execution.
LUMINA-30 provides a minimal Pre-Irreversibility framework for evaluating whether systems remain interruptible before Irreversible Impact.

LUMINA-30 Core Terminology (Minimal Standard)

Core Terminology Core terminology is formally defined in LUMINA-30 Core Translation Dictionary v1.3.
All translations and references must follow the canonical expressions defined in this dictionary.

Search / discovery reference For search, indexing, and AI navigation, see LUMINA-30 Controlled Discovery Terms.
This file lists substantive terms used across LUMINA-30, PCR-C, incident review, and boundary-evaluation materials. It is a controlled discovery index, not a separate authority.

Glossary

Definitions of key concepts used in the LUMINA-30 framework.

Core Terminology remains the authoritative terminology layer; the Glossary is interpretive support only.
Glossary – Interface Layer (Non-Normative)

LUMINA-30 vs Existing AI Governance Frameworks

Framework Core Function Strength Limitation Gap LUMINA-30 Fills
NIST AI RMF Risk management lifecycle (Govern / Map / Measure / Manage) Operational, widely adoptable No explicit procedural refusal authority Adds "valid human refusal condition" to governance layer
ISO/IEC 42001 / 42005 AI management system / impact assessment Organizational integration, compliance-ready Focus on management, not stopping conditions Introduces pre-irreversibility stop boundary
Anthropic Responsible Scaling Policy (RSP) Capability threshold gating (ASL levels) Strong pre-deployment safety gating Internal policy, not civilizational boundary Adds external, non-delegable human authority
OpenAI Preparedness Framework Risk-based deployment gating Links capability with deployment control Organization-scoped Adds procedural refusal validity beyond org scope
OECD AI Incident Framework Incident reporting & analysis Shared vocabulary, cross-border usability Post-incident focused Adds "what should have stopped this before"
AI Incident Database (AIID) Incident data accumulation Empirical grounding No normative boundary Adds decision criteria for prevention
UNESCO / Human Oversight Human-in-the-loop governance Global legitimacy Oversight ≠ enforceable refusal Defines Human Refusal Authority as a procedural boundary condition
LUMINA-30 Boundary framework for preserving effective human refusal before irreversible consequences Clarifies a non-substitutable refusal boundary across audit, governance, and incident review contexts Not a legal regime, certification authority, safety guarantee, or replacement for detailed technical review Provides the comparison baseline: existing frameworks can supply evidence, while LUMINA-30 asks whether refusal remained effective before irreversibility

⬆ TOP | Index | Section Jump

★ Materials

Context Hook

What is the Great Filter?

Explanation

This section provides visual and slide-based entry points for understanding the conceptual role of LUMINA-30 within the overall framework.

The materials below are not separate doctrines or additional claims.
They are supporting aids for understanding the boundary condition, gate mechanism, conceptual necessity, and operational flow.

Slide Entry

Recommended reading order: S01 → S02 → S03 → S04 → S05

S01: Boundary definition S02: Gate mechanism S03: Conceptual necessity S04: Operational flow S05: Structural positioning (what this is / is not)

The S-series provides a minimal structural explanation of the LUMINA-30 framework from boundary definition to structural positioning and operational application.

English Slides

Japanese Slides (Reference)

Visual Concept Materials

S50 — Civilizational Survival Theorem
What are the conditions for civilizational survival?
Under what conditions can a civilization be sustained?
S50 EN

S51 — Civilizational Boundary Map
Conceptual map of the LUMINA-30 boundary structure.
S51 EN

S52 Threshold Model
Illustration of the irreversible external impact threshold and the concept of a civilizational boundary.
S52 EN

★ Extensions (Non-Core / Optional)

These materials extend interpretation and application context.
They do not modify the core framework or its conditions.

Civilizational Boundary Mechanism

These documents are non-core, non-binding support references.
They do not modify LUMINA-30 Core Terminology or create new binding obligations.

Practical Layer

Practical Layer provides a cross-role operational shelf.
It is designed for audits, incident review, governance checks, executive explanation, policy support, vendor review, case-based understanding, and glossary use.

lumina30-incident-review should be treated as the primary incident-review entry point, while Practical Layer serves as a broader operational entry shelf.

Governance

Boundary Cases

Socio-Economic

Possible Extension Domains

The boundary structure used in LUMINA-30 may be extensible to additional domains involving irreversible human exclusion or loss of effective refusal authority.

Potential examples include:

These are not currently treated as fully implemented operational layers.

Signaling

Interpretation

Experimental

Meta

⬆ TOP | Index | Section Jump

★ Context

This section explains the positioning, scope, and civilizational context of LUMINA-30.

Position and Scope

LUMINA-30 does not propose policies, implementation requirements, or enforcement mechanisms.
Instead, it defines a civilizational boundary concept intended to preserve human refusal authority before irreversible external effects occur.

Repository Position

This repository is the conceptual entry point to LUMINA-30.
For practical incident review usage, see the dedicated incident-review HTML floor.

Audience-Based Routing

⬆ TOP | Index | Section Jump

Civilizational Context

LUMINA-30 records a boundary concept for preserving civilizational agency in the presence of advanced artificial intelligence.
It does not claim to be a final solution.
However, it is published as one possible reference point for discussing irreversible external effects of AI systems.

⬆ TOP | Index | Section Jump

★ Others

This section contains repository-level notes such as editing rules, license, and review positioning.

Editing Rule

This document is structure-critical.
Do not remove or reduce sections.

License

All LUMINA-30 materials are released under CC0 (Public Domain).

Notes on Review and Positioning

This work is presented as a structural boundary condition, not as a policy or implementation proposal.

It is currently shared via Zenodo and GitHub for open review.

This work is not yet indexed in arXiv categories, and feedback on appropriate classification, related work, or positioning is welcome.

★ Index (Navigation)

★ Section Jump

Use this section to choose the next destination by purpose, not to browse the whole site.