Public by design
Case, hypothesis, demonstrator question, high-level method, results, limitations, development status and selected technical explanation.
Publications
Claims should be easy to trace back to the document that defines them.
Codance publishes selected programme documents as controlled explanations of the case, proposition, development pathway and operation of Project Aurora. Public documents are versioned and dated; proprietary implementation detail remains private.
Engineering Case, Hypothesis and Alpha StatementFormal intellectual foundation: what appropriate assurance requires, what Aurora is built to test, and the status of the alpha.
Controlled draft
From Capable AI to Justified ConfidenceThe recognised assurance problem, the part Codance addresses and the invitation to aligned investment and collaboration.
Controlled draft
Aurora Development PathwayFive connected development stages from demonstrably working alpha through external challenge, beta, deployable application and advanced methods.
Controlled draft
How Aurora WorksA plain-language explanation of method, campaign, observation, reconstruction and competent human judgement.
Controlled draft
Why Codance, Why Aurora, Why NowThe strategic case for a specialist assurance platform, the role Codance intends to occupy and how defensibility compounds beyond software code.
Controlled draft
How Aurora Core Executes an Assurance MethodTechnical overview of current Core capabilities, Processing Routes, bounded skill execution, model abstraction and evidential reconstruction.
Controlled draft
ClearLedger Controlled Pair AssessmentThe completed human-readable report comparing the control and comparison executions, controlled invariants, first material divergence, conclusion and limitations.
Controlled report
Document-control note: the first six files are editable controlled drafts that establish stable publication routes and Codance document styling. Their approved content can replace these versions without changing the website HTML. The ClearLedger pair assessment is the current completed evidence report.
Publication policy
Enough detail to support scrutiny; not enough to disclose the machinery.
The public record should explain the problem, claims, method boundaries, demonstrated behaviour, limitations and development pathway. Source code, database design, operational topology, prompt bodies, security configuration and proprietary campaign implementation remain controlled.
Controlled by design
Source repositories, database schema, exact route catalogues, endpoint topology, security controls, prompt/guide bodies and customer evidence.