Evidence, architecture, and public record.
A curated resource page for the proof surfaces behind Aurora-Lens: demonstration, precedence, implementation, research, and chronology.
Proof surfaces, not a filing cabinet.
These resources are selected to support the public claims made across the site: admissibility before consequence, governed refusal, auditability, and persistent-state reasoning.
Formal filings, public release sequence, implementation history, and evidence categories.
Submit requests and inspect admissibility decisions, continuation, and audit output in real time.
Documented public release, direct circulation, and repository dissemination artifacts.
What supports the claim?
The site should not ask visitors to accept governance as atmosphere. It points to public records, reproducible demonstrations, implementation artifacts, and audit behaviour.
Provisional filings, public demonstration, package releases, and live deployment.
Repository screenshots, dated outreach, package history, publications, and deployment traces.
Ambiguity containment, pediatric dosing stop, and emergency triage stop.
Every non-admitted outcome preserves the attempted action, governing decision, and continuation path.
The core frame.
Aurora-Lens is not a content filter. It is a release-boundary governance layer.
Checks whether candidate output is admissible before it becomes visible, actionable, or consequential.
Controls lawful continuation after refusal, ambiguity, revision, containment, or escalation.
Preserves the decision path so non-admitted outcomes can be inspected and replayed.
Maintains persistent discourse state so meaning is checked against what continues to exist, rather than reconstructed from sequence alone.
Evaluate locally with pip install aurora-lens[spacy] and python -m spacy download en_core_web_sm. See PyPI for release history.
Public research surfaces.
Keep the product site focused. Link outward for the longer record.