Checkpoint 006 · Subwave R3

Contracts before coupling.

GTC’s observed distribution is frozen, and every memory candidate now faces the same lifecycle, isolation, portability, and failure-containment contract.

15

Contract tests pass

Profile/game/session scope, transcript sync, session switches, rewind, compression, delegation, bounded injection, export, restore, delete, and provider failure are executable.

Partial

GTC provenance

The live tools, OpenAPI surface, source tree, Docker image IDs, and Compose hashes are pinned—but the source-to-image chain is not reproducible yet.

Known GTC gaps

  • Mutable Compose tags remain.
  • The local parse image lacks registry provenance.
  • Live OpenAPI says 0.6.0 while source describes 0.12.1 plus a dirty Compose file.
  • Authentication is disabled and mcp-svc is not live.

Boundary decision

GTC stays a separately versioned distribution used by Nagato. Memory providers must implement the product contract; raw conversations and Recall evidence do not cross into personal Hermes by default.

R3 establishes testable interfaces; it does not claim a reproducible GTC release. Generated 25 July 2026.