Canonical cooperation Gov · CWV 1.8.1

XRT Dynamic Memory Transcript System

Continuable conversation memory with evidence, chain, cursor, Current Working View, handoff, amendments, provenance, and canonical-promotion truth.

Canonical specification Changelog Agents and Teams

Gov Manual

Purpose

Preserve evidence and the current working view so another participant can continue without losing or duplicating work.

Use when

Capturing transcripts, creating handoffs, continuing chains, or tracing chat-derived governance evolution.

Core rule

Raw evidence, semantic reconstruction, CWV, and canonical governance are distinct states.

Required segment records

xrt_manifest · conversation_identity · chain · capture_cursor
cwv_summary · decisions · open_loops · handoff · evidence · integrity

Focused context examples

xrt aus context Themen von heute
xrt aus context Themen der ca. letzten Stunde
xrt aus context des Themas lvsc workspaces / Codex Chat erhalten

The selection can be temporal or thematic. The Markdown derivative identifies its raw source and limitations; it does not replace the transcript.

Operational provenance

Every evolution entry connects the source chat, retained XRT or handover, canonical Gov, Evolution Step commit, executing interface, and verified public page. GOV PULL and GOV UPDATE are conversational controls; implemented terminal commands belong to the 2HE Command Reference.

Reproducible continuation protocol

Read cwv_summary.
Read decisions.
Read open_loops.
Read capture_cursor.
Read handoff.
Verify chain and amendments; inspect evidence only when needed.

The required record types recur in every conforming segment, but the total record count is not fixed. Optional records and append-only amendments vary.

Completion classes

`local_capture`

Evidence exists only in local capture storage or durable publication is incomplete. Useful preservation, but not a device-independent handover.

`durable_handover`

The reviewed semantic segment and available byte-exact raw evidence are privately stored, independently fetched, digest-verified, and registered with distinct resolvers.

Private registry and XRT LFS

Plain xrt keeps a local capture copy, publishes the reviewed semantic segment and discovery metadata to fhxfhx/2HE__Private_Context_Archive, and stores compressed raw evidence by SHA-256 in the Google Drive-backed private My Drive/PROJECTS/UP2/PROJECTS/2HE/2HE-PRODUCTS/2HE-App/LFS/XRT store. Registry resolvers use xrt-lfs://sha256/..., independent of each device?s mount path.

2he chat xrt publish SEGMENT --raw-transcript RAW --entity ENTITY --area AREA --project PROJECT --confirm-reviewed
2he chat xrt lookup --project PROJECT --topic TOPIC
2he chat xrt raw verify RESOLVER
2he chat xrt raw fetch RESOLVER --output .temp/raw.jsonl

Living evidence lookup

Chats normally read the small semantic fast path: CWV, decisions, open loops, cursor, and handoff. Raw evidence is retrieved only when exact wording, tool output, images, provenance, or an omitted finding is needed. A verified fetch restores the immutable transcript into Git-ignored temporary storage, where the participant searches only the relevant records and promotes any new conclusion into a successor semantic segment.

Continuation

A stable chain ID links unique segments. The capture cursor defines the deduplication boundary. Successors start after included_through; amendments preserve prior history.

Canonical update truth

An XRT can capture an improvement, but only promotion to repository main changes the Gov CWV. Pages deployment and public verification remain separate proof states.

When XRT is useful

Extend a durable topic/project chain for material decisions, cross-chat or cross-team handoffs, unresolved continuation, multi-session evolution, or context-risk boundaries. Discover before creating. Do not create one XRT per chat, and skip acknowledgements, trivial questions, transient diagnostics, and work already represented sufficiently in canonical main.

XRT and RAgents

RAgents or another Team surface answers who is doing what now. XRT preserves what was learned, decided, and left open. Raw transcripts preserve exact evidence privately; repository main defines the canonical result. The layers may link but never replace each other.

Concurrent publication

Each segment is immutable and uniquely named. Publication commits the complete package and retries a rejected non-fast-forward push against the current remote head. An existing identity with different bytes is rejected. Lookup exposes all known chain heads; timestamps alone never resolve competing successors. Review and merge their meaning explicitly while preserving both original segments.

Privacy: durable raw transcript evidence is retained only in the approved private XRT LFS, never on public Pages. Recognized secrets are replaced in the archived copy by a short explanatory redaction marker. Local copies remain Git-ignored capture caches; semantic and raw evidence stay separate and independently verifiable.