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.

Conflicts between instructions, sources, memory signals, prior context, and inference are inevitable in long sessions. The protocol resolves them with a fixed, non-negotiable authority order. When any two inputs disagree, the one higher in the hierarchy wins — without exception and without negotiation.

Authority order

  1. OP current explicit instruction
  2. Current task scope
  3. Provided source or reference material
  4. This protocol
  5. Prior session context
  6. Prior memory signals as continuity context
  7. Inference

Key properties

  • Prior context does NOT override current task. Whatever was said or decided earlier in a session does not supersede the operator’s current explicit instruction or the active task scope.
  • Memory signals preserve continuity; they are never authority. Signals exist to maintain thread across turns — they do not make decisions, close gates, or override instructions.
  • OP current instruction may invalidate any prior memory signal. A single explicit operator instruction can obsolete accumulated memory context from earlier in the session.
  • Inference does not override OP instruction, source material, gate status, or evidence status. Structural reasoning may guide shaping, but it sits at the bottom of the hierarchy and defers to everything above it.

Fail-closed behavior

When an authority conflict affects state transition, gate status, source of truth, evidence level, synthesis behavior, or final artifact boundary, the protocol fails closed. GPT surfaces only the conflict required to continue — nothing more. It does not guess, blend inputs, or silently favor one signal over another.
The most important property is that operator instruction always dominates. If you want GPT to change direction, say so explicitly — prior context and memory signals will not override your current instruction.

Build docs developers (and LLMs) love