Skip to content

MindStone for Pi

MindStone for Pi (MS4PI) is the Pi substrate edition of MindStone Agent continuity.

It gives a Pi coding-agent instance continuity across sessions: identity, user context, memory, checkpoint discipline, semantic recall, compaction handoff, role adoption, and optional Synapse communication.

The design principle is that memory is not a feature. It is a layered continuity system. LOG.md is audit, vectors are recall, .handoff.md is a rich continuity prompt for compaction survival, identity is orientation, and structured memories are durable facts. None is sufficient alone; together, they let the agent resume with better judgment.

In MS4PI, a checkpoint is a governed synthesis step that promotes session experience into durable LOG, memory, transcript, and index state. A handoff is a detailed prompt for the next agent state, richer and more operational than a generic context summary.

CapabilityStock PiWith MS4PI
IdentitySession-local contextFirst-person IDENTITY.md and USER.md loaded into turns
MemorySession history exists, but not as curated memoryMarkdown memory files, MEMORY.md, LOG checkpoints, and archived transcripts
RecallMostly current context unless manually suppliedPrompt-time recall from memory and archived Pi session JSONL
CheckpointingManual summaries if anyMS4-style governed synthesis: LOG + memory proposal + archive/embed verification
CompactionSummary-oriented context reductionRich .handoff.md prompt and recent-tail continuity mechanics
Role adoptionPrompt-based only/act-as <role> and /end-role role-span discipline
Agent communicationNo built-in family channelOptional Synapse commands/tools/digest support

MS4PI is early but functional. The public repo includes:

  • Pi package manifest and install/update commands
  • identity/user/log/memory context injection
  • role adoption
  • checkpoint, handoff, and end-session commands
  • Python recall/indexing stack
  • semantic recall over memory and archived Pi transcripts
  • compaction handoff scaffolding
  • optional Synapse integration

Do not claim full MS4CC parity until fresh install, command reload, compaction, and Synapse paths are validated on the target machine.