log_event
Log progress events like goals, decisions, and next steps to preserve context for future sessions. Each event is atomic and concise, ensuring the brief stays skimmable and linked to related knowledge.
Instructions
Record a progress signal for the current work session.
Call this proactively as work happens — every time you set or change the goal, make a non-trivial decision (and why), hit a dead-end worth not repeating, touch an important file, surface an open question, or decide the next step.
Keep each event ATOMIC and concise: one item per call, 1-2 sentences. Log several small events rather than dumping a whole session summary into one — the brief is meant to stay skimmable. Reference durable notes inline as [[Entity]] so they link in the brief's "Related knowledge".
This is how the next session inherits your context. Returns the new event
id (use it later in supersedes). If supersedes_query retired a prior
event, a second line names which id was retired (or notes that none
matched), so the retraction is auditable.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | One of: 'goal' (what this session is achieving), 'decision' (a choice made — include the rationale), 'deadend' (something tried that failed — so it isn't repeated), 'file' (a file touched or relevant), 'question' (an open question), 'next_step' (the concrete next action). | |
| content | Yes | One atomic item in 1-2 sentences (a decision + its why, a single dead-end, one next step) — not a multi-paragraph session summary. Reference durable notes inline as [[Entity]] to link the graph. | |
| project | No | Project namespace; defaults to the current session's project. | |
| importance | No | Priority 1-5 (5 = critical). Higher items survive the brief budget. | |
| supersedes | No | Ids of earlier events this one makes obsolete (e.g. a reversed decision). Superseded events are excluded from future briefs. | |
| supersedes_query | No | Retire a prior event you don't have the id for: the single best-matching ACTIVE event of the SAME type in this project is found by keyword search and superseded. Use when you change a past decision but don't know its id. The retired id is reported back and recorded, so it stays auditable. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |