AA b20: project-wide conventions still to be formalized#

Status: OPEN
Scope: whole project. Not HELL-specific and not paper-specific, so it belongs in this
registry under the placement rule.
Origin: migrated 2026m08d04 from AHA/aa-open-tasks.md entries
AA-AHA-counting-a1 and AA-AHA-edit-handoff-rules-a1, which emerged from AHA
documentation sessions.

Task list#

k	s	Task	Notes
k4	s1	Formalize the Evolvix lettered-counting system (a/1–9, b/10–99, …).	The numbering used in HELL’s con/pro structure, in the DD and AA registries, and in the `b/<NN>/` directory layout follows a letter-prefix convention where each letter spans a power-of-ten range. It needs a formal specification so future sessions and compilers apply it consistently. Details live in LLoL’s head — ASK before implementing. Partially documented at DD b11 and in `AHA/HELL.md`.
k4	s1	Design a convention for WHO edits WHAT, so LLoL and Claude do not overwrite each other’s state.	This problem exists in any repo where LLoL hand-edits files that Claude also maintains, and vice versa: either side can silently clobber what the other “remembers” — stray manual edits that read as corruption, or a Claude rewrite that drops a manual change. Flagged after a live edit collision; the same task is tracked in the sibling `balospe-launch` repo as `edit-handoff-rules`. Evolvix used a simple `-busy.txt` / `-sent.txt` handoff marker — too coarse for the mixed doc-types here (append-only LLogs, BB current-best files, DesignDocs, source `.rst`). Design: per-file-type ownership + a lightweight lock/handoff signal + a re-read-before-edit rule. ASK LLoL; details in LLoL’s head and `balospe-launch/AA/aa-launch.md`.

Note

A partial mitigation already exists for the second item, added 2026m08d03–04: make check-paths (see AHA/linting.md) detects when a reference and its target have drifted apart, which catches one common symptom of an edit collision — though not the collision itself.

AA b20: project-wide conventions still to be formalized#

Task list#

See also#