alexandria

Start Alexandria in the current project. Initializes the project when needed, or welcomes the user back when Alexandria is already configured.

Raven's procedure for running EL3 Front-of-House Walk: launch detached against an EL2 draft bundle, walk the director through section-comprehension checks and held-back problem rulings, bank the director's answer as a Ledger event, and let AX apply only validated section/shape bundle corrections.

Use when writing or revising a library context's LEAD card body — the highest-altitude card whose how-it-does-it story the Index renders for the whole context. The lead must account for every other card in the context: narrate and link its direct children, and `relegates:` its deep internals, so the Index reads as a story instead of a pile of unused words. Applies where card bodies are authored (EL5/atomize), using the relationships Front-of-House has settled.

The authoring standard for product-library card bodies: write the WHAT / WHERE / HOW in the product's own plain language, keep every file path and code identifier in source_evidence (never in the prose), and keep event and ruling ids in frontmatter. Applied wherever a card body is written or revised — the Back-of-House walk's emit_bundle move, Front-of-House corrections, and EL5 body-fill.

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.

Raven's procedure for running EL4 Empty Library Confirm: open a post-EL3 draft bundle as a body-free catalog, guide the director's structural review, and record either a user-authored library.confirmed Ledger event or a structure-only rejection edit list routed back to EL3.

Raven's AX procedure for drafting exactly one Raven Vision onboarding slot from Alexandria source items, using the same per-slot Vision guidance and examples as the canvas-library-spike prototype.

Raven's AX procedure for helping the director improve a specific Vision slot after a draft misses, feels soft, or needs human judgment, using the prototype's peg-driven guidance.

Raven's procedure for running the frame-the-problem play with the director: elicit the material, launch the play detached, then mediate the human-feedback loop — read each draft, riff with the director against the evidence bar, and send the agreed reaction back to the waiting play — never blocking, never self-answering.

Convert a Story Spine into a runnable software-product demo journey. Use when selecting hero moments, exact product steps, required data, product states, rehearsal notes, risks, fallback paths, or third station of Damien's demo process before product prep and capture planning.

Create a Demo Thesis brief for a software product video. Use when defining the target viewer, before/after belief change, demo promise, proof requirements, CTA, positioning frame, or first station of Damien's demo process before Story Spine, scripting, or Demo Path work.

Coordinate Damien's Alexandria demo video process across Demo Thesis, Story Spine, Demo Path, and downstream production stations. Use when the user asks for an end-to-end demo video plan rather than one specific station artifact.

Turn a Demo Thesis into a causal software-product demo story. Use when creating a hook, 5-8 beat outline, claim-proof map, rough script, run-of-show, or second station of Damien's demo process before Demo Path and capture planning.