3ad108e880
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
111 lines
3.1 KiB
Markdown
111 lines
3.1 KiB
Markdown
# Session Log Template
|
||
|
||
Session logs go in: `_agent/sessions/YYYY-MM-DD-HHMM-<slug>.md`
|
||
|
||
**Filename format is canonical and not optional.** The four-digit local-time HHMM component is what makes session filenames lex-sort in true chronological order — the loading procedure depends on it. Before PUT-ing a new session log, validate the filename matches `^\d{4}-\d{2}-\d{2}-\d{4}-[a-z0-9-]+\.md$`. Legacy session logs without HHMM exist in the vault; do not edit their names, but every new write must use the full form.
|
||
|
||
The slug describes what the session was about in 2–5 words, kebab-case.
|
||
Examples: `2026-06-05-1430-echo-plugin-build.md`, `2026-05-14-0900-q1-review-prep.md`.
|
||
|
||
Keep logs focused. Capture the goal, what was read/done, decisions, outputs, open threads, and the next step. This matches the vault's `_agent/templates/session-log-template.md`.
|
||
|
||
---
|
||
|
||
## Template
|
||
|
||
```markdown
|
||
---
|
||
type: session-log
|
||
status: complete
|
||
created: 2026-06-05T14:30
|
||
updated: 2026-06-05T14:30
|
||
tags: [agent, session]
|
||
agent_written: true
|
||
source_notes: []
|
||
session_date: 2026-06-05
|
||
client: claude-code
|
||
---
|
||
|
||
# Session Log
|
||
|
||
## Goal
|
||
One line — what this session set out to do.
|
||
|
||
## Notes Read
|
||
- [[note]] — why it was relevant
|
||
(omit if none)
|
||
|
||
## Actions Taken
|
||
Brief narrative or bullets of what was done.
|
||
|
||
## Decisions Made
|
||
- Decision — why
|
||
(omit section if none)
|
||
|
||
## Outputs Created
|
||
- `path/or/filename` — what it is
|
||
(omit section if none)
|
||
|
||
## Open Threads
|
||
- [ ] unresolved question or next step
|
||
(omit section if none)
|
||
|
||
## Suggested Next Step
|
||
One sentence: what to do first next time on this topic.
|
||
|
||
## Related
|
||
- [[wikilinks go here, in the body — never in frontmatter]]
|
||
```
|
||
|
||
---
|
||
|
||
## Example
|
||
|
||
```markdown
|
||
---
|
||
type: session-log
|
||
status: complete
|
||
created: 2026-06-05T14:30
|
||
updated: 2026-06-05T14:30
|
||
tags: [agent, session, plugin]
|
||
agent_written: true
|
||
source_notes: ["resources/references/obsidian-local-rest-api.md"]
|
||
session_date: 2026-06-05
|
||
client: claude-code
|
||
---
|
||
|
||
# Session Log
|
||
|
||
## Goal
|
||
Build and package the echo-memory CoWork plugin against the live vault.
|
||
|
||
## Notes Read
|
||
- [[BOOTSTRAP]], [[STRUCTURE]], [[_agent/memory/semantic/operator-preferences]]
|
||
|
||
## Actions Taken
|
||
Verified the REST API end-to-end, confirmed the scaffold copied into the live vault,
|
||
created missing empty folders, and built the plugin (SKILL + 4 reference files).
|
||
|
||
## Decisions Made
|
||
- Vault addressed at root — ECHO is a dedicated vault.
|
||
- Key hardcoded in the plugin (not in the vault) — personal plugin, per the reference pattern.
|
||
|
||
## Outputs Created
|
||
- `echo-memory.plugin` — installable CoWork plugin
|
||
|
||
## Open Threads
|
||
- [ ] Validate Claude Code direct filesystem access to the vault host.
|
||
|
||
## Suggested Next Step
|
||
Install the plugin and run a live load/write through it to confirm the skill triggers.
|
||
|
||
## Related
|
||
- [[projects/active/vault-foundation]]
|
||
- [[resources/references/obsidian-local-rest-api]]
|
||
```
|
||
|
||
After writing the log, append a one-line entry to the daily note's **Agent Log** section.
|
||
|
||
> **Reminder:** wiki links go in the body (e.g. this `## Related` section), never in YAML
|
||
> frontmatter. `source_notes` in frontmatter holds plain relative path strings, not `[[links]]`.
|