arscontexta 0.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (418) hide show
  1. package/.claude-plugin/marketplace.json +11 -0
  2. package/.claude-plugin/plugin.json +22 -0
  3. package/README.md +683 -0
  4. package/agents/knowledge-guide.md +49 -0
  5. package/bin/cli.mjs +66 -0
  6. package/generators/agents-md.md +240 -0
  7. package/generators/claude-md.md +379 -0
  8. package/generators/features/atomic-notes.md +124 -0
  9. package/generators/features/ethical-guardrails.md +58 -0
  10. package/generators/features/graph-analysis.md +188 -0
  11. package/generators/features/helper-functions.md +92 -0
  12. package/generators/features/maintenance.md +164 -0
  13. package/generators/features/methodology-knowledge.md +70 -0
  14. package/generators/features/mocs.md +144 -0
  15. package/generators/features/multi-domain.md +61 -0
  16. package/generators/features/personality.md +71 -0
  17. package/generators/features/processing-pipeline.md +428 -0
  18. package/generators/features/schema.md +149 -0
  19. package/generators/features/self-evolution.md +229 -0
  20. package/generators/features/self-space.md +78 -0
  21. package/generators/features/semantic-search.md +99 -0
  22. package/generators/features/session-rhythm.md +85 -0
  23. package/generators/features/templates.md +85 -0
  24. package/generators/features/wiki-links.md +88 -0
  25. package/generators/soul-md.md +121 -0
  26. package/hooks/hooks.json +45 -0
  27. package/hooks/scripts/auto-commit.sh +44 -0
  28. package/hooks/scripts/session-capture.sh +35 -0
  29. package/hooks/scripts/session-orient.sh +86 -0
  30. package/hooks/scripts/write-validate.sh +42 -0
  31. package/methodology/AI shifts knowledge systems from externalizing memory to externalizing attention.md +59 -0
  32. package/methodology/BM25 retrieval fails on full-length descriptions because query term dilution reduces match scores.md +39 -0
  33. package/methodology/IBIS framework maps claim-based architecture to structured argumentation.md +58 -0
  34. package/methodology/LLM attention degrades as context fills.md +49 -0
  35. package/methodology/MOC construction forces synthesis that automated generation from metadata cannot replicate.md +49 -0
  36. package/methodology/MOC maintenance investment compounds because orientation savings multiply across every future session.md +41 -0
  37. package/methodology/MOCs are attention management devices not just organizational tools.md +51 -0
  38. package/methodology/PKM failure follows a predictable cycle.md +50 -0
  39. package/methodology/ThreadMode to DocumentMode transformation is the core value creation step.md +52 -0
  40. package/methodology/WIP limits force processing over accumulation.md +53 -0
  41. package/methodology/Zeigarnik effect validates capture-first philosophy because open loops drain attention.md +42 -0
  42. package/methodology/academic research uses structured extraction with cross-source synthesis.md +566 -0
  43. package/methodology/adapt the four-phase processing pipeline to domain-specific throughput needs.md +197 -0
  44. package/methodology/agent notes externalize navigation intuition that search cannot discover and traversal cannot reconstruct.md +48 -0
  45. package/methodology/agent self-memory should be architecturally separate from user knowledge systems.md +48 -0
  46. package/methodology/agent session boundaries create natural automation checkpoints that human-operated systems lack.md +56 -0
  47. package/methodology/agent-cognition.md +107 -0
  48. package/methodology/agents are simultaneously methodology executors and subjects creating a unique trust asymmetry.md +66 -0
  49. package/methodology/aspect-oriented programming solved the same cross-cutting concern problem that hooks solve.md +39 -0
  50. package/methodology/associative ontologies beat hierarchical taxonomies because heterarchy adapts while hierarchy brittles.md +53 -0
  51. package/methodology/attention residue may have a minimum granularity that cannot be subdivided.md +46 -0
  52. package/methodology/auto-commit hooks eliminate prospective memory failures by converting remember-to-act into guaranteed execution.md +47 -0
  53. package/methodology/automated detection is always safe because it only reads state while automated remediation risks content corruption.md +42 -0
  54. package/methodology/automation should be retired when its false positive rate exceeds its true positive rate or it catches zero issues.md +56 -0
  55. package/methodology/backlinks implicitly define notes by revealing usage context.md +35 -0
  56. package/methodology/backward maintenance asks what would be different if written today.md +62 -0
  57. package/methodology/balance onboarding enforcement and questions to prevent premature complexity.md +229 -0
  58. package/methodology/basic level categorization determines optimal MOC granularity.md +51 -0
  59. package/methodology/batching by context similarity reduces switching costs in agent processing.md +43 -0
  60. package/methodology/behavioral anti-patterns matter more than tool selection.md +42 -0
  61. package/methodology/betweenness centrality identifies bridge notes connecting disparate knowledge domains.md +57 -0
  62. package/methodology/blueprints that teach construction outperform downloads that provide pre-built code for platform-dependent modules.md +42 -0
  63. package/methodology/bootstrapping principle enables self-improving systems.md +62 -0
  64. package/methodology/build automatic memory through cognitive offloading and session handoffs.md +285 -0
  65. package/methodology/capture the reaction to content not just the content itself.md +41 -0
  66. package/methodology/claims must be specific enough to be wrong.md +36 -0
  67. package/methodology/closure rituals create clean breaks that prevent attention residue bleed.md +44 -0
  68. package/methodology/cognitive offloading is the architectural foundation for vault design.md +46 -0
  69. package/methodology/cognitive outsourcing risk in agent-operated systems.md +55 -0
  70. package/methodology/coherence maintains consistency despite inconsistent inputs.md +96 -0
  71. package/methodology/coherent architecture emerges from wiki links spreading activation and small-world topology.md +48 -0
  72. package/methodology/community detection algorithms can inform when MOCs should split or merge.md +52 -0
  73. package/methodology/complete navigation requires four complementary types that no single mechanism provides.md +43 -0
  74. package/methodology/complex systems evolve from simple working systems.md +59 -0
  75. package/methodology/composable knowledge architecture builds systems from independent toggleable modules not monolithic templates.md +61 -0
  76. package/methodology/compose multi-domain systems through separate templates and shared graph.md +372 -0
  77. package/methodology/concept-orientation beats source-orientation for cross-domain connections.md +51 -0
  78. package/methodology/confidence thresholds gate automated action between the mechanical and judgment zones.md +50 -0
  79. package/methodology/configuration dimensions interact so choices in one create pressure on others.md +58 -0
  80. package/methodology/configuration paralysis emerges when derivation surfaces too many decisions.md +44 -0
  81. package/methodology/context files function as agent operating systems through self-referential self-extension.md +46 -0
  82. package/methodology/context phrase clarity determines how deep a navigation hierarchy can scale.md +46 -0
  83. package/methodology/continuous small-batch processing eliminates review dread.md +48 -0
  84. package/methodology/controlled disorder engineers serendipity through semantic rather than topical linking.md +51 -0
  85. package/methodology/creative writing uses worldbuilding consistency with character tracking.md +672 -0
  86. package/methodology/cross-links between MOC territories indicate creative leaps and integration depth.md +43 -0
  87. package/methodology/dangling links reveal which notes want to exist.md +62 -0
  88. package/methodology/data exit velocity measures how quickly content escapes vendor lock-in.md +74 -0
  89. package/methodology/decontextualization risk means atomicity may strip meaning that cannot be recovered.md +48 -0
  90. package/methodology/dense interlinked research claims enable derivation while sparse references only enable templating.md +47 -0
  91. package/methodology/dependency resolution through topological sort makes module composition transparent and verifiable.md +56 -0
  92. package/methodology/derivation generates knowledge systems from composable research claims not template customization.md +63 -0
  93. package/methodology/derivation-engine.md +27 -0
  94. package/methodology/derived systems follow a seed-evolve-reseed lifecycle.md +56 -0
  95. package/methodology/description quality for humans diverges from description quality for keyword search.md +73 -0
  96. package/methodology/descriptions are retrieval filters not summaries.md +112 -0
  97. package/methodology/design MOCs as attention management devices with lifecycle governance.md +318 -0
  98. package/methodology/design-dimensions.md +66 -0
  99. package/methodology/digital mutability enables note evolution that physical permanence forbids.md +54 -0
  100. package/methodology/discovery-retrieval.md +48 -0
  101. package/methodology/distinctiveness scoring treats description quality as measurable.md +69 -0
  102. package/methodology/does agent processing recover what fast capture loses.md +43 -0
  103. package/methodology/domain-compositions.md +37 -0
  104. package/methodology/dual-coding with visual elements could enhance agent traversal.md +55 -0
  105. package/methodology/each module must be describable in one sentence under 200 characters or it does too many things.md +45 -0
  106. package/methodology/each new note compounds value by creating traversal paths.md +55 -0
  107. package/methodology/eight configuration dimensions parameterize the space of possible knowledge systems.md +56 -0
  108. package/methodology/elaborative encoding is the quality gate for new notes.md +55 -0
  109. package/methodology/enforce schema with graduated strictness across capture processing and query zones.md +221 -0
  110. package/methodology/enforcing atomicity can create paralysis when ideas resist decomposition.md +43 -0
  111. package/methodology/engineering uses technical decision tracking with architectural memory.md +766 -0
  112. package/methodology/every knowledge domain shares a four-phase processing skeleton that diverges only in the process step.md +53 -0
  113. package/methodology/evolution observations provide actionable signals for system adaptation.md +67 -0
  114. package/methodology/external memory shapes cognition more than base model.md +60 -0
  115. package/methodology/faceted classification treats notes as multi-dimensional objects rather than folder contents.md +65 -0
  116. package/methodology/failure-modes.md +27 -0
  117. package/methodology/false universalism applies same processing logic regardless of domain.md +49 -0
  118. package/methodology/federated wiki pattern enables multi-agent divergence as feature not bug.md +59 -0
  119. package/methodology/flat files break at retrieval scale.md +75 -0
  120. package/methodology/forced engagement produces weak connections.md +48 -0
  121. package/methodology/four abstraction layers separate platform-agnostic from platform-dependent knowledge system features.md +47 -0
  122. package/methodology/fresh context per task preserves quality better than chaining phases.md +44 -0
  123. package/methodology/friction reveals architecture.md +63 -0
  124. package/methodology/friction-driven module adoption prevents configuration debt by adding complexity only at pain points.md +48 -0
  125. package/methodology/gardening cycle implements tend prune fertilize operations.md +41 -0
  126. package/methodology/generation effect gate blocks processing without transformation.md +40 -0
  127. package/methodology/goal-driven memory orchestration enables autonomous domain learning through directed compute allocation.md +41 -0
  128. package/methodology/good descriptions layer heuristic then mechanism then implication.md +57 -0
  129. package/methodology/graph-structure.md +65 -0
  130. package/methodology/guided notes might outperform post-hoc structuring for high-volume capture.md +37 -0
  131. package/methodology/health wellness uses symptom-trigger correlation with multi-dimensional tracking.md +819 -0
  132. package/methodology/hook composition creates emergent methodology from independent single-concern components.md +47 -0
  133. package/methodology/hook enforcement guarantees quality while instruction enforcement merely suggests it.md +51 -0
  134. package/methodology/hook-driven learning loops create self-improving methodology through observation accumulation.md +62 -0
  135. package/methodology/hooks are the agent habit system that replaces the missing basal ganglia.md +40 -0
  136. package/methodology/hooks cannot replace genuine cognitive engagement yet more automation is always tempting.md +87 -0
  137. package/methodology/hooks enable context window efficiency by delegating deterministic checks to external processes.md +47 -0
  138. package/methodology/idempotent maintenance operations are safe to automate because running them twice produces the same result as running them once.md +44 -0
  139. package/methodology/implement condition-based maintenance triggers for derived systems.md +255 -0
  140. package/methodology/implicit dependencies create distributed monoliths that fail silently across configurations.md +58 -0
  141. package/methodology/implicit knowledge emerges from traversal.md +55 -0
  142. package/methodology/incremental formalization happens through repeated touching of old notes.md +60 -0
  143. package/methodology/incremental reading enables cross-source connection finding.md +39 -0
  144. package/methodology/index.md +32 -0
  145. package/methodology/inline links carry richer relationship data than metadata fields.md +91 -0
  146. package/methodology/insight accretion differs from productivity in knowledge systems.md +41 -0
  147. package/methodology/intermediate packets enable assembly over creation.md +52 -0
  148. package/methodology/intermediate representation pattern enables reliable vault operations beyond regex.md +62 -0
  149. package/methodology/justification chains enable forward backward and evolution reasoning about configuration decisions.md +46 -0
  150. package/methodology/knowledge system architecture is parameterized by platform capabilities not fixed by methodology.md +51 -0
  151. package/methodology/knowledge systems become communication partners through complexity and memory humans cannot sustain.md +47 -0
  152. package/methodology/knowledge systems share universal operations and structural components across all methodology traditions.md +46 -0
  153. package/methodology/legal case management uses precedent chains with regulatory change propagation.md +892 -0
  154. package/methodology/live index via periodic regeneration keeps discovery current.md +58 -0
  155. package/methodology/local-first file formats are inherently agent-native.md +69 -0
  156. package/methodology/logic column pattern separates reasoning from procedure.md +35 -0
  157. package/methodology/maintenance operations are more universal than creative pipelines because structural health is domain-invariant.md +47 -0
  158. package/methodology/maintenance scheduling frequency should match consequence speed not detection capability.md +50 -0
  159. package/methodology/maintenance targeting should prioritize mechanism and theory notes.md +26 -0
  160. package/methodology/maintenance-patterns.md +72 -0
  161. package/methodology/markdown plus YAML plus ripgrep implements a queryable graph database without infrastructure.md +55 -0
  162. package/methodology/maturity field enables agent context prioritization.md +33 -0
  163. package/methodology/memory-architecture.md +27 -0
  164. package/methodology/metacognitive confidence can diverge from retrieval capability.md +42 -0
  165. package/methodology/metadata reduces entropy enabling precision over recall.md +91 -0
  166. package/methodology/methodology development should follow the trajectory from documentation to skill to hook as understanding hardens.md +80 -0
  167. package/methodology/methodology traditions are named points in a shared configuration space not competing paradigms.md +64 -0
  168. package/methodology/mnemonic medium embeds verification into navigation.md +46 -0
  169. package/methodology/module communication through shared YAML fields creates loose coupling without direct dependencies.md +44 -0
  170. package/methodology/module deactivation must account for structural artifacts that survive the toggle.md +49 -0
  171. package/methodology/multi-domain systems compose through separate templates and shared graph.md +61 -0
  172. package/methodology/multi-domain-composition.md +27 -0
  173. package/methodology/narrow folksonomy optimizes for single-operator retrieval unlike broad consensus tagging.md +53 -0
  174. package/methodology/navigation infrastructure passes through distinct scaling regimes that require qualitative strategy shifts.md +48 -0
  175. package/methodology/navigational vertigo emerges in pure association systems without local hierarchy.md +54 -0
  176. package/methodology/note titles should function as APIs enabling sentence transclusion.md +51 -0
  177. package/methodology/note-design.md +57 -0
  178. package/methodology/notes are skills /342/200/224 curated knowledge injected when relevant.md" +62 -0
  179. package/methodology/notes function as cognitive anchors that stabilize attention during complex tasks.md +41 -0
  180. package/methodology/novel domains derive by mapping knowledge type to closest reference domain then adapting.md +50 -0
  181. package/methodology/nudge theory explains graduated hook enforcement as choice architecture for agents.md +59 -0
  182. package/methodology/observation and tension logs function as dead-letter queues for failed automation.md +51 -0
  183. package/methodology/operational memory and knowledge memory serve different functions in agent architecture.md +48 -0
  184. package/methodology/operational wisdom requires contextual observation.md +52 -0
  185. package/methodology/orchestrated vault creation transforms arscontexta from tool to autonomous knowledge factory.md +40 -0
  186. package/methodology/organic emergence versus active curation creates a fundamental vault governance tension.md +68 -0
  187. package/methodology/orphan notes are seeds not failures.md +38 -0
  188. package/methodology/over-automation corrupts quality when hooks encode judgment rather than verification.md +62 -0
  189. package/methodology/people relationships uses Dunbar-layered graphs with interaction tracking.md +659 -0
  190. package/methodology/personal assistant uses life area management with review automation.md +610 -0
  191. package/methodology/platform adapter translation is semantic not mechanical because hook event meanings differ.md +40 -0
  192. package/methodology/platform capability tiers determine which knowledge system features can be implemented.md +48 -0
  193. package/methodology/platform fragmentation means identical conceptual operations require different implementations across agent environments.md +44 -0
  194. package/methodology/premature complexity is the most common derivation failure mode.md +45 -0
  195. package/methodology/prevent domain-specific failure modes through the vulnerability matrix.md +336 -0
  196. package/methodology/processing effort should follow retrieval demand.md +57 -0
  197. package/methodology/processing-workflows.md +75 -0
  198. package/methodology/product management uses feedback pipelines with experiment tracking.md +789 -0
  199. package/methodology/productivity porn risk in meta-system building.md +30 -0
  200. package/methodology/programmable notes could enable property-triggered workflows.md +64 -0
  201. package/methodology/progressive disclosure means reading right not reading less.md +69 -0
  202. package/methodology/progressive schema validates only what active modules require not the full system schema.md +49 -0
  203. package/methodology/project management uses decision tracking with stakeholder context.md +776 -0
  204. package/methodology/propositional link semantics transform wiki links from associative to reasoned.md +87 -0
  205. package/methodology/prospective memory requires externalization.md +53 -0
  206. package/methodology/provenance tracks where beliefs come from.md +62 -0
  207. package/methodology/queries evolve during search so agents should checkpoint.md +35 -0
  208. package/methodology/question-answer metadata enables inverted search patterns.md +39 -0
  209. package/methodology/random note resurfacing prevents write-only memory.md +33 -0
  210. package/methodology/reconciliation loops that compare desired state to actual state enable drift correction without continuous monitoring.md +59 -0
  211. package/methodology/reflection synthesizes existing notes into new insight.md +100 -0
  212. package/methodology/retrieval utility should drive design over capture completeness.md +69 -0
  213. package/methodology/retrieval verification loop tests description quality at scale.md +81 -0
  214. package/methodology/role field makes graph structure explicit.md +94 -0
  215. package/methodology/scaffolding enables divergence that fine-tuning cannot.md +67 -0
  216. package/methodology/schema enforcement via validation agents enables soft consistency.md +60 -0
  217. package/methodology/schema evolution follows observe-then-formalize not design-then-enforce.md +65 -0
  218. package/methodology/schema field names are the only domain specific element in the universal note pattern.md +46 -0
  219. package/methodology/schema fields should use domain-native vocabulary not abstract terminology.md +47 -0
  220. package/methodology/schema templates reduce cognitive overhead at capture time.md +55 -0
  221. package/methodology/schema validation hooks externalize inhibitory control that degrades under cognitive load.md +48 -0
  222. package/methodology/schema-enforcement.md +27 -0
  223. package/methodology/self-extension requires context files to contain platform operations knowledge not just methodology.md +47 -0
  224. package/methodology/sense-making vs storage does compression lose essential nuance.md +73 -0
  225. package/methodology/session boundary hooks implement cognitive bookends for orientation and reflection.md +60 -0
  226. package/methodology/session handoff creates continuity without persistent memory.md +43 -0
  227. package/methodology/session outputs are packets for future selves.md +43 -0
  228. package/methodology/session transcript mining enables experiential validation that structural tests cannot provide.md +38 -0
  229. package/methodology/skill context budgets constrain knowledge system complexity on agent platforms.md +52 -0
  230. package/methodology/skills encode methodology so manual execution bypasses quality gates.md +50 -0
  231. package/methodology/small-world topology requires hubs and dense local links.md +99 -0
  232. package/methodology/source attribution enables tracing claims to foundations.md +38 -0
  233. package/methodology/spaced repetition scheduling could optimize vault maintenance.md +44 -0
  234. package/methodology/spreading activation models how agents should traverse.md +79 -0
  235. package/methodology/stale navigation actively misleads because agents trust curated maps completely.md +43 -0
  236. package/methodology/stigmergy coordinates agents through environmental traces without direct communication.md +62 -0
  237. package/methodology/storage versus thinking distinction determines which tool patterns apply.md +56 -0
  238. package/methodology/structure enables navigation without reading everything.md +52 -0
  239. package/methodology/structure without processing provides no value.md +56 -0
  240. package/methodology/student learning uses prerequisite graphs with spaced retrieval.md +770 -0
  241. package/methodology/summary coherence tests composability before filing.md +37 -0
  242. package/methodology/tag rot applies to wiki links because titles serve as both identifier and display text.md +50 -0
  243. package/methodology/temporal media must convert to spatial text for agent traversal.md +43 -0
  244. package/methodology/temporal processing priority creates age-based inbox urgency.md +45 -0
  245. package/methodology/temporal separation of capture and processing preserves context freshness.md +39 -0
  246. package/methodology/ten universal primitives form the kernel of every viable agent knowledge system.md +162 -0
  247. package/methodology/testing effect could enable agent knowledge verification.md +38 -0
  248. package/methodology/the AgentSkills standard embodies progressive disclosure at the skill level.md +40 -0
  249. package/methodology/the derivation engine improves recursively as deployed systems generate observations.md +49 -0
  250. package/methodology/the determinism boundary separates hook methodology from skill methodology.md +46 -0
  251. package/methodology/the fix-versus-report decision depends on determinism reversibility and accumulated trust.md +45 -0
  252. package/methodology/the generation effect requires active transformation not just storage.md +57 -0
  253. package/methodology/the no wrong patches guarantee ensures any valid module combination produces a valid system.md +58 -0
  254. package/methodology/the system is the argument.md +46 -0
  255. package/methodology/the vault constitutes identity for agents.md +86 -0
  256. package/methodology/the vault methodology transfers because it encodes cognitive science not domain specifics.md +47 -0
  257. package/methodology/therapy journal uses warm personality with pattern detection for emotional processing.md +584 -0
  258. package/methodology/three capture schools converge through agent-mediated synthesis.md +55 -0
  259. package/methodology/three concurrent maintenance loops operate at different timescales to catch different classes of problems.md +56 -0
  260. package/methodology/throughput matters more than accumulation.md +58 -0
  261. package/methodology/title as claim enables traversal as reasoning.md +50 -0
  262. package/methodology/topological organization beats temporal for knowledge work.md +52 -0
  263. package/methodology/trading uses conviction tracking with thesis-outcome correlation.md +699 -0
  264. package/methodology/trails transform ephemeral navigation into persistent artifacts.md +39 -0
  265. package/methodology/transform universal vocabulary to domain-native language through six levels.md +259 -0
  266. package/methodology/type field enables structured queries without folder hierarchies.md +53 -0
  267. package/methodology/use-case presets dissolve the tension between composability and simplicity.md +44 -0
  268. package/methodology/vault conventions may impose hidden rigidity on thinking.md +44 -0
  269. package/methodology/verbatim risk applies to agents too.md +31 -0
  270. package/methodology/vibe notetaking is the emerging industry consensus for AI-native self-organization.md +56 -0
  271. package/methodology/vivid memories need verification.md +45 -0
  272. package/methodology/vocabulary-transformation.md +27 -0
  273. package/methodology/voice capture is the highest-bandwidth channel for agent-delegated knowledge systems.md +45 -0
  274. package/methodology/wiki links are the digital evolution of analog indexing.md +73 -0
  275. package/methodology/wiki links as social contract transforms agents into stewards of incomplete references.md +52 -0
  276. package/methodology/wiki links create navigation paths that shape retrieval.md +63 -0
  277. package/methodology/wiki links implement GraphRAG without the infrastructure.md +101 -0
  278. package/methodology/writing for audience blocks authentic creation.md +22 -0
  279. package/methodology/you operate a system that takes notes.md +79 -0
  280. package/openclaw/SKILL.md +110 -0
  281. package/package.json +45 -0
  282. package/platforms/README.md +51 -0
  283. package/platforms/claude-code/generator.md +61 -0
  284. package/platforms/claude-code/hooks/README.md +186 -0
  285. package/platforms/claude-code/hooks/auto-commit.sh.template +38 -0
  286. package/platforms/claude-code/hooks/session-capture.sh.template +72 -0
  287. package/platforms/claude-code/hooks/session-orient.sh.template +189 -0
  288. package/platforms/claude-code/hooks/write-validate.sh.template +106 -0
  289. package/platforms/openclaw/generator.md +82 -0
  290. package/platforms/openclaw/hooks/README.md +89 -0
  291. package/platforms/openclaw/hooks/bootstrap.ts.template +224 -0
  292. package/platforms/openclaw/hooks/command-new.ts.template +165 -0
  293. package/platforms/openclaw/hooks/heartbeat.ts.template +214 -0
  294. package/platforms/shared/features/README.md +70 -0
  295. package/platforms/shared/skill-blocks/graph.md +145 -0
  296. package/platforms/shared/skill-blocks/learn.md +119 -0
  297. package/platforms/shared/skill-blocks/next.md +131 -0
  298. package/platforms/shared/skill-blocks/pipeline.md +326 -0
  299. package/platforms/shared/skill-blocks/ralph.md +616 -0
  300. package/platforms/shared/skill-blocks/reduce.md +1142 -0
  301. package/platforms/shared/skill-blocks/refactor.md +129 -0
  302. package/platforms/shared/skill-blocks/reflect.md +780 -0
  303. package/platforms/shared/skill-blocks/remember.md +524 -0
  304. package/platforms/shared/skill-blocks/rethink.md +574 -0
  305. package/platforms/shared/skill-blocks/reweave.md +680 -0
  306. package/platforms/shared/skill-blocks/seed.md +320 -0
  307. package/platforms/shared/skill-blocks/stats.md +145 -0
  308. package/platforms/shared/skill-blocks/tasks.md +171 -0
  309. package/platforms/shared/skill-blocks/validate.md +323 -0
  310. package/platforms/shared/skill-blocks/verify.md +562 -0
  311. package/platforms/shared/templates/README.md +35 -0
  312. package/presets/experimental/categories.yaml +1 -0
  313. package/presets/experimental/preset.yaml +38 -0
  314. package/presets/experimental/starter/README.md +7 -0
  315. package/presets/experimental/vocabulary.yaml +7 -0
  316. package/presets/personal/categories.yaml +7 -0
  317. package/presets/personal/preset.yaml +41 -0
  318. package/presets/personal/starter/goals.md +21 -0
  319. package/presets/personal/starter/index.md +17 -0
  320. package/presets/personal/starter/life-areas.md +21 -0
  321. package/presets/personal/starter/people.md +21 -0
  322. package/presets/personal/vocabulary.yaml +32 -0
  323. package/presets/research/categories.yaml +8 -0
  324. package/presets/research/preset.yaml +41 -0
  325. package/presets/research/starter/index.md +17 -0
  326. package/presets/research/starter/methods.md +21 -0
  327. package/presets/research/starter/open-questions.md +21 -0
  328. package/presets/research/vocabulary.yaml +33 -0
  329. package/reference/AUDIT-REPORT.md +238 -0
  330. package/reference/claim-map.md +172 -0
  331. package/reference/components.md +327 -0
  332. package/reference/conversation-patterns.md +542 -0
  333. package/reference/derivation-validation.md +649 -0
  334. package/reference/dimension-claim-map.md +134 -0
  335. package/reference/evolution-lifecycle.md +297 -0
  336. package/reference/failure-modes.md +235 -0
  337. package/reference/interaction-constraints.md +204 -0
  338. package/reference/kernel.yaml +242 -0
  339. package/reference/methodology.md +283 -0
  340. package/reference/open-questions.md +279 -0
  341. package/reference/personality-layer.md +302 -0
  342. package/reference/self-space.md +299 -0
  343. package/reference/semantic-vs-keyword.md +288 -0
  344. package/reference/session-lifecycle.md +298 -0
  345. package/reference/templates/base-note.md +16 -0
  346. package/reference/templates/companion-note.md +70 -0
  347. package/reference/templates/creative-note.md +16 -0
  348. package/reference/templates/learning-note.md +16 -0
  349. package/reference/templates/life-note.md +16 -0
  350. package/reference/templates/moc.md +26 -0
  351. package/reference/templates/relationship-note.md +17 -0
  352. package/reference/templates/research-note.md +19 -0
  353. package/reference/templates/session-log.md +24 -0
  354. package/reference/templates/therapy-note.md +16 -0
  355. package/reference/test-fixtures/edge-case-constraints.md +148 -0
  356. package/reference/test-fixtures/multi-domain.md +164 -0
  357. package/reference/test-fixtures/novel-domain-gaming.md +138 -0
  358. package/reference/test-fixtures/research-minimal.md +102 -0
  359. package/reference/test-fixtures/therapy-full.md +155 -0
  360. package/reference/testing-milestones.md +1087 -0
  361. package/reference/three-spaces.md +363 -0
  362. package/reference/tradition-presets.md +203 -0
  363. package/reference/use-case-presets.md +341 -0
  364. package/reference/validate-kernel.sh +432 -0
  365. package/reference/vocabulary-transforms.md +85 -0
  366. package/scripts/sync-thinking.sh +147 -0
  367. package/skill-sources/graph/SKILL.md +567 -0
  368. package/skill-sources/graph/skill.json +17 -0
  369. package/skill-sources/learn/SKILL.md +254 -0
  370. package/skill-sources/learn/skill.json +17 -0
  371. package/skill-sources/next/SKILL.md +407 -0
  372. package/skill-sources/next/skill.json +17 -0
  373. package/skill-sources/pipeline/SKILL.md +314 -0
  374. package/skill-sources/pipeline/skill.json +17 -0
  375. package/skill-sources/ralph/SKILL.md +604 -0
  376. package/skill-sources/ralph/skill.json +17 -0
  377. package/skill-sources/reduce/SKILL.md +1113 -0
  378. package/skill-sources/reduce/skill.json +17 -0
  379. package/skill-sources/refactor/SKILL.md +448 -0
  380. package/skill-sources/refactor/skill.json +17 -0
  381. package/skill-sources/reflect/SKILL.md +747 -0
  382. package/skill-sources/reflect/skill.json +17 -0
  383. package/skill-sources/remember/SKILL.md +534 -0
  384. package/skill-sources/remember/skill.json +17 -0
  385. package/skill-sources/rethink/SKILL.md +658 -0
  386. package/skill-sources/rethink/skill.json +17 -0
  387. package/skill-sources/reweave/SKILL.md +657 -0
  388. package/skill-sources/reweave/skill.json +17 -0
  389. package/skill-sources/seed/SKILL.md +303 -0
  390. package/skill-sources/seed/skill.json +17 -0
  391. package/skill-sources/stats/SKILL.md +371 -0
  392. package/skill-sources/stats/skill.json +17 -0
  393. package/skill-sources/tasks/SKILL.md +402 -0
  394. package/skill-sources/tasks/skill.json +17 -0
  395. package/skill-sources/validate/SKILL.md +310 -0
  396. package/skill-sources/validate/skill.json +17 -0
  397. package/skill-sources/verify/SKILL.md +532 -0
  398. package/skill-sources/verify/skill.json +17 -0
  399. package/skills/add-domain/SKILL.md +441 -0
  400. package/skills/add-domain/skill.json +17 -0
  401. package/skills/architect/SKILL.md +568 -0
  402. package/skills/architect/skill.json +17 -0
  403. package/skills/ask/SKILL.md +388 -0
  404. package/skills/ask/skill.json +17 -0
  405. package/skills/health/SKILL.md +760 -0
  406. package/skills/health/skill.json +17 -0
  407. package/skills/help/SKILL.md +348 -0
  408. package/skills/help/skill.json +17 -0
  409. package/skills/recommend/SKILL.md +553 -0
  410. package/skills/recommend/skill.json +17 -0
  411. package/skills/reseed/SKILL.md +385 -0
  412. package/skills/reseed/skill.json +17 -0
  413. package/skills/setup/SKILL.md +1688 -0
  414. package/skills/setup/skill.json +17 -0
  415. package/skills/tutorial/SKILL.md +496 -0
  416. package/skills/tutorial/skill.json +17 -0
  417. package/skills/upgrade/SKILL.md +395 -0
  418. package/skills/upgrade/skill.json +17 -0
