// SPDX-License-Identifier: CC-BY-SA-4.0
// SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell (hyperpolymath)
= Shared Continuity Core — Session Management Standards
:toc:
:status: PROPOSAL
:version: 1.0.0

This document defines the shared continuity core fields and conventions
that must be used across all session-management protocols in the estate.

== The Enriched 25-Field Continuity Core

Every session-close, handover, or checkpoint artefact must capture the
following 25 fields (either as document attributes or as sections).

=== Meta-Attributes (10 fields)

1.  `:protocol:` — The canonical name of the protocol being executed.
2.  `:protocol-version:` — The version of the protocol definition.
3.  `:session-id:` — Unique identifier (e.g., `YYYY-MM-DD-short-topic`).
4.  `:session-start:` — Approximate start timestamp (ISO 8601 or similar).
5.  `:session-end:` — Approximate end timestamp (ISO 8601 or similar).
6.  `:assistant:` — Assistant identity (e.g., `Claude Opus 4.6 (1M context)`).
7.  `:author:` — Human author/owner identity (e.g., `Jonathan D.A. Jewell`).
8.  `:format-schema:` — Version of this core schema (currently `session-close.v1.enriched`).
9.  `:archival-convention:` — Convention used (MUST be `timestamped append-only`).
10. `:cross-references:` — List of relevant external links (git, memory, Desktop).

=== Core Sections (15 fields)

11. **Goal** — High-level objective of the session.
12. **Current task** — Description of the work-in-progress at closure.
13. **Last completed action** — The final successful milestone reached.
14. **Next intended action** — The primary task for the next session.
15. **Repository** — Primary repository path and state.
16. **Branch** — Active git branch.
17. **HEAD commit** — Table or block with Repo, Hash, and Subject.
18. **Files of interest** — New artefacts, modified files, memory, private files.
19. **Known blockers** — Explicit list of obstacles preventing progress.
20. **Residual risks** — Potential issues, technical debt, or unverified areas.
21. **Recommended next protocol** — The protocol to run next (e.g., `intake repo`).
22. **Commits made this session** — Table with Order, Repo, Hash, and Subject.
23. **Verifications run this session** — Table with Item, What, and Result (✅/❌).
24. **Decisions made & Deferred** — Lists of architectural choices and open questions.
25. **Discipline check (Meta-rule audit)** — Table with Rule, Honoured?, and Evidence.

== Verification Block Format

Every protocol must include a `Verification` block specifying the mandatory
checks required before the protocol declares success.

[source,adoc]
----
== Verification

[cols="1,3,2",options="header"]
|===
| Item | What was verified | Result

| `just build` | Full build of the affected components | ✅
| `just test`  | Execution of the primary test suite    | ✅
| `doc-claims` | Grounding pass on the new artefacts   | ✅
|===
----

== Archival Convention (Timestamped Append-Only)

*   **Rule**: NEVER overwrite a single `SESSION_STATE` template file.
*   **Action**: Save each closure as a unique, timestamped file.
*   **Naming**: `SESSION-CLOSE-<ISO-date>-<short-topic>.adoc`.
*   **Location**: Adjacent to the repository root or in a dedicated `history/` directory.

== Discipline-Check Meta-Rule Audit Format

The meta-rule audit ensures the standing rules in `../../../../../../../home/hyper/.claude/projects/-var-mnt-eclipse-repos/memory/MEMORY.md` were followed.

[source,adoc]
----
== Discipline check (the meta-rule audit)

[cols="2,1,3",options="header"]
|===
| Standing rule | Honoured? | Evidence

| Full battery before claims | ✅ | All unit tests passed (6/6)
| WIRE EVERYTHING | ✅ | All templates filled, no stubs
| panic-attack assail clean | ✅ | Run manually before commit
|===
----

== Cross-Reference Convention

Always link to:
*   **TRG/CRG**: Toolchain and Component Readiness Grades.
*   **Panic-attack**: Security and integrity reports.
*   **Doc-claims**: Grounding reports.
*   **Dual-use**: Designations and governance docs.

== Doc-Claims Grounding Pass Requirement

Every new protocol artefact must be groundable by `invariant-path doc-claims`.
Any ungrounded references must be explicitly characterised as either:
1.  **Authoring bugs**: Missing files or incorrect paths (must be FIXED).
2.  **Cross-estate references**: Legitimate links outside the current root.
3.  **Known limitations**: v0 single-root grounder limitations.
