abi. Clone Guide

The four ways things get onto the map

You can use one or all four. Each stamps where it came from, so every node on the map can be traced back to a source.

• By hand. Add a department, role, system, process, external party or AI agent yourself. Free, unlimited, no AI involved
• Interviews. Send someone a private link to a conversation with the intake agent, by text or by voice. It follows the workarounds rather than a questionnaire
• Documents. Upload SOPs, playbooks and checklists. Uploading is free; reading one into the map is a model call, so it is part of Pro and Max. Delete removes a document and the text read from it for good; what it already added to the map stays
• abi. Capture. An extension that records which systems somebody moves between while they work. See the Capture guide

Map, List, Intake and Docs

• Map is the 3D model. Layers show and hide people, processes, systems and external parties; filters highlight without hiding. Names can be switched off entirely
• Search, at the top of the map (or press /): type a person, process or system and the map isolates it with everything it connects to, as Present does. Escape clears it
• Ask abi.: open abi. at the top of the page and type a question about the map, such as who signs off invoices. She answers from the map alone and says what it does not hold yet. A question uses 5 credits
• List is the same data as a table, with the same curation actions, for when you want to work through it rather than look at it
• Intake is where interviews, documents and capture codes live, plus the Evidence list showing what each source actually contributed
• Docs is the Operations Manual abi. writes from the map. See below

Documentation: the Operations Manual

On the Docs view, abi. writes the business down from its map: every process step by step, who does each step and in which system, how long it takes and what comes back; a page per role, which is the handover pack when someone moves on; the systems and AI agents; and a business continuity section naming the work only one person has described and the systems most of the work runs on. Whatever the map does not hold yet is listed at the end as what to go and get.

• Every fact and figure is counted from the map. abi. writes only the paragraphs, from the same facts, and never sees anyone's name
• Each version is kept. When the map changes, the Docs view says so and offers a new version
• Download it as a PDF, a Word file or Markdown. Untick People's names for a copy that leaves the business, such as one for a buyer's adviser or an auditor: names become role titles, everywhere
• Writing a version costs 25 credits and abi. asks first. If she cannot reach the writer, she writes the paragraphs plainly and nothing is charged. Part of abi. Pro and abi. Max
• Tick Keep it up to date monthly and abi. writes a new version on her own each month the map has changed, at the same price. A month in which nothing changed costs nothing
• Put a copy in Google Drive connects a Drive to the map: abi. makes one folder there and puts every new version in it as a Google Doc, so the manual belongs to the business even without the app. She can see only that folder and the documents she made
• On a client's map, the manual carries your export brand (logo, colour, name and footer, set once in Settings)
• Not sure what you will get? On a map with no manual yet, See an example opens the one abi. wrote for the sample map

Confirm, flag, broken

Anything the AI inferred is marked as inferred until a person says otherwise. Every node can be confirmed, flagged for a second look, or marked broken.

• Unaccounted software is the filter worth running first: systems somebody mentioned that are not in your official inventory
• A flagged node stays on the map. Flagging records a disagreement rather than deleting a fact
• Where two sources disagree, both are kept and the conflict is shown

Your own map, client maps and proposals

A free consultant account gets its own business map plus five client maps, as lifetime slots.

• A slot is spent when a map is created, permanently. Archiving or deleting a client map does not free one, so there is no need to tidy up
• Your own business map does not count against the five
• A proposal map is built from assumptions rather than interviews, and says so on every screen: every node is a question to confirm in discovery
• Once a client map holds real work its identity is locked, so a map cannot quietly become a different client's

Sharing what you have built

• Present hides the chrome and orbits the map, department by department
• A share link gives a read-only view. Names can be hidden on it, which is the usual choice for a client's own map
• Proposal turns ranked quick wins into a priced case for change, each line traceable to who said it