---
name: uipath-genome
description: "UiPath automation genome (`*-genome.md`): always invoke to build, execute or edit a genome file, before any skill it names. Portable markdown blueprint of an automation at process and component level: steps, business rules, handoffs, platform resources, acceptance criteria, and the UiPath skill that builds each part. EXTRACT a genome from a UiPath project or solution (`.xaml`/`.cs`, `.flow`, `.bpmn`, `agent.json`, `Workflow.json`, `caseplan.json`, `.uipx`) or another automation or test framework's export, for documentation or migration to UiPath; AUTHOR one from an idea; EXECUTE one to build the automation. Triggers: 'genome', 'blueprint', 'document this automation/solution/process', 'reverse-engineer what this project does', 'build/implement this genome'. PDD/SDD, SOP or idea to design without a genome→uipath-planner. Build without a genome→that artifact's skill. Legacy activity upgrade→uipath-activity-migrator. Quality review→uipath-review. Finding what to automate→uipath-automation-discovery."
when_to_use: "User points at a *-genome.md file (or one whose first line is `<!-- UIPATH-AUTOMATION-GENOME`) and asks to build, execute, implement, follow or edit it. User says 'genome', 'blueprint', 'document what this automation does', 'extract a spec from this project/solution', 'reverse-engineer this process', 'describe this solution at high and low level', 'propose a workshop or demo scenario to build'."
---

# UiPath Genome — document, author, and execute automation blueprints

Genome: markdown specification an AI agent consumes to rebuild an automation — what it does, business rules, data moving between parts, platform resources, its transactional shape, verification, and which UiPath skill builds each part. Genomes stay thin: build skills carry UiPath know-how; a genome describes *what*, skills know *how*.

> **Read by the mode's read plan (§ Read Plans), never from memory.** This file routes; guides carry the rules, each subject in exactly one guide. A file the plan reads whole is read whole — not grepped or skimmed; a pointer that names a section (`guide.md § Section`) is a section read, that section in full; a guide no condition of the plan has reached stays closed. The two **catalogs** — [selector-translation-guide.md § Tag attribute catalog](references/selector-translation-guide.md) and a framework selectors guide's per-technology tables — are read by section: list headings, then read the sections for the technologies the source recorded; the rules around them are read whole.

## When to Use This Skill

- Existing UiPath project or solution to document, understand, or prepare for migration ("what does this solution do", "extract a genome", "document this process at high and low level")
- Described automation idea needing a specification before building, or a goal (a self-paced workshop, a demo, trying a product) needing a scenario proposed first
- `*-genome.md` file to build from
- Existing genome to update, split into components, or re-extract after source changed

## Mode Detection

Determine mode from input, in this order:

1. **`*-genome.md` path plus build intent** ("build", "execute", "implement", "follow") → **Execute**. Read [execution-guide.md](references/execution-guide.md).
2. **Directory, project file, solution manifest, or another framework's export** (`project.json`, `project.uiproj`, `.uipx`, `.flow`, `.bpmn`, `agent.json`, `Workflow.json`, `caseplan.json`, `uipath.json`; or a folder with none of these holding another automation or test framework's export) → **Extract**. Read [extraction-guide.md](references/extraction-guide.md) and the framework's guides (§ Source Frameworks). A `.bpmn` here is an existing process project to document; a BPMN model handed over as the design to build from is `uipath-planner`'s. A Windows-Legacy UiPath project whose activities are to be upgraded in place is `uipath-activity-migrator`'s; documenting it, or blueprinting it for a rebuild, is an extraction.
3. **Description, idea, SOP, transcript or other process document with no source project, when the user asks for a genome or blueprint; or a goal to propose a scenario for** (a self-paced workshop, a demo, trying a product) → **Author**. Read [authoring-guide.md](references/authoring-guide.md). The same input without a genome or blueprint asked for — designing or building from an SOP, a transcript, a process spec or an idea — is `uipath-planner`'s.
4. **`*-genome.md` path plus edit intent** ("update", "add a step", "split", "remove the inferred flags") → **Edit** in place per the edit tables in the authoring guide (Step 8) and, for an extracted genome, the extraction guide (Step 7); when the source changed or the extraction was cut short, re-extract only the changed or unread objects (extraction guide § Partial Re-extraction).

A PDD or SDD with no genome or blueprint asked for, a request to design a solution and derive tasks, or any input this list assigns to another skill is that skill's job, not a genome. Say so and stop.

