> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aiblueprint.web.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Revise with the Blueprint Assistant

> Ask questions, stage one or several proposals, and regenerate only affected documents.

The Blueprint Assistant uses the approved context for the current project. A chat response does not silently change your documents. Changes are staged as proposals for your review.

## Ask, review, apply

<Steps>
  <Step title="Ask a question or request a change">
    Be explicit about the outcome and constraint. You can ask for a recommendation first, then say **draft this as a proposal**.
  </Step>

  <Step title="Review the proposal card">
    Check the rationale, proposed actions, and affected documents. Nothing changes at this stage.
  </Step>

  <Step title="Decline or keep it pending">
    Decline proposals you do not want. You can leave valid proposals pending while you add related changes.
  </Step>

  <Step title="Apply one or apply all">
    Use **Apply** for one proposal. When two or more proposals are waiting, use **Apply all** so affected documents regenerate once as a consistent batch.
  </Step>

  <Step title="Review regenerated documents">
    Regeneration supersedes the whole-Blueprint approval and locks Project ZIP. Open every changed current version so it becomes **Reviewed**, then return to Blueprint Summary and use **Sign Approve Blueprint** once for the complete current set.
  </Step>
</Steps>

<Frame caption="Sanitized example: two proposals are staged before one regeneration.">
  <img src="https://mintcdn.com/ia-blueprint/xvYlFUH0B2wc9dt4/images/assistant-proposals.svg?fit=max&auto=format&n=xvYlFUH0B2wc9dt4&q=85&s=b9e593a262bbe0cfbded1333604f5095" alt="Blueprint Assistant with two pending proposals and Apply all" width="1200" height="650" data-path="images/assistant-proposals.svg" />
</Frame>

## Single and multiple proposals

Use a single proposal for an isolated change, such as renaming an actor or correcting one rule. Stack proposals when decisions are related, such as changing an approval flow, permissions, and acceptance criteria together.

<Tip>
  Batch related proposals before applying them. One batch keeps the document set aligned and avoids separate regeneration cycles.
</Tip>

## Direct edits and AI-backed revisions

A literal direct edit that does not call AI is free. An AI proposal or rewrite can use credits. The interface shows the applicable action before you commit it.

## Two kinds of history

* **Revision history** inside the Assistant records conversation-level context revisions.
* **Blueprint versions** records the whole set of generated documents as one recoverable version.

Use Blueprint versions when you need to restore the complete document set to an earlier consistent state.

<Warning>
  Applying a proposal can change more than one downstream document. Do not approve the Blueprint again until generation finishes and every changed current version has been reviewed.
</Warning>