Skip to content

Start a session from a rendered framing, not a pasted transcript

List the prompt assets the repository ships, render one against the durable state, and read the context it embeds.

described Sessions and handoverbasicagentread-only

Situation

Every new session starts with the same paragraph somebody types from memory, and the repository state it describes is whatever that person last remembered.

Scenario

setup: installed
given:
  - 'Majordomus installed; the skeleton ships its prompt assets'
steps:
  - id: which
    run: ['prompt', 'list']
    note: 'the small set of versioned framings; nothing ranks them'
    expect:
      exit: 0
      stdout_contains: ['continue', 'handover', 'review']
  - id: refuse-unknown
    run: ['prompt', 'show', 'nosuch']
    note: 'an asset that does not exist is named with the command that lists them'
    expect:
      exit: 12
      stdout_contains: ['no prompt asset', 'prompt list']
  - id: the-context
    run: ['context']
    note: 'what a prompt embeds: durable state in authority order, within the budget'
    expect:
      exit: 0
      stdout_contains: ['^## GIT', '^## BUDGET']
then:
  - 'a prompt is rendered against a closed set of state tokens'
  - 'the context inside it is the same one `context` prints'

Outcome

The framing is a versioned file under .ai/repo/prompts/; rendering it embeds the assembled context, so the session starts from durable state and a budget, not from a paste.

No scenario yet

This use case is described, not proved: it names its commands and rules, and nothing executes it. It cannot be more than described until a scenario is added.

Why the tool knows this

The chain from this page to the code: the use case names commands, rules and claims; each rule is dispatched from the registry and each claim names the test that proves it; the scenario above executed the commands. Nothing in this chain is prose about intent.

The rules that make it hold

Guarantees exercised

Related use cases

Computed from what they share: claims, rules, commands, category, applications. Nobody maintains this list.