AnyAims (AA) Registry#

The AA registry collects open project-management tasks (Anything Aimed at doing later) for the balospe.com project in one central place, so they are easy to find rather than scattered across the site.

Each AA file is self-contained: it explains the task, the context that prompted it, and (where applicable) a ready-to-paste prompt that a fresh Claude session can use to execute the task. New AA files should follow the same self-contained pattern so they survive context compaction and session boundaries.

Placement rule (LLoL, 2026m08d04) — supersedes the earlier “migrate everything here” note

An AA file belongs next to the thing it plans. Only larger-than-that-thing tasks belong in this registry.

Paper-scoped — lives beside the paper, e.g. hell/mm/b/16/aa-b16-finalizing.rst (at paper level, so it survives oov3 -> oov4). See AA b16 — Finalizing the RiskyMAD paper (list of record, lives beside the drafts it plans).
Cross-paper / project-wide — lives here.
HELL’s own review system — lives in hell/aa/ (see the collision warning below).

This reverses the earlier note, which said AA files near their work “may eventually be migrated here”. They should not be: co-location is what makes a plan discoverable while the thing is being forged. Files already here stay here; nothing is being moved out.

AA files may live in HELL. The append-only rule in CLAUDE.md names source/matheology/hell/ll/ (LLogs) specifically — it has never applied to HELL as a whole, which also holds actively rewritten drafts under hell/mm/. And AA files do carry audit value: a task written down and not done is evidence of what was attempted, foreseen, or forgotten.

Terminology — POST AA and HELL AA

The name tells you the folder. That is the whole mnemonic.

POST AA — source/_post/aa/ (the POST System folder). Site-wide, and anything outside HELL. This registry.
HELL AA — source/matheology/hell/aa/. HELL’s own adversarial-review system.
paper AA — beside the paper it plans, e.g. hell/mm/b/16/aa-b16-finalizing.rst. Named, not numbered: its location already makes it unambiguous.

So “POST AA b19” is in _post/aa/b/19/ and “HELL AA b16” is in hell/aa/b/16/.

Warning

Two independently numbered AA series exist. Always qualify which one you mean.

This registry (AA) — source/_post/aa/b/NN/ — b11–b23 used. Project-wide and paper-related tasks.
HELL AA — source/matheology/hell/aa/b/NN/ — b10–b16 used, all still open (pending / deferred). Scope: HELL’s own adversarial-review system.

The numbers collide at b11–b15: a bare “AA b14” is either Adversarial review of the Zenodo mirror page (here) or Resolve Stale Link Debt (HELL AA). Write HELL AA bNN for that series. Whether to merge or renumber the two is an open decision for LLoL.

Naming convention#

Files follow the lettered-numbering layout specified in AHA/HELL.md. The directory and filename both carry the lettered ID:

_post/aa/b/<NN>/b<NN>-<short-topic>.rst

a1–a9 are reserved for greatest-hits retroactive assignment; b10 is reserved for the format template; b11+ are first usable entries (b11, b12, b13, …). Same scheme as the DD registry. Numbering starts at b11 to match the HEAVEN paper sequence convention. Both the directory name (b/11/) and the filename prefix (b11-...) carry the lettered ID so the ID stays visible in either browsing context.

Why lettered numbering, not timestamps? AA tasks are intended to be findable and citable across sessions. Timestamps encode “when started” which decays in usefulness; status lines inside the file capture “what state is the task in now.” Track time-of-creation and time-of-completion as content of the file (in the Status and Origin lines), not in the filename.

Each AA file should include:

A header VVN encoding who created it (per AHA/vvn-composition.md).
A Status line: TO RUN / IN PROGRESS / DONE / DEFERRED / ABANDONED (with reason).
An Origin line that identifies the session, prompt, or context that prompted creation (with a date), so anyone reading later can reconstruct the why.
A ready-to-paste execution prompt if the task is meant to be executed by a Claude session.

Currently active AA tasks#

The list-table below is the scannable summary of currently active AAs. Only entries that are not yet DONE appear here. Completed AAs and the session LLogs that recorded their completion are in AA Completed Log.

