Whitepapers and technical publications are produced from governed LaTeX sources, projected to PDF, hashed for provenance and archived through Zenodo after explicit public-release authority.
| Publication | Area | Status | Persistent record |
|---|---|---|---|
| Human Authority Above Automated Execution A full academic treatment of authority-first governance for consequential automation. | Governance / AI systems | Published v2.0.0 | DOI 10.5281/zenodo.22106945 |
| Private-by-Default Public Infrastructure A full academic treatment of public proof, open interfaces, protected implementation, tiered scrutiny, contestability and institutional exit. | Institutional architecture / IP | Published v2.0.0 | DOI 10.5281/zenodo.22107351 |
| Evidence-Led Institutional Computing Provenance, tests, authority and deployment evidence as first-class infrastructure. | Assurance / Systems | Published v1.0.0 | DOI 10.5281/zenodo.22106634 |
| From Knowledge to Execution A synchronized model linking structured knowledge, formal theory, software, verification and public projection. | Research architecture | Planned | DOI on release |
| Technological Autonomy as Institutional Resilience Local compute, open interfaces, provider independence and sovereign edge infrastructure. | Infrastructure / Resilience | Planned | DOI on release |
The first institutional series establishes the public governance boundary: human authority, private-by-default implementation, and evidence-led execution.
Version 2.0.0 develops the authority-first model as an academic paper, connecting six execution states, goal lineage, provenance, uncertainty and release authority to human-factors research, systems safety and contemporary AI governance.
Version 2.0.0 distinguishes transparency, openness, accountability, interoperability and verifiability; defines fail-closed release control, evidence-bearing public proof and tiered scrutiny; and sets explicit limits on when protected implementation remains compatible with public accountability.
Provenance, tests, artifact identity, authority and deployment evidence are treated as infrastructure rather than post-hoc documentation.
A public paper is not just a PDF file. The publication object includes source, compiled artifact, identity, hashes, version, release authority and archival metadata.
LaTeX source is versioned and remains the primary publication representation.
PDF is generated through a repeatable build process with preflight validation.
Approved publications are deposited with governed identity metadata, artifact hashes and a persistent DOI.
Draft preparation can be automated. Public release remains an explicit act of authority.
Published Zenodo versions are immutable. Superseding work is released as a new version in the same archival lineage so the scholarly history remains inspectable.