Public records · source registry
Not only a narrative. Open the trail. This layer leads to code, records, versions and limitations. Its purpose is to let a reviewer move from a striking presentation to a verifiable source.
Source · claim · contradiction · decision Launch spark
Primary entry points
Public records. The links below lead to external entry points. Statuses and numbers should be updated only from current sources, never from the site's memory.
Published documentation GitBook research portfolio
Source The creator’s spArkHAT Research portfolio and linked project documents.
Status Published documentation covering AIOA, LSC, EagleEYE, spArkSWARM and collaboration.
Limitations Project-authored records explain scope and evidence boundaries; publication is not independent validation.
Static engineering showcase AIOA on Hugging Face
Source LuciferSun333 / AIOA — public Hugging Face Space.
Status Static showcase of the AIOA engineering project.
Limitations Not a production agent API, LIVE provider validation or autonomous execution service.
Unvalidated research showcase LSC on Hugging Face
Source LuciferSun333 / LSC — public Hugging Face Space.
Status Static presentation of an unvalidated scientific hypothesis, open to falsification.
Limitations Presentation and reproducibility materials do not establish a discovery or independent experimental confirmation.
Project-reported submission status Software Heritage preservation
Source Owner-reported Save Code Now requests for AIOA, LSC and the public EagleEYE showcase (19 October 2026).
Status preservation requests submitted; permanent SWHIDs unverified
Limitations A submitted request does not confirm a completed archive. No permanent SWHID is claimed; private EagleEYE code is excluded.
Source code AIOA / AOIA-Core The public repository for a local runtime: an architecture for evidence, provenance, contradictions, memory and human-approved execution.
Open repository ↗
Integrated memory module AIOA Memory Patch The CockroachDB hackathon line for durable evidence, memory, review and modular Knowledge HATs.
Open repository ↗
Latest Phase 1 milestone LSC 6.5.0.0 The confirmed Zenodo entry point used for the frozen Codex of Light milestone.
Open Zenodo ↗
Earlier frozen research record LSC freeze A stable entry point to the earlier frozen research track and predictions preserved before future analysis.
Open DOI ↗
Candidate mapping Aureon-1 Radar / MRAD The supplied Zenodo address is retained as a candidate until final project mapping is confirmed.
Open candidate ↗
Process audit MDLH / model agreement risk An audit of whether multi-model agreement can look like confirmation despite a shared source of uncertainty.
Open PhilPapers ↗
Creator profile LuciferSOL GitHub The public creator profile leading to the AIOA and LSC repositories and further experiments.
Open profile ↗
Reviewer workflow
Four questions before trust. An attractive interface should make verification easier, not replace it.
Where is the source? Open the code, DOI, data or tool record. Do not treat a summary as a primary source.
What is the status? Implemented, partial, planned, hypothesis and documentation-only must remain distinct.
What contradicts it? Alternative explanations and conflicting results must remain visible.
Who approves? Memory, models and tools provide material. Authority to act remains with the human.
Public promise We show code, records and limitations. Every important claim should have a verifiable entry point. Corrections are not removed from history merely because they disrupt the narrative. Biological metaphors are design inspiration, not evidence of effectiveness. Public boundary We do not publish certainty created by presentation alone. No hard test counts without a current source. No discovery claims without independent validation. No equation of model consensus with independent confirmation.
Correction channel
Found a dead link, an error or an overstated claim? Send a specific correction with its source. That message is more valuable than praise alone.
Send correction →
OUR WORK WITH AI
How we build AIOA with Codex. One goal, successive iterations: a plan, working code, tests and review. This is how we develop AIOA and bring NonZero into a shared repository.
11 November 2026 Integration in progress
Hours on one task. Progress across sessions. A complex coding task can take hours; a larger integration can span several days and sessions. With Codex, we carry one goal through implementation, tests, corrections and independent review.
Checkpoints preserve the plan and change history so work can resume. Readiness is assessed through working code and reviewed results.
NonZero → AIOA-spArkHAT We are integrating the full NonZero feature scope into the main AIOA-spArkHAT repository. The goal is one maintained Hybrid Core, with shared permissions, human approvals and execution records.
Integration and parity checks are still in progress. Completion depends on the required tests, review and release approval.
The time described covers an engineering process carried across successive sessions.