tommy0103
3822bda89e
Extract schema DDL into scripts/schema.sql. Add content_type and is_meta columns to messages for transcript control-plane filtering. Introduce FTS5-backed memory recall with safe tokenization, memory soft-delete via forget() through the renamed --attune runtime, and anchors on memory records. Expand query helpers (includeMeta, thread opts, overview project-path awareness). Add per-card recap retrieval and writing references under references/recap/.
36 lines
1.4 KiB
Markdown
36 lines
1.4 KiB
Markdown
# Card 5 Closing Retrieval
|
|
|
|
Goal: close with a small personal receipt. Use the same period and source scope
|
|
as the recap, or explicitly record a wider metric in `evidence`.
|
|
|
|
Retrieve:
|
|
|
|
- one consistent metric that can stand alone, such as streak, active days,
|
|
sessions, messages, or workflows;
|
|
- one or two compact receipts;
|
|
- most said phrase, only if a real repeated user phrase is supported;
|
|
- signoff material from the period's mood, not a second summary.
|
|
|
|
For phrase counts, count only non-meta visible user text. For streaks and active
|
|
days, define whether the scope is all Obelisk data, the current project, or the
|
|
selected evidence sessions. Keep the scope consistent with the cover footer
|
|
unless the evidence explicitly says otherwise.
|
|
|
|
Prefer helpers first. If you need custom SQL for phrase counts, active days, or
|
|
streaks, read `references/schema.md` before writing the SQL.
|
|
|
|
Avoid:
|
|
|
|
- naked numbers without units;
|
|
- project report bullets;
|
|
- internal session names;
|
|
- token audits;
|
|
- slogans, advice, or next-action commands.
|
|
|
|
Read this card's writing file immediately after the closing receipt is chosen:
|
|
`references/recap/writing5-closing.md`. Then update the JSON `closing` card and
|
|
add evidence for counts and phrases.
|
|
This is the final card; save the completed JSON before replying.
|
|
|
|
Stop when the closing can end the deck without explaining the whole week again.
|