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.

Note

This is the centralized location going forward. Older AA files that still live near the work they describe (e.g. source/matheology/hell/mm/b/19/si/aa-sgir-paper-tasks_2026m04d18.rst) may eventually be migrated here too — but only when LLoL decides such a migration is worth the effort. Do not auto-migrate without asking.

Naming convention#

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

_POST/AnyAims/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.

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.