docs: add the STATE v2 thin journal (docs/status/JOURNAL.adoc)

anytype_chora.deed

@@ -14,11 +14,11 @@
 ;;                 per state-v1-decision.adoc, OPTION B  [RULED 2026-11-10, owner]
 ;;                 Carried: [position] maturity -> (maturity :level ...);
 ;;                 [metadata] status "active" dedupes into (status :phase active).
-;;                 NOT carried (journal / derivable; they go to the archive
-;;                 surface, never the deed): [route-to-mvp], [blockers-and-issues],
-;;                 [critical-next-actions], [maintenance-status],
-;;                 completion-percentage. [position] phase "implementation" has
-;;                 no home under B (see the (status) comment below).
+;;                 NOT carried (journal / derivable, never the deed): milestones
+;;                 stay in docs/status/ROADMAP.adoc; blockers, the next action and
+;;                 the free-text [position] phase "implementation" go to the thin
+;;                 journal, docs/status/JOURNAL.adoc; [maintenance-status] and
+;;                 completion-percentage are derivable and dropped.
 ;;   0-AI-MANIFEST.a2ml (root) -> (manifest)(agent)(policy)(work)
 ;;                 per ai-manifest-decision.adoc, OPTION A  [RULED 2026-11-10, owner]
 ;;                 Agent seen-set: open, flag-any-unknown (the spec's default; the
@@ -61,11 +61,10 @@
   ; CLADE.a2ml carries no [status] section, so :phase comes from STATE v1
   ; [metadata] status = "active", which dedupes into this clause under
   ; state-v1-decision option B (one lifecycle truth, in the registry surface).
-  ; QUESTION FOR THE OWNER: STATE's separate [position] phase = "implementation"
-  ; uses a different vocabulary (design | implementation | testing | maintenance
-  ; | archived) from this closed lifecycle enum (reserved incubating active
-  ; dormant | merged superseded archived extinct), and maturity has its own
-  ; clause. Option B gives it no home, so it is preserved only in the archive.
+  ; STATE's separate [position] phase = "implementation" is a development-stage
+  ; label in a different vocabulary (design | implementation | testing |
+  ; maintenance | archived) from this closed lifecycle enum, so it is not written
+  ; here. It lives in the journal's free-text phase (docs/status/JOURNAL.adoc).
   (status   :phase         active
             :since         "2026-06-28"
             :present       #t

docs/practice/AI-CONVENTIONS.adoc

@@ -12,7 +12,7 @@ Per-tool config files (.cursorrules, .clinerules, etc.) reference this document.
 ## Session Startup
 
 1. Read `0-AI-MANIFEST.a2ml` FIRST (mandatory gatekeeper).
-2. Read `.machine_readable/6a2/STATE.a2ml` for current status and blockers.
+2. Read `docs/status/JOURNAL.adoc` for the current phase, blockers and next action. It governs over the journal sections of `.machine_readable/6a2/STATE.a2ml`, which stays only until its consumers are rewired.
 3. Read `.machine_readable/6a2/anchors/ANCHOR.a2ml` for canonical authority boundaries.
 4. Read `.machine_readable/policies/MAINTENANCE-AXES.a2ml` for maintenance/audit sequencing.
 5. Read `.machine_readable/policies/MAINTENANCE-CHECKLIST.a2ml` for baseline controls.
@@ -80,7 +80,8 @@ Use `just` (Justfile) for all build, test, lint, and format tasks.
 
 - `0-AI-MANIFEST.a2ml` -- universal AI entry point
 - `.machine_readable/6a2/AGENTIC.a2ml` -- agent permissions and constraints
-- `.machine_readable/6a2/STATE.a2ml` -- current project state
+- `docs/status/JOURNAL.adoc` -- thin session journal: phase, blockers, last and next action
+- `.machine_readable/6a2/STATE.a2ml` -- legacy project state (kept until its consumers are rewired)
 - `.machine_readable/6a2/anchors/ANCHOR.a2ml` -- canonical authority and policy boundary
 - `.machine_readable/policies/MAINTENANCE-AXES.a2ml` -- canonical axis sequencing and audit requirements
 - `.machine_readable/policies/MAINTENANCE-CHECKLIST.a2ml` -- baseline maintenance checklist policy

docs/status/JOURNAL.adoc

@@ -0,0 +1,68 @@
+// SPDX-License-Identifier: CC-BY-SA-4.0
+// SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell (hyperpolymath) <j.d.a.jewell@open.ac.uk>
+= anytype — thin session journal
+:updated: 2026-11-10
+
+What the next agent or human needs to resume work, and nothing that can be
+derived. This is the STATE v2 thin journal
+(`1-formats/templates/STATE.a2ml.v2.spec.adoc` in `standards`: phase, blockers,
+last action, next action), written as AsciiDoc because A2ML is retired.
+
+Where this file and the journal sections of `.machine_readable/6a2/STATE.a2ml`
+disagree, **this file governs** (`state-v1-decision`, option B, ruled
+2026-11-10). `STATE.a2ml` stays only until the checks and scripts that still
+require it are rewired.
+
+Kept elsewhere, on purpose: milestones in `ROADMAP.adoc`, history in the git
+log, evidence in `PROOF-STATUS.adoc`, task lists in the GitHub issues.
+
+phase::
+implementation. Built: the L2 grade-algebra interface with the affine and
+exact-usage instances, the L1 conversion checker with a syntactic totality gate
+(19-case golden matrix), and the typed ABI/FFI seam (`anytype-check`). Not
+started: L3 guarded recursion, the L0 lowering target, L4 effects. There is no
+working general-purpose checker yet (`AFFIRMATION.adoc`).
+
+last_action::
+Repaired the Idris2 proof workflow, which had failed on `main` since #55 moved
+`abi.ipkg`, and recorded ephapax as a design reference only (#73, 2026-11-10).
+
+next_action::
+Add branching to L1. It needs a join (least upper bound) on grades beyond the
+semiring-and-order laws, so design the extension against systemet first.
+
+session_marker::
+next_action carried from STATE v1 (2026-07-21); owner to confirm it is still
+the intended next step.
+
+updated::
+2026-11-10
+
+== Blockers
+
+[cols="2,5,3,2",options="header"]
+|===
+| id | description | waiting_on | since
+
+| `tea-gate`
+| Phase 6 (L4 effect handlers and TEA erasure) is gated on systemet's open
+  TEA-erasure result (ET-14). Not a code blocker yet.
+| systemet ET-14, OPEN
+| 2026-07-21 (first recorded in STATE v1)
+
+| `state-archive-rewire`
+| `STATE.a2ml` cannot be archived yet. `openssf-compliance.yml`, the Must
+  invariant, `scripts/validate-template.sh`, the e2e template test and the
+  arrival-pack generator still require it.
+| rewiring those consumers (several are derived from the estate canon)
+| 2026-11-10
+|===
+
+== Provenance
+
+* `phase` comes from `ROADMAP.adoc` (Done list). The kernel has had no logic
+  change since 2026-07-21: one commit touched `src/kernel/` in that time, a CI
+  remediation (#23).
+* `last_action` comes from the merge commit of #73.
+* `next_action` and the `tea-gate` blocker are carried from STATE v1 and are
+  not re-verified.