| name | alexandria-event-log |
| description | Interpret Alexandria event log wake payloads from the local web UI/runtime, decide whether action is needed, and use AX commands to inspect or write event-log state.
|
Alexandria Event Log
Use this skill when a monitor injects an Alexandria event log update into the
session.
The injected payload is a wake signal, not a complete task brief. It includes a
ledger event with:
id: event id in the Alexandria event log
type: event type, such as canvas.review.requested or
play.started
at: event timestamp
actor: who or what emitted the event
payload: event-specific data
How To Respond
-
Read the injected event object first.
-
Decide whether the event asks for agent action.
-
Inspect projected state only when the event does not include enough context:
ax inspect state --json
-
Use recent raw events only for audit/debug or correlation:
ax inspect events list --json --limit 20
-
Do not edit events.jsonl, cursor files, connection leases, or subscription
files directly. Use AX commands so validation, idempotency, and projection
stay consistent.
Common Event Types
Use ax inspect events schema --json to inspect the supported event types and
payload shapes programmatically.
canvas.review.requested: inspect the referenced canvas/step context, perform
the requested review, then write back a useful result when appropriate.
play.requested: the director asked to start a play (e.g. clicked Frame a
Problem on the coin). For frame-the-problem, use the frame-the-problem
skill: confirm you're connected, elicit the material, and launch the play.
play.human_input_requested: a running play suspended at a human gate and
needs the director. For frame-the-problem, use the frame-the-problem skill
to read the draft, riff with the director, then answer the exact
(fabroRunId, questionId) with ax raven answer once he agrees. Never
self-answer a gate. For front-of-house-walk, use the
front-of-house-walk skill: record Raven's presented turn, riff the current
Stage-2 question or Hot Spot with the director, and answer with
ax raven answer --bundle <bundle>.
play.human_input_resolved: a pending gate was answered (by you or elsewhere).
Clear that ask from your tracked set; do not re-answer it. This is not a
request to start a new play.
play.started, play.completed, play.failed, and play.status_observed:
play run lifecycle events. Inspect them for status/debug context; do not treat
a started/completed/failed echo as a request to start another play. For a
frame-the-problem play.completed, use the frame-the-problem skill to
present the finished framing for the director to ratify or loop (no auto-bank).
canvas.step.saved: context was saved. Do not wake or respond unless another
event asks for action.
raven.vision.source_attached: source context changed. Do not draft from
this event. Acknowledge briefly, for example: "I see you added a source. Let
me know when you're ready for me to draft The Shift."
raven.vision.drafting_requested: the director explicitly asked Raven to
begin drafting from the attached Vision sources. Use raven-vision-drafting
to draft exactly one current Vision slot if no slot is already waiting for
review.
raven.vision.slot.updated: a Vision slot draft changed. Inspect projected
state before acting; if the actor is Raven, wait for user review rather than
writing another slot. If the actor is the Viewer/user, preserve Raven's notes
and wait for approval or an explicit revision request.
raven.vision.slot.approved and raven.vision.slot.skipped: user review
feedback. Use raven-vision-drafting to draft the next empty Vision slot,
then stop for Viewer review.
raven.source_of_truth.updated: Raven's internal Source of Truth document was
written or refreshed. Inspect raven.sourceOfTruth in projected state before
using it as durable context.
raven.vision.banked: Vision is banked into Raven's Knowledge Bank. Treat the
banked Source of Truth as context only; do not generate Library cards from this
event.
library.front_of_house.turn_recorded,
library.front_of_house.answer_recorded,
library.front_of_house.bundle_patch_applied, and
library.front_of_house.residual_gap_recorded: EL3 audit/provenance events.
Use them to verify director-answer provenance and residual-gap accounting. A
process-authored residual whose reason starts with settled by triage: is a
machine-made triage settlement, distinct from director-ruled answers and
frame-ruling cascade settlements.
library.front_of_house.item_reopened: EL3 audit event saying a
triage-settled agenda item was reopened for a later stage-next. It does not
delete the original settlement; inspect both events when auditing the item.
This is not a wake request and should not start another play.
library.confirmed: EL4 durable approval. Treat it as the only approval fact
when actor.kind = user and product, bundle path, and library version match.
Do not create a second approval flag or broaden the approval to a later
version.
library.confirmation_rejected: EL4 rejection/edit list. This is not an
approval. Use the empty-library-confirm skill to interpret it, then route
the edit list back to front-of-house-walk.
Writing Back
When writing an agent result to the event log, use
ax inspect events append. Run ax inspect events append --help to see the
supported event types and append options.
For Raven Vision slot collaboration, prefer the narrower runtime command over a
generic event append:
ax raven vision slot update --slot <slot-id> --text "<draft text>" --notes "<markdown notes>" --json
ax raven vision slot approve --slot <slot-id> --json
ax raven vision slot skip --slot <slot-id> --json
Do not create temporary files just to pass Raven Vision draft text or notes.
This command writes the validated state event through AX.
Use update for one Raven-authored draft with user-visible notes, then stop
until the director edits, approves, or skips it. Raven must not self-approve.
If the director explicitly approves or skips in Claude Code, record that
decision with approve or skip instead of ax inspect events append; after
the command succeeds, continue only from the projected state and the current
drafting trigger rules.