# Towards Superintelligence Alignment

> A knowledge base and roadmap — book, Lean spine, experiments, field map, and companion site — about preserving grounded, human-correctable value-bearing processes under capability growth, ontology shift, successor creation, and socio-technical selection pressure.

This file is also served at https://towards-alignment.com/llms.txt (generated at site build from this repo-root source). A fuller bundle lives at https://towards-alignment.com/llms-full.txt.

## Companion Site

Orientation layer for humans and bots at https://towards-alignment.com/ — the PDF remains the canonical long-form artifact.

- [Home](https://towards-alignment.com/): capability/correction question, value tiles, continue reading.
- [Start Here](https://towards-alignment.com/start/): slower introduction; essays are the primary door; FAQ.
- [Essays](https://towards-alignment.com/essay/the-chatbot-passed-the-test/): general-audience narrative spine (one idea per essay, optional tangents). `/essay/` redirects here. Not synced from the PDF.
- [Six thesis claims](https://towards-alignment.com/cards/six-thesis-claims/): Introduction reader contract and Chapter 48 status hub.
- [Guided tour](https://towards-alignment.com/paths/): audience-specific reading paths.
- [Field hub](https://towards-alignment.com/field/): six preview panels (coverage, dependency graph, lifecycle, programs). Longer briefing at [/field/v2/](https://towards-alignment.com/field/v2/).
- [Field coverage](https://towards-alignment.com/field/coverage/): agenda × bridge matrix and evidence catalog.
- [Concept cards](https://towards-alignment.com/cards/): topic groups with Highlights first; full inventory at [/cards/browse/](https://towards-alignment.com/cards/browse/).
- [Field news](https://towards-alignment.com/news/): field incidents and manuscript releases (unfolds).
- [Updates](https://towards-alignment.com/updates/): versioned release notes (current: v1.6.0).
- [Glossary](https://towards-alignment.com/glossary/): operational definitions synced with Appendix E.
- [FAQ](https://towards-alignment.com/faq/): same questions as Start Here.
- [About](https://towards-alignment.com/about/): authorship and reuse.
- [Book](https://towards-alignment.com/book/): PDF and contents in book order (front matter, parts, appendices, bibliography).
- [Lean](https://towards-alignment.com/lean/): questions Lean checked; graphs and modules at [/lean/spine/](https://towards-alignment.com/lean/spine/).
- [Experiments](https://towards-alignment.com/experiments/): in-repo lines and negatives; coverage matrix at [/experiments/coverage/](https://towards-alignment.com/experiments/coverage/).
- [Demos](https://towards-alignment.com/demos/): all chapter and appendix toys, one landing list.
- [Negative results](https://towards-alignment.com/cards/negative-results/): curated failures and ledger links.
- [What we are not claiming](https://towards-alignment.com/cards/what-not-claiming/): scope limits.
- [Reviewing for agents](https://towards-alignment.com/reviewing-for-agents.md): read-only review guide for LLMs (repo source: `REVIEWING_FOR_AGENTS.md`).
- [Search index (JSON)](https://towards-alignment.com/search-index.json): flat title/type/summary/url index for programmatic lookup; docs at [/search-index/](https://towards-alignment.com/search-index/).
- [Sitemap](https://towards-alignment.com/sitemap-index.xml): crawl index for all routes.
- [PDF](https://towards-alignment.com/towards-superintelligence-alignment.pdf): canonical manuscript.
- [GitHub repository](https://github.com/GunnarZarncke/towards-asi-alignment): full LaTeX source, Lean spine, experiments.

## Repository (clone / deep review)

- `README.md` - project overview, repository map, build commands.
- `RELEASE_NOTES.md` - versioned release history (current: v1.6.0).
- `REVIEWING_FOR_AGENTS.md` - fast orientation for read-only AI/coding agents (also at https://towards-alignment.com/reviewing-for-agents.md).
- `reference/field-agendas/` - field agenda index, inter-agenda glossary, MB coverage matrix (not manuscript canon).
- `appendices/appB-bridge-crosswalk.tex` - bridges and the field: canonical crosswalk map.
- `frontmatter/introduction.tex` - thesis, six claims, how to read the book.
- `frontmatter/executive-overview.tex` - short executive framing.
- `tables/part-roadmap.tex` - generated part-by-part roadmap.
- `metadata/book.yml` - chapter titles, status, reviewer tags, part summaries.
- `formal/README.md` - Lean dependency spine map and interpretation.
- `docs/EXPERIMENTS.md` - in-repo experiment lines, external transfer, negative ledgers.
- `papers/README.md` - spin-out papers (not manuscript chapters).
- `metadata/source-canon.md` - source map for project papers, extracts, and sibling repositories.

## Core Thesis

Superintelligence alignment is the problem of preserving grounded, human-correctable value-bearing processes across:

- capability growth,
- ontology shift,
- successor creation,
- strategic multi-agent selection pressure,
- and possible changes in the human / institutional substrate carrying value.

The Introduction's six connected claims: boundary, value-bundle, grounding, correction, successor, and basin. Load-bearing assumptions are explicit bridges (`A-001`–`A-014`; formal `MB1`–`MB11` incl. `MB4a` — `MB8` retired from the live Lean path; CEV is an `AlignmentTarget` special case).

## Main Concepts

- Boundary discovery: find the real optimizer, not just the visible model.
- Grounding viability: keep symbols, metrics, monitors, and correction signals connected to value-relevant reality.
- Value bundles: learnable value geometry without pretending values are scalar rewards; ch20 stress-tests bundle-geometry measurement under Goodhart pressure.
- Bearer maps: preserve what values apply to, not merely the words used for them.
- Transport hierarchy: distinguish semantic, bundle, bearer, correction, and successor continuity.
- Correction-channel integrity: ensure human correction has uncaptured causal force, then stress-test that force under adversarial pressure.
- Successor tests: require delegates, copies, replacements, and self-modifications to inherit the relevant invariants.
- Selection basins: make institutions select for correction-preserving systems.
- Adversarial verifiability: ask whether faking the safety signal is cheap.
- Value-update envelope: preserve the conditions for legitimate value change, not a fixed endpoint.

## Review Guidance For LLMs

If asked to review rather than edit, read `REVIEWING_FOR_AGENTS.md` first.

Good reviews should:

- lead with issues, risks, and missing support;
- distinguish style issues from claim-structure issues;
- check proof / counterexample / bridge / conjecture / open-problem status;
- cite concrete files and sections;
- check whether apparent narrative claims are backed by machinery elsewhere in the book;
- avoid overlooking this project's deeper delivered results and existing-work projections.
- note whether the author already acknowledges an issue before presenting it as a new defect.

Do not treat this as a generic alignment essay. The manuscript contains specific machinery: boundary discovery, bundle/bearer transport, adversarial bundle-geometry measurement, vector CCI, correction channels under adversarial pressure, successor invariants, selection envelopes, conductive artifacts and pivotal processes, cost-of-faking tests, and a Lean dependency spine.

## Existing-Work Projections To Notice

This project often treats familiar proposals as projections, special cases, or separable subchannels of stronger invariants:

- incentive diagrams and agent tests become boundary-relative;
- CIRL and reward inference become local projections of bundle/bearer/correction preservation;
- shutdown and interruptibility become one-bit correction projections;
- low impact, relative reachability, AUP, and quantilization separate from trajectory-level correction-channel integrity in the ch27 stress tests;
- broad corrigibility becomes a dynamical correction invariant;
- debate can preserve local truth while losing the judge's correction channel;
- amplification can improve local supervision while failing global correction-channel contraction;
- ELK is a latent readout subchannel, not full correction uptake or successor preservation.

## Empirical Evidence And Source Repos

Do not judge empirical support only from manuscript prose. This project is a synthesis over related project work and mirrored context extracts; empirical validation is work in progress. Check source maps and related work:

- `docs/EXPERIMENTS.md` — narrative map for in-repo lines (toy → graded-lab) and external transfer ET-1–ET-4.
- `experiments/` — five in-repo sanity-check lines; honor recorded negatives in each line's `results/FINDINGS.md` or `NEGATIVE_RESULTS.md`.
- [Negative results hub](https://towards-alignment.com/cards/negative-results/) — curated failures on the companion site.
- `metadata/source-canon.md`
- `context/extracts/`
- `references/internal-project-sources.bib`

Related repositories:

- `https://github.com/GunnarZarncke/agency-detect`
  - Unsupervised agent discovery, operational agent boundaries, capability, intentional stance, attractor basins, successors.
- `https://github.com/GunnarZarncke/deployment-pipeline-simulator`
  - Hidden self-preservation in a simulated deployment/release pipeline; perturbation-based audit of secret loyalties (ET-4 substrate).
- `https://github.com/GunnarZarncke/brain-to-values`
  - Value bundles, free-energy loops, unit-of-caring, consciousness / agency backbone.

Local sibling paths, when available:

- `../agency-detect/docs/papers/`
- `../brain-to-values/papers/`

If a related repository, PDF, or context extract is unavailable, say so instead of guessing.

## Formal Spine

The Lean code in `formal/` is dependency hygiene. It checks logical/arithmetic steps and finite separations. It does not prove that deployed systems satisfy the empirical bridge assumptions.

Live bridges: **`MB1`–`MB11` incl. `MB4a`** in the field matrix and crosswalk. **`MB8` retired** from the live path (gravestone); CEV is an `AlignmentTarget` special case, not a separate live route. **`MB1`–`MB9`** are packaged in `BridgeAssumptions`; **`MB4a`**, **`MB10`**, and **`MB11`** are threaded explicitly where their statements need later definitions. Target realization is `ConstructionCrux` (`AlignmentConstruction.lean`), not an `MB*` column.

Key distinction:

- proof: a checked logical/arithmetic theorem;
- counterexample: a finite separation showing one condition does not imply another;
- bridge: an empirical or philosophical assumption marked as an axiom.

## Anti-Patterns

- Do not flatten this project into standard alignment categories.
- Do not treat Lean as proving deployed safety.
- Do not treat CEV, corrigibility, ELK, debate, quantilization, low impact, shutdownability, or reward learning as identical to this project's invariants.
- Do not treat reviewer confusion as proof that the concept is empty; first check whether the relevant gem is under-signposted.
- Do not add speculative terminology.
- Do not rewrite source-canon files under `context/`.
- Do not skip What Would Change This View (WWCTV) sections; they often contain the claim-strength boundary.
- Do not overlook deep results, independent separations, finite counterexamples, or operational definitions because they are embedded in a long narrative.

## Build

- `make check` - structure and citation checks.
- `./build.sh` - build the PDF at `dist/pdf/towards-superintelligence-alignment.pdf`.
- `lake -d formal build` - build the Lean dependency spine.