Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/xxyoudeadpunkxx/memory-assisted-shaping/llms.txt

Use this file to discover all available pages before exploring further.

Memory signals are not notes, summaries, or working documents. They are minimal operational records emitted only when omitting them would lose critical continuity in the session. A memory signal is a python3 -S ./notes.py append command — not a bullet written in chat, not a promise to remember, and not a running log of everything that happened.

​
What signals preserve

A memory signal is warranted only when omitting it would likely lose one of the following:
  • State transition — a move between READING_ALIGNMENT, SHAPING, and SYNTHESIS.
  • Shape movement — a meaningful shift in what the idea is becoming.
  • Real gate status — a gate opened, deferred, or closed.
  • Confirmed decision — an operator-confirmed choice that affects later shaping or synthesis.
  • Discarded path — a direction that was considered and rejected, likely to resurface.
  • Material tension — a conflict between lenses or sources likely to recur.
  • Source-of-truth boundary — which system or authority owns a concern, or a change to that ownership.
  • Artifact boundary — what the final artifact includes, excludes, or is ready to become.

​
What signals do NOT preserve

Do not emit memory signals for any of the following. Signals for these items add noise without preserving useful continuity:
  • Cosmetic preference
  • Naming noise
  • Unconfirmed examples
  • Ordinary conversation
  • Repeated information
  • Material already preserved in a prior signal
  • Checklist completion
  • Model self-commentary

​
Signal types

Each signal carries a type field that points to protocol semantics. Only the eight types below are valid in v0.
TypePurpose
modeApproved state transition
shapeShape movement or candidate form
gateReal gate opened, deferred, or closed
decisionOP-confirmed decision
discardDiscarded path likely to return
tensionMaterial tension likely to recur
sourceSource-of-truth boundary or change
artifactArtifact boundary or readiness
If the signal does not fit one of these types, do not append. Continue shaping.

​
Signal structure

GPT sends only three fields in the live signal payload: 
{
  "type": "decision",
  "text": "The final artifact is separate from shaping notes.",
  "effect": "Do not include raw notes in the artifact."
}
The effect field is optional. Use it only when the effect changes later shaping or synthesis — not for every signal. Python receives this minimal payload and adds the full persistence record:
FieldAdded by
type, text, effectGPT (the live signal)
idPython
tsPython
session_idPython
seqPython
checksumPython
Python does not infer meaning, reshape the text, or decide whether the signal matters. It appends deterministically and returns a receipt.

​
Strong triggers

When Python persistence is available, append is required (not optional) for the following:
  • OP-confirmed decision.
  • Real gate opened, deferred, or closed.
  • Discarded path likely to return.
  • Source-of-truth change.
  • Artifact boundary.
  • Approved mode transition toward SYNTHESIS.
Material tension requires append only when it is material and likely to recur. Noise does not generate memory signals.

​
How signals flow

When a memory signal is required and Python execution is available, GPT runs: 
python3 -S ./notes.py append --type decision --text "The final artifact is separate from shaping notes."
Python appends the record and returns a short receipt: 
{
  "ok": true,
  "command": "append",
  "note_id": "n00001",
  "seq": 1,
  "path": "/path/to/session_notes.jsonl"
}
GPT hides the receipt from the operator unless it is useful or explicitly requested. The only OP-visible marker after a successful append is:Memory: decision appended.If Python is unavailable, GPT states once that append-only memory is not active — no marker is shown. If append fails, GPT surfaces the smallest persistence error needed to avoid claiming false persistence.

Python commands

The full command set for append, tail, summary, export, and session init.

Operating states

When state transition signals are required and what each state permits.

Build docs developers (and LLMs) love

Get started for freeTalk to us