## Read Plans

Every turn resends the whole context: a reference read early is paid again on every later turn, and one a later answer rules out is paid for nothing. Each mode reads its guide (§ Mode Detection) and, at each phase, only what this table names for it:

| Mode | Phase | Read |
|---|---|---|
| Extract | start | [genome-format-guide.md](references/genome-format-guide.md) and [skill-mapping-guide.md](references/skill-mapping-guide.md) whole; the template of the level chosen; the Source Map of the extracted example [salesforce-accounts-and-contacts-genome.md](assets/examples/salesforce-accounts-and-contacts-genome.md) to calibrate the step table |
| Author | start | genome-format-guide.md and skill-mapping-guide.md whole; the template of the level chosen; one of [assets/examples/](assets/examples/) to calibrate depth |
| Edit | start | genome-format-guide.md whole |
| Execute | start, before any question | each skill named in Build With / Components, invoked once for preflight discovery and the scaffolding options — its SKILL.md only, its mandatory reads wait for the build; [transactional-execution-guide.md](references/transactional-execution-guide.md) when the Transactional Shape is not the stub, before the split questions |
| Execute | build, once the configuration answers exist | the owning skill's mandatory reads, through its own journey; the migration reads of § Source Frameworks when an export was resolved; [source-migration-guide.md § Verification](references/source-migration-guide.md) when a group builds UI activities, extracted genome or not; [execution-parts-guide.md](references/execution-parts-guide.md) when a group is planned in parts, runs through subagents or forks, or resumes after a pause or a compaction; [offline-definition-workarounds-guide.md](references/offline-definition-workarounds-guide.md) when no application is reachable; a corrected doc's row in [package-doc-errata-guide.md](references/package-doc-errata-guide.md) with that doc, and its § Tools rows for the tools a group builds with; skill-mapping-guide.md only when a Build With row names a retired skill or one the host lacks; a genome-format-guide.md section only where an execution guide points to it |
| Execute | end | [open-items-guide.md](references/open-items-guide.md) when the target environment needs setup |

Each phase's reads go out in at most three turns, never file by file as each file names the next:

1. **Turn 1**, one message: every file the phase reads whole, and the heading list (a search for `^#` lines) of every file it reads by section.
2. **Turn 2**, one message: the sections chosen from those lists, and the owning skill's discovery for the activity kinds in play.
3. **Turn 3**, only what turn 2 routed to.

A plan never narrows an owning skill's contract: a read that skill mandates is performed even when no plan names it, a read that misses (a wrong path) is retried the next turn, and neither is dropped to stay within three turns.

## Source Frameworks

A UiPath source (`.uipx`, `project.json`, `project.uiproj`, `.xaml`/`.cs`, `.flow`, `.bpmn`, `caseplan.json`, `agent.json`, `Workflow.json`, `uipath.json`) is read with [uipath-source-guide.md](references/uipath-source-guide.md) — whole at extraction; at execution only its § UI Target Locators and § Test Data, with [source-migration-guide.md](references/source-migration-guide.md) § Migration preflight step 4, § UI targets and § Verification: its UI targets are carried over, not translated. Every other framework is read through the **framework migration pack**, which holds per framework a **source guide**, a **selectors guide** and an **inventory script**. Resolve it once per run, in both modes:

1. **Ask for its location.** Ask "Where is the framework migration guide?" unless the request, or the execution scaffolding answer ([execution-guide.md § 1.3](references/execution-guide.md)), already gave it. Accept a folder path (`<PACK_DIR>`); a git URL is cloned into a scratch folder first. Never search the disk for it, never work from memory of its contents, never copy its files into this skill or beside a genome.
2. **Select the framework row** in `<PACK_DIR>/README.md` § Frameworks: the row whose detection signals match the given files (Extract), or the framework the Source Map names (Execute). An extracted genome names its framework in the Source Map; that name selects the row and makes the execution a **migration**.
3. **Run, then read.** Run the row's script before reading any export file. Extract reads `<PACK_DIR>/<framework>/source-guide.md` in full and writes the genome and its Source Map. Execute reads [source-migration-guide.md](references/source-migration-guide.md) — whole when the build has UI activities, otherwise only its § Migration preflight, § Rules, § Source steps that are not UI actions, § Result parity, § Test data and § What the executor records — and derives the catalogs with the same script (its § Migration preflight). A build with UI activities also reads the source guide's § Composite actions and `<PACK_DIR>/<framework>/selectors-guide.md` by technology section together with [selector-translation-guide.md](references/selector-translation-guide.md).

