/prznt

OrientThe system holds context before any command acts.

Memory Layer

context

How it runs

Business, brand, strategy, infrastructure, safety, and source locations sit here.

Output

Commands start with the larger context in view.

Inside

Holds the context the system sits inside
Routes work to the right source of understanding
Keeps public work, client work, and internal work aligned

The system starts from understanding, not a blank prompt.

Memory Review

/memory-review

How it runs

Walks a memory file sentence by sentence, quotes the exact text under review, and asks one question at a time.

Output

Keeps the durable record accurate so the automations reading from it do not drift.

ConvertCalls, sources, and drafts become usable material.

Debrief

/debrief

How it runs

Reads a recorded meeting, identifies the call type, and pulls the claims that matter. Each claim points back to the transcript.

Output

Produces a sourced debrief with commitments, objections, urgency signals, next steps, and the strategic frame for the relationship.

Voice

/voice

How it runs

Walks the request through a process tree, applies global voice rules, adds client voice when Prime is active, and scores the draft for clarity.

Output

Drafts and refines emails, posts, bios, docs, replies, and other professional writing so it sounds like the person sending it.

Learnings

/learnings

How it runs

Reads a meeting transcript or video captions, asks what the source should help with, and extracts through five reusable lenses.

Output

Creates a tagged markdown file of atomic learnings plus an HTML idea sheet. The same lenses make calls, talks, and reading searchable together.

OperateAlaia holds the operating state. Commands move work through it.

Alaia

operational record

How it runs

Stores the client, opportunity, debrief, project, invoice, reminder, and hour records the automations depend on.

Output

Gives the work a current operating state: who it belongs to, what was promised, what is billable, what is open, and what should happen next.

Inside

Connects clients, opportunities, notes, projects, invoices, and hours
Receives billable time from Prime
Keeps debriefs and commitments attached to the relationship
Gives Leader and planning work a trusted client record

The automations become parts of one client operating system.

Prime

/prime

How it runs

Starts a client clock and loads the client's working memory into the session: context, voice, design, and open work.

Output

Makes the session client-aware and time-tracked from the first response. The clock survives resets, crashes, and long work blocks.

Invoice

/invoice

How it runs

Pulls client hours for a date range, asks for missing notes, and renders the invoice in the house format.

Output

Creates a sendable HTML and PDF invoice with the next client-specific invoice number.

Leader

/leader

How it runs

Gathers open tasks, follow-ups, debrief commitments, and calendar context, then walks the day one decision at a time.

Output

Turns scattered inputs into a confirmed day plan. Each item gets dispatched, deferred, rejected, or clarified before it moves.

Planner

/planner

How it runs

Walks the decision tree in dependency order, answers what the codebase can answer, and asks only what needs human judgment.

Output

Stress-tests the plan until the build, reason, constraints, and open risks are clear.

Dispatcher

/dispatch

How it runs

Fans out independent background agents, each with its own state file, status, and blocker channel.

Output

Runs unrelated tasks in parallel across repos. Each agent checkpoints to disk so work can resume after a clear, crash, or context reset.