AIMS Plotter — Phase 3 Tasks#

Note

Living task tracker. This file collects tasks identified during Phase 2I that belong to Phase 3 (content deployment and beyond). Append new tasks as they are discovered. Mark tasks done with a date when completed. This is not an llog — it may be reordered and edited for clarity.

Last updated: 2026-03-25

See also: AHA doc Section 18 (AnyAims Remaining) for shorter-term action items tied to the current design document: Links for Matheology BEST Names Design

Conceptual Formalization#

  • [ ] Define KUFIR (Knowledge-Uncertainty Feedback Integration Refinery). Formalize the invisible pipeline that governs how doubt becomes evidence, evidence becomes structured chronicle, and chronicle becomes reasoning that changes the system. Introduced informally in AHA doc Section 16.1 (Lifecycle, stages 2–4). Phase 3 should give it a precise description — not necessarily a POST code or registry entry, but a clear enough articulation that agents and contributors can follow it.

  • [ ] Define KPR (Knowledge Pipeline Refinery). Short-name alias for KUFIR. Decide whether both names are needed or whether one suffices. If both are kept, clarify when to use which.

  • [ ] Formalize the Seed/Feed/Grow/Reap lifecycle model. The AHA doc (Section 16.1) describes the agricultural metaphor in prose. Phase 3 should produce a more structured specification: entry/exit criteria for each stage, required artefacts, who (or what agent role) is responsible at each stage.

  • [ ] Formalize FLAMES coverage categories. FLAMES (FeedbackFlows, LabLogs, LifeLogs, AnyAims, MockupModels, EnclosedExperiments, StableSystems) defines what HELL’s Cons and Pros may cover. Phase 3 should clarify boundaries between categories and how they map to POST codes.

  • [ ] Formalize the PoE/PoC/PoR/PoT/PoU pipeline stages. Place of Evidence, Place of Chronicling, Place of Reasoning, Place of Translating, Place of Using — the five-stage pipeline described in AHA Section 16.1. Phase 3 should define each stage precisely, including what artefacts live at each stage and how transitions are triggered. The “Place of” naming emphasizes data-locality and the fluid, ongoing nature of each activity.

Architecture Decisions Deferred to Phase 3#

  • [ ] Resolve BREACH 5.2 — .. include:: directives pulling files with their own labels may cause label collisions. Deferred until after the big integration run or its cleanup.

  • [ ] Review PoR fields against 7Sp DOISI designs (AA-2 from AHA Section 17.2) before finalizing the PoR field structure. (Moved from AHA Section 11.2.)

  • [ ] Tech-debt Jubilee argument for recompile cycles. Add the argument that accumulated link debt requires periodic global reconciliation to the Jubilee theological discussion. (Moved from AHA Section 11.2.)

  • [ ] Decide on D2 chaining depth based on integration evidence collected in compiler/ee/d2-chaining-evidence.rst.

  • [ ] Decide whether Pet needs con/pro based on integration evidence collected in compiler/ee/d1-d2-testing-matrix.rst.

  • [ ] Resolve PoR field #40 name collision (model) based on evidence in compiler/ee/por-field-collision-check.rst.

  • [ ] Review PoR field real-world usage census (AA-5) after the OOv1→OOv2 migration. Decide which fields to keep, merge, drop, or add based on empirical data collected in compiler/ee/por-field-usage-census.rst. Includes review of proposed new fields discovered during migration.

  • [ ] Harmonize pipeline stage names in older HELL content. hell/pro/b/38 uses older names (Chronicling, Using) which are now canonical, but the OOv1 llog (llog_2026m03d19c_opus-ultrathink-reply-3-for-jubilee-argument.rst) still has “Point of Evidence/Reasoning/Translation” (append-only, not editable). Consider adding a correction note to that llog.

Publication Renumbering#

  • [ ] Design the mapping file format and renumbering script. The mapping (old→new for every element) must be machine-readable. The script must update all labels, :ref: links, prose references, HELL citations, and compiled pages in one pass. See DD 19.7.

  • [ ] Expert sub-type renumbering. Find a way to make renumbering work cleanly for expert-level sub-types (lemmas, corollaries, assumptions accessed via D2 chaining) — if possible without breaking the system. Sub-types are syntactically children of their parent, so renumbering the parent should carry them automatically, but edge cases need testing.

  • [ ] Apply D2 registry changes from DD 19.7: add obs (Observation), rename rl → ru (Rule), drop sc (Schema), reserve single-letter codes for post-renumbering use.

Content Deployment#

  • [ ] Run Phase 2I prompt sequence (prompts 1–7b) to migrate labels, test PoR fields, define compilation skill, generate first compiled views, write public documentation, and close Phase 2I.

  • [ ] File reorganization — move AHA doc, prompts, and llogs to permanent homes after integration stabilizes. (Timing: after prompt sequence completes and content has settled.)

  • [x] Rename BEST Names design document file — the compiler’s working copy has been renamed to compiler/ww/5d-link-naming-matheology-aha.rst with label prefix compiler-5d-link-naming-* (done 2026-03-25, Phase 2I-3). The frozen llog copy aha-best-names-for-matheology-links.rst retains its original filename and labels. All prompt scripts and compiler cross-references updated. The beginner’s guide was also renamed to compiler/aha/5d-link-naming-intro.rst and its prompt moved to compiler/aha/prompt_5d-link-naming-intro.rst.

  • [ ] Re-run adversarial stress test (Phase 2I-5) or an improved version to complete Phase 3. The original test (2I-adversarial-stress-test.rst) was run against the pre-revision design. The 2026-03-25 revision added DD 19.7 (publication renumbering), KUFIR/FLAMES lifecycle, new D2 types (obs, ru), and the Place-of pipeline. These changes need adversarial testing.