No row matches → say which framework the files appear to come from and that the pack has no guide for it; never improvise an extraction. Pack not available → Extract stops (no genome is extracted from a framework nobody has read); Execute continues without the migration part — live capture or placeholders, stated in the report ([source-migration-guide.md § Migration preflight](references/source-migration-guide.md) step 1).

## Critical Rules

Each rule names its subject and the one guide that states it in full; the guide's wording is the rule.

1. **Choose the genome level before writing** — one project is a component genome, two or more (or a coordinator plus what it invokes) a process genome with one component genome per project, and test components are folders of one test project: [genome-format-guide.md § Two Levels](references/genome-format-guide.md).
2. **Read the source, do not ask about it.** Extraction reads every non-generated file and never asks what the automation does, only for resources beside it, which it reads and links: [extraction-guide.md](references/extraction-guide.md) Steps 1 and 3.
3. **Infer complexity, never ask for it**, defaulting lower when ambiguous: [genome-format-guide.md § Complexity](references/genome-format-guide.md).
4. **Replication-grade detail in behavioural wording**, with activity names, variable names, file paths and code syntax banned from the body: [genome-format-guide.md § Workflow](references/genome-format-guide.md) and § Provenance.
5. **Configuration Questions carry the values left open**; a value an extracted source fixes for every environment is written where it acts, not asked: [genome-format-guide.md § Configuration Questions](references/genome-format-guide.md).
6. **Every section present, always**, stub lines for sections that do not apply: [genome-format-guide.md § Stub Lines](references/genome-format-guide.md).
7. **One skill per Build With row, from the mapping guide only**; operate-only skills belong under Platform Dependencies: [skill-mapping-guide.md](references/skill-mapping-guide.md).
8. **Preamble and blueprint blockquote are mandatory and name `uipath-genome` as the skill that builds the genome**, and Build With (or Components) precedes Workflow (or Process Map) so an agent builds instead of executing the steps: [genome-format-guide.md § Two Levels](references/genome-format-guide.md) rule 5.
9. **Acceptance criteria are specific and testable**; "completes successfully" and "handles errors" are banned: [genome-format-guide.md § Acceptance Criteria](references/genome-format-guide.md).
10. **Flag ambiguity, never leave gaps**: best interpretation plus `*[Inferred]*`, uncertainty recorded in the Source Map: [genome-format-guide.md § Ambiguity Marker](references/genome-format-guide.md).
11. **Write immediately, offer edits after**; edits are in place, never a regeneration: [genome-format-guide.md § Write, Then Offer Edits](references/genome-format-guide.md).
12. **Execution never edits the genome and never skips the configuration questions** — the genome's own and the scaffolding questions, once per owning skill with per-project differences, waived only by an explicit "take the defaults" in the current request — then advances group by group without pausing, assesses every acceptance criterion, and ends by writing the open-items files when the target environment needs setup — what the engineer must set up there: [execution-guide.md](references/execution-guide.md) § 1.3, § 2.2, § 3; [open-items-guide.md](references/open-items-guide.md).
13. **Extraction writes genomes only, and the Source Map is the migration contract** — framework, export path and identity, per-step source objects with ids, checkpoints, counts; locators and rows stay in the export: [genome-format-guide.md § Source Map](references/genome-format-guide.md).
14. **Execution on an extracted genome is a migration by default** — catalogs derived from the export at preflight, every UI activity given an `INFERRED (<confidence>)` Object Repository target with the first live run as healing pass, test data filled from the data catalog, one credential asset per account and no secret ever copied: [source-migration-guide.md](references/source-migration-guide.md).
15. **Build through the owning skill, verifiably** — its mandatory reads; for every activity kind the build uses, the default XAML (the shape) and the package's per-activity doc (the property and its value encoding), fetched before the first file using it is written; workflows authored as files, not generated; subagents under the same obligation: [execution-guide.md § 2.2](references/execution-guide.md).
16. **Composite source actions are contracts in the genome and patterns at build** — the substep carries what is typed, how the entry is matched, which key confirms, the path levels, the row rule ([genome-format-guide.md § Workflow](references/genome-format-guide.md)); execution expands each into its pattern with a verify sub-step, never the nearest single activity ([source-migration-guide.md § Composite interactions](references/source-migration-guide.md)).
17. **UiPath selector truth lives in one guide** — tag chain by technology, one tag is one node, node-dependent `aaname`, one application one scope, the tag comes from the strongest evidence (recorded markup over a known node role over the control type), no borrowed identifier, widget anatomy: [selector-translation-guide.md](references/selector-translation-guide.md) rules 1–16. **Verification is a property of the acting activity** (`VerifyOptions` observing the element that shows the outcome): [source-migration-guide.md § Verification](references/source-migration-guide.md).
18. **A migrated target carries a verdict, and `offline-unverified` is one** — `verified` against the target application, `shape-verified` against a comparable instance of the same product, `offline-unverified` when nothing is reachable, per interaction family: [source-migration-guide.md § Verifying targets](references/source-migration-guide.md). A reachable application is a windfall, never a precondition for finishing the run. Offline, definitions are read back per [selector-translation-guide.md § Checking a definition](references/selector-translation-guide.md).
19. **Most source steps are not UI activities** — waits, assertions, stores, labels, jumps, comments, log lines and engine settings become verification, reads, structure, a log message or nothing at all, and linking is the last thing done to a workflow file: [source-migration-guide.md § Source steps that are not UI actions](references/source-migration-guide.md) and § UI targets.
20. **The transactional shape is described in the genome and split at build.** Every genome carries a Transactional Shape — one block per flow (one kind of item handed from its producer to its consumer: components 1 → 2, 2 → 3, an independent 5 → 6; an item's children are levels of its flow, not a flow), each with the unit of work and its alternatives, the as-is roles, store and coordination, the per-item outcomes, the split options for the unit and for each alternative unit — A one process without a queue, B a producer process and a consumer process, C one process with a queue — with what each requires and changes, and the evidence — or its stub; it asserts no split, no store, no template and no unit. Execution asks the split questions per flow (unit, split option, producers, consumers, store, template, shared steps, triggers) with defaults prepared from the genome, may materialise one component as several projects or two components as one, resolves each component across its flows, and records the choice; the behaviour is owed whatever the choice: [genome-format-guide.md § Transactional Shape](references/genome-format-guide.md); [transactional-execution-guide.md](references/transactional-execution-guide.md).
21. **Source values are read from the source, not from their rendering** — comparison literals and case rules verbatim, counts, lengths, occurrences, waits and control-flow flags; an empty rendering is "not shown", never "not set". Extraction writes them so ([extraction-guide.md](references/extraction-guide.md) Step 3); execution checks every one the genome cites before a group builds on it and follows the source where they disagree ([source-migration-guide.md § Migration preflight](references/source-migration-guide.md) step 4). A scripting wrapper's verbs are the caller's UI steps on the elements its identities name, never a library of verbs.
22. **A suspected source defect is verified before it is written: first in the full rendering, then in the framework's source itself.** The inventory output is the pack's rendering, not the source. Each finding is read in the export with a generic reader that keeps every key, and is classified as a rendering artefact (reported for the pack), a source defect, a source rule, or unresolved platform semantics. It is then written in that form, with its evidence in the Source Map ([extraction-guide.md](references/extraction-guide.md) Step 4b; marker: [genome-format-guide.md § Source Defects](references/genome-format-guide.md)).

## Workflows

### Extract (project or solution → genome)

Detect framework and deployment unit → ask for related resources → inventory → size the source and state the plan (in parts above one part's budget, reconciled by the parent) → extract signals with the source guide's tables → build call and handoff graphs → verify every suspected source defect in the full rendering and in the framework's source → infer complexity → map signals to sections (process genome first, then components; the Transactional Shape from the source's per-item constructs) → complete the Source Map as the migration contract, a step table per component → write, check with `scripts/check-genome.py` against the source export and fix → offer edits. Full procedure: [extraction-guide.md](references/extraction-guide.md); framework guides and scripts: § Source Frameworks.

### Author (description → genome)

Receive (a goal: one question round, up to three proposed scenarios, the pick becomes the description) → choose level → infer complexity → extract → suggest platform capabilities and describe the transactional shape (as-is, split options per unit of work, evidence) → bounded follow-ups (simple 0-1, medium 1-2, complex 2-3 rounds, none after a picked scenario, all questions of a round in one message) → generate → write → check with `scripts/check-genome.py` and fix → offer edits. Full procedure: [authoring-guide.md](references/authoring-guide.md).

### Execute (genome → automation)

Parse and validate the genome → preflight discovery → ask every configuration question (genome, then the split questions per flow, then scaffolding per owning skill) → resolve one project or one solution (libraries pack first; each consumer project on the REFramework template when chosen; a split may materialise one component as several projects) → plan skill groups → build each group through the owning skill → on an extracted genome, migrate UI targets and test data from the export → wire handoffs → assess every acceptance criterion → report → write the open-items files when the target environment needs setup: its setup steps for the engineer (one per project, plus one for the solution that orders and links them). Full procedure: [execution-guide.md](references/execution-guide.md); split and REFramework: [transactional-execution-guide.md](references/transactional-execution-guide.md); parts: [execution-parts-guide.md](references/execution-parts-guide.md); target and data migration: [source-migration-guide.md](references/source-migration-guide.md); setup for the engineer: [open-items-guide.md](references/open-items-guide.md).

## Task Navigation

| I need to… | Mode | Read |
|---|---|---|
| Write any genome — sections, levels, stubs, wording, Source Map rows | All | [genome-format-guide.md](references/genome-format-guide.md); templates [component](assets/templates/component-genome-template.md) / [process](assets/templates/process-genome-template.md); depth calibration [assets/examples/](assets/examples/) |
| Fill Build With / Components, or plan execution groups | All | [skill-mapping-guide.md](references/skill-mapping-guide.md) |
| Describe the transactional shape: its flows (chains, independent flows — and nested levels that are not flows), per flow the unit of work and its alternatives, the as-is (produced by, consumed by, item store, coordination, item kinds, step groups), the per-item outcomes, the split options per unit of work, and the evidence — no verdict | Extract / Author | [genome-format-guide.md § Transactional Shape](references/genome-format-guide.md); [authoring-guide.md](references/authoring-guide.md) Steps 4–5; [extraction-guide.md](references/extraction-guide.md) Step 3; UiPath sources: [uipath-source-guide.md § Signals — XAML › REFramework projects](references/uipath-source-guide.md) |
| Ask the split questions (unit, split option, producers, consumers, store, template, shared steps, triggers) with defaults prepared from the genome; materialise the projects; place steps on the REFramework surfaces; verify the four exits | Execute | [transactional-execution-guide.md](references/transactional-execution-guide.md) |
| Extract from a project, solution or export | Extract | [extraction-guide.md](references/extraction-guide.md) + framework's source guide (§ Source Frameworks) |
| Size a large source, extract it in parts — shared decisions, brief, ledgers, return contract, parts as forks of the parent — and reconcile the parts | Extract | [extraction-guide.md](references/extraction-guide.md) Step 2b, § Extraction in Parts |
| Finish a cut-short extraction, or bring a genome in line with a changed source | Edit | [extraction-guide.md § Partial Re-extraction](references/extraction-guide.md) |
| Word a composite UI step (type-ahead, menu path, option list, table row, keystrokes) | Extract / Author | [genome-format-guide.md § Workflow](references/genome-format-guide.md); source guide § Composite actions for the framework's actions |
| Record checkpoints, screenshots and result logs from a test suite | Extract | [extraction-guide.md](references/extraction-guide.md) Step 3 evidence policy; source guide § Evidence |
| Decide whether a suspected defect is the source's or the rendering's; mark it | Extract / Edit | [extraction-guide.md](references/extraction-guide.md) Step 4b; [genome-format-guide.md § Source Defects](references/genome-format-guide.md) |
| Author from a description; edit a genome | Author / Edit | [authoring-guide.md](references/authoring-guide.md); extracted-genome edits: [extraction-guide.md](references/extraction-guide.md) Step 7 |
| Execute: questions, projects, groups, acceptance, report | Execute | [execution-guide.md](references/execution-guide.md) |
| List what the engineer must set up in the target environment — packages, folder, queues, assets, credentials, triggers, machine prerequisites — one open-items file per project plus the solution's | Execute | [open-items-guide.md](references/open-items-guide.md) |
| Build a large group in parts — ledger, brief and rulings, read plans, progress, the part report; pause and resume after a compaction, with or without subagents; fork a part to author disjoint files — when, what the owner alone does, review | Execute | [execution-parts-guide.md](references/execution-parts-guide.md) |
| Derive catalogs from the export; write the target spec; map steps to source objects | Execute | [source-migration-guide.md § Migration preflight](references/source-migration-guide.md) |
| Build Object Repository targets from a catalog — how many elements, which screens, helpers | Execute | [source-migration-guide.md § Object Repository identity](references/source-migration-guide.md) |
| Build a type-ahead pick, option list, date, menu path, table row or keystroke step | Execute | [source-migration-guide.md § Composite interactions](references/source-migration-guide.md) |
| Decide what a wait, assertion, store, label, jump, comment, log line or engine setting becomes | Execute | [source-migration-guide.md § Source steps that are not UI actions](references/source-migration-guide.md) |
| Register and link targets with one tool per run; order the build — when to link, why a rewritten file loses its links, why a link "succeeded" and did not | Execute | [source-migration-guide.md § UI targets](references/source-migration-guide.md) |
| Decide where a verification goes (`VerifyOptions` vs Check activity) | Execute | [source-migration-guide.md § Verification](references/source-migration-guide.md) |
| Translate a recorded locator into a UiPath selector; decide tag, attributes, caption path (`<nav>`), scope, confidence | Execute | [selector-translation-guide.md](references/selector-translation-guide.md) rules (in full) + its § Tag attribute catalog and the framework selectors guide (by technology section) |
| Verify migrated targets — against the target application, against a comparable instance, or read them back offline | Execute | [source-migration-guide.md § Verifying targets](references/source-migration-guide.md); [selector-translation-guide.md § Checking a definition](references/selector-translation-guide.md) |
| Author a definition with no reachable application | Execute | [offline-definition-workarounds-guide.md](references/offline-definition-workarounds-guide.md) |
| Fill test data files from source rows; credentials | Execute | [source-migration-guide.md § Test data](references/source-migration-guide.md), rules 3–5 |
| Make a migrated test run comparable with the source's | Execute | [source-migration-guide.md § Result parity](references/source-migration-guide.md) |

## Anti-patterns

Each is prohibited in full where its subject lives; this list only routes.

1. **Asking the user what the project does or which complexity it is**; previewing before writing; code, file paths or activity names in the body; Integration Service treated as an application; compressed steps or disconnected rules and handlers — [genome-format-guide.md](references/genome-format-guide.md) and [extraction-guide.md § Anti-patterns](references/extraction-guide.md).
2. **Producing a genome when the user brought a PDD/SDD, SOP, transcript or idea without asking for a genome or blueprint, or asked for a solution design.** That is `uipath-planner`; an in-place activity upgrade of a Legacy project is `uipath-activity-migrator` (§ Mode Detection).
3. **Retired skill names in Build With** (`uipath-rpa-workflows`, `uipath-coded-workflows`, `uipath-coded-agents`); a stale name will not resolve at execution — [skill-mapping-guide.md](references/skill-mapping-guide.md) rule 5.
4. **A process genome without Handoffs, or a component Interface that disagrees with Handoffs** — [genome-format-guide.md § Handoffs](references/genome-format-guide.md).
5. **Building before configuration answers exist, stopping between execution groups, or generating workflows by script** — [execution-guide.md § Anti-patterns](references/execution-guide.md).
6. **A Source Map without the export's location or per-step source objects, or catalogs copied beside the genome** — [genome-format-guide.md § Source Map](references/genome-format-guide.md).
7. **Placeholder targets, generated rows, copied passwords, naive composite translation, per-step Object Repository entries, Check activities instead of `VerifyOptions`, targets reported done with no verdict, a linked workflow rewritten wholesale instead of edited** — [source-migration-guide.md § Anti-patterns](references/source-migration-guide.md).
8. **Merged widget nodes, invented identifiers, `DIV` as a default tag, per-screen scopes, assumed grid markup** — [selector-translation-guide.md](references/selector-translation-guide.md) rules 8, 9, 13, 14.
9. **A split, a store or a verdict asserted in the genome; a producer folded into the consumer's initialisation outside option C, or under C without a once-guard; a source's coordination queues carried by habit; a state machine around a linear flow; framework plumbing transcribed as steps; or a split question skipped** — [genome-format-guide.md § Transactional Shape](references/genome-format-guide.md); [transactional-execution-guide.md § Anti-patterns](references/transactional-execution-guide.md); [extraction-guide.md § Anti-patterns](references/extraction-guide.md) 12–13.
10. **A source defect written from a rendering, or a rendering artefact written as a source defect** — [extraction-guide.md](references/extraction-guide.md) Step 4b and § Anti-patterns 16.