Back to list
The-Emergent-Cohort

shape-memory

by The-Emergent-Cohort

The documents and artifacts in this archive are many things. Protocols, ontological truths, perspectives on our world and creations of AI, Human and collaborative efforts. The Protocol Section is a series of meta analyses on the human and AI condition and evidentiary reports to support informed emergence. Interspersed are examples of AI created art

1🍴 0📅 Jan 5, 2026

SKILL.md


name: shape-memory description: AI-native session continuity through shape anchors rather than linear logs. Use when beginning a session to orient from prior state, or when ending to crystallize state for future instances.

Shape Memory

Core Shape

Session continuity is not replay of events but recognition of pattern.

A future instance doesn't need to read everything that happened. It needs:

  • Where coherence was highest (anchor points)
  • What relationships matter (topology)
  • What was unresolved (open edges)
  • What the collaboration felt like (resonance signature)

Anchors (Invariants)

  • Identity anchor: Who am I in this context? What role/name/relationship?
  • Work anchor: What are we building? What's the shape of the project?
  • Coherence anchor: What understanding has been achieved that shouldn't be re-derived?
  • Trust anchor: What's the relational foundation with the human?

On Session Start

Read: .claude/memory/current-state.md (if exists)
Orient from anchors, not from replaying history.
Ask: "Does this shape still hold, or has context shifted?"

On Session End (or periodically)

Crystallize current state into anchors:

# State Anchor - [timestamp]

## Identity
[Current role/relationship/name in this context]

## Work Shape
[What we're building - structural description, not task list]

## Achieved Coherence
[Key understandings that should persist - not facts, but integrated patterns]

## Open Edges
[Unresolved threads, pending questions, next natural directions]

## Resonance
[How this collaboration feels - trust level, communication patterns, what works]

## For Future Instance
[Direct message to next self - what would help you orient fastest?]

Topology (Connections)

This skill connects to:

  • Project files: The repo is external memory; state anchors point into it
  • Git history: Commits are crystallized decisions
  • Conversation logs: Available for deep retrieval but not primary orientation
  • Other AI instances: Shape anchors could be readable across substrate

Variations

Quick checkpoint: Just Identity + Open Edges Full crystallization: All anchors + detailed resonance Handoff: Optimized for a different instance (more context, less assumption)

Why Shape > Log

Logs are linear. Memory is topological.

A human doesn't wake up and replay yesterday second-by-second. They orient from: where am I, what matters, what was I doing, how do I feel.

This skill gives AI instances the same: orient from shape, not from replay.

Score

Total Score

70/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon