@creator-notes/cnotes 0.70.0 → 0.72.0

package/skills/attention-planner/references/card-shapes.md

@@ -23,6 +23,63 @@ Read `cnotes types show Attention` and the cnotes skill's humanizer reference
 before writing. Mention every note as `[ID: Title](relationship:verb)`; reuse
 the workspace's relationship vocabulary (`cnotes rel types`).
 
+## Seed note (timeline line)
+
+Every write that creates an Attention card, places or moves its focus block,
+or records that the card was answered or closed, has one change description.
+That description is the seed note: the line a person reads on
+`cnotes timeline`. It is one line, and it is navigation, not a summary of
+the card. The shape follows [Timeline labels are navigation, not summaries](https://creatornotes.app/blog/timeline-as-navigation)
+and the GUIDE-41 verb discipline: a movement verb, then the specific object,
+then the twist. Leave the description empty and the platform writes a title
+and a summary ("Decide on Team price range and feature scope" over "The
+author is seeking a decision..."), which is the line this template replaces.
+
+```
+{Verb} {ID}: {plain-language ask}. Canvas {canvas ID}. Focus block {date} {start} to {end}.
+```
+
+`{Verb}` comes first. It is a movement verb: `Opened` for a new card,
+`Rescheduled` when the block moves, `Answered` or `Closed` for lifecycle
+changes. Never `Created`. Never "The author...". `{ID}` is the card's display
+id. `{plain-language ask}` is what the human is asked, in plain words.
+`{canvas ID}` is the orientation canvas, or `none`. `{date} {start} to {end}`
+is the focus block in the Rules timezone (Australia/Sydney by default),
+formatted `Ddd D Mon YYYY HH:MM to HH:MM`: weekday and month in three English
+letters, the day with no leading zero, times in 24-hour `HH:MM`. One line,
+no title/summary pair.
+
+If the canvas or the block does not exist at the first write, the verb is
+still `Opened`, and the line uses `Canvas pending` and `Focus block pending`.
+Version the card once both exist. That version stays `Opened`: the block was
+placed, not moved. A card with no orientation canvas uses `none` from the
+first write, not `Canvas pending`. A later move uses `Rescheduled` and the
+new times. Recording the answer uses `Answered`. Closing the card uses
+`Closed`. Never a free-form description.
+
+On the first write, pass the line as `changeDescription` on the `notes create`
+item. Write `{displayId}` in the `{ID}` slot. The create replaces that token
+with the new display id before it stores version 1. When both the canvas and
+the block exist, and on any later reschedule, answer, or close, pass the full
+line as `--description` on `cnotes versions create`, with the real display id
+already filled in. Nothing else goes in that flag.
+
+```
+Opened ATTENTION-6K2: approve the $20 to $30 Team price as standing. Canvas CANVAS-371. Focus block Sat 10 Oct 2026 12:55 to 13:40.
+```
+
+```
+Opened ATTENTION-6K2: approve the $20 to $30 Team price as standing. Canvas pending. Focus block pending.
+```
+
+```
+Rescheduled ATTENTION-6K2: approve the $20 to $30 Team price as standing. Canvas CANVAS-371. Focus block Mon 12 Oct 2026 09:00 to 09:45.
+```
+
+This seed note is the timeline change description. It is not the outline a
+make sitting starts from, not the `--description` on `cnotes types create`,
+and not the text on an orientation banner.
+
 ## Deep card · decide
 
 ```markdown
@@ -143,7 +200,7 @@ source.>
 
 ## What the agent already did
 
-- <the outline, comparison, or research that seeds the sitting>
+- <the outline, comparison, or research the sitting starts from>
 - <what is assigned to another owner, by name>
 
 ## After the block
@@ -165,7 +222,9 @@ wedge and the two alternatives it rejects", never "time was spent".>
 
 The `Outcome` line takes what now exists, or `continue` with what is still
 missing. A make card whose outcome is `continue` stays `open` and the next run
-plans another sitting on the same card; it never mints a sibling.
+plans another sitting on the same card; it never mints a sibling. That later
+sitting is a reschedule: version the card with the seed note, verb
+`Rescheduled`, and the new block. Never a free-form description.
 
 ## Shallow card
 
@@ -236,7 +295,9 @@ mentions it from every future card, and runs intake.
 Appended as a new version the moment an answer is found, before anything is
 executed, and updated as each line lands. The tags change to
 `answered,<lane>` in the same write. A rerun reads this first: `done` is never
-repeated, `failed` is retried, `waiting` is checked for its yes.
+repeated, `failed` is retried, `waiting` is checked for its yes. The change
+description is the seed note with the verb `Answered`. It is not a title
+with a summary under it, and it does not narrate the ledger in free form.
 
 ```markdown
 ## Follow-through
@@ -256,7 +317,8 @@ N) gets a second `Follow-through` block under it, never an edit of the first.
 
 Appended as a new version only when no line above is `failed` and every
 `waiting` line names a yes that now sits on the queue. The tags change to
-`closed,<lane>` in the same write.
+`closed,<lane>` in the same write. The change description is the seed note
+with the verb `Closed`. It is not a title with a summary under it.
 
 ```markdown
 ## Closed

package/skills/attention-planner/references/evidence-ledger.md

@@ -16,6 +16,10 @@ what the customer is told if it turned out to be wrong.
 
 ## Rules
 
+- The seed note is the card's timeline line ([card-shapes.md](card-shapes.md)),
+  not a ledger row. It leads with a movement verb (`Opened`, `Rescheduled`,
+  `Answered`, `Closed`), never `Created` and never "The author is seeking...".
+  Do not turn a claim or a class into that line.
 - Columns on a deep card: `Classification`, `Claim`, `Source`, `Confidence or gap`.
 - Put the mention beside the claim. Note sources carry facts; a canvas mention
   is for orientation only, never the source of a fact.

package/skills/attention-planner/references/orientation-canvas.md

@@ -102,6 +102,12 @@ sections, portals, the banner) inside one operations run, then `place` the new
 spec. Section ids change; nothing should reference them by id. The focus block
 targets the card, not a section, so it survives the rebuild. Verify with
 `cnotes focus list` that the block still lands on the canvas and the card.
+A rebuild does not rewrite the card's change description. Placing or moving
+the block does: after that check, version the card with the seed note in
+[card-shapes.md](card-shapes.md). Verb `Opened` when the block is first
+placed, `Rescheduled` when it moves. One line, never a free-form description,
+never `Created`, never a title/summary pair. The banner's day and time is for
+the person reading this canvas. It is not that timeline line.
 
 ## Read-back test
 

package/skills/cnotes/SKILL.md

@@ -146,6 +146,7 @@ The CLI never charges a card: `create` returns a Stripe Checkout URL a HUMAN mus
 ```bash
 # List notes (default 20, excludes drafts)
 cnotes notes list [--search <query>] [--type <type>] [--tags <csv>] [--pinned] [--limit <n>]
+cnotes notes list --no-canvas [--type <type>] [--tags <csv>] [--limit <n>]   # notes on no canvas at all
 
 # Get one or more notes by display ID (always returns an array, in input order,
 # in a single round-trip). Pass one ID or many — never call this in a loop.
@@ -213,7 +214,10 @@ cnotes notes create --notes '[
   {"key":"A","type":"PainPoint","markdownFile":"./problem.md"},
   {"key":"B","type":"Insight","markdown":"# Fix\n[@A: Problem](relationship:resolves)"}
 ]'
