> ## Documentation Index > Fetch the complete documentation index at: https://docs.bluegenai.com/llms.txt > Use this file to discover all available pages before exploring further. # Editing your CAB > Changing a generated blueprint manually or by asking the agent, reviewing what changed, and what the version history does and does not record. A generated blueprint is a first draft, and there are two ways to change it: edit it yourself, or ask the CAB agent to. Both routes end in the same place: a review screen where you accept or discard each change before anything is written. ## The Blueprint Toolbar The blueprint preview toolbar beside the Generate Tickets button, its six icon buttons labelled Version History, Open in New Tab, Share CAB, Edit CAB, Download Markdown and Download PDF. A badge on the Version History clock shows the number of saved versions. | Button | What it does | | ----------------- | -------------------------------------------------------------- | | Version History | Opens the list of saved versions | | Open in New Tab | Opens the blueprint full-page | | Share CAB | Shares the blueprint with people who have no BlueGenAI account | | **Edit CAB** | **Enters manual edit mode** | | Download Markdown | Downloads the blueprint as a text file | | Download PDF | Downloads it as a PDF | Hover over any of the icons to get an explanation of its function. **Version History appears only once the blueprint has more than one saved versions**, so a freshly generated blueprint shows no version history. ## Sharing a Blueprint Outside the Platform **Share CAB gives a blueprint to people who do not have a BlueGenAI account.** A stakeholder, a client, or a colleague on the business side can read the whole document from a link, without signing up and without being added to the project. This is what makes a blueprint usable as a review artifact. A specification is only worth generating if the people who need to agree with it can read it, and most of them are not platform users. A shared blueprint needs no account and no approval; anyone holding the link can read it. Share it only where you would be content for the whole document to travel. **You may turn off the sharing link at any time** **Note** that this is a different mechanism from inviting someone to the project. An invitation gives a person a role and a sign-in; a share link gives one document to anyone who has the URL. See [Collaboration Features](/admin-platform/collaboration-features). ## Editing It Yourself **Edit CAB** turns the blueprint into a form. After a few seconds the panel title gains an **Editing** pill and the toolbar becomes **Review with AI**, **Save Changes**, and a close control. The blueprint in edit mode with a single field focused, showing a blue focus border around an editable value inside the rendered document. **The editor knows the blueprint's structure.** You are editing fields, not a document. Click any value to change it. Every list ends with a labelled control for adding an item: `+ Add acceptance criteria`, `+ Add field`, `+ Add role`. Hovering an item offers controls to insert a sibling or remove it. A list item shown struck through and greyed out, marking it for removal once the edit is saved. **Removals are pending until you save.** A removed item stays on screen struck through, so you can see what you are about to lose. ### One Edit, Start to Finish A recording of the CAB editor: selecting Add role produces a blank role card, which is filled in as ROLE-004 Program Auditor with a description, a primary goal and a permission row. Review with AI runs a spinner, then the review surface opens showing one your-edit change and fourteen AI suggestions across fifteen cards. Save All applies them and the version badge increments to five. **Notice the count.** One added role produced fourteen further suggestions. Adding a role means deciding what it can reach, which screens mention it, and which stories belong to it, and the review works those out rather than leaving you to find them. That is the review earning its cost; see [Reviewing changes](#reviewing-changes) below. ## Asking the Agent Instead The **BlueGenAI CAB Agent** tab beside **CAB Configuration** takes requests in plain language. Its composer reads `Ask anything about your CAB, or request changes...`. **The agent tab opens completely blank:** no heading, no examples, nothing describing what it can do. It works, but the product does not tell you what to ask it. Requests that work: | Ask for | Example | | --------------------------------- | ------------------------------------------------------------------------------------ | | A new item in a named section | Add a business rule requiring a completed W-9 before an application can be submitted | | A change to something specific | Change the applicant role so it cannot approve its own submission | | A correction across the blueprint | The system is called LEAD, not Lead Grants; fix it wherever it appears | | An answer rather than a change | Which screens does the reviewer role reach? | **One request can change several sections.** A single rule request produced six changes across user stories, the data model, three screens, and the rules section; the agent works out what else the change implies rather than editing only what you named. ## Reviewing Changes Both routes land here. Hand edits go through it when you select **Review with AI**; agent changes go through it automatically. **The review looks at your edits, not only at its own suggestions.** It reads what you changed, checks it against the rest of the blueprint, and can propose corrections to your wording or to anything your change has knock-on effects for. Running it is a second opinion on your work as much as a way of getting the agent to do some. The review surface with seven numbered callouts: the Save All and Discard All buttons that apply or drop everything at once, the AI Review chip marking this as a review pass, the counts showing two of your own edits and eight AI suggestions, the change-type label showing where the change came from, the pager reading one of ten, the WAS and NOW rows holding the current and proposed values, and the Accept and Discard controls for the single change on screen. Each change is labelled by where it came from: | Label | Meaning | | ---------------- | ---------------------------------- | | **YOUR EDIT** | You changed it by hand | | **AI ADDED** | The agent added something new | | **AI SUGGESTED** | The agent changed existing content | Modifications show a **WAS** row and a **NOW** row; additions show what is being added. Agent changes carry a one-line reason, your own do not. Selecting a change scrolls the blueprint to it and outlines it, so you see it in context. **Reviewing with AI is optional and it costs.** You can save hand edits without it, though you then lose the consistency check. When you do run it, the cost is added to the project's generation cost. ## Deciding What to Keep Two boxed views of the review surface with an arrow between them. In the before state the toolbar reads Save All and Discard All and there is no tally beside the pager. In the after state, with one change accepted and one discarded, the buttons read Save and Discard and a tally beside the pager reads one accepted, one discarded and eight still undecided. Accept or discard each change with the controls on its card. Nothing is applied until you use the toolbar. **Undecided changes count as accepted.** Saving keeps everything you accepted *and* everything you never looked at. Only changes you explicitly discarded are dropped. On a review with 20 changes, working through the first five and saving keeps the other 15. **Discard All** drops everything and writes nothing. It does not create a version. ## Version History **Saving creates a version.** Open the clock button to see them. Each entry is a timestamp: no author, no description, no summary. The current version sits at the top, and selecting an older one previews it without restoring. **Restoring deletes every version newer than the one you restore.** This is not an undo stack you can move up and down; going back three versions destroys the two in between, permanently. The confirmation says so, and the confirm button is styled like an ordinary action rather than a destructive one. The Restore this version confirmation, warning that it will replace the current blueprint with the selected version, that all versions created after it will be permanently deleted, and that the action cannot be undone. ## What Is Recorded, and What Is Not This distinction matters if anyone ever asks you who changed what. **While a change is under review, attribution is complete.** Every proposed change is marked as yours or the agent's. Each accept or reject is recorded against a named person with their email address and the time they decided. The agent's suggestions move through a tracked lifecycle from queued to resolved. **Once a change is applied, none of that travels with the blueprint.** The document has no edited marker, no record of who edited it, and no per-section history. Reading a finished blueprint tells you what it says, not which parts a person rewrote. Version history records *when*, not *who*; versions are named by timestamp, and the save operation is not given a user identity. **So the review process is auditable; the finished document is not self-describing.** If your organisation needs a change record, capture it during review rather than expecting to reconstruct it afterwards. ## Working with Other People Only one person can edit a blueprint at a time. The platform holds a lock while a review is running or awaiting a decision, and checks that the version you started from is still current before applying anything. ## Your Next Step A corrected blueprint is what everything downstream is built from. What the conversion produces, and what happens when you run it twice. What the ten sections tell you about your application. ## Related topics - [Using CAB to support Requirement Clarification](/cab/requirement-clarification.md) - [Weekly release notes](/changelog/weekly-release-notes.md) - [Troubleshooting & FAQ](/tips-and-tricks/troubleshooting-faq.md) - [BlueGenAI Documentation](/index.md) - [Quick Start Guide](/getting-started/quick-start-guide.md)