Synapse Creation
Establish the corpus boundary
Read ../../../.github/specs/synapse-create.spec.md when present. Resolve the input set, operating mode, depth, output profile, destination, privacy constraints, and whether existing corpus modification is allowed.
Inspect before writing
Search existing synapses, aliases, titles, sources, and neighboring concepts. Identify overlap, contradiction, supersession, and missing connections before creating a new file.
Apply the Synapse Test
Accept a candidate only when it expresses a durable, reusable relationship or developed insight that can stand as a bounded knowledge object. Reject or defer raw notes, isolated facts, quotations without synthesis, tasks, source dumps, and fragments that require further extraction.
Reconcile and develop
- Prefer updating or connecting an existing synapse when it already owns the concept.
- Bound each new synapse around one central relationship.
- Preserve observed content, interpretation, uncertainty, and temporal scope.
- Add required frontmatter, source trail, lifecycle state, classification, and links.
- Explain the core synapse, context, why it matters, and relevant connections.
- Use repository naming and placement rules; do not invent new taxonomies casually.
Protect the corpus
Do not overwrite, merge, relocate, or bulk-migrate existing synapses without the governing approval gate. Keep sensitive personal material contextual and minimal. Never convert interpretation into fact or remove contradictory source evidence.
Validate and report
Check atomicity, uniqueness, metadata, links, source availability, provenance, uncertainty, placement, and safety. Report created, updated, skipped, conflicted, and deferred candidates with the reason for each decision.
1---2name: synapse-creation3description: Create, refine, connect, audit, or migrate atomic Mind Garden synapses from developed knowledge. Use when evaluating the Synapse Test, reconciling duplicate insights, writing source-linked knowledge notes, adding relationships, organizing lifecycle metadata, or reviewing an existing synapse corpus.4---56# Synapse Creation78## Establish the corpus boundary910Read `../../../.github/specs/synapse-create.spec.md` when present. Resolve the input set, operating mode, depth, output profile, destination, privacy constraints, and whether existing corpus modification is allowed.1112## Inspect before writing1314Search existing synapses, aliases, titles, sources, and neighboring concepts. Identify overlap, contradiction, supersession, and missing connections before creating a new file.1516## Apply the Synapse Test1718Accept a candidate only when it expresses a durable, reusable relationship or developed insight that can stand as a bounded knowledge object. Reject or defer raw notes, isolated facts, quotations without synthesis, tasks, source dumps, and fragments that require further extraction.1920## Reconcile and develop21221. Prefer updating or connecting an existing synapse when it already owns the concept.231. Bound each new synapse around one central relationship.241. Preserve observed content, interpretation, uncertainty, and temporal scope.251. Add required frontmatter, source trail, lifecycle state, classification, and links.261. Explain the core synapse, context, why it matters, and relevant connections.271. Use repository naming and placement rules; do not invent new taxonomies casually.2829## Protect the corpus3031Do not overwrite, merge, relocate, or bulk-migrate existing synapses without the governing approval gate. Keep sensitive personal material contextual and minimal. Never convert interpretation into fact or remove contradictory source evidence.3233## Validate and report3435Check atomicity, uniqueness, metadata, links, source availability, provenance, uncertainty, placement, and safety. Report created, updated, skipped, conflicted, and deferred candidates with the reason for each decision.
egohygiene