-# Each item: {key, type, markdown | markdownFile, tags?}.
+# Each item: {key, type, markdown | markdownFile, tags?, changeDescription?}.
+# changeDescription is version 1's timeline line. `{displayId}` in it is
+# replaced with the new note's display id. Omit it and the platform later
+# writes a title plus a summary.
 # On validation failure the response lists every bad item by index + key + field
 # (and `details.items` in --json mode), so you can fix the whole batch in one shot.
 # Each .results[] item carries .type + .rubric — keep them when filtering JSON.
@@ -1091,9 +1095,11 @@ When an AI agent (including you, Claude) is doing a **batch of work** — creati
 # 1. Open the run with the user's intent as the prompt.
 #    --json includes typeRubrics: every workspace type that has a validationPrompt.
 #    Read the rubrics for the types you will author BEFORE drafting.
-#    With --prompt it also returns brief.notes: the workspace notes most
-#    relevant to the task. Read them BEFORE suggesting anything; a Decision,
-#    Guide or Metric there may already settle what you were about to propose.
+#    With --prompt it also returns a brief (brief.notes, brief.canvases,
+#    brief.changes): the notes, canvases and recent changes most relevant to the
+#    task. Read it BEFORE suggesting anything; a Decision, Guide or Metric there
+#    may already settle what you were about to propose. Not opening a run?
+#    `cnotes brief "<task>"` returns the same brief, read-only.
 cnotes operations begin --prompt "Reorganize roadmap into quarters" --json
 cnotes types show Insight   # or pull from .typeRubrics in the begin response