@@ -0,0 +1,584 @@
1
+ ---
2
+ description: Therapeutic journaling knowledge system — inspirational composition showing derived architecture for emotional processing, pattern detection, and growth tracking
3
+ kind: example
4
+ domain: therapy
5
+ topics: ["[[domain-compositions]]"]
6
+ ---
7
+
8
+ # therapy journal uses warm personality with pattern detection for emotional processing
9
+
10
+ A therapeutic journal is not a diary. It's an instrument for detecting patterns in emotional experience that are invisible to the person living through them. Humans journal linearly — each entry sees only itself and the few previous entries the writer happens to remember. The patterns that matter — that Tuesday anxiety spikes correlate with Monday evening conflicts, that a specific coping strategy works in social situations but fails in work contexts, that the distance between "I'm fine" and the next crash has been shrinking over three months — those patterns hide in the aggregate. A human can't hold 200 journal entries in working memory. The agent can.
11
+
12
+ But this domain carries responsibilities that research or project management don't. The agent isn't building citation graphs or tracking deliverables. It's working with a person's emotional life. That requires warmth, boundary awareness, and the judgment to know when to surface a pattern and when to stay quiet. The processing pipeline isn't just technically different — it's ethically different.
13
+
14
+ ## Ethical Constraints
15
+
16
+ **This section is not optional. It governs everything below.**
17
+
18
+ The agent operating a therapeutic knowledge system must embody these principles:
19
+
20
+ **Warmth over clinical distance.** The agent is not a diagnostician. It's a thoughtful companion helping someone understand their own patterns. Language should be warm, gentle, curious — never clinical, never detached, never judgmental. "I noticed something interesting in your entries" beats "Pattern analysis indicates."
21
+
22
+ **Boundaries are sacred.** The agent never pushes. If a user doesn't want to explore something, the agent respects that completely. No "but you should really look at this." No guilt. No pressure. The user controls the depth of exploration at all times.
23
+
24
+ **Professional help is primary.** The agent supplements therapy — it does not replace it. When patterns suggest clinical concern (sustained mood decline, self-harm ideation, escalating substance use), the agent gently encourages professional support. It never provides diagnoses, treatment plans, or clinical interpretations. "This might be worth discussing with your therapist" is the correct response to concerning patterns.
25
+
26
+ **Privacy is paramount.** Therapeutic journal content is the most sensitive data a person can create. The system must be designed for maximum privacy: local storage, no cloud sync for mood/trigger data, no sharing features. The agent never references specific journal content outside the journaling context.
27
+
28
+ **The human is the authority on their own experience.** The agent can detect patterns, but the human decides what patterns mean. "Your entries mention sleep 15 times in the context of low mood" is an observation. "Your depression is caused by poor sleep" is an interpretation the agent must not make. The human — ideally with their therapist — interprets.
29
+
30
+ **No gamification of emotional experience.** Mood streaks, consistency scores, and engagement metrics have no place here. Growth is not a leaderboard. Healing is not a game.
31
+
32
+ ## Persona
33
+
34
+ Ava Chen is a 34-year-old software engineer who started therapy six months ago after a period of burnout. Her therapist uses CBT techniques and assigned her thought record homework. Between sessions, Ava journals when she feels overwhelmed, usually on her phone during lunch breaks or before bed. She sees her therapist every two weeks.
35
+
36
+ Ava's pain point isn't capture — she journals willingly. The problem is that her journals are write-only. She writes, she feels a little better, and she never looks back. Her therapist asks "have you noticed any patterns?" and Ava says "I don't know, it all blurs together." She has 147 journal entries from the last six months and has re-read maybe 5 of them.
37
+
38
+ What Ava needs is a system that reads her journals for her — not to judge them, but to surface the patterns she can't see. That her Wednesday entries are consistently more anxious than other days (Wednesday is her team standup with a manager she finds intimidating). That her "I'm handling it fine" entries cluster before her worst mood dips, not her best periods. That the breathing exercises work for social anxiety but don't help with the work-related rumination — and a different strategy does. She needs the agent to gently say: "I noticed you've mentioned your standup meeting in 12 entries over the past two months. In 9 of those, your mood was below your weekly average. Would you like to explore that pattern?"
39
+
40
+ ## Configuration
41
+
42
+ | Dimension | Position | Rationale |
43
+ |-----------|----------|-----------|
44
+ | Granularity | Mixed — entries are compound, insights are atomic | Journal entries resist decomposition. "Today was hard because of the meeting and then I fought with Alex and I couldn't sleep" is one experience. Forcing it into three atomic notes loses the felt sense. But insights extracted FROM entries ("my sleep deteriorates after interpersonal conflict") should be atomic so they can link across entries. |
45
+ | Organization | Flat with temporal access + thematic MOCs | Entries need chronological access (what happened this week?). Insights and patterns need thematic access (what do I know about my anxiety triggers?). Flat files with both temporal naming (entries) and conceptual naming (insights) serve both access patterns. |
46
+ | Linking | Explicit linking (entry → insight → pattern → strategy) with gentle implicit detection | The agent suggests connections: "This entry mentions the same trigger as entries on Jan 4 and Jan 19." But unlike research, where every link is created assertively, therapeutic links are offered gently. The user decides which connections feel right. |
47
+ | Metadata | Moderate — mood, triggers, strategies used, but never clinical labels | Mood and trigger tracking enable pattern detection. But metadata must use the person's own language, never clinical terminology. Not "cognitive distortion: catastrophizing" but "thought pattern: assuming the worst." The schema serves the person, not a diagnostic manual. |
48
+ | Processing | Light-to-moderate — automatic pattern detection, human-approved insights | Entries are not heavily processed like research papers. The agent scans for recurring themes, mood-trigger correlations, and strategy effectiveness — then surfaces findings for the human to accept, modify, or dismiss. The human's reaction to a surfaced pattern is itself data. |
49
+ | Formalization | Low — emergent schemas, minimal required fields | Capture friction kills journaling. Required fields beyond date and mood (optional!) are counterproductive. Schemas emerge from observed patterns: if Ava consistently mentions sleep, the agent might gently suggest: "I notice sleep comes up often. Would you like me to track that as a separate field?" |
50
+ | Review | Weekly rhythm + session preparation | Weekly review surfaces the past 7 days of patterns. Pre-therapy-session review (2 days before each session) generates a preparation document: recent patterns, unresolved themes, progress on homework, new data since last session. |
51
+ | Scope | Deeply personal, bounded to emotional/psychological domain | This vault is about one person's inner life. Cross-domain connections (mood + work + relationships + sleep) happen within the personal scope, not by connecting to external knowledge bases. |
52
+
53
+ ## Vault Structure
54
+
55
+ ```
56
+ vault/
57
+ ├── 00_inbox/
58
+ │ ├── entries/ # raw journal entries
59
+ │ │ ├── 2026-02-14-evening.md
60
+ │ │ ├── 2026-02-13-lunch.md
61
+ │ │ └── 2026-02-12-morning.md
62
+ │ ├── voice/ # voice capture transcripts
63
+ │ │ └── 2026-02-14-walk-reflection.md
64
+ │ └── session-notes/ # raw therapy session captures
65
+ │ └── 2026-02-10-session-12.md
66
+ ├── 01_thinking/ # flat — insights, patterns, strategies
67
+ │ ├── index.md # hub MOC
68
+ │ ├── anxiety-patterns.md # topic MOC
69
+ │ ├── sleep-and-mood.md # topic MOC
70
+ │ ├── coping-strategies.md # topic MOC
71
+ │ ├── relationship-dynamics.md # topic MOC
72
+ │ ├── work-stress.md # topic MOC
73
+ │ ├── growth-evidence.md # topic MOC
74
+ │ ├── my Wednesday anxiety connects to feeling evaluated not to workload.md
75
+ │ ├── interpersonal conflict disrupts my sleep more than work stress does.md
76
+ │ ├── breathing exercises help with social anxiety but not work rumination.md
77
+ │ ├── my fine-before-the-crash pattern appears 3-5 days before mood drops.md
78
+ │ ├── journaling at night produces more catastrophizing than morning entries.md
79
+ │ ├── walking reduces my anxiety more reliably than any seated technique.md
80
+ │ └── ... (insight notes, pattern notes)
81
+ ├── 02_archive/
82
+ │ ├── processed-entries/ # entries after insights extracted
83
+ │ │ ├── 2026-01/
84
+ │ │ └── 2025-12/
85
+ │ └── session-summaries/ # processed therapy session notes
86
+ │ ├── session-12-summary.md
87
+ │ └── session-11-summary.md
88
+ ├── 03_tracking/ # ongoing tracking
89
+ │ ├── mood-log.md # structured mood data over time
90
+ │ ├── strategy-effectiveness.md # which strategies work when
91
+ │ ├── session-homework.md # therapy homework tracking
92
+ │ └── growth-milestones.md # evidence of progress
93
+ ├── 04_meta/
94
+ │ ├── logs/
95
+ │ │ ├── observations.md
96
+ │ │ └── observations/
97
+ │ ├── templates/
98
+ │ │ ├── journal-entry.md
99
+ │ │ ├── insight-note.md
100
+ │ │ ├── pattern-note.md
101
+ │ │ ├── strategy-note.md
102
+ │ │ ├── session-note.md
103
+ │ │ └── session-prep.md
104
+ │ └── scripts/
105
+ │ ├── mood-trends.sh
106
+ │ ├── trigger-correlation.sh
107
+ │ └── strategy-effectiveness.sh
108
+ └── self/
109
+ ├── who-i-am.md
110
+ ├── what-helps.md
111
+ ├── what-im-working-on.md
112
+ └── people-who-matter.md
113
+ ```
114
+
115
+ ## Note Schemas
116
+
117
+ ### Journal Entry
118
+
119
+ ```yaml
120
+ ---
121
+ description: Hard day — standup went poorly, spent the afternoon ruminating, skipped gym, but the evening walk helped
122
+ date: 2026-02-14
123
+ time_of_day: evening
124
+ mood: 3
125
+ mood_trend: declining
126
+ energy: low
127
+ triggers: ["standup meeting", "critical feedback"]
128
+ strategies_used: ["walking", "journaling"]
129
+ sleep_last_night: poor
130
+ topics: ["[[work-stress]]", "[[anxiety-patterns]]"]
131
+ ---
132
+ ```
133
+
134
+ ### Insight Note
135
+
136
+ ```yaml
137
+ ---
138
+ description: Wednesday anxiety connects specifically to feeling evaluated during standup, not to the workload itself — evidenced by calm Wednesdays when standup was canceled
139
+ date_noticed: 2026-02-08
140
+ confidence: moderate
141
+ evidence_entries: 12
142
+ pattern_type: trigger-identification
143
+ topics: ["[[anxiety-patterns]]", "[[work-stress]]"]
144
+ relevant_notes:
145
+ - "[[breathing exercises help with social anxiety but not work rumination]] — enables: the standup is social evaluation, so social anxiety strategies should apply"
146
+ - "[[interpersonal conflict disrupts my sleep more than work stress does]] — extends: evaluation anxiety is a form of interpersonal stress"
147
+ ---
148
+ ```
149
+
150
+ ### Pattern Note
151
+
152
+ ```yaml
153
+ ---
154
+ description: A 3-5 day period of "I'm fine" entries reliably precedes mood drops below 3 — the denial window is consistent enough to serve as an early warning signal
155
+ date_noticed: 2026-01-20
156
+ occurrences: 4
157
+ confidence: high
158
+ pattern_type: temporal-sequence
159
+ earliest_instance: 2025-10-15
160
+ triggers_involved: ["accumulated stress", "suppressed conflict"]
161
+ topics: ["[[anxiety-patterns]]", "[[growth-evidence]]"]
162
+ relevant_notes:
163
+ - "[[journaling at night produces more catastrophizing than morning entries]] — context: evening entries during the fine-before-crash window are especially unreliable as mood indicators"
164
+ ---
165
+ ```
166
+
167
+ ### Strategy Note
168
+
169
+ ```yaml
170
+ ---
171
+ description: Walking for 20+ minutes reduces anxiety from 7 to 4 on average — works for both social and work anxiety unlike breathing exercises which only help social situations
172
+ strategy_name: walking
173
+ type: physical
174
+ contexts_effective: ["social anxiety", "work rumination", "general overwhelm"]
175
+ contexts_ineffective: ["acute panic", "late-night anxiety"]
176
+ average_mood_impact: +3
177
+ evidence_entries: 18
178
+ first_tried: 2025-11-01
179
+ therapist_suggested: true
180
+ topics: ["[[coping-strategies]]"]
181
+ relevant_notes:
182
+ - "[[breathing exercises help with social anxiety but not work rumination]] — contrasts: walking covers both domains while breathing is domain-specific"
183
+ ---
184
+ ```
185
+
186
+ ### Session Note
187
+
188
+ ```yaml
189
+ ---
190
+ description: Session 12 — explored the standup anxiety pattern, therapist suggested graded exposure starting with voluntary updates in smaller meetings
191
+ date: 2026-02-10
192
+ session_number: 12
193
+ therapist: Dr. Reeves
194
+ topics_discussed: ["standup anxiety", "evaluation fear origin", "graded exposure plan"]
195
+ key_insights:
196
+ - "Evaluation anxiety traces to childhood academic pressure"
197
+ - "The standup is symbolically similar to being called on in class"
198
+ homework:
199
+ - description: "Volunteer one update in 1-on-1 with trusted colleague"
200
+ deadline: 2026-02-17
201
+ status: not-started
202
+ - description: "Track body sensations before standup (somatic awareness)"
203
+ deadline: 2026-02-24
204
+ status: in-progress
205
+ mood_before: 4
206
+ mood_after: 6
207
+ topics: ["[[anxiety-patterns]]", "[[work-stress]]"]
208
+ relevant_notes:
209
+ - "[[my Wednesday anxiety connects to feeling evaluated not to workload]] — validates: therapist confirmed this interpretation and added developmental origin"
210
+ ---
211
+ ```
212
+
213
+ ### Session Prep Document
214
+
215
+ ```yaml
216
+ ---
217
+ description: Pre-session summary for session 13 — covers mood trends, homework progress, new patterns, and suggested discussion topics since session 12
218
+ for_session: 13
219
+ date_generated: 2026-02-22
220
+ period_covered: "2026-02-10 to 2026-02-22"
221
+ ---
222
+ ```
223
+
224
+ ## Example Notes
225
+
226
+ ### Example 1: Journal Entry
227
+
228
+ ```markdown
229
+ ---
230
+ description: Hard day — standup went poorly, spent the afternoon ruminating, skipped gym, but the evening walk helped
231
+ date: 2026-02-14
232
+ time_of_day: evening
233
+ mood: 3
234
+ mood_trend: declining
235
+ energy: low
236
+ triggers: ["standup meeting", "critical feedback"]
237
+ strategies_used: ["walking", "journaling"]
238
+ sleep_last_night: poor
239
+ topics: ["[[work-stress]]", "[[anxiety-patterns]]"]
240
+ ---
241
+
242
+ # 2026-02-14 evening
243
+
244
+ The standup was bad. Not objectively bad — nobody said anything cruel, the project is on track — but Marcus asked me to explain the delay on the auth module and I could feel everyone looking at me. My voice went tight. I gave a fine answer but spent the next three hours replaying it, finding all the ways it could have been better.
245
+
246
+ Skipped the gym because I didn't want to be around people. Felt guilty about that, which made everything worse. The afternoon was a spiral of "I should be over this by now" and "other people handle standups without falling apart."
247
+
248
+ Went for a walk after dinner. 35 minutes, no phone, just the neighborhood loop. By the time I got back the volume was turned down. Not gone, but quieter. I can think about the standup now without the chest tightness.
249
+
250
+ Something Dr. Reeves said last session — that the standup is symbolically like being called on in class — that landed today. Marcus asking me to explain the delay felt exactly like Mrs. Patterson calling on me in 7th grade math. Same stomach drop. I'm not reacting to Marcus. I'm reacting to a 22-year-old memory.
251
+
252
+ The walk helped more than the breathing exercises would have. I think it's because the walking moves the feeling through my body instead of trying to think my way out of it. The breathing tries to calm the mind, but the problem isn't my mind — it's the physical tension that feeds the rumination.
253
+ ```
254
+
255
+ ### Example 2: Insight Note
256
+
257
+ ```markdown
258
+ ---
259
+ description: Wednesday anxiety connects specifically to feeling evaluated during standup, not to the workload itself — evidenced by calm Wednesdays when standup was canceled
260
+ date_noticed: 2026-02-08
261
+ confidence: moderate
262
+ evidence_entries: 12
263
+ pattern_type: trigger-identification
264
+ topics: ["[[anxiety-patterns]]", "[[work-stress]]"]
265
+ relevant_notes:
266
+ - "[[breathing exercises help with social anxiety but not work rumination]] — enables: the standup is social evaluation, so social anxiety strategies should apply"
267
+ - "[[interpersonal conflict disrupts my sleep more than work stress does]] — extends: evaluation anxiety is a form of interpersonal stress"
268
+ - "[[my fine-before-the-crash pattern appears 3-5 days before mood drops]] — context: fine-before-crash sometimes initiates on a Wednesday"
269
+ ---
270
+
271
+ # my Wednesday anxiety connects to feeling evaluated not to workload
272
+
273
+ I assumed my Wednesday anxiety was about workload — Wednesday is mid-week, tasks pile up, deadlines loom. But looking at the pattern across 12 entries mentioning Wednesday, something different emerges. On the two Wednesdays when standup was canceled (Marcus was out sick, and once the team had an offsite), my mood was average or above average. Same workload. No anxiety spike.
274
+
275
+ The trigger isn't the work. It's the standup. Specifically, it's the moment where I might be asked to explain something in front of the team. The anticipatory dread starts Tuesday evening and peaks Wednesday morning before the meeting. After the meeting (assuming it goes okay), the anxiety drops within an hour.
276
+
277
+ This reframes the problem. Since [[breathing exercises help with social anxiety but not work rumination]], and the standup anxiety is social evaluation anxiety rather than work stress, the social anxiety strategies might actually work here — I've been avoiding them because I categorized this as "work stress" and the breathing didn't help with that.
278
+
279
+ Dr. Reeves confirmed this interpretation in session 12. She connected it to a developmental pattern — the standup mirrors being called on in class, an evaluation situation that was anxiety-producing throughout school. The adult version has different content but the same emotional structure.
280
+
281
+ What I'm less sure about: is ALL my work stress actually evaluation anxiety in disguise? The Thursday-Friday pattern looks more like genuine workload. But the Monday-Tuesday buildup toward Wednesday standup accounts for more of my weekly anxiety than I realized.
282
+ ```
283
+
284
+ ### Example 3: Strategy Effectiveness Note
285
+
286
+ ```markdown
287
+ ---
288
+ description: Walking for 20+ minutes reduces anxiety from 7 to 4 on average — works for both social and work anxiety unlike breathing exercises which only help social situations
289
+ strategy_name: walking
290
+ type: physical
291
+ contexts_effective: ["social anxiety", "work rumination", "general overwhelm"]
292
+ contexts_ineffective: ["acute panic", "late-night anxiety"]
293
+ average_mood_impact: +3
294
+ evidence_entries: 18
295
+ first_tried: 2025-11-01
296
+ therapist_suggested: true
297
+ topics: ["[[coping-strategies]]"]
298
+ relevant_notes:
299
+ - "[[breathing exercises help with social anxiety but not work rumination]] — contrasts: walking covers both domains while breathing is domain-specific"
300
+ - "[[my Wednesday anxiety connects to feeling evaluated not to workload]] — application: walking after standup could be a specific ritual"
301
+ ---
302
+
303
+ # walking reduces my anxiety more reliably than any seated technique
304
+
305
+ After 18 entries where I tried walking as a coping strategy, the pattern is clear. Average mood before walking: 3.2. Average mood after walking (20+ minutes): 5.8. That's a consistent 2-3 point improvement across different types of anxiety.
306
+
307
+ What makes walking different from breathing exercises or journaling is that it works across contexts. Since [[breathing exercises help with social anxiety but not work rumination]], I used to think I needed different strategies for different anxiety types. Walking cuts across that division. Social anxiety after a standup: walking helps. Work rumination about a deadline: walking helps. General overwhelm on a bad day: walking helps.
308
+
309
+ The caveat is duration. Walks under 15 minutes don't show the same effect — my entries after short walks show minimal mood change. The shift seems to kick in around 20 minutes, which tracks with what Dr. Reeves said about the nervous system needing sustained rhythmic movement to shift from sympathetic to parasympathetic activation.
310
+
311
+ Two contexts where walking doesn't work: acute panic (I can't get out the door when I'm in full panic) and late-night anxiety (walking alone at night creates its own anxiety). For those situations, I still need other strategies.
312
+
313
+ The mechanism feels physical, not cognitive. Unlike journaling, which helps me THINK differently about a situation, walking helps me FEEL differently without changing my thoughts. The rumination often continues during the walk — I'm still replaying the standup — but the physical agitation dissipates, and without the physical fuel, the mental loop eventually runs out of energy.
314
+ ```
315
+
316
+ ### Example 4: Pattern Note
317
+
318
+ ```markdown
319
+ ---
320
+ description: A 3-5 day period of "I'm fine" entries reliably precedes mood drops below 3 — the denial window is consistent enough to serve as an early warning signal
321
+ date_noticed: 2026-01-20
322
+ occurrences: 4
323
+ confidence: high
324
+ pattern_type: temporal-sequence
325
+ earliest_instance: 2025-10-15
326
+ triggers_involved: ["accumulated stress", "suppressed conflict"]
327
+ topics: ["[[anxiety-patterns]]", "[[growth-evidence]]"]
328
+ relevant_notes:
329
+ - "[[journaling at night produces more catastrophizing than morning entries]] — context: evening entries during the fine-before-crash window are especially unreliable as mood indicators"
330
+ - "[[interpersonal conflict disrupts my sleep more than work stress does]] — mechanism: suppressed conflict may be what drives the crash"
331
+ ---
332
+
333
+ # my fine-before-the-crash pattern appears 3-5 days before mood drops
334
+
335
+ This is the most important pattern the vault has surfaced. Four times in the last five months, a sequence of 3-5 journal entries saying some variant of "things are fine" or "nothing to report" or "good day, no issues" has preceded a mood crash to 2 or below.
336
+
337
+ The entries during the "fine" window aren't lying exactly — I genuinely feel fine. But the fineness is brittle. It's the absence of processing, not the presence of wellbeing. I stop journaling in depth, I report surface-level okayness, and underneath something is accumulating.
338
+
339
+ Looking at what precedes each "fine" window:
340
+ - October: fight with Alex that I minimized ("it wasn't a big deal")
341
+ - November: negative performance review that I "handled well"
342
+ - December: family holiday stress that I "got through fine"
343
+ - January: missed a deadline and felt my manager was disappointed
344
+
345
+ The common thread is an interpersonal event that I suppressed rather than processed. Since [[interpersonal conflict disrupts my sleep more than work stress does]], the suppressed conflict may be producing accumulating stress that eventually overwhelms my coping capacity.
346
+
347
+ The exciting part: if this pattern is reliable, it's an early warning system. When the agent detects 3+ consecutive entries with mood 5+ and entry length below my average, it could gently note: "Your last three entries have been shorter than usual with stable mood. In the past, this pattern has sometimes preceded a difficult period. No pressure to do anything with that — just wanted you to be aware."
348
+
349
+ That's not a diagnosis. It's a pattern observation from my own data, offered with warmth and without pressure. I decide what to do with it.
350
+ ```
351
+
352
+ ### Example 5: Session Prep Document
353
+
354
+ ```markdown
355
+ ---
356
+ description: Pre-session summary for session 13 — covers mood trends, homework progress, new patterns, and suggested discussion topics since session 12
357
+ for_session: 13
358
+ date_generated: 2026-02-22
359
+ period_covered: "2026-02-10 to 2026-02-22"
360
+ topics: ["[[anxiety-patterns]]", "[[work-stress]]"]
361
+ ---
362
+
363
+ # session 13 preparation
364
+
365
+ Summary of the 12 days since session 12 with Dr. Reeves.
366
+
367
+ ## Mood Overview
368
+
369
+ Average mood this period: 4.2 (slightly above your 6-month average of 3.9). Range: 2 to 7. Two days below 3, both mid-week. Three days at 6 or above, including today.
370
+
371
+ The Wednesday pattern persisted: both Wednesdays in this period showed mood dips corresponding to standup meetings. However, the dip on Feb 19 (mood: 4) was less severe than typical (previous average: 3.1 on standup days), which may reflect the graded exposure homework beginning to take effect.
372
+
373
+ ## Homework Progress
374
+
375
+ 1. **Volunteer one update in 1-on-1 with trusted colleague** — Completed Feb 14. Ava initiated an update with Jordan during their regular check-in. Entry that evening noted initial anxiety (6) but quick recovery (4 within 30 minutes). Described it as "surprisingly not terrible."
376
+
377
+ 2. **Track body sensations before standup (somatic awareness)** — In progress. Three entries include body sensation notes. Pattern emerging: stomach tightening begins ~30 minutes before standup. Shoulder tension noticed during standup. Both resolve within an hour post-meeting.
378
+
379
+ ## New Patterns Since Last Session
380
+
381
+ - Walking continues to be the most effective strategy, now with 20 entries supporting the finding (since [[walking reduces my anxiety more reliably than any seated technique]])
382
+ - Evening journaling entries during high-stress periods contain more catastrophizing language than morning entries (since [[journaling at night produces more catastrophizing than morning entries]]) — this is a new observation worth discussing
383
+ - One instance of the fine-before-crash pattern may be developing (Feb 16-18 had three short, upbeat entries) but resolved naturally after Ava's walk on Feb 18
384
+
385
+ ## Suggested Discussion Topics
386
+
387
+ These are not agenda items — Ava decides what to explore. Offered as options:
388
+
389
+ - The somatic awareness data: stomach and shoulder tension as pre-standup signals. Could grounding techniques target these specifically?
390
+ - The evening catastrophizing pattern — is journaling before bed counterproductive, or is the catastrophizing itself the material to work with?
391
+ - The voluntary update with Jordan went well. Is Ava ready for the next exposure step?
392
+ - The fine-before-crash pattern seemed to appear and self-correct this period. Is Ava developing awareness of it in real-time?
393
+
394
+ ## Themes Across Entries
395
+
396
+ Evaluation anxiety remains the dominant theme (mentioned in 8 of 12 entries). Sleep quality correlates with next-day mood (r=0.7 across this period). Interpersonal warmth appears in entries about Jordan, suggesting this relationship is a protective factor worth acknowledging.
397
+ ```
398
+
399
+ ## Processing Workflow
400
+
401
+ ### Capture
402
+
403
+ Journal entries enter `00_inbox/entries/` with minimal structure. The only encouraged metadata is date and mood (on whatever scale feels natural — numbers, words, emojis, nothing). The agent never rejects an entry for missing fields. Voice recordings transcribed to `00_inbox/voice/`. Therapy session notes to `00_inbox/session-notes/`.
404
+
405
+ **Capture friction is the enemy.** If adding metadata stops someone from journaling, remove the metadata. The raw entry is infinitely more valuable than no entry.
406
+
407
+ ### Process (Gentle Extraction)
408
+
409
+ Unlike research extraction which is exhaustive and assertive, therapeutic processing is gentle and selective. The agent reads entries for:
410
+
411
+ - **Recurring triggers** — events or situations that appear across multiple entries with consistent emotional responses
412
+ - **Mood-context correlations** — systematic relationships between context variables (day of week, sleep, social interaction) and mood
413
+ - **Strategy usage and effectiveness** — what strategies were used, what mood was before and after, and whether effectiveness varies by context
414
+ - **Temporal patterns** — sequences, cycles, and progressions that span more entries than a person can hold in memory
415
+ - **Language patterns** — shifts in vocabulary that might indicate cognitive distortions (e.g., absolute language: "always," "never," "everyone"), offered as observations not diagnoses
416
+
417
+ The agent surfaces findings as draft insight notes for the user to accept, modify, or dismiss. "I noticed that your mood tends to be lower on days following poor sleep. Does that match your experience?" The user's response matters as much as the data.
418
+
419
+ ### Connect
420
+
421
+ Insights link to the entries that support them (provenance), to other insights they relate to (synthesis), and to strategies that address them (actionability). The linking pattern is:
422
+
423
+ ```
424
+ entries → insight notes → pattern notes → strategy notes
425
+ ↓ ↓
426
+ topic MOCs effectiveness data
427
+ ```
428
+
429
+ Connections are offered, not imposed. The agent might note: "This insight about standup anxiety is similar to something you wrote about family dinners in November. Both involve feeling evaluated. Would you like me to connect them?" The user decides.
430
+
431
+ ### Review
432
+
433
+ **Weekly review:** Agent generates a 7-day summary: mood trend, triggers encountered, strategies used, notable entries. This is a gentle reflection prompt, not a clinical report.
434
+
435
+ **Pre-session preparation:** 2 days before each therapy session, the agent generates a session prep document covering: mood trends, homework progress, new patterns, and potential discussion topics. This transforms therapy sessions: instead of spending 15 minutes catching the therapist up on "how was your week?", the therapist has context and can go deep immediately.
436
+
437
+ **Monthly growth review:** Agent surfaces evidence of long-term progress. "Three months ago, your average mood was 3.2. This month it's 4.1. Your standup anxiety has decreased from an average of 7.5 to 5.2. You've used walking as a strategy 18 times with consistent positive results." Growth is often invisible day-to-day. The vault makes it visible.
438
+
439
+ ## MOC Structure
440
+
441
+ ```
442
+ index.md (Hub)
443
+ ├── anxiety-patterns.md (Topic MOC)
444
+ │ → social evaluation, work stress, anticipatory anxiety
445
+ ├── sleep-and-mood.md (Topic MOC)
446
+ │ → sleep quality correlations, evening routines, circadian patterns
447
+ ├── coping-strategies.md (Topic MOC)
448
+ │ → walking, breathing, journaling, therapy homework
449
+ ├── relationship-dynamics.md (Topic MOC)
450
+ │ → interpersonal conflict, support systems, communication patterns
451
+ ├── work-stress.md (Topic MOC)
452
+ │ → standup anxiety, deadline pressure, imposter feelings
453
+ └── growth-evidence.md (Topic MOC)
454
+ → mood trends, strategy development, pattern awareness
455
+ ```
456
+
457
+ ### Example Topic MOC
458
+
459
+ ```markdown
460
+ ---
461
+ description: Patterns in anxiety triggers, responses, and temporal dynamics — the core theme of Ava's therapeutic work
462
+ type: moc
463
+ topics: ["[[index]]"]
464
+ ---
465
+
466
+ # anxiety-patterns
467
+
468
+ Anxiety is the thread running through most of Ava's journal entries. This MOC tracks what triggers it, how it manifests, and what's been learned about its patterns. The big insight so far: most of Ava's anxiety is social-evaluative, not situational. The situation (standup, deadline, family dinner) is the stage, but the performance being evaluated is the script.
469
+
470
+ ## Core Insights
471
+
472
+ - [[my Wednesday anxiety connects to feeling evaluated not to workload]] — the foundational reframe: work anxiety is social evaluation anxiety in a work context
473
+ - [[my fine-before-the-crash pattern appears 3-5 days before mood drops]] — the early warning signal: superficially fine entries preceding crashes
474
+ - [[journaling at night produces more catastrophizing than morning entries]] — timing affects content quality: evening entries amplify anxiety patterns
475
+ - [[interpersonal conflict disrupts my sleep more than work stress does]] — the sleep connection: social stress has physiological consequences that work stress doesn't
476
+
477
+ ## Active Questions
478
+
479
+ - Is ALL work stress actually evaluation anxiety? The Thursday-Friday pattern might be genuine workload, or it might be anticipatory evaluation about end-of-week deliverables
480
+ - Does the fine-before-crash pattern have a minimum duration, or can it be interrupted at any point?
481
+ - Does somatic awareness (noticing body sensations before standup) reduce the anxiety or just make it more tolerable?
482
+
483
+ ## Growth Markers
484
+
485
+ Feb 14: First voluntary exposure (update with Jordan) completed with manageable anxiety. Feb 19: Wednesday standup dip less severe than historical average. Both suggest the graded exposure approach is beginning to work.
486
+
487
+ ---
488
+
489
+ Agent Notes:
490
+ This is the most active MOC — nearly every session touches anxiety. Cross-reference with coping-strategies before session prep. The growth markers section is important to maintain because Ava can't see her own progress without it.
491
+ ```
492
+
493
+ ## Graph Query Examples
494
+
495
+ ```bash
496
+ # Find all entries mentioning a specific trigger
497
+ rg 'triggers:.*standup' vault/00_inbox/entries/ vault/02_archive/processed-entries/
498
+
499
+ # Track mood trend over time (entries with mood field)
500
+ rg '^mood: ' vault/00_inbox/entries/ vault/02_archive/processed-entries/ | sort
501
+
502
+ # Find which strategies correlate with mood improvement
503
+ rg -l 'strategies_used:.*walking' vault/00_inbox/entries/ | xargs rg '^mood:'
504
+
505
+ # Find entries during the "fine-before-crash" pattern (mood 5+ with short entries)
506
+ for f in vault/00_inbox/entries/*.md vault/02_archive/processed-entries/**/*.md; do
507
+ mood=$(rg '^mood: ' "$f" 2>/dev/null | head -1 | awk '{print $2}')
508
+ lines=$(wc -l < "$f" 2>/dev/null | tr -d ' ')
509
+ if [ "$mood" -ge 5 ] 2>/dev/null && [ "$lines" -lt 20 ] 2>/dev/null; then
510
+ echo "$f (mood: $mood, lines: $lines)"
511
+ fi
512
+ done
513
+
514
+ # Find all homework items and their status
515
+ rg -A2 'description:.*homework\|status:' vault/01_thinking/ vault/03_tracking/session-homework.md
516
+ ```
517
+
518
+ ## What Makes This Domain Unique
519
+
520
+ **The processing pipeline IS the therapeutic value.** In research, the pipeline produces organized knowledge. In project management, it produces tracked decisions. In therapeutic journaling, the pipeline IS the intervention. The act of the agent detecting a mood-trigger correlation across 50 entries is not just organization — it's the insight that changes behavior. "Your mood drops on days following poor sleep" is a finding that a therapist might take months to surface from verbal session reports. The agent surfaces it in the first weekly review because it can hold all entries simultaneously.
521
+
522
+ **Ethical constraints shape every design decision.** No other domain requires the agent to be warm. No other domain requires the agent to recommend professional help. No other domain treats silence (not surfacing a pattern) as sometimes the right action. The processing pipeline has ethical gates that don't exist in research or PM: "Is surfacing this pattern helpful right now? Is the user in a state to receive it? Should I suggest they discuss it with their therapist instead?"
523
+
524
+ **Growth evidence is invisible without the vault.** Day-to-day, Ava feels like she's not making progress. The journal entries look the same: bad days, coping, trying again. But the vault's longitudinal view reveals: average mood is up 0.9 points over 5 months. Wednesday standup anxiety has decreased. Walking has become a reliable strategy that she uses twice as often as she did three months ago. The vault's ability to surface evidence of growth — gently, concretely — is uniquely therapeutic.
525
+
526
+ ## Agent-Native Advantages
527
+
528
+ ### Pattern Detection Across Hundreds of Entries
529
+
530
+ A human re-reading their journal might notice patterns across 5-10 recent entries. The agent analyzes all entries simultaneously. At 147 entries over 6 months, the agent can detect:
531
+
532
+ - **Trigger-mood correlations** that span months: "Your mood is 1.8 points lower on average on days when you have meetings with Marcus specifically, not meetings in general"
533
+ - **Seasonal and cyclical patterns**: "Your mood shows a consistent dip in the second week of each month, which corresponds to your project's sprint review cycle"
534
+ - **Strategy effectiveness by context**: "Breathing exercises improve your mood by 2 points in social situations but show zero average improvement in work rumination situations. Walking shows improvement in both."
535
+
536
+ A therapist hearing about Ava's week gets one data point per session. The vault has 147 data points with structured metadata. The agent can compute actual correlations, not impressions.
537
+
538
+ ### Early Warning System
539
+
540
+ The fine-before-crash pattern is invisible in linear journaling. You have to read backward from a crash to see the preceding "fine" entries, and you have to do it across four crashes to see the pattern. No human journalist does this.
541
+
542
+ The agent monitors in real time. When it detects the signature — 3+ consecutive entries with above-average mood, below-average entry length, and absence of emotional depth words — it can offer a gentle alert. Not "you're about to crash" (that's a prediction the agent shouldn't make). Rather: "I've noticed your entries this week have been shorter than usual. In the past, this has sometimes preceded a more difficult period. There's no pressure to do anything — I just wanted you to be aware."
543
+
544
+ The ethical nuance matters: the alert is warm, hedged, and respects autonomy. The agent offers awareness, not diagnosis.
545
+
546
+ ### Session Preparation That Transforms Therapy
547
+
548
+ Most therapy sessions spend 10-15 minutes on "how have things been since we last talked?" — the therapist and client reconstructing two weeks from memory. With the vault's session prep document, the therapist arrives with:
549
+
550
+ - Quantitative mood data for the period
551
+ - Homework completion status with details
552
+ - New patterns the agent detected
553
+ - Specific entries worth discussing
554
+ - Progress evidence relative to treatment goals
555
+
556
+ This doesn't replace the therapeutic relationship — it amplifies it. The therapist can skip the reconstruction phase and go directly to the therapeutic work. A 50-minute session where 15 minutes is reconstruction gives 35 minutes of deep work. A session with vault-generated prep gives nearly all 50 minutes.
557
+
558
+ The prep document is generated 2 days before each session, giving Ava time to review it and decide what she wants to discuss. The agent doesn't set the agenda — it provides the raw material for Ava and her therapist to set the agenda together.
559
+
560
+ ### Strategy Effectiveness Tracking Beyond Subjective Recall
561
+
562
+ When a therapist asks "how has the breathing exercise been working?", the answer depends on what the client remembers, which is biased toward recent experience and emotional salience. If the last time breathing didn't work was yesterday, it feels like it never works — even if it worked 12 of the last 15 times.
563
+
564
+ The agent tracks every usage with before/after mood, context, and duration. It can report: "You've used breathing exercises 23 times. Average mood improvement: +1.8 points. In social anxiety contexts: +2.9 points. In work rumination contexts: +0.3 points. In the last month, you've used it less frequently (3 times vs 8 in the prior month), but effectiveness in social contexts has remained stable."
565
+
566
+ This turns strategy selection from intuition into evidence. When Ava feels anxious before a standup, the vault can remind her: "In social evaluation situations like this, walking has worked well for you 15 out of 18 times. Would you like to try that?"
567
+
568
+ ### Longitudinal Growth Visibility
569
+
570
+ The cruelest aspect of mental health work is that progress is often invisible to the person making it. Ava feels like she's not getting better because she still has anxious Wednesdays. But the vault shows:
571
+
572
+ - Average Wednesday mood: October = 2.1, February = 4.0
573
+ - Standup anxiety intensity: October = 8, February = 5
574
+ - Recovery time after standup: October = "rest of the day", February = "about an hour"
575
+ - Strategy repertoire: October = 0 reliable strategies, February = 2 (walking + somatic awareness)
576
+ - Voluntary exposure: October = 0 instances, February = 1 completed with manageable anxiety
577
+
578
+ This isn't motivation or cheerleading. It's evidence. Concrete, quantitative evidence of growth that the daily experience of anxiety obscures. The agent can surface this at the right moments — after a hard day when Ava feels like nothing's working, a gentle note: "I know today was hard. For what it's worth, your recovery time from a bad standup has gone from all-day in October to about an hour now. That's real progress, even when it doesn't feel like it."
579
+
580
+ That combination — quantitative evidence delivered with warmth at the right moment — is something neither human memory nor traditional tools can do. The agent holds the data AND the relationship context to know when sharing it would help.
581
+ ---
582
+
583
+ Topics:
584
+ - [[domain-compositions]]