Active AAs (scannable summary)#
AA	Status	Title	One-line summary
b11	TO RUN	Evolvix integration into paper sequence	Two-tier strategy for citing the Prototype Evolvix Zenodo deposit and the balospe.com bridge across the broader paper sequence (b18a-b18e and beyond).
b12	TO RUN	Central intro page for the Balospe framework	LLoL to choose home and confirm scope; Claude or LLoL writes the page.
b15	TO RUN	VVN marker mistake prevention	Design decision needed (LLoL or a fresh Claude session) to prevent common VVN-marker errors.
b16	OPEN (multi)	SGIR (b19) paper finalization tasks	Container for 9 sub-tasks for finalizing the b19 SGIR pandemic paper. Includes a ready-to-paste prompt for resolving the `wwv-sgir-evolvix-study` toctree-citation-conflict in a fresh session.
b17	OPEN (3)	b16 revision — the non-paper leftovers	Stale b19 stability claim, `_`-escaping advice, assessor registry. The b16 paper tasks moved out on 2026m08d04 to AA b16 — Finalizing the RiskyMAD paper (list of record, lives beside the drafts it plans).
b18	OPEN (9)	Build-warning gating and link guards	Turn on Sphinx `-W`, triage the 890-warning backlog, test the untested `_redirects` splat rules, watch the probationary TELES path-segment clause, repair a public download button pointing at an uncommitted PDF.
b19	OPEN (7)	Matheo citation infrastructure	Cross-page bibliography capture (7 pages), 116 deprecated `Matheo-N` keys across 22 files, empty `[]` citations on 8 pages incl. a published floor page, and the inline display-style decision.
b20	OPEN (2)	Project-wide conventions to formalize	The Evolvix lettered-counting system, and edit-handoff rules so LLoL and Claude do not overwrite each other’s state.
b21	OPEN (3)	Deferred build and site tasks	Browsable full-page sitemap tree; 154 CRITICAL llog heading errors (blocks `-W` gating); the RFC 5321 FF slug-length limit.
b22	OPEN (3)	Refrain ordering, VVN shape, residual `-m` keys	The Rule 7 refrain runs reversed on 116 public sites (wording now decided, sweep parked, published papers off-limits); the Matheo VVNs use a non-spec bloated shape; 7 unresolved `-m` keys in HELL.
b23	OPEN (2)	Floor-pour curation guard and register	`make matheo-floor` used to destroy hand-curation silently (104 lines measured). A guard now refuses and rescues; doors, glance and the WorkInProgress pointers are generated. 37 on-ramp lines still manual.
todos	COLLECTOR	Collected `.. todo::` entries	The machine-collected half of AnyAims: every in-page `.. todo::` marker, gathered in one place by `sphinx.ext.todo`.

AA files that live elsewhere — pointers#

Under the placement rule, an AA file lives next to the thing it plans. This registry therefore does not hold them, but lists them here so they stay findable:

Important

Linking rule (LLoL, 2026m08d04): every standing AA file must be reachable from an AA index. When you create an AA file anywhere in the site, add a row to this table (and, if it lives inside HELL, to the HELL AA index too). An AA file nobody can find is a task nobody will do.

This is checked mechanically, not left to memory: make check-paths (Check D) fails if a standing AA file is not linked from an index. See AHA/linting.md.

Standing AA files that live outside this registry#
AA file	Scope	Note
b16 finalizing	the b16 RiskyMAD paper	The single list of record for everything still to do on b16. Inside HELL, so also listed in the HELL AA index.
JUB AA	the JUB framework	axioms ax15–ax25 formalization and review follow-ups
PET AA	the PET framework	carries `AA-PET-EDEN-a1` (k7 s7), the EDEN self-check integration
e7He AA	the e7He model	model-local aims
FORGE AA	the FORGE compiler	compiler-local aims
PROMY AA	the PROMY compiler	compiler-local aims
SISYF backlog	the SISYF compiler	plus implementation tasks
Compiler backlog	compiler POST work	AnyAims compiler backlog
Good News Pack AA	the Good News Pack	pack-local aims
HELL AA index	HELL’s own review system	`hell/aa/b/<NN>/` — b10–b16, separately numbered; see the collision warning above

Note

Two things deliberately NOT listed here, because they are not standing AA task lists:

AAA — AnyAllArrival (hell/aaa/, heaven/aaa/, heaven/study/aaa.rst) is a different register: in-transit arrivals, not tasks. It has its own index.
Dated ``aa-*`` session-prompt artifacts inside llogs (e.g. hell/ll/study/b/18/aa-b18-self-review-focus-prompt_2026m04d20_16h20.rst) are execution prompts belonging to their session, not standing lists. They stay with their llog.

Structure and archive (not task lists)#
Where	What
`AHA/aa-anyaims-sorting.md`	explains which AA file lives where, and why. Holds no tasks.
`AHA/HH/`	dated snapshots of AA files whose live content has moved. Never add tasks there.

Completed AAs#

Completed AAs and the session LLogs that record their completion are chronologically logged in AA Completed Log. The AA files themselves remain at their b/NN/ locations for full audit trail; they are linked from the DONE log via :doc: cross-references.