Retention
Begins with recognizable retention tactics and progresses toward reinforcement, withholding, fear, caretaking, proof, and scarcity structures that can keep engagement active.
NarcyNarc.com
The Structural Field Cards are not arranged as a pile of definitions. Their order is deliberate. The sequence moves from noticing an event, to locating a structure, to watching how that structure operates, changes, persists, or fails. Numbering helps preserve that architecture without claiming that every real-world interaction unfolds in one fixed order.
A field-card sequence is a teaching map, not a prediction engine. Earlier cards usually establish the conditions needed to understand later cards. Later cards often describe movement, interaction, escalation, persistence, breakdown, or reorganization. A reader can enter the map anywhere, but the sequence explains how the concepts relate.
The card itself slows interpretation down: questionable event → classification → placement → function → operational elements → outcomes → associations → structural observation → field guidance.
The cards within a collection are arranged so foundational structures generally appear before movement, interaction, persistence, failure, or reorganization.
Begins with recognizable retention tactics and progresses toward reinforcement, withholding, fear, caretaking, proof, and scarcity structures that can keep engagement active.
Moves from control, transfer, and framing into repair, omission, selective disclosure, revision, context loss, role reassignment, accountability fog, memory disputes, motive assignment, and story ownership.
Starts with what is harvested, then maps importance, allocation, rotation, scarcity, visibility, prioritization, access, engagement, dependency, and continuity.
Shifts the lens from mechanisms to recurring internal states and effects that may emerge through repeated exposure, cognitive strain, emotional demand, or reinforcing patterns.
This collection is explicitly cyclical. Uncertainty activates proof seeking; defensive attribution, filibuster, issue expansion, reciprocal traps, escalation, exhaustion, reset, and re-entry can prevent lasting settlement.
Begins with placement and hierarchy, then maps partitioned access, visibility, information, obligations, and allocation before moving into parallel operation, dormancy, retention, containment, leakage, collision, breach, and structural reorganization.
Starts before a reputation event is fully formed: seeding, credibility positioning, and audience selection. It then moves through evidence packaging, framing, social proof, amplification, preemption, contradiction containment, and repair.
Blame begins only after responsibility becomes meaningful. The sequence first establishes blame, then tracks its movement, and finally examines what blame does to the larger responsibility field.
Blame cannot be transferred before blame exists. Attribution establishes a fault claim. Placement gives that claim a location. Transfer and deflection track movement away from that position. Reversal changes the direction of fault. Expansion and concentration change the size and weight of the blame field. Reciprocal looping changes its motion. Persistence changes its duration. Blame–Ownership Separation asks the closing question: did blame remain active while actual ownership failed to settle?
This is why the first Blame cards can feel as though they “stick” to a point, while later cards seem to change the narrative, spread responsibility, soften impact, intensify concentration, or keep fault circulating. The collection has pivoted from tracking movement to tracking field dynamics.
Card numbers identify a concept’s place in the library. They do not claim that real interactions must occur numerically, that every earlier card must appear before a later card, or that an unrepresented number range is an error. Some ranges may be reserved, under development, or introduced elsewhere in the framework. Conceptual prerequisites matter more than release order.
Blame is secondary to an accountability field. Someone does not have to accept responsibility before blame appears, but an event, impact, obligation, or corrective question must first make responsibility relevant. Blame can then be attributed, moved, widened, concentrated, circulated, or separated from ownership.
Do not use a later card as proof of an earlier one. Do not treat a sequence as motive. Do not assume that structural similarity establishes diagnosis. Instead, use the order as a way to ask better questions: What appeared first? What changed? What moved? What stayed stable? What became easier or harder to resolve? Where did responsibility finally settle — if it settled at all?