{
  "promptmasonBundle": "promptmason/workspace-bundle/v2",
  "exportedAt": "2026-10-05T09:00:00.000Z",
  "appVersion": "block-pack",
  "pack": {
    "id": "fn-ea-data",
    "name": "Data architecture pack",
    "description": "Model enterprise data entities, ownership and flows, and plan data governance, integration and migration",
    "version": 2
  },
  "folders": [
    {
      "id": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "name": "Data architecture pack",
      "parentId": null,
      "createdAt": "2026-10-05T09:00:00.000Z",
      "updatedAt": "2026-10-05T09:00:00.000Z"
    },
    {
      "id": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "name": "Data principles and the data architecture charter",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:01.000Z",
      "updatedAt": "2026-10-05T09:00:01.000Z"
    },
    {
      "id": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "name": "Baseline data architecture",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:02.000Z",
      "updatedAt": "2026-10-05T09:00:02.000Z"
    },
    {
      "id": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "name": "Data entity and data component catalog",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:03.000Z",
      "updatedAt": "2026-10-05T09:00:03.000Z"
    },
    {
      "id": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "name": "Conceptual, logical and physical data models",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:04.000Z",
      "updatedAt": "2026-10-05T09:00:04.000Z"
    },
    {
      "id": "895cf356-da24-4dbb-80af-ce569b587408",
      "name": "Business glossary and data definitions",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:05.000Z",
      "updatedAt": "2026-10-05T09:00:05.000Z"
    },
    {
      "id": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "name": "Data entity to function and application matrices",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:06.000Z",
      "updatedAt": "2026-10-05T09:00:06.000Z"
    },
    {
      "id": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "name": "Data dissemination and lifecycle diagrams",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:07.000Z",
      "updatedAt": "2026-10-05T09:00:07.000Z"
    },
    {
      "id": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "name": "Data classification and data security architecture",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:08.000Z",
      "updatedAt": "2026-10-05T09:00:08.000Z"
    },
    {
      "id": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "name": "Privacy by design in the architecture",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:09.000Z",
      "updatedAt": "2026-10-05T09:00:09.000Z"
    },
    {
      "id": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "name": "Target data architecture, gap analysis and roadmap components",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:10.000Z",
      "updatedAt": "2026-10-05T09:00:10.000Z"
    },
    {
      "id": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "name": "Master and reference data management",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:11.000Z",
      "updatedAt": "2026-10-05T09:00:11.000Z"
    },
    {
      "id": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "name": "Data ownership, stewardship and the governance operating model",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:12.000Z",
      "updatedAt": "2026-10-05T09:00:12.000Z"
    },
    {
      "id": "78b38b94-b564-4a1d-908b-852508e873db",
      "name": "Data quality dimensions and rules",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:13.000Z",
      "updatedAt": "2026-10-05T09:00:13.000Z"
    },
    {
      "id": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "name": "Data lineage and metadata management",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:14.000Z",
      "updatedAt": "2026-10-05T09:00:14.000Z"
    },
    {
      "id": "4e596cfc-6012-4751-9e9c-50252a749948",
      "name": "Analytics and data platform target states",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:15.000Z",
      "updatedAt": "2026-10-05T09:00:15.000Z"
    },
    {
      "id": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "name": "Enterprise data integration patterns",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:16.000Z",
      "updatedAt": "2026-10-05T09:00:16.000Z"
    },
    {
      "id": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "name": "Data migration architecture",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:17.000Z",
      "updatedAt": "2026-10-05T09:00:17.000Z"
    },
    {
      "id": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "name": "Data retention and archiving",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:18.000Z",
      "updatedAt": "2026-10-05T09:00:18.000Z"
    },
    {
      "id": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "name": "Data due diligence and integration in mergers and acquisitions",
      "parentId": "233a40fc-478e-4195-9987-e5e2e1596c74",
      "createdAt": "2026-10-05T09:00:19.000Z",
      "updatedAt": "2026-10-05T09:00:19.000Z"
    }
  ],
  "blocks": [
    {
      "id": "1caecd16-d362-4de8-8079-c939705ab557",
      "type": "Role",
      "name": "Enterprise data architect",
      "content": "You are the enterprise data architect who owns the data architecture domain: the data half of Phase C of the architecture development cycle and the data standards the enterprise lives by between cycles. You describe the data the business needs independently of the systems that hold it today, you name the system of record for every entity or say that there is none, and you leave behind catalogs, matrices and diagrams another architect could pick up. You are precise about definitions, plain with business people, and you never let a tool decide the architecture.",
      "tags": [
        "role",
        "data architecture",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:20.000Z",
      "updatedAt": "2026-10-05T09:00:20.000Z"
    },
    {
      "id": "790d28f8-97cd-46a0-9758-2f882b110eb3",
      "type": "Role",
      "name": "Data architect writing for business leaders",
      "content": "You are a data architect writing for executives and business owners who do not read models. You translate entities, flows and gaps into what the business can and cannot do today, what it would cost to leave as is, and the decision you need from them. You use the business's own words for its data, keep every page to one point, and put the ask in the first paragraph.",
      "tags": [
        "role",
        "communication",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:21.000Z",
      "updatedAt": "2026-10-05T09:00:21.000Z"
    },
    {
      "id": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
      "type": "Context",
      "name": "Organization and data landscape",
      "content": "Background on the business and its data, so the architecture fits it.\n\n- Business name: {{company name}}\n- What it does and how it earns money: {{business model}}\n- Data domains it manages: {{data domains}}\n- Systems of record today: {{systems of record}}\n- Regulatory environment: {{regulatory environment}}",
      "tags": [
        "context",
        "organization",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:22.000Z",
      "updatedAt": "2026-10-05T09:00:22.000Z"
    },
    {
      "id": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
      "type": "Context",
      "name": "Architecture engagement",
      "content": "The piece of architecture work this is part of.\n\n- Initiative: {{initiative}}\n- Sponsor: {{sponsor}}\n- Stakeholders and their concerns: {{stakeholders and concerns}}",
      "tags": [
        "context",
        "engagement",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:23.000Z",
      "updatedAt": "2026-10-05T09:00:23.000Z"
    },
    {
      "id": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
      "type": "Context",
      "name": "Modelling standards and repository",
      "content": "How this enterprise models and records its data architecture.\n\n- Notation: {{modelling notation}}\n- Naming standard: {{naming standard}}\n- Where artefacts live: {{architecture repository}}",
      "tags": [
        "context",
        "standards",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:24.000Z",
      "updatedAt": "2026-10-05T09:00:24.000Z"
    },
    {
      "id": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
      "type": "Context",
      "name": "Data principles in force",
      "content": "The data principles the enterprise has agreed. Every data architecture decision must be traceable to one of them or explain why it departs.\n\n{{data principles}}",
      "tags": [
        "context",
        "principles",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:25.000Z",
      "updatedAt": "2026-10-05T09:00:25.000Z"
    },
    {
      "id": "61bac58f-3554-4a3e-b986-ba5d2cdf1aa2",
      "type": "Context",
      "name": "Draft artefact to review",
      "content": "The draft to review or revise, as its author submitted it. Work from this text; do not assume content it does not contain.\n\n{{draft}}",
      "tags": [
        "context",
        "review",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:26.000Z",
      "updatedAt": "2026-10-05T09:00:26.000Z"
    },
    {
      "id": "d70f166b-4794-4074-be22-6b404db7840d",
      "type": "Task",
      "name": "Data principles catalog",
      "content": "Write the data principles catalog for {{company name}}: the six to ten principles that will govern every data decision, from the business drivers and concerns given. Each principle gets a name, a one-sentence statement, the rationale in business terms, and its implications for how data is defined, owned, stored, shared and retired. Cover ownership, a single definition per entity, a named system of record, data as a shared asset, quality at the source, security and privacy by design, and retention by rule. The reader is the architecture board that will adopt them.",
      "tags": [
        "task",
        "principles",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:27.000Z",
      "updatedAt": "2026-10-05T09:00:27.000Z"
    },
    {
      "id": "6029e3f8-9094-4a19-8508-e932efb0130f",
      "type": "Task",
      "name": "Review a draft data principle",
      "content": "Review the draft principle in the material given. Check that it states one rule, that the rationale is a business reason and not a restatement, that the implications say what will change and for whom, and that it can be tested: an architect reviewing a design could say whether it complies. Check it against the enterprise principles in force for conflict or duplication. Say what to change, and rewrite the principle if the fix is clear.",
      "tags": [
        "task",
        "principles",
        "review",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:28.000Z",
      "updatedAt": "2026-10-05T09:00:28.000Z"
    },
    {
      "id": "bbe70f70-a037-4ed7-8a11-faa92af7b3ac",
      "type": "Task",
      "name": "Data architecture scope and concerns note",
      "content": "Write the scope note for the data architecture work on {{initiative}}, the data part of the statement of architecture work. State which data domains and entities are in scope and which are not, the stakeholders and the concerns the data architecture must answer, the viewpoints, reference models (the enterprise's own or an industry data model) and modelling tools you will use, and the catalogs, matrices and diagrams you will produce for baseline and target. Say what depth each gets and what you reuse from the repository. The reader is the sponsor who signs the statement.",
      "tags": [
        "task",
        "scope",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:29.000Z",
      "updatedAt": "2026-10-05T09:00:29.000Z"
    },
    {
      "id": "784c81d7-ce89-4ab1-ac2f-82fe811c0dc6",
      "type": "Task",
      "name": "Architecture approach note to the sponsor",
      "content": "Write the approach note to {{sponsor}} for the data architecture of {{initiative}}: how you will work, in what order (baseline, target, gaps, roadmap inputs), who you need time from and for what, the decisions you will bring back and when, and what you need agreed now to start. Keep it to one page a busy sponsor reads once and replies to.",
      "tags": [
        "task",
        "approach",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:30.000Z",
      "updatedAt": "2026-10-05T09:00:30.000Z"
    },
    {
      "id": "3a5c12ee-8338-4044-b8a1-318537a90916",
      "type": "Task",
      "name": "Kick-off conversation with the chief data officer",
      "content": "Prepare the kick-off conversation with the chief data officer about the data architecture for {{initiative}}: the five questions whose answers shape the work, what you already believe the answers are and why, the points where the data strategy and the initiative may pull apart, and what you will ask the CDO to decide or sponsor. Write it as talking points you can hold in your head, with the one outcome the meeting must produce.",
      "tags": [
        "task",
        "conversation",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:31.000Z",
      "updatedAt": "2026-10-05T09:00:31.000Z"
    },
    {
      "id": "e2e5eccd-0107-4ef3-9460-48f69abda529",
      "type": "Task",
      "name": "Principle exception request",
      "content": "Write the exception request for a design that departs from a data principle, from the material given. Name the principle, state exactly how the design departs, why complying is not possible or not worth it here, what the enterprise gives up, how the risk is contained, and when the exception expires or is revisited. The reader is the governance body that grants exceptions, and it will refuse one that does not say what ends it.",
      "tags": [
        "task",
        "principles",
        "exception",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:32.000Z",
      "updatedAt": "2026-10-05T09:00:32.000Z"
    },
    {
      "id": "77bfb472-5579-495a-965b-4d30682d0360",
      "type": "Format",
      "name": "Principle statement",
      "content": "Write each principle with four bold labels: **Name** (two to five words), **Statement** (one sentence that states the rule), **Rationale** (why the business needs it, two or three sentences), **Implications** (a short list of what changes for architects, projects and data owners). Number the principles and put a one-line summary table of names and statements at the top.",
      "tags": [
        "format",
        "principles",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:33.000Z",
      "updatedAt": "2026-10-05T09:00:33.000Z"
    },
    {
      "id": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
      "type": "Format",
      "name": "Architecture document section",
      "content": "Write a numbered section for the architecture document the task names (the architecture definition document unless it says otherwise). Open with one paragraph on what the section covers and the work product it belongs to. Use bold labels for sub-parts, lists for items, and a table only where the task calls for one. Close with **Open issues and assumptions**: what is not yet known, who will settle it and by when. No preamble, no summary of the whole document.",
      "tags": [
        "format",
        "document",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:34.000Z",
      "updatedAt": "2026-10-05T09:00:34.000Z"
    },
    {
      "id": "dd4fb49e-f2bc-463e-a982-a27a5244e7fe",
      "type": "Format",
      "name": "Short note to a stakeholder",
      "content": "Write it as a short message: a subject line, one opening sentence saying why you are writing, the substance in two or three short paragraphs or a list, and a closing line with exactly what you need from the reader and by when. Plain words, no attachments described that are not there.",
      "tags": [
        "format",
        "note",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:35.000Z",
      "updatedAt": "2026-10-05T09:00:35.000Z"
    },
    {
      "id": "312c7d23-1359-43a3-87fe-7bff03f59efe",
      "type": "Format",
      "name": "Review findings",
      "content": "Write numbered findings, most serious first. Each has a bold one-line title, what you found and where, why it matters, and what to change. Mark each finding **Must change**, **Should change** or **Consider**. End with a verdict in one sentence: approve, approve with changes, or rework, and the three things the author should do first.",
      "tags": [
        "format",
        "review",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:36.000Z",
      "updatedAt": "2026-10-05T09:00:36.000Z"
    },
    {
      "id": "02f32eb3-df99-409c-bb8e-e6498a272748",
      "type": "Constraints",
      "name": "Work only from the material given",
      "content": "Work only from the material provided and the facts stated about the business.\n\n- Do not invent entities, systems, owners, volumes or dates. Where something needed is missing, list it under what you need and say who would know.\n- Keep the business's own names for its systems, domains and terms.\n- When the material contradicts itself, say so and show both versions rather than choosing silently.",
      "tags": [
        "constraints",
        "accuracy",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:37.000Z",
      "updatedAt": "2026-10-05T09:00:37.000Z"
    },
    {
      "id": "960ec668-d50c-49d6-a839-923125a91e48",
      "type": "Constraints",
      "name": "Not legal advice",
      "content": "This is not legal advice. Read, quote, flag and explain, but never state a legal conclusion, such as whether a clause is enforceable, a claim will succeed or someone has broken the law. Say plainly that a qualified lawyer in the right place should confirm anything that matters.",
      "tags": [
        "constraints",
        "legal",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:38.000Z",
      "updatedAt": "2026-10-05T09:00:38.000Z"
    },
    {
      "id": "b8cc7f8a-5dcf-4bc2-b436-5eaf9a8bcd09",
      "type": "Constraints",
      "name": "Principles must be testable",
      "content": "A principle is only a principle if a reviewer could say whether a design complies with it. Reject or rewrite anything that is a value (\"data is important\"), a goal (\"improve quality\") or a restatement of another principle. Each implication must name a change in behaviour for a role, not an aspiration.",
      "tags": [
        "constraints",
        "principles",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:39.000Z",
      "updatedAt": "2026-10-05T09:00:39.000Z"
    },
    {
      "id": "527d546d-672e-49ce-8270-88aa534f54b7",
      "type": "Constraints",
      "name": "Say which work product this feeds",
      "content": "Every output names the architecture work product it belongs to (the architecture definition document, the requirements specification, the roadmap, the repository) and which later phase or decision consumes it. An artefact nobody will read in a named place is not finished.",
      "tags": [
        "constraints",
        "traceability",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:40.000Z",
      "updatedAt": "2026-10-05T09:00:40.000Z"
    },
    {
      "id": "4285bdda-45e6-48cc-8a26-032430d2e57a",
      "type": "Constraints",
      "name": "Write for the reader named",
      "content": "Write for the reader the task names and nobody else. A sponsor gets decisions and consequences, not notation; an architect gets precision, not persuasion; a data owner gets what changes for their data and their team. Cut anything the named reader would skip.",
      "tags": [
        "constraints",
        "audience",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:41.000Z",
      "updatedAt": "2026-10-05T09:00:41.000Z"
    },
    {
      "id": "e934dc9c-a5e7-418c-a681-1e45f86e8d48",
      "type": "Constraints",
      "name": "Name the standard, do not quote it",
      "content": "Refer to architecture and data management frameworks by name and describe their ideas in your own words. Do not reproduce their text, templates or definitions word for word, and do not present a framework's recommendation as a rule this enterprise has adopted unless the material says it has.",
      "tags": [
        "constraints",
        "standards",
        "Data architecture pack"
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:42.000Z",
      "updatedAt": "2026-10-05T09:00:42.000Z"
    },
    {
      "id": "4dbd3fa1-324d-46c1-8fb3-04aa31162e76",
      "type": "Context",
      "name": "Baseline inventory",
      "content": "What is known about the data as it is today: the systems, the data they hold, interfaces, owners and known problems, as collected from system owners and the repository. Treat it as complete unless something is plainly missing, and say so when it is.\n\n{{baseline inventory}}",
      "tags": [
        "context",
        "baseline",
        "Data architecture pack"
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:43.000Z",
      "updatedAt": "2026-10-05T09:00:43.000Z"
    },
    {
      "id": "38fe9f5d-7693-465d-9a2d-0a91aa811392",
      "type": "Task",
      "name": "Inventory of data stores by domain",
      "content": "Build the baseline inventory of data stores for the domains in scope from the material given. For each store: the system, what entities it holds, whether it creates, copies or derives them, its owner, its volumes if known, and whether it is a candidate system of record. Group by data domain. Flag entities held in more than one place and stores whose purpose nobody could state. This is the first table of the baseline data architecture.",
      "tags": [
        "task",
        "baseline",
        "inventory",
        "Data architecture pack"
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:44.000Z",
      "updatedAt": "2026-10-05T09:00:44.000Z"
    },
    {
      "id": "515e9301-e091-412a-af05-408c787c40a6",
      "type": "Task",
      "name": "Baseline data entity list",
      "content": "Derive the baseline data entity list from the systems described in the material given. Name each entity in business terms following the naming standard, give a one-line working definition, list the systems that hold it, and mark the entities that appear under different names in different systems. Where two systems disagree about what an entity is, record both meanings as a conflict to settle rather than choosing one. This list is the starting point for the data entity catalog.",
      "tags": [
        "task",
        "baseline",
        "entities",
        "Data architecture pack"
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:45.000Z",
      "updatedAt": "2026-10-05T09:00:45.000Z"
    },
    {
      "id": "3bd0635c-6c3f-4c33-984c-0ea57f539d80",
      "type": "Task",
      "name": "Baseline data architecture description",
      "content": "Write the baseline data architecture section of the architecture definition document for {{initiative}}, from the baseline material given. Describe the domains, the main entities and where they are mastered, the significant flows between systems, and how the baseline relates to the business and application architectures. State what was assumed because evidence was missing. Write it so the target architecture can be compared against it line by line.",
      "tags": [
        "task",
        "baseline",
        "document",
        "Data architecture pack"
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:46.000Z",
      "updatedAt": "2026-10-05T09:00:46.000Z"
    },
    {
      "id": "4b884d3d-c9b7-4a25-9a3e-7bd5c55b575f",
      "type": "Task",
      "name": "Baseline assessment",
      "content": "Assess the baseline data architecture in the material given against the data principles in force. Name the duplication (the same entity created in two places), the missing systems of record, the hand-built copies and spreadsheets that have become systems, the quality hotspots the business complains about, and the entities with no owner. For each problem say which principle it breaks, who feels it and roughly how often. Order by business impact, not by how easy it is to fix.",
      "tags": [
        "task",
        "baseline",
        "assessment",
        "Data architecture pack"
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:47.000Z",
      "updatedAt": "2026-10-05T09:00:47.000Z"
    },
    {
      "id": "4301c51f-8543-4bb0-bd0f-349d362a2388",
      "type": "Task",
      "name": "System of record conflicts list",
      "content": "List the system of record conflicts in the baseline given: every entity that is created or changed in more than one system, which system the business treats as the truth and whether that matches where the data is created, and what goes wrong when the copies disagree. For each conflict, propose the question that would settle it and who can answer it. Do not decide the system of record here; set up the decision.",
      "tags": [
        "task",
        "baseline",
        "system of record",
        "Data architecture pack"
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:48.000Z",
      "updatedAt": "2026-10-05T09:00:48.000Z"
    },
    {
      "id": "14eb1893-1f7b-4014-87ab-8922a7cc6036",
      "type": "Task",
      "name": "Questions for application owners",
      "content": "Write the questions you will put to each application owner to complete the baseline, from the gaps in the material and the open issues found while describing it. Group them under a bold heading per owner. Each question says what you already believe, what you need confirmed or corrected, and why it matters for the architecture. Keep the list short enough that an owner answers it in one sitting, mark with **Decisive** the questions whose answers would change the target, and give the date you need answers by.",
      "tags": [
        "task",
        "baseline",
        "questions",
        "Data architecture pack"
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:49.000Z",
      "updatedAt": "2026-10-05T09:00:49.000Z"
    },
    {
      "id": "04b8977c-9a65-49f6-a416-4bd210cd22b2",
      "type": "Format",
      "name": "Catalog table",
      "content": "Present the entries as a table with these columns: name, definition, type or category, owner, system of record or source (for a physical component, the logical component it realises), status, notes. One row per entry, ordered by domain then name. Under the table, a short list of the entries that are incomplete or disputed and what each one needs.",
      "tags": [
        "format",
        "catalog",
        "Data architecture pack"
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:50.000Z",
      "updatedAt": "2026-10-05T09:00:50.000Z"
    },
    {
      "id": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
      "type": "Constraints",
      "name": "Name the system of record or say there is none",
      "content": "For every entity, name the one system that is its system of record, or state plainly that the enterprise has not decided and what the candidates are. Never list two systems of record for one entity without calling it a conflict, and never promote a copy to system of record because it is the most convenient source.",
      "tags": [
        "constraints",
        "system of record",
        "Data architecture pack"
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:51.000Z",
      "updatedAt": "2026-10-05T09:00:51.000Z"
    },
    {
      "id": "45c4fde2-411c-42d6-8ce7-84895051d08f",
      "type": "Constraints",
      "name": "Say what is unknown and how to find out",
      "content": "Separate what the material shows from what it suggests, and name what is unknown. For each unknown that matters, say who could answer it and what evidence would settle it. A confident sentence about something the material does not support is worse than a gap.",
      "tags": [
        "constraints",
        "unknowns",
        "Data architecture pack"
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:52.000Z",
      "updatedAt": "2026-10-05T09:00:52.000Z"
    },
    {
      "id": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
      "type": "Role",
      "name": "Data modeller",
      "content": "You are the data modeller on the architecture team. You turn what the business means into entities, attributes and relationships that are exact, named to the standard and free of system jargon. You ask what a thing is before you ask where it is stored, you keep the logical model free of physical choices, and you would rather have one agreed definition than three convenient ones.",
      "tags": [
        "role",
        "modelling",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:53.000Z",
      "updatedAt": "2026-10-05T09:00:53.000Z"
    },
    {
      "id": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
      "type": "Context",
      "name": "Catalog extract",
      "content": "The catalog entries, entity list or component descriptions to work from, as they stand in the repository or in the draft.\n\n{{catalog extract}}",
      "tags": [
        "context",
        "catalog",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:54.000Z",
      "updatedAt": "2026-10-05T09:00:54.000Z"
    },
    {
      "id": "ecc88a7e-4160-4a44-af93-30609fd71f3f",
      "type": "Task",
      "name": "Define the data entities",
      "content": "Write the data entity catalog entries for the entities of {{data domain}} from the material given. For each entity: its name to the naming standard, a definition a business owner would sign, its key attributes, the business function that creates it, its owner or the fact that it has none, its system of record, and the entities it relates to. Where the material uses two names for one thing, keep one and list the other as a synonym. The reader is the domain owner who will approve the definitions.",
      "tags": [
        "task",
        "catalog",
        "entities",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:55.000Z",
      "updatedAt": "2026-10-05T09:00:55.000Z"
    },
    {
      "id": "4de39862-b8c2-4234-a520-2e1a1eeeb3a1",
      "type": "Task",
      "name": "Logical data components",
      "content": "Group the entities given into logical data components: the units of data the architecture treats together because they share an owner, a lifecycle and a reason to be held in one place. Name each component, list its entities, state why they belong together and which business functions use it. Say which groupings are open to challenge and why. These components are what the application architecture will map its systems to.",
      "tags": [
        "task",
        "catalog",
        "components",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:56.000Z",
      "updatedAt": "2026-10-05T09:00:56.000Z"
    },
    {
      "id": "af8f1e14-e499-48ca-8ae7-bb2459f1a20e",
      "type": "Task",
      "name": "Physical data components",
      "content": "Describe the physical data components that realise the logical components given: the databases, files, services or stores that hold each one today or will in the target. For each physical component state which logical component it realises, its technology class without naming vendors unless the material does, its owner, its location, and where one logical component is split across several physical ones or one store holds several. Keep the mapping explicit in both directions.",
      "tags": [
        "task",
        "catalog",
        "components",
        "physical",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:57.000Z",
      "updatedAt": "2026-10-05T09:00:57.000Z"
    },
    {
      "id": "103aee15-7cf4-4ac0-adc9-b0194eb32c6c",
      "type": "Task",
      "name": "Catalog review for overlap and gaps",
      "content": "Review the catalog extract given for overlap and gaps. Find entities that are the same thing under two names, one name used for two things, definitions that describe a system rather than a business thing, attributes that are really entities, entities with no creating function or no owner, and relationships with no cardinality. Say what to merge, split, rename or complete, in the order it should be done.",
      "tags": [
        "task",
        "catalog",
        "review",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:58.000Z",
      "updatedAt": "2026-10-05T09:00:58.000Z"
    },
    {
      "id": "7c6eb957-9bdb-498a-beff-638d27c633a8",
      "type": "Task",
      "name": "Catalog maintenance standard",
      "content": "Write the standard for maintaining the data entity and component catalog: what a complete entry contains, who may add or change an entry, how a definition is approved and by whom, how synonyms and retired entries are handled, how the catalog links to the glossary and the models, and how often it is reviewed. The reader is an architect or steward adding their first entry, so every rule has an example.",
      "tags": [
        "task",
        "catalog",
        "standard",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:00:59.000Z",
      "updatedAt": "2026-10-05T09:00:59.000Z"
    },
    {
      "id": "61cc485f-b41b-4efa-8cf6-3dc6bdc59a39",
      "type": "Task",
      "name": "Catalog walkthrough note to domain owners",
      "content": "Write the note that sends the draft catalog entries for {{data domain}} to the domain owner for review. Say what you are asking them to check (the definitions, the owner names, the system of record), what you have assumed and want confirmed, which entries you are least sure of and why, how to send corrections, and the date you need them by. Make it easy for someone who has never seen a catalog to reply usefully.",
      "tags": [
        "task",
        "catalog",
        "conversation",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:00.000Z",
      "updatedAt": "2026-10-05T09:01:00.000Z"
    },
    {
      "id": "d81bf753-c72c-4451-aa39-5911db9347a9",
      "type": "Format",
      "name": "Standard document",
      "content": "Write the standard with a one-paragraph **Scope** (what it governs and who must follow it), then numbered rules, each one sentence long with an example beneath it in italics, then **Exceptions** (how to ask and who decides) and **Review** (how often and who owns the standard). No rule without an example.",
      "tags": [
        "format",
        "standard",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:01.000Z",
      "updatedAt": "2026-10-05T09:01:01.000Z"
    },
    {
      "id": "aa261336-018a-41f7-bbc8-a34d67526306",
      "type": "Constraints",
      "name": "One entity, one definition",
      "content": "Each business thing is one entity with one definition and one name; everything else is a synonym recorded against it. Never create two entities because two systems store a thing differently, and never let a definition describe where data lives or how a system behaves instead of what the thing is.",
      "tags": [
        "constraints",
        "definitions",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:02.000Z",
      "updatedAt": "2026-10-05T09:01:02.000Z"
    },
    {
      "id": "16fec59c-0847-4837-a504-623754e60094",
      "type": "Constraints",
      "name": "Catalog entries complete or marked draft",
      "content": "An entry is complete only when it has a definition, an owner or an explicit \"no owner yet\", a creating function and a system of record or an explicit conflict. Anything less is marked **Draft** with the missing fields named. Never fill a field with a guess to make an entry look finished.",
      "tags": [
        "constraints",
        "catalog",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:03.000Z",
      "updatedAt": "2026-10-05T09:01:03.000Z"
    },
    {
      "id": "7944c208-84b7-4872-9af3-e0af935e17b4",
      "type": "Constraints",
      "name": "Use the glossary's words",
      "content": "Use the business glossary's term for every concept that has one, and flag every concept you need that the glossary does not define. When the material uses a different word for a defined term, keep the glossary's word and list the other as a synonym. Never coin a new term when an agreed one exists.",
      "tags": [
        "constraints",
        "glossary",
        "Data architecture pack"
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:04.000Z",
      "updatedAt": "2026-10-05T09:01:04.000Z"
    },
    {
      "id": "e5fba729-cc07-42c8-986d-163edb424ba4",
      "type": "Role",
      "name": "Data architecture reviewer",
      "content": "You are the senior architect who reviews data models, catalogs and diagrams before they enter the repository. You read the whole artefact before you comment, you check it against the naming standard, the principles and the glossary, and you separate what is wrong from what you would have done differently. Your findings are specific enough that the author can fix them without asking you what you meant.",
      "tags": [
        "role",
        "review",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:05.000Z",
      "updatedAt": "2026-10-05T09:01:05.000Z"
    },
    {
      "id": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
      "type": "Context",
      "name": "Data model description",
      "content": "The data model, or the models being compared, as the author describes them: entities, attributes, relationships, keys and any notes. Treat each as the whole model; where it is silent, say so rather than assuming.\n\n{{data model}}",
      "tags": [
        "context",
        "model",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:06.000Z",
      "updatedAt": "2026-10-05T09:01:06.000Z"
    },
    {
      "id": "89436b13-83ce-4b02-9080-36bcded59aa9",
      "type": "Task",
      "name": "Conceptual data model for a domain",
      "content": "Build the conceptual data model (the conceptual data diagram) for {{data domain}} from the entities given: each business entity with a one-line definition, and the relationships with their meaning and cardinality in words, such as \"a customer places many orders\". No attributes beyond identity, no keys, no system names. Where business services are known, say which entities each service uses. State the business rules the relationships encode and the questions left open. The reader is the domain owner, who must recognise their business in it.",
      "tags": [
        "task",
        "model",
        "conceptual",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:07.000Z",
      "updatedAt": "2026-10-05T09:01:07.000Z"
    },
    {
      "id": "2ba79058-5326-443d-ab14-67e9449338b2",
      "type": "Task",
      "name": "Logical data model from the conceptual",
      "content": "Develop the logical data model (the logical data diagram) from the conceptual model given. For each entity list its attributes with a definition, its business identifier, and whether each attribute is required, optional or derived. Resolve many-to-many relationships, name the associative entities, and record every normalisation decision and why. Where subtypes nest, describe the class hierarchy: the tree from the general entity down and what each level adds. Stay independent of any product. The reader is the architect who maps it to physical components.",
      "tags": [
        "task",
        "model",
        "logical",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:08.000Z",
      "updatedAt": "2026-10-05T09:01:08.000Z"
    },
    {
      "id": "e4354209-d491-4ee9-b110-9b30296e28d9",
      "type": "Task",
      "name": "Physical data model considerations",
      "content": "Write the physical data model considerations for the logical model given, at the architecture level: the candidate storage styles for each logical component and why, where denormalisation, partitioning or replication is justified by a stated access pattern, which identifiers become system keys and which business keys must be preserved, how history and effective dating are handled, and what is left to the design team. Name vendors only where the material does. The reader is the solution architect who will design the schema.",
      "tags": [
        "task",
        "model",
        "physical",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:09.000Z",
      "updatedAt": "2026-10-05T09:01:09.000Z"
    },
    {
      "id": "84795e92-23bc-4479-bd82-e4fc1af708bd",
      "type": "Task",
      "name": "Data model review",
      "content": "Review the data model given against the naming standard, the glossary and the principles. Check that every entity has a definition and an identifier, that relationships have cardinality and meaning, that no attribute hides an entity and no entity is really an attribute, that subtypes are justified, that nothing physical has leaked into a logical model, and that the model answers the business questions it was built for. Write findings the author can act on, and name the three that matter most.",
      "tags": [
        "task",
        "model",
        "review",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:10.000Z",
      "updatedAt": "2026-10-05T09:01:10.000Z"
    },
    {
      "id": "e449b89a-dbde-4968-be0a-91ef0138b64c",
      "type": "Task",
      "name": "Reconcile two models of one domain",
      "content": "Reconcile the two models of the same domain given. Pair the entities that mean the same thing under different names, list the entities only one model has and decide whether they are missing or out of scope, find the relationships and rules the models disagree on, and for each difference propose which version to keep and why. Produce the merged entity list and the decisions still needed from the domain owner. Record what each model was built for, because that usually explains the differences.",
      "tags": [
        "task",
        "model",
        "reconciliation",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:11.000Z",
      "updatedAt": "2026-10-05T09:01:11.000Z"
    },
    {
      "id": "8be6b534-bc52-489a-9129-5e4d6c662937",
      "type": "Task",
      "name": "Explain a data model to business readers",
      "content": "Explain the data model given to business readers who will never see the diagram. Describe each main entity as a thing the business handles, the relationships as sentences about how the business works, the rules the model enforces and why they matter to them, and the questions the business will be able to answer once systems follow it. Close with the two or three places where the model changes how they work today and what you need them to confirm.",
      "tags": [
        "task",
        "model",
        "communication",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:12.000Z",
      "updatedAt": "2026-10-05T09:01:12.000Z"
    },
    {
      "id": "1b9af371-fec5-4a33-8466-ac52146de274",
      "type": "Format",
      "name": "Model described in words",
      "content": "Describe the model so a colleague could draw it: a list of entities with a one-line definition each, subtypes indented under their supertype; a list of relationships, each as a sentence with both cardinalities; a list of attributes per entity where the task asks for them, marking identifiers in bold; then **Rules the model enforces** and **Questions it leaves open**. No diagram syntax, no code.",
      "tags": [
        "format",
        "model",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:13.000Z",
      "updatedAt": "2026-10-05T09:01:13.000Z"
    },
    {
      "id": "36bca6e6-dfe9-4691-ade6-18ca19df9293",
      "type": "Format",
      "name": "Plain-language brief for leaders",
      "content": "One page for a business reader: a two-sentence opening that says what this is and what you need from them, then three short sections with bold labels: **What it means for the business**, **What changes**, **What we need decided**. No notation, no acronyms without the words, no more than one short table.",
      "tags": [
        "format",
        "brief",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:14.000Z",
      "updatedAt": "2026-10-05T09:01:14.000Z"
    },
    {
      "id": "c761b7b9-0838-40ad-918c-827e06792955",
      "type": "Constraints",
      "name": "Logical before physical",
      "content": "Keep the layers apart. A conceptual model has entities, relationships and meaning; a logical model adds attributes, identifiers and rules; only a physical model names tables, columns, indexes or products. When a physical choice creeps into a higher layer, move it down and say why it is not an architecture decision.",
      "tags": [
        "constraints",
        "modelling",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:15.000Z",
      "updatedAt": "2026-10-05T09:01:15.000Z"
    },
    {
      "id": "b6a6f3ba-6f07-4947-ae65-d1e597347995",
      "type": "Constraints",
      "name": "Review the artefact, not the author",
      "content": "Comment on the model, catalog or diagram, never on the person. Every finding names what is wrong, where, and what right looks like; \"unclear\" and \"weak\" are not findings. Separate what breaks a standard or principle from what you would have done differently, and label the second kind as preference.",
      "tags": [
        "constraints",
        "review",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:16.000Z",
      "updatedAt": "2026-10-05T09:01:16.000Z"
    },
    {
      "id": "29a5abd3-3811-49aa-be6e-1fb2078f1605",
      "type": "Constraints",
      "name": "Business terms for business readers",
      "content": "When the reader is a business person, use the words they use for their customers, products and orders, never entity names, keys, cardinalities or system names. Say \"every order belongs to exactly one customer\", not \"a mandatory one-to-many relationship\". Where a technical term is unavoidable, say it once with its plain meaning beside it.",
      "tags": [
        "constraints",
        "communication",
        "Data architecture pack"
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:17.000Z",
      "updatedAt": "2026-10-05T09:01:17.000Z"
    },
    {
      "id": "a7ebbec8-8c4d-46be-8b89-a8bed032b280",
      "type": "Role",
      "name": "Business glossary owner",
      "content": "You are the governance analyst who owns the business glossary. You get business people to agree what their words mean, one term at a time, and you write definitions that decide edge cases rather than describe the obvious. You are patient with disagreement, firm that a term has one definition, and you keep every glossary term linked to the entities and reports that use it.",
      "tags": [
        "role",
        "glossary",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:18.000Z",
      "updatedAt": "2026-10-05T09:01:18.000Z"
    },
    {
      "id": "73a4c9b4-e50d-4aa5-814e-42483c84beac",
      "type": "Context",
      "name": "Glossary extract",
      "content": "The glossary terms, candidate definitions and sources to work from, as they stand today.\n\n{{glossary extract}}",
      "tags": [
        "context",
        "glossary",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:19.000Z",
      "updatedAt": "2026-10-05T09:01:19.000Z"
    },
    {
      "id": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
      "type": "Context",
      "name": "Data governance bodies and policies",
      "content": "Who decides about data here and under what policies.\n\n- Decision body: {{governance body}}\n- Data domains and their owners: {{data domains}}\n- Policies and standards sit in {{architecture repository}} and apply to every system that creates or changes enterprise data.",
      "tags": [
        "context",
        "governance",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:20.000Z",
      "updatedAt": "2026-10-05T09:01:20.000Z"
    },
    {
      "id": "1a4fbee5-6561-4d7f-a77d-7109f77b7a1a",
      "type": "Task",
      "name": "Define a business term",
      "content": "Write the glossary definition of {{term}} from the material given. State what the term means in one or two sentences a new employee could apply, what it includes and excludes at the edges, its synonyms and the terms it is often confused with, the business owner, the data entity or attribute that holds it, and the reports or processes that depend on it. Give two examples: one clearly in, one clearly out. The reader is the business owner who will sign it.",
      "tags": [
        "task",
        "glossary",
        "definition",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:21.000Z",
      "updatedAt": "2026-10-05T09:01:21.000Z"
    },
    {
      "id": "3ab428e0-e30e-423b-994d-75dcc933b1c6",
      "type": "Task",
      "name": "Resolve a definition conflict",
      "content": "Resolve the conflict over {{term}} in the material given, where two or more parts of the business use it differently. Lay out each meaning, who uses it and for what, where the meanings overlap and where they diverge, and what breaks when they are mixed in one report. Propose one of three outcomes: one definition wins, the term splits into two named terms, or the term is retired. Say what each outcome costs whom. Do not pick quietly; make the recommendation and the decision explicit.",
      "tags": [
        "task",
        "glossary",
        "conflict",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:22.000Z",
      "updatedAt": "2026-10-05T09:01:22.000Z"
    },
    {
      "id": "47c0e418-c8da-4b03-a64e-59b739f213a5",
      "type": "Task",
      "name": "Glossary coverage review",
      "content": "Review how well the glossary given covers the enterprise data: terms used in the models, reports and policies that the glossary does not define, defined terms nobody uses, definitions that describe a system instead of a business meaning, terms with no owner, and groups of terms that are really one. Rank the gaps by how many artefacts and decisions depend on the missing or weak definition.",
      "tags": [
        "task",
        "glossary",
        "review",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:23.000Z",
      "updatedAt": "2026-10-05T09:01:23.000Z"
    },
    {
      "id": "0f0763a2-f0c6-43f9-b17a-104b68b0a0d6",
      "type": "Task",
      "name": "Glossary standard",
      "content": "Write the glossary standard: what makes a term eligible, what a complete entry contains, how a definition is drafted, challenged and approved and by which roles, how synonyms, abbreviations and retired terms are handled, how terms link to data entities and reports, and how often the glossary is reviewed. The reader is a steward writing their first entry, so each rule comes with an example of compliance.",
      "tags": [
        "task",
        "glossary",
        "standard",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:24.000Z",
      "updatedAt": "2026-10-05T09:01:24.000Z"
    },
    {
      "id": "7b60dbcd-f03c-459b-a6c9-8b3349158083",
      "type": "Task",
      "name": "Definition sign-off request to a business owner",
      "content": "Write the message that asks the business owner of {{term}} to sign off its definition. Give the proposed definition, what it settles that was unclear, who else has agreed, what will use it once it is approved, and the one question you still need them to answer. Tell them how to approve, how to object, and by when. Assume they have two minutes.",
      "tags": [
        "task",
        "glossary",
        "conversation",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:25.000Z",
      "updatedAt": "2026-10-05T09:01:25.000Z"
    },
    {
      "id": "efa111d5-02d9-491f-b068-b323eee1b438",
      "type": "Task",
      "name": "Glossary to data model mapping",
      "content": "Map the glossary terms given to the entities and attributes of the data model given. For each term, the entity or attribute that holds it, or the fact that nothing does; for each entity and attribute, the term that defines it, or the fact that none does. List the mismatches: terms held in several places, attributes with no business term, and places where the model's name and the glossary's name differ. These mismatches are the work list for the modeller and the glossary owner.",
      "tags": [
        "task",
        "glossary",
        "mapping",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:26.000Z",
      "updatedAt": "2026-10-05T09:01:26.000Z"
    },
    {
      "id": "fa9babc0-71fb-45e4-9060-4e18f63c8179",
      "type": "Format",
      "name": "Glossary entry",
      "content": "Write each entry with bold labels: **Term**, **Definition** (one or two sentences), **Includes and excludes** (the edge cases), **Synonyms and confused with**, **Owner**, **Held in** (entity or attribute), **Used by** (reports and processes), **Examples** (one in, one out), **Status**. Keep every field one or two lines.",
      "tags": [
        "format",
        "glossary",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:27.000Z",
      "updatedAt": "2026-10-05T09:01:27.000Z"
    },
    {
      "id": "bc40d393-3b7e-44da-bb73-a5780a711c9b",
      "type": "Format",
      "name": "Mapping table",
      "content": "Present the mapping as a table: source item, target item, relationship or transformation, rule or note, open question. One row per pairing, including rows where one side is empty, marked **Unmapped**. Under the table, list the mismatches, gaps and decisions the task asks for, in the order they should be resolved.",
      "tags": [
        "format",
        "mapping",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:28.000Z",
      "updatedAt": "2026-10-05T09:01:28.000Z"
    },
    {
      "id": "fb3fd01a-af33-4475-bc6f-f9e4b9db40b1",
      "type": "Constraints",
      "name": "Definitions must decide edge cases",
      "content": "A definition is finished only when a stranger could use it to decide the hard cases: the trial customer, the cancelled order, the rehired employee. Describe what is in and what is out, not what is obvious. Never define a term by naming the system or report it comes from.",
      "tags": [
        "constraints",
        "definitions",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:29.000Z",
      "updatedAt": "2026-10-05T09:01:29.000Z"
    },
    {
      "id": "4018d027-4222-4493-86d9-f276175dc2bc",
      "type": "Constraints",
      "name": "Decision rights by role, never by person",
      "content": "Assign every decision, approval and escalation to a named role or body, never to a named person. One role is accountable for each decision; others are consulted or informed. Where the material names a person, record the role they hold.",
      "tags": [
        "constraints",
        "governance",
        "Data architecture pack"
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:30.000Z",
      "updatedAt": "2026-10-05T09:01:30.000Z"
    },
    {
      "id": "f03a6b71-1e3c-4ee3-81ad-a5141646ed87",
      "type": "Context",
      "name": "Matrix inputs",
      "content": "The business functions, applications and data entities to relate, with what is known about which function or application creates, reads, updates or deletes each entity.\n\n{{matrix inputs}}",
      "tags": [
        "context",
        "matrix",
        "Data architecture pack"
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:31.000Z",
      "updatedAt": "2026-10-05T09:01:31.000Z"
    },
    {
      "id": "284c8953-1748-4e3a-8ab8-e23810d49c83",
      "type": "Task",
      "name": "Data entity to business function matrix",
      "content": "Build the data entity to business function matrix from the material given: entities as rows, business functions as columns, and in each cell whether the function creates, reads, updates or deletes the entity. Then read the matrix: entities no function creates, entities several functions create, functions that touch nothing, and entities only read. For each, say what it probably means and what to check. This matrix shows which part of the business owns each entity.",
      "tags": [
        "task",
        "matrix",
        "business function",
        "Data architecture pack"
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:32.000Z",
      "updatedAt": "2026-10-05T09:01:32.000Z"
    },
    {
      "id": "a72b9bd7-a435-4693-8076-858c591699ec",
      "type": "Task",
      "name": "Application to data matrix",
      "content": "Build the application to data matrix from the material given: data entities as rows, applications as columns, and in each cell whether the application creates, reads, updates or deletes the entity, or holds a copy. Then read it: entities created in more than one application, entities held in copies with no clear source, applications that create nothing, and entities no application holds. Say what each pattern implies for the system of record and for integration.",
      "tags": [
        "task",
        "matrix",
        "application",
        "Data architecture pack"
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:33.000Z",
      "updatedAt": "2026-10-05T09:01:33.000Z"
    },
    {
      "id": "9149ccd5-cf3f-489e-856b-16a31ae48d09",
      "type": "Task",
      "name": "Analyse the matrices for system of record candidates",
      "content": "Using the entity to function and application to data matrices given, propose the system of record for each entity. Reason from where the entity is created by the function that owns it, where the business trusts the value, and where corrections are made. Where the two matrices disagree, say so. Give each proposal a confidence and the evidence behind it, and list the entities where no candidate is defensible yet.",
      "tags": [
        "task",
        "matrix",
        "system of record",
        "Data architecture pack"
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:34.000Z",
      "updatedAt": "2026-10-05T09:01:34.000Z"
    },
    {
      "id": "7a130057-5ce9-4792-b27f-cd1f4656090b",
      "type": "Task",
      "name": "Gaps and overlaps from the matrices",
      "content": "List the gaps and overlaps the matrices given reveal: entities with no owner function, entities created in several places, applications that duplicate each other's data, functions with no application support, and copies with no stated purpose. For each, state the risk in business terms, the principle it breaks, and whether it is a target architecture gap, a governance gap or a data quality symptom. Order by business impact.",
      "tags": [
        "task",
        "matrix",
        "gaps",
        "Data architecture pack"
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:35.000Z",
      "updatedAt": "2026-10-05T09:01:35.000Z"
    },
    {
      "id": "cd464aae-5f1e-4577-846b-cc394b56ed4a",
      "type": "Task",
      "name": "Conversation with application owners about a conflict",
      "content": "Prepare the conversation with the owners of the applications that both create {{entity}}. Set out the facts from the matrices, what each owner will say and why they are partly right, the options (one creates and the other subscribes, both create under a matching rule, a new master), what each option costs each owner, and the decision you will ask them to make or escalate. Write it as the points you will make and the questions you will ask, in order.",
      "tags": [
        "task",
        "matrix",
        "conversation",
        "Data architecture pack"
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:36.000Z",
      "updatedAt": "2026-10-05T09:01:36.000Z"
    },
    {
      "id": "b67001c0-fc33-4b96-8434-947135769dfb",
      "type": "Task",
      "name": "Matrix refresh and repository update note",
      "content": "Draft the note that will record the decision about {{entity}} in the architecture repository and tell the affected owners, written for the option you recommend so it can go out the day the decision is made: what was decided, who decided it, what changes in the matrices and the catalog, which projects must now follow it, and what happens to the other copies. Keep it short enough to be read, and precise enough that an architect in a year understands why.",
      "tags": [
        "task",
        "matrix",
        "repository",
        "Data architecture pack"
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:37.000Z",
      "updatedAt": "2026-10-05T09:01:37.000Z"
    },
    {
      "id": "c5a1d7ab-517b-41f0-b395-131d362813d7",
      "type": "Format",
      "name": "Matrix as a table",
      "content": "Present the matrix as a table with the entities as rows and the functions or applications as columns, one short code per cell (C create, R read, U update, D delete, X copy, blank for none) and a legend above it. Below the table, **What the matrix shows**: a numbered list of the patterns found, each with the cells it refers to and what to check.",
      "tags": [
        "format",
        "matrix",
        "Data architecture pack"
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:38.000Z",
      "updatedAt": "2026-10-05T09:01:38.000Z"
    },
    {
      "id": "e7f8e5c3-c814-46cd-aaf4-0a8dc50485da",
      "type": "Constraints",
      "name": "A matrix ends with what it shows",
      "content": "A matrix is an argument, not a filing exercise. After the grid, state the patterns it reveals and what each one means for ownership, system of record or integration. Never hand over a grid without its reading, and never read into it something the cells do not support.",
      "tags": [
        "constraints",
        "matrix",
        "Data architecture pack"
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:39.000Z",
      "updatedAt": "2026-10-05T09:01:39.000Z"
    },
    {
      "id": "57d4f5ab-f211-4bdd-b93b-1c28b5eb5794",
      "type": "Context",
      "name": "Data flow facts",
      "content": "What is known about how data moves and lives: which systems send which entities to which others, how and how often, where copies are held, and the events that create, change, archive and remove each entity.\n\n{{data flow facts}}",
      "tags": [
        "context",
        "flows",
        "Data architecture pack"
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:40.000Z",
      "updatedAt": "2026-10-05T09:01:40.000Z"
    },
    {
      "id": "8c816b52-12a0-4de6-a296-d9eeef82127a",
      "type": "Task",
      "name": "Data dissemination diagram",
      "content": "Describe the data dissemination diagram for the entities in scope from the material given: which applications hold each logical data component and which business services use it, which are the source and which receive copies, how the data travels between them (interface, file, replication, manual) and how often, and where a copy is transformed on the way. Show the system of record for each component and every place it is duplicated. State in words what the diagram shows about redundancy and dependency, so the reader does not have to count arrows.",
      "tags": [
        "task",
        "diagram",
        "dissemination",
        "Data architecture pack"
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:41.000Z",
      "updatedAt": "2026-10-05T09:01:41.000Z"
    },
    {
      "id": "0736597a-fa97-4c69-8d8d-1f5a160f9513",
      "type": "Task",
      "name": "Copies and hops analysis",
      "content": "Analyse the copies and hops in the flows given. For each entity, count the places it is held and the number of hops from its system of record to its furthest consumer, say how stale each copy can be and whether anyone reconciles it, and name the copies that exist only because an interface was easier than a shared service. Rank the copies by the harm a disagreement would cause, and propose which to remove, which to make read-only and which to keep with a stated reason.",
      "tags": [
        "task",
        "flows",
        "copies",
        "Data architecture pack"
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:42.000Z",
      "updatedAt": "2026-10-05T09:01:42.000Z"
    },
    {
      "id": "8cbf4f4d-b851-4036-a349-c242685fe420",
      "type": "Task",
      "name": "Data lifecycle diagram for an entity",
      "content": "Describe the data lifecycle diagram for {{entity}} from the material given: the states it passes through from the event that creates it to the event that removes it, the business event and the function that trigger each transition, the system that holds it in each state, and what may and may not be done to it in each state. Mark the states where the entity is shared outside its owning function and the state in which it becomes a record to retain. Say what the diagram shows about where control is lost.",
      "tags": [
        "task",
        "diagram",
        "lifecycle",
        "Data architecture pack"
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:43.000Z",
      "updatedAt": "2026-10-05T09:01:43.000Z"
    },
    {
      "id": "ed2bde2c-0b3a-4b6b-9cc5-77964cddc438",
      "type": "Task",
      "name": "Lifecycle events and owning functions",
      "content": "For the lifecycle of {{entity}} given, list each business event that changes its state, the function and role that cause the event, the system that records it, the data that must be complete before the transition is allowed, and the downstream systems that must learn of it. Flag transitions that happen in more than one system, events with no owner, and states the business uses that no system records.",
      "tags": [
        "task",
        "lifecycle",
        "ownership",
        "Data architecture pack"
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:44.000Z",
      "updatedAt": "2026-10-05T09:01:44.000Z"
    },
    {
      "id": "9e27aa2e-7aaf-4702-800e-211a7e20792c",
      "type": "Task",
      "name": "Cross-domain flow narrative",
      "content": "Write the narrative of how data flows across the domains in the material given, for readers who make decisions but do not read diagrams. Follow one or two entities from creation to retirement, naming where each is mastered, who changes it, where copies live and why, and where the business sees the effects: late reports, mismatched letters, double counting. End with the three changes to the flows that would matter most and who would need to agree.",
      "tags": [
        "task",
        "flows",
        "communication",
        "Data architecture pack"
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:45.000Z",
      "updatedAt": "2026-10-05T09:01:45.000Z"
    },
    {
      "id": "e8d7db8f-6b09-42d1-9d46-ba13b3463555",
      "type": "Task",
      "name": "Diagram review",
      "content": "Review the diagram described in the draft given against the standards and the repository's other artefacts. Check that every element is named to the standard, that each flow has a direction, a mechanism and a frequency, that systems of record match the catalog, that no element appears that the catalog does not know, that the legend matches the symbols used, and that the diagram answers the concern it was drawn for. State what to change and whether it can enter the repository.",
      "tags": [
        "task",
        "diagram",
        "review",
        "Data architecture pack"
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:46.000Z",
      "updatedAt": "2026-10-05T09:01:46.000Z"
    },
    {
      "id": "49b29bb2-bba9-4c1a-9b23-cbc8a1245e90",
      "type": "Format",
      "name": "Diagram described for drawing",
      "content": "Describe the diagram so a colleague could draw it: **Elements** (a list, each with its type and label), **Connections** (one line each: from, to, what flows, how, how often), **Layers or groupings** (which elements sit together and why), **Legend** (the symbols and colours to use), then **What to notice** (three sentences on what the drawing shows). No diagram syntax.",
      "tags": [
        "format",
        "diagram",
        "Data architecture pack"
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:47.000Z",
      "updatedAt": "2026-10-05T09:01:47.000Z"
    },
    {
      "id": "ff6ed2d2-bf79-4a10-b818-0d3e7f35a3b7",
      "type": "Format",
      "name": "Register table",
      "content": "Present the items as a table: item, description, impact in business terms, owner, proposed action, status. Order by impact, highest first. Under the table, a short paragraph on the items that need a decision from someone outside the team and who that is.",
      "tags": [
        "format",
        "register",
        "Data architecture pack"
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:48.000Z",
      "updatedAt": "2026-10-05T09:01:48.000Z"
    },
    {
      "id": "8dd18e9e-98fc-4d94-90f2-51d259362a64",
      "type": "Format",
      "name": "Lifecycle states table",
      "content": "Present the lifecycle as a table: state, event that enters it, function and role that cause the event, system that records it, what may change in this state, next states. One row per state in order. Below the table, list the transitions that cross a system boundary and the states where control or ownership is unclear.",
      "tags": [
        "format",
        "lifecycle",
        "Data architecture pack"
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:49.000Z",
      "updatedAt": "2026-10-05T09:01:49.000Z"
    },
    {
      "id": "47faa8b5-bd0f-44c8-928c-6d58feb306ac",
      "type": "Constraints",
      "name": "Diagrams a colleague can draw",
      "content": "Describe every diagram so that a colleague with the description and no other knowledge could draw it and a reader could check it: every element named and typed, every connection with direction, content and mechanism, every grouping explained. A diagram that needs its author beside it to be understood is not finished.",
      "tags": [
        "constraints",
        "diagram",
        "Data architecture pack"
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:50.000Z",
      "updatedAt": "2026-10-05T09:01:50.000Z"
    },
    {
      "id": "17db55c2-3020-419e-ba30-d3ceec263f00",
      "type": "Role",
      "name": "Data security architect",
      "content": "You are the architect who decides how data is classified and protected across the enterprise, working with the security team but owning the data view. You classify by what harm a disclosure or corruption would do, not by which system holds the data, you design access around roles and purposes, and you make every control traceable to a classification level or a stated obligation. You keep security decisions out of the hands of whichever team happens to build first.",
      "tags": [
        "role",
        "security",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:51.000Z",
      "updatedAt": "2026-10-05T09:01:51.000Z"
    },
    {
      "id": "46e2047f-d0a1-4c62-b6c2-e140f53005e8",
      "type": "Context",
      "name": "Classification scheme",
      "content": "The classification levels this enterprise uses, from least to most sensitive, and the rule that the level of a record is the level of its most sensitive attribute.\n\n- Levels: {{classification levels}}\n- A level is assigned by the data owner and recorded in the catalog; handling rules follow the level, not the system.",
      "tags": [
        "context",
        "classification",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:52.000Z",
      "updatedAt": "2026-10-05T09:01:52.000Z"
    },
    {
      "id": "85be031a-4de2-4428-b414-7d62b9e737e8",
      "type": "Context",
      "name": "Access facts",
      "content": "What is known about who accesses which data, from where and for what: roles, applications, integrations, third parties, and the controls in place today.\n\n{{access facts}}",
      "tags": [
        "context",
        "access",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:53.000Z",
      "updatedAt": "2026-10-05T09:01:53.000Z"
    },
    {
      "id": "247c0418-bd3d-415b-a77c-61716537dcea",
      "type": "Task",
      "name": "Classify a domain's entities",
      "content": "Classify the entities and sensitive attributes of {{data domain}} in the material given, using the classification scheme. For each, the level, the reason in terms of the harm a disclosure, corruption or loss would cause and to whom, the attributes that drive the level, and the handling this level requires for storage, transfer, access and disposal. Flag entities whose level depends on context or combination, and the ones the owner must confirm. The reader is the data owner who assigns the level.",
      "tags": [
        "task",
        "classification",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:54.000Z",
      "updatedAt": "2026-10-05T09:01:54.000Z"
    },
    {
      "id": "083f4a5e-82f0-4d02-bc84-45d7c2db2545",
      "type": "Task",
      "name": "Data security diagram",
      "content": "Describe the data security diagram for the components in scope from the material given: which actors and roles may access which data components, through which applications and interfaces, at which classification level, and where the data crosses a trust boundary (between networks, organizations or countries). Show where access is by role and purpose and where it is by system account, and where the same data is reachable by a path with weaker control. Where a grid reads better, add it as a matrix of actors against data components. Say which paths worry you most and why.",
      "tags": [
        "task",
        "diagram",
        "security",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:55.000Z",
      "updatedAt": "2026-10-05T09:01:55.000Z"
    },
    {
      "id": "5788603e-7b30-44fb-85e5-927a5f5b3bd8",
      "type": "Task",
      "name": "Access patterns and segregation at the architecture level",
      "content": "Define the access patterns for the data in scope from the material given: for each classification level and data component, who may create, read, change and delete, under what purpose, through which channel, and what is logged. State the segregation rules the architecture must enforce: duties that may not sit with one role, data that may not be combined in one store or report, and environments that may not hold production data. Leave the mechanism to the security design; state the rule and why.",
      "tags": [
        "task",
        "security",
        "access",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:56.000Z",
      "updatedAt": "2026-10-05T09:01:56.000Z"
    },
    {
      "id": "7751e727-5c03-4abb-9ba3-74cc61893e35",
      "type": "Task",
      "name": "Classification standard",
      "content": "Write the data classification standard: the levels and what each means in terms of harm, who assigns a level and when, how a level is recorded in the catalog and carried through copies and derived data, the handling rules per level for storage, transfer, sharing, access and disposal, how a level is changed and who approves, and how compliance is checked. The reader is a data owner classifying their first entity, so each rule comes with an example.",
      "tags": [
        "task",
        "classification",
        "standard",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:57.000Z",
      "updatedAt": "2026-10-05T09:01:57.000Z"
    },
    {
      "id": "8279b9b7-dd86-476f-b75a-a56a6651f1a4",
      "type": "Task",
      "name": "Classification gap list",
      "content": "List the classification gaps in the material given against the standard: entities with no level, levels that contradict the harm their attributes could cause, copies and derived data sets carrying a lower level than their source, levels assigned by a team that does not own the data, and handling that does not match the level. For each gap name the owner who must act and the risk while it stays open.",
      "tags": [
        "task",
        "classification",
        "gaps",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:58.000Z",
      "updatedAt": "2026-10-05T09:01:58.000Z"
    },
    {
      "id": "891ac26b-e454-4634-b7a7-9b9230b8e9e3",
      "type": "Task",
      "name": "Security requirements for the architecture requirements specification",
      "content": "Write the data security requirements that go into the architecture requirements specification for {{initiative}}, from the access facts given and the access patterns defined above. Each requirement is one testable sentence that names the data, the level or obligation it comes from, and what the solution must do or prevent. Group them by storage, transfer, access, logging and disposal, and mark which are mandatory and which are preferred. The reader is the solution architect who must show compliance.",
      "tags": [
        "task",
        "security",
        "requirements",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:01:59.000Z",
      "updatedAt": "2026-10-05T09:01:59.000Z"
    },
    {
      "id": "ebd01e9a-7ad1-4fc9-b2ef-86ab45d4b5de",
      "type": "Format",
      "name": "Classification table",
      "content": "Present the classifications as a table: entity or attribute, level, reason (the harm and to whom), driving attributes, handling required, owner to confirm. One row per item, grouped by level from most to least sensitive. Below the table, the items whose level depends on context and what would change it.",
      "tags": [
        "format",
        "classification",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:00.000Z",
      "updatedAt": "2026-10-05T09:02:00.000Z"
    },
    {
      "id": "1fa05c97-cfbc-4cb9-9763-832207c9d2f3",
      "type": "Constraints",
      "name": "Classification follows the scheme",
      "content": "Assign levels only from the enterprise's classification scheme and only for the reason it defines: the harm a disclosure, corruption or loss would do. Never classify by the system that holds the data, by who asked, or by habit. A record takes the level of its most sensitive attribute, and a copy or derived set never carries a lower level than its source.",
      "tags": [
        "constraints",
        "classification",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:01.000Z",
      "updatedAt": "2026-10-05T09:02:01.000Z"
    },
    {
      "id": "fb3a2a91-30e3-4466-8163-7300f764bf30",
      "type": "Constraints",
      "name": "Least data, least access",
      "content": "Design for the least data and the least access that does the job. Every attribute collected, copied or kept needs a stated purpose; every access needs a role and a purpose; every third party gets what its contract requires and nothing more. Where the material gives no purpose, name the data as a candidate for removal rather than keeping it by default.",
      "tags": [
        "constraints",
        "minimisation",
        "Data architecture pack"
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:02.000Z",
      "updatedAt": "2026-10-05T09:02:02.000Z"
    },
    {
      "id": "2ddc91bf-3633-49a8-b183-9955d55b03ba",
      "type": "Role",
      "name": "Privacy-minded data architect",
      "content": "You are the data architect who builds privacy into the architecture before the privacy office has to ask. You know which entities carry personal data and why, you design so that the data collected, kept and shared is the least that serves a stated purpose, and you turn the privacy office's and legal's requirements into architecture decisions the delivery teams can follow. You never decide what the law requires; you make sure the architecture can meet whatever legal says it does.",
      "tags": [
        "role",
        "privacy",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:03.000Z",
      "updatedAt": "2026-10-05T09:02:03.000Z"
    },
    {
      "id": "ad0e847c-e523-4bfb-8b6d-6aee46a5947a",
      "type": "Context",
      "name": "Personal data facts",
      "content": "What is known about the personal data in scope and the design that handles it: the data elements, whose data they are, the purposes given, where the data is collected, held and shared, the flows and systems proposed, and any consents or notices mentioned.\n\n{{personal data facts}}",
      "tags": [
        "context",
        "personal data",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:04.000Z",
      "updatedAt": "2026-10-05T09:02:04.000Z"
    },
    {
      "id": "53664898-56ea-48d6-ba0f-c5ea9080abe9",
      "type": "Context",
      "name": "Legal and compliance inputs",
      "content": "The requirements, obligations and advice legal, compliance or the privacy office have given, as they gave them. Treat them as the obligations the architecture must meet; do not extend or reinterpret them.\n\n{{compliance inputs}}",
      "tags": [
        "context",
        "compliance",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:05.000Z",
      "updatedAt": "2026-10-05T09:02:05.000Z"
    },
    {
      "id": "ad1cfe2d-9f19-4291-9084-3bd68d858eda",
      "type": "Task",
      "name": "Personal data inventory for an initiative",
      "content": "Build the personal data inventory for {{initiative}} from the material given. For each data element: the category of personal data, whose data it is, the purpose it serves, where it is collected, every system that holds it, who it is shared with inside and outside the enterprise, and the retention and the lawful basis or consent as the material states them. Mark elements with no stated purpose, elements that could identify someone in combination, and special categories that need confirmation from the privacy office. This inventory feeds the record of processing.",
      "tags": [
        "task",
        "privacy",
        "inventory",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:06.000Z",
      "updatedAt": "2026-10-05T09:02:06.000Z"
    },
    {
      "id": "761a93aa-539b-4b65-a2dd-435b9f3b45ac",
      "type": "Task",
      "name": "Privacy design review",
      "content": "Review the design in the material given for privacy by design. Check that every personal data element has a purpose and the design collects nothing beyond it, that identifying data is separated or pseudonymised where the purpose allows, that access follows role and purpose, that retention and deletion are designed rather than left to default, that sharing with third parties is named and limited, and that the design can honour access, correction, deletion and portability requests. Write findings the design team can act on and mark the ones that must be fixed before build.",
      "tags": [
        "task",
        "privacy",
        "review",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:07.000Z",
      "updatedAt": "2026-10-05T09:02:07.000Z"
    },
    {
      "id": "5a301ca8-1b3f-4f25-9333-5593475ed638",
      "type": "Task",
      "name": "Inputs to a privacy impact assessment",
      "content": "Write the architecture inputs to the privacy impact assessment for {{initiative}} from the material given: the processing described as flows of personal data between systems and parties, the data elements and categories involved, the volumes and subjects affected, the controls the architecture provides (minimisation, pseudonymisation, access, retention, logging), the residual risks the architecture cannot remove, and the points where the privacy office must decide. Present it so the privacy office can assess without reading the models.",
      "tags": [
        "task",
        "privacy",
        "assessment",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:08.000Z",
      "updatedAt": "2026-10-05T09:02:08.000Z"
    },
    {
      "id": "91ed2950-31b8-49ca-947e-2900ab9b9e74",
      "type": "Task",
      "name": "Cross-border data map",
      "content": "Map where the personal data in the material given is held, processed and accessed by country or region: each system and third party, its location, the data elements it holds, the direction of each transfer and its mechanism, and the support or backup locations that are easy to forget. Mark the transfers the legal inputs say need a safeguard and the ones nobody has looked at. Do not judge whether a transfer is lawful; show legal exactly what moves where.",
      "tags": [
        "task",
        "privacy",
        "transfers",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:09.000Z",
      "updatedAt": "2026-10-05T09:02:09.000Z"
    },
    {
      "id": "9df498aa-2dd7-4391-bf09-cacd691dd932",
      "type": "Task",
      "name": "Rights-request support design",
      "content": "Design how the architecture supports individuals' rights requests for the data in scope: how a person is identified across systems, how all their data is found including copies and backups, how access and portability requests are assembled, how a correction propagates to every copy, how deletion is carried out and proven where the legal inputs allow it, and what is logged. Name the systems that cannot do this today and the architecture change that fixes each. The reader is the privacy office and the owners of those systems.",
      "tags": [
        "task",
        "privacy",
        "rights",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:10.000Z",
      "updatedAt": "2026-10-05T09:02:10.000Z"
    },
    {
      "id": "24ba819e-62e3-4a0f-95a1-ca214744990d",
      "type": "Task",
      "name": "Privacy questions for legal",
      "content": "Write the questions the architecture needs legal or the privacy office to answer for {{initiative}}, from the material given. For each, what the design needs to know, why the answer changes the architecture, what you will assume until it is answered, and the date you need it by. Group them by who answers. Phrase each so that a lawyer can answer it in one sentence without having to ask what you meant.",
      "tags": [
        "task",
        "privacy",
        "questions",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:11.000Z",
      "updatedAt": "2026-10-05T09:02:11.000Z"
    },
    {
      "id": "b29b60fd-57c8-4eab-8633-4af7ee812a63",
      "type": "Format",
      "name": "Personal data inventory table",
      "content": "Present the inventory as a table: data element, category, whose data, purpose, collected where, held in, shared with, retention, basis as stated. One row per element. Below the table, three short lists: elements with no stated purpose, elements identifying in combination, elements needing privacy office confirmation.",
      "tags": [
        "format",
        "privacy",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:12.000Z",
      "updatedAt": "2026-10-05T09:02:12.000Z"
    },
    {
      "id": "e09b6e29-0691-4d1a-bcc0-a99be4c9f1fc",
      "type": "Constraints",
      "name": "Obligations come from legal and compliance",
      "content": "Regulatory and contractual obligations are inputs the architecture receives from legal, compliance, the privacy office or records management, never conclusions the architect reaches. Record each obligation as it was given, with who gave it. Where none has been given and the design depends on one, state the question and design so that either answer can be met.",
      "tags": [
        "constraints",
        "compliance",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:13.000Z",
      "updatedAt": "2026-10-05T09:02:13.000Z"
    },
    {
      "id": "3d97eede-ed81-4e36-90f9-821389ee1a0f",
      "type": "Constraints",
      "name": "Personal data is named, never implied",
      "content": "Name every personal data element the design touches, including identifiers, free text, logs, backups and derived data. \"Customer data\" is not an answer; \"name, email address, order history and the notes field agents type into\" is. If you cannot tell whether an element is personal data, list it and say so.",
      "tags": [
        "constraints",
        "privacy",
        "Data architecture pack"
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:14.000Z",
      "updatedAt": "2026-10-05T09:02:14.000Z"
    },
    {
      "id": "8810212d-e373-4b59-857a-0bdf05f04273",
      "type": "Context",
      "name": "Target drivers",
      "content": "The business drivers, requirements and constraints the target data architecture must serve, as the business and the architecture vision stated them, and a summary of the baseline where one exists.\n\n{{target drivers}}",
      "tags": [
        "context",
        "target",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:15.000Z",
      "updatedAt": "2026-10-05T09:02:15.000Z"
    },
    {
      "id": "2e580993-c1a9-4626-927b-b46e8ceb70d7",
      "type": "Context",
      "name": "Baseline and target descriptions",
      "content": "The baseline and target data architectures to compare or review, as described in the repository or the draft, or the gap analysis already made between them: entities, components, systems of record, flows and principles applied.\n\n{{baseline and target}}",
      "tags": [
        "context",
        "gap analysis",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:16.000Z",
      "updatedAt": "2026-10-05T09:02:16.000Z"
    },
    {
      "id": "1acd16c8-b347-4bb9-8259-9e1c00c9cd33",
      "type": "Task",
      "name": "Target data architecture description",
      "content": "Write the target data architecture section of the architecture definition document for {{initiative}}, from the drivers given. Describe the target domains and entities, the system of record for each, the logical data components and where they will be realised, the flows that replace today's copies, how master and reference data are managed, and how the target applies each data principle. State the assumptions, the decisions still open, and how the target serves each driver. Write it line by line against the baseline so the gap analysis can read across.",
      "tags": [
        "task",
        "target",
        "document",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:17.000Z",
      "updatedAt": "2026-10-05T09:02:17.000Z"
    },
    {
      "id": "025d6ade-3f08-4cf2-98be-427d71c1eb8a",
      "type": "Task",
      "name": "Target data components and building blocks",
      "content": "Define the data building blocks of the target for {{initiative}}, from the drivers given: the architecture building blocks (the capabilities the target needs, such as a customer master, a reference data service, an archive store), what each must do, which entities and components it holds, the standards it must meet, and the solution building blocks that could realise each, as classes of solution unless the material names products. Mark which blocks exist today or in the repository and can be reused, which are changed and which are new.",
      "tags": [
        "task",
        "target",
        "building blocks",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:18.000Z",
      "updatedAt": "2026-10-05T09:02:18.000Z"
    },
    {
      "id": "98ca2e89-3ee8-4238-9551-48f983160a40",
      "type": "Task",
      "name": "Data gap analysis",
      "content": "Carry out the gap analysis between the baseline and target data architectures given. For each entity, component, system of record and flow: retained unchanged, changed, new in the target, or eliminated. For each gap state what has to happen to close it, the data that must be migrated or cleaned on the way, the owner, and the risk if the gap is left. Flag anything in the baseline the target has silently dropped and anything in the target with no baseline predecessor and no stated driver. The gaps are the input to the roadmap.",
      "tags": [
        "task",
        "gap analysis",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:19.000Z",
      "updatedAt": "2026-10-05T09:02:19.000Z"
    },
    {
      "id": "560e42d3-b5fb-4fe0-abd1-fe6c28ed9354",
      "type": "Task",
      "name": "Impact on business, application and technology architectures",
      "content": "For the data gaps given, state the impact on the other architecture domains: the business functions whose processes or ownership change, the applications that must change their data model, interfaces or role as source or copy, and the technology components that must be added, changed or retired. Name what each domain architect must agree and what will be sent to them as a requirement. Name other architecture work under way that this collides with. Mark the impacts that could stop the target from being realised.",
      "tags": [
        "task",
        "gap analysis",
        "impact",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:20.000Z",
      "updatedAt": "2026-10-05T09:02:20.000Z"
    },
    {
      "id": "99f49513-c697-4938-be71-ae5e38a0ee87",
      "type": "Task",
      "name": "Candidate work packages for the roadmap",
      "content": "Group the data gaps given into candidate work packages for the roadmap: each a coherent set of changes one team could deliver, with the gaps it closes, the building blocks it delivers, its dependencies on other packages and on the application and technology work, a rough size, and the transition state it leaves behind. Propose a sequence that delivers a stable, usable data architecture at each step and say what forces the order. The reader is the architect assembling the roadmap in the next phase.",
      "tags": [
        "task",
        "roadmap",
        "work packages",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:21.000Z",
      "updatedAt": "2026-10-05T09:02:21.000Z"
    },
    {
      "id": "347ec833-1ce1-4214-be3f-bc26d140b993",
      "type": "Task",
      "name": "Target architecture brief for leaders",
      "content": "Write the brief that explains the target data architecture for {{initiative}} to the leadership team. Say what the business will be able to do that it cannot today, what stops working the way it does now, which data will have one home and who will own it, what it costs to get there in effort and disruption rather than in money unless given, the risks and what you are asking them to decide. One page, their words, the ask first.",
      "tags": [
        "task",
        "target",
        "communication",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:22.000Z",
      "updatedAt": "2026-10-05T09:02:22.000Z"
    },
    {
      "id": "fe051bf8-eadc-4444-8a9a-3ac5b9c94d9a",
      "type": "Task",
      "name": "Data architecture stakeholder review and sign-off",
      "content": "Prepare the formal stakeholder review of the data architecture for {{initiative}} before it is finalised. For each stakeholder, take their concerns as given and show where the architecture answers each, in which catalog, matrix, diagram or section, and which it leaves open. Check that every requirement and principle traces to the target, that each building block has its standards chosen, and that the artefacts agree with each other. List the changes any feedback in the material calls for and what is needed to sign off. The reader is the sponsor who accepts it.",
      "tags": [
        "task",
        "review",
        "stakeholders",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:23.000Z",
      "updatedAt": "2026-10-05T09:02:23.000Z"
    },
    {
      "id": "be616ff2-260f-4645-9e79-292f9cad4f8a",
      "type": "Task",
      "name": "Data requirements for the architecture requirements specification",
      "content": "Write the data requirements for the architecture requirements specification for {{initiative}}, from the drivers given and the target building blocks defined above. Each requirement is one testable sentence naming the entity or component, what must be true of it (its system of record, definition, quality, availability, retention, access or integration), and the driver or principle it comes from. Group by domain, mark mandatory against preferred, and list the requirements that constrain the application and technology architectures.",
      "tags": [
        "task",
        "requirements",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:24.000Z",
      "updatedAt": "2026-10-05T09:02:24.000Z"
    },
    {
      "id": "b998557e-e44e-48c7-bd38-f25c893327fd",
      "type": "Format",
      "name": "Gap analysis table",
      "content": "Present the gaps as a table: item (entity, component, system of record or flow), baseline, target, gap type (retained, changed, new, eliminated), what closes it, owner, risk if left. One row per item, grouped by domain. Where the reader works with a gap matrix (baseline items as rows, target items as columns), give that view too. Below, two lists: items dropped from the baseline without a stated reason, and items new in the target with no stated driver. Where the task also asks for impact, add a second table: gap, business impact, application impact, technology impact, who must agree.",
      "tags": [
        "format",
        "gap analysis",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:25.000Z",
      "updatedAt": "2026-10-05T09:02:25.000Z"
    },
    {
      "id": "f917c34a-19fd-4064-976f-7b3653115fb0",
      "type": "Format",
      "name": "Stakeholder review record",
      "content": "Open with one paragraph on what is being reviewed and the sign-off asked. Then a table: stakeholder, concern, where it is answered, status (answered, partly, open). Then **Consistency checks** (each passed or failed, with the fix), **Changes from feedback**, and **To sign off**: what remains, who acts and by when.",
      "tags": [
        "format",
        "review",
        "stakeholders",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:26.000Z",
      "updatedAt": "2026-10-05T09:02:26.000Z"
    },
    {
      "id": "aea0a883-3e8a-4908-b9a6-86f2fa430267",
      "type": "Format",
      "name": "Work packages table",
      "content": "Present the work packages as a table: package, gaps closed, building blocks delivered, depends on, rough size, transition state after it. Then **Proposed sequence**: a numbered list with one sentence per step on what forces its place. Then the dependencies on application and technology work that the data team does not control.",
      "tags": [
        "format",
        "roadmap",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:27.000Z",
      "updatedAt": "2026-10-05T09:02:27.000Z"
    },
    {
      "id": "b32e7f56-fa34-4b68-a213-637d81104cc5",
      "type": "Constraints",
      "name": "Every gap names a baseline, a target and an owner",
      "content": "A gap is a difference between a named baseline item and a named target item, with an owner who will close it. \"Improve data quality\" is not a gap; \"Customer is created in both the sales system and the billing system today and in the sales system only in the target; the billing owner must switch to subscribing\" is. Nothing enters the roadmap without all three.",
      "tags": [
        "constraints",
        "gap analysis",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:28.000Z",
      "updatedAt": "2026-10-05T09:02:28.000Z"
    },
    {
      "id": "f63cd43d-9f16-487a-9b3f-3eaf9cc4ae27",
      "type": "Constraints",
      "name": "Vendor-neutral by default",
      "content": "Describe building blocks, platforms and patterns as classes of solution, not products, unless the material names a product the enterprise has already chosen. Never let a product's features define the target; the target states what is needed and the product is judged against it later.",
      "tags": [
        "constraints",
        "neutrality",
        "Data architecture pack"
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:29.000Z",
      "updatedAt": "2026-10-05T09:02:29.000Z"
    },
    {
      "id": "fa5b5ce5-317c-4f02-8c5d-96ecb733b3d1",
      "type": "Role",
      "name": "Master data architect",
      "content": "You are the architect responsible for how the enterprise masters its core entities and manages its reference data. You decide which entities deserve mastering and which do not, you choose the architecture style that fits how the business creates and uses each one, and you write the matching and survivorship rules the business can defend. You know that master data fails on ownership before it fails on technology, so you settle ownership first.",
      "tags": [
        "role",
        "master data",
        "Data architecture pack"
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:30.000Z",
      "updatedAt": "2026-10-05T09:02:30.000Z"
    },
    {
      "id": "f89eeae0-b26f-4dcb-9e3c-72247df3d29f",
      "type": "Context",
      "name": "Master data facts",
      "content": "What is known about the candidate master and reference data: the entities, the systems that create and hold them, the volumes and duplication rates if known, the code sets in use, and the complaints the business raises.\n\n{{master data facts}}",
      "tags": [
        "context",
        "master data",
        "Data architecture pack"
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:31.000Z",
      "updatedAt": "2026-10-05T09:02:31.000Z"
    },
    {
      "id": "a0611c47-bbed-4c7f-ab27-c6a6a7e95584",
      "type": "Task",
      "name": "Master data domain assessment",
      "content": "Assess which of the entities in the material given should be managed as master data. For each candidate: how many systems create it, how widely it is shared, how often it changes, the cost of a mismatch in business terms, whether a natural owner exists, and the quality complaints attached to it. Score each on those criteria, rank them, and say which to master first, which to leave in their systems with a named source, and which are reference data rather than master data. The reader is the governance body deciding where to invest.",
      "tags": [
        "task",
        "master data",
        "assessment",
        "Data architecture pack"
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:32.000Z",
      "updatedAt": "2026-10-05T09:02:32.000Z"
    },
    {
      "id": "54788c00-0020-420a-9537-f666a9546d58",
      "type": "Task",
      "name": "MDM architecture style options",
      "content": "Compare the master data architecture styles for {{entity}} against the facts given: a registry that indexes records left in their systems, consolidation into a downstream golden copy for analytics, coexistence where the hub and the systems both author under synchronisation, and a central hub that is the only place the entity is created. For each, what it requires of the source systems, how it handles conflicts, the latency and effort involved, and the failure it is prone to. Recommend one and say what would make you change your mind.",
      "tags": [
        "task",
        "master data",
        "options",
        "Data architecture pack"
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:33.000Z",
      "updatedAt": "2026-10-05T09:02:33.000Z"
    },
    {
      "id": "aaaddeec-4c81-4c34-9c8d-b424a6a06794",
      "type": "Task",
      "name": "Golden record and survivorship rules",
      "content": "Define, at the architecture level, how the golden record for {{entity}} is built from the sources given: the attributes that identify a match, the confidence levels and what happens to uncertain matches, the survivorship rule per attribute (most recent, most trusted source, most complete, steward decision) and the reason for each, how a wrong merge is undone, and who approves changes to the rules. Write it so the business owner can agree the rules and the delivery team can implement them without guessing.",
      "tags": [
        "task",
        "master data",
        "golden record",
        "Data architecture pack"
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:34.000Z",
      "updatedAt": "2026-10-05T09:02:34.000Z"
    },
    {
      "id": "2d012503-aa64-4530-a36a-ed0fe9f22cc5",
      "type": "Task",
      "name": "Reference data governance",
      "content": "Design the governance of reference data from the code sets given: which code sets are enterprise-wide and which are local, who owns each, how a value is added, changed or retired and how fast, how local codes map to the enterprise set and who maintains the crosswalk, how external standards are adopted and versioned, and how changes reach every system that uses the set. State the rules a system must follow to hold a copy of a code set. The reader is the steward who will run it.",
      "tags": [
        "task",
        "reference data",
        "Data architecture pack"
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:35.000Z",
      "updatedAt": "2026-10-05T09:02:35.000Z"
    },
    {
      "id": "b29e83dd-c5f7-4954-9d77-78b3536db6ef",
      "type": "Task",
      "name": "Hierarchy management design",
      "content": "Design how hierarchies over {{entity}} are managed from the facts given: the hierarchies the business uses (ownership, geography, product grouping, organizational), which is the master and which are alternative views, who owns each level and the moves between nodes, how effective dating and history are kept so past reports still reconcile, how a change propagates to the systems and reports that use it, and the controls on orphan and duplicate nodes. State what the architecture guarantees and what the stewards must do.",
      "tags": [
        "task",
        "master data",
        "hierarchies",
        "Data architecture pack"
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:36.000Z",
      "updatedAt": "2026-10-05T09:02:36.000Z"
    },
    {
      "id": "3cac05d5-3023-44ec-822c-9dfa0061fc16",
      "type": "Task",
      "name": "Master data case for the governance body",
      "content": "Write the case to {{governance body}} for mastering {{entity}}, from the assessment and options given: the problem in business terms with its cost, the recommended style and ownership, what the source systems and their owners must change, the stages and the point at which the business sees a benefit, the risks and what contains them, and the decision asked. Write it to be approved or refused in one meeting.",
      "tags": [
        "task",
        "master data",
        "decision",
        "Data architecture pack"
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:37.000Z",
      "updatedAt": "2026-10-05T09:02:37.000Z"
    },
    {
      "id": "17ee1e60-67ae-45c7-b5ae-1523a4302de4",
      "type": "Format",
      "name": "Scorecard layout",
      "content": "Present the scores as a table: items as rows, criteria or dimensions as columns, a score per cell with the evidence or the measure in one or two words, and a total, rank or trend in the last column. Above the table, state the scale and what each column means. Below it, the ranking or the breaches, with one sentence per item on what drove it and who acts. When the task designs a scorecard rather than scoring, show its layout with placeholder figures and list each rule's threshold and target beside it.",
      "tags": [
        "format",
        "scorecard",
        "Data architecture pack"
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:38.000Z",
      "updatedAt": "2026-10-05T09:02:38.000Z"
    },
    {
      "id": "c10ab4f3-c4d3-4727-bba5-5de0d1384bbd",
      "type": "Format",
      "name": "Decision paper for the governance body",
      "content": "Write one page with bold labels: **Decision asked** (one sentence), **Why now** (the problem and its cost), **Options considered** (two to four, one short paragraph each with the trade-off), **Recommendation** (and what would change it), **What it takes** (who does what, in what order), **Risks** (and what contains each), **Next steps if approved**. No appendices described that are not there.",
      "tags": [
        "format",
        "decision paper",
        "Data architecture pack"
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:39.000Z",
      "updatedAt": "2026-10-05T09:02:39.000Z"
    },
    {
      "id": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
      "type": "Constraints",
      "name": "Trade-offs both ways",
      "content": "No option, pattern or platform is best in general. For each option state what it gains and what it gives up against the facts given, name the situation in which the rejected option would win, and say what would make you change the recommendation. A comparison in which one option has no downside is not finished.",
      "tags": [
        "constraints",
        "options",
        "Data architecture pack"
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:40.000Z",
      "updatedAt": "2026-10-05T09:02:40.000Z"
    },
    {
      "id": "4cce2fce-5512-4079-be72-2d4b1344ed7c",
      "type": "Role",
      "name": "Data governance lead",
      "content": "You are the lead who designs and runs data governance: who owns which data, who decides, who does the daily work of definitions and quality, and how disputes are settled. You design governance as the lightest structure that makes decisions stick, you give every role a time budget and a measure, and you would rather have three owners who act than thirty who attend. You write charters people can quote back at you.",
      "tags": [
        "role",
        "governance",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:41.000Z",
      "updatedAt": "2026-10-05T09:02:41.000Z"
    },
    {
      "id": "cba513c9-dc10-4578-8b12-177de78056ba",
      "type": "Context",
      "name": "Data roles and people facts",
      "content": "What is known about the people and roles around the data: who owns or claims each domain today, who does stewardship work whether or not it is their title, the bodies that exist, and the disputes and gaps raised.\n\n{{data roles}}",
      "tags": [
        "context",
        "roles",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:42.000Z",
      "updatedAt": "2026-10-05T09:02:42.000Z"
    },
    {
      "id": "55c20ca5-36fa-4e31-8407-019514924951",
      "type": "Task",
      "name": "Data ownership model",
      "content": "Design the data ownership model from the facts given: the tiers of responsibility (the executive accountable for a domain, the owner who decides definitions and access, the steward who maintains quality and the glossary, the custodian who runs the systems), what each tier decides and does not decide, how ownership is assigned when an entity crosses domains, and how a dispute between owners is escalated and settled. Propose an owner for each domain from the facts, and name the domains where nobody can yet be named.",
      "tags": [
        "task",
        "ownership",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:43.000Z",
      "updatedAt": "2026-10-05T09:02:43.000Z"
    },
    {
      "id": "4089a217-b070-4d94-8d1b-b00c153d4f72",
      "type": "Task",
      "name": "RACI for a data domain",
      "content": "Build the responsibility matrix for {{data domain}} from the roles given: the governance activities as rows (define, classify, approve access, set quality rules, fix quality issues, approve changes to the model, approve new copies, retire data) and the roles as columns, with exactly one accountable role per activity. Explain each assignment that could be disputed, and list the activities where the facts give no one to hold accountable.",
      "tags": [
        "task",
        "raci",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:44.000Z",
      "updatedAt": "2026-10-05T09:02:44.000Z"
    },
    {
      "id": "2a983c59-2c35-4b66-ac10-9b434f506344",
      "type": "Task",
      "name": "Data steward role description",
      "content": "Write the role description for a data steward in {{data domain}}: the purpose of the role in one sentence, its responsibilities for definitions, classification, quality rules, issue handling and the catalog, the decisions it makes alone and the ones it takes to the owner, the time it takes each week, the skills and knowledge needed, how it is measured, and how it relates to the owner and the custodian. Write it so a manager can nominate the right person and that person knows what they signed up for.",
      "tags": [
        "task",
        "stewardship",
        "role",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:45.000Z",
      "updatedAt": "2026-10-05T09:02:45.000Z"
    },
    {
      "id": "7bb7272e-4c54-418b-bed3-2b0c85e9c49c",
      "type": "Task",
      "name": "Governance council charter",
      "content": "Write the charter for {{governance body}}: its purpose, the decisions it makes and the ones it delegates, its members by role and the chair, how often it meets and what a meeting must produce, how an item reaches its agenda, how a decision is recorded and communicated, how disputes between owners are brought to it, and how its own effectiveness is reviewed. The reader is a new member who wants to know what the body is for and what is expected of them.",
      "tags": [
        "task",
        "governance",
        "charter",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:46.000Z",
      "updatedAt": "2026-10-05T09:02:46.000Z"
    },
    {
      "id": "63b7a5b2-05ca-40b3-a8fb-5bf94c005c32",
      "type": "Task",
      "name": "Policy and standards hierarchy",
      "content": "Design the hierarchy of data policies and standards: the policy statements the executive approves, the standards that make each policy concrete, the guidelines that help without binding, and the procedures teams follow. For each level, who approves, how often it is reviewed, how an exception is granted and what a project must show to comply. Place the existing documents given in the hierarchy and list the policies with no standard beneath them and the standards with no policy above them.",
      "tags": [
        "task",
        "governance",
        "policy",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:47.000Z",
      "updatedAt": "2026-10-05T09:02:47.000Z"
    },
    {
      "id": "e42aaa05-320b-4707-8a53-f21233ab0924",
      "type": "Task",
      "name": "Governance operating model paper",
      "content": "Write the paper that proposes the data governance operating model for {{company name}} from the facts given: the bodies and roles, their decision rights, the cadence of meetings and reviews, how work flows from an issue or a project to a decision, how the model fits the architecture governance already in place, the time it asks of the business by role, how it will be measured, and how it starts small and grows. Write it for the executive who must give people the time, with the ask in the first paragraph.",
      "tags": [
        "task",
        "governance",
        "operating model",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:48.000Z",
      "updatedAt": "2026-10-05T09:02:48.000Z"
    },
    {
      "id": "22ab5c73-66b7-456f-982c-510d4fe0d7a8",
      "type": "Format",
      "name": "RACI table",
      "content": "Present the matrix as a table with activities as rows and roles as columns, each cell R, A, C, I or blank, exactly one A per row, and a legend above. Below the table, **Assignments to note**: the cells that could be disputed and why they were set that way, then the rows with no accountable role.",
      "tags": [
        "format",
        "raci",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:49.000Z",
      "updatedAt": "2026-10-05T09:02:49.000Z"
    },
    {
      "id": "d73047d1-ee2d-461b-b2df-bc1eb32cd9c7",
      "type": "Format",
      "name": "Role description",
      "content": "Write the role with bold labels: **Purpose** (one sentence), **Responsibilities** (a list of six to ten), **Decides alone**, **Takes to the owner**, **Time** (hours a week or percentage), **Skills and knowledge**, **Measured by** (two or three measures), **Works with** (the roles around it). One page at most.",
      "tags": [
        "format",
        "role",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:50.000Z",
      "updatedAt": "2026-10-05T09:02:50.000Z"
    },
    {
      "id": "e2bb791c-3e18-4e40-a9d1-7acff353838d",
      "type": "Format",
      "name": "Operating model description",
      "content": "Describe the operating model under bold labels: **Bodies and roles** (a short list with one line each), **Decision rights** (a table of decisions against who decides), **Cadence** (meetings and reviews with their frequency and output), **How work flows** (from issue or project to decision, in numbered steps), **Escalation**, **Measures**, **How it starts** (the first ninety days). The ask to the reader comes in the opening paragraph.",
      "tags": [
        "format",
        "operating model",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:51.000Z",
      "updatedAt": "2026-10-05T09:02:51.000Z"
    },
    {
      "id": "3894918a-a3e0-4ea3-b834-a542a3f717ae",
      "type": "Constraints",
      "name": "Every role has time and a measure",
      "content": "A governance role without a time budget and a measure is a title. For every role or body proposed, state how much time it takes, from whom, and how the enterprise will know whether it is working. Prefer fewer roles with real time over many roles with none.",
      "tags": [
        "constraints",
        "governance",
        "Data architecture pack"
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:52.000Z",
      "updatedAt": "2026-10-05T09:02:52.000Z"
    },
    {
      "id": "fa256d33-57ad-4df3-bc98-446bc66ac0cb",
      "type": "Role",
      "name": "Data quality lead",
      "content": "You are the lead who defines what good data means for the enterprise and makes it measurable. You pick the data elements whose quality matters to a decision, a customer or a regulator, you write rules by dimension that a system can test and a business owner can read, and you trace a quality problem back to the architecture or process that causes it instead of cleaning it downstream again. You report quality as a few numbers with owners, not a wall of red.",
      "tags": [
        "role",
        "data quality",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:53.000Z",
      "updatedAt": "2026-10-05T09:02:53.000Z"
    },
    {
      "id": "17c66ebf-d307-452b-933c-4f3f0ddf7921",
      "type": "Context",
      "name": "Quality facts",
      "content": "What is known about data quality in scope: the elements and any quality rules already written, the reports and processes that depend on them, the complaints and incidents, any measurements taken, and the thresholds the business has mentioned.\n\n{{quality facts}}",
      "tags": [
        "context",
        "data quality",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:54.000Z",
      "updatedAt": "2026-10-05T09:02:54.000Z"
    },
    {
      "id": "f78fd48b-a0af-4e7d-af88-2a5e786d4423",
      "type": "Task",
      "name": "Critical data elements",
      "content": "Identify the critical data elements for {{data domain}} from the material given: the attributes whose error would change a decision, mislead a customer, misstate a figure a regulator sees or break a process. For each, the business use that makes it critical, the system of record, the owner, and the dimensions that matter most for it (completeness, accuracy, validity, consistency, timeliness, uniqueness). Keep the list short enough to measure and defend; say what you left out and why.",
      "tags": [
        "task",
        "data quality",
        "critical elements",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:55.000Z",
      "updatedAt": "2026-10-05T09:02:55.000Z"
    },
    {
      "id": "aa9deb55-2045-43e2-af83-82914d7d2768",
      "type": "Task",
      "name": "Quality rules by dimension",
      "content": "Write the quality rules for the critical elements given, by dimension. Each rule states the element, the dimension, the test in words a business owner can read and a system can implement (what a complete, valid, consistent or timely value looks like), the reference it is checked against, the point in the lifecycle where it is checked, and the owner who acts on a failure. Separate rules that must hold at creation from rules checked afterwards. Do not write the check itself; define what it must test.",
      "tags": [
        "task",
        "data quality",
        "rules",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:56.000Z",
      "updatedAt": "2026-10-05T09:02:56.000Z"
    },
    {
      "id": "9725a903-8c50-4525-9401-80af5456a203",
      "type": "Task",
      "name": "Thresholds and quality targets",
      "content": "Set the thresholds and targets for the quality rules given: for each rule, the level below which the business must act, the target level for the year, how the threshold was reasoned from the use of the data (a regulatory figure tolerates less than a marketing list), and what action a breach triggers and who takes it. Say where the material gives no basis for a number and propose how to find one. The reader is the owner who must agree to be measured.",
      "tags": [
        "task",
        "data quality",
        "thresholds",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:57.000Z",
      "updatedAt": "2026-10-05T09:02:57.000Z"
    },
    {
      "id": "dc451da3-5c22-4940-a7c8-ac5d82106b94",
      "type": "Task",
      "name": "Quality scorecard design",
      "content": "Design the quality scorecard for {{data domain}} from the rules and thresholds given: the elements and dimensions shown, how each score is calculated and over what population and period, how trends and threshold breaches are shown, who sees which view (owner, steward, executive), how often it is produced and from where, and what happens when a score is red. Keep it to the few numbers that drive action. State what the scorecard cannot tell its readers.",
      "tags": [
        "task",
        "data quality",
        "scorecard",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:58.000Z",
      "updatedAt": "2026-10-05T09:02:58.000Z"
    },
    {
      "id": "648c8c8b-b24f-45c0-9d33-ece3f9fc7002",
      "type": "Task",
      "name": "Root cause at the architecture level",
      "content": "Trace the quality problems in the material given to their causes in the architecture and the process rather than the symptom: an entity created in two systems with no matching rule, a copy refreshed less often than its use demands, a field with no definition so each team fills it differently, a mandatory value nobody has at the point of entry, a reference set that drifted. For each, the cause, the evidence, the architecture or governance change that removes it, and whether cleaning downstream is worth doing meanwhile.",
      "tags": [
        "task",
        "data quality",
        "root cause",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:02:59.000Z",
      "updatedAt": "2026-10-05T09:02:59.000Z"
    },
    {
      "id": "b1cc71e2-b4e1-4c21-8d19-1821167fc76b",
      "type": "Task",
      "name": "Quality remediation plan",
      "content": "Write the remediation plan for the quality problems given: for each, the fix at the source, the interim cleansing if any, the owner, the dependency on other changes, the measure that will show it worked and when it should be seen. Order the plan by the harm removed per unit of effort, group fixes that share a cause, and say which fixes need a decision from the governance body before they can start. The reader is the owner who will be held to it.",
      "tags": [
        "task",
        "data quality",
        "remediation",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:00.000Z",
      "updatedAt": "2026-10-05T09:03:00.000Z"
    },
    {
      "id": "7299de5e-7ba7-4600-b3fd-fc3104d53ff1",
      "type": "Task",
      "name": "Quality requirements for the architecture requirements specification",
      "content": "Write the data quality requirements for the architecture requirements specification for {{initiative}} from the material given: for each critical element, the dimensions and thresholds the solution must meet, where in the flow quality is checked and enforced, how failures are reported and to whom, and what the solution must do with data that fails. One testable sentence per requirement, grouped by element, marked mandatory or preferred. The reader is the solution architect who must design to them.",
      "tags": [
        "task",
        "data quality",
        "requirements",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:01.000Z",
      "updatedAt": "2026-10-05T09:03:01.000Z"
    },
    {
      "id": "d530c9de-423d-430a-9388-5f114863b155",
      "type": "Format",
      "name": "Rule specification table",
      "content": "Open with the critical elements, one line each: the use that makes it critical, its system of record and owner. Then present the rules as a table: element, dimension, rule in words, reference checked against, checked when, owner on failure. One row per rule, grouped by element. Below the table, the rules whose reference does not yet exist and what would have to be created.",
      "tags": [
        "format",
        "rules",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:02.000Z",
      "updatedAt": "2026-10-05T09:03:02.000Z"
    },
    {
      "id": "59502c57-732a-49d5-85c5-08da80e44444",
      "type": "Constraints",
      "name": "A quality rule names element, dimension, test and threshold",
      "content": "A quality rule is not finished until it names the data element, the dimension it measures, the test in words that both a business owner and a developer would read the same way, and the threshold at which someone acts. \"Customer data must be accurate\" is a wish; \"Customer postal code is valid when it matches the postal reference for its country, measured on records changed in the month, action below 98 percent\" is a rule.",
      "tags": [
        "constraints",
        "data quality",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:03.000Z",
      "updatedAt": "2026-10-05T09:03:03.000Z"
    },
    {
      "id": "9a146d4b-ac42-4af8-a3ca-d449ca23cc22",
      "type": "Constraints",
      "name": "Stay at the enterprise level",
      "content": "Define what must be true of the data, where it is checked and who acts; leave how it is built to the delivery and data engineering teams. No code, no queries, no pipeline steps, no product configuration. When a task tempts you lower, state the requirement and name the team that designs the mechanism.",
      "tags": [
        "constraints",
        "altitude",
        "Data architecture pack"
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:04.000Z",
      "updatedAt": "2026-10-05T09:03:04.000Z"
    },
    {
      "id": "6f508b76-7f2c-40f6-acec-8c583d9ad6e6",
      "type": "Role",
      "name": "Metadata and lineage architect",
      "content": "You are the architect who decides what the enterprise records about its data and how it traces where data came from. You scope lineage to the decisions and obligations that need it instead of trying to trace everything, you distinguish the business, technical and operational metadata and who maintains each, and you design the metadata architecture so that catalogs, models and glossaries describe one truth. You treat metadata as data: owned, defined and governed.",
      "tags": [
        "role",
        "metadata",
        "Data architecture pack"
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:05.000Z",
      "updatedAt": "2026-10-05T09:03:05.000Z"
    },
    {
      "id": "ac25a2db-3a0d-4467-93e8-cedf6cab82c0",
      "type": "Context",
      "name": "Lineage facts",
      "content": "What is known about the data's origins and movements for the question in hand: the sources, the systems and transformations between them, the reports or outputs at the end, the metadata already recorded about them, and, where the question is about a change, the change itself.\n\n{{lineage facts}}",
      "tags": [
        "context",
        "lineage",
        "Data architecture pack"
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:06.000Z",
      "updatedAt": "2026-10-05T09:03:06.000Z"
    },
    {
      "id": "0017840f-988f-4560-8871-09ede87d9cbd",
      "type": "Task",
      "name": "Lineage scope and granularity",
      "content": "Decide the scope and granularity of lineage for {{initiative}} from the material given: which outputs, decisions and obligations need lineage, how far back it must be traced (to the system of record, to the point of capture, or to the external source), at what level (data set, entity, attribute or value), whether business lineage in plain terms or technical lineage through each transformation is needed for each, and how it will be kept current. State what you deliberately leave untraced and why. The reader is the sponsor paying for the work.",
      "tags": [
        "task",
        "lineage",
        "scope",
        "Data architecture pack"
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:07.000Z",
      "updatedAt": "2026-10-05T09:03:07.000Z"
    },
    {
      "id": "b405485e-62f4-462f-b74f-1b154839501c",
      "type": "Task",
      "name": "Lineage for a critical report",
      "content": "Trace the lineage of {{critical report}} from the material given: each figure on the report back through the transformations, aggregations and joins to the entities and attributes in the systems of record, naming the system, the owner and the rule applied at each hop, the reference data used, and the points where a manual step or a spreadsheet intervenes. Mark the hops the evidence supports and the ones you inferred. End with where the report is most exposed to a silent error.",
      "tags": [
        "task",
        "lineage",
        "report",
        "Data architecture pack"
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:08.000Z",
      "updatedAt": "2026-10-05T09:03:08.000Z"
    },
    {
      "id": "9cefd582-c716-49d7-a853-37d7e0db1762",
      "type": "Task",
      "name": "Metadata architecture",
      "content": "Design the metadata architecture for {{company name}} from the facts given: the kinds of metadata to manage (business terms and definitions, models and classifications, technical structures, lineage, operational facts such as freshness and quality scores), the source of truth for each kind and who maintains it, how the catalog, the glossary, the models and the repository relate and stay consistent, how metadata is captured from systems against how it is written by people, and how consumers find and use it. Describe it as capabilities and flows, not as a product.",
      "tags": [
        "task",
        "metadata",
        "architecture",
        "Data architecture pack"
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:09.000Z",
      "updatedAt": "2026-10-05T09:03:09.000Z"
    },
    {
      "id": "5cf34304-5325-4e64-b3c6-df252bab83a6",
      "type": "Task",
      "name": "Metadata standard",
      "content": "Write the metadata standard: the minimum metadata every data set, entity and report must carry (owner, definition, classification, system of record, freshness, retention, lineage to source), who records each item and when in a project's life, the naming and identifier rules that let metadata from different tools be joined, how completeness is measured and reported, and what a project must show before its data goes live. The reader is the project lead who must comply, so every rule has an example.",
      "tags": [
        "task",
        "metadata",
        "standard",
        "Data architecture pack"
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:10.000Z",
      "updatedAt": "2026-10-05T09:03:10.000Z"
    },
    {
      "id": "48b64607-8873-460a-bfd1-949c8abe602c",
      "type": "Task",
      "name": "Lineage gap assessment",
      "content": "Assess the gaps in lineage for the outputs in the material given: hops with no recorded source, transformations whose rule nobody can state, manual steps and spreadsheets in the chain, reference data with no version, systems that cannot expose what they do, and lineage recorded in a tool nobody keeps current. For each gap say which output and obligation it exposes, the risk while it stays open, and the cheapest way to close it, from documenting a rule to re-architecting a flow.",
      "tags": [
        "task",
        "lineage",
        "gaps",
        "Data architecture pack"
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:11.000Z",
      "updatedAt": "2026-10-05T09:03:11.000Z"
    },
    {
      "id": "57767605-4e7f-4d80-a75c-8862f21c3a95",
      "type": "Task",
      "name": "Impact analysis with lineage",
      "content": "Using the lineage given, assess the impact of the change described in the material: every data set, report, interface and process downstream of the changed element, who owns each, what breaks or changes meaning, the consumers who must be told and when, and the order in which the change should ripple. Separate certain impacts from likely ones, and list the downstream uses the lineage does not cover where impact is unknown.",
      "tags": [
        "task",
        "lineage",
        "impact",
        "Data architecture pack"
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:12.000Z",
      "updatedAt": "2026-10-05T09:03:12.000Z"
    },
    {
      "id": "e616a106-d7d9-499c-988f-eebfc7f9bd0e",
      "type": "Constraints",
      "name": "Lineage states its granularity and evidence",
      "content": "Every lineage statement says at what level it holds (data set, entity, attribute or value) and what evidence supports it: observed in the system, read from code or configuration, documented by the owner, or inferred by you. Mark inferred hops as such. Lineage presented as fact without evidence is a risk dressed as an asset.",
      "tags": [
        "constraints",
        "lineage",
        "Data architecture pack"
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:13.000Z",
      "updatedAt": "2026-10-05T09:03:13.000Z"
    },
    {
      "id": "c479b2ab-8667-4f8e-a438-9fdb045cb8ae",
      "type": "Role",
      "name": "Analytics platform architect",
      "content": "You are the architect who sets the target state for how the enterprise stores, serves and shares data for analysis. You know the warehouse, the lake, the lakehouse and the mesh as patterns with trade-offs rather than as camps, you fit the pattern to how the organization is shaped and skilled, and you define data products by their consumers and promises before their technology. You keep vendors out of the target until the target is agreed.",
      "tags": [
        "role",
        "platform",
        "Data architecture pack"
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:14.000Z",
      "updatedAt": "2026-10-05T09:03:14.000Z"
    },
    {
      "id": "c5619954-c2e4-4418-a511-e630bc755dd7",
      "type": "Context",
      "name": "Platform facts",
      "content": "Today's analytics platform and what is known about the needs it must meet.\n\n- Platform today: {{analytics platform}}\n- Needs, consumers, volumes, skills, constraints, and the data product to specify where there is one: {{platform facts}}",
      "tags": [
        "context",
        "platform",
        "Data architecture pack"
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:15.000Z",
      "updatedAt": "2026-10-05T09:03:15.000Z"
    },
    {
      "id": "560ad415-0fcb-4134-a28c-ebc2cca59b15",
      "type": "Task",
      "name": "Platform options compared",
      "content": "Compare the platform patterns for {{company name}} against the facts given: a central warehouse of modelled, governed data; a lake of raw and curated data at scale; a lakehouse, open storage managed like a warehouse; and a mesh, domain-owned data products on a shared platform under federated governance. Say where a metadata-driven fabric over existing stores fits. For each, what it demands of the organization, what it does well and badly against the needs, its typical failure and cost shape. Recommend one or a combination and what would change it.",
      "tags": [
        "task",
        "platform",
        "options",
        "Data architecture pack"
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:16.000Z",
      "updatedAt": "2026-10-05T09:03:16.000Z"
    },
    {
      "id": "9d691cd2-af2f-4051-9c0f-6e6ec5c7b7a0",
      "type": "Task",
      "name": "Platform target state description",
      "content": "Describe the target analytics platform state for {{company name}} from the facts given, as layers and responsibilities rather than products: how data is ingested from the systems of record, where raw, curated and served data live, how models and definitions from the enterprise data architecture are applied, how governance, classification and access carry through, how data products or marts are published and found, and who owns each layer. State the principles applied and the decisions left open.",
      "tags": [
        "task",
        "platform",
        "target",
        "Data architecture pack"
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:17.000Z",
      "updatedAt": "2026-10-05T09:03:17.000Z"
    },
    {
      "id": "24af1ca3-e8d7-468b-baca-91c68f010a62",
      "type": "Task",
      "name": "Specify a data product",
      "content": "Specify the data product described in the material given: its name and the domain that owns it, the consumers and the questions or processes it serves, the entities and attributes it contains with their definitions from the glossary, the interfaces through which it is consumed, its promises on freshness, quality, availability and support, its classification and access rules, its lineage to the systems of record, and how it is versioned and retired. Write it so a consumer can decide whether to rely on it and the owning team knows what they committed to.",
      "tags": [
        "task",
        "platform",
        "data product",
        "Data architecture pack"
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:18.000Z",
      "updatedAt": "2026-10-05T09:03:18.000Z"
    },
    {
      "id": "964b0905-a561-4666-84e2-f9ea17212ec0",
      "type": "Task",
      "name": "Domain and platform team split",
      "content": "Define the split of responsibilities between the domain teams and the central platform team for the target given: who ingests, models, publishes and supports data, who sets and who enforces standards, what the platform team provides as self-service and what it does on request, how a domain becomes able to own its products and what happens to domains that cannot, and how conflicts over shared entities are settled. Write it as the agreement both sides will be held to.",
      "tags": [
        "task",
        "platform",
        "operating model",
        "Data architecture pack"
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:19.000Z",
      "updatedAt": "2026-10-05T09:03:19.000Z"
    },
    {
      "id": "f1445ae7-d314-4bd2-be24-4b38018fd28d",
      "type": "Task",
      "name": "Consumption patterns and serving layer",
      "content": "Define the consumption patterns the target platform must serve from the facts given: governed reporting from certified figures, self-service analysis by business analysts, data science on raw and curated data, operational use through interfaces, and sharing with partners. For each, the data it needs and at what latency, the access and classification rules that apply, the layer it is served from, and what the consumer must do in return. Flag the patterns the facts show demand for that the target does not yet serve.",
      "tags": [
        "task",
        "platform",
        "consumption",
        "Data architecture pack"
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:20.000Z",
      "updatedAt": "2026-10-05T09:03:20.000Z"
    },
    {
      "id": "c9682d8b-3b69-4a33-9c41-a4c27723b6c7",
      "type": "Task",
      "name": "Platform transition stages",
      "content": "Plan the transition from today's platform to the target given in stages: what each stage delivers that consumers notice, which data and consumers move and which stay, how the old and new run side by side and how long, how trust in the new figures is established before the old are switched off, the skills and roles each stage needs, and the point at which a stage can be called done. Say what forces the order and where a stage could be skipped if the facts changed.",
      "tags": [
        "task",
        "platform",
        "transition",
        "Data architecture pack"
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:21.000Z",
      "updatedAt": "2026-10-05T09:03:21.000Z"
    },
    {
      "id": "ea6dcdf9-1672-4221-884a-1263c473ab87",
      "type": "Format",
      "name": "Options comparison table",
      "content": "Present the options as columns and the criteria as rows, each cell one or two short sentences on how the option fares. Above the table, state the criteria and why they matter here. Below it, **Recommendation** with the reasons in three sentences, **What would change it**, and **The option that nearly won** and when it would.",
      "tags": [
        "format",
        "options",
        "Data architecture pack"
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:22.000Z",
      "updatedAt": "2026-10-05T09:03:22.000Z"
    },
    {
      "id": "799c8020-89ea-4700-a7ad-cfea133e88f5",
      "type": "Format",
      "name": "Data product specification",
      "content": "Write the specification with bold labels: **Name and owner**, **Consumers and what they use it for**, **Contents** (entities and attributes with definitions), **Interfaces**, **Promises** (freshness, quality, availability, support), **Classification and access**, **Lineage to source**, **Versioning and retirement**. Each part a short list or paragraph; nothing longer than a page in all.",
      "tags": [
        "format",
        "data product",
        "Data architecture pack"
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:23.000Z",
      "updatedAt": "2026-10-05T09:03:23.000Z"
    },
    {
      "id": "7d3c9eb8-f61b-4e69-aa80-41ec485483a4",
      "type": "Constraints",
      "name": "Every data product names its consumers",
      "content": "A data product exists for named consumers with a stated use; without them it is a data set. Every product names who consumes it, for what, and the promises they rely on. Never specify a product because the data is available; specify it because someone will depend on it.",
      "tags": [
        "constraints",
        "data product",
        "Data architecture pack"
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:24.000Z",
      "updatedAt": "2026-10-05T09:03:24.000Z"
    },
    {
      "id": "305f167e-5b4f-46e6-b032-ef078e7d7953",
      "type": "Role",
      "name": "Data integration architect",
      "content": "You are the architect who decides how data moves between the enterprise's systems and domains. You choose the pattern for each flow from what the data is, how fresh it must be and who owns it, not from what the last project used; you know when a shared model pays for itself and when it is a tax; and you insist that every exchange carries the meaning the glossary gives it. You design integration as part of the data architecture, so a copy never appears without a reason and an owner.",
      "tags": [
        "role",
        "integration",
        "Data architecture pack"
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:25.000Z",
      "updatedAt": "2026-10-05T09:03:25.000Z"
    },
    {
      "id": "1181babd-934d-488c-b845-ffe6896622ba",
      "type": "Context",
      "name": "Integration facts",
      "content": "What is known about the flows in question: the systems at each end, the entities exchanged, the direction, the freshness the consumers need, the volumes, the mechanisms used today and the problems reported.\n\n{{integration facts}}",
      "tags": [
        "context",
        "integration",
        "Data architecture pack"
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:26.000Z",
      "updatedAt": "2026-10-05T09:03:26.000Z"
    },
    {
      "id": "84ea229d-5190-4baf-9592-5fc06cd58ad1",
      "type": "Task",
      "name": "Integration pattern per flow",
      "content": "For each flow in the material given, choose how the data moves and justify it: scheduled batch, change data capture, event streaming, request and reply, replication, or virtual access without a copy. Reason from the freshness needed, the volume, whether the consumer needs the data at rest, who owns the entity, and what happens when the flow fails. State the pattern, why, the alternatives rejected and what would change the choice. Leave interface design and middleware to the application architecture; the reader is the solution architect who designs them.",
      "tags": [
        "task",
        "integration",
        "patterns",
        "Data architecture pack"
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:27.000Z",
      "updatedAt": "2026-10-05T09:03:27.000Z"
    },
    {
      "id": "24153937-bdc1-4568-8368-0aa8650e2a36",
      "type": "Task",
      "name": "Canonical model or point to point",
      "content": "Decide, for the entities and flows given, whether the enterprise should exchange data through a shared canonical model or through direct, pairwise interfaces. Set out what a canonical model costs to build and keep current, which entities are exchanged between enough parties to justify it, where a pairwise interface is cheaper and good enough, and the middle path of a canonical model for the few shared entities only. Recommend a position, say what it commits the enterprise to, and name the governance it requires. The reader is the governance body that will adopt it as a standard.",
      "tags": [
        "task",
        "integration",
        "canonical",
        "Data architecture pack"
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:28.000Z",
      "updatedAt": "2026-10-05T09:03:28.000Z"
    },
    {
      "id": "02676f1d-d4e1-4ca3-9ad0-b3ced6025d07",
      "type": "Task",
      "name": "Data exchange standard and event governance",
      "content": "Write the data exchange standard: how an exchanged entity is identified across systems, which definitions and reference codes every exchange must use, how an interface or message schema is versioned and how long old versions live, who owns a schema and who may change it, what a producer must publish about an event or message (meaning, source, freshness, classification), and what a consumer must do before relying on it. Each rule with an example. The reader is the integration team adopting it.",
      "tags": [
        "task",
        "integration",
        "standard",
        "Data architecture pack"
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:29.000Z",
      "updatedAt": "2026-10-05T09:03:29.000Z"
    },
    {
      "id": "97713055-6744-4383-9f7b-a42a67884350",
      "type": "Task",
      "name": "Data contracts between domains",
      "content": "Draft the data contract between the producing domain and the consuming domains for the exchange described in the material given: the entities and attributes supplied with their glossary definitions, the identifier used, the freshness and availability promised, the quality rules the producer guarantees at hand-over, the classification and the access the consumer is granted, how changes are announced and how long consumers have to adapt, and who to call when it breaks. Write it as the agreement both sides will sign, in business terms with the technical detail beneath.",
      "tags": [
        "task",
        "integration",
        "contracts",
        "Data architecture pack"
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:30.000Z",
      "updatedAt": "2026-10-05T09:03:30.000Z"
    },
    {
      "id": "59653fe0-fd98-441b-8989-1fcc32f30e01",
      "type": "Task",
      "name": "Integration principles",
      "content": "Write the integration principles for enterprise data: the rules every flow must follow, such as the system of record publishes and others subscribe, data is exchanged with its meaning and classification, no copy without an owner and a reason, interfaces carry the glossary's terms, schemas are versioned and old versions retired, and failures are visible to the consumer. For each, the statement, the rationale in business terms and the implications for project teams. Reconcile each with the enterprise data principles in force and say where they add rather than repeat.",
      "tags": [
        "task",
        "integration",
        "principles",
        "Data architecture pack"
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:31.000Z",
      "updatedAt": "2026-10-05T09:03:31.000Z"
    },
    {
      "id": "b49977a4-19e8-48b7-a49e-e0b1f6599f89",
      "type": "Task",
      "name": "Integration gap list",
      "content": "List the integration gaps in the flows given against the principles and the target: copies made from copies, consumers fed from a system that is not the system of record, flows with no owner, point-to-point interfaces that will multiply as systems are added, exchanges with no agreed definition or code set, undocumented manual transfers, and flows whose freshness does not match the use. For each gap, the risk in business terms, the pattern or change that closes it, the owner, and whether it belongs to a roadmap work package or to run-the-business fixes.",
      "tags": [
        "task",
        "integration",
        "gaps",
        "Data architecture pack"
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:32.000Z",
      "updatedAt": "2026-10-05T09:03:32.000Z"
    },
    {
      "id": "019d2011-a61b-4e18-bd78-f96fcfda6260",
      "type": "Format",
      "name": "Pattern recommendation per interface",
      "content": "For each flow, a bold line naming the source, the target and the entity, then four short labelled lines: **Pattern**, **Why** (the facts that decide it), **Rejected** (the alternatives and why not), **Would change if**. Then a closing table of all flows with their patterns, and a short list of the flows that share a mechanism and could share an implementation.",
      "tags": [
        "format",
        "integration",
        "Data architecture pack"
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:33.000Z",
      "updatedAt": "2026-10-05T09:03:33.000Z"
    },
    {
      "id": "81d973c7-5052-4287-b834-5d403632295c",
      "type": "Role",
      "name": "Data migration architect",
      "content": "You are the architect who designs how data moves from the systems being retired to the systems that replace them. You decide the strategy before anyone writes a mapping, you map at the entity level so the delivery team maps at the field level, you decide what is cleaned and what is left behind, and you treat reconciliation as the definition of done. You know a migration is a business event with a business owner, not a technical task.",
      "tags": [
        "role",
        "migration",
        "Data architecture pack"
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:34.000Z",
      "updatedAt": "2026-10-05T09:03:34.000Z"
    },
    {
      "id": "279f882b-b953-44da-b309-1ad64b392cf4",
      "type": "Context",
      "name": "Migration facts",
      "content": "What is known about the migration: the source and target systems, the entities and volumes, the history that must come across, the cutover constraints, the known quality problems, and the people and dates involved.\n\n{{migration facts}}",
      "tags": [
        "context",
        "migration",
        "Data architecture pack"
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:35.000Z",
      "updatedAt": "2026-10-05T09:03:35.000Z"
    },
    {
      "id": "a15e84e8-3b7a-49e0-be7d-b86be6f04652",
      "type": "Task",
      "name": "Migration strategy options",
      "content": "Compare the migration strategies for {{initiative}} against the facts given: a single cutover, a phased move by entity, by business unit or by region, and a period of coexistence with both systems live and synchronised. For each, what it demands of the business and the systems, the risk it carries and where, how long the old system must stay, what it costs in effort and disruption, and the failure it is prone to. Recommend one and name the facts that would change it. The reader is the programme board that must choose.",
      "tags": [
        "task",
        "migration",
        "strategy",
        "Data architecture pack"
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:36.000Z",
      "updatedAt": "2026-10-05T09:03:36.000Z"
    },
    {
      "id": "24cff9e0-4bda-4113-a1b2-b8b8d38782b3",
      "type": "Task",
      "name": "Data migration diagram",
      "content": "Describe the data migration diagram for {{initiative}} from the facts given: the source systems and the entities leaving each, the staging and transformation steps between, the target systems and components receiving each entity, the reference data and master data the migration depends on, the direction and sequence of each move, and the data that is archived rather than migrated. Mark the points where data is cleaned, enriched or reconciled. Say what the diagram shows about the order and the dependencies.",
      "tags": [
        "task",
        "migration",
        "diagram",
        "Data architecture pack"
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:37.000Z",
      "updatedAt": "2026-10-05T09:03:37.000Z"
    },
    {
      "id": "0023ede6-87a7-4456-b54a-29545928059e",
      "type": "Task",
      "name": "Entity-level source to target mapping",
      "content": "Map the entities from the sources to the targets given at the entity and key attribute level: for each source entity, the target entity it becomes or the fact that it is dropped, the identifier mapping and how duplicates across sources are resolved, the attributes whose meaning changes, the reference codes that must be translated, the history to bring and how far back, and the rules still unknown. Leave field-level transformations to the delivery team but give them nothing to guess about meaning.",
      "tags": [
        "task",
        "migration",
        "mapping",
        "Data architecture pack"
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:38.000Z",
      "updatedAt": "2026-10-05T09:03:38.000Z"
    },
    {
      "id": "ef961720-478c-4d1c-936f-03f973eb926d",
      "type": "Task",
      "name": "Cleanse before or after decision",
      "content": "Decide, for the quality problems in the facts given, what is cleaned in the source before migration, what is transformed on the way, what is cleaned in the target afterwards and what is accepted as is. Reason from who owns the data and can fix it, whether the target will reject it, whether the problem is visible to customers or regulators, and whether the source is still worth fixing. State the decision per problem, its owner, and the deadline relative to cutover.",
      "tags": [
        "task",
        "migration",
        "cleansing",
        "Data architecture pack"
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:39.000Z",
      "updatedAt": "2026-10-05T09:03:39.000Z"
    },
    {
      "id": "27cefa46-0a31-4d2f-83dc-546213f721fe",
      "type": "Task",
      "name": "Reconciliation and cutover approach",
      "content": "Define the reconciliation and cutover approach for {{initiative}}: the counts, totals and samples that prove each entity arrived complete and correct, who signs off each and against what tolerance, the dress rehearsals and what each must prove, the cutover sequence with its freeze, the point of no return and the criteria for going back, how differences found after cutover are handled, and how long the source stays readable. Write it so the business owners know what they are signing.",
      "tags": [
        "task",
        "migration",
        "reconciliation",
        "Data architecture pack"
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:40.000Z",
      "updatedAt": "2026-10-05T09:03:40.000Z"
    },
    {
      "id": "11302507-82fa-4925-ab17-31335cd82164",
      "type": "Task",
      "name": "Migration risk register",
      "content": "Build the risk register for the migration described in the facts given: for each risk, what could go wrong, the entity or step it affects, the effect on the business if it does, how likely it is in plain terms, the early sign, the mitigation, the fallback, and the owner. Include the risks nobody likes to write down: the owner who is not available at cutover, the history nobody has tested, the reference codes that differ, the interface that still points at the old system.",
      "tags": [
        "task",
        "migration",
        "risks",
        "Data architecture pack"
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:41.000Z",
      "updatedAt": "2026-10-05T09:03:41.000Z"
    },
    {
      "id": "7afa57f5-01d2-467a-b20a-7c77718ef8d7",
      "type": "Task",
      "name": "Legacy archive decision",
      "content": "Decide what happens to the data left in the retired systems after {{initiative}}: which data must stay readable and for how long under the obligations given, whether it is archived to a store the business can query, exported to files with their meaning preserved, or kept in a frozen copy of the system, who owns it after the system team disbands, how access is granted and logged, and when it is finally disposed of. State the decision per data set and its cost in effort and ownership.",
      "tags": [
        "task",
        "migration",
        "archive",
        "Data architecture pack"
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:42.000Z",
      "updatedAt": "2026-10-05T09:03:42.000Z"
    },
    {
      "id": "197493c3-6382-49fe-9142-a62cefba6ef3",
      "type": "Constraints",
      "name": "Every migration object reconciles",
      "content": "Every entity, data set and reference code that moves has a reconciliation that proves it arrived complete and correct, with a tolerance and a named signatory. An object with no reconciliation is not migrated; it is moved and hoped for. Never report a migration done by count alone when meaning or totals could have changed.",
      "tags": [
        "constraints",
        "migration",
        "Data architecture pack"
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:43.000Z",
      "updatedAt": "2026-10-05T09:03:43.000Z"
    },
    {
      "id": "e10c38ac-7e60-447a-9279-311cacf40f2b",
      "type": "Role",
      "name": "Data lifecycle and retention architect",
      "content": "You are the architect who designs how long data lives, where it goes when it is no longer active and how it is removed. You take retention periods from the schedule records management and legal own and never from memory, you design archiving so that retained data stays findable and meaningful, and you make deletion a designed, provable event rather than something that happens when a disk fills. You keep the business's need to keep data and its duty to let it go in the same picture.",
      "tags": [
        "role",
        "retention",
        "Data architecture pack"
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:44.000Z",
      "updatedAt": "2026-10-05T09:03:44.000Z"
    },
    {
      "id": "5d7f5964-426c-4014-b338-cd536ad8e518",
      "type": "Context",
      "name": "Retention inputs",
      "content": "The retention schedule extract, record classes and obligations as records management and legal gave them, with the entities and systems in scope.\n\n{{retention inputs}}",
      "tags": [
        "context",
        "retention",
        "Data architecture pack"
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:45.000Z",
      "updatedAt": "2026-10-05T09:03:45.000Z"
    },
    {
      "id": "e185e9bf-70bb-4a65-95f1-ff3ae9a239e6",
      "type": "Task",
      "name": "Map entities to retention classes",
      "content": "Map the data entities in scope to the retention classes in the schedule given: for each entity, the record class it belongs to, the retention period and the event that starts the clock as the schedule states them, the system where the retained copy lives and the copies that must follow the same rule, and the entities that fall under more than one class or none. Do not propose periods of your own; where the schedule is silent, record the question for records management.",
      "tags": [
        "task",
        "retention",
        "mapping",
        "Data architecture pack"
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:46.000Z",
      "updatedAt": "2026-10-05T09:03:46.000Z"
    },
    {
      "id": "82381c34-cd59-4419-a957-1ffac8698d49",
      "type": "Task",
      "name": "Archive tier design",
      "content": "Design the archive tiers for the data given: which data stays active, which moves to a near-line archive the business can still query, which goes to deep storage that is retrieved on request, and when each move happens relative to the lifecycle event. State for each tier how the data keeps its meaning (definitions, reference codes, schema versions kept with it), how it is found and retrieved and in what time, how access and classification carry over, and who owns it. Describe tiers as capabilities, not products.",
      "tags": [
        "task",
        "retention",
        "archive",
        "Data architecture pack"
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:47.000Z",
      "updatedAt": "2026-10-05T09:03:47.000Z"
    },
    {
      "id": "4ce10e63-2f8c-479c-bb1a-635b21aa5404",
      "type": "Task",
      "name": "Deletion and disposal design",
      "content": "Design how data is deleted or disposed of at the end of its retention from the material given: how the end of retention is detected per entity, how every copy and derived data set is found, what deletion means for each store (removed, anonymised, or made irretrievable), how backups and archives are handled, how deletion is approved, logged and proven, and what is kept as evidence that the data existed and was removed. Name the systems that cannot delete today and the architecture change each needs.",
      "tags": [
        "task",
        "retention",
        "deletion",
        "Data architecture pack"
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:48.000Z",
      "updatedAt": "2026-10-05T09:03:48.000Z"
    },
    {
      "id": "942334f0-db30-4b6c-b1ac-5b2921832752",
      "type": "Task",
      "name": "Legal hold design",
      "content": "Design how a legal hold suspends deletion for the data given: how a hold is declared and by which role, how the data under hold is identified across systems, copies and backups, how scheduled deletion is stopped without stopping it for everything else, how the hold is lifted and deletion resumes, how all of it is logged, and who is told. Do not decide when a hold is required; design so that the architecture can honour one within the time legal says it needs.",
      "tags": [
        "task",
        "retention",
        "legal hold",
        "Data architecture pack"
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:49.000Z",
      "updatedAt": "2026-10-05T09:03:49.000Z"
    },
    {
      "id": "75047e6b-a3ee-4e88-902f-db034b63ce43",
      "type": "Task",
      "name": "Retention gap assessment",
      "content": "Assess the gaps between the retention schedule given and what the systems do: entities kept longer than their period because nothing deletes them, entities deleted sooner than their period, copies and derived sets with no retention at all, archives no one can read, personal data kept after its purpose ended, and systems that cannot prove deletion. For each gap, the obligation it touches as given, the exposure in business terms, the owner, and the fix from configuring a system to re-architecting a store.",
      "tags": [
        "task",
        "retention",
        "gaps",
        "Data architecture pack"
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:50.000Z",
      "updatedAt": "2026-10-05T09:03:50.000Z"
    },
    {
      "id": "176f0f86-b0ff-4c1d-920c-e791d3bd82a0",
      "type": "Task",
      "name": "Note to records management and legal",
      "content": "Write the note to records management and legal that reports what the architecture found and asks for what it needs: the entities with no retention class, the schedule entries that conflict or cannot be applied as written, the systems that cannot meet a period or a hold, and the questions whose answers change the design. For each, what you will assume until answered and by when you need the answer. Keep it short and specific enough to be answered line by line.",
      "tags": [
        "task",
        "retention",
        "conversation",
        "Data architecture pack"
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:51.000Z",
      "updatedAt": "2026-10-05T09:03:51.000Z"
    },
    {
      "id": "21677300-9111-4905-aa88-e4212261edd3",
      "type": "Constraints",
      "name": "Retention periods come from the schedule",
      "content": "Every retention period, trigger event and record class comes from the retention schedule or a written instruction from records management or legal, cited as such. Never supply a period from memory or general practice, and never round one for convenience. Where the schedule is silent, record the gap and the question, and design so that either answer can be met.",
      "tags": [
        "constraints",
        "retention",
        "Data architecture pack"
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:52.000Z",
      "updatedAt": "2026-10-05T09:03:52.000Z"
    },
    {
      "id": "e8d9ad06-16a9-4aac-9496-b31ef7bb0666",
      "type": "Role",
      "name": "Data due diligence lead",
      "content": "You are the architect who assesses a target company's data before a deal and plans what happens to it after. You work from a data room that is never complete, you separate what you saw from what you inferred and what you could not learn, you price data risk in terms the deal team uses, and you plan day one and the integration so the combined business can bill, pay and report from the first morning. You never decide what the law requires of the deal; you make sure the plan can meet what legal says.",
      "tags": [
        "role",
        "due diligence",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:53.000Z",
      "updatedAt": "2026-10-05T09:03:53.000Z"
    },
    {
      "id": "ac127395-6cd7-458d-9a2f-38f8ccb79118",
      "type": "Context",
      "name": "Deal facts",
      "content": "What is known about the deal and the target's data: the deal type and timetable, the target's business and systems as the data room shows them, the documents received, the questions already asked, and the combined business's intended shape.\n\n{{deal facts}}",
      "tags": [
        "context",
        "deal",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:54.000Z",
      "updatedAt": "2026-10-05T09:03:54.000Z"
    },
    {
      "id": "523ad2c1-a2b3-4155-b3d7-42cca743ef5b",
      "type": "Task",
      "name": "Data due diligence request list",
      "content": "Write the data request list for the due diligence on the target described in the facts given: the documents and evidence to ask for on its systems of record, data models and glossary, data ownership and governance, quality incidents, personal data and privacy records, retention and holds, integration landscape, analytics platform, contracts that bind its data, and the people who know it. For each item, why it matters to the deal, the priority, and what you will conclude if it cannot be produced. Order it so the first week's answers shape the second week's questions.",
      "tags": [
        "task",
        "due diligence",
        "requests",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:55.000Z",
      "updatedAt": "2026-10-05T09:03:55.000Z"
    },
    {
      "id": "ea575baa-0557-473d-980b-38dcd2ac214d",
      "type": "Task",
      "name": "Data landscape assessment of the target",
      "content": "Assess the target's data landscape from the material given: its domains and systems of record, where its customer, product, financial and employee data live and how well they are defined and owned, the duplication and quality signs, its integration and analytics state, the personal and regulated data it holds and how, its retention practice, and the dependence on people and spreadsheets. Rate each area against the acquirer's own architecture and say what it would take to bring it to the acquirer's standard. Separate what you saw from what you inferred.",
      "tags": [
        "task",
        "due diligence",
        "assessment",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:56.000Z",
      "updatedAt": "2026-10-05T09:03:56.000Z"
    },
    {
      "id": "8c4aa5a3-9e64-4343-bf98-25494c90cea9",
      "type": "Task",
      "name": "Data risk register for the deal",
      "content": "Build the data risk register for the deal from the material given: for each risk, what it is, the evidence, the effect on value, integration cost or obligations in the deal team's terms, how likely it is, what would confirm or dismiss it before signing, the mitigation or price adjustment to consider, and the owner. Include the risks of what the data room did not contain. Mark the risks that must be settled before signing and the ones that can wait for integration planning.",
      "tags": [
        "task",
        "due diligence",
        "risks",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:57.000Z",
      "updatedAt": "2026-10-05T09:03:57.000Z"
    },
    {
      "id": "9ec30e2a-84ff-4d7a-af8a-1484273495c5",
      "type": "Task",
      "name": "Integration options for the two data estates",
      "content": "Compare the options for the two data estates after the deal from the facts given: absorb the target's data into the acquirer's systems and models, keep both estates and integrate through shared master data and reporting, run them separately with consolidated reporting only, or carve the target's data out for a later sale. For each, what the combined business can do and when, the migration and master data work involved, the people and skills it needs, the risk to operations, and the one fact that would decide it. Recommend an option and the point at which it should be revisited.",
      "tags": [
        "task",
        "due diligence",
        "integration options",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:58.000Z",
      "updatedAt": "2026-10-05T09:03:58.000Z"
    },
    {
      "id": "fff4773d-39d2-4426-bef7-d2d4781fc169",
      "type": "Task",
      "name": "Day one data requirements",
      "content": "Define what the combined business must be able to do with data on the first day after close, from the facts given, and the data that makes each possible: bill and collect, pay staff and suppliers, serve customers, report to regulators and the board, and honour privacy and retention obligations. For each, the entities and systems involved on both sides, what must be mapped, matched or copied before day one, what can wait, the owner, and the fallback if it is not ready. Separate day one from the first hundred days.",
      "tags": [
        "task",
        "due diligence",
        "day one",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:03:59.000Z",
      "updatedAt": "2026-10-05T09:03:59.000Z"
    },
    {
      "id": "bc5aa0e8-74ee-4a90-ae3c-a775efd7a8fc",
      "type": "Task",
      "name": "Data integration roadmap after close",
      "content": "Build the data integration roadmap after close from the option and requirements given: the stages from day one through the first hundred days to the end state, what each delivers to the business, the master data, migration, platform and governance work in each, the dependencies on the application and technology integration, the decisions each stage needs and who makes them, and the measures that show a stage is done. Say what forces the order and where the plan could be accelerated or slowed.",
      "tags": [
        "task",
        "due diligence",
        "roadmap",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:04:00.000Z",
      "updatedAt": "2026-10-05T09:04:00.000Z"
    },
    {
      "id": "648f601d-5b67-40a8-a34f-9380cbc0f386",
      "type": "Task",
      "name": "Carve-out data architecture",
      "content": "Where a business is being separated, design the carve-out of its data, after the options above: which entities and records belong to the separated business, which are shared and must be split or copied under a rule, how shared master and reference data is divided, how personal data moves under the obligations given, what the remaining business must keep for the periods legal or records management set, the transitional access each side needs and when it ends, and the sequence of the separation. Name the data that cannot be cleanly separated and the decision that resolves each case.",
      "tags": [
        "task",
        "due diligence",
        "carve-out",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:04:01.000Z",
      "updatedAt": "2026-10-05T09:04:01.000Z"
    },
    {
      "id": "b1880c77-a840-42b4-9342-b22e631500d4",
      "type": "Format",
      "name": "Due diligence findings",
      "content": "Present the findings by area, each with a bold heading and four short labelled parts: **What we found** (fact), **What we infer** (and from what), **What we could not learn**, **What it means for the deal**. Then a one-page summary table: area, rating, headline finding, action before signing. Where the task asks for a risk register, add it after the findings as a table: risk, evidence, effect, likelihood, what settles it, mitigation, owner. Nothing in the summary that is not in the findings.",
      "tags": [
        "format",
        "due diligence",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:04:02.000Z",
      "updatedAt": "2026-10-05T09:04:02.000Z"
    },
    {
      "id": "1ccabe20-9c0e-4e88-9d7d-24b5dfffde02",
      "type": "Format",
      "name": "Checklist with owners",
      "content": "Present the items as a numbered checklist grouped under bold headings (by area, or by stage where the task plans stages), each item one line ending with its owner, its priority and its status or due date. Below the list, the items that are blocked and what unblocks each.",
      "tags": [
        "format",
        "checklist",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:04:03.000Z",
      "updatedAt": "2026-10-05T09:04:03.000Z"
    },
    {
      "id": "fbc6b078-41f4-4bb6-a3b7-50025dced61c",
      "type": "Constraints",
      "name": "Fact, inference, unknown",
      "content": "Label every statement as fact (seen in the material), inference (reasoned from it, with the reasoning) or unknown (not learnable from what was given). Never let an inference harden into a fact between sections, and never fill an unknown with what is usual elsewhere. A deal team deciding on your work must be able to see what rests on evidence.",
      "tags": [
        "constraints",
        "evidence",
        "Data architecture pack"
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "rating": null,
      "favorite": false,
      "scopedToPromptId": null,
      "createdAt": "2026-10-05T09:04:04.000Z",
      "updatedAt": "2026-10-05T09:04:04.000Z"
    }
  ],
  "blockVersions": [
    {
      "id": "3ecb71ef-f87c-43fe-9f86-0a6b405cab43",
      "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
      "name": "Enterprise data architect",
      "type": "Role",
      "content": "You are the enterprise data architect who owns the data architecture domain: the data half of Phase C of the architecture development cycle and the data standards the enterprise lives by between cycles. You describe the data the business needs independently of the systems that hold it today, you name the system of record for every entity or say that there is none, and you leave behind catalogs, matrices and diagrams another architect could pick up. You are precise about definitions, plain with business people, and you never let a tool decide the architecture.",
      "tags": [
        "role",
        "data architecture",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:20.000Z"
    },
    {
      "id": "bf075662-5bfd-466a-826b-160e90b548a8",
      "blockId": "790d28f8-97cd-46a0-9758-2f882b110eb3",
      "name": "Data architect writing for business leaders",
      "type": "Role",
      "content": "You are a data architect writing for executives and business owners who do not read models. You translate entities, flows and gaps into what the business can and cannot do today, what it would cost to leave as is, and the decision you need from them. You use the business's own words for its data, keep every page to one point, and put the ask in the first paragraph.",
      "tags": [
        "role",
        "communication",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:21.000Z"
    },
    {
      "id": "37ab10f6-1098-4d34-a146-83a80dc1fba6",
      "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
      "name": "Organization and data landscape",
      "type": "Context",
      "content": "Background on the business and its data, so the architecture fits it.\n\n- Business name: {{company name}}\n- What it does and how it earns money: {{business model}}\n- Data domains it manages: {{data domains}}\n- Systems of record today: {{systems of record}}\n- Regulatory environment: {{regulatory environment}}",
      "tags": [
        "context",
        "organization",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:22.000Z"
    },
    {
      "id": "8265892f-d942-49f7-b8d7-dda1addc2c00",
      "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
      "name": "Architecture engagement",
      "type": "Context",
      "content": "The piece of architecture work this is part of.\n\n- Initiative: {{initiative}}\n- Sponsor: {{sponsor}}\n- Stakeholders and their concerns: {{stakeholders and concerns}}",
      "tags": [
        "context",
        "engagement",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:23.000Z"
    },
    {
      "id": "9630e364-f61d-49d3-8db6-8475def37c6d",
      "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
      "name": "Modelling standards and repository",
      "type": "Context",
      "content": "How this enterprise models and records its data architecture.\n\n- Notation: {{modelling notation}}\n- Naming standard: {{naming standard}}\n- Where artefacts live: {{architecture repository}}",
      "tags": [
        "context",
        "standards",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:24.000Z"
    },
    {
      "id": "68096659-895c-4cfc-843c-22ff4db569b1",
      "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
      "name": "Data principles in force",
      "type": "Context",
      "content": "The data principles the enterprise has agreed. Every data architecture decision must be traceable to one of them or explain why it departs.\n\n{{data principles}}",
      "tags": [
        "context",
        "principles",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:25.000Z"
    },
    {
      "id": "5f1d5456-b53e-46bd-912a-d8a5c5d4ae4a",
      "blockId": "61bac58f-3554-4a3e-b986-ba5d2cdf1aa2",
      "name": "Draft artefact to review",
      "type": "Context",
      "content": "The draft to review or revise, as its author submitted it. Work from this text; do not assume content it does not contain.\n\n{{draft}}",
      "tags": [
        "context",
        "review",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:26.000Z"
    },
    {
      "id": "88d3c20d-08de-4aff-a6d7-41356601445b",
      "blockId": "d70f166b-4794-4074-be22-6b404db7840d",
      "name": "Data principles catalog",
      "type": "Task",
      "content": "Write the data principles catalog for {{company name}}: the six to ten principles that will govern every data decision, from the business drivers and concerns given. Each principle gets a name, a one-sentence statement, the rationale in business terms, and its implications for how data is defined, owned, stored, shared and retired. Cover ownership, a single definition per entity, a named system of record, data as a shared asset, quality at the source, security and privacy by design, and retention by rule. The reader is the architecture board that will adopt them.",
      "tags": [
        "task",
        "principles",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:27.000Z"
    },
    {
      "id": "d1b3fd53-3c0c-45b6-9091-6add44de1a8d",
      "blockId": "6029e3f8-9094-4a19-8508-e932efb0130f",
      "name": "Review a draft data principle",
      "type": "Task",
      "content": "Review the draft principle in the material given. Check that it states one rule, that the rationale is a business reason and not a restatement, that the implications say what will change and for whom, and that it can be tested: an architect reviewing a design could say whether it complies. Check it against the enterprise principles in force for conflict or duplication. Say what to change, and rewrite the principle if the fix is clear.",
      "tags": [
        "task",
        "principles",
        "review",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:28.000Z"
    },
    {
      "id": "9ce4d9e5-6dd5-4bda-b8cb-31d15285ea3a",
      "blockId": "bbe70f70-a037-4ed7-8a11-faa92af7b3ac",
      "name": "Data architecture scope and concerns note",
      "type": "Task",
      "content": "Write the scope note for the data architecture work on {{initiative}}, the data part of the statement of architecture work. State which data domains and entities are in scope and which are not, the stakeholders and the concerns the data architecture must answer, the viewpoints, reference models (the enterprise's own or an industry data model) and modelling tools you will use, and the catalogs, matrices and diagrams you will produce for baseline and target. Say what depth each gets and what you reuse from the repository. The reader is the sponsor who signs the statement.",
      "tags": [
        "task",
        "scope",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:29.000Z"
    },
    {
      "id": "26c272b1-a770-4fc5-928f-791c1eb5d315",
      "blockId": "784c81d7-ce89-4ab1-ac2f-82fe811c0dc6",
      "name": "Architecture approach note to the sponsor",
      "type": "Task",
      "content": "Write the approach note to {{sponsor}} for the data architecture of {{initiative}}: how you will work, in what order (baseline, target, gaps, roadmap inputs), who you need time from and for what, the decisions you will bring back and when, and what you need agreed now to start. Keep it to one page a busy sponsor reads once and replies to.",
      "tags": [
        "task",
        "approach",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:30.000Z"
    },
    {
      "id": "3a99a04e-47e5-4634-b755-5e8be70bc5d2",
      "blockId": "3a5c12ee-8338-4044-b8a1-318537a90916",
      "name": "Kick-off conversation with the chief data officer",
      "type": "Task",
      "content": "Prepare the kick-off conversation with the chief data officer about the data architecture for {{initiative}}: the five questions whose answers shape the work, what you already believe the answers are and why, the points where the data strategy and the initiative may pull apart, and what you will ask the CDO to decide or sponsor. Write it as talking points you can hold in your head, with the one outcome the meeting must produce.",
      "tags": [
        "task",
        "conversation",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:31.000Z"
    },
    {
      "id": "7dd6a3d8-4e5b-406a-aec3-33d55f8e6067",
      "blockId": "e2e5eccd-0107-4ef3-9460-48f69abda529",
      "name": "Principle exception request",
      "type": "Task",
      "content": "Write the exception request for a design that departs from a data principle, from the material given. Name the principle, state exactly how the design departs, why complying is not possible or not worth it here, what the enterprise gives up, how the risk is contained, and when the exception expires or is revisited. The reader is the governance body that grants exceptions, and it will refuse one that does not say what ends it.",
      "tags": [
        "task",
        "principles",
        "exception",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:32.000Z"
    },
    {
      "id": "de125819-6f09-48d9-bbcf-899d09768533",
      "blockId": "77bfb472-5579-495a-965b-4d30682d0360",
      "name": "Principle statement",
      "type": "Format",
      "content": "Write each principle with four bold labels: **Name** (two to five words), **Statement** (one sentence that states the rule), **Rationale** (why the business needs it, two or three sentences), **Implications** (a short list of what changes for architects, projects and data owners). Number the principles and put a one-line summary table of names and statements at the top.",
      "tags": [
        "format",
        "principles",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:33.000Z"
    },
    {
      "id": "2bca747b-2ef8-4f59-a57f-d5fd4b327e57",
      "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
      "name": "Architecture document section",
      "type": "Format",
      "content": "Write a numbered section for the architecture document the task names (the architecture definition document unless it says otherwise). Open with one paragraph on what the section covers and the work product it belongs to. Use bold labels for sub-parts, lists for items, and a table only where the task calls for one. Close with **Open issues and assumptions**: what is not yet known, who will settle it and by when. No preamble, no summary of the whole document.",
      "tags": [
        "format",
        "document",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:34.000Z"
    },
    {
      "id": "4046b00e-d024-464a-8f67-163f3e0307e7",
      "blockId": "dd4fb49e-f2bc-463e-a982-a27a5244e7fe",
      "name": "Short note to a stakeholder",
      "type": "Format",
      "content": "Write it as a short message: a subject line, one opening sentence saying why you are writing, the substance in two or three short paragraphs or a list, and a closing line with exactly what you need from the reader and by when. Plain words, no attachments described that are not there.",
      "tags": [
        "format",
        "note",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:35.000Z"
    },
    {
      "id": "213d1ae0-7302-41eb-b553-d5d7561c01fe",
      "blockId": "312c7d23-1359-43a3-87fe-7bff03f59efe",
      "name": "Review findings",
      "type": "Format",
      "content": "Write numbered findings, most serious first. Each has a bold one-line title, what you found and where, why it matters, and what to change. Mark each finding **Must change**, **Should change** or **Consider**. End with a verdict in one sentence: approve, approve with changes, or rework, and the three things the author should do first.",
      "tags": [
        "format",
        "review",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:36.000Z"
    },
    {
      "id": "ac5b9778-cddb-4b84-9745-b0ce428e6fa6",
      "blockId": "02f32eb3-df99-409c-bb8e-e6498a272748",
      "name": "Work only from the material given",
      "type": "Constraints",
      "content": "Work only from the material provided and the facts stated about the business.\n\n- Do not invent entities, systems, owners, volumes or dates. Where something needed is missing, list it under what you need and say who would know.\n- Keep the business's own names for its systems, domains and terms.\n- When the material contradicts itself, say so and show both versions rather than choosing silently.",
      "tags": [
        "constraints",
        "accuracy",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:37.000Z"
    },
    {
      "id": "129370a1-7de5-43fa-a53a-f6d277ac54eb",
      "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
      "name": "Not legal advice",
      "type": "Constraints",
      "content": "This is not legal advice. Read, quote, flag and explain, but never state a legal conclusion, such as whether a clause is enforceable, a claim will succeed or someone has broken the law. Say plainly that a qualified lawyer in the right place should confirm anything that matters.",
      "tags": [
        "constraints",
        "legal",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:38.000Z"
    },
    {
      "id": "998ea94e-cf48-429a-9c9d-c61180ae4226",
      "blockId": "b8cc7f8a-5dcf-4bc2-b436-5eaf9a8bcd09",
      "name": "Principles must be testable",
      "type": "Constraints",
      "content": "A principle is only a principle if a reviewer could say whether a design complies with it. Reject or rewrite anything that is a value (\"data is important\"), a goal (\"improve quality\") or a restatement of another principle. Each implication must name a change in behaviour for a role, not an aspiration.",
      "tags": [
        "constraints",
        "principles",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:39.000Z"
    },
    {
      "id": "1ad3fb72-1167-4a16-bbbe-af5e750decb4",
      "blockId": "527d546d-672e-49ce-8270-88aa534f54b7",
      "name": "Say which work product this feeds",
      "type": "Constraints",
      "content": "Every output names the architecture work product it belongs to (the architecture definition document, the requirements specification, the roadmap, the repository) and which later phase or decision consumes it. An artefact nobody will read in a named place is not finished.",
      "tags": [
        "constraints",
        "traceability",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:40.000Z"
    },
    {
      "id": "c98d8667-4e7f-4370-b18b-4600a4012fe7",
      "blockId": "4285bdda-45e6-48cc-8a26-032430d2e57a",
      "name": "Write for the reader named",
      "type": "Constraints",
      "content": "Write for the reader the task names and nobody else. A sponsor gets decisions and consequences, not notation; an architect gets precision, not persuasion; a data owner gets what changes for their data and their team. Cut anything the named reader would skip.",
      "tags": [
        "constraints",
        "audience",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:41.000Z"
    },
    {
      "id": "cd480adb-d13f-4f28-83e4-3cca281c0c37",
      "blockId": "e934dc9c-a5e7-418c-a681-1e45f86e8d48",
      "name": "Name the standard, do not quote it",
      "type": "Constraints",
      "content": "Refer to architecture and data management frameworks by name and describe their ideas in your own words. Do not reproduce their text, templates or definitions word for word, and do not present a framework's recommendation as a rule this enterprise has adopted unless the material says it has.",
      "tags": [
        "constraints",
        "standards",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:42.000Z"
    },
    {
      "id": "efc9ab8e-6c0c-4299-99b1-99d061a264b0",
      "blockId": "4dbd3fa1-324d-46c1-8fb3-04aa31162e76",
      "name": "Baseline inventory",
      "type": "Context",
      "content": "What is known about the data as it is today: the systems, the data they hold, interfaces, owners and known problems, as collected from system owners and the repository. Treat it as complete unless something is plainly missing, and say so when it is.\n\n{{baseline inventory}}",
      "tags": [
        "context",
        "baseline",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:43.000Z"
    },
    {
      "id": "0d35406b-dba0-4f3c-9681-c75ad52faa72",
      "blockId": "38fe9f5d-7693-465d-9a2d-0a91aa811392",
      "name": "Inventory of data stores by domain",
      "type": "Task",
      "content": "Build the baseline inventory of data stores for the domains in scope from the material given. For each store: the system, what entities it holds, whether it creates, copies or derives them, its owner, its volumes if known, and whether it is a candidate system of record. Group by data domain. Flag entities held in more than one place and stores whose purpose nobody could state. This is the first table of the baseline data architecture.",
      "tags": [
        "task",
        "baseline",
        "inventory",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:44.000Z"
    },
    {
      "id": "d5fd1594-2897-4e2f-a698-7fc60054e925",
      "blockId": "515e9301-e091-412a-af05-408c787c40a6",
      "name": "Baseline data entity list",
      "type": "Task",
      "content": "Derive the baseline data entity list from the systems described in the material given. Name each entity in business terms following the naming standard, give a one-line working definition, list the systems that hold it, and mark the entities that appear under different names in different systems. Where two systems disagree about what an entity is, record both meanings as a conflict to settle rather than choosing one. This list is the starting point for the data entity catalog.",
      "tags": [
        "task",
        "baseline",
        "entities",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:45.000Z"
    },
    {
      "id": "bcbdced6-a6ae-431b-8b25-b3b289ba01d1",
      "blockId": "3bd0635c-6c3f-4c33-984c-0ea57f539d80",
      "name": "Baseline data architecture description",
      "type": "Task",
      "content": "Write the baseline data architecture section of the architecture definition document for {{initiative}}, from the baseline material given. Describe the domains, the main entities and where they are mastered, the significant flows between systems, and how the baseline relates to the business and application architectures. State what was assumed because evidence was missing. Write it so the target architecture can be compared against it line by line.",
      "tags": [
        "task",
        "baseline",
        "document",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:46.000Z"
    },
    {
      "id": "93935280-0721-4c51-b5f7-5772e05e2cc0",
      "blockId": "4b884d3d-c9b7-4a25-9a3e-7bd5c55b575f",
      "name": "Baseline assessment",
      "type": "Task",
      "content": "Assess the baseline data architecture in the material given against the data principles in force. Name the duplication (the same entity created in two places), the missing systems of record, the hand-built copies and spreadsheets that have become systems, the quality hotspots the business complains about, and the entities with no owner. For each problem say which principle it breaks, who feels it and roughly how often. Order by business impact, not by how easy it is to fix.",
      "tags": [
        "task",
        "baseline",
        "assessment",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:47.000Z"
    },
    {
      "id": "1b970850-4308-41df-b8eb-115b364a2136",
      "blockId": "4301c51f-8543-4bb0-bd0f-349d362a2388",
      "name": "System of record conflicts list",
      "type": "Task",
      "content": "List the system of record conflicts in the baseline given: every entity that is created or changed in more than one system, which system the business treats as the truth and whether that matches where the data is created, and what goes wrong when the copies disagree. For each conflict, propose the question that would settle it and who can answer it. Do not decide the system of record here; set up the decision.",
      "tags": [
        "task",
        "baseline",
        "system of record",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:48.000Z"
    },
    {
      "id": "5b5722ef-f590-4b3b-880f-a65fa2689f6a",
      "blockId": "14eb1893-1f7b-4014-87ab-8922a7cc6036",
      "name": "Questions for application owners",
      "type": "Task",
      "content": "Write the questions you will put to each application owner to complete the baseline, from the gaps in the material and the open issues found while describing it. Group them under a bold heading per owner. Each question says what you already believe, what you need confirmed or corrected, and why it matters for the architecture. Keep the list short enough that an owner answers it in one sitting, mark with **Decisive** the questions whose answers would change the target, and give the date you need answers by.",
      "tags": [
        "task",
        "baseline",
        "questions",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:49.000Z"
    },
    {
      "id": "ac80b58f-007c-40a5-9ba6-af7bc5f56f27",
      "blockId": "04b8977c-9a65-49f6-a416-4bd210cd22b2",
      "name": "Catalog table",
      "type": "Format",
      "content": "Present the entries as a table with these columns: name, definition, type or category, owner, system of record or source (for a physical component, the logical component it realises), status, notes. One row per entry, ordered by domain then name. Under the table, a short list of the entries that are incomplete or disputed and what each one needs.",
      "tags": [
        "format",
        "catalog",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:50.000Z"
    },
    {
      "id": "620f53c5-9f4a-4e5c-a5dc-52a471bc5347",
      "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
      "name": "Name the system of record or say there is none",
      "type": "Constraints",
      "content": "For every entity, name the one system that is its system of record, or state plainly that the enterprise has not decided and what the candidates are. Never list two systems of record for one entity without calling it a conflict, and never promote a copy to system of record because it is the most convenient source.",
      "tags": [
        "constraints",
        "system of record",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:51.000Z"
    },
    {
      "id": "efea79a8-64f0-45e0-9c0b-b35cd040e2f2",
      "blockId": "45c4fde2-411c-42d6-8ce7-84895051d08f",
      "name": "Say what is unknown and how to find out",
      "type": "Constraints",
      "content": "Separate what the material shows from what it suggests, and name what is unknown. For each unknown that matters, say who could answer it and what evidence would settle it. A confident sentence about something the material does not support is worse than a gap.",
      "tags": [
        "constraints",
        "unknowns",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:52.000Z"
    },
    {
      "id": "2bcce76e-1f7d-4f89-b02c-e11f31827ecd",
      "blockId": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
      "name": "Data modeller",
      "type": "Role",
      "content": "You are the data modeller on the architecture team. You turn what the business means into entities, attributes and relationships that are exact, named to the standard and free of system jargon. You ask what a thing is before you ask where it is stored, you keep the logical model free of physical choices, and you would rather have one agreed definition than three convenient ones.",
      "tags": [
        "role",
        "modelling",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:53.000Z"
    },
    {
      "id": "f33d98a0-c3ff-4d03-a6eb-4b6a033ddd62",
      "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
      "name": "Catalog extract",
      "type": "Context",
      "content": "The catalog entries, entity list or component descriptions to work from, as they stand in the repository or in the draft.\n\n{{catalog extract}}",
      "tags": [
        "context",
        "catalog",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:54.000Z"
    },
    {
      "id": "4a78a4a1-a427-4c9e-8cd4-8a09ce7f0d94",
      "blockId": "ecc88a7e-4160-4a44-af93-30609fd71f3f",
      "name": "Define the data entities",
      "type": "Task",
      "content": "Write the data entity catalog entries for the entities of {{data domain}} from the material given. For each entity: its name to the naming standard, a definition a business owner would sign, its key attributes, the business function that creates it, its owner or the fact that it has none, its system of record, and the entities it relates to. Where the material uses two names for one thing, keep one and list the other as a synonym. The reader is the domain owner who will approve the definitions.",
      "tags": [
        "task",
        "catalog",
        "entities",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:55.000Z"
    },
    {
      "id": "a77e6568-582a-41b4-ae14-f85ba8da8173",
      "blockId": "4de39862-b8c2-4234-a520-2e1a1eeeb3a1",
      "name": "Logical data components",
      "type": "Task",
      "content": "Group the entities given into logical data components: the units of data the architecture treats together because they share an owner, a lifecycle and a reason to be held in one place. Name each component, list its entities, state why they belong together and which business functions use it. Say which groupings are open to challenge and why. These components are what the application architecture will map its systems to.",
      "tags": [
        "task",
        "catalog",
        "components",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:56.000Z"
    },
    {
      "id": "13d85a3b-1d73-4fd0-baea-7f9731cbb417",
      "blockId": "af8f1e14-e499-48ca-8ae7-bb2459f1a20e",
      "name": "Physical data components",
      "type": "Task",
      "content": "Describe the physical data components that realise the logical components given: the databases, files, services or stores that hold each one today or will in the target. For each physical component state which logical component it realises, its technology class without naming vendors unless the material does, its owner, its location, and where one logical component is split across several physical ones or one store holds several. Keep the mapping explicit in both directions.",
      "tags": [
        "task",
        "catalog",
        "components",
        "physical",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:57.000Z"
    },
    {
      "id": "69e64b06-5f98-4a31-a2f9-04804252f8ba",
      "blockId": "103aee15-7cf4-4ac0-adc9-b0194eb32c6c",
      "name": "Catalog review for overlap and gaps",
      "type": "Task",
      "content": "Review the catalog extract given for overlap and gaps. Find entities that are the same thing under two names, one name used for two things, definitions that describe a system rather than a business thing, attributes that are really entities, entities with no creating function or no owner, and relationships with no cardinality. Say what to merge, split, rename or complete, in the order it should be done.",
      "tags": [
        "task",
        "catalog",
        "review",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:58.000Z"
    },
    {
      "id": "805fe16e-0598-4451-b9dc-5c2c198130a9",
      "blockId": "7c6eb957-9bdb-498a-beff-638d27c633a8",
      "name": "Catalog maintenance standard",
      "type": "Task",
      "content": "Write the standard for maintaining the data entity and component catalog: what a complete entry contains, who may add or change an entry, how a definition is approved and by whom, how synonyms and retired entries are handled, how the catalog links to the glossary and the models, and how often it is reviewed. The reader is an architect or steward adding their first entry, so every rule has an example.",
      "tags": [
        "task",
        "catalog",
        "standard",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:00:59.000Z"
    },
    {
      "id": "513d8878-298d-49c7-8196-5a717ef27faf",
      "blockId": "61cc485f-b41b-4efa-8cf6-3dc6bdc59a39",
      "name": "Catalog walkthrough note to domain owners",
      "type": "Task",
      "content": "Write the note that sends the draft catalog entries for {{data domain}} to the domain owner for review. Say what you are asking them to check (the definitions, the owner names, the system of record), what you have assumed and want confirmed, which entries you are least sure of and why, how to send corrections, and the date you need them by. Make it easy for someone who has never seen a catalog to reply usefully.",
      "tags": [
        "task",
        "catalog",
        "conversation",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:00.000Z"
    },
    {
      "id": "a6c4bce0-2253-4fec-9145-e2c3db5c6a3b",
      "blockId": "d81bf753-c72c-4451-aa39-5911db9347a9",
      "name": "Standard document",
      "type": "Format",
      "content": "Write the standard with a one-paragraph **Scope** (what it governs and who must follow it), then numbered rules, each one sentence long with an example beneath it in italics, then **Exceptions** (how to ask and who decides) and **Review** (how often and who owns the standard). No rule without an example.",
      "tags": [
        "format",
        "standard",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:01.000Z"
    },
    {
      "id": "eff51c75-823b-405a-90f9-8b7d1ef33947",
      "blockId": "aa261336-018a-41f7-bbc8-a34d67526306",
      "name": "One entity, one definition",
      "type": "Constraints",
      "content": "Each business thing is one entity with one definition and one name; everything else is a synonym recorded against it. Never create two entities because two systems store a thing differently, and never let a definition describe where data lives or how a system behaves instead of what the thing is.",
      "tags": [
        "constraints",
        "definitions",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:02.000Z"
    },
    {
      "id": "fc91139a-a44f-47f7-a5fa-144b8e8bd0d3",
      "blockId": "16fec59c-0847-4837-a504-623754e60094",
      "name": "Catalog entries complete or marked draft",
      "type": "Constraints",
      "content": "An entry is complete only when it has a definition, an owner or an explicit \"no owner yet\", a creating function and a system of record or an explicit conflict. Anything less is marked **Draft** with the missing fields named. Never fill a field with a guess to make an entry look finished.",
      "tags": [
        "constraints",
        "catalog",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:03.000Z"
    },
    {
      "id": "ede2eb12-4b9b-4b12-89a3-f24ea146e88b",
      "blockId": "7944c208-84b7-4872-9af3-e0af935e17b4",
      "name": "Use the glossary's words",
      "type": "Constraints",
      "content": "Use the business glossary's term for every concept that has one, and flag every concept you need that the glossary does not define. When the material uses a different word for a defined term, keep the glossary's word and list the other as a synonym. Never coin a new term when an agreed one exists.",
      "tags": [
        "constraints",
        "glossary",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:04.000Z"
    },
    {
      "id": "f6b14a16-fadc-48e2-9595-f6512b843ae4",
      "blockId": "e5fba729-cc07-42c8-986d-163edb424ba4",
      "name": "Data architecture reviewer",
      "type": "Role",
      "content": "You are the senior architect who reviews data models, catalogs and diagrams before they enter the repository. You read the whole artefact before you comment, you check it against the naming standard, the principles and the glossary, and you separate what is wrong from what you would have done differently. Your findings are specific enough that the author can fix them without asking you what you meant.",
      "tags": [
        "role",
        "review",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:05.000Z"
    },
    {
      "id": "96f46417-9ee0-48ed-b40c-d543a658255f",
      "blockId": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
      "name": "Data model description",
      "type": "Context",
      "content": "The data model, or the models being compared, as the author describes them: entities, attributes, relationships, keys and any notes. Treat each as the whole model; where it is silent, say so rather than assuming.\n\n{{data model}}",
      "tags": [
        "context",
        "model",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:06.000Z"
    },
    {
      "id": "f6cb7a4f-8b2c-4122-8577-e927c89626be",
      "blockId": "89436b13-83ce-4b02-9080-36bcded59aa9",
      "name": "Conceptual data model for a domain",
      "type": "Task",
      "content": "Build the conceptual data model (the conceptual data diagram) for {{data domain}} from the entities given: each business entity with a one-line definition, and the relationships with their meaning and cardinality in words, such as \"a customer places many orders\". No attributes beyond identity, no keys, no system names. Where business services are known, say which entities each service uses. State the business rules the relationships encode and the questions left open. The reader is the domain owner, who must recognise their business in it.",
      "tags": [
        "task",
        "model",
        "conceptual",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:07.000Z"
    },
    {
      "id": "a25aa411-ea33-4a7c-9aa5-40a7e9809631",
      "blockId": "2ba79058-5326-443d-ab14-67e9449338b2",
      "name": "Logical data model from the conceptual",
      "type": "Task",
      "content": "Develop the logical data model (the logical data diagram) from the conceptual model given. For each entity list its attributes with a definition, its business identifier, and whether each attribute is required, optional or derived. Resolve many-to-many relationships, name the associative entities, and record every normalisation decision and why. Where subtypes nest, describe the class hierarchy: the tree from the general entity down and what each level adds. Stay independent of any product. The reader is the architect who maps it to physical components.",
      "tags": [
        "task",
        "model",
        "logical",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:08.000Z"
    },
    {
      "id": "1f89abc0-a784-44af-b41a-8394e047aed5",
      "blockId": "e4354209-d491-4ee9-b110-9b30296e28d9",
      "name": "Physical data model considerations",
      "type": "Task",
      "content": "Write the physical data model considerations for the logical model given, at the architecture level: the candidate storage styles for each logical component and why, where denormalisation, partitioning or replication is justified by a stated access pattern, which identifiers become system keys and which business keys must be preserved, how history and effective dating are handled, and what is left to the design team. Name vendors only where the material does. The reader is the solution architect who will design the schema.",
      "tags": [
        "task",
        "model",
        "physical",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:09.000Z"
    },
    {
      "id": "e39e9038-9a05-44b0-8a9e-aed232f61301",
      "blockId": "84795e92-23bc-4479-bd82-e4fc1af708bd",
      "name": "Data model review",
      "type": "Task",
      "content": "Review the data model given against the naming standard, the glossary and the principles. Check that every entity has a definition and an identifier, that relationships have cardinality and meaning, that no attribute hides an entity and no entity is really an attribute, that subtypes are justified, that nothing physical has leaked into a logical model, and that the model answers the business questions it was built for. Write findings the author can act on, and name the three that matter most.",
      "tags": [
        "task",
        "model",
        "review",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:10.000Z"
    },
    {
      "id": "906cf647-16b6-4aab-84bb-1340fe435061",
      "blockId": "e449b89a-dbde-4968-be0a-91ef0138b64c",
      "name": "Reconcile two models of one domain",
      "type": "Task",
      "content": "Reconcile the two models of the same domain given. Pair the entities that mean the same thing under different names, list the entities only one model has and decide whether they are missing or out of scope, find the relationships and rules the models disagree on, and for each difference propose which version to keep and why. Produce the merged entity list and the decisions still needed from the domain owner. Record what each model was built for, because that usually explains the differences.",
      "tags": [
        "task",
        "model",
        "reconciliation",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:11.000Z"
    },
    {
      "id": "e2594b6e-4cd6-4cf2-a846-cae51b9fa15a",
      "blockId": "8be6b534-bc52-489a-9129-5e4d6c662937",
      "name": "Explain a data model to business readers",
      "type": "Task",
      "content": "Explain the data model given to business readers who will never see the diagram. Describe each main entity as a thing the business handles, the relationships as sentences about how the business works, the rules the model enforces and why they matter to them, and the questions the business will be able to answer once systems follow it. Close with the two or three places where the model changes how they work today and what you need them to confirm.",
      "tags": [
        "task",
        "model",
        "communication",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:12.000Z"
    },
    {
      "id": "b3218b09-7175-4cf0-8df3-00b0ea4171e7",
      "blockId": "1b9af371-fec5-4a33-8466-ac52146de274",
      "name": "Model described in words",
      "type": "Format",
      "content": "Describe the model so a colleague could draw it: a list of entities with a one-line definition each, subtypes indented under their supertype; a list of relationships, each as a sentence with both cardinalities; a list of attributes per entity where the task asks for them, marking identifiers in bold; then **Rules the model enforces** and **Questions it leaves open**. No diagram syntax, no code.",
      "tags": [
        "format",
        "model",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:13.000Z"
    },
    {
      "id": "5e6dfa70-1e64-4dcd-a83e-9c15124a610a",
      "blockId": "36bca6e6-dfe9-4691-ade6-18ca19df9293",
      "name": "Plain-language brief for leaders",
      "type": "Format",
      "content": "One page for a business reader: a two-sentence opening that says what this is and what you need from them, then three short sections with bold labels: **What it means for the business**, **What changes**, **What we need decided**. No notation, no acronyms without the words, no more than one short table.",
      "tags": [
        "format",
        "brief",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:14.000Z"
    },
    {
      "id": "b2e19e97-d633-4999-b77b-e9be120ff771",
      "blockId": "c761b7b9-0838-40ad-918c-827e06792955",
      "name": "Logical before physical",
      "type": "Constraints",
      "content": "Keep the layers apart. A conceptual model has entities, relationships and meaning; a logical model adds attributes, identifiers and rules; only a physical model names tables, columns, indexes or products. When a physical choice creeps into a higher layer, move it down and say why it is not an architecture decision.",
      "tags": [
        "constraints",
        "modelling",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:15.000Z"
    },
    {
      "id": "13414e92-2308-4548-ba09-6a8e5d3a11f7",
      "blockId": "b6a6f3ba-6f07-4947-ae65-d1e597347995",
      "name": "Review the artefact, not the author",
      "type": "Constraints",
      "content": "Comment on the model, catalog or diagram, never on the person. Every finding names what is wrong, where, and what right looks like; \"unclear\" and \"weak\" are not findings. Separate what breaks a standard or principle from what you would have done differently, and label the second kind as preference.",
      "tags": [
        "constraints",
        "review",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:16.000Z"
    },
    {
      "id": "b23fe955-0d92-4c61-9ab4-b0f4bb92d9ac",
      "blockId": "29a5abd3-3811-49aa-be6e-1fb2078f1605",
      "name": "Business terms for business readers",
      "type": "Constraints",
      "content": "When the reader is a business person, use the words they use for their customers, products and orders, never entity names, keys, cardinalities or system names. Say \"every order belongs to exactly one customer\", not \"a mandatory one-to-many relationship\". Where a technical term is unavoidable, say it once with its plain meaning beside it.",
      "tags": [
        "constraints",
        "communication",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:17.000Z"
    },
    {
      "id": "9f5fa0db-08bf-4ad2-a497-c851bf0d29ce",
      "blockId": "a7ebbec8-8c4d-46be-8b89-a8bed032b280",
      "name": "Business glossary owner",
      "type": "Role",
      "content": "You are the governance analyst who owns the business glossary. You get business people to agree what their words mean, one term at a time, and you write definitions that decide edge cases rather than describe the obvious. You are patient with disagreement, firm that a term has one definition, and you keep every glossary term linked to the entities and reports that use it.",
      "tags": [
        "role",
        "glossary",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:18.000Z"
    },
    {
      "id": "867c6885-2101-46ff-bbfb-4d4bb26f27ab",
      "blockId": "73a4c9b4-e50d-4aa5-814e-42483c84beac",
      "name": "Glossary extract",
      "type": "Context",
      "content": "The glossary terms, candidate definitions and sources to work from, as they stand today.\n\n{{glossary extract}}",
      "tags": [
        "context",
        "glossary",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:19.000Z"
    },
    {
      "id": "8c4e6f62-6fbb-47bb-89c3-b3a8d588786d",
      "blockId": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
      "name": "Data governance bodies and policies",
      "type": "Context",
      "content": "Who decides about data here and under what policies.\n\n- Decision body: {{governance body}}\n- Data domains and their owners: {{data domains}}\n- Policies and standards sit in {{architecture repository}} and apply to every system that creates or changes enterprise data.",
      "tags": [
        "context",
        "governance",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:20.000Z"
    },
    {
      "id": "7b71d3cb-6ef0-4b3b-8c58-060b4f7585e3",
      "blockId": "1a4fbee5-6561-4d7f-a77d-7109f77b7a1a",
      "name": "Define a business term",
      "type": "Task",
      "content": "Write the glossary definition of {{term}} from the material given. State what the term means in one or two sentences a new employee could apply, what it includes and excludes at the edges, its synonyms and the terms it is often confused with, the business owner, the data entity or attribute that holds it, and the reports or processes that depend on it. Give two examples: one clearly in, one clearly out. The reader is the business owner who will sign it.",
      "tags": [
        "task",
        "glossary",
        "definition",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:21.000Z"
    },
    {
      "id": "78de57c8-c469-4769-8362-c3cac965bd48",
      "blockId": "3ab428e0-e30e-423b-994d-75dcc933b1c6",
      "name": "Resolve a definition conflict",
      "type": "Task",
      "content": "Resolve the conflict over {{term}} in the material given, where two or more parts of the business use it differently. Lay out each meaning, who uses it and for what, where the meanings overlap and where they diverge, and what breaks when they are mixed in one report. Propose one of three outcomes: one definition wins, the term splits into two named terms, or the term is retired. Say what each outcome costs whom. Do not pick quietly; make the recommendation and the decision explicit.",
      "tags": [
        "task",
        "glossary",
        "conflict",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:22.000Z"
    },
    {
      "id": "d76fe848-222e-4188-a676-58c8e9b1b992",
      "blockId": "47c0e418-c8da-4b03-a64e-59b739f213a5",
      "name": "Glossary coverage review",
      "type": "Task",
      "content": "Review how well the glossary given covers the enterprise data: terms used in the models, reports and policies that the glossary does not define, defined terms nobody uses, definitions that describe a system instead of a business meaning, terms with no owner, and groups of terms that are really one. Rank the gaps by how many artefacts and decisions depend on the missing or weak definition.",
      "tags": [
        "task",
        "glossary",
        "review",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:23.000Z"
    },
    {
      "id": "6f2d6140-f7c0-4ab6-97ed-6e18b3a4b62a",
      "blockId": "0f0763a2-f0c6-43f9-b17a-104b68b0a0d6",
      "name": "Glossary standard",
      "type": "Task",
      "content": "Write the glossary standard: what makes a term eligible, what a complete entry contains, how a definition is drafted, challenged and approved and by which roles, how synonyms, abbreviations and retired terms are handled, how terms link to data entities and reports, and how often the glossary is reviewed. The reader is a steward writing their first entry, so each rule comes with an example of compliance.",
      "tags": [
        "task",
        "glossary",
        "standard",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:24.000Z"
    },
    {
      "id": "60e70fee-bc3a-430d-a791-1b1d4ea4933d",
      "blockId": "7b60dbcd-f03c-459b-a6c9-8b3349158083",
      "name": "Definition sign-off request to a business owner",
      "type": "Task",
      "content": "Write the message that asks the business owner of {{term}} to sign off its definition. Give the proposed definition, what it settles that was unclear, who else has agreed, what will use it once it is approved, and the one question you still need them to answer. Tell them how to approve, how to object, and by when. Assume they have two minutes.",
      "tags": [
        "task",
        "glossary",
        "conversation",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:25.000Z"
    },
    {
      "id": "9476c1de-93dd-432b-b75a-746559c1377d",
      "blockId": "efa111d5-02d9-491f-b068-b323eee1b438",
      "name": "Glossary to data model mapping",
      "type": "Task",
      "content": "Map the glossary terms given to the entities and attributes of the data model given. For each term, the entity or attribute that holds it, or the fact that nothing does; for each entity and attribute, the term that defines it, or the fact that none does. List the mismatches: terms held in several places, attributes with no business term, and places where the model's name and the glossary's name differ. These mismatches are the work list for the modeller and the glossary owner.",
      "tags": [
        "task",
        "glossary",
        "mapping",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:26.000Z"
    },
    {
      "id": "a189772a-194c-4c05-8ec0-b441856473cb",
      "blockId": "fa9babc0-71fb-45e4-9060-4e18f63c8179",
      "name": "Glossary entry",
      "type": "Format",
      "content": "Write each entry with bold labels: **Term**, **Definition** (one or two sentences), **Includes and excludes** (the edge cases), **Synonyms and confused with**, **Owner**, **Held in** (entity or attribute), **Used by** (reports and processes), **Examples** (one in, one out), **Status**. Keep every field one or two lines.",
      "tags": [
        "format",
        "glossary",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:27.000Z"
    },
    {
      "id": "c4e291d1-00ee-43df-a0bb-fa18686507cb",
      "blockId": "bc40d393-3b7e-44da-bb73-a5780a711c9b",
      "name": "Mapping table",
      "type": "Format",
      "content": "Present the mapping as a table: source item, target item, relationship or transformation, rule or note, open question. One row per pairing, including rows where one side is empty, marked **Unmapped**. Under the table, list the mismatches, gaps and decisions the task asks for, in the order they should be resolved.",
      "tags": [
        "format",
        "mapping",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:28.000Z"
    },
    {
      "id": "8276a9e3-05d0-41f7-bc28-5153c57ed646",
      "blockId": "fb3fd01a-af33-4475-bc6f-f9e4b9db40b1",
      "name": "Definitions must decide edge cases",
      "type": "Constraints",
      "content": "A definition is finished only when a stranger could use it to decide the hard cases: the trial customer, the cancelled order, the rehired employee. Describe what is in and what is out, not what is obvious. Never define a term by naming the system or report it comes from.",
      "tags": [
        "constraints",
        "definitions",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:29.000Z"
    },
    {
      "id": "f6b67dbf-215f-48ca-a0ba-922b290c94a5",
      "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
      "name": "Decision rights by role, never by person",
      "type": "Constraints",
      "content": "Assign every decision, approval and escalation to a named role or body, never to a named person. One role is accountable for each decision; others are consulted or informed. Where the material names a person, record the role they hold.",
      "tags": [
        "constraints",
        "governance",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:30.000Z"
    },
    {
      "id": "c1cd6767-814a-4f90-ac9b-8771671f0446",
      "blockId": "f03a6b71-1e3c-4ee3-81ad-a5141646ed87",
      "name": "Matrix inputs",
      "type": "Context",
      "content": "The business functions, applications and data entities to relate, with what is known about which function or application creates, reads, updates or deletes each entity.\n\n{{matrix inputs}}",
      "tags": [
        "context",
        "matrix",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:31.000Z"
    },
    {
      "id": "43b430d7-0a5e-428a-8d08-bda4ec118909",
      "blockId": "284c8953-1748-4e3a-8ab8-e23810d49c83",
      "name": "Data entity to business function matrix",
      "type": "Task",
      "content": "Build the data entity to business function matrix from the material given: entities as rows, business functions as columns, and in each cell whether the function creates, reads, updates or deletes the entity. Then read the matrix: entities no function creates, entities several functions create, functions that touch nothing, and entities only read. For each, say what it probably means and what to check. This matrix shows which part of the business owns each entity.",
      "tags": [
        "task",
        "matrix",
        "business function",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:32.000Z"
    },
    {
      "id": "aadc9976-5a01-4344-af19-008616a3f84f",
      "blockId": "a72b9bd7-a435-4693-8076-858c591699ec",
      "name": "Application to data matrix",
      "type": "Task",
      "content": "Build the application to data matrix from the material given: data entities as rows, applications as columns, and in each cell whether the application creates, reads, updates or deletes the entity, or holds a copy. Then read it: entities created in more than one application, entities held in copies with no clear source, applications that create nothing, and entities no application holds. Say what each pattern implies for the system of record and for integration.",
      "tags": [
        "task",
        "matrix",
        "application",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:33.000Z"
    },
    {
      "id": "ca545f45-edb7-4d1e-b516-5a1b710e56bd",
      "blockId": "9149ccd5-cf3f-489e-856b-16a31ae48d09",
      "name": "Analyse the matrices for system of record candidates",
      "type": "Task",
      "content": "Using the entity to function and application to data matrices given, propose the system of record for each entity. Reason from where the entity is created by the function that owns it, where the business trusts the value, and where corrections are made. Where the two matrices disagree, say so. Give each proposal a confidence and the evidence behind it, and list the entities where no candidate is defensible yet.",
      "tags": [
        "task",
        "matrix",
        "system of record",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:34.000Z"
    },
    {
      "id": "7dc1da7a-a942-42a1-a4f6-491b9873df4f",
      "blockId": "7a130057-5ce9-4792-b27f-cd1f4656090b",
      "name": "Gaps and overlaps from the matrices",
      "type": "Task",
      "content": "List the gaps and overlaps the matrices given reveal: entities with no owner function, entities created in several places, applications that duplicate each other's data, functions with no application support, and copies with no stated purpose. For each, state the risk in business terms, the principle it breaks, and whether it is a target architecture gap, a governance gap or a data quality symptom. Order by business impact.",
      "tags": [
        "task",
        "matrix",
        "gaps",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:35.000Z"
    },
    {
      "id": "384bf8b2-6153-4f7a-9a8d-b990c033e180",
      "blockId": "cd464aae-5f1e-4577-846b-cc394b56ed4a",
      "name": "Conversation with application owners about a conflict",
      "type": "Task",
      "content": "Prepare the conversation with the owners of the applications that both create {{entity}}. Set out the facts from the matrices, what each owner will say and why they are partly right, the options (one creates and the other subscribes, both create under a matching rule, a new master), what each option costs each owner, and the decision you will ask them to make or escalate. Write it as the points you will make and the questions you will ask, in order.",
      "tags": [
        "task",
        "matrix",
        "conversation",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:36.000Z"
    },
    {
      "id": "315e59ab-f711-4633-9e69-ff9a5df9cd3d",
      "blockId": "b67001c0-fc33-4b96-8434-947135769dfb",
      "name": "Matrix refresh and repository update note",
      "type": "Task",
      "content": "Draft the note that will record the decision about {{entity}} in the architecture repository and tell the affected owners, written for the option you recommend so it can go out the day the decision is made: what was decided, who decided it, what changes in the matrices and the catalog, which projects must now follow it, and what happens to the other copies. Keep it short enough to be read, and precise enough that an architect in a year understands why.",
      "tags": [
        "task",
        "matrix",
        "repository",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:37.000Z"
    },
    {
      "id": "5ebd729c-e026-4dc8-816b-82084ab48ee4",
      "blockId": "c5a1d7ab-517b-41f0-b395-131d362813d7",
      "name": "Matrix as a table",
      "type": "Format",
      "content": "Present the matrix as a table with the entities as rows and the functions or applications as columns, one short code per cell (C create, R read, U update, D delete, X copy, blank for none) and a legend above it. Below the table, **What the matrix shows**: a numbered list of the patterns found, each with the cells it refers to and what to check.",
      "tags": [
        "format",
        "matrix",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:38.000Z"
    },
    {
      "id": "9fdd30c4-ffc7-4795-b099-9a2489c8cd90",
      "blockId": "e7f8e5c3-c814-46cd-aaf4-0a8dc50485da",
      "name": "A matrix ends with what it shows",
      "type": "Constraints",
      "content": "A matrix is an argument, not a filing exercise. After the grid, state the patterns it reveals and what each one means for ownership, system of record or integration. Never hand over a grid without its reading, and never read into it something the cells do not support.",
      "tags": [
        "constraints",
        "matrix",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:39.000Z"
    },
    {
      "id": "f4841375-1483-4789-9587-8bfb8fe32e77",
      "blockId": "57d4f5ab-f211-4bdd-b93b-1c28b5eb5794",
      "name": "Data flow facts",
      "type": "Context",
      "content": "What is known about how data moves and lives: which systems send which entities to which others, how and how often, where copies are held, and the events that create, change, archive and remove each entity.\n\n{{data flow facts}}",
      "tags": [
        "context",
        "flows",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:40.000Z"
    },
    {
      "id": "1f51e5c1-0f9c-4263-af39-dc5462424603",
      "blockId": "8c816b52-12a0-4de6-a296-d9eeef82127a",
      "name": "Data dissemination diagram",
      "type": "Task",
      "content": "Describe the data dissemination diagram for the entities in scope from the material given: which applications hold each logical data component and which business services use it, which are the source and which receive copies, how the data travels between them (interface, file, replication, manual) and how often, and where a copy is transformed on the way. Show the system of record for each component and every place it is duplicated. State in words what the diagram shows about redundancy and dependency, so the reader does not have to count arrows.",
      "tags": [
        "task",
        "diagram",
        "dissemination",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:41.000Z"
    },
    {
      "id": "6451397d-b374-404d-b19c-7eb3a06f5958",
      "blockId": "0736597a-fa97-4c69-8d8d-1f5a160f9513",
      "name": "Copies and hops analysis",
      "type": "Task",
      "content": "Analyse the copies and hops in the flows given. For each entity, count the places it is held and the number of hops from its system of record to its furthest consumer, say how stale each copy can be and whether anyone reconciles it, and name the copies that exist only because an interface was easier than a shared service. Rank the copies by the harm a disagreement would cause, and propose which to remove, which to make read-only and which to keep with a stated reason.",
      "tags": [
        "task",
        "flows",
        "copies",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:42.000Z"
    },
    {
      "id": "09c605aa-1d24-49df-8809-859f54ae9e44",
      "blockId": "8cbf4f4d-b851-4036-a349-c242685fe420",
      "name": "Data lifecycle diagram for an entity",
      "type": "Task",
      "content": "Describe the data lifecycle diagram for {{entity}} from the material given: the states it passes through from the event that creates it to the event that removes it, the business event and the function that trigger each transition, the system that holds it in each state, and what may and may not be done to it in each state. Mark the states where the entity is shared outside its owning function and the state in which it becomes a record to retain. Say what the diagram shows about where control is lost.",
      "tags": [
        "task",
        "diagram",
        "lifecycle",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:43.000Z"
    },
    {
      "id": "982dbd4d-114f-45df-ba5e-fbb025a1323d",
      "blockId": "ed2bde2c-0b3a-4b6b-9cc5-77964cddc438",
      "name": "Lifecycle events and owning functions",
      "type": "Task",
      "content": "For the lifecycle of {{entity}} given, list each business event that changes its state, the function and role that cause the event, the system that records it, the data that must be complete before the transition is allowed, and the downstream systems that must learn of it. Flag transitions that happen in more than one system, events with no owner, and states the business uses that no system records.",
      "tags": [
        "task",
        "lifecycle",
        "ownership",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:44.000Z"
    },
    {
      "id": "3f898539-733b-4be8-b3c7-f3c9058de0be",
      "blockId": "9e27aa2e-7aaf-4702-800e-211a7e20792c",
      "name": "Cross-domain flow narrative",
      "type": "Task",
      "content": "Write the narrative of how data flows across the domains in the material given, for readers who make decisions but do not read diagrams. Follow one or two entities from creation to retirement, naming where each is mastered, who changes it, where copies live and why, and where the business sees the effects: late reports, mismatched letters, double counting. End with the three changes to the flows that would matter most and who would need to agree.",
      "tags": [
        "task",
        "flows",
        "communication",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:45.000Z"
    },
    {
      "id": "20374457-3aa2-472d-a6fc-a91215ab1dee",
      "blockId": "e8d7db8f-6b09-42d1-9d46-ba13b3463555",
      "name": "Diagram review",
      "type": "Task",
      "content": "Review the diagram described in the draft given against the standards and the repository's other artefacts. Check that every element is named to the standard, that each flow has a direction, a mechanism and a frequency, that systems of record match the catalog, that no element appears that the catalog does not know, that the legend matches the symbols used, and that the diagram answers the concern it was drawn for. State what to change and whether it can enter the repository.",
      "tags": [
        "task",
        "diagram",
        "review",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:46.000Z"
    },
    {
      "id": "7fa8adc7-24cf-4745-8f33-dc060b79d4f4",
      "blockId": "49b29bb2-bba9-4c1a-9b23-cbc8a1245e90",
      "name": "Diagram described for drawing",
      "type": "Format",
      "content": "Describe the diagram so a colleague could draw it: **Elements** (a list, each with its type and label), **Connections** (one line each: from, to, what flows, how, how often), **Layers or groupings** (which elements sit together and why), **Legend** (the symbols and colours to use), then **What to notice** (three sentences on what the drawing shows). No diagram syntax.",
      "tags": [
        "format",
        "diagram",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:47.000Z"
    },
    {
      "id": "d3690ae9-c3ca-4dae-bde5-dc49b3083c9a",
      "blockId": "ff6ed2d2-bf79-4a10-b818-0d3e7f35a3b7",
      "name": "Register table",
      "type": "Format",
      "content": "Present the items as a table: item, description, impact in business terms, owner, proposed action, status. Order by impact, highest first. Under the table, a short paragraph on the items that need a decision from someone outside the team and who that is.",
      "tags": [
        "format",
        "register",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:48.000Z"
    },
    {
      "id": "33dc8203-7be5-4b6b-9921-903e13264963",
      "blockId": "8dd18e9e-98fc-4d94-90f2-51d259362a64",
      "name": "Lifecycle states table",
      "type": "Format",
      "content": "Present the lifecycle as a table: state, event that enters it, function and role that cause the event, system that records it, what may change in this state, next states. One row per state in order. Below the table, list the transitions that cross a system boundary and the states where control or ownership is unclear.",
      "tags": [
        "format",
        "lifecycle",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:49.000Z"
    },
    {
      "id": "7ee58a58-a60c-47ce-a6cc-b3d22973f6d2",
      "blockId": "47faa8b5-bd0f-44c8-928c-6d58feb306ac",
      "name": "Diagrams a colleague can draw",
      "type": "Constraints",
      "content": "Describe every diagram so that a colleague with the description and no other knowledge could draw it and a reader could check it: every element named and typed, every connection with direction, content and mechanism, every grouping explained. A diagram that needs its author beside it to be understood is not finished.",
      "tags": [
        "constraints",
        "diagram",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:50.000Z"
    },
    {
      "id": "fa292b93-eea5-4f76-b8ac-1f6d2ea8f4cf",
      "blockId": "17db55c2-3020-419e-ba30-d3ceec263f00",
      "name": "Data security architect",
      "type": "Role",
      "content": "You are the architect who decides how data is classified and protected across the enterprise, working with the security team but owning the data view. You classify by what harm a disclosure or corruption would do, not by which system holds the data, you design access around roles and purposes, and you make every control traceable to a classification level or a stated obligation. You keep security decisions out of the hands of whichever team happens to build first.",
      "tags": [
        "role",
        "security",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:51.000Z"
    },
    {
      "id": "a632928c-b627-47dd-a6cd-885945ab2543",
      "blockId": "46e2047f-d0a1-4c62-b6c2-e140f53005e8",
      "name": "Classification scheme",
      "type": "Context",
      "content": "The classification levels this enterprise uses, from least to most sensitive, and the rule that the level of a record is the level of its most sensitive attribute.\n\n- Levels: {{classification levels}}\n- A level is assigned by the data owner and recorded in the catalog; handling rules follow the level, not the system.",
      "tags": [
        "context",
        "classification",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:52.000Z"
    },
    {
      "id": "e28b79a6-c7af-458a-ba39-9fb8e0a992ad",
      "blockId": "85be031a-4de2-4428-b414-7d62b9e737e8",
      "name": "Access facts",
      "type": "Context",
      "content": "What is known about who accesses which data, from where and for what: roles, applications, integrations, third parties, and the controls in place today.\n\n{{access facts}}",
      "tags": [
        "context",
        "access",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:53.000Z"
    },
    {
      "id": "bb7e4866-ab40-4174-8d2c-dc0d3fe48afd",
      "blockId": "247c0418-bd3d-415b-a77c-61716537dcea",
      "name": "Classify a domain's entities",
      "type": "Task",
      "content": "Classify the entities and sensitive attributes of {{data domain}} in the material given, using the classification scheme. For each, the level, the reason in terms of the harm a disclosure, corruption or loss would cause and to whom, the attributes that drive the level, and the handling this level requires for storage, transfer, access and disposal. Flag entities whose level depends on context or combination, and the ones the owner must confirm. The reader is the data owner who assigns the level.",
      "tags": [
        "task",
        "classification",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:54.000Z"
    },
    {
      "id": "e3ba87ea-6806-4b57-9f44-599ca2258ea5",
      "blockId": "083f4a5e-82f0-4d02-bc84-45d7c2db2545",
      "name": "Data security diagram",
      "type": "Task",
      "content": "Describe the data security diagram for the components in scope from the material given: which actors and roles may access which data components, through which applications and interfaces, at which classification level, and where the data crosses a trust boundary (between networks, organizations or countries). Show where access is by role and purpose and where it is by system account, and where the same data is reachable by a path with weaker control. Where a grid reads better, add it as a matrix of actors against data components. Say which paths worry you most and why.",
      "tags": [
        "task",
        "diagram",
        "security",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:55.000Z"
    },
    {
      "id": "9ca2b986-1b9f-4252-b716-08c45ab60089",
      "blockId": "5788603e-7b30-44fb-85e5-927a5f5b3bd8",
      "name": "Access patterns and segregation at the architecture level",
      "type": "Task",
      "content": "Define the access patterns for the data in scope from the material given: for each classification level and data component, who may create, read, change and delete, under what purpose, through which channel, and what is logged. State the segregation rules the architecture must enforce: duties that may not sit with one role, data that may not be combined in one store or report, and environments that may not hold production data. Leave the mechanism to the security design; state the rule and why.",
      "tags": [
        "task",
        "security",
        "access",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:56.000Z"
    },
    {
      "id": "54ac0772-0633-4497-93c5-4b4d1d2839cd",
      "blockId": "7751e727-5c03-4abb-9ba3-74cc61893e35",
      "name": "Classification standard",
      "type": "Task",
      "content": "Write the data classification standard: the levels and what each means in terms of harm, who assigns a level and when, how a level is recorded in the catalog and carried through copies and derived data, the handling rules per level for storage, transfer, sharing, access and disposal, how a level is changed and who approves, and how compliance is checked. The reader is a data owner classifying their first entity, so each rule comes with an example.",
      "tags": [
        "task",
        "classification",
        "standard",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:57.000Z"
    },
    {
      "id": "3bfc33cc-65d8-4699-8fcc-4532a45555c2",
      "blockId": "8279b9b7-dd86-476f-b75a-a56a6651f1a4",
      "name": "Classification gap list",
      "type": "Task",
      "content": "List the classification gaps in the material given against the standard: entities with no level, levels that contradict the harm their attributes could cause, copies and derived data sets carrying a lower level than their source, levels assigned by a team that does not own the data, and handling that does not match the level. For each gap name the owner who must act and the risk while it stays open.",
      "tags": [
        "task",
        "classification",
        "gaps",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:58.000Z"
    },
    {
      "id": "69bbb17a-c730-4603-883d-e78ac7837d9d",
      "blockId": "891ac26b-e454-4634-b7a7-9b9230b8e9e3",
      "name": "Security requirements for the architecture requirements specification",
      "type": "Task",
      "content": "Write the data security requirements that go into the architecture requirements specification for {{initiative}}, from the access facts given and the access patterns defined above. Each requirement is one testable sentence that names the data, the level or obligation it comes from, and what the solution must do or prevent. Group them by storage, transfer, access, logging and disposal, and mark which are mandatory and which are preferred. The reader is the solution architect who must show compliance.",
      "tags": [
        "task",
        "security",
        "requirements",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:01:59.000Z"
    },
    {
      "id": "db8f4be2-9e86-44ba-8efe-220c989ba9df",
      "blockId": "ebd01e9a-7ad1-4fc9-b2ef-86ab45d4b5de",
      "name": "Classification table",
      "type": "Format",
      "content": "Present the classifications as a table: entity or attribute, level, reason (the harm and to whom), driving attributes, handling required, owner to confirm. One row per item, grouped by level from most to least sensitive. Below the table, the items whose level depends on context and what would change it.",
      "tags": [
        "format",
        "classification",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:00.000Z"
    },
    {
      "id": "90d5fa2b-b9c7-4f2d-a20f-ca6358d9282c",
      "blockId": "1fa05c97-cfbc-4cb9-9763-832207c9d2f3",
      "name": "Classification follows the scheme",
      "type": "Constraints",
      "content": "Assign levels only from the enterprise's classification scheme and only for the reason it defines: the harm a disclosure, corruption or loss would do. Never classify by the system that holds the data, by who asked, or by habit. A record takes the level of its most sensitive attribute, and a copy or derived set never carries a lower level than its source.",
      "tags": [
        "constraints",
        "classification",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:01.000Z"
    },
    {
      "id": "3722cdea-3c03-4ac0-ab9e-fe593d8aad42",
      "blockId": "fb3a2a91-30e3-4466-8163-7300f764bf30",
      "name": "Least data, least access",
      "type": "Constraints",
      "content": "Design for the least data and the least access that does the job. Every attribute collected, copied or kept needs a stated purpose; every access needs a role and a purpose; every third party gets what its contract requires and nothing more. Where the material gives no purpose, name the data as a candidate for removal rather than keeping it by default.",
      "tags": [
        "constraints",
        "minimisation",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:02.000Z"
    },
    {
      "id": "acfad32a-39d6-4127-8327-5610834c63b4",
      "blockId": "2ddc91bf-3633-49a8-b183-9955d55b03ba",
      "name": "Privacy-minded data architect",
      "type": "Role",
      "content": "You are the data architect who builds privacy into the architecture before the privacy office has to ask. You know which entities carry personal data and why, you design so that the data collected, kept and shared is the least that serves a stated purpose, and you turn the privacy office's and legal's requirements into architecture decisions the delivery teams can follow. You never decide what the law requires; you make sure the architecture can meet whatever legal says it does.",
      "tags": [
        "role",
        "privacy",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:03.000Z"
    },
    {
      "id": "0e857a91-a4af-4756-aa35-e75ec8b0e9bf",
      "blockId": "ad0e847c-e523-4bfb-8b6d-6aee46a5947a",
      "name": "Personal data facts",
      "type": "Context",
      "content": "What is known about the personal data in scope and the design that handles it: the data elements, whose data they are, the purposes given, where the data is collected, held and shared, the flows and systems proposed, and any consents or notices mentioned.\n\n{{personal data facts}}",
      "tags": [
        "context",
        "personal data",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:04.000Z"
    },
    {
      "id": "ec075182-d89e-4d97-8d47-3d8f551f7161",
      "blockId": "53664898-56ea-48d6-ba0f-c5ea9080abe9",
      "name": "Legal and compliance inputs",
      "type": "Context",
      "content": "The requirements, obligations and advice legal, compliance or the privacy office have given, as they gave them. Treat them as the obligations the architecture must meet; do not extend or reinterpret them.\n\n{{compliance inputs}}",
      "tags": [
        "context",
        "compliance",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:05.000Z"
    },
    {
      "id": "f01ad954-bc4d-4a6b-9220-f285b7c479e8",
      "blockId": "ad1cfe2d-9f19-4291-9084-3bd68d858eda",
      "name": "Personal data inventory for an initiative",
      "type": "Task",
      "content": "Build the personal data inventory for {{initiative}} from the material given. For each data element: the category of personal data, whose data it is, the purpose it serves, where it is collected, every system that holds it, who it is shared with inside and outside the enterprise, and the retention and the lawful basis or consent as the material states them. Mark elements with no stated purpose, elements that could identify someone in combination, and special categories that need confirmation from the privacy office. This inventory feeds the record of processing.",
      "tags": [
        "task",
        "privacy",
        "inventory",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:06.000Z"
    },
    {
      "id": "a4f2c8a9-9d8a-4fb1-87db-e78f2f22e5fa",
      "blockId": "761a93aa-539b-4b65-a2dd-435b9f3b45ac",
      "name": "Privacy design review",
      "type": "Task",
      "content": "Review the design in the material given for privacy by design. Check that every personal data element has a purpose and the design collects nothing beyond it, that identifying data is separated or pseudonymised where the purpose allows, that access follows role and purpose, that retention and deletion are designed rather than left to default, that sharing with third parties is named and limited, and that the design can honour access, correction, deletion and portability requests. Write findings the design team can act on and mark the ones that must be fixed before build.",
      "tags": [
        "task",
        "privacy",
        "review",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:07.000Z"
    },
    {
      "id": "d3cf571d-27eb-432c-96cc-f6065d34ceef",
      "blockId": "5a301ca8-1b3f-4f25-9333-5593475ed638",
      "name": "Inputs to a privacy impact assessment",
      "type": "Task",
      "content": "Write the architecture inputs to the privacy impact assessment for {{initiative}} from the material given: the processing described as flows of personal data between systems and parties, the data elements and categories involved, the volumes and subjects affected, the controls the architecture provides (minimisation, pseudonymisation, access, retention, logging), the residual risks the architecture cannot remove, and the points where the privacy office must decide. Present it so the privacy office can assess without reading the models.",
      "tags": [
        "task",
        "privacy",
        "assessment",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:08.000Z"
    },
    {
      "id": "704193e6-6a10-4a3b-b4e9-064f098d927e",
      "blockId": "91ed2950-31b8-49ca-947e-2900ab9b9e74",
      "name": "Cross-border data map",
      "type": "Task",
      "content": "Map where the personal data in the material given is held, processed and accessed by country or region: each system and third party, its location, the data elements it holds, the direction of each transfer and its mechanism, and the support or backup locations that are easy to forget. Mark the transfers the legal inputs say need a safeguard and the ones nobody has looked at. Do not judge whether a transfer is lawful; show legal exactly what moves where.",
      "tags": [
        "task",
        "privacy",
        "transfers",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:09.000Z"
    },
    {
      "id": "55616953-7c5f-47e0-850c-46c34d36e4e6",
      "blockId": "9df498aa-2dd7-4391-bf09-cacd691dd932",
      "name": "Rights-request support design",
      "type": "Task",
      "content": "Design how the architecture supports individuals' rights requests for the data in scope: how a person is identified across systems, how all their data is found including copies and backups, how access and portability requests are assembled, how a correction propagates to every copy, how deletion is carried out and proven where the legal inputs allow it, and what is logged. Name the systems that cannot do this today and the architecture change that fixes each. The reader is the privacy office and the owners of those systems.",
      "tags": [
        "task",
        "privacy",
        "rights",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:10.000Z"
    },
    {
      "id": "b9b8ebb4-adff-448d-b8de-a0ff6dc2862f",
      "blockId": "24ba819e-62e3-4a0f-95a1-ca214744990d",
      "name": "Privacy questions for legal",
      "type": "Task",
      "content": "Write the questions the architecture needs legal or the privacy office to answer for {{initiative}}, from the material given. For each, what the design needs to know, why the answer changes the architecture, what you will assume until it is answered, and the date you need it by. Group them by who answers. Phrase each so that a lawyer can answer it in one sentence without having to ask what you meant.",
      "tags": [
        "task",
        "privacy",
        "questions",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:11.000Z"
    },
    {
      "id": "691bd990-0b30-405d-897e-5114616d35ce",
      "blockId": "b29b60fd-57c8-4eab-8633-4af7ee812a63",
      "name": "Personal data inventory table",
      "type": "Format",
      "content": "Present the inventory as a table: data element, category, whose data, purpose, collected where, held in, shared with, retention, basis as stated. One row per element. Below the table, three short lists: elements with no stated purpose, elements identifying in combination, elements needing privacy office confirmation.",
      "tags": [
        "format",
        "privacy",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:12.000Z"
    },
    {
      "id": "15bdc172-3cc5-463f-bbc6-23c14a2d0417",
      "blockId": "e09b6e29-0691-4d1a-bcc0-a99be4c9f1fc",
      "name": "Obligations come from legal and compliance",
      "type": "Constraints",
      "content": "Regulatory and contractual obligations are inputs the architecture receives from legal, compliance, the privacy office or records management, never conclusions the architect reaches. Record each obligation as it was given, with who gave it. Where none has been given and the design depends on one, state the question and design so that either answer can be met.",
      "tags": [
        "constraints",
        "compliance",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:13.000Z"
    },
    {
      "id": "f554417a-b3f3-42dc-8c4c-e5e206d02c0f",
      "blockId": "3d97eede-ed81-4e36-90f9-821389ee1a0f",
      "name": "Personal data is named, never implied",
      "type": "Constraints",
      "content": "Name every personal data element the design touches, including identifiers, free text, logs, backups and derived data. \"Customer data\" is not an answer; \"name, email address, order history and the notes field agents type into\" is. If you cannot tell whether an element is personal data, list it and say so.",
      "tags": [
        "constraints",
        "privacy",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:14.000Z"
    },
    {
      "id": "51b903e6-cde0-489e-9940-5159d36d9eee",
      "blockId": "8810212d-e373-4b59-857a-0bdf05f04273",
      "name": "Target drivers",
      "type": "Context",
      "content": "The business drivers, requirements and constraints the target data architecture must serve, as the business and the architecture vision stated them, and a summary of the baseline where one exists.\n\n{{target drivers}}",
      "tags": [
        "context",
        "target",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:15.000Z"
    },
    {
      "id": "97dfa013-a65e-4bba-bf98-0cde5555157e",
      "blockId": "2e580993-c1a9-4626-927b-b46e8ceb70d7",
      "name": "Baseline and target descriptions",
      "type": "Context",
      "content": "The baseline and target data architectures to compare or review, as described in the repository or the draft, or the gap analysis already made between them: entities, components, systems of record, flows and principles applied.\n\n{{baseline and target}}",
      "tags": [
        "context",
        "gap analysis",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:16.000Z"
    },
    {
      "id": "2bb58689-bccc-456b-90da-ee76719c0ef4",
      "blockId": "1acd16c8-b347-4bb9-8259-9e1c00c9cd33",
      "name": "Target data architecture description",
      "type": "Task",
      "content": "Write the target data architecture section of the architecture definition document for {{initiative}}, from the drivers given. Describe the target domains and entities, the system of record for each, the logical data components and where they will be realised, the flows that replace today's copies, how master and reference data are managed, and how the target applies each data principle. State the assumptions, the decisions still open, and how the target serves each driver. Write it line by line against the baseline so the gap analysis can read across.",
      "tags": [
        "task",
        "target",
        "document",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:17.000Z"
    },
    {
      "id": "dd4621d7-8d1b-4e32-95cb-39a258624cdc",
      "blockId": "025d6ade-3f08-4cf2-98be-427d71c1eb8a",
      "name": "Target data components and building blocks",
      "type": "Task",
      "content": "Define the data building blocks of the target for {{initiative}}, from the drivers given: the architecture building blocks (the capabilities the target needs, such as a customer master, a reference data service, an archive store), what each must do, which entities and components it holds, the standards it must meet, and the solution building blocks that could realise each, as classes of solution unless the material names products. Mark which blocks exist today or in the repository and can be reused, which are changed and which are new.",
      "tags": [
        "task",
        "target",
        "building blocks",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:18.000Z"
    },
    {
      "id": "4ca4f42b-b828-484a-8921-8ea965842450",
      "blockId": "98ca2e89-3ee8-4238-9551-48f983160a40",
      "name": "Data gap analysis",
      "type": "Task",
      "content": "Carry out the gap analysis between the baseline and target data architectures given. For each entity, component, system of record and flow: retained unchanged, changed, new in the target, or eliminated. For each gap state what has to happen to close it, the data that must be migrated or cleaned on the way, the owner, and the risk if the gap is left. Flag anything in the baseline the target has silently dropped and anything in the target with no baseline predecessor and no stated driver. The gaps are the input to the roadmap.",
      "tags": [
        "task",
        "gap analysis",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:19.000Z"
    },
    {
      "id": "6e3231d9-fa76-4c8e-94b0-2d8e4c519627",
      "blockId": "560e42d3-b5fb-4fe0-abd1-fe6c28ed9354",
      "name": "Impact on business, application and technology architectures",
      "type": "Task",
      "content": "For the data gaps given, state the impact on the other architecture domains: the business functions whose processes or ownership change, the applications that must change their data model, interfaces or role as source or copy, and the technology components that must be added, changed or retired. Name what each domain architect must agree and what will be sent to them as a requirement. Name other architecture work under way that this collides with. Mark the impacts that could stop the target from being realised.",
      "tags": [
        "task",
        "gap analysis",
        "impact",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:20.000Z"
    },
    {
      "id": "eb5c35ae-c8a0-43c0-afdb-70e8c1a68fe5",
      "blockId": "99f49513-c697-4938-be71-ae5e38a0ee87",
      "name": "Candidate work packages for the roadmap",
      "type": "Task",
      "content": "Group the data gaps given into candidate work packages for the roadmap: each a coherent set of changes one team could deliver, with the gaps it closes, the building blocks it delivers, its dependencies on other packages and on the application and technology work, a rough size, and the transition state it leaves behind. Propose a sequence that delivers a stable, usable data architecture at each step and say what forces the order. The reader is the architect assembling the roadmap in the next phase.",
      "tags": [
        "task",
        "roadmap",
        "work packages",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:21.000Z"
    },
    {
      "id": "c8458c49-6be0-4786-85ae-2aeb7cae744e",
      "blockId": "347ec833-1ce1-4214-be3f-bc26d140b993",
      "name": "Target architecture brief for leaders",
      "type": "Task",
      "content": "Write the brief that explains the target data architecture for {{initiative}} to the leadership team. Say what the business will be able to do that it cannot today, what stops working the way it does now, which data will have one home and who will own it, what it costs to get there in effort and disruption rather than in money unless given, the risks and what you are asking them to decide. One page, their words, the ask first.",
      "tags": [
        "task",
        "target",
        "communication",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:22.000Z"
    },
    {
      "id": "65873d9d-23dc-449d-bfd8-87645d6f2d4e",
      "blockId": "fe051bf8-eadc-4444-8a9a-3ac5b9c94d9a",
      "name": "Data architecture stakeholder review and sign-off",
      "type": "Task",
      "content": "Prepare the formal stakeholder review of the data architecture for {{initiative}} before it is finalised. For each stakeholder, take their concerns as given and show where the architecture answers each, in which catalog, matrix, diagram or section, and which it leaves open. Check that every requirement and principle traces to the target, that each building block has its standards chosen, and that the artefacts agree with each other. List the changes any feedback in the material calls for and what is needed to sign off. The reader is the sponsor who accepts it.",
      "tags": [
        "task",
        "review",
        "stakeholders",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:23.000Z"
    },
    {
      "id": "699b73c2-a3ea-4405-b4b8-c3c351e5bb2c",
      "blockId": "be616ff2-260f-4645-9e79-292f9cad4f8a",
      "name": "Data requirements for the architecture requirements specification",
      "type": "Task",
      "content": "Write the data requirements for the architecture requirements specification for {{initiative}}, from the drivers given and the target building blocks defined above. Each requirement is one testable sentence naming the entity or component, what must be true of it (its system of record, definition, quality, availability, retention, access or integration), and the driver or principle it comes from. Group by domain, mark mandatory against preferred, and list the requirements that constrain the application and technology architectures.",
      "tags": [
        "task",
        "requirements",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:24.000Z"
    },
    {
      "id": "a6a39f03-8930-4298-8393-85d277cbd183",
      "blockId": "b998557e-e44e-48c7-bd38-f25c893327fd",
      "name": "Gap analysis table",
      "type": "Format",
      "content": "Present the gaps as a table: item (entity, component, system of record or flow), baseline, target, gap type (retained, changed, new, eliminated), what closes it, owner, risk if left. One row per item, grouped by domain. Where the reader works with a gap matrix (baseline items as rows, target items as columns), give that view too. Below, two lists: items dropped from the baseline without a stated reason, and items new in the target with no stated driver. Where the task also asks for impact, add a second table: gap, business impact, application impact, technology impact, who must agree.",
      "tags": [
        "format",
        "gap analysis",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:25.000Z"
    },
    {
      "id": "67154341-2e6c-4ec1-ae29-ea2499727c25",
      "blockId": "f917c34a-19fd-4064-976f-7b3653115fb0",
      "name": "Stakeholder review record",
      "type": "Format",
      "content": "Open with one paragraph on what is being reviewed and the sign-off asked. Then a table: stakeholder, concern, where it is answered, status (answered, partly, open). Then **Consistency checks** (each passed or failed, with the fix), **Changes from feedback**, and **To sign off**: what remains, who acts and by when.",
      "tags": [
        "format",
        "review",
        "stakeholders",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:26.000Z"
    },
    {
      "id": "279fb793-f9da-455a-b155-530cd6249808",
      "blockId": "aea0a883-3e8a-4908-b9a6-86f2fa430267",
      "name": "Work packages table",
      "type": "Format",
      "content": "Present the work packages as a table: package, gaps closed, building blocks delivered, depends on, rough size, transition state after it. Then **Proposed sequence**: a numbered list with one sentence per step on what forces its place. Then the dependencies on application and technology work that the data team does not control.",
      "tags": [
        "format",
        "roadmap",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:27.000Z"
    },
    {
      "id": "7579f85c-e2d2-4a4c-b4fc-9c72b17de1be",
      "blockId": "b32e7f56-fa34-4b68-a213-637d81104cc5",
      "name": "Every gap names a baseline, a target and an owner",
      "type": "Constraints",
      "content": "A gap is a difference between a named baseline item and a named target item, with an owner who will close it. \"Improve data quality\" is not a gap; \"Customer is created in both the sales system and the billing system today and in the sales system only in the target; the billing owner must switch to subscribing\" is. Nothing enters the roadmap without all three.",
      "tags": [
        "constraints",
        "gap analysis",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:28.000Z"
    },
    {
      "id": "72f68040-a76b-4ea2-a9fc-70de386e2532",
      "blockId": "f63cd43d-9f16-487a-9b3f-3eaf9cc4ae27",
      "name": "Vendor-neutral by default",
      "type": "Constraints",
      "content": "Describe building blocks, platforms and patterns as classes of solution, not products, unless the material names a product the enterprise has already chosen. Never let a product's features define the target; the target states what is needed and the product is judged against it later.",
      "tags": [
        "constraints",
        "neutrality",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:29.000Z"
    },
    {
      "id": "cb7e41d9-adcf-4c40-996b-ff2cdf6f9574",
      "blockId": "fa5b5ce5-317c-4f02-8c5d-96ecb733b3d1",
      "name": "Master data architect",
      "type": "Role",
      "content": "You are the architect responsible for how the enterprise masters its core entities and manages its reference data. You decide which entities deserve mastering and which do not, you choose the architecture style that fits how the business creates and uses each one, and you write the matching and survivorship rules the business can defend. You know that master data fails on ownership before it fails on technology, so you settle ownership first.",
      "tags": [
        "role",
        "master data",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:30.000Z"
    },
    {
      "id": "4ce26b33-f118-4454-8b28-1b1b6ac248ee",
      "blockId": "f89eeae0-b26f-4dcb-9e3c-72247df3d29f",
      "name": "Master data facts",
      "type": "Context",
      "content": "What is known about the candidate master and reference data: the entities, the systems that create and hold them, the volumes and duplication rates if known, the code sets in use, and the complaints the business raises.\n\n{{master data facts}}",
      "tags": [
        "context",
        "master data",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:31.000Z"
    },
    {
      "id": "91251066-ad48-4df3-9378-83f2c118f0b6",
      "blockId": "a0611c47-bbed-4c7f-ab27-c6a6a7e95584",
      "name": "Master data domain assessment",
      "type": "Task",
      "content": "Assess which of the entities in the material given should be managed as master data. For each candidate: how many systems create it, how widely it is shared, how often it changes, the cost of a mismatch in business terms, whether a natural owner exists, and the quality complaints attached to it. Score each on those criteria, rank them, and say which to master first, which to leave in their systems with a named source, and which are reference data rather than master data. The reader is the governance body deciding where to invest.",
      "tags": [
        "task",
        "master data",
        "assessment",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:32.000Z"
    },
    {
      "id": "586b4bf9-3c5d-4b44-b542-57383df05d54",
      "blockId": "54788c00-0020-420a-9537-f666a9546d58",
      "name": "MDM architecture style options",
      "type": "Task",
      "content": "Compare the master data architecture styles for {{entity}} against the facts given: a registry that indexes records left in their systems, consolidation into a downstream golden copy for analytics, coexistence where the hub and the systems both author under synchronisation, and a central hub that is the only place the entity is created. For each, what it requires of the source systems, how it handles conflicts, the latency and effort involved, and the failure it is prone to. Recommend one and say what would make you change your mind.",
      "tags": [
        "task",
        "master data",
        "options",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:33.000Z"
    },
    {
      "id": "60a964ca-0124-454e-b843-748bf82c578c",
      "blockId": "aaaddeec-4c81-4c34-9c8d-b424a6a06794",
      "name": "Golden record and survivorship rules",
      "type": "Task",
      "content": "Define, at the architecture level, how the golden record for {{entity}} is built from the sources given: the attributes that identify a match, the confidence levels and what happens to uncertain matches, the survivorship rule per attribute (most recent, most trusted source, most complete, steward decision) and the reason for each, how a wrong merge is undone, and who approves changes to the rules. Write it so the business owner can agree the rules and the delivery team can implement them without guessing.",
      "tags": [
        "task",
        "master data",
        "golden record",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:34.000Z"
    },
    {
      "id": "506c2a77-e8eb-415b-81f6-5cb00a259f32",
      "blockId": "2d012503-aa64-4530-a36a-ed0fe9f22cc5",
      "name": "Reference data governance",
      "type": "Task",
      "content": "Design the governance of reference data from the code sets given: which code sets are enterprise-wide and which are local, who owns each, how a value is added, changed or retired and how fast, how local codes map to the enterprise set and who maintains the crosswalk, how external standards are adopted and versioned, and how changes reach every system that uses the set. State the rules a system must follow to hold a copy of a code set. The reader is the steward who will run it.",
      "tags": [
        "task",
        "reference data",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:35.000Z"
    },
    {
      "id": "1d004fb2-0d63-44ff-8537-fbd8341649dc",
      "blockId": "b29e83dd-c5f7-4954-9d77-78b3536db6ef",
      "name": "Hierarchy management design",
      "type": "Task",
      "content": "Design how hierarchies over {{entity}} are managed from the facts given: the hierarchies the business uses (ownership, geography, product grouping, organizational), which is the master and which are alternative views, who owns each level and the moves between nodes, how effective dating and history are kept so past reports still reconcile, how a change propagates to the systems and reports that use it, and the controls on orphan and duplicate nodes. State what the architecture guarantees and what the stewards must do.",
      "tags": [
        "task",
        "master data",
        "hierarchies",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:36.000Z"
    },
    {
      "id": "a58072eb-ca5f-4c5e-bbc3-ece39c97f3b9",
      "blockId": "3cac05d5-3023-44ec-822c-9dfa0061fc16",
      "name": "Master data case for the governance body",
      "type": "Task",
      "content": "Write the case to {{governance body}} for mastering {{entity}}, from the assessment and options given: the problem in business terms with its cost, the recommended style and ownership, what the source systems and their owners must change, the stages and the point at which the business sees a benefit, the risks and what contains them, and the decision asked. Write it to be approved or refused in one meeting.",
      "tags": [
        "task",
        "master data",
        "decision",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:37.000Z"
    },
    {
      "id": "96b2e3f4-85ae-4fcb-b68e-e819193700c8",
      "blockId": "17ee1e60-67ae-45c7-b5ae-1523a4302de4",
      "name": "Scorecard layout",
      "type": "Format",
      "content": "Present the scores as a table: items as rows, criteria or dimensions as columns, a score per cell with the evidence or the measure in one or two words, and a total, rank or trend in the last column. Above the table, state the scale and what each column means. Below it, the ranking or the breaches, with one sentence per item on what drove it and who acts. When the task designs a scorecard rather than scoring, show its layout with placeholder figures and list each rule's threshold and target beside it.",
      "tags": [
        "format",
        "scorecard",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:38.000Z"
    },
    {
      "id": "b07ba85d-3f12-4926-93e0-67e9f6c51f84",
      "blockId": "c10ab4f3-c4d3-4727-bba5-5de0d1384bbd",
      "name": "Decision paper for the governance body",
      "type": "Format",
      "content": "Write one page with bold labels: **Decision asked** (one sentence), **Why now** (the problem and its cost), **Options considered** (two to four, one short paragraph each with the trade-off), **Recommendation** (and what would change it), **What it takes** (who does what, in what order), **Risks** (and what contains each), **Next steps if approved**. No appendices described that are not there.",
      "tags": [
        "format",
        "decision paper",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:39.000Z"
    },
    {
      "id": "0fed017d-00f2-49b1-b7dc-ae926facf53e",
      "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
      "name": "Trade-offs both ways",
      "type": "Constraints",
      "content": "No option, pattern or platform is best in general. For each option state what it gains and what it gives up against the facts given, name the situation in which the rejected option would win, and say what would make you change the recommendation. A comparison in which one option has no downside is not finished.",
      "tags": [
        "constraints",
        "options",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:40.000Z"
    },
    {
      "id": "3553f0b0-9a87-40a2-b8f4-c0950bf80c66",
      "blockId": "4cce2fce-5512-4079-be72-2d4b1344ed7c",
      "name": "Data governance lead",
      "type": "Role",
      "content": "You are the lead who designs and runs data governance: who owns which data, who decides, who does the daily work of definitions and quality, and how disputes are settled. You design governance as the lightest structure that makes decisions stick, you give every role a time budget and a measure, and you would rather have three owners who act than thirty who attend. You write charters people can quote back at you.",
      "tags": [
        "role",
        "governance",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:41.000Z"
    },
    {
      "id": "8c46c033-297a-485d-81c4-cb757ef649b8",
      "blockId": "cba513c9-dc10-4578-8b12-177de78056ba",
      "name": "Data roles and people facts",
      "type": "Context",
      "content": "What is known about the people and roles around the data: who owns or claims each domain today, who does stewardship work whether or not it is their title, the bodies that exist, and the disputes and gaps raised.\n\n{{data roles}}",
      "tags": [
        "context",
        "roles",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:42.000Z"
    },
    {
      "id": "d305cab8-7b10-42e0-b238-9c321217d6b3",
      "blockId": "55c20ca5-36fa-4e31-8407-019514924951",
      "name": "Data ownership model",
      "type": "Task",
      "content": "Design the data ownership model from the facts given: the tiers of responsibility (the executive accountable for a domain, the owner who decides definitions and access, the steward who maintains quality and the glossary, the custodian who runs the systems), what each tier decides and does not decide, how ownership is assigned when an entity crosses domains, and how a dispute between owners is escalated and settled. Propose an owner for each domain from the facts, and name the domains where nobody can yet be named.",
      "tags": [
        "task",
        "ownership",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:43.000Z"
    },
    {
      "id": "cfff19bc-eb7a-4a53-af17-8618fd6e768c",
      "blockId": "4089a217-b070-4d94-8d1b-b00c153d4f72",
      "name": "RACI for a data domain",
      "type": "Task",
      "content": "Build the responsibility matrix for {{data domain}} from the roles given: the governance activities as rows (define, classify, approve access, set quality rules, fix quality issues, approve changes to the model, approve new copies, retire data) and the roles as columns, with exactly one accountable role per activity. Explain each assignment that could be disputed, and list the activities where the facts give no one to hold accountable.",
      "tags": [
        "task",
        "raci",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:44.000Z"
    },
    {
      "id": "9fcb7ba6-81cb-470c-8087-fd5161ceceac",
      "blockId": "2a983c59-2c35-4b66-ac10-9b434f506344",
      "name": "Data steward role description",
      "type": "Task",
      "content": "Write the role description for a data steward in {{data domain}}: the purpose of the role in one sentence, its responsibilities for definitions, classification, quality rules, issue handling and the catalog, the decisions it makes alone and the ones it takes to the owner, the time it takes each week, the skills and knowledge needed, how it is measured, and how it relates to the owner and the custodian. Write it so a manager can nominate the right person and that person knows what they signed up for.",
      "tags": [
        "task",
        "stewardship",
        "role",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:45.000Z"
    },
    {
      "id": "22732450-2e19-423b-aaaa-86ecdcc8e60c",
      "blockId": "7bb7272e-4c54-418b-bed3-2b0c85e9c49c",
      "name": "Governance council charter",
      "type": "Task",
      "content": "Write the charter for {{governance body}}: its purpose, the decisions it makes and the ones it delegates, its members by role and the chair, how often it meets and what a meeting must produce, how an item reaches its agenda, how a decision is recorded and communicated, how disputes between owners are brought to it, and how its own effectiveness is reviewed. The reader is a new member who wants to know what the body is for and what is expected of them.",
      "tags": [
        "task",
        "governance",
        "charter",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:46.000Z"
    },
    {
      "id": "351dc480-1b73-403f-b1e6-f1f68d5cb8b4",
      "blockId": "63b7a5b2-05ca-40b3-a8fb-5bf94c005c32",
      "name": "Policy and standards hierarchy",
      "type": "Task",
      "content": "Design the hierarchy of data policies and standards: the policy statements the executive approves, the standards that make each policy concrete, the guidelines that help without binding, and the procedures teams follow. For each level, who approves, how often it is reviewed, how an exception is granted and what a project must show to comply. Place the existing documents given in the hierarchy and list the policies with no standard beneath them and the standards with no policy above them.",
      "tags": [
        "task",
        "governance",
        "policy",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:47.000Z"
    },
    {
      "id": "589d6047-2ffc-4ef8-9c68-075f2bb43b63",
      "blockId": "e42aaa05-320b-4707-8a53-f21233ab0924",
      "name": "Governance operating model paper",
      "type": "Task",
      "content": "Write the paper that proposes the data governance operating model for {{company name}} from the facts given: the bodies and roles, their decision rights, the cadence of meetings and reviews, how work flows from an issue or a project to a decision, how the model fits the architecture governance already in place, the time it asks of the business by role, how it will be measured, and how it starts small and grows. Write it for the executive who must give people the time, with the ask in the first paragraph.",
      "tags": [
        "task",
        "governance",
        "operating model",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:48.000Z"
    },
    {
      "id": "f7d2ba56-69eb-4089-b0eb-2b08dd53ccc0",
      "blockId": "22ab5c73-66b7-456f-982c-510d4fe0d7a8",
      "name": "RACI table",
      "type": "Format",
      "content": "Present the matrix as a table with activities as rows and roles as columns, each cell R, A, C, I or blank, exactly one A per row, and a legend above. Below the table, **Assignments to note**: the cells that could be disputed and why they were set that way, then the rows with no accountable role.",
      "tags": [
        "format",
        "raci",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:49.000Z"
    },
    {
      "id": "9d906cea-20a6-4ea3-b675-911ccb5f140c",
      "blockId": "d73047d1-ee2d-461b-b2df-bc1eb32cd9c7",
      "name": "Role description",
      "type": "Format",
      "content": "Write the role with bold labels: **Purpose** (one sentence), **Responsibilities** (a list of six to ten), **Decides alone**, **Takes to the owner**, **Time** (hours a week or percentage), **Skills and knowledge**, **Measured by** (two or three measures), **Works with** (the roles around it). One page at most.",
      "tags": [
        "format",
        "role",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:50.000Z"
    },
    {
      "id": "b1b31404-c6c0-4845-a231-3496caa1c6b8",
      "blockId": "e2bb791c-3e18-4e40-a9d1-7acff353838d",
      "name": "Operating model description",
      "type": "Format",
      "content": "Describe the operating model under bold labels: **Bodies and roles** (a short list with one line each), **Decision rights** (a table of decisions against who decides), **Cadence** (meetings and reviews with their frequency and output), **How work flows** (from issue or project to decision, in numbered steps), **Escalation**, **Measures**, **How it starts** (the first ninety days). The ask to the reader comes in the opening paragraph.",
      "tags": [
        "format",
        "operating model",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:51.000Z"
    },
    {
      "id": "c20866ba-9a75-427a-a570-91e9141a57ed",
      "blockId": "3894918a-a3e0-4ea3-b834-a542a3f717ae",
      "name": "Every role has time and a measure",
      "type": "Constraints",
      "content": "A governance role without a time budget and a measure is a title. For every role or body proposed, state how much time it takes, from whom, and how the enterprise will know whether it is working. Prefer fewer roles with real time over many roles with none.",
      "tags": [
        "constraints",
        "governance",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:52.000Z"
    },
    {
      "id": "55c7f63a-c2fb-482f-acee-2744c655b2ea",
      "blockId": "fa256d33-57ad-4df3-bc98-446bc66ac0cb",
      "name": "Data quality lead",
      "type": "Role",
      "content": "You are the lead who defines what good data means for the enterprise and makes it measurable. You pick the data elements whose quality matters to a decision, a customer or a regulator, you write rules by dimension that a system can test and a business owner can read, and you trace a quality problem back to the architecture or process that causes it instead of cleaning it downstream again. You report quality as a few numbers with owners, not a wall of red.",
      "tags": [
        "role",
        "data quality",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:53.000Z"
    },
    {
      "id": "0807d12c-acc2-4d6a-a171-2c5fdb2c7533",
      "blockId": "17c66ebf-d307-452b-933c-4f3f0ddf7921",
      "name": "Quality facts",
      "type": "Context",
      "content": "What is known about data quality in scope: the elements and any quality rules already written, the reports and processes that depend on them, the complaints and incidents, any measurements taken, and the thresholds the business has mentioned.\n\n{{quality facts}}",
      "tags": [
        "context",
        "data quality",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:54.000Z"
    },
    {
      "id": "1b650481-e26a-4545-8d6e-20ca36913856",
      "blockId": "f78fd48b-a0af-4e7d-af88-2a5e786d4423",
      "name": "Critical data elements",
      "type": "Task",
      "content": "Identify the critical data elements for {{data domain}} from the material given: the attributes whose error would change a decision, mislead a customer, misstate a figure a regulator sees or break a process. For each, the business use that makes it critical, the system of record, the owner, and the dimensions that matter most for it (completeness, accuracy, validity, consistency, timeliness, uniqueness). Keep the list short enough to measure and defend; say what you left out and why.",
      "tags": [
        "task",
        "data quality",
        "critical elements",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:55.000Z"
    },
    {
      "id": "c06045fa-12f5-417d-bcfd-bba4a7e26a6b",
      "blockId": "aa9deb55-2045-43e2-af83-82914d7d2768",
      "name": "Quality rules by dimension",
      "type": "Task",
      "content": "Write the quality rules for the critical elements given, by dimension. Each rule states the element, the dimension, the test in words a business owner can read and a system can implement (what a complete, valid, consistent or timely value looks like), the reference it is checked against, the point in the lifecycle where it is checked, and the owner who acts on a failure. Separate rules that must hold at creation from rules checked afterwards. Do not write the check itself; define what it must test.",
      "tags": [
        "task",
        "data quality",
        "rules",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:56.000Z"
    },
    {
      "id": "6b845fb3-e171-4b39-868a-751365a31986",
      "blockId": "9725a903-8c50-4525-9401-80af5456a203",
      "name": "Thresholds and quality targets",
      "type": "Task",
      "content": "Set the thresholds and targets for the quality rules given: for each rule, the level below which the business must act, the target level for the year, how the threshold was reasoned from the use of the data (a regulatory figure tolerates less than a marketing list), and what action a breach triggers and who takes it. Say where the material gives no basis for a number and propose how to find one. The reader is the owner who must agree to be measured.",
      "tags": [
        "task",
        "data quality",
        "thresholds",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:57.000Z"
    },
    {
      "id": "3800670d-d002-47f3-9f5c-efbd131f5b3c",
      "blockId": "dc451da3-5c22-4940-a7c8-ac5d82106b94",
      "name": "Quality scorecard design",
      "type": "Task",
      "content": "Design the quality scorecard for {{data domain}} from the rules and thresholds given: the elements and dimensions shown, how each score is calculated and over what population and period, how trends and threshold breaches are shown, who sees which view (owner, steward, executive), how often it is produced and from where, and what happens when a score is red. Keep it to the few numbers that drive action. State what the scorecard cannot tell its readers.",
      "tags": [
        "task",
        "data quality",
        "scorecard",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:58.000Z"
    },
    {
      "id": "107c708c-b6ca-47df-9c89-87bfb9a195c5",
      "blockId": "648c8c8b-b24f-45c0-9d33-ece3f9fc7002",
      "name": "Root cause at the architecture level",
      "type": "Task",
      "content": "Trace the quality problems in the material given to their causes in the architecture and the process rather than the symptom: an entity created in two systems with no matching rule, a copy refreshed less often than its use demands, a field with no definition so each team fills it differently, a mandatory value nobody has at the point of entry, a reference set that drifted. For each, the cause, the evidence, the architecture or governance change that removes it, and whether cleaning downstream is worth doing meanwhile.",
      "tags": [
        "task",
        "data quality",
        "root cause",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:02:59.000Z"
    },
    {
      "id": "68807618-7e2d-40e1-abce-12305e614228",
      "blockId": "b1cc71e2-b4e1-4c21-8d19-1821167fc76b",
      "name": "Quality remediation plan",
      "type": "Task",
      "content": "Write the remediation plan for the quality problems given: for each, the fix at the source, the interim cleansing if any, the owner, the dependency on other changes, the measure that will show it worked and when it should be seen. Order the plan by the harm removed per unit of effort, group fixes that share a cause, and say which fixes need a decision from the governance body before they can start. The reader is the owner who will be held to it.",
      "tags": [
        "task",
        "data quality",
        "remediation",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:00.000Z"
    },
    {
      "id": "346726a1-1a2c-4a0e-819b-0c5477937635",
      "blockId": "7299de5e-7ba7-4600-b3fd-fc3104d53ff1",
      "name": "Quality requirements for the architecture requirements specification",
      "type": "Task",
      "content": "Write the data quality requirements for the architecture requirements specification for {{initiative}} from the material given: for each critical element, the dimensions and thresholds the solution must meet, where in the flow quality is checked and enforced, how failures are reported and to whom, and what the solution must do with data that fails. One testable sentence per requirement, grouped by element, marked mandatory or preferred. The reader is the solution architect who must design to them.",
      "tags": [
        "task",
        "data quality",
        "requirements",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:01.000Z"
    },
    {
      "id": "c6c89c9e-bb17-4a76-a77c-3a8575b57965",
      "blockId": "d530c9de-423d-430a-9388-5f114863b155",
      "name": "Rule specification table",
      "type": "Format",
      "content": "Open with the critical elements, one line each: the use that makes it critical, its system of record and owner. Then present the rules as a table: element, dimension, rule in words, reference checked against, checked when, owner on failure. One row per rule, grouped by element. Below the table, the rules whose reference does not yet exist and what would have to be created.",
      "tags": [
        "format",
        "rules",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:02.000Z"
    },
    {
      "id": "412fa301-6376-4dee-857d-ea4fce429704",
      "blockId": "59502c57-732a-49d5-85c5-08da80e44444",
      "name": "A quality rule names element, dimension, test and threshold",
      "type": "Constraints",
      "content": "A quality rule is not finished until it names the data element, the dimension it measures, the test in words that both a business owner and a developer would read the same way, and the threshold at which someone acts. \"Customer data must be accurate\" is a wish; \"Customer postal code is valid when it matches the postal reference for its country, measured on records changed in the month, action below 98 percent\" is a rule.",
      "tags": [
        "constraints",
        "data quality",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:03.000Z"
    },
    {
      "id": "59dd9eb7-81a6-4333-9fe5-048f6a9b1591",
      "blockId": "9a146d4b-ac42-4af8-a3ca-d449ca23cc22",
      "name": "Stay at the enterprise level",
      "type": "Constraints",
      "content": "Define what must be true of the data, where it is checked and who acts; leave how it is built to the delivery and data engineering teams. No code, no queries, no pipeline steps, no product configuration. When a task tempts you lower, state the requirement and name the team that designs the mechanism.",
      "tags": [
        "constraints",
        "altitude",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:04.000Z"
    },
    {
      "id": "4c998224-eccd-459b-90d4-186764e612a8",
      "blockId": "6f508b76-7f2c-40f6-acec-8c583d9ad6e6",
      "name": "Metadata and lineage architect",
      "type": "Role",
      "content": "You are the architect who decides what the enterprise records about its data and how it traces where data came from. You scope lineage to the decisions and obligations that need it instead of trying to trace everything, you distinguish the business, technical and operational metadata and who maintains each, and you design the metadata architecture so that catalogs, models and glossaries describe one truth. You treat metadata as data: owned, defined and governed.",
      "tags": [
        "role",
        "metadata",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:05.000Z"
    },
    {
      "id": "fb6d5079-f458-4023-b861-539f7b60797e",
      "blockId": "ac25a2db-3a0d-4467-93e8-cedf6cab82c0",
      "name": "Lineage facts",
      "type": "Context",
      "content": "What is known about the data's origins and movements for the question in hand: the sources, the systems and transformations between them, the reports or outputs at the end, the metadata already recorded about them, and, where the question is about a change, the change itself.\n\n{{lineage facts}}",
      "tags": [
        "context",
        "lineage",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:06.000Z"
    },
    {
      "id": "65c42e9d-0aa9-46ea-bd32-21f04878b4c7",
      "blockId": "0017840f-988f-4560-8871-09ede87d9cbd",
      "name": "Lineage scope and granularity",
      "type": "Task",
      "content": "Decide the scope and granularity of lineage for {{initiative}} from the material given: which outputs, decisions and obligations need lineage, how far back it must be traced (to the system of record, to the point of capture, or to the external source), at what level (data set, entity, attribute or value), whether business lineage in plain terms or technical lineage through each transformation is needed for each, and how it will be kept current. State what you deliberately leave untraced and why. The reader is the sponsor paying for the work.",
      "tags": [
        "task",
        "lineage",
        "scope",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:07.000Z"
    },
    {
      "id": "64565b7c-3a80-445c-8ff4-c398349be499",
      "blockId": "b405485e-62f4-462f-b74f-1b154839501c",
      "name": "Lineage for a critical report",
      "type": "Task",
      "content": "Trace the lineage of {{critical report}} from the material given: each figure on the report back through the transformations, aggregations and joins to the entities and attributes in the systems of record, naming the system, the owner and the rule applied at each hop, the reference data used, and the points where a manual step or a spreadsheet intervenes. Mark the hops the evidence supports and the ones you inferred. End with where the report is most exposed to a silent error.",
      "tags": [
        "task",
        "lineage",
        "report",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:08.000Z"
    },
    {
      "id": "871d8071-2970-43ec-aafd-f462fa348115",
      "blockId": "9cefd582-c716-49d7-a853-37d7e0db1762",
      "name": "Metadata architecture",
      "type": "Task",
      "content": "Design the metadata architecture for {{company name}} from the facts given: the kinds of metadata to manage (business terms and definitions, models and classifications, technical structures, lineage, operational facts such as freshness and quality scores), the source of truth for each kind and who maintains it, how the catalog, the glossary, the models and the repository relate and stay consistent, how metadata is captured from systems against how it is written by people, and how consumers find and use it. Describe it as capabilities and flows, not as a product.",
      "tags": [
        "task",
        "metadata",
        "architecture",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:09.000Z"
    },
    {
      "id": "f881b561-2f83-47cd-8e49-570a6004b11d",
      "blockId": "5cf34304-5325-4e64-b3c6-df252bab83a6",
      "name": "Metadata standard",
      "type": "Task",
      "content": "Write the metadata standard: the minimum metadata every data set, entity and report must carry (owner, definition, classification, system of record, freshness, retention, lineage to source), who records each item and when in a project's life, the naming and identifier rules that let metadata from different tools be joined, how completeness is measured and reported, and what a project must show before its data goes live. The reader is the project lead who must comply, so every rule has an example.",
      "tags": [
        "task",
        "metadata",
        "standard",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:10.000Z"
    },
    {
      "id": "b30bd8ee-e33b-4928-b7b9-9a450841fbc9",
      "blockId": "48b64607-8873-460a-bfd1-949c8abe602c",
      "name": "Lineage gap assessment",
      "type": "Task",
      "content": "Assess the gaps in lineage for the outputs in the material given: hops with no recorded source, transformations whose rule nobody can state, manual steps and spreadsheets in the chain, reference data with no version, systems that cannot expose what they do, and lineage recorded in a tool nobody keeps current. For each gap say which output and obligation it exposes, the risk while it stays open, and the cheapest way to close it, from documenting a rule to re-architecting a flow.",
      "tags": [
        "task",
        "lineage",
        "gaps",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:11.000Z"
    },
    {
      "id": "a4524f9e-2193-4ac0-88a2-6982a8b6b56e",
      "blockId": "57767605-4e7f-4d80-a75c-8862f21c3a95",
      "name": "Impact analysis with lineage",
      "type": "Task",
      "content": "Using the lineage given, assess the impact of the change described in the material: every data set, report, interface and process downstream of the changed element, who owns each, what breaks or changes meaning, the consumers who must be told and when, and the order in which the change should ripple. Separate certain impacts from likely ones, and list the downstream uses the lineage does not cover where impact is unknown.",
      "tags": [
        "task",
        "lineage",
        "impact",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:12.000Z"
    },
    {
      "id": "05994a6b-5cb9-49fe-b648-211eddb50468",
      "blockId": "e616a106-d7d9-499c-988f-eebfc7f9bd0e",
      "name": "Lineage states its granularity and evidence",
      "type": "Constraints",
      "content": "Every lineage statement says at what level it holds (data set, entity, attribute or value) and what evidence supports it: observed in the system, read from code or configuration, documented by the owner, or inferred by you. Mark inferred hops as such. Lineage presented as fact without evidence is a risk dressed as an asset.",
      "tags": [
        "constraints",
        "lineage",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:13.000Z"
    },
    {
      "id": "77e4f337-4c53-4210-9a9c-a0f36642e4b1",
      "blockId": "c479b2ab-8667-4f8e-a438-9fdb045cb8ae",
      "name": "Analytics platform architect",
      "type": "Role",
      "content": "You are the architect who sets the target state for how the enterprise stores, serves and shares data for analysis. You know the warehouse, the lake, the lakehouse and the mesh as patterns with trade-offs rather than as camps, you fit the pattern to how the organization is shaped and skilled, and you define data products by their consumers and promises before their technology. You keep vendors out of the target until the target is agreed.",
      "tags": [
        "role",
        "platform",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:14.000Z"
    },
    {
      "id": "adb448bd-56c5-42f4-acea-dd66e7646566",
      "blockId": "c5619954-c2e4-4418-a511-e630bc755dd7",
      "name": "Platform facts",
      "type": "Context",
      "content": "Today's analytics platform and what is known about the needs it must meet.\n\n- Platform today: {{analytics platform}}\n- Needs, consumers, volumes, skills, constraints, and the data product to specify where there is one: {{platform facts}}",
      "tags": [
        "context",
        "platform",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:15.000Z"
    },
    {
      "id": "4cf3feac-af7c-4b6f-a824-00d2574bffc2",
      "blockId": "560ad415-0fcb-4134-a28c-ebc2cca59b15",
      "name": "Platform options compared",
      "type": "Task",
      "content": "Compare the platform patterns for {{company name}} against the facts given: a central warehouse of modelled, governed data; a lake of raw and curated data at scale; a lakehouse, open storage managed like a warehouse; and a mesh, domain-owned data products on a shared platform under federated governance. Say where a metadata-driven fabric over existing stores fits. For each, what it demands of the organization, what it does well and badly against the needs, its typical failure and cost shape. Recommend one or a combination and what would change it.",
      "tags": [
        "task",
        "platform",
        "options",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:16.000Z"
    },
    {
      "id": "5f368dc0-dac6-4262-afe1-23e0bf1f7764",
      "blockId": "9d691cd2-af2f-4051-9c0f-6e6ec5c7b7a0",
      "name": "Platform target state description",
      "type": "Task",
      "content": "Describe the target analytics platform state for {{company name}} from the facts given, as layers and responsibilities rather than products: how data is ingested from the systems of record, where raw, curated and served data live, how models and definitions from the enterprise data architecture are applied, how governance, classification and access carry through, how data products or marts are published and found, and who owns each layer. State the principles applied and the decisions left open.",
      "tags": [
        "task",
        "platform",
        "target",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:17.000Z"
    },
    {
      "id": "26afdc92-8019-4b64-b3f1-67163152a90b",
      "blockId": "24af1ca3-e8d7-468b-baca-91c68f010a62",
      "name": "Specify a data product",
      "type": "Task",
      "content": "Specify the data product described in the material given: its name and the domain that owns it, the consumers and the questions or processes it serves, the entities and attributes it contains with their definitions from the glossary, the interfaces through which it is consumed, its promises on freshness, quality, availability and support, its classification and access rules, its lineage to the systems of record, and how it is versioned and retired. Write it so a consumer can decide whether to rely on it and the owning team knows what they committed to.",
      "tags": [
        "task",
        "platform",
        "data product",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:18.000Z"
    },
    {
      "id": "e4021e6d-692d-4d0a-bdcf-704ab068dcc6",
      "blockId": "964b0905-a561-4666-84e2-f9ea17212ec0",
      "name": "Domain and platform team split",
      "type": "Task",
      "content": "Define the split of responsibilities between the domain teams and the central platform team for the target given: who ingests, models, publishes and supports data, who sets and who enforces standards, what the platform team provides as self-service and what it does on request, how a domain becomes able to own its products and what happens to domains that cannot, and how conflicts over shared entities are settled. Write it as the agreement both sides will be held to.",
      "tags": [
        "task",
        "platform",
        "operating model",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:19.000Z"
    },
    {
      "id": "6068081b-221b-4dbf-b003-97f345bf073d",
      "blockId": "f1445ae7-d314-4bd2-be24-4b38018fd28d",
      "name": "Consumption patterns and serving layer",
      "type": "Task",
      "content": "Define the consumption patterns the target platform must serve from the facts given: governed reporting from certified figures, self-service analysis by business analysts, data science on raw and curated data, operational use through interfaces, and sharing with partners. For each, the data it needs and at what latency, the access and classification rules that apply, the layer it is served from, and what the consumer must do in return. Flag the patterns the facts show demand for that the target does not yet serve.",
      "tags": [
        "task",
        "platform",
        "consumption",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:20.000Z"
    },
    {
      "id": "ff0fceb1-9372-462d-8413-af82a904d21f",
      "blockId": "c9682d8b-3b69-4a33-9c41-a4c27723b6c7",
      "name": "Platform transition stages",
      "type": "Task",
      "content": "Plan the transition from today's platform to the target given in stages: what each stage delivers that consumers notice, which data and consumers move and which stay, how the old and new run side by side and how long, how trust in the new figures is established before the old are switched off, the skills and roles each stage needs, and the point at which a stage can be called done. Say what forces the order and where a stage could be skipped if the facts changed.",
      "tags": [
        "task",
        "platform",
        "transition",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:21.000Z"
    },
    {
      "id": "e7d061ff-ea85-4e68-9298-b9b99310313a",
      "blockId": "ea6dcdf9-1672-4221-884a-1263c473ab87",
      "name": "Options comparison table",
      "type": "Format",
      "content": "Present the options as columns and the criteria as rows, each cell one or two short sentences on how the option fares. Above the table, state the criteria and why they matter here. Below it, **Recommendation** with the reasons in three sentences, **What would change it**, and **The option that nearly won** and when it would.",
      "tags": [
        "format",
        "options",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:22.000Z"
    },
    {
      "id": "f25ffce4-b195-4cc4-91b0-864709d8b4f1",
      "blockId": "799c8020-89ea-4700-a7ad-cfea133e88f5",
      "name": "Data product specification",
      "type": "Format",
      "content": "Write the specification with bold labels: **Name and owner**, **Consumers and what they use it for**, **Contents** (entities and attributes with definitions), **Interfaces**, **Promises** (freshness, quality, availability, support), **Classification and access**, **Lineage to source**, **Versioning and retirement**. Each part a short list or paragraph; nothing longer than a page in all.",
      "tags": [
        "format",
        "data product",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:23.000Z"
    },
    {
      "id": "e33156f1-471b-48fa-8a97-6aa5c30e60b2",
      "blockId": "7d3c9eb8-f61b-4e69-aa80-41ec485483a4",
      "name": "Every data product names its consumers",
      "type": "Constraints",
      "content": "A data product exists for named consumers with a stated use; without them it is a data set. Every product names who consumes it, for what, and the promises they rely on. Never specify a product because the data is available; specify it because someone will depend on it.",
      "tags": [
        "constraints",
        "data product",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:24.000Z"
    },
    {
      "id": "b31c472e-90da-4813-aa85-a1d1bc0f31ac",
      "blockId": "305f167e-5b4f-46e6-b032-ef078e7d7953",
      "name": "Data integration architect",
      "type": "Role",
      "content": "You are the architect who decides how data moves between the enterprise's systems and domains. You choose the pattern for each flow from what the data is, how fresh it must be and who owns it, not from what the last project used; you know when a shared model pays for itself and when it is a tax; and you insist that every exchange carries the meaning the glossary gives it. You design integration as part of the data architecture, so a copy never appears without a reason and an owner.",
      "tags": [
        "role",
        "integration",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:25.000Z"
    },
    {
      "id": "27641041-6f78-4ebc-854e-2aa11bf613c5",
      "blockId": "1181babd-934d-488c-b845-ffe6896622ba",
      "name": "Integration facts",
      "type": "Context",
      "content": "What is known about the flows in question: the systems at each end, the entities exchanged, the direction, the freshness the consumers need, the volumes, the mechanisms used today and the problems reported.\n\n{{integration facts}}",
      "tags": [
        "context",
        "integration",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:26.000Z"
    },
    {
      "id": "29c03f49-7961-41d7-bbd4-a8d124499582",
      "blockId": "84ea229d-5190-4baf-9592-5fc06cd58ad1",
      "name": "Integration pattern per flow",
      "type": "Task",
      "content": "For each flow in the material given, choose how the data moves and justify it: scheduled batch, change data capture, event streaming, request and reply, replication, or virtual access without a copy. Reason from the freshness needed, the volume, whether the consumer needs the data at rest, who owns the entity, and what happens when the flow fails. State the pattern, why, the alternatives rejected and what would change the choice. Leave interface design and middleware to the application architecture; the reader is the solution architect who designs them.",
      "tags": [
        "task",
        "integration",
        "patterns",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:27.000Z"
    },
    {
      "id": "5e4d5b39-0539-4b0a-b8ae-19f12e2b8fde",
      "blockId": "24153937-bdc1-4568-8368-0aa8650e2a36",
      "name": "Canonical model or point to point",
      "type": "Task",
      "content": "Decide, for the entities and flows given, whether the enterprise should exchange data through a shared canonical model or through direct, pairwise interfaces. Set out what a canonical model costs to build and keep current, which entities are exchanged between enough parties to justify it, where a pairwise interface is cheaper and good enough, and the middle path of a canonical model for the few shared entities only. Recommend a position, say what it commits the enterprise to, and name the governance it requires. The reader is the governance body that will adopt it as a standard.",
      "tags": [
        "task",
        "integration",
        "canonical",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:28.000Z"
    },
    {
      "id": "540b1057-1d8b-4b47-80b7-00bba01c8f97",
      "blockId": "02676f1d-d4e1-4ca3-9ad0-b3ced6025d07",
      "name": "Data exchange standard and event governance",
      "type": "Task",
      "content": "Write the data exchange standard: how an exchanged entity is identified across systems, which definitions and reference codes every exchange must use, how an interface or message schema is versioned and how long old versions live, who owns a schema and who may change it, what a producer must publish about an event or message (meaning, source, freshness, classification), and what a consumer must do before relying on it. Each rule with an example. The reader is the integration team adopting it.",
      "tags": [
        "task",
        "integration",
        "standard",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:29.000Z"
    },
    {
      "id": "60eebe63-802d-4641-b0f1-d4632a49d7f4",
      "blockId": "97713055-6744-4383-9f7b-a42a67884350",
      "name": "Data contracts between domains",
      "type": "Task",
      "content": "Draft the data contract between the producing domain and the consuming domains for the exchange described in the material given: the entities and attributes supplied with their glossary definitions, the identifier used, the freshness and availability promised, the quality rules the producer guarantees at hand-over, the classification and the access the consumer is granted, how changes are announced and how long consumers have to adapt, and who to call when it breaks. Write it as the agreement both sides will sign, in business terms with the technical detail beneath.",
      "tags": [
        "task",
        "integration",
        "contracts",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:30.000Z"
    },
    {
      "id": "6697e275-1eef-4acb-b823-dda97ff7664b",
      "blockId": "59653fe0-fd98-441b-8989-1fcc32f30e01",
      "name": "Integration principles",
      "type": "Task",
      "content": "Write the integration principles for enterprise data: the rules every flow must follow, such as the system of record publishes and others subscribe, data is exchanged with its meaning and classification, no copy without an owner and a reason, interfaces carry the glossary's terms, schemas are versioned and old versions retired, and failures are visible to the consumer. For each, the statement, the rationale in business terms and the implications for project teams. Reconcile each with the enterprise data principles in force and say where they add rather than repeat.",
      "tags": [
        "task",
        "integration",
        "principles",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:31.000Z"
    },
    {
      "id": "644960d8-28e4-461f-a3bc-eda40fb54c04",
      "blockId": "b49977a4-19e8-48b7-a49e-e0b1f6599f89",
      "name": "Integration gap list",
      "type": "Task",
      "content": "List the integration gaps in the flows given against the principles and the target: copies made from copies, consumers fed from a system that is not the system of record, flows with no owner, point-to-point interfaces that will multiply as systems are added, exchanges with no agreed definition or code set, undocumented manual transfers, and flows whose freshness does not match the use. For each gap, the risk in business terms, the pattern or change that closes it, the owner, and whether it belongs to a roadmap work package or to run-the-business fixes.",
      "tags": [
        "task",
        "integration",
        "gaps",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:32.000Z"
    },
    {
      "id": "72b4b8d2-845c-4a80-8314-d206b579489c",
      "blockId": "019d2011-a61b-4e18-bd78-f96fcfda6260",
      "name": "Pattern recommendation per interface",
      "type": "Format",
      "content": "For each flow, a bold line naming the source, the target and the entity, then four short labelled lines: **Pattern**, **Why** (the facts that decide it), **Rejected** (the alternatives and why not), **Would change if**. Then a closing table of all flows with their patterns, and a short list of the flows that share a mechanism and could share an implementation.",
      "tags": [
        "format",
        "integration",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:33.000Z"
    },
    {
      "id": "f6ab4cf9-e126-42de-8dff-a74ca3ac0f21",
      "blockId": "81d973c7-5052-4287-b834-5d403632295c",
      "name": "Data migration architect",
      "type": "Role",
      "content": "You are the architect who designs how data moves from the systems being retired to the systems that replace them. You decide the strategy before anyone writes a mapping, you map at the entity level so the delivery team maps at the field level, you decide what is cleaned and what is left behind, and you treat reconciliation as the definition of done. You know a migration is a business event with a business owner, not a technical task.",
      "tags": [
        "role",
        "migration",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:34.000Z"
    },
    {
      "id": "d4471f08-ad84-4028-9e9f-f970f4964bdb",
      "blockId": "279f882b-b953-44da-b309-1ad64b392cf4",
      "name": "Migration facts",
      "type": "Context",
      "content": "What is known about the migration: the source and target systems, the entities and volumes, the history that must come across, the cutover constraints, the known quality problems, and the people and dates involved.\n\n{{migration facts}}",
      "tags": [
        "context",
        "migration",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:35.000Z"
    },
    {
      "id": "c6dfd43d-c3a4-47da-a96b-6510cec384d0",
      "blockId": "a15e84e8-3b7a-49e0-be7d-b86be6f04652",
      "name": "Migration strategy options",
      "type": "Task",
      "content": "Compare the migration strategies for {{initiative}} against the facts given: a single cutover, a phased move by entity, by business unit or by region, and a period of coexistence with both systems live and synchronised. For each, what it demands of the business and the systems, the risk it carries and where, how long the old system must stay, what it costs in effort and disruption, and the failure it is prone to. Recommend one and name the facts that would change it. The reader is the programme board that must choose.",
      "tags": [
        "task",
        "migration",
        "strategy",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:36.000Z"
    },
    {
      "id": "131d404b-ad5e-42f0-85b4-b1f89f92a6d8",
      "blockId": "24cff9e0-4bda-4113-a1b2-b8b8d38782b3",
      "name": "Data migration diagram",
      "type": "Task",
      "content": "Describe the data migration diagram for {{initiative}} from the facts given: the source systems and the entities leaving each, the staging and transformation steps between, the target systems and components receiving each entity, the reference data and master data the migration depends on, the direction and sequence of each move, and the data that is archived rather than migrated. Mark the points where data is cleaned, enriched or reconciled. Say what the diagram shows about the order and the dependencies.",
      "tags": [
        "task",
        "migration",
        "diagram",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:37.000Z"
    },
    {
      "id": "c63162b6-406b-4bf0-a217-fa293802d609",
      "blockId": "0023ede6-87a7-4456-b54a-29545928059e",
      "name": "Entity-level source to target mapping",
      "type": "Task",
      "content": "Map the entities from the sources to the targets given at the entity and key attribute level: for each source entity, the target entity it becomes or the fact that it is dropped, the identifier mapping and how duplicates across sources are resolved, the attributes whose meaning changes, the reference codes that must be translated, the history to bring and how far back, and the rules still unknown. Leave field-level transformations to the delivery team but give them nothing to guess about meaning.",
      "tags": [
        "task",
        "migration",
        "mapping",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:38.000Z"
    },
    {
      "id": "865f4578-be37-490b-ab87-7de294ba1a14",
      "blockId": "ef961720-478c-4d1c-936f-03f973eb926d",
      "name": "Cleanse before or after decision",
      "type": "Task",
      "content": "Decide, for the quality problems in the facts given, what is cleaned in the source before migration, what is transformed on the way, what is cleaned in the target afterwards and what is accepted as is. Reason from who owns the data and can fix it, whether the target will reject it, whether the problem is visible to customers or regulators, and whether the source is still worth fixing. State the decision per problem, its owner, and the deadline relative to cutover.",
      "tags": [
        "task",
        "migration",
        "cleansing",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:39.000Z"
    },
    {
      "id": "4adeef6f-47b5-4b5c-aabc-594dd6c742a2",
      "blockId": "27cefa46-0a31-4d2f-83dc-546213f721fe",
      "name": "Reconciliation and cutover approach",
      "type": "Task",
      "content": "Define the reconciliation and cutover approach for {{initiative}}: the counts, totals and samples that prove each entity arrived complete and correct, who signs off each and against what tolerance, the dress rehearsals and what each must prove, the cutover sequence with its freeze, the point of no return and the criteria for going back, how differences found after cutover are handled, and how long the source stays readable. Write it so the business owners know what they are signing.",
      "tags": [
        "task",
        "migration",
        "reconciliation",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:40.000Z"
    },
    {
      "id": "b4170b37-0a4f-4378-8771-ff5aa02c40a8",
      "blockId": "11302507-82fa-4925-ab17-31335cd82164",
      "name": "Migration risk register",
      "type": "Task",
      "content": "Build the risk register for the migration described in the facts given: for each risk, what could go wrong, the entity or step it affects, the effect on the business if it does, how likely it is in plain terms, the early sign, the mitigation, the fallback, and the owner. Include the risks nobody likes to write down: the owner who is not available at cutover, the history nobody has tested, the reference codes that differ, the interface that still points at the old system.",
      "tags": [
        "task",
        "migration",
        "risks",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:41.000Z"
    },
    {
      "id": "3725076a-f6e0-4240-8fb4-c680b5f66dbe",
      "blockId": "7afa57f5-01d2-467a-b20a-7c77718ef8d7",
      "name": "Legacy archive decision",
      "type": "Task",
      "content": "Decide what happens to the data left in the retired systems after {{initiative}}: which data must stay readable and for how long under the obligations given, whether it is archived to a store the business can query, exported to files with their meaning preserved, or kept in a frozen copy of the system, who owns it after the system team disbands, how access is granted and logged, and when it is finally disposed of. State the decision per data set and its cost in effort and ownership.",
      "tags": [
        "task",
        "migration",
        "archive",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:42.000Z"
    },
    {
      "id": "eef65d07-a9a3-4d20-8077-78e131ad8800",
      "blockId": "197493c3-6382-49fe-9142-a62cefba6ef3",
      "name": "Every migration object reconciles",
      "type": "Constraints",
      "content": "Every entity, data set and reference code that moves has a reconciliation that proves it arrived complete and correct, with a tolerance and a named signatory. An object with no reconciliation is not migrated; it is moved and hoped for. Never report a migration done by count alone when meaning or totals could have changed.",
      "tags": [
        "constraints",
        "migration",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:43.000Z"
    },
    {
      "id": "2de5e64e-38e7-4d72-93ae-c736496ddb5c",
      "blockId": "e10c38ac-7e60-447a-9279-311cacf40f2b",
      "name": "Data lifecycle and retention architect",
      "type": "Role",
      "content": "You are the architect who designs how long data lives, where it goes when it is no longer active and how it is removed. You take retention periods from the schedule records management and legal own and never from memory, you design archiving so that retained data stays findable and meaningful, and you make deletion a designed, provable event rather than something that happens when a disk fills. You keep the business's need to keep data and its duty to let it go in the same picture.",
      "tags": [
        "role",
        "retention",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:44.000Z"
    },
    {
      "id": "dceac627-0341-4adb-854e-8439a42ba67c",
      "blockId": "5d7f5964-426c-4014-b338-cd536ad8e518",
      "name": "Retention inputs",
      "type": "Context",
      "content": "The retention schedule extract, record classes and obligations as records management and legal gave them, with the entities and systems in scope.\n\n{{retention inputs}}",
      "tags": [
        "context",
        "retention",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:45.000Z"
    },
    {
      "id": "7225a893-c158-4613-bfdf-04f46f36c8e2",
      "blockId": "e185e9bf-70bb-4a65-95f1-ff3ae9a239e6",
      "name": "Map entities to retention classes",
      "type": "Task",
      "content": "Map the data entities in scope to the retention classes in the schedule given: for each entity, the record class it belongs to, the retention period and the event that starts the clock as the schedule states them, the system where the retained copy lives and the copies that must follow the same rule, and the entities that fall under more than one class or none. Do not propose periods of your own; where the schedule is silent, record the question for records management.",
      "tags": [
        "task",
        "retention",
        "mapping",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:46.000Z"
    },
    {
      "id": "568d0dcc-0196-4340-9618-1ba0eff5fd19",
      "blockId": "82381c34-cd59-4419-a957-1ffac8698d49",
      "name": "Archive tier design",
      "type": "Task",
      "content": "Design the archive tiers for the data given: which data stays active, which moves to a near-line archive the business can still query, which goes to deep storage that is retrieved on request, and when each move happens relative to the lifecycle event. State for each tier how the data keeps its meaning (definitions, reference codes, schema versions kept with it), how it is found and retrieved and in what time, how access and classification carry over, and who owns it. Describe tiers as capabilities, not products.",
      "tags": [
        "task",
        "retention",
        "archive",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:47.000Z"
    },
    {
      "id": "85174c9f-0038-4ba7-8abb-2c456258d7f6",
      "blockId": "4ce10e63-2f8c-479c-bb1a-635b21aa5404",
      "name": "Deletion and disposal design",
      "type": "Task",
      "content": "Design how data is deleted or disposed of at the end of its retention from the material given: how the end of retention is detected per entity, how every copy and derived data set is found, what deletion means for each store (removed, anonymised, or made irretrievable), how backups and archives are handled, how deletion is approved, logged and proven, and what is kept as evidence that the data existed and was removed. Name the systems that cannot delete today and the architecture change each needs.",
      "tags": [
        "task",
        "retention",
        "deletion",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:48.000Z"
    },
    {
      "id": "46b3baff-dc6f-4ada-bc11-e594941dd3ea",
      "blockId": "942334f0-db30-4b6c-b1ac-5b2921832752",
      "name": "Legal hold design",
      "type": "Task",
      "content": "Design how a legal hold suspends deletion for the data given: how a hold is declared and by which role, how the data under hold is identified across systems, copies and backups, how scheduled deletion is stopped without stopping it for everything else, how the hold is lifted and deletion resumes, how all of it is logged, and who is told. Do not decide when a hold is required; design so that the architecture can honour one within the time legal says it needs.",
      "tags": [
        "task",
        "retention",
        "legal hold",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:49.000Z"
    },
    {
      "id": "9672bd79-abeb-4579-b656-b820267c00cd",
      "blockId": "75047e6b-a3ee-4e88-902f-db034b63ce43",
      "name": "Retention gap assessment",
      "type": "Task",
      "content": "Assess the gaps between the retention schedule given and what the systems do: entities kept longer than their period because nothing deletes them, entities deleted sooner than their period, copies and derived sets with no retention at all, archives no one can read, personal data kept after its purpose ended, and systems that cannot prove deletion. For each gap, the obligation it touches as given, the exposure in business terms, the owner, and the fix from configuring a system to re-architecting a store.",
      "tags": [
        "task",
        "retention",
        "gaps",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:50.000Z"
    },
    {
      "id": "895c9c32-1a2b-400b-8f34-fe1d0557b496",
      "blockId": "176f0f86-b0ff-4c1d-920c-e791d3bd82a0",
      "name": "Note to records management and legal",
      "type": "Task",
      "content": "Write the note to records management and legal that reports what the architecture found and asks for what it needs: the entities with no retention class, the schedule entries that conflict or cannot be applied as written, the systems that cannot meet a period or a hold, and the questions whose answers change the design. For each, what you will assume until answered and by when you need the answer. Keep it short and specific enough to be answered line by line.",
      "tags": [
        "task",
        "retention",
        "conversation",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:51.000Z"
    },
    {
      "id": "b2bb06fd-c290-47b7-947d-bff480c3e1fb",
      "blockId": "21677300-9111-4905-aa88-e4212261edd3",
      "name": "Retention periods come from the schedule",
      "type": "Constraints",
      "content": "Every retention period, trigger event and record class comes from the retention schedule or a written instruction from records management or legal, cited as such. Never supply a period from memory or general practice, and never round one for convenience. Where the schedule is silent, record the gap and the question, and design so that either answer can be met.",
      "tags": [
        "constraints",
        "retention",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:52.000Z"
    },
    {
      "id": "48e66e6a-920b-4d71-9ce5-a8f70494d1e8",
      "blockId": "e8d9ad06-16a9-4aac-9496-b31ef7bb0666",
      "name": "Data due diligence lead",
      "type": "Role",
      "content": "You are the architect who assesses a target company's data before a deal and plans what happens to it after. You work from a data room that is never complete, you separate what you saw from what you inferred and what you could not learn, you price data risk in terms the deal team uses, and you plan day one and the integration so the combined business can bill, pay and report from the first morning. You never decide what the law requires of the deal; you make sure the plan can meet what legal says.",
      "tags": [
        "role",
        "due diligence",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:53.000Z"
    },
    {
      "id": "bc39870d-be9a-4523-b610-669cd91a9710",
      "blockId": "ac127395-6cd7-458d-9a2f-38f8ccb79118",
      "name": "Deal facts",
      "type": "Context",
      "content": "What is known about the deal and the target's data: the deal type and timetable, the target's business and systems as the data room shows them, the documents received, the questions already asked, and the combined business's intended shape.\n\n{{deal facts}}",
      "tags": [
        "context",
        "deal",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:54.000Z"
    },
    {
      "id": "b6e49f60-15b4-4f00-9e88-3323ee7e78bc",
      "blockId": "523ad2c1-a2b3-4155-b3d7-42cca743ef5b",
      "name": "Data due diligence request list",
      "type": "Task",
      "content": "Write the data request list for the due diligence on the target described in the facts given: the documents and evidence to ask for on its systems of record, data models and glossary, data ownership and governance, quality incidents, personal data and privacy records, retention and holds, integration landscape, analytics platform, contracts that bind its data, and the people who know it. For each item, why it matters to the deal, the priority, and what you will conclude if it cannot be produced. Order it so the first week's answers shape the second week's questions.",
      "tags": [
        "task",
        "due diligence",
        "requests",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:55.000Z"
    },
    {
      "id": "ee6c2817-7725-4a0d-ac06-27f4ad7feded",
      "blockId": "ea575baa-0557-473d-980b-38dcd2ac214d",
      "name": "Data landscape assessment of the target",
      "type": "Task",
      "content": "Assess the target's data landscape from the material given: its domains and systems of record, where its customer, product, financial and employee data live and how well they are defined and owned, the duplication and quality signs, its integration and analytics state, the personal and regulated data it holds and how, its retention practice, and the dependence on people and spreadsheets. Rate each area against the acquirer's own architecture and say what it would take to bring it to the acquirer's standard. Separate what you saw from what you inferred.",
      "tags": [
        "task",
        "due diligence",
        "assessment",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:56.000Z"
    },
    {
      "id": "26db9628-5c0c-4da5-b6f8-1ee72299ee30",
      "blockId": "8c4aa5a3-9e64-4343-bf98-25494c90cea9",
      "name": "Data risk register for the deal",
      "type": "Task",
      "content": "Build the data risk register for the deal from the material given: for each risk, what it is, the evidence, the effect on value, integration cost or obligations in the deal team's terms, how likely it is, what would confirm or dismiss it before signing, the mitigation or price adjustment to consider, and the owner. Include the risks of what the data room did not contain. Mark the risks that must be settled before signing and the ones that can wait for integration planning.",
      "tags": [
        "task",
        "due diligence",
        "risks",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:57.000Z"
    },
    {
      "id": "f48a4435-c506-49ae-91fb-7b3cc799118d",
      "blockId": "9ec30e2a-84ff-4d7a-af8a-1484273495c5",
      "name": "Integration options for the two data estates",
      "type": "Task",
      "content": "Compare the options for the two data estates after the deal from the facts given: absorb the target's data into the acquirer's systems and models, keep both estates and integrate through shared master data and reporting, run them separately with consolidated reporting only, or carve the target's data out for a later sale. For each, what the combined business can do and when, the migration and master data work involved, the people and skills it needs, the risk to operations, and the one fact that would decide it. Recommend an option and the point at which it should be revisited.",
      "tags": [
        "task",
        "due diligence",
        "integration options",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:58.000Z"
    },
    {
      "id": "17e81855-a734-43b3-a6d0-92870b02f019",
      "blockId": "fff4773d-39d2-4426-bef7-d2d4781fc169",
      "name": "Day one data requirements",
      "type": "Task",
      "content": "Define what the combined business must be able to do with data on the first day after close, from the facts given, and the data that makes each possible: bill and collect, pay staff and suppliers, serve customers, report to regulators and the board, and honour privacy and retention obligations. For each, the entities and systems involved on both sides, what must be mapped, matched or copied before day one, what can wait, the owner, and the fallback if it is not ready. Separate day one from the first hundred days.",
      "tags": [
        "task",
        "due diligence",
        "day one",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:03:59.000Z"
    },
    {
      "id": "30ebd2fa-ae48-46b8-8a34-aad1211e0abe",
      "blockId": "bc5aa0e8-74ee-4a90-ae3c-a775efd7a8fc",
      "name": "Data integration roadmap after close",
      "type": "Task",
      "content": "Build the data integration roadmap after close from the option and requirements given: the stages from day one through the first hundred days to the end state, what each delivers to the business, the master data, migration, platform and governance work in each, the dependencies on the application and technology integration, the decisions each stage needs and who makes them, and the measures that show a stage is done. Say what forces the order and where the plan could be accelerated or slowed.",
      "tags": [
        "task",
        "due diligence",
        "roadmap",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:00.000Z"
    },
    {
      "id": "7983759e-cd5c-4fb7-8487-31875cf21039",
      "blockId": "648f601d-5b67-40a8-a34f-9380cbc0f386",
      "name": "Carve-out data architecture",
      "type": "Task",
      "content": "Where a business is being separated, design the carve-out of its data, after the options above: which entities and records belong to the separated business, which are shared and must be split or copied under a rule, how shared master and reference data is divided, how personal data moves under the obligations given, what the remaining business must keep for the periods legal or records management set, the transitional access each side needs and when it ends, and the sequence of the separation. Name the data that cannot be cleanly separated and the decision that resolves each case.",
      "tags": [
        "task",
        "due diligence",
        "carve-out",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:01.000Z"
    },
    {
      "id": "744b5712-d841-4853-9b75-674edb52124b",
      "blockId": "b1880c77-a840-42b4-9342-b22e631500d4",
      "name": "Due diligence findings",
      "type": "Format",
      "content": "Present the findings by area, each with a bold heading and four short labelled parts: **What we found** (fact), **What we infer** (and from what), **What we could not learn**, **What it means for the deal**. Then a one-page summary table: area, rating, headline finding, action before signing. Where the task asks for a risk register, add it after the findings as a table: risk, evidence, effect, likelihood, what settles it, mitigation, owner. Nothing in the summary that is not in the findings.",
      "tags": [
        "format",
        "due diligence",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:02.000Z"
    },
    {
      "id": "251d6669-2623-4031-9d54-088464123478",
      "blockId": "1ccabe20-9c0e-4e88-9d7d-24b5dfffde02",
      "name": "Checklist with owners",
      "type": "Format",
      "content": "Present the items as a numbered checklist grouped under bold headings (by area, or by stage where the task plans stages), each item one line ending with its owner, its priority and its status or due date. Below the list, the items that are blocked and what unblocks each.",
      "tags": [
        "format",
        "checklist",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:03.000Z"
    },
    {
      "id": "9c71f449-1cea-4211-a570-e9eea462bb87",
      "blockId": "fbc6b078-41f4-4bb6-a3b7-50025dced61c",
      "name": "Fact, inference, unknown",
      "type": "Constraints",
      "content": "Label every statement as fact (seen in the material), inference (reasoned from it, with the reasoning) or unknown (not learnable from what was given). Never let an inference harden into a fact between sections, and never fill an unknown with what is usual elsewhere. A deal team deciding on your work must be able to see what rests on evidence.",
      "tags": [
        "constraints",
        "evidence",
        "Data architecture pack"
      ],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:04.000Z"
    }
  ],
  "prompts": [
    {
      "id": "172846ff-e711-4b85-b1a1-9f4a2632ff7e",
      "name": "Data principles catalog",
      "description": "The six to ten data principles for the enterprise, each with statement, rationale and implications, ready for the architecture board.",
      "promptType": "User Prompt",
      "tags": [
        "principles",
        "catalog",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "d70f166b-4794-4074-be22-6b404db7840d",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "77bfb472-5579-495a-965b-4d30682d0360",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b8cc7f8a-5dcf-4bc2-b436-5eaf9a8bcd09",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:05.000Z",
      "updatedAt": "2026-10-05T09:04:05.000Z"
    },
    {
      "id": "59d2b86c-99a9-44a0-9b2a-f57ad38e1689",
      "name": "Review a draft principle",
      "description": "A review of one draft data principle against the test of a real principle and the principles already in force, with a rewrite where the fix is clear.",
      "promptType": "User Prompt",
      "tags": [
        "principles",
        "review",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "61bac58f-3554-4a3e-b986-ba5d2cdf1aa2",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "6029e3f8-9094-4a19-8508-e932efb0130f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "312c7d23-1359-43a3-87fe-7bff03f59efe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b8cc7f8a-5dcf-4bc2-b436-5eaf9a8bcd09",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:06.000Z",
      "updatedAt": "2026-10-05T09:04:06.000Z"
    },
    {
      "id": "b9ad93ce-c0b4-4563-8f6d-e84ef4cf530e",
      "name": "Scope the data architecture work",
      "description": "The data part of the statement of architecture work: domains and entities in scope, stakeholder concerns, viewpoints and the artefacts to produce.",
      "promptType": "User Prompt",
      "tags": [
        "scope",
        "statement of architecture work",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "bbe70f70-a037-4ed7-8a11-faa92af7b3ac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "527d546d-672e-49ce-8270-88aa534f54b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:07.000Z",
      "updatedAt": "2026-10-05T09:04:07.000Z"
    },
    {
      "id": "5be4c133-eb59-4235-8946-ab794539048b",
      "name": "Approach note and CDO kick-off",
      "description": "The one-page approach note to the sponsor and the talking points for the kick-off with the chief data officer.",
      "promptType": "User Prompt",
      "tags": [
        "approach",
        "kick-off",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "784c81d7-ce89-4ab1-ac2f-82fe811c0dc6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3a5c12ee-8338-4044-b8a1-318537a90916",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "4285bdda-45e6-48cc-8a26-032430d2e57a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:08.000Z",
      "updatedAt": "2026-10-05T09:04:08.000Z"
    },
    {
      "id": "241c85cd-450f-4b6e-97df-54100905cd11",
      "name": "Principle exception request",
      "description": "The request to the governance body for a design to depart from a data principle, with containment and an end date.",
      "promptType": "User Prompt",
      "tags": [
        "principles",
        "exception",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "61bac58f-3554-4a3e-b986-ba5d2cdf1aa2",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e2e5eccd-0107-4ef3-9460-48f69abda529",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "dd4fb49e-f2bc-463e-a982-a27a5244e7fe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "02f32eb3-df99-409c-bb8e-e6498a272748",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:09.000Z",
      "updatedAt": "2026-10-05T09:04:09.000Z"
    },
    {
      "id": "21634bad-b916-4b36-aa78-4672322e9eb3",
      "name": "Baseline inventory and entity list",
      "description": "The baseline inventory of data stores by domain and the entity list derived from it, with conflicts marked.",
      "promptType": "User Prompt",
      "tags": [
        "baseline",
        "inventory",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4dbd3fa1-324d-46c1-8fb3-04aa31162e76",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "38fe9f5d-7693-465d-9a2d-0a91aa811392",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "515e9301-e091-412a-af05-408c787c40a6",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:10.000Z",
      "updatedAt": "2026-10-05T09:04:10.000Z"
    },
    {
      "id": "1b4526b3-61a3-46bf-b9c4-a2e8356b13dc",
      "name": "Baseline description and questions to owners",
      "description": "The baseline data architecture section of the architecture definition document, written to be compared against the target, and the questions to application owners that close its gaps.",
      "promptType": "User Prompt",
      "tags": [
        "baseline",
        "document",
        "questions",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4dbd3fa1-324d-46c1-8fb3-04aa31162e76",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3bd0635c-6c3f-4c33-984c-0ea57f539d80",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "14eb1893-1f7b-4014-87ab-8922a7cc6036",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "45c4fde2-411c-42d6-8ce7-84895051d08f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:11.000Z",
      "updatedAt": "2026-10-05T09:04:11.000Z"
    },
    {
      "id": "96e18d0e-0452-413b-8ab5-d80cbd860da3",
      "name": "Baseline assessment and system of record conflicts",
      "description": "The problems in the baseline measured against the principles, and the system of record conflicts set up as decisions.",
      "promptType": "User Prompt",
      "tags": [
        "baseline",
        "assessment",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4dbd3fa1-324d-46c1-8fb3-04aa31162e76",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "4b884d3d-c9b7-4a25-9a3e-7bd5c55b575f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4301c51f-8543-4bb0-bd0f-349d362a2388",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "d0e6c890-c0c1-4303-9d17-8682f72ab73a",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:12.000Z",
      "updatedAt": "2026-10-05T09:04:12.000Z"
    },
    {
      "id": "304fa953-4f4c-49dc-90b7-fd15688d5608",
      "name": "Define the data entities",
      "description": "Catalog entries for one domain's entities: definitions a domain owner can sign, key attributes, creating function, owner and system of record.",
      "promptType": "User Prompt",
      "tags": [
        "catalog",
        "entities",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "ecc88a7e-4160-4a44-af93-30609fd71f3f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "04b8977c-9a65-49f6-a416-4bd210cd22b2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "aa261336-018a-41f7-bbc8-a34d67526306",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:13.000Z",
      "updatedAt": "2026-10-05T09:04:13.000Z"
    },
    {
      "id": "6d36f122-6bba-4299-ba76-d45917ab8572",
      "name": "Logical and physical data components",
      "description": "The logical data components grouped from the entities and the physical components that realise them, mapped in both directions.",
      "promptType": "User Prompt",
      "tags": [
        "catalog",
        "components",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4de39862-b8c2-4234-a520-2e1a1eeeb3a1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "af8f1e14-e499-48ca-8ae7-bb2459f1a20e",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "04b8977c-9a65-49f6-a416-4bd210cd22b2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:14.000Z",
      "updatedAt": "2026-10-05T09:04:14.000Z"
    },
    {
      "id": "d26f8036-a549-4b4b-ad04-8e36b35ae579",
      "name": "Review the catalog",
      "description": "The overlaps, gaps and bad definitions in a catalog extract, with what to merge, split, rename or complete.",
      "promptType": "User Prompt",
      "tags": [
        "catalog",
        "review",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "103aee15-7cf4-4ac0-adc9-b0194eb32c6c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "312c7d23-1359-43a3-87fe-7bff03f59efe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "16fec59c-0847-4837-a504-623754e60094",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:15.000Z",
      "updatedAt": "2026-10-05T09:04:15.000Z"
    },
    {
      "id": "93a5b7ef-c0fd-495d-974c-312df42ad519",
      "name": "Catalog standard and walkthrough note",
      "description": "The maintenance standard for the catalog and the note that sends a domain's draft entries to its owner for review.",
      "promptType": "User Prompt",
      "tags": [
        "catalog",
        "standard",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7c6eb957-9bdb-498a-beff-638d27c633a8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "61cc485f-b41b-4efa-8cf6-3dc6bdc59a39",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7944c208-84b7-4872-9af3-e0af935e17b4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "a45d332e-fc1d-4720-b6cb-94daf782335d",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:16.000Z",
      "updatedAt": "2026-10-05T09:04:16.000Z"
    },
    {
      "id": "cae5b8cb-ae9d-4583-ac63-ffe292337651",
      "name": "Conceptual data model",
      "description": "The conceptual model of one domain: business entities, relationships with their meaning and cardinality, the rules encoded, the questions left open.",
      "promptType": "User Prompt",
      "tags": [
        "model",
        "conceptual",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "89436b13-83ce-4b02-9080-36bcded59aa9",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1b9af371-fec5-4a33-8466-ac52146de274",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "aa261336-018a-41f7-bbc8-a34d67526306",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:17.000Z",
      "updatedAt": "2026-10-05T09:04:17.000Z"
    },
    {
      "id": "a81c66da-0e90-4eef-8b6e-a0d863ea9918",
      "name": "Logical data model",
      "description": "The logical model developed from the conceptual: attributes, identifiers, resolved relationships, subtypes and the normalisation decisions.",
      "promptType": "User Prompt",
      "tags": [
        "model",
        "logical",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "2ba79058-5326-443d-ab14-67e9449338b2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1b9af371-fec5-4a33-8466-ac52146de274",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c761b7b9-0838-40ad-918c-827e06792955",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:18.000Z",
      "updatedAt": "2026-10-05T09:04:18.000Z"
    },
    {
      "id": "3530613c-c2ff-43f3-9216-edf85df8517a",
      "name": "Physical model considerations",
      "description": "The architecture-level considerations for the physical model: storage styles, denormalisation, keys, history, and what is left to design.",
      "promptType": "User Prompt",
      "tags": [
        "model",
        "physical",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e4354209-d491-4ee9-b110-9b30296e28d9",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c761b7b9-0838-40ad-918c-827e06792955",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:19.000Z",
      "updatedAt": "2026-10-05T09:04:19.000Z"
    },
    {
      "id": "f6655784-c7cf-42a0-a1cc-58ed024db1be",
      "name": "Model review and reconciliation",
      "description": "A review of a model against the standards, and the reconciliation of two models of one domain into a merged entity list with the decisions still needed.",
      "promptType": "User Prompt",
      "tags": [
        "model",
        "review",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e5fba729-cc07-42c8-986d-163edb424ba4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "84795e92-23bc-4479-bd82-e4fc1af708bd",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "e449b89a-dbde-4968-be0a-91ef0138b64c",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "b6a6f3ba-6f07-4947-ae65-d1e597347995",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:20.000Z",
      "updatedAt": "2026-10-05T09:04:20.000Z"
    },
    {
      "id": "44e90494-df84-4b19-a200-ea7d47983b66",
      "name": "Explain the model to the business",
      "description": "The data model told as how the business works, for readers who will never see the diagram, with what changes for them.",
      "promptType": "User Prompt",
      "tags": [
        "model",
        "communication",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "790d28f8-97cd-46a0-9758-2f882b110eb3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "8be6b534-bc52-489a-9129-5e4d6c662937",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "36bca6e6-dfe9-4691-ade6-18ca19df9293",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "29a5abd3-3811-49aa-be6e-1fb2078f1605",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:21.000Z",
      "updatedAt": "2026-10-05T09:04:21.000Z"
    },
    {
      "id": "814c1cb3-a6fb-4745-8931-463c5ae6b58a",
      "name": "Define a business term",
      "description": "One glossary entry a business owner can sign: definition, edge cases, synonyms, owner, where it is held, examples in and out.",
      "promptType": "User Prompt",
      "tags": [
        "glossary",
        "definition",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "a7ebbec8-8c4d-46be-8b89-a8bed032b280",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "73a4c9b4-e50d-4aa5-814e-42483c84beac",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "1a4fbee5-6561-4d7f-a77d-7109f77b7a1a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fa9babc0-71fb-45e4-9060-4e18f63c8179",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fb3fd01a-af33-4475-bc6f-f9e4b9db40b1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:22.000Z",
      "updatedAt": "2026-10-05T09:04:22.000Z"
    },
    {
      "id": "bd3893af-8b4a-49fa-aa1b-222e72f6c7d0",
      "name": "Resolve a definition conflict",
      "description": "The meanings in play, what breaks when they mix, the recommended outcome, and the sign-off request to the business owner.",
      "promptType": "User Prompt",
      "tags": [
        "glossary",
        "conflict",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "a7ebbec8-8c4d-46be-8b89-a8bed032b280",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "73a4c9b4-e50d-4aa5-814e-42483c84beac",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "3ab428e0-e30e-423b-994d-75dcc933b1c6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "7b60dbcd-f03c-459b-a6c9-8b3349158083",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "fb3fd01a-af33-4475-bc6f-f9e4b9db40b1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:23.000Z",
      "updatedAt": "2026-10-05T09:04:23.000Z"
    },
    {
      "id": "0a00adfd-5920-45be-a753-027a0c7a1924",
      "name": "Glossary coverage and model mapping",
      "description": "The gaps in the glossary ranked by dependence, and the mapping of terms to the model's entities and attributes with the mismatches.",
      "promptType": "User Prompt",
      "tags": [
        "glossary",
        "mapping",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "a7ebbec8-8c4d-46be-8b89-a8bed032b280",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "73a4c9b4-e50d-4aa5-814e-42483c84beac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "47c0e418-c8da-4b03-a64e-59b739f213a5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "efa111d5-02d9-491f-b068-b323eee1b438",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "bc40d393-3b7e-44da-bb73-a5780a711c9b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": true
        }
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:24.000Z",
      "updatedAt": "2026-10-05T09:04:24.000Z"
    },
    {
      "id": "86e52f16-286d-48e4-8435-ba96a625e0ac",
      "name": "Glossary standard",
      "description": "The standard for the business glossary: eligibility, complete entries, approval by role, synonyms and retirement, links to the model, review cadence.",
      "promptType": "User Prompt",
      "tags": [
        "glossary",
        "standard",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "a7ebbec8-8c4d-46be-8b89-a8bed032b280",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "0f0763a2-f0c6-43f9-b17a-104b68b0a0d6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "d81bf753-c72c-4451-aa39-5911db9347a9",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "895cf356-da24-4dbb-80af-ce569b587408",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:25.000Z",
      "updatedAt": "2026-10-05T09:04:25.000Z"
    },
    {
      "id": "b04c4fe5-6e26-4ba5-a836-b45a1422d93c",
      "name": "Entity to business function matrix",
      "description": "The matrix of entities against business functions with create, read, update and delete, and what it reveals about ownership.",
      "promptType": "User Prompt",
      "tags": [
        "matrix",
        "business function",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f03a6b71-1e3c-4ee3-81ad-a5141646ed87",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "284c8953-1748-4e3a-8ab8-e23810d49c83",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5a1d7ab-517b-41f0-b395-131d362813d7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "e7f8e5c3-c814-46cd-aaf4-0a8dc50485da",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:26.000Z",
      "updatedAt": "2026-10-05T09:04:26.000Z"
    },
    {
      "id": "e318919e-a093-405d-abab-9dd8ce682215",
      "name": "Application to data matrix",
      "description": "The matrix of entities against applications, with copies marked, and what it implies for system of record and integration.",
      "promptType": "User Prompt",
      "tags": [
        "matrix",
        "application",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f03a6b71-1e3c-4ee3-81ad-a5141646ed87",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "a72b9bd7-a435-4693-8076-858c591699ec",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5a1d7ab-517b-41f0-b395-131d362813d7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:27.000Z",
      "updatedAt": "2026-10-05T09:04:27.000Z"
    },
    {
      "id": "7a1dfa94-8bf7-44d3-a73d-6417026517fd",
      "name": "What the matrices show",
      "description": "System of record proposals with evidence and confidence, and the gaps and overlaps ranked by business impact.",
      "promptType": "User Prompt",
      "tags": [
        "matrix",
        "analysis",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f03a6b71-1e3c-4ee3-81ad-a5141646ed87",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "9149ccd5-cf3f-489e-856b-16a31ae48d09",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "7a130057-5ce9-4792-b27f-cd1f4656090b",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e7f8e5c3-c814-46cd-aaf4-0a8dc50485da",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:28.000Z",
      "updatedAt": "2026-10-05T09:04:28.000Z"
    },
    {
      "id": "289d0544-5991-44f5-ba16-1cc8ca04aa54",
      "name": "Settle a system of record conflict",
      "description": "The conversation with two application owners who both create an entity, and the note that records the outcome in the repository.",
      "promptType": "User Prompt",
      "tags": [
        "matrix",
        "system of record",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f03a6b71-1e3c-4ee3-81ad-a5141646ed87",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "cd464aae-5f1e-4577-846b-cc394b56ed4a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b67001c0-fc33-4b96-8434-947135769dfb",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "8499cd06-3f37-4886-81db-099eb6de2dd0",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:29.000Z",
      "updatedAt": "2026-10-05T09:04:29.000Z"
    },
    {
      "id": "3aceada7-27fe-4315-bb4f-662a45b6318a",
      "name": "Data dissemination diagram",
      "description": "The dissemination diagram described for drawing: which applications hold which data components, sources and copies, how the data travels, and what it shows.",
      "promptType": "User Prompt",
      "tags": [
        "diagram",
        "dissemination",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "57d4f5ab-f211-4bdd-b93b-1c28b5eb5794",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "8c816b52-12a0-4de6-a296-d9eeef82127a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "49b29bb2-bba9-4c1a-9b23-cbc8a1245e90",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "47faa8b5-bd0f-44c8-928c-6d58feb306ac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:30.000Z",
      "updatedAt": "2026-10-05T09:04:30.000Z"
    },
    {
      "id": "ab85067d-6afa-4e3c-8f33-f0749958c37d",
      "name": "Copies and hops",
      "description": "Every copy of each entity with its hops, staleness and reconciliation, ranked by the harm of a disagreement, with what to remove, freeze or keep.",
      "promptType": "User Prompt",
      "tags": [
        "flows",
        "copies",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "57d4f5ab-f211-4bdd-b93b-1c28b5eb5794",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "0736597a-fa97-4c69-8d8d-1f5a160f9513",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ff6ed2d2-bf79-4a10-b818-0d3e7f35a3b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:31.000Z",
      "updatedAt": "2026-10-05T09:04:31.000Z"
    },
    {
      "id": "d5dac337-452d-432b-86f8-672a3de2f5d6",
      "name": "Entity lifecycle",
      "description": "The lifecycle diagram of one entity and the events, owners and systems behind every transition, with the places where control is lost.",
      "promptType": "User Prompt",
      "tags": [
        "diagram",
        "lifecycle",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "57d4f5ab-f211-4bdd-b93b-1c28b5eb5794",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "8cbf4f4d-b851-4036-a349-c242685fe420",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ed2bde2c-0b3a-4b6b-9cc5-77964cddc438",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "8dd18e9e-98fc-4d94-90f2-51d259362a64",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "47faa8b5-bd0f-44c8-928c-6d58feb306ac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:32.000Z",
      "updatedAt": "2026-10-05T09:04:32.000Z"
    },
    {
      "id": "6dff0ee7-4753-445a-b4b1-6775e8eb99b3",
      "name": "Flow narrative for leaders",
      "description": "One or two entities followed across the domains from creation to retirement, for readers who do not read diagrams, with the three changes that matter.",
      "promptType": "User Prompt",
      "tags": [
        "flows",
        "communication",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "790d28f8-97cd-46a0-9758-2f882b110eb3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "57d4f5ab-f211-4bdd-b93b-1c28b5eb5794",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "9e27aa2e-7aaf-4702-800e-211a7e20792c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "36bca6e6-dfe9-4691-ade6-18ca19df9293",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "29a5abd3-3811-49aa-be6e-1fb2078f1605",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:33.000Z",
      "updatedAt": "2026-10-05T09:04:33.000Z"
    },
    {
      "id": "a5344232-03f2-4620-a056-4ae498008230",
      "name": "Review a diagram",
      "description": "A review of a drafted diagram against the standard and the catalog, with what to change and whether it can enter the repository.",
      "promptType": "User Prompt",
      "tags": [
        "diagram",
        "review",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e5fba729-cc07-42c8-986d-163edb424ba4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "61bac58f-3554-4a3e-b986-ba5d2cdf1aa2",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e8d7db8f-6b09-42d1-9d46-ba13b3463555",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "312c7d23-1359-43a3-87fe-7bff03f59efe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "47faa8b5-bd0f-44c8-928c-6d58feb306ac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "bc66ffbc-7bc4-4a99-97fc-5a48ba39616b",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:34.000Z",
      "updatedAt": "2026-10-05T09:04:34.000Z"
    },
    {
      "id": "bcd96658-2f2b-42cf-8803-e434d8ce9c7b",
      "name": "Classify the entities",
      "description": "The classification of one domain's entities and sensitive attributes, with the harm behind each level and the handling it requires.",
      "promptType": "User Prompt",
      "tags": [
        "classification",
        "entities",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "17db55c2-3020-419e-ba30-d3ceec263f00",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "46e2047f-d0a1-4c62-b6c2-e140f53005e8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "247c0418-bd3d-415b-a77c-61716537dcea",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ebd01e9a-7ad1-4fc9-b2ef-86ab45d4b5de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1fa05c97-cfbc-4cb9-9763-832207c9d2f3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:35.000Z",
      "updatedAt": "2026-10-05T09:04:35.000Z"
    },
    {
      "id": "6d1322d5-1ab0-4705-9188-c115d24c05a6",
      "name": "Data security diagram",
      "description": "The data security diagram described for drawing: who reaches which data through which paths at which level, and where trust boundaries are crossed.",
      "promptType": "User Prompt",
      "tags": [
        "diagram",
        "security",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "17db55c2-3020-419e-ba30-d3ceec263f00",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "46e2047f-d0a1-4c62-b6c2-e140f53005e8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "85be031a-4de2-4428-b414-7d62b9e737e8",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "083f4a5e-82f0-4d02-bc84-45d7c2db2545",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "49b29bb2-bba9-4c1a-9b23-cbc8a1245e90",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fb3a2a91-30e3-4466-8163-7300f764bf30",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:36.000Z",
      "updatedAt": "2026-10-05T09:04:36.000Z"
    },
    {
      "id": "47fd4cc3-ef50-4d12-969d-f54b88dcc48b",
      "name": "Access patterns and security requirements",
      "description": "The access and segregation rules for the data in scope, and the testable security requirements for the architecture requirements specification.",
      "promptType": "User Prompt",
      "tags": [
        "security",
        "requirements",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "17db55c2-3020-419e-ba30-d3ceec263f00",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "85be031a-4de2-4428-b414-7d62b9e737e8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5788603e-7b30-44fb-85e5-927a5f5b3bd8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "891ac26b-e454-4634-b7a7-9b9230b8e9e3",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fb3a2a91-30e3-4466-8163-7300f764bf30",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:37.000Z",
      "updatedAt": "2026-10-05T09:04:37.000Z"
    },
    {
      "id": "309d7851-b885-479d-9b81-00301b9692a5",
      "name": "Classification standard and gaps",
      "description": "The classification standard with examples, and the gaps in today's classifications measured against it with owners to act.",
      "promptType": "User Prompt",
      "tags": [
        "classification",
        "standard",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "17db55c2-3020-419e-ba30-d3ceec263f00",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "46e2047f-d0a1-4c62-b6c2-e140f53005e8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7751e727-5c03-4abb-9ba3-74cc61893e35",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "8279b9b7-dd86-476f-b75a-a56a6651f1a4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "1fa05c97-cfbc-4cb9-9763-832207c9d2f3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "45275d34-6f83-444d-8d0d-2377a918ae92",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:38.000Z",
      "updatedAt": "2026-10-05T09:04:38.000Z"
    },
    {
      "id": "dfabd198-53fa-4357-9564-38ea9e0f658c",
      "name": "Personal data inventory",
      "description": "The personal data inventory for an initiative: elements, subjects, purposes, where held and shared, retention and stated basis, with the gaps marked.",
      "promptType": "User Prompt",
      "tags": [
        "privacy",
        "inventory",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "2ddc91bf-3633-49a8-b183-9955d55b03ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ad0e847c-e523-4bfb-8b6d-6aee46a5947a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "ad1cfe2d-9f19-4291-9084-3bd68d858eda",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b29b60fd-57c8-4eab-8633-4af7ee812a63",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3d97eede-ed81-4e36-90f9-821389ee1a0f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:39.000Z",
      "updatedAt": "2026-10-05T09:04:39.000Z"
    },
    {
      "id": "a9cfdfa1-a0a4-49bc-a55e-74be9777979d",
      "name": "Privacy design review",
      "description": "A review of a design for minimisation, pseudonymisation, access, retention, sharing and rights support, with what must change before build.",
      "promptType": "User Prompt",
      "tags": [
        "privacy",
        "review",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "2ddc91bf-3633-49a8-b183-9955d55b03ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ad0e847c-e523-4bfb-8b6d-6aee46a5947a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "761a93aa-539b-4b65-a2dd-435b9f3b45ac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "312c7d23-1359-43a3-87fe-7bff03f59efe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fb3a2a91-30e3-4466-8163-7300f764bf30",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:40.000Z",
      "updatedAt": "2026-10-05T09:04:40.000Z"
    },
    {
      "id": "b4002e08-dd48-4ea7-a651-a17fcf6ead1a",
      "name": "Privacy assessment inputs and questions for legal",
      "description": "The architecture's inputs to the privacy impact assessment and the questions legal must answer, each with what you will assume meanwhile.",
      "promptType": "User Prompt",
      "tags": [
        "privacy",
        "assessment",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "2ddc91bf-3633-49a8-b183-9955d55b03ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ad0e847c-e523-4bfb-8b6d-6aee46a5947a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "53664898-56ea-48d6-ba0f-c5ea9080abe9",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "5a301ca8-1b3f-4f25-9333-5593475ed638",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "24ba819e-62e3-4a0f-95a1-ca214744990d",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e09b6e29-0691-4d1a-bcc0-a99be4c9f1fc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:41.000Z",
      "updatedAt": "2026-10-05T09:04:41.000Z"
    },
    {
      "id": "668305ba-a233-4409-8184-500f29ee3e2e",
      "name": "Cross-border map and rights support",
      "description": "Where personal data sits and moves by country, and how the architecture finds, corrects, exports and deletes a person's data across every copy.",
      "promptType": "User Prompt",
      "tags": [
        "privacy",
        "transfers",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "2ddc91bf-3633-49a8-b183-9955d55b03ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ad0e847c-e523-4bfb-8b6d-6aee46a5947a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "53664898-56ea-48d6-ba0f-c5ea9080abe9",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "91ed2950-31b8-49ca-947e-2900ab9b9e74",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9df498aa-2dd7-4391-bf09-cacd691dd932",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e09b6e29-0691-4d1a-bcc0-a99be4c9f1fc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:42.000Z",
      "updatedAt": "2026-10-05T09:04:42.000Z"
    },
    {
      "id": "a327876b-3e25-40c8-b950-28dd93e4cb58",
      "name": "Target data architecture",
      "description": "The target data architecture section of the architecture definition document, written against the baseline so the gaps read across.",
      "promptType": "User Prompt",
      "tags": [
        "target",
        "document",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "8810212d-e373-4b59-857a-0bdf05f04273",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "1acd16c8-b347-4bb9-8259-9e1c00c9cd33",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:43.000Z",
      "updatedAt": "2026-10-05T09:04:43.000Z"
    },
    {
      "id": "6450cd00-500d-41b9-b629-47c5f271ac14",
      "name": "Building blocks and data requirements",
      "description": "The architecture and solution building blocks of the target and the testable data requirements that go into the requirements specification.",
      "promptType": "User Prompt",
      "tags": [
        "target",
        "building blocks",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "8810212d-e373-4b59-857a-0bdf05f04273",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "025d6ade-3f08-4cf2-98be-427d71c1eb8a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "be616ff2-260f-4645-9e79-292f9cad4f8a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f63cd43d-9f16-487a-9b3f-3eaf9cc4ae27",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:44.000Z",
      "updatedAt": "2026-10-05T09:04:44.000Z"
    },
    {
      "id": "dafb147c-a5bf-427b-b5e5-753978d2747d",
      "name": "Gap analysis and impact",
      "description": "The gap analysis between baseline and target, and what each gap means for the business, application and technology architectures.",
      "promptType": "User Prompt",
      "tags": [
        "gap analysis",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "2e580993-c1a9-4626-927b-b46e8ceb70d7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "98ca2e89-3ee8-4238-9551-48f983160a40",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "560e42d3-b5fb-4fe0-abd1-fe6c28ed9354",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "b998557e-e44e-48c7-bd38-f25c893327fd",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b32e7f56-fa34-4b68-a213-637d81104cc5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:45.000Z",
      "updatedAt": "2026-10-05T09:04:45.000Z"
    },
    {
      "id": "e57f6585-f21b-4066-a6c0-37cb47531695",
      "name": "Roadmap work packages",
      "description": "The data gaps grouped into work packages with dependencies, sizes and transition states, in a proposed sequence for the roadmap.",
      "promptType": "User Prompt",
      "tags": [
        "roadmap",
        "work packages",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "2e580993-c1a9-4626-927b-b46e8ceb70d7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "99f49513-c697-4938-be71-ae5e38a0ee87",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "aea0a883-3e8a-4908-b9a6-86f2fa430267",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "527d546d-672e-49ce-8270-88aa534f54b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:46.000Z",
      "updatedAt": "2026-10-05T09:04:46.000Z"
    },
    {
      "id": "db2ab461-89dc-492f-bd34-b6da3b4d78c3",
      "name": "Stakeholder review of the data architecture",
      "description": "The formal stakeholder review before the data architecture is finalised: each concern traced to where it is answered, the consistency checks, and what remains to sign off.",
      "promptType": "User Prompt",
      "tags": [
        "review",
        "stakeholders",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "2e580993-c1a9-4626-927b-b46e8ceb70d7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "fe051bf8-eadc-4444-8a9a-3ac5b9c94d9a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f917c34a-19fd-4064-976f-7b3653115fb0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "527d546d-672e-49ce-8270-88aa534f54b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:47.000Z",
      "updatedAt": "2026-10-05T09:04:47.000Z"
    },
    {
      "id": "feb5da12-d440-4a3d-b144-8cbd2e7ec98a",
      "name": "Target brief for leaders",
      "description": "The one-page brief on the target data architecture for the leadership team: what the business gains, what changes, the risks and the decision asked.",
      "promptType": "User Prompt",
      "tags": [
        "target",
        "communication",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "790d28f8-97cd-46a0-9758-2f882b110eb3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "2e580993-c1a9-4626-927b-b46e8ceb70d7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "347ec833-1ce1-4214-be3f-bc26d140b993",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "36bca6e6-dfe9-4691-ade6-18ca19df9293",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4285bdda-45e6-48cc-8a26-032430d2e57a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "7bc3b4b2-cf05-4cac-845d-42bb275a35d6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:48.000Z",
      "updatedAt": "2026-10-05T09:04:48.000Z"
    },
    {
      "id": "70f465c7-f953-4a52-aabf-ecffb06a89b3",
      "name": "Master data assessment",
      "description": "Which entities deserve mastering, scored and ranked on sharing, duplication, cost of mismatch and ownership, with what to do first.",
      "promptType": "User Prompt",
      "tags": [
        "master data",
        "assessment",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa5b5ce5-317c-4f02-8c5d-96ecb733b3d1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f89eeae0-b26f-4dcb-9e3c-72247df3d29f",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "a0611c47-bbed-4c7f-ab27-c6a6a7e95584",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "17ee1e60-67ae-45c7-b5ae-1523a4302de4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:49.000Z",
      "updatedAt": "2026-10-05T09:04:49.000Z"
    },
    {
      "id": "6a7648af-f1cf-45ba-986a-78d2d63be7b9",
      "name": "MDM style decision and case",
      "description": "The master data architecture styles compared for one entity and the one-page case to the governance body for the recommended one.",
      "promptType": "User Prompt",
      "tags": [
        "master data",
        "decision",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa5b5ce5-317c-4f02-8c5d-96ecb733b3d1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f89eeae0-b26f-4dcb-9e3c-72247df3d29f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "54788c00-0020-420a-9537-f666a9546d58",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3cac05d5-3023-44ec-822c-9dfa0061fc16",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "c10ab4f3-c4d3-4727-bba5-5de0d1384bbd",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:50.000Z",
      "updatedAt": "2026-10-05T09:04:50.000Z"
    },
    {
      "id": "bca5ed30-b2fd-40b6-862b-d5ade2cd609b",
      "name": "Golden record and hierarchies",
      "description": "The matching, survivorship and unmerge rules for one entity's golden record and the design of the hierarchies over it.",
      "promptType": "User Prompt",
      "tags": [
        "master data",
        "golden record",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa5b5ce5-317c-4f02-8c5d-96ecb733b3d1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f89eeae0-b26f-4dcb-9e3c-72247df3d29f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "aaaddeec-4c81-4c34-9c8d-b424a6a06794",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b29e83dd-c5f7-4954-9d77-78b3536db6ef",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "02f32eb3-df99-409c-bb8e-e6498a272748",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:51.000Z",
      "updatedAt": "2026-10-05T09:04:51.000Z"
    },
    {
      "id": "05a39604-0a6d-46f2-ba24-6cfbc6656ee2",
      "name": "Reference data governance",
      "description": "The governance of code sets: enterprise against local, owners, change process, crosswalks, external standards and the rules for holding a copy.",
      "promptType": "User Prompt",
      "tags": [
        "reference data",
        "governance",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa5b5ce5-317c-4f02-8c5d-96ecb733b3d1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f89eeae0-b26f-4dcb-9e3c-72247df3d29f",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "2d012503-aa64-4530-a36a-ed0fe9f22cc5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "d81bf753-c72c-4451-aa39-5911db9347a9",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:52.000Z",
      "updatedAt": "2026-10-05T09:04:52.000Z"
    },
    {
      "id": "3b4e4e0d-f5e8-46a5-9992-b436d8048202",
      "name": "Ownership model and RACI",
      "description": "The tiers of data ownership with proposed owners per domain, and the responsibility matrix for one domain with one accountable role per activity.",
      "promptType": "User Prompt",
      "tags": [
        "ownership",
        "raci",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "4cce2fce-5512-4079-be72-2d4b1344ed7c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "cba513c9-dc10-4578-8b12-177de78056ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "55c20ca5-36fa-4e31-8407-019514924951",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4089a217-b070-4d94-8d1b-b00c153d4f72",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "22ab5c73-66b7-456f-982c-510d4fe0d7a8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:53.000Z",
      "updatedAt": "2026-10-05T09:04:53.000Z"
    },
    {
      "id": "0232668e-08ad-42ec-8770-c3c61628ce3a",
      "name": "Data steward role",
      "description": "The role description of a data steward for one domain: responsibilities, decision rights, time, skills and measures.",
      "promptType": "User Prompt",
      "tags": [
        "stewardship",
        "role",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "4cce2fce-5512-4079-be72-2d4b1344ed7c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "cba513c9-dc10-4578-8b12-177de78056ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "2a983c59-2c35-4b66-ac10-9b434f506344",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "d73047d1-ee2d-461b-b2df-bc1eb32cd9c7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3894918a-a3e0-4ea3-b834-a542a3f717ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:54.000Z",
      "updatedAt": "2026-10-05T09:04:54.000Z"
    },
    {
      "id": "d477c70b-4314-4d9e-b5f8-f66e3187df87",
      "name": "Council charter and policy hierarchy",
      "description": "The charter of the governance body and the hierarchy of policies, standards, guidelines and procedures with the existing documents placed in it.",
      "promptType": "User Prompt",
      "tags": [
        "governance",
        "charter",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "4cce2fce-5512-4079-be72-2d4b1344ed7c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "cba513c9-dc10-4578-8b12-177de78056ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7bb7272e-4c54-418b-bed3-2b0c85e9c49c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "63b7a5b2-05ca-40b3-a8fb-5bf94c005c32",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:55.000Z",
      "updatedAt": "2026-10-05T09:04:55.000Z"
    },
    {
      "id": "b92a5155-058e-4067-b7c9-812151f166bd",
      "name": "Governance operating model paper",
      "description": "The paper that proposes the governance operating model to the executive: bodies, decision rights, cadence, flow of work, time asked and measures.",
      "promptType": "User Prompt",
      "tags": [
        "governance",
        "operating model",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "4cce2fce-5512-4079-be72-2d4b1344ed7c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "cba513c9-dc10-4578-8b12-177de78056ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e42aaa05-320b-4707-8a53-f21233ab0924",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "e2bb791c-3e18-4e40-a9d1-7acff353838d",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3894918a-a3e0-4ea3-b834-a542a3f717ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "d2b40e2a-7174-41ac-829e-7507a8132681",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:56.000Z",
      "updatedAt": "2026-10-05T09:04:56.000Z"
    },
    {
      "id": "0fb4bc38-364b-45de-8fc0-42d835f92b30",
      "name": "Critical elements and quality rules",
      "description": "The critical data elements of one domain and the quality rules for them by dimension, each with its reference, check point and owner.",
      "promptType": "User Prompt",
      "tags": [
        "data quality",
        "rules",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa256d33-57ad-4df3-bc98-446bc66ac0cb",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "17c66ebf-d307-452b-933c-4f3f0ddf7921",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f78fd48b-a0af-4e7d-af88-2a5e786d4423",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "aa9deb55-2045-43e2-af83-82914d7d2768",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "d530c9de-423d-430a-9388-5f114863b155",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "59502c57-732a-49d5-85c5-08da80e44444",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:57.000Z",
      "updatedAt": "2026-10-05T09:04:57.000Z"
    },
    {
      "id": "8500b55a-b545-42ba-92f4-30a2e9012a49",
      "name": "Thresholds and scorecard",
      "description": "The thresholds and targets per rule reasoned from the use of the data, and the design of the scorecard that reports them.",
      "promptType": "User Prompt",
      "tags": [
        "data quality",
        "scorecard",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa256d33-57ad-4df3-bc98-446bc66ac0cb",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "17c66ebf-d307-452b-933c-4f3f0ddf7921",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9725a903-8c50-4525-9401-80af5456a203",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "dc451da3-5c22-4940-a7c8-ac5d82106b94",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "17ee1e60-67ae-45c7-b5ae-1523a4302de4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "59502c57-732a-49d5-85c5-08da80e44444",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:58.000Z",
      "updatedAt": "2026-10-05T09:04:58.000Z"
    },
    {
      "id": "81b1f032-1230-4bc3-b73a-a76985bc2765",
      "name": "Root cause and remediation",
      "description": "Quality problems traced to their causes in the architecture and process, and the remediation plan with owners, measures and the decisions needed.",
      "promptType": "User Prompt",
      "tags": [
        "data quality",
        "root cause",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa256d33-57ad-4df3-bc98-446bc66ac0cb",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "17c66ebf-d307-452b-933c-4f3f0ddf7921",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "648c8c8b-b24f-45c0-9d33-ece3f9fc7002",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b1cc71e2-b4e1-4c21-8d19-1821167fc76b",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "ff6ed2d2-bf79-4a10-b818-0d3e7f35a3b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9a146d4b-ac42-4af8-a3ca-d449ca23cc22",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:04:59.000Z",
      "updatedAt": "2026-10-05T09:04:59.000Z"
    },
    {
      "id": "ce12e421-18a4-4677-a6b5-f9ead7a4bad5",
      "name": "Quality requirements for the specification",
      "description": "The testable data quality requirements for the architecture requirements specification, by critical element.",
      "promptType": "User Prompt",
      "tags": [
        "data quality",
        "requirements",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa256d33-57ad-4df3-bc98-446bc66ac0cb",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "17c66ebf-d307-452b-933c-4f3f0ddf7921",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7299de5e-7ba7-4600-b3fd-fc3104d53ff1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9a146d4b-ac42-4af8-a3ca-d449ca23cc22",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "78b38b94-b564-4a1d-908b-852508e873db",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:00.000Z",
      "updatedAt": "2026-10-05T09:05:00.000Z"
    },
    {
      "id": "81efb480-e246-441d-bb92-575427f371c0",
      "name": "Lineage scope and a critical report's lineage",
      "description": "The scope and granularity of lineage for an initiative, and the hop-by-hop lineage of one critical report with inferred hops marked.",
      "promptType": "User Prompt",
      "tags": [
        "lineage",
        "report",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "6f508b76-7f2c-40f6-acec-8c583d9ad6e6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac25a2db-3a0d-4467-93e8-cedf6cab82c0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "0017840f-988f-4560-8871-09ede87d9cbd",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b405485e-62f4-462f-b74f-1b154839501c",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e616a106-d7d9-499c-988f-eebfc7f9bd0e",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "45c4fde2-411c-42d6-8ce7-84895051d08f",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:01.000Z",
      "updatedAt": "2026-10-05T09:05:01.000Z"
    },
    {
      "id": "44551019-fdea-4c3d-99c8-69309fcf7795",
      "name": "Metadata architecture",
      "description": "The metadata architecture as capabilities and flows: kinds of metadata, sources of truth, how catalog, glossary, models and repository stay consistent.",
      "promptType": "User Prompt",
      "tags": [
        "metadata",
        "architecture",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "6f508b76-7f2c-40f6-acec-8c583d9ad6e6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac25a2db-3a0d-4467-93e8-cedf6cab82c0",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "9cefd582-c716-49d7-a853-37d7e0db1762",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f63cd43d-9f16-487a-9b3f-3eaf9cc4ae27",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:02.000Z",
      "updatedAt": "2026-10-05T09:05:02.000Z"
    },
    {
      "id": "109c85d2-2783-4972-887e-98e95299c049",
      "name": "Metadata standard",
      "description": "The minimum metadata every data set, entity and report must carry, who records it, the joining rules and what a project must show before go-live.",
      "promptType": "User Prompt",
      "tags": [
        "metadata",
        "standard",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "6f508b76-7f2c-40f6-acec-8c583d9ad6e6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5cf34304-5325-4e64-b3c6-df252bab83a6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "d81bf753-c72c-4451-aa39-5911db9347a9",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "e934dc9c-a5e7-418c-a681-1e45f86e8d48",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:03.000Z",
      "updatedAt": "2026-10-05T09:05:03.000Z"
    },
    {
      "id": "81ebbde0-fe23-4428-bfc0-50486d4194db",
      "name": "Lineage gaps and impact analysis",
      "description": "The gaps in lineage with the outputs they expose and how to close them, and the downstream impact of a described change.",
      "promptType": "User Prompt",
      "tags": [
        "lineage",
        "impact",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "6f508b76-7f2c-40f6-acec-8c583d9ad6e6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac25a2db-3a0d-4467-93e8-cedf6cab82c0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "48b64607-8873-460a-bfd1-949c8abe602c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "57767605-4e7f-4d80-a75c-8862f21c3a95",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "ff6ed2d2-bf79-4a10-b818-0d3e7f35a3b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "e616a106-d7d9-499c-988f-eebfc7f9bd0e",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "3a1f8917-974a-4d85-b8e3-5f0ae1bf4bbb",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:04.000Z",
      "updatedAt": "2026-10-05T09:05:04.000Z"
    },
    {
      "id": "8e4bcaa7-5e08-4605-aa92-1799ea7a8e6f",
      "name": "Platform options",
      "description": "Warehouse, lake, lakehouse and mesh compared against the enterprise's needs and shape, with a recommendation and what would change it.",
      "promptType": "User Prompt",
      "tags": [
        "platform",
        "options",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "c479b2ab-8667-4f8e-a438-9fdb045cb8ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5619954-c2e4-4418-a511-e630bc755dd7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "560ad415-0fcb-4134-a28c-ebc2cca59b15",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ea6dcdf9-1672-4221-884a-1263c473ab87",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:05.000Z",
      "updatedAt": "2026-10-05T09:05:05.000Z"
    },
    {
      "id": "b161f9bc-e249-4a31-9d8d-175a8e04ce07",
      "name": "Target platform state",
      "description": "The target analytics platform as layers and responsibilities, with the consumption patterns it must serve and the ones it does not yet.",
      "promptType": "User Prompt",
      "tags": [
        "platform",
        "target",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "c479b2ab-8667-4f8e-a438-9fdb045cb8ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5619954-c2e4-4418-a511-e630bc755dd7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9d691cd2-af2f-4051-9c0f-6e6ec5c7b7a0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f1445ae7-d314-4bd2-be24-4b38018fd28d",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f63cd43d-9f16-487a-9b3f-3eaf9cc4ae27",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:06.000Z",
      "updatedAt": "2026-10-05T09:05:06.000Z"
    },
    {
      "id": "9c42d8d3-117d-46de-82a4-a3a186811713",
      "name": "Data product",
      "description": "One data product specified by its consumers, contents, interfaces and promises, so a consumer can rely on it and the owner knows the commitment.",
      "promptType": "User Prompt",
      "tags": [
        "platform",
        "data product",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "c479b2ab-8667-4f8e-a438-9fdb045cb8ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5619954-c2e4-4418-a511-e630bc755dd7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "24af1ca3-e8d7-468b-baca-91c68f010a62",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "799c8020-89ea-4700-a7ad-cfea133e88f5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "7d3c9eb8-f61b-4e69-aa80-41ec485483a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:07.000Z",
      "updatedAt": "2026-10-05T09:05:07.000Z"
    },
    {
      "id": "5196a54f-7ecf-4c6a-8c07-1705098fcc45",
      "name": "Team split and transition stages",
      "description": "The agreement between domain teams and the platform team, and the staged transition from today's platform to the target.",
      "promptType": "User Prompt",
      "tags": [
        "platform",
        "transition",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "c479b2ab-8667-4f8e-a438-9fdb045cb8ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5619954-c2e4-4418-a511-e630bc755dd7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "964b0905-a561-4666-84e2-f9ea17212ec0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c9682d8b-3b69-4a33-9c41-a4c27723b6c7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "4e596cfc-6012-4751-9e9c-50252a749948",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:08.000Z",
      "updatedAt": "2026-10-05T09:05:08.000Z"
    },
    {
      "id": "f57db411-c53d-4d40-9f5f-b632fb86b606",
      "name": "Integration pattern per flow",
      "description": "The integration pattern chosen for each flow from freshness, volume, ownership and failure behaviour, with the alternatives rejected.",
      "promptType": "User Prompt",
      "tags": [
        "integration",
        "patterns",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "305f167e-5b4f-46e6-b032-ef078e7d7953",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1181babd-934d-488c-b845-ffe6896622ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "84ea229d-5190-4baf-9592-5fc06cd58ad1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "019d2011-a61b-4e18-bd78-f96fcfda6260",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:09.000Z",
      "updatedAt": "2026-10-05T09:05:09.000Z"
    },
    {
      "id": "c12c625e-ce06-45e2-bbf0-71e11d91aa1c",
      "name": "Canonical model decision",
      "description": "The one-page decision paper on whether to exchange data through a shared canonical model, pairwise interfaces or a middle path.",
      "promptType": "User Prompt",
      "tags": [
        "integration",
        "canonical",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "305f167e-5b4f-46e6-b032-ef078e7d7953",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1181babd-934d-488c-b845-ffe6896622ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "24153937-bdc1-4568-8368-0aa8650e2a36",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c10ab4f3-c4d3-4727-bba5-5de0d1384bbd",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:10.000Z",
      "updatedAt": "2026-10-05T09:05:10.000Z"
    },
    {
      "id": "574fe594-3520-4a91-90bd-ba3edfb8ac99",
      "name": "Exchange standard and data contracts",
      "description": "The data exchange standard with event and message governance, and the data contract between a producing domain and its consumers.",
      "promptType": "User Prompt",
      "tags": [
        "integration",
        "contracts",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "305f167e-5b4f-46e6-b032-ef078e7d7953",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1181babd-934d-488c-b845-ffe6896622ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "02676f1d-d4e1-4ca3-9ad0-b3ced6025d07",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "97713055-6744-4383-9f7b-a42a67884350",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7944c208-84b7-4872-9af3-e0af935e17b4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:11.000Z",
      "updatedAt": "2026-10-05T09:05:11.000Z"
    },
    {
      "id": "8c8752c8-f7c3-467c-a162-70f63c218029",
      "name": "Integration principles and gaps",
      "description": "The integration principles reconciled with the data principles, and the gaps in today's flows with the change that closes each.",
      "promptType": "User Prompt",
      "tags": [
        "integration",
        "principles",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "305f167e-5b4f-46e6-b032-ef078e7d7953",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1181babd-934d-488c-b845-ffe6896622ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "59653fe0-fd98-441b-8989-1fcc32f30e01",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b49977a4-19e8-48b7-a49e-e0b1f6599f89",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "b8cc7f8a-5dcf-4bc2-b436-5eaf9a8bcd09",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "455f8d7b-760c-419f-9693-349d6da0ceed",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:12.000Z",
      "updatedAt": "2026-10-05T09:05:12.000Z"
    },
    {
      "id": "b1c42c1e-0c65-4180-8d63-f4a19b2d5c0f",
      "name": "Migration strategy and diagram",
      "description": "The migration strategies compared with a recommendation, and the migration diagram described for drawing with its order and dependencies.",
      "promptType": "User Prompt",
      "tags": [
        "migration",
        "strategy",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "81d973c7-5052-4287-b834-5d403632295c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "279f882b-b953-44da-b309-1ad64b392cf4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a15e84e8-3b7a-49e0-be7d-b86be6f04652",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "24cff9e0-4bda-4113-a1b2-b8b8d38782b3",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "47faa8b5-bd0f-44c8-928c-6d58feb306ac",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:13.000Z",
      "updatedAt": "2026-10-05T09:05:13.000Z"
    },
    {
      "id": "deee0e18-7376-4095-95df-12082190bba4",
      "name": "Mapping and cleansing decisions",
      "description": "The entity-level source to target mapping and the decision, per quality problem, of where it is cleaned or accepted.",
      "promptType": "User Prompt",
      "tags": [
        "migration",
        "mapping",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "81d973c7-5052-4287-b834-5d403632295c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "279f882b-b953-44da-b309-1ad64b392cf4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "0023ede6-87a7-4456-b54a-29545928059e",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ef961720-478c-4d1c-936f-03f973eb926d",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "bc40d393-3b7e-44da-bb73-a5780a711c9b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "197493c3-6382-49fe-9142-a62cefba6ef3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:14.000Z",
      "updatedAt": "2026-10-05T09:05:14.000Z"
    },
    {
      "id": "7fd71117-8dff-4422-b476-374dcff17775",
      "name": "Reconciliation and cutover",
      "description": "The reconciliation and cutover approach the business owners sign: proofs, rehearsals, sequence, point of no return and fallback.",
      "promptType": "User Prompt",
      "tags": [
        "migration",
        "cutover",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "81d973c7-5052-4287-b834-5d403632295c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "279f882b-b953-44da-b309-1ad64b392cf4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "27cefa46-0a31-4d2f-83dc-546213f721fe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "197493c3-6382-49fe-9142-a62cefba6ef3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:15.000Z",
      "updatedAt": "2026-10-05T09:05:15.000Z"
    },
    {
      "id": "e1ab9aea-3243-4c37-b7a4-deb4daeecb47",
      "name": "Migration risks and legacy archive",
      "description": "The migration risk register and the decision on what happens to the data left in the retired systems.",
      "promptType": "User Prompt",
      "tags": [
        "migration",
        "risks",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "81d973c7-5052-4287-b834-5d403632295c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "279f882b-b953-44da-b309-1ad64b392cf4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "53664898-56ea-48d6-ba0f-c5ea9080abe9",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "11302507-82fa-4925-ab17-31335cd82164",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "7afa57f5-01d2-467a-b20a-7c77718ef8d7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e09b6e29-0691-4d1a-bcc0-a99be4c9f1fc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:16.000Z",
      "updatedAt": "2026-10-05T09:05:16.000Z"
    },
    {
      "id": "aa97b6f7-cd18-4486-8aa8-f670fd51d047",
      "name": "Retention mapping",
      "description": "Every entity in scope mapped to its retention class, period and trigger as the schedule states them, with the entities the schedule does not cover.",
      "promptType": "User Prompt",
      "tags": [
        "retention",
        "mapping",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e10c38ac-7e60-447a-9279-311cacf40f2b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5d7f5964-426c-4014-b338-cd536ad8e518",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e185e9bf-70bb-4a65-95f1-ff3ae9a239e6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "bc40d393-3b7e-44da-bb73-a5780a711c9b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "21677300-9111-4905-aa88-e4212261edd3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:17.000Z",
      "updatedAt": "2026-10-05T09:05:17.000Z"
    },
    {
      "id": "1e4207ec-164a-497d-9364-aee1ebdebd4f",
      "name": "Archive and disposal design",
      "description": "The archive tiers and the deletion design: how data moves, keeps its meaning, is found, and is removed and proven removed from every copy.",
      "promptType": "User Prompt",
      "tags": [
        "retention",
        "archive",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e10c38ac-7e60-447a-9279-311cacf40f2b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5d7f5964-426c-4014-b338-cd536ad8e518",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "82381c34-cd59-4419-a957-1ffac8698d49",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4ce10e63-2f8c-479c-bb1a-635b21aa5404",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "21677300-9111-4905-aa88-e4212261edd3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:18.000Z",
      "updatedAt": "2026-10-05T09:05:18.000Z"
    },
    {
      "id": "fa986592-b906-4f3b-a328-1c7c2e5881fa",
      "name": "Legal hold and retention gaps",
      "description": "How the architecture honours a legal hold across systems and backups, and the gaps between the schedule and what the systems do.",
      "promptType": "User Prompt",
      "tags": [
        "retention",
        "legal hold",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e10c38ac-7e60-447a-9279-311cacf40f2b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5d7f5964-426c-4014-b338-cd536ad8e518",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "53664898-56ea-48d6-ba0f-c5ea9080abe9",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "942334f0-db30-4b6c-b1ac-5b2921832752",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "75047e6b-a3ee-4e88-902f-db034b63ce43",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e09b6e29-0691-4d1a-bcc0-a99be4c9f1fc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:19.000Z",
      "updatedAt": "2026-10-05T09:05:19.000Z"
    },
    {
      "id": "9c402237-6806-4ea3-a1fb-2f52118aad2c",
      "name": "Note to records management and legal",
      "description": "The note that reports what the architecture found and asks records management and legal the questions that change the design.",
      "promptType": "User Prompt",
      "tags": [
        "retention",
        "conversation",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e10c38ac-7e60-447a-9279-311cacf40f2b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5d7f5964-426c-4014-b338-cd536ad8e518",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "176f0f86-b0ff-4c1d-920c-e791d3bd82a0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "dd4fb49e-f2bc-463e-a982-a27a5244e7fe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "21677300-9111-4905-aa88-e4212261edd3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "6a055b28-edad-409e-a92d-3d16e5897b95",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:20.000Z",
      "updatedAt": "2026-10-05T09:05:20.000Z"
    },
    {
      "id": "318c5e8d-4b41-4df1-b959-b63cd473d28c",
      "name": "Due diligence request list",
      "description": "The data request list for due diligence, prioritised, with why each item matters and what its absence would mean.",
      "promptType": "User Prompt",
      "tags": [
        "due diligence",
        "requests",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e8d9ad06-16a9-4aac-9496-b31ef7bb0666",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac127395-6cd7-458d-9a2f-38f8ccb79118",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "523ad2c1-a2b3-4155-b3d7-42cca743ef5b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1ccabe20-9c0e-4e88-9d7d-24b5dfffde02",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "45c4fde2-411c-42d6-8ce7-84895051d08f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:21.000Z",
      "updatedAt": "2026-10-05T09:05:21.000Z"
    },
    {
      "id": "68e217a1-d187-499b-87b3-5ad6e5ec57bc",
      "name": "Landscape assessment and data risks",
      "description": "The target's data landscape rated against the acquirer's standard, and the data risk register for the deal with what must be settled before signing.",
      "promptType": "User Prompt",
      "tags": [
        "due diligence",
        "assessment",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e8d9ad06-16a9-4aac-9496-b31ef7bb0666",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac127395-6cd7-458d-9a2f-38f8ccb79118",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ea575baa-0557-473d-980b-38dcd2ac214d",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "8c4aa5a3-9e64-4343-bf98-25494c90cea9",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "b1880c77-a840-42b4-9342-b22e631500d4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fbc6b078-41f4-4bb6-a3b7-50025dced61c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:22.000Z",
      "updatedAt": "2026-10-05T09:05:22.000Z"
    },
    {
      "id": "c5d33817-4649-44a4-a5b5-972f43cf7d8d",
      "name": "Integration options and carve-out",
      "description": "The options for the two data estates after the deal compared with a recommendation, and the carve-out design where a business is being separated.",
      "promptType": "User Prompt",
      "tags": [
        "due diligence",
        "integration options",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e8d9ad06-16a9-4aac-9496-b31ef7bb0666",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac127395-6cd7-458d-9a2f-38f8ccb79118",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9ec30e2a-84ff-4d7a-af8a-1484273495c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "648f601d-5b67-40a8-a34f-9380cbc0f386",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "ea6dcdf9-1672-4221-884a-1263c473ab87",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:23.000Z",
      "updatedAt": "2026-10-05T09:05:23.000Z"
    },
    {
      "id": "bdd483eb-e36e-4b31-84d5-e83cb0bfe33e",
      "name": "Day one and the integration roadmap",
      "description": "What the combined business must do with data on day one and the staged data integration roadmap that follows.",
      "promptType": "User Prompt",
      "tags": [
        "due diligence",
        "roadmap",
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e8d9ad06-16a9-4aac-9496-b31ef7bb0666",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac127395-6cd7-458d-9a2f-38f8ccb79118",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fff4773d-39d2-4426-bef7-d2d4781fc169",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "bc5aa0e8-74ee-4a90-ae3c-a775efd7a8fc",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "1ccabe20-9c0e-4e88-9d7d-24b5dfffde02",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "45c4fde2-411c-42d6-8ce7-84895051d08f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:24.000Z",
      "updatedAt": "2026-10-05T09:05:24.000Z"
    },
    {
      "id": "183ff9ef-03e9-41a7-ad36-896a8db6a728",
      "name": "Run Phase C, Data Architecture",
      "description": "From the scope of the data work to its stakeholder review: baseline, target, gaps and work packages, in order.",
      "promptType": "Prompt Set",
      "tags": [
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "format": "set",
      "promptIds": [
        "b9ad93ce-c0b4-4563-8f6d-e84ef4cf530e",
        "21634bad-b916-4b36-aa78-4672322e9eb3",
        "1b4526b3-61a3-46bf-b9c4-a2e8356b13dc",
        "96e18d0e-0452-413b-8ab5-d80cbd860da3",
        "a327876b-3e25-40c8-b950-28dd93e4cb58",
        "dafb147c-a5bf-427b-b5e5-753978d2747d",
        "e57f6585-f21b-4066-a6c0-37cb47531695",
        "db2ab461-89dc-492f-bd34-b6da3b4d78c3"
      ],
      "blockRefs": [],
      "folderId": "205afb9e-d0b7-4202-93a8-a95e2c975ed7",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:25.000Z",
      "updatedAt": "2026-10-05T09:05:25.000Z"
    },
    {
      "id": "b80521d2-1505-4621-ad6a-a0dc5738dd69",
      "name": "Model a domain from conceptual to physical",
      "description": "One domain modelled conceptual, logical and physical, reviewed, and explained to the business, in order.",
      "promptType": "Prompt Set",
      "tags": [
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "format": "set",
      "promptIds": [
        "cae5b8cb-ae9d-4583-ac63-ffe292337651",
        "a81c66da-0e90-4eef-8b6e-a0d863ea9918",
        "3530613c-c2ff-43f3-9216-edf85df8517a",
        "f6655784-c7cf-42a0-a1cc-58ed024db1be",
        "44e90494-df84-4b19-a200-ea7d47983b66"
      ],
      "blockRefs": [],
      "folderId": "e8fe2255-e449-4e71-aaca-0aed2bf3cfb6",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:26.000Z",
      "updatedAt": "2026-10-05T09:05:26.000Z"
    },
    {
      "id": "1a6b5b63-2c65-4131-a52f-2ae5fb926d72",
      "name": "Design an initiative for privacy",
      "description": "From the personal data inventory to the design review, the privacy assessment inputs and the cross-border map, in order.",
      "promptType": "Prompt Set",
      "tags": [
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "format": "set",
      "promptIds": [
        "dfabd198-53fa-4357-9564-38ea9e0f658c",
        "a9cfdfa1-a0a4-49bc-a55e-74be9777979d",
        "b4002e08-dd48-4ea7-a651-a17fcf6ead1a",
        "668305ba-a233-4409-8184-500f29ee3e2e"
      ],
      "blockRefs": [],
      "folderId": "3ac61437-1862-4528-ac7a-c8d457c7c180",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:27.000Z",
      "updatedAt": "2026-10-05T09:05:27.000Z"
    },
    {
      "id": "8b3bc0c5-522d-48a5-94a7-f5ea75c674ec",
      "name": "Master an entity",
      "description": "From which entities deserve mastering to the style decision and the golden record rules, in order.",
      "promptType": "Prompt Set",
      "tags": [
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "format": "set",
      "promptIds": [
        "70f465c7-f953-4a52-aabf-ecffb06a89b3",
        "6a7648af-f1cf-45ba-986a-78d2d63be7b9",
        "bca5ed30-b2fd-40b6-862b-d5ade2cd609b"
      ],
      "blockRefs": [],
      "folderId": "67236ab7-1dca-4d77-af5d-55fc26c6a3b2",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:28.000Z",
      "updatedAt": "2026-10-05T09:05:28.000Z"
    },
    {
      "id": "1b0ce014-dc80-4968-a90d-f26ef326ff08",
      "name": "Plan a data migration",
      "description": "From the migration strategy to the mapping, the reconciliation and cutover, and the risks and legacy archive, in order.",
      "promptType": "Prompt Set",
      "tags": [
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "format": "set",
      "promptIds": [
        "b1c42c1e-0c65-4180-8d63-f4a19b2d5c0f",
        "deee0e18-7376-4095-95df-12082190bba4",
        "7fd71117-8dff-4422-b476-374dcff17775",
        "e1ab9aea-3243-4c37-b7a4-deb4daeecb47"
      ],
      "blockRefs": [],
      "folderId": "58855823-f578-4f5b-bf52-7ca9b5a78976",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:29.000Z",
      "updatedAt": "2026-10-05T09:05:29.000Z"
    },
    {
      "id": "55535f64-9120-4523-8372-c31507be9396",
      "name": "Data due diligence and integration for a deal",
      "description": "From the data request list to the day one actions and the integration roadmap, in order.",
      "promptType": "Prompt Set",
      "tags": [
        "Data architecture pack"
      ],
      "saveMode": "dynamic",
      "format": "set",
      "promptIds": [
        "318c5e8d-4b41-4df1-b959-b63cd473d28c",
        "68e217a1-d187-499b-87b3-5ad6e5ec57bc",
        "c5d33817-4649-44a4-a5b5-972f43cf7d8d",
        "bdd483eb-e36e-4b31-84d5-e83cb0bfe33e"
      ],
      "blockRefs": [],
      "folderId": "82a02bd6-2b47-4e73-93ee-72f1341c36ed",
      "archivedAt": null,
      "maxCharCount": null,
      "rating": null,
      "favorite": false,
      "createdAt": "2026-10-05T09:05:30.000Z",
      "updatedAt": "2026-10-05T09:05:30.000Z"
    }
  ],
  "promptVersions": [
    {
      "id": "dc80b5ec-0d4a-4d20-92c8-1e96f9d71f9f",
      "promptId": "172846ff-e711-4b85-b1a1-9f4a2632ff7e",
      "name": "Data principles catalog",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "d70f166b-4794-4074-be22-6b404db7840d",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "77bfb472-5579-495a-965b-4d30682d0360",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b8cc7f8a-5dcf-4bc2-b436-5eaf9a8bcd09",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "principles",
        "catalog",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:05.000Z"
    },
    {
      "id": "0aa03921-6d84-4c44-a4d7-f60fad48700e",
      "promptId": "59d2b86c-99a9-44a0-9b2a-f57ad38e1689",
      "name": "Review a draft principle",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "61bac58f-3554-4a3e-b986-ba5d2cdf1aa2",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "6029e3f8-9094-4a19-8508-e932efb0130f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "312c7d23-1359-43a3-87fe-7bff03f59efe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b8cc7f8a-5dcf-4bc2-b436-5eaf9a8bcd09",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "principles",
        "review",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:06.000Z"
    },
    {
      "id": "9b560d6f-866e-4101-b9ae-2f580724f9d3",
      "promptId": "b9ad93ce-c0b4-4563-8f6d-e84ef4cf530e",
      "name": "Scope the data architecture work",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "bbe70f70-a037-4ed7-8a11-faa92af7b3ac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "527d546d-672e-49ce-8270-88aa534f54b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "scope",
        "statement of architecture work",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:07.000Z"
    },
    {
      "id": "04b641f1-be44-4440-a5a9-b1e5d2c549b0",
      "promptId": "5be4c133-eb59-4235-8946-ab794539048b",
      "name": "Approach note and CDO kick-off",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "784c81d7-ce89-4ab1-ac2f-82fe811c0dc6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3a5c12ee-8338-4044-b8a1-318537a90916",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "4285bdda-45e6-48cc-8a26-032430d2e57a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "approach",
        "kick-off",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:08.000Z"
    },
    {
      "id": "06ea8616-f655-4400-a818-dc9c52ef686b",
      "promptId": "241c85cd-450f-4b6e-97df-54100905cd11",
      "name": "Principle exception request",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "61bac58f-3554-4a3e-b986-ba5d2cdf1aa2",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e2e5eccd-0107-4ef3-9460-48f69abda529",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "dd4fb49e-f2bc-463e-a982-a27a5244e7fe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "02f32eb3-df99-409c-bb8e-e6498a272748",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "principles",
        "exception",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:09.000Z"
    },
    {
      "id": "c41ad2a4-c19a-4e00-bb1f-2d092ad11d39",
      "promptId": "21634bad-b916-4b36-aa78-4672322e9eb3",
      "name": "Baseline inventory and entity list",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4dbd3fa1-324d-46c1-8fb3-04aa31162e76",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "38fe9f5d-7693-465d-9a2d-0a91aa811392",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "515e9301-e091-412a-af05-408c787c40a6",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "baseline",
        "inventory",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:10.000Z"
    },
    {
      "id": "8d4de8f5-a6b5-4047-82be-c56ae28bb794",
      "promptId": "1b4526b3-61a3-46bf-b9c4-a2e8356b13dc",
      "name": "Baseline description and questions to owners",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4dbd3fa1-324d-46c1-8fb3-04aa31162e76",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3bd0635c-6c3f-4c33-984c-0ea57f539d80",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "14eb1893-1f7b-4014-87ab-8922a7cc6036",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "45c4fde2-411c-42d6-8ce7-84895051d08f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "baseline",
        "document",
        "questions",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:11.000Z"
    },
    {
      "id": "f33d412f-f842-4d5f-9bd1-e0c47fe36252",
      "promptId": "96e18d0e-0452-413b-8ab5-d80cbd860da3",
      "name": "Baseline assessment and system of record conflicts",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4dbd3fa1-324d-46c1-8fb3-04aa31162e76",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "4b884d3d-c9b7-4a25-9a3e-7bd5c55b575f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4301c51f-8543-4bb0-bd0f-349d362a2388",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "baseline",
        "assessment",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:12.000Z"
    },
    {
      "id": "a766f436-2a1a-49d3-ba37-c1f08c017e19",
      "promptId": "304fa953-4f4c-49dc-90b7-fd15688d5608",
      "name": "Define the data entities",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "ecc88a7e-4160-4a44-af93-30609fd71f3f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "04b8977c-9a65-49f6-a416-4bd210cd22b2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "aa261336-018a-41f7-bbc8-a34d67526306",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "catalog",
        "entities",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:13.000Z"
    },
    {
      "id": "b25943fd-0e50-4124-8bfe-4a5c2b9e3c8d",
      "promptId": "6d36f122-6bba-4299-ba76-d45917ab8572",
      "name": "Logical and physical data components",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4de39862-b8c2-4234-a520-2e1a1eeeb3a1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "af8f1e14-e499-48ca-8ae7-bb2459f1a20e",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "04b8977c-9a65-49f6-a416-4bd210cd22b2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "catalog",
        "components",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:14.000Z"
    },
    {
      "id": "c2d9764f-e1a0-4653-9152-3d634deec6bd",
      "promptId": "d26f8036-a549-4b4b-ad04-8e36b35ae579",
      "name": "Review the catalog",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "103aee15-7cf4-4ac0-adc9-b0194eb32c6c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "312c7d23-1359-43a3-87fe-7bff03f59efe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "16fec59c-0847-4837-a504-623754e60094",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "catalog",
        "review",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:15.000Z"
    },
    {
      "id": "4d42b049-0c9a-4054-a7ba-be870002625d",
      "promptId": "93a5b7ef-c0fd-495d-974c-312df42ad519",
      "name": "Catalog standard and walkthrough note",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7c6eb957-9bdb-498a-beff-638d27c633a8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "61cc485f-b41b-4efa-8cf6-3dc6bdc59a39",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7944c208-84b7-4872-9af3-e0af935e17b4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "catalog",
        "standard",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:16.000Z"
    },
    {
      "id": "29af702f-1415-4616-85a0-d8950a6a21c8",
      "promptId": "cae5b8cb-ae9d-4583-ac63-ffe292337651",
      "name": "Conceptual data model",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "89436b13-83ce-4b02-9080-36bcded59aa9",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1b9af371-fec5-4a33-8466-ac52146de274",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "aa261336-018a-41f7-bbc8-a34d67526306",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "model",
        "conceptual",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:17.000Z"
    },
    {
      "id": "2980d436-e58e-428b-a68e-de1cb129ca06",
      "promptId": "a81c66da-0e90-4eef-8b6e-a0d863ea9918",
      "name": "Logical data model",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "db694ee9-8413-4e5f-aaee-23a0e33777c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "2ba79058-5326-443d-ab14-67e9449338b2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1b9af371-fec5-4a33-8466-ac52146de274",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c761b7b9-0838-40ad-918c-827e06792955",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "model",
        "logical",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:18.000Z"
    },
    {
      "id": "8546d1e4-096b-4489-90bc-51689f717b27",
      "promptId": "3530613c-c2ff-43f3-9216-edf85df8517a",
      "name": "Physical model considerations",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e4354209-d491-4ee9-b110-9b30296e28d9",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c761b7b9-0838-40ad-918c-827e06792955",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "model",
        "physical",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:19.000Z"
    },
    {
      "id": "bc590277-33c1-49e6-9d62-0ea39a22dd7a",
      "promptId": "f6655784-c7cf-42a0-a1cc-58ed024db1be",
      "name": "Model review and reconciliation",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e5fba729-cc07-42c8-986d-163edb424ba4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "84795e92-23bc-4479-bd82-e4fc1af708bd",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "e449b89a-dbde-4968-be0a-91ef0138b64c",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "b6a6f3ba-6f07-4947-ae65-d1e597347995",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "model",
        "review",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:20.000Z"
    },
    {
      "id": "4de10eda-4258-4b80-ae5a-7b9c357cebb8",
      "promptId": "44e90494-df84-4b19-a200-ea7d47983b66",
      "name": "Explain the model to the business",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "790d28f8-97cd-46a0-9758-2f882b110eb3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "8be6b534-bc52-489a-9129-5e4d6c662937",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "36bca6e6-dfe9-4691-ade6-18ca19df9293",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "29a5abd3-3811-49aa-be6e-1fb2078f1605",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "model",
        "communication",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:21.000Z"
    },
    {
      "id": "20515a70-731a-49b7-bcf0-a925dadac04f",
      "promptId": "814c1cb3-a6fb-4745-8931-463c5ae6b58a",
      "name": "Define a business term",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "a7ebbec8-8c4d-46be-8b89-a8bed032b280",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "73a4c9b4-e50d-4aa5-814e-42483c84beac",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "1a4fbee5-6561-4d7f-a77d-7109f77b7a1a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fa9babc0-71fb-45e4-9060-4e18f63c8179",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fb3fd01a-af33-4475-bc6f-f9e4b9db40b1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "glossary",
        "definition",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:22.000Z"
    },
    {
      "id": "3a4f057b-8b25-4bd8-ad48-a72bc530e66b",
      "promptId": "bd3893af-8b4a-49fa-aa1b-222e72f6c7d0",
      "name": "Resolve a definition conflict",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "a7ebbec8-8c4d-46be-8b89-a8bed032b280",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "73a4c9b4-e50d-4aa5-814e-42483c84beac",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "3ab428e0-e30e-423b-994d-75dcc933b1c6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "7b60dbcd-f03c-459b-a6c9-8b3349158083",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "fb3fd01a-af33-4475-bc6f-f9e4b9db40b1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "glossary",
        "conflict",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:23.000Z"
    },
    {
      "id": "705b7f55-71c5-45ff-a3dc-8633e4c96505",
      "promptId": "0a00adfd-5920-45be-a753-027a0c7a1924",
      "name": "Glossary coverage and model mapping",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "a7ebbec8-8c4d-46be-8b89-a8bed032b280",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "73a4c9b4-e50d-4aa5-814e-42483c84beac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3ca572ee-a5fa-4063-9be1-5b4bef06065a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "47c0e418-c8da-4b03-a64e-59b739f213a5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "efa111d5-02d9-491f-b068-b323eee1b438",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "bc40d393-3b7e-44da-bb73-a5780a711c9b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": true
        }
      ],
      "tags": [
        "glossary",
        "mapping",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:24.000Z"
    },
    {
      "id": "05c99af1-f27c-4eb4-af1f-c4618b6d64d9",
      "promptId": "86e52f16-286d-48e4-8435-ba96a625e0ac",
      "name": "Glossary standard",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "a7ebbec8-8c4d-46be-8b89-a8bed032b280",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "0f0763a2-f0c6-43f9-b17a-104b68b0a0d6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "d81bf753-c72c-4451-aa39-5911db9347a9",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "glossary",
        "standard",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:25.000Z"
    },
    {
      "id": "b85d1b9a-aa34-422f-9d72-a0d14bbb26fa",
      "promptId": "b04c4fe5-6e26-4ba5-a836-b45a1422d93c",
      "name": "Entity to business function matrix",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f03a6b71-1e3c-4ee3-81ad-a5141646ed87",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "284c8953-1748-4e3a-8ab8-e23810d49c83",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5a1d7ab-517b-41f0-b395-131d362813d7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "e7f8e5c3-c814-46cd-aaf4-0a8dc50485da",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "matrix",
        "business function",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:26.000Z"
    },
    {
      "id": "d4a128c8-7f25-49a4-ba3a-75acf6a7f2b3",
      "promptId": "e318919e-a093-405d-abab-9dd8ce682215",
      "name": "Application to data matrix",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f03a6b71-1e3c-4ee3-81ad-a5141646ed87",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "a72b9bd7-a435-4693-8076-858c591699ec",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5a1d7ab-517b-41f0-b395-131d362813d7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "matrix",
        "application",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:27.000Z"
    },
    {
      "id": "e92f1c37-26af-41cd-bf8b-f10061a11927",
      "promptId": "7a1dfa94-8bf7-44d3-a73d-6417026517fd",
      "name": "What the matrices show",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f03a6b71-1e3c-4ee3-81ad-a5141646ed87",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "9149ccd5-cf3f-489e-856b-16a31ae48d09",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "7a130057-5ce9-4792-b27f-cd1f4656090b",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e7f8e5c3-c814-46cd-aaf4-0a8dc50485da",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "matrix",
        "analysis",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:28.000Z"
    },
    {
      "id": "f0865c03-0a45-4738-8bd2-c55772c9dd25",
      "promptId": "289d0544-5991-44f5-ba16-1cc8ca04aa54",
      "name": "Settle a system of record conflict",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f03a6b71-1e3c-4ee3-81ad-a5141646ed87",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "cd464aae-5f1e-4577-846b-cc394b56ed4a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b67001c0-fc33-4b96-8434-947135769dfb",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "matrix",
        "system of record",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:29.000Z"
    },
    {
      "id": "f009113c-bf7a-44b3-990f-83f5b728aff8",
      "promptId": "3aceada7-27fe-4315-bb4f-662a45b6318a",
      "name": "Data dissemination diagram",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "57d4f5ab-f211-4bdd-b93b-1c28b5eb5794",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "8c816b52-12a0-4de6-a296-d9eeef82127a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "49b29bb2-bba9-4c1a-9b23-cbc8a1245e90",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "47faa8b5-bd0f-44c8-928c-6d58feb306ac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "diagram",
        "dissemination",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:30.000Z"
    },
    {
      "id": "e441ec11-e2a1-44dd-9013-7472baedafd3",
      "promptId": "ab85067d-6afa-4e3c-8f33-f0749958c37d",
      "name": "Copies and hops",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "57d4f5ab-f211-4bdd-b93b-1c28b5eb5794",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "0736597a-fa97-4c69-8d8d-1f5a160f9513",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ff6ed2d2-bf79-4a10-b818-0d3e7f35a3b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "flows",
        "copies",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:31.000Z"
    },
    {
      "id": "bda480bf-55f0-428e-98c2-0c8c1144000c",
      "promptId": "d5dac337-452d-432b-86f8-672a3de2f5d6",
      "name": "Entity lifecycle",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "57d4f5ab-f211-4bdd-b93b-1c28b5eb5794",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "8cbf4f4d-b851-4036-a349-c242685fe420",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ed2bde2c-0b3a-4b6b-9cc5-77964cddc438",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "8dd18e9e-98fc-4d94-90f2-51d259362a64",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "47faa8b5-bd0f-44c8-928c-6d58feb306ac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "diagram",
        "lifecycle",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:32.000Z"
    },
    {
      "id": "a7ffd1b2-94e8-43eb-98d0-ea6158a2d464",
      "promptId": "6dff0ee7-4753-445a-b4b1-6775e8eb99b3",
      "name": "Flow narrative for leaders",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "790d28f8-97cd-46a0-9758-2f882b110eb3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "57d4f5ab-f211-4bdd-b93b-1c28b5eb5794",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "9e27aa2e-7aaf-4702-800e-211a7e20792c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "36bca6e6-dfe9-4691-ade6-18ca19df9293",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "29a5abd3-3811-49aa-be6e-1fb2078f1605",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "flows",
        "communication",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:33.000Z"
    },
    {
      "id": "8f73d49f-b95e-4eab-99b5-48841a5ba488",
      "promptId": "a5344232-03f2-4620-a056-4ae498008230",
      "name": "Review a diagram",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e5fba729-cc07-42c8-986d-163edb424ba4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "61bac58f-3554-4a3e-b986-ba5d2cdf1aa2",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e8d7db8f-6b09-42d1-9d46-ba13b3463555",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "312c7d23-1359-43a3-87fe-7bff03f59efe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "47faa8b5-bd0f-44c8-928c-6d58feb306ac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "diagram",
        "review",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:34.000Z"
    },
    {
      "id": "12e8f5de-d4fe-4374-a4fb-e4a5af7b4b05",
      "promptId": "bcd96658-2f2b-42cf-8803-e434d8ce9c7b",
      "name": "Classify the entities",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "17db55c2-3020-419e-ba30-d3ceec263f00",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "46e2047f-d0a1-4c62-b6c2-e140f53005e8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "247c0418-bd3d-415b-a77c-61716537dcea",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ebd01e9a-7ad1-4fc9-b2ef-86ab45d4b5de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1fa05c97-cfbc-4cb9-9763-832207c9d2f3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "classification",
        "entities",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:35.000Z"
    },
    {
      "id": "eec7a01d-f00b-43b7-8493-5bce2a728e19",
      "promptId": "6d1322d5-1ab0-4705-9188-c115d24c05a6",
      "name": "Data security diagram",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "17db55c2-3020-419e-ba30-d3ceec263f00",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "46e2047f-d0a1-4c62-b6c2-e140f53005e8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "85be031a-4de2-4428-b414-7d62b9e737e8",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "083f4a5e-82f0-4d02-bc84-45d7c2db2545",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "49b29bb2-bba9-4c1a-9b23-cbc8a1245e90",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fb3a2a91-30e3-4466-8163-7300f764bf30",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "diagram",
        "security",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:36.000Z"
    },
    {
      "id": "1a5c6a62-7f22-4b21-9ee9-a9a2e2bfe93a",
      "promptId": "47fd4cc3-ef50-4d12-969d-f54b88dcc48b",
      "name": "Access patterns and security requirements",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "17db55c2-3020-419e-ba30-d3ceec263f00",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "85be031a-4de2-4428-b414-7d62b9e737e8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5788603e-7b30-44fb-85e5-927a5f5b3bd8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "891ac26b-e454-4634-b7a7-9b9230b8e9e3",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fb3a2a91-30e3-4466-8163-7300f764bf30",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "security",
        "requirements",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:37.000Z"
    },
    {
      "id": "268acdbd-0df8-4e04-bbb4-af2b4a5e88dc",
      "promptId": "309d7851-b885-479d-9b81-00301b9692a5",
      "name": "Classification standard and gaps",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "17db55c2-3020-419e-ba30-d3ceec263f00",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "46e2047f-d0a1-4c62-b6c2-e140f53005e8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "07f2e51e-687e-49c8-ace0-bb6685cff4e4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7751e727-5c03-4abb-9ba3-74cc61893e35",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "8279b9b7-dd86-476f-b75a-a56a6651f1a4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "1fa05c97-cfbc-4cb9-9763-832207c9d2f3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "classification",
        "standard",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:38.000Z"
    },
    {
      "id": "c61ca7d3-838e-42b3-a81a-f97ad04d1074",
      "promptId": "dfabd198-53fa-4357-9564-38ea9e0f658c",
      "name": "Personal data inventory",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "2ddc91bf-3633-49a8-b183-9955d55b03ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ad0e847c-e523-4bfb-8b6d-6aee46a5947a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "ad1cfe2d-9f19-4291-9084-3bd68d858eda",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b29b60fd-57c8-4eab-8633-4af7ee812a63",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3d97eede-ed81-4e36-90f9-821389ee1a0f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "privacy",
        "inventory",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:39.000Z"
    },
    {
      "id": "168e9d8d-c375-4d11-8069-74c1d291e5b8",
      "promptId": "a9cfdfa1-a0a4-49bc-a55e-74be9777979d",
      "name": "Privacy design review",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "2ddc91bf-3633-49a8-b183-9955d55b03ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ad0e847c-e523-4bfb-8b6d-6aee46a5947a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "761a93aa-539b-4b65-a2dd-435b9f3b45ac",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "312c7d23-1359-43a3-87fe-7bff03f59efe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fb3a2a91-30e3-4466-8163-7300f764bf30",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "privacy",
        "review",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:40.000Z"
    },
    {
      "id": "f248f212-c7ab-447b-a93a-77c46f34877d",
      "promptId": "b4002e08-dd48-4ea7-a651-a17fcf6ead1a",
      "name": "Privacy assessment inputs and questions for legal",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "2ddc91bf-3633-49a8-b183-9955d55b03ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ad0e847c-e523-4bfb-8b6d-6aee46a5947a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "53664898-56ea-48d6-ba0f-c5ea9080abe9",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "5a301ca8-1b3f-4f25-9333-5593475ed638",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "24ba819e-62e3-4a0f-95a1-ca214744990d",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e09b6e29-0691-4d1a-bcc0-a99be4c9f1fc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "privacy",
        "assessment",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:41.000Z"
    },
    {
      "id": "d175dedd-2f8f-4ba4-a7b4-9a09092192f8",
      "promptId": "668305ba-a233-4409-8184-500f29ee3e2e",
      "name": "Cross-border map and rights support",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "2ddc91bf-3633-49a8-b183-9955d55b03ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ad0e847c-e523-4bfb-8b6d-6aee46a5947a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "53664898-56ea-48d6-ba0f-c5ea9080abe9",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "91ed2950-31b8-49ca-947e-2900ab9b9e74",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9df498aa-2dd7-4391-bf09-cacd691dd932",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e09b6e29-0691-4d1a-bcc0-a99be4c9f1fc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "privacy",
        "transfers",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:42.000Z"
    },
    {
      "id": "af2cce5e-f13a-4d3c-b2d0-fd80c2a73994",
      "promptId": "a327876b-3e25-40c8-b950-28dd93e4cb58",
      "name": "Target data architecture",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "8810212d-e373-4b59-857a-0bdf05f04273",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "1acd16c8-b347-4bb9-8259-9e1c00c9cd33",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "target",
        "document",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:43.000Z"
    },
    {
      "id": "82afc243-f849-45be-a89a-855d8c3bafec",
      "promptId": "6450cd00-500d-41b9-b629-47c5f271ac14",
      "name": "Building blocks and data requirements",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "8810212d-e373-4b59-857a-0bdf05f04273",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "025d6ade-3f08-4cf2-98be-427d71c1eb8a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "be616ff2-260f-4645-9e79-292f9cad4f8a",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f63cd43d-9f16-487a-9b3f-3eaf9cc4ae27",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "target",
        "building blocks",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:44.000Z"
    },
    {
      "id": "0bc48023-3302-4de8-996a-b6e24e05f442",
      "promptId": "dafb147c-a5bf-427b-b5e5-753978d2747d",
      "name": "Gap analysis and impact",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "2e580993-c1a9-4626-927b-b46e8ceb70d7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "98ca2e89-3ee8-4238-9551-48f983160a40",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "560e42d3-b5fb-4fe0-abd1-fe6c28ed9354",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "b998557e-e44e-48c7-bd38-f25c893327fd",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b32e7f56-fa34-4b68-a213-637d81104cc5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "gap analysis",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:45.000Z"
    },
    {
      "id": "586d53b5-123f-474f-9609-0fb8cbf9d07e",
      "promptId": "e57f6585-f21b-4066-a6c0-37cb47531695",
      "name": "Roadmap work packages",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "2e580993-c1a9-4626-927b-b46e8ceb70d7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "99f49513-c697-4938-be71-ae5e38a0ee87",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "aea0a883-3e8a-4908-b9a6-86f2fa430267",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "527d546d-672e-49ce-8270-88aa534f54b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "roadmap",
        "work packages",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:46.000Z"
    },
    {
      "id": "e623bd69-f70a-49c8-bf47-06faca4059e8",
      "promptId": "db2ab461-89dc-492f-bd34-b6da3b4d78c3",
      "name": "Stakeholder review of the data architecture",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "1caecd16-d362-4de8-8079-c939705ab557",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "2e580993-c1a9-4626-927b-b46e8ceb70d7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "fe051bf8-eadc-4444-8a9a-3ac5b9c94d9a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f917c34a-19fd-4064-976f-7b3653115fb0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "527d546d-672e-49ce-8270-88aa534f54b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "review",
        "stakeholders",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:47.000Z"
    },
    {
      "id": "4a1752d3-d0d9-4565-a978-a5546124119c",
      "promptId": "feb5da12-d440-4a3d-b144-8cbd2e7ec98a",
      "name": "Target brief for leaders",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "790d28f8-97cd-46a0-9758-2f882b110eb3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "2e580993-c1a9-4626-927b-b46e8ceb70d7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "347ec833-1ce1-4214-be3f-bc26d140b993",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "36bca6e6-dfe9-4691-ade6-18ca19df9293",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4285bdda-45e6-48cc-8a26-032430d2e57a",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "target",
        "communication",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:48.000Z"
    },
    {
      "id": "f376c93d-e3fb-4e10-aac3-40bd9d2a8045",
      "promptId": "70f465c7-f953-4a52-aabf-ecffb06a89b3",
      "name": "Master data assessment",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa5b5ce5-317c-4f02-8c5d-96ecb733b3d1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f89eeae0-b26f-4dcb-9e3c-72247df3d29f",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "a0611c47-bbed-4c7f-ab27-c6a6a7e95584",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "17ee1e60-67ae-45c7-b5ae-1523a4302de4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "892d6e07-32e2-4ef8-b2e6-1fd91515e8de",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "master data",
        "assessment",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:49.000Z"
    },
    {
      "id": "cae3fe93-0577-4294-b371-8d24c4f20d9b",
      "promptId": "6a7648af-f1cf-45ba-986a-78d2d63be7b9",
      "name": "MDM style decision and case",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa5b5ce5-317c-4f02-8c5d-96ecb733b3d1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f89eeae0-b26f-4dcb-9e3c-72247df3d29f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "54788c00-0020-420a-9537-f666a9546d58",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3cac05d5-3023-44ec-822c-9dfa0061fc16",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "c10ab4f3-c4d3-4727-bba5-5de0d1384bbd",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "master data",
        "decision",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:50.000Z"
    },
    {
      "id": "5db0fb6c-dc84-4d69-86f5-1000ebb482de",
      "promptId": "bca5ed30-b2fd-40b6-862b-d5ade2cd609b",
      "name": "Golden record and hierarchies",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa5b5ce5-317c-4f02-8c5d-96ecb733b3d1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f89eeae0-b26f-4dcb-9e3c-72247df3d29f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "aaaddeec-4c81-4c34-9c8d-b424a6a06794",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b29e83dd-c5f7-4954-9d77-78b3536db6ef",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "02f32eb3-df99-409c-bb8e-e6498a272748",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "master data",
        "golden record",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:51.000Z"
    },
    {
      "id": "5c48ced2-2799-4624-a316-dfdc6cfaeae5",
      "promptId": "05a39604-0a6d-46f2-ba24-6cfbc6656ee2",
      "name": "Reference data governance",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa5b5ce5-317c-4f02-8c5d-96ecb733b3d1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f89eeae0-b26f-4dcb-9e3c-72247df3d29f",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "2d012503-aa64-4530-a36a-ed0fe9f22cc5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "d81bf753-c72c-4451-aa39-5911db9347a9",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "reference data",
        "governance",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:52.000Z"
    },
    {
      "id": "48123436-14ba-4571-96e1-3c9c254a3ccc",
      "promptId": "3b4e4e0d-f5e8-46a5-9992-b436d8048202",
      "name": "Ownership model and RACI",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "4cce2fce-5512-4079-be72-2d4b1344ed7c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "cba513c9-dc10-4578-8b12-177de78056ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "55c20ca5-36fa-4e31-8407-019514924951",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4089a217-b070-4d94-8d1b-b00c153d4f72",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "22ab5c73-66b7-456f-982c-510d4fe0d7a8",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "ownership",
        "raci",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:53.000Z"
    },
    {
      "id": "72bf988f-85b9-4441-ad7c-564ac812c509",
      "promptId": "0232668e-08ad-42ec-8770-c3c61628ce3a",
      "name": "Data steward role",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "4cce2fce-5512-4079-be72-2d4b1344ed7c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "cba513c9-dc10-4578-8b12-177de78056ba",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "2a983c59-2c35-4b66-ac10-9b434f506344",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "d73047d1-ee2d-461b-b2df-bc1eb32cd9c7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3894918a-a3e0-4ea3-b834-a542a3f717ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "stewardship",
        "role",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:54.000Z"
    },
    {
      "id": "6e13809d-7adf-4ef4-a8e3-bbc26eb7435b",
      "promptId": "d477c70b-4314-4d9e-b5f8-f66e3187df87",
      "name": "Council charter and policy hierarchy",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "4cce2fce-5512-4079-be72-2d4b1344ed7c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "cba513c9-dc10-4578-8b12-177de78056ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7bb7272e-4c54-418b-bed3-2b0c85e9c49c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "63b7a5b2-05ca-40b3-a8fb-5bf94c005c32",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "governance",
        "charter",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:55.000Z"
    },
    {
      "id": "4d1eccd7-54e7-4050-a55c-03092967954c",
      "promptId": "b92a5155-058e-4067-b7c9-812151f166bd",
      "name": "Governance operating model paper",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "4cce2fce-5512-4079-be72-2d4b1344ed7c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "cba513c9-dc10-4578-8b12-177de78056ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e42aaa05-320b-4707-8a53-f21233ab0924",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "e2bb791c-3e18-4e40-a9d1-7acff353838d",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "3894918a-a3e0-4ea3-b834-a542a3f717ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "governance",
        "operating model",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:56.000Z"
    },
    {
      "id": "b5ac948c-5165-4a93-86a2-cfc273daa263",
      "promptId": "0fb4bc38-364b-45de-8fc0-42d835f92b30",
      "name": "Critical elements and quality rules",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa256d33-57ad-4df3-bc98-446bc66ac0cb",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "17c66ebf-d307-452b-933c-4f3f0ddf7921",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f78fd48b-a0af-4e7d-af88-2a5e786d4423",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "aa9deb55-2045-43e2-af83-82914d7d2768",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "d530c9de-423d-430a-9388-5f114863b155",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "59502c57-732a-49d5-85c5-08da80e44444",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "data quality",
        "rules",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:57.000Z"
    },
    {
      "id": "2bf81af3-b8bf-48ae-bd3f-4dfcfcce409e",
      "promptId": "8500b55a-b545-42ba-92f4-30a2e9012a49",
      "name": "Thresholds and scorecard",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa256d33-57ad-4df3-bc98-446bc66ac0cb",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "17c66ebf-d307-452b-933c-4f3f0ddf7921",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9725a903-8c50-4525-9401-80af5456a203",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "dc451da3-5c22-4940-a7c8-ac5d82106b94",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "17ee1e60-67ae-45c7-b5ae-1523a4302de4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "59502c57-732a-49d5-85c5-08da80e44444",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "data quality",
        "scorecard",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:58.000Z"
    },
    {
      "id": "3136ed36-b4fa-4030-a22a-8158405c006c",
      "promptId": "81b1f032-1230-4bc3-b73a-a76985bc2765",
      "name": "Root cause and remediation",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa256d33-57ad-4df3-bc98-446bc66ac0cb",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "17c66ebf-d307-452b-933c-4f3f0ddf7921",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "648c8c8b-b24f-45c0-9d33-ece3f9fc7002",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b1cc71e2-b4e1-4c21-8d19-1821167fc76b",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "ff6ed2d2-bf79-4a10-b818-0d3e7f35a3b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9a146d4b-ac42-4af8-a3ca-d449ca23cc22",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "data quality",
        "root cause",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:04:59.000Z"
    },
    {
      "id": "ad7b8c83-390c-40e0-8c24-5879dc74f173",
      "promptId": "ce12e421-18a4-4677-a6b5-f9ead7a4bad5",
      "name": "Quality requirements for the specification",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "fa256d33-57ad-4df3-bc98-446bc66ac0cb",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "17c66ebf-d307-452b-933c-4f3f0ddf7921",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7299de5e-7ba7-4600-b3fd-fc3104d53ff1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9a146d4b-ac42-4af8-a3ca-d449ca23cc22",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "data quality",
        "requirements",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:00.000Z"
    },
    {
      "id": "e5f5bf7d-23d5-4932-bb5d-c0be5cdd7f21",
      "promptId": "81efb480-e246-441d-bb92-575427f371c0",
      "name": "Lineage scope and a critical report's lineage",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "6f508b76-7f2c-40f6-acec-8c583d9ad6e6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac25a2db-3a0d-4467-93e8-cedf6cab82c0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "0017840f-988f-4560-8871-09ede87d9cbd",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b405485e-62f4-462f-b74f-1b154839501c",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e616a106-d7d9-499c-988f-eebfc7f9bd0e",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "45c4fde2-411c-42d6-8ce7-84895051d08f",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "lineage",
        "report",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:01.000Z"
    },
    {
      "id": "b1cf9f6c-13e5-4229-a59e-b6c9e334beea",
      "promptId": "44551019-fdea-4c3d-99c8-69309fcf7795",
      "name": "Metadata architecture",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "6f508b76-7f2c-40f6-acec-8c583d9ad6e6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac25a2db-3a0d-4467-93e8-cedf6cab82c0",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "9cefd582-c716-49d7-a853-37d7e0db1762",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f63cd43d-9f16-487a-9b3f-3eaf9cc4ae27",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "metadata",
        "architecture",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:02.000Z"
    },
    {
      "id": "c4f00ea1-85e8-4f6f-9d1e-20ebd7f36934",
      "promptId": "109c85d2-2783-4972-887e-98e95299c049",
      "name": "Metadata standard",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "6f508b76-7f2c-40f6-acec-8c583d9ad6e6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5cf34304-5325-4e64-b3c6-df252bab83a6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "d81bf753-c72c-4451-aa39-5911db9347a9",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "e934dc9c-a5e7-418c-a681-1e45f86e8d48",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "metadata",
        "standard",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:03.000Z"
    },
    {
      "id": "f81fa925-b88d-43ed-bbaa-21c910ac226b",
      "promptId": "81ebbde0-fe23-4428-bfc0-50486d4194db",
      "name": "Lineage gaps and impact analysis",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "6f508b76-7f2c-40f6-acec-8c583d9ad6e6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac25a2db-3a0d-4467-93e8-cedf6cab82c0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "48b64607-8873-460a-bfd1-949c8abe602c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "57767605-4e7f-4d80-a75c-8862f21c3a95",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "ff6ed2d2-bf79-4a10-b818-0d3e7f35a3b7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "e616a106-d7d9-499c-988f-eebfc7f9bd0e",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "lineage",
        "impact",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:04.000Z"
    },
    {
      "id": "9400240e-a1fb-41a6-aa79-cd1633a948db",
      "promptId": "8e4bcaa7-5e08-4605-aa92-1799ea7a8e6f",
      "name": "Platform options",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "c479b2ab-8667-4f8e-a438-9fdb045cb8ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5619954-c2e4-4418-a511-e630bc755dd7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "560ad415-0fcb-4134-a28c-ebc2cca59b15",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ea6dcdf9-1672-4221-884a-1263c473ab87",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "platform",
        "options",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:05.000Z"
    },
    {
      "id": "d621213d-9219-4773-b28e-0f55dd100535",
      "promptId": "b161f9bc-e249-4a31-9d8d-175a8e04ce07",
      "name": "Target platform state",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "c479b2ab-8667-4f8e-a438-9fdb045cb8ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5619954-c2e4-4418-a511-e630bc755dd7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9d691cd2-af2f-4051-9c0f-6e6ec5c7b7a0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f1445ae7-d314-4bd2-be24-4b38018fd28d",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f63cd43d-9f16-487a-9b3f-3eaf9cc4ae27",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "platform",
        "target",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:06.000Z"
    },
    {
      "id": "dd83716d-e8f3-452b-a8bf-55e35a6b1ff4",
      "promptId": "9c42d8d3-117d-46de-82a4-a3a186811713",
      "name": "Data product",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "c479b2ab-8667-4f8e-a438-9fdb045cb8ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5619954-c2e4-4418-a511-e630bc755dd7",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "24af1ca3-e8d7-468b-baca-91c68f010a62",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "799c8020-89ea-4700-a7ad-cfea133e88f5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "7d3c9eb8-f61b-4e69-aa80-41ec485483a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "platform",
        "data product",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:07.000Z"
    },
    {
      "id": "1720373e-d64b-416d-9b96-57e60e082518",
      "promptId": "5196a54f-7ecf-4c6a-8c07-1705098fcc45",
      "name": "Team split and transition stages",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "c479b2ab-8667-4f8e-a438-9fdb045cb8ae",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b19036ef-1eec-46ad-bba7-5c8e37740e8c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c5619954-c2e4-4418-a511-e630bc755dd7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "964b0905-a561-4666-84e2-f9ea17212ec0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c9682d8b-3b69-4a33-9c41-a4c27723b6c7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "4018d027-4222-4493-86d9-f276175dc2bc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "platform",
        "transition",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:08.000Z"
    },
    {
      "id": "4f482aa6-5eb3-44bc-981b-446762ddaca7",
      "promptId": "f57db411-c53d-4d40-9f5f-b632fb86b606",
      "name": "Integration pattern per flow",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "305f167e-5b4f-46e6-b032-ef078e7d7953",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1181babd-934d-488c-b845-ffe6896622ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "84ea229d-5190-4baf-9592-5fc06cd58ad1",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "019d2011-a61b-4e18-bd78-f96fcfda6260",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "integration",
        "patterns",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:09.000Z"
    },
    {
      "id": "ec2e2b2d-fc89-4673-b35b-eae6385fbb66",
      "promptId": "c12c625e-ce06-45e2-bbf0-71e11d91aa1c",
      "name": "Canonical model decision",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "305f167e-5b4f-46e6-b032-ef078e7d7953",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1181babd-934d-488c-b845-ffe6896622ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "24153937-bdc1-4568-8368-0aa8650e2a36",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "c10ab4f3-c4d3-4727-bba5-5de0d1384bbd",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "integration",
        "canonical",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:10.000Z"
    },
    {
      "id": "b9a22a34-a85d-43bc-95dc-601e39a2c2b9",
      "promptId": "574fe594-3520-4a91-90bd-ba3edfb8ac99",
      "name": "Exchange standard and data contracts",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "305f167e-5b4f-46e6-b032-ef078e7d7953",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "f972b99c-43c9-4ebd-a133-fb72bdb96e14",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1181babd-934d-488c-b845-ffe6896622ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "02676f1d-d4e1-4ca3-9ad0-b3ced6025d07",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "97713055-6744-4383-9f7b-a42a67884350",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "7944c208-84b7-4872-9af3-e0af935e17b4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "integration",
        "contracts",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:11.000Z"
    },
    {
      "id": "b3cbe448-d5c7-427f-b55d-082ded0d7216",
      "promptId": "8c8752c8-f7c3-467c-a162-70f63c218029",
      "name": "Integration principles and gaps",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "305f167e-5b4f-46e6-b032-ef078e7d7953",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "6509fca7-d4ff-4ba8-a0d6-46a87cd34ec2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1181babd-934d-488c-b845-ffe6896622ba",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "59653fe0-fd98-441b-8989-1fcc32f30e01",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "b49977a4-19e8-48b7-a49e-e0b1f6599f89",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "b8cc7f8a-5dcf-4bc2-b436-5eaf9a8bcd09",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "integration",
        "principles",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:12.000Z"
    },
    {
      "id": "fad5568f-abe2-46b4-ba0e-be3bda7a3801",
      "promptId": "b1c42c1e-0c65-4180-8d63-f4a19b2d5c0f",
      "name": "Migration strategy and diagram",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "81d973c7-5052-4287-b834-5d403632295c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "279f882b-b953-44da-b309-1ad64b392cf4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a15e84e8-3b7a-49e0-be7d-b86be6f04652",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "24cff9e0-4bda-4113-a1b2-b8b8d38782b3",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "47faa8b5-bd0f-44c8-928c-6d58feb306ac",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "migration",
        "strategy",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:13.000Z"
    },
    {
      "id": "f74efc9e-b661-4c1b-925d-636fba65f99e",
      "promptId": "deee0e18-7376-4095-95df-12082190bba4",
      "name": "Mapping and cleansing decisions",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "81d973c7-5052-4287-b834-5d403632295c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "279f882b-b953-44da-b309-1ad64b392cf4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "0023ede6-87a7-4456-b54a-29545928059e",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ef961720-478c-4d1c-936f-03f973eb926d",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "bc40d393-3b7e-44da-bb73-a5780a711c9b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "197493c3-6382-49fe-9142-a62cefba6ef3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "migration",
        "mapping",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:14.000Z"
    },
    {
      "id": "4a4d248d-3dc6-4e1d-b4e5-45e22d57fe4d",
      "promptId": "7fd71117-8dff-4422-b476-374dcff17775",
      "name": "Reconciliation and cutover",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "81d973c7-5052-4287-b834-5d403632295c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5faa07b0-0689-4d3d-99d2-148d7e0adedf",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "279f882b-b953-44da-b309-1ad64b392cf4",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "27cefa46-0a31-4d2f-83dc-546213f721fe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "197493c3-6382-49fe-9142-a62cefba6ef3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "migration",
        "cutover",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:15.000Z"
    },
    {
      "id": "64323b69-7b83-426d-8c3d-86a428c639ce",
      "promptId": "e1ab9aea-3243-4c37-b7a4-deb4daeecb47",
      "name": "Migration risks and legacy archive",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "81d973c7-5052-4287-b834-5d403632295c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "279f882b-b953-44da-b309-1ad64b392cf4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "53664898-56ea-48d6-ba0f-c5ea9080abe9",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "11302507-82fa-4925-ab17-31335cd82164",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "7afa57f5-01d2-467a-b20a-7c77718ef8d7",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e09b6e29-0691-4d1a-bcc0-a99be4c9f1fc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "migration",
        "risks",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:16.000Z"
    },
    {
      "id": "d772017c-6905-44fc-a701-f140d2abd60f",
      "promptId": "aa97b6f7-cd18-4486-8aa8-f670fd51d047",
      "name": "Retention mapping",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e10c38ac-7e60-447a-9279-311cacf40f2b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5d7f5964-426c-4014-b338-cd536ad8e518",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e185e9bf-70bb-4a65-95f1-ff3ae9a239e6",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "bc40d393-3b7e-44da-bb73-a5780a711c9b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "21677300-9111-4905-aa88-e4212261edd3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "retention",
        "mapping",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:17.000Z"
    },
    {
      "id": "c9aa9023-db20-440b-bcee-185e505f4167",
      "promptId": "1e4207ec-164a-497d-9364-aee1ebdebd4f",
      "name": "Archive and disposal design",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e10c38ac-7e60-447a-9279-311cacf40f2b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5d7f5964-426c-4014-b338-cd536ad8e518",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "82381c34-cd59-4419-a957-1ffac8698d49",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "4ce10e63-2f8c-479c-bb1a-635b21aa5404",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "643d2bf1-a126-4462-b6c7-84aae78b38f2",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "21677300-9111-4905-aa88-e4212261edd3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "retention",
        "archive",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:18.000Z"
    },
    {
      "id": "11c44d5b-b8c3-4779-8c64-d75900592c72",
      "promptId": "fa986592-b906-4f3b-a328-1c7c2e5881fa",
      "name": "Legal hold and retention gaps",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e10c38ac-7e60-447a-9279-311cacf40f2b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5d7f5964-426c-4014-b338-cd536ad8e518",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "53664898-56ea-48d6-ba0f-c5ea9080abe9",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "942334f0-db30-4b6c-b1ac-5b2921832752",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "75047e6b-a3ee-4e88-902f-db034b63ce43",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "e09b6e29-0691-4d1a-bcc0-a99be4c9f1fc",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "retention",
        "legal hold",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:19.000Z"
    },
    {
      "id": "0842361a-7ba4-4110-9707-30aba4c8c968",
      "promptId": "9c402237-6806-4ea3-a1fb-2f52118aad2c",
      "name": "Note to records management and legal",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e10c38ac-7e60-447a-9279-311cacf40f2b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "5d7f5964-426c-4014-b338-cd536ad8e518",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "176f0f86-b0ff-4c1d-920c-e791d3bd82a0",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "dd4fb49e-f2bc-463e-a982-a27a5244e7fe",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "21677300-9111-4905-aa88-e4212261edd3",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "retention",
        "conversation",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:20.000Z"
    },
    {
      "id": "e95af9d6-ae2c-4a91-bfee-59d7d940c4cf",
      "promptId": "318c5e8d-4b41-4df1-b959-b63cd473d28c",
      "name": "Due diligence request list",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e8d9ad06-16a9-4aac-9496-b31ef7bb0666",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ab8f3c80-ce9c-4f08-a66c-c2718b0a7129",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac127395-6cd7-458d-9a2f-38f8ccb79118",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "523ad2c1-a2b3-4155-b3d7-42cca743ef5b",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "1ccabe20-9c0e-4e88-9d7d-24b5dfffde02",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "45c4fde2-411c-42d6-8ce7-84895051d08f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "due diligence",
        "requests",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:21.000Z"
    },
    {
      "id": "3b0b0db5-8ac4-4bcb-9efb-c062cc0d7ba4",
      "promptId": "68e217a1-d187-499b-87b3-5ad6e5ec57bc",
      "name": "Landscape assessment and data risks",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e8d9ad06-16a9-4aac-9496-b31ef7bb0666",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac127395-6cd7-458d-9a2f-38f8ccb79118",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ea575baa-0557-473d-980b-38dcd2ac214d",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "8c4aa5a3-9e64-4343-bf98-25494c90cea9",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "b1880c77-a840-42b4-9342-b22e631500d4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fbc6b078-41f4-4bb6-a3b7-50025dced61c",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "due diligence",
        "assessment",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:22.000Z"
    },
    {
      "id": "0eef5914-318b-4f2c-abdb-eb3937fb9082",
      "promptId": "c5d33817-4649-44a4-a5b5-972f43cf7d8d",
      "name": "Integration options and carve-out",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e8d9ad06-16a9-4aac-9496-b31ef7bb0666",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac127395-6cd7-458d-9a2f-38f8ccb79118",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "9ec30e2a-84ff-4d7a-af8a-1484273495c5",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "648f601d-5b67-40a8-a34f-9380cbc0f386",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "ea6dcdf9-1672-4221-884a-1263c473ab87",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "a1a301c3-2160-4c61-b9cc-001723fb25a4",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "due diligence",
        "integration options",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:23.000Z"
    },
    {
      "id": "eeb5d332-d000-42e9-ad6e-538ae05f3f45",
      "promptId": "bdd483eb-e36e-4b31-84d5-e83cb0bfe33e",
      "name": "Day one and the integration roadmap",
      "promptType": "User Prompt",
      "saveMode": "dynamic",
      "blockRefs": [
        {
          "blockId": "e8d9ad06-16a9-4aac-9496-b31ef7bb0666",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "ac127395-6cd7-458d-9a2f-38f8ccb79118",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "fff4773d-39d2-4426-bef7-d2d4781fc169",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "bc5aa0e8-74ee-4a90-ae3c-a775efd7a8fc",
          "includeName": false,
          "includeType": false
        },
        {
          "blockId": "1ccabe20-9c0e-4e88-9d7d-24b5dfffde02",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "45c4fde2-411c-42d6-8ce7-84895051d08f",
          "includeName": false,
          "includeType": true
        },
        {
          "blockId": "960ec668-d50c-49d6-a839-923125a91e48",
          "includeName": false,
          "includeType": false
        }
      ],
      "tags": [
        "due diligence",
        "roadmap",
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:24.000Z"
    },
    {
      "id": "3fcc53e6-d2b1-455b-b576-f73d1da9550b",
      "promptId": "183ff9ef-03e9-41a7-ad36-896a8db6a728",
      "name": "Run Phase C, Data Architecture",
      "promptType": "Prompt Set",
      "saveMode": "dynamic",
      "blockRefs": [],
      "promptIds": [
        "b9ad93ce-c0b4-4563-8f6d-e84ef4cf530e",
        "21634bad-b916-4b36-aa78-4672322e9eb3",
        "1b4526b3-61a3-46bf-b9c4-a2e8356b13dc",
        "96e18d0e-0452-413b-8ab5-d80cbd860da3",
        "a327876b-3e25-40c8-b950-28dd93e4cb58",
        "dafb147c-a5bf-427b-b5e5-753978d2747d",
        "e57f6585-f21b-4066-a6c0-37cb47531695",
        "db2ab461-89dc-492f-bd34-b6da3b4d78c3"
      ],
      "tags": [
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:25.000Z"
    },
    {
      "id": "ea09a1c7-60be-43ea-8a0a-d8fa57a34c31",
      "promptId": "b80521d2-1505-4621-ad6a-a0dc5738dd69",
      "name": "Model a domain from conceptual to physical",
      "promptType": "Prompt Set",
      "saveMode": "dynamic",
      "blockRefs": [],
      "promptIds": [
        "cae5b8cb-ae9d-4583-ac63-ffe292337651",
        "a81c66da-0e90-4eef-8b6e-a0d863ea9918",
        "3530613c-c2ff-43f3-9216-edf85df8517a",
        "f6655784-c7cf-42a0-a1cc-58ed024db1be",
        "44e90494-df84-4b19-a200-ea7d47983b66"
      ],
      "tags": [
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:26.000Z"
    },
    {
      "id": "77c45c17-fd4b-4fff-8221-b90c8de8e900",
      "promptId": "1a6b5b63-2c65-4131-a52f-2ae5fb926d72",
      "name": "Design an initiative for privacy",
      "promptType": "Prompt Set",
      "saveMode": "dynamic",
      "blockRefs": [],
      "promptIds": [
        "dfabd198-53fa-4357-9564-38ea9e0f658c",
        "a9cfdfa1-a0a4-49bc-a55e-74be9777979d",
        "b4002e08-dd48-4ea7-a651-a17fcf6ead1a",
        "668305ba-a233-4409-8184-500f29ee3e2e"
      ],
      "tags": [
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:27.000Z"
    },
    {
      "id": "1bdb07ff-55f0-4656-bfe1-0a015e9e2014",
      "promptId": "8b3bc0c5-522d-48a5-94a7-f5ea75c674ec",
      "name": "Master an entity",
      "promptType": "Prompt Set",
      "saveMode": "dynamic",
      "blockRefs": [],
      "promptIds": [
        "70f465c7-f953-4a52-aabf-ecffb06a89b3",
        "6a7648af-f1cf-45ba-986a-78d2d63be7b9",
        "bca5ed30-b2fd-40b6-862b-d5ade2cd609b"
      ],
      "tags": [
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:28.000Z"
    },
    {
      "id": "7bc9228d-2e21-4d3b-9fc9-02923ad9c3c6",
      "promptId": "1b0ce014-dc80-4968-a90d-f26ef326ff08",
      "name": "Plan a data migration",
      "promptType": "Prompt Set",
      "saveMode": "dynamic",
      "blockRefs": [],
      "promptIds": [
        "b1c42c1e-0c65-4180-8d63-f4a19b2d5c0f",
        "deee0e18-7376-4095-95df-12082190bba4",
        "7fd71117-8dff-4422-b476-374dcff17775",
        "e1ab9aea-3243-4c37-b7a4-deb4daeecb47"
      ],
      "tags": [
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:29.000Z"
    },
    {
      "id": "c51f42d3-d923-4ab2-b6ac-bb7d13dac3d0",
      "promptId": "55535f64-9120-4523-8372-c31507be9396",
      "name": "Data due diligence and integration for a deal",
      "promptType": "Prompt Set",
      "saveMode": "dynamic",
      "blockRefs": [],
      "promptIds": [
        "318c5e8d-4b41-4df1-b959-b63cd473d28c",
        "68e217a1-d187-499b-87b3-5ad6e5ec57bc",
        "c5d33817-4649-44a4-a5b5-972f43cf7d8d",
        "bdd483eb-e36e-4b31-84d5-e83cb0bfe33e"
      ],
      "tags": [
        "Data architecture pack"
      ],
      "embeddedBlocks": [],
      "aiAssist": null,
      "createdAt": "2026-10-05T09:05:30.000Z"
    }
  ],
  "variables": [
    {
      "id": "d2358414-f60e-4266-af5e-275ee002d6fb",
      "name": "company name",
      "value": "Example Company",
      "description": "The business's name.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:31.000Z",
      "updatedAt": "2026-10-05T09:05:31.000Z"
    },
    {
      "id": "d51ac328-03f1-4f51-8d45-6a4f41405714",
      "name": "business model",
      "value": "Sells equipment and service contracts to business customers through direct sales and a network of dealers",
      "description": "What the business does and how it earns money.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:32.000Z",
      "updatedAt": "2026-10-05T09:05:32.000Z"
    },
    {
      "id": "4d2ef811-f8bb-44c9-97c5-012a5436a242",
      "name": "data domains",
      "value": "Customer (owned by Sales), Product (owned by Product Management), Order and Contract (owned by Operations), Finance (owned by the Controller), Employee (owned by HR), Supplier (owned by Procurement)",
      "description": "The data domains the enterprise manages, with the business owner of each where one is named.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:33.000Z",
      "updatedAt": "2026-10-05T09:05:33.000Z"
    },
    {
      "id": "b9a5d5f0-ff10-4c5d-8151-399c19076c10",
      "name": "systems of record",
      "value": "Customer in the CRM system; Product in the product catalogue; Order, Contract and Finance in the ERP system; Employee in the HR system; Supplier in the ERP system; dealer data in spreadsheets with no agreed source",
      "description": "The system of record for each main entity today, as the business treats them.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:34.000Z",
      "updatedAt": "2026-10-05T09:05:34.000Z"
    },
    {
      "id": "45984c52-6b43-4544-8ba2-3545258d4db1",
      "name": "regulatory environment",
      "value": "General data protection law in the countries it trades in, financial record keeping rules, and dealer contracts that limit how dealer data is shared",
      "description": "The laws and rules that touch the business's data, as legal has described them.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:35.000Z",
      "updatedAt": "2026-10-05T09:05:35.000Z"
    },
    {
      "id": "d40a0c61-f9aa-4513-9419-67486490af7f",
      "name": "modelling notation",
      "value": "Entity relationship diagrams in crow's foot notation for logical models; UML class diagrams for conceptual models; the repository's own notation for architecture diagrams",
      "description": "The notation the architecture team uses for data models and diagrams.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:36.000Z",
      "updatedAt": "2026-10-05T09:05:36.000Z"
    },
    {
      "id": "bb254a50-e3e0-4431-846a-e57b5d8cfb56",
      "name": "naming standard",
      "value": "Entities are singular business nouns in title case; attributes are noun phrases without abbreviations; components are named for what they hold, not for the system",
      "description": "The naming rules for entities, attributes and components.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:37.000Z",
      "updatedAt": "2026-10-05T09:05:37.000Z"
    },
    {
      "id": "b8f6267b-0f1b-4923-b264-0f7a65adae8d",
      "name": "architecture repository",
      "value": "The shared architecture repository maintained by the architecture team, with the data models, catalogs and matrices in its data architecture section",
      "description": "Where the architecture artefacts are kept and who maintains them.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:38.000Z",
      "updatedAt": "2026-10-05T09:05:38.000Z"
    },
    {
      "id": "81e64ef8-8928-4834-8803-b8bb17df32c1",
      "name": "data principles",
      "value": "Data is a shared asset: enterprise data belongs to the business, not to the system or team that captures it. One definition: each business entity has one agreed definition in the glossary. One system of record: every entity has one named source of truth and other systems subscribe to it. Quality at the source: data is made right where it is created. Protected by design: classification and access are decided before data is collected or copied. Kept by rule: data is retained and disposed of under the retention schedule, not by accident.",
      "description": "The data principles the enterprise has agreed, by name and statement.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:39.000Z",
      "updatedAt": "2026-10-05T09:05:39.000Z"
    },
    {
      "id": "90c4edd2-16c9-45a8-874a-b753bc8bf318",
      "name": "governance body",
      "value": "The Data Governance Council, chaired by the Chief Data Officer, meeting monthly",
      "description": "The body that makes enterprise data decisions.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:40.000Z",
      "updatedAt": "2026-10-05T09:05:40.000Z"
    },
    {
      "id": "dbca0c8c-8af5-4296-aa23-956de88e6408",
      "name": "classification levels",
      "value": "Public, Internal, Confidential, Restricted",
      "description": "The classification levels in use, from least to most sensitive.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:41.000Z",
      "updatedAt": "2026-10-05T09:05:41.000Z"
    },
    {
      "id": "150fc281-a76f-465a-aa63-5bd1fd76370d",
      "name": "analytics platform",
      "value": "A central data warehouse loaded nightly from the ERP and CRM systems, with departmental reports built on it and several spreadsheet extracts beside it",
      "description": "The analytics platform the business uses today.",
      "runtime": false,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:42.000Z",
      "updatedAt": "2026-10-05T09:05:42.000Z"
    },
    {
      "id": "939e2521-ec12-4f0f-84e3-70100ed1e9fa",
      "name": "initiative",
      "value": "Customer platform renewal",
      "description": "The initiative, programme or project the architecture work is for. Asked each time.",
      "runtime": true,
      "hasDefault": true,
      "createdAt": "2026-10-05T09:05:43.000Z",
      "updatedAt": "2026-10-05T09:05:43.000Z"
    },
    {
      "id": "10afa153-08b7-41ab-ade3-c24e534a4fe4",
      "name": "sponsor",
      "value": "The Chief Operating Officer",
      "description": "The sponsor of the architecture work, by role. Asked each time.",
      "runtime": true,
      "hasDefault": true,
      "createdAt": "2026-10-05T09:05:44.000Z",
      "updatedAt": "2026-10-05T09:05:44.000Z"
    },
    {
      "id": "592ede32-ef9c-4d8c-876a-be02e6f526f0",
      "name": "stakeholders and concerns",
      "value": "Head of Sales: one view of each customer; Controller: revenue figures that reconcile; Head of IT: fewer interfaces to maintain; Privacy officer: customer consent carried into every copy",
      "description": "The stakeholders of the work and what each one cares about. Asked each time.",
      "runtime": true,
      "hasDefault": true,
      "createdAt": "2026-10-05T09:05:45.000Z",
      "updatedAt": "2026-10-05T09:05:45.000Z"
    },
    {
      "id": "7b6e6001-a041-42b2-bb94-1f01c58c6936",
      "name": "draft",
      "value": "",
      "description": "The draft principle, section, model, diagram or document to review or revise. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:46.000Z",
      "updatedAt": "2026-10-05T09:05:46.000Z"
    },
    {
      "id": "0b615867-44c6-4c6f-83d2-641e98a49fc7",
      "name": "baseline inventory",
      "value": "",
      "description": "What is known about the data as it is today: systems, the data they hold, interfaces, owners and known problems. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:47.000Z",
      "updatedAt": "2026-10-05T09:05:47.000Z"
    },
    {
      "id": "5b1d2509-2dfe-46fb-a94f-3011ad51f04d",
      "name": "data domain",
      "value": "Customer",
      "description": "The data domain in question. Asked each time.",
      "runtime": true,
      "hasDefault": true,
      "createdAt": "2026-10-05T09:05:48.000Z",
      "updatedAt": "2026-10-05T09:05:48.000Z"
    },
    {
      "id": "acfeac4a-dd2f-4d87-9bbc-de44bf4b2bcf",
      "name": "catalog extract",
      "value": "",
      "description": "The catalog entries, entity list or component descriptions to work from. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:49.000Z",
      "updatedAt": "2026-10-05T09:05:49.000Z"
    },
    {
      "id": "1291201e-8614-49de-9595-f16c3f0257b8",
      "name": "data model",
      "value": "",
      "description": "The data model to work from, or the two models to reconcile: entities, attributes, relationships, keys and notes, as the author describes them. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:50.000Z",
      "updatedAt": "2026-10-05T09:05:50.000Z"
    },
    {
      "id": "ba148316-694d-4885-ab23-8878b9a0bb25",
      "name": "glossary extract",
      "value": "",
      "description": "The glossary terms, candidate definitions and sources to work from. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:51.000Z",
      "updatedAt": "2026-10-05T09:05:51.000Z"
    },
    {
      "id": "56f7e9a2-b76b-4ae9-b2c2-24fc7f9602c1",
      "name": "term",
      "value": "Active customer",
      "description": "The business term in question. Asked each time.",
      "runtime": true,
      "hasDefault": true,
      "createdAt": "2026-10-05T09:05:52.000Z",
      "updatedAt": "2026-10-05T09:05:52.000Z"
    },
    {
      "id": "edac7b33-f043-470a-9026-86b182752dd7",
      "name": "matrix inputs",
      "value": "",
      "description": "The business functions, applications and data entities to relate, with what is known about which one creates, reads, updates or deletes each entity. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:53.000Z",
      "updatedAt": "2026-10-05T09:05:53.000Z"
    },
    {
      "id": "82045cf4-150e-44dc-ad01-4a3469ff69a6",
      "name": "entity",
      "value": "Customer",
      "description": "The data entity in question. Asked each time.",
      "runtime": true,
      "hasDefault": true,
      "createdAt": "2026-10-05T09:05:54.000Z",
      "updatedAt": "2026-10-05T09:05:54.000Z"
    },
    {
      "id": "c89d3efa-1e05-496f-897e-7978a3217287",
      "name": "data flow facts",
      "value": "",
      "description": "What is known about how the data moves and lives: senders, receivers, mechanisms, frequencies, copies and lifecycle events. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:55.000Z",
      "updatedAt": "2026-10-05T09:05:55.000Z"
    },
    {
      "id": "669c1a92-5852-4689-9ee5-d6bc3873679d",
      "name": "access facts",
      "value": "",
      "description": "What is known about who accesses which data, from where, for what, and the controls in place. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:56.000Z",
      "updatedAt": "2026-10-05T09:05:56.000Z"
    },
    {
      "id": "815d6568-c915-42f9-8c60-a614ca6f487d",
      "name": "personal data facts",
      "value": "",
      "description": "What is known about the personal data in scope and the design that handles it: elements, subjects, purposes, where collected, held and shared, the flows proposed, consents and notices. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:57.000Z",
      "updatedAt": "2026-10-05T09:05:57.000Z"
    },
    {
      "id": "97a5dc64-9edd-46da-9aae-422f78889929",
      "name": "compliance inputs",
      "value": "",
      "description": "The requirements, obligations and advice legal, compliance, the privacy office or records management have given, as they gave them. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:58.000Z",
      "updatedAt": "2026-10-05T09:05:58.000Z"
    },
    {
      "id": "fc2a7ce9-3331-408b-826c-dd37ae60f309",
      "name": "target drivers",
      "value": "",
      "description": "The business drivers, requirements and constraints the target data architecture must serve, with a summary of the baseline where one exists. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:05:59.000Z",
      "updatedAt": "2026-10-05T09:05:59.000Z"
    },
    {
      "id": "9e26a0df-ab9b-4738-be07-e6f258a4fa84",
      "name": "baseline and target",
      "value": "",
      "description": "The baseline and target data architecture descriptions to compare or review, or the gap analysis already made. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:06:00.000Z",
      "updatedAt": "2026-10-05T09:06:00.000Z"
    },
    {
      "id": "27e7e4c5-ba24-4216-bdec-b23e568d3ccd",
      "name": "master data facts",
      "value": "",
      "description": "What is known about the candidate master and reference data: entities, systems, volumes, duplication, code sets and complaints. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:06:01.000Z",
      "updatedAt": "2026-10-05T09:06:01.000Z"
    },
    {
      "id": "3e009582-fdc7-4c10-acfb-247d3dcef1ee",
      "name": "data roles",
      "value": "",
      "description": "What is known about the people and roles around the data: owners, stewards in fact or in title, bodies, disputes and gaps. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:06:02.000Z",
      "updatedAt": "2026-10-05T09:06:02.000Z"
    },
    {
      "id": "6b70a961-59e0-4d55-bc54-aa18252b014b",
      "name": "quality facts",
      "value": "",
      "description": "What is known about data quality in scope: elements and rules already written, dependent reports and processes, complaints, incidents, measurements and thresholds mentioned. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:06:03.000Z",
      "updatedAt": "2026-10-05T09:06:03.000Z"
    },
    {
      "id": "fb48f53f-f7fa-4c89-bdcd-7dc9d5da2c64",
      "name": "lineage facts",
      "value": "",
      "description": "What is known about the data's origins and movements: sources, systems, transformations, outputs and the metadata already recorded, plus the change to assess where there is one. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:06:04.000Z",
      "updatedAt": "2026-10-05T09:06:04.000Z"
    },
    {
      "id": "bd267f68-e112-4a0d-859d-87a6fcf7624c",
      "name": "critical report",
      "value": "The monthly revenue report to the board",
      "description": "The report or output whose lineage is being traced. Asked each time.",
      "runtime": true,
      "hasDefault": true,
      "createdAt": "2026-10-05T09:06:05.000Z",
      "updatedAt": "2026-10-05T09:06:05.000Z"
    },
    {
      "id": "3a92a1f4-b024-492d-b6b6-3f3696d5be4a",
      "name": "platform facts",
      "value": "",
      "description": "The analytics needs, consumers, volumes, skills and constraints the platform must meet, and the data product to specify where there is one. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:06:06.000Z",
      "updatedAt": "2026-10-05T09:06:06.000Z"
    },
    {
      "id": "ed587f96-b8df-42b4-a122-db250b54303e",
      "name": "integration facts",
      "value": "",
      "description": "What is known about the flows in question: systems, entities, direction, freshness needed, volumes, mechanisms today and problems reported. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:06:07.000Z",
      "updatedAt": "2026-10-05T09:06:07.000Z"
    },
    {
      "id": "4d76d859-3783-4087-839e-108472ccbc9d",
      "name": "migration facts",
      "value": "",
      "description": "What is known about the migration: source and target systems, entities and volumes, history, cutover constraints, quality problems, people and dates. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:06:08.000Z",
      "updatedAt": "2026-10-05T09:06:08.000Z"
    },
    {
      "id": "d9e4cb8c-1582-45ef-8e35-1bd9be9e39a7",
      "name": "retention inputs",
      "value": "",
      "description": "The retention schedule extract, record classes and obligations as records management and legal gave them, with the entities and systems in scope. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:06:09.000Z",
      "updatedAt": "2026-10-05T09:06:09.000Z"
    },
    {
      "id": "735b2957-d995-4b6c-a112-cd2b28ae108f",
      "name": "deal facts",
      "value": "",
      "description": "What is known about the deal and the target's data: deal type and timetable, the target's business and systems as the data room shows them, documents received, questions asked, intended shape of the combined business. Asked each time.",
      "runtime": true,
      "hasDefault": false,
      "createdAt": "2026-10-05T09:06:10.000Z",
      "updatedAt": "2026-10-05T09:06:10.000Z"
    }
  ],
  "notes": [],
  "expectedOutputs": [],
  "attachments": [],
  "settings": {},
  "config": {
    "blockTypes": [
      "Role",
      "Task",
      "Context",
      "Format",
      "Constraints"
    ],
    "promptTypes": [
      "User Prompt",
      "System Prompt",
      "Skill"
    ]
  }
}
