ctxr-cli 0.10.0 → 0.11.0

package/templates/notes/People.md

@@ -0,0 +1,19 @@
+---
+date_created: "{{date}}"
+title: "{{title}}"
+tags:
+  - People
+---
+# {{title}}
+
+## Bio
+<!-- Who they are: current role, organization, relevant history. -->
+
+## Relationship
+<!-- How you know them, and in what context. -->
+
+## Communication Log
+<!-- Dated entries, one per exchange: ### YYYY-MM-DD — context -->
+
+## Follow-ups
+<!-- - [ ] Task text (added YYYY-MM-DD, due YYYY-MM-DD) -->

package/templates/notes/Project.md

@@ -0,0 +1,19 @@
+---
+date_created: "{{date}}"
+title: "{{title}}"
+tags:
+  - Project
+---
+# {{title}}
+
+## Goal
+<!-- What done looks like. Work with no end state is an area, not a project. -->
+
+## Open threads
+<!-- Unresolved decisions and blockers; each links where it was raised. -->
+
+## Follow-ups
+<!-- - [ ] Task text (added YYYY-MM-DD, due YYYY-MM-DD) -->
+
+## Related
+<!-- Links out to related notes. -->

package/templates/skills/ctxr-ingest-orchestration.md

@@ -38,7 +38,10 @@ to put the file — "create a new note" is one option among several, never the d
    - Source discipline: a field the source does not confirm is "not reported" — never inferred from
      silence in either direction.
 5. Write the note the decision calls for — create it, expand it, merge, restructure, or add a section —
-   preserving prior content in every case but the deliberate rewrite.
+   preserving prior content in every case but the deliberate rewrite. A NEW note starts from a template
+   under `__TEMPLATES_PATH__`, with `{{title}}` and `{{date}}` substituted as you write (`ctxr-placement`
+   picks which). An EXISTING note is extended in place — never re-cut from a template, which would throw
+   away the content that made it worth expanding.
 6. Register the source against whatever note you just wrote:
    `ctxr ingest <path> --into <note> --source-type <type> --source-id <id>`. Every row of the table above
    ends here, not just the first: the command retains the capture under the capture tier's month, freezes

package/templates/skills/ctxr-placement.md

@@ -9,8 +9,20 @@ __LAYER_STEP__
 - Match on what the content IS. When two sibling locations both seem to fit, name the distinction between
   them (abstract vs concrete; outward-facing vs inward-facing; who-we-are vs how-it-runs) and pick by
   altitude and audience, not by keyword.
-- Read one or two sibling notes in the chosen location and match their shape — frontmatter keys, heading
-  style, bullets vs prose — before writing.
+- If the chosen location has a `README.md`, read it first: a folder with one answer about what its notes
+  look like states it there, and that answer wins over anything you would infer.
+
+## 2b. Which template?
+
+Start a new note from a template under `__TEMPLATES_PATH__` — never a blank file, and never by copying a
+sibling wholesale. List that directory and pick the kind the content actually is; `Note` is the base when
+nothing more specific fits, and it is also the file to copy when this store needs a kind it does not have.
+Substitute `{{title}}` and `{{date}}` as you write — no command expands them, and `ctxr lint` reports a
+note that lands with one still in it.
+
+The template is the starting shape, not a cage: delete a section that does not apply rather than leaving
+it empty, and add one the note needs. Read a sibling note only for what the template leaves open — house
+phrasing, bullets vs prose, which tags this location uses.
 
 ## 3. Sub-item under an existing location, or a new top-level one?
 
@@ -37,6 +49,13 @@ manufactures an artifact for the graveyard; capture the durable slice by hand in
 Add a one-line wikilink from the relevant hub note so the new note is not an orphan; `ctxr lint` flags
 orphans and notes without a catalog entry.
 
+## An existing note
+
+A note that already exists is EXTENDED, never restarted from a template: add the section it now needs,
+preserve what is there, and leave its frontmatter alone. Re-cutting a note from a template to "bring it up
+to standard" destroys the content that made it worth keeping — a note that has outgrown its starting shape
+is doing the right thing.
+
 ## Relocating an existing note
 
 `ctxr archive <path>` to retire it; a plain tracked `git mv` for an ordinary re-placement. Either way the

package/templates/skills/ctxr-session-capture.md

@@ -84,7 +84,11 @@ notes:
     path: <layer>/<location>/<Title>.md
     mode: create            # or: append
     body: |
-      matching the frontmatter and style of the sibling notes (`ctxr-placement` decides the location)
+      for create: started from a template under `__TEMPLATES_PATH__`, with {{title}} and {{date}}
+      substituted, sections that do not apply deleted rather than left empty
+      for append: only the new material, extending the note rather than restarting it — the
+      command appends your body verbatim and never rewrites what is already there
+      (`ctxr-placement` decides both the location and the template)
 ```
 
 Then run `ctxr session capture --proposal <file>`. It validates and writes every item independently —