Protocol Library
A living methods library for ND‑led systems research. Each protocol turns a recurring kind of cognitive friction into a sequence of steps, questions and data hooks that can be logged, analysed and reused across contexts.
In this research programme, protocols are treated as configurable engines and methodological units, not self‑help tips: they generate structured data (friction records, tasks, metrics) that feed into a shared schema for longitudinal ND research and tooling.
Several of these protocols are already implemented in live tools such as the Cognition Compass and Quiet Friction Obsidian plugins, which write Markdown + YAML and JSON/CSV logs directly to the shared schema.
Core Tested Protocols
When perfectionism blocks action, compress an overwhelming project into 3–5 candidate tasks and choose a single first physical action.
Convene internal parts (e.g. Perfectionist Executor, Angry Protector, Girl Who Carries Shame, Royal Self) into a structured council for shared decision making.
Briefly check energy, focus and bodily signals to adjust plans to what is realistically and safely doable right now.
Planned / In Testing
- Boundary Check Protocol – Detect when people‑pleasing pulls you past safe limits, and define concrete scripts and exit rules in advance.
- Friction Logging Protocol – Capture moments of cognitive friction in situ as structured data that can feed future analysis and protocol design.
- Recovery Window Protocol – Deliberately allocate and protect recovery windows after intense work or social load, instead of treating rest as residual.
- Context Switching Protocol – A short sequence to close one context and prepare the next, reducing trace friction and task bleed‑through.
- Safety Check Protocol – Before high‑risk or high‑load situations, check physical and emotional safety and define red‑flag indicators.
- Signal Amplifier Protocol – Make weak early signals of overload or burnout visible before crisis, using simple recurring prompts and metrics.
- Weekly Systems Review Protocol – Review friction logs and adjust protocols and environment, rather than attributing patterns solely to willpower.