tadforce 0.0.0-stage → 0.3.0

package/templates/specs/sections.yml

@@ -0,0 +1,494 @@
+# TADForce section specifications.
+# One entry per `<!-- tad:pending <id> -->` marker of the skeletons. The agent replaces the marker with
+# content that satisfies the spec. Specs are written in English; the content is written in the
+# document language (tadforce.config.json > language).
+#
+#   intent   what the reader must understand after reading the section
+#   facts    facts.json paths to read first (use {{n:...}} placeholders for every count)
+#   modules  skills/tadforce/references/modules/*.md files to read when the module is detected
+#   must     elements that must appear
+#   never    what must not appear (debt goes to the Improvement Axes document, not to the client TAD)
+#   figure   expected figure, if any (see skills/tadforce/references/figure-rules.md)
+#   length   indicative size
+version: 1
+
+requiredAnchors:
+  tad: [doc-control, ch-summary, ch-purpose, method, ch-context, ch-general, general-context, ch-functional, ch-data, data-overview, ch-application, ch-ui, ch-integration, ch-security, sec-sharing, ch-reporting, ch-operations, ch-nfr, ch-decisions, ch-outlook, appendices, annex-apex, annex-automation, annex-objects, annex-apps, annex-lwc, annex-security, annex-integration, annex-glossary]
+  axes: [doc-control, ax-summary, ax-method, ax-findings, ax-register, ax-roadmap]
+
+sections:
+  # ------------------------------------------------------------------ 1 Executive summary
+  summary.overview:
+    doc: tad
+    intent: "In one screen: what the platform is, who uses it and on which Salesforce products it stands."
+    facts: [ui.apps, modules.clouds, counts]
+    must:
+      - "Name the solution and its role in the client's information system (system of engagement, service desk, commerce front-office, partner portal...)."
+      - "The user populations and the application each one uses (from ui.apps and glossary.actors)."
+      - "The 2 to 5 Salesforce products actually used (modules.clouds), one line each on what they bring to this client."
+    never:
+      - "Counts written as raw numbers (the KPI tiles below carry them)."
+      - "Defects, risks or roadmap items."
+    length: "2 short paragraphs and 2 bullet lists."
+  summary.capabilities:
+    doc: tad
+    intent: "The business capabilities covered, grouped by domain."
+    facts: [ui.apps, data.objects, automation.flows, systems]
+    must:
+      - "Table 'Domain | Main capabilities' with 5 to 9 rows, each row grounded on components that exist."
+    never:
+      - "Capabilities that no component supports."
+      - "Decommissioned features (knowledge/exclusions.yml > features)."
+  summary.achievements:
+    doc: tad
+    intent: "The 4 to 6 achievements that make this implementation remarkable: what the integrator built, not what Salesforce provides."
+    facts: [apex.classes, data.cmdtTypes, automation, security.permissionSetGroups, integration]
+    must:
+      - "Raw HTML block <div class=\"cards\"> with one <div class=\"card\"><h4>Title</h4><p>2 to 4 sentences</p></div> per achievement."
+      - "Each card names the mechanism and its key component in code font, and says why it matters (configurable without code, scales, secure by design...)."
+    never:
+      - "Marketing superlatives."
+      - "Anything not visible in the metadata or in the inputs."
+  summary.principles:
+    doc: tad
+    intent: "The architecture principles actually applied, as a numbered list of 4 to 7 items."
+    facts: [modules, counts.apex, data.cmdtTypes, integration.namedCredentials]
+    must:
+      - "Each principle in bold followed by one sentence of evidence (example: 'Configuration in Custom Metadata: scoring rules and thresholds are records, not code')."
+
+  # ------------------------------------------------------------------ 2 Purpose, scope, references
+  purpose.object:
+    doc: tad
+    intent: "Why this document exists and who reads it."
+    must:
+      - "Purposes: shared understanding, run and maintenance, evolutions, architecture and security reviews, knowledge transfer."
+      - "Audience list (architects, application owners, operations, security, developers)."
+    length: "1 paragraph and 1 list."
+  purpose.scope:
+    doc: tad
+    intent: "What is in and out of scope."
+    must:
+      - "Two-column table 'Included | Excluded'."
+      - "Excluded column names the internals of external systems, package internals, business data, and CI/CD administration when the client owns it."
+  purpose.references:
+    doc: tad
+    intent: "Documents used as inputs."
+    facts: [knowledge/inputs]
+    must:
+      - "Table 'Ref. | Document | Purpose' with DR-01, DR-02... identifiers."
+      - "Include the official Salesforce documentation relied on (Well-Architected, Integration Patterns, product documentation)."
+    never:
+      - "Documents that were not provided."
+
+  # ------------------------------------------------------------------ 3 Context
+  context.drivers:
+    doc: tad
+    intent: "The business drivers that justify the platform."
+    must:
+      - "3 to 6 bullets, each a business outcome (not a feature)."
+    never:
+      - "Invented figures."
+  context.actors:
+    doc: tad
+    intent: "Who uses the platform and through which application."
+    facts: [ui.apps, security.permissionSetGroups, security.profiles, org.usersByProfile, org.usersByLicense]
+    must:
+      - "Table 'Population | Application | Main activities'. Users per population only when org facts exist."
+      - "External populations (customers, partners, citizens) when Experience Cloud or a mobile app exists."
+  context.scope:
+    doc: tad
+    intent: "Functional perimeter in one table."
+    must:
+      - "Table 'Domain | Covered by' linking to the chapter 5 sections with {{ref:...}} placeholders."
+
+  # ------------------------------------------------------------------ 4 General architecture
+  general.context:
+    doc: tad
+    intent: "Explain the context view above."
+    facts: [systems, integration, ui.apps]
+    must:
+      - "One paragraph per side of the figure (users, Salesforce, connected systems)."
+      - "External systems named exactly as in glossary.systems."
+    never:
+      - "System names not confirmed in the glossary."
+  general.products:
+    doc: tad
+    intent: "What each Salesforce product, industry cloud or package is used for in this org."
+    facts: [modules.clouds, namespaces, org.packages]
+    modules: [all detected]
+    must:
+      - "Table 'Product | Use in the solution', one row per entry of modules.clouds that is really used."
+      - "A 'standard first' statement: what is standard, what is specific."
+  general.layers:
+    doc: tad
+    intent: "Explain the layered view and the responsibility of each layer."
+    must:
+      - "Table 'Layer | Components | Responsibility' (Presentation, Orchestration, Apex services, Data, Integration)."
+  general.principles:
+    doc: tad
+    intent: "Design principles with their concrete application."
+    must:
+      - "4 to 8 bullets 'principle: how it is applied' (standard first, configuration over code, bulk-safe, secure server-side...)."
+  general.naming:
+    doc: tad
+    intent: "Naming conventions observed in the metadata (table above) and their meaning."
+    facts: [naming]
+    must:
+      - "Interpret the prefixes and suffixes (example: '*TriggerHandler', 'lwcNNN_')."
+      - "Where the convention is not followed, state it as a neutral fact."
+
+  # ------------------------------------------------------------------ 5 Functional
+  functional.domains:
+    doc: tad
+    intent: "Map of the functional domains and where each one is described."
+    must:
+      - "A Mermaid flowchart of domains (classes actor, sf, ext, data) followed by a Figure caption, or a table 'Domain | Objects | Main components | Section'."
+    figure: "flowchart LR of the domains."
+  functional.processes:
+    doc: tad
+    intent: "One '##' section per business domain, describing the business process as implemented."
+    facts: [data.objects, automation.flows, apex.classes, ui.lwc, automation.omnistudio]
+    modules: [all detected]
+    must:
+      - "Write one '## <Domain> {#fn-<slug>}' section per domain (typically 5 to 10)."
+      - "For each domain: what the user does, what the platform does (components in code font), statuses and transitions, notifications."
+      - "Cloud-specific processes follow the module reference (case management for Service Cloud, quote-to-cash for CPQ/Revenue, appointment lifecycle for Field Service, checkout for Commerce...)."
+      - "A sequence or state diagram when the process has branches or asynchronous steps (only observed calls)."
+      - "Optional '> [!INTEGRATOR]' callout for a notable design choice of the integrator."
+    never:
+      - "Decommissioned features."
+      - "Screens or steps not evidenced by metadata or inputs."
+
+  # ------------------------------------------------------------------ 6 Data
+  data.principles:
+    doc: tad
+    intent: "Modeling choices."
+    facts: [data.objects, namespaces, modules.clouds]
+    must:
+      - "Standard and industry objects first, custom objects for specific needs only."
+      - "Lookup versus master-detail policy, external IDs for integrations, configuration in Custom Metadata."
+  data.overview:
+    doc: tad
+    intent: "Explain the overview ERD generated above."
+    must:
+      - "The central objects and how the domains hang off them (1 to 2 paragraphs)."
+    never:
+      - "Relationships that are not Lookup or Master-Detail fields."
+  data.domains:
+    doc: tad
+    intent: "One '###' per data domain with its ERD and an object table."
+    facts: [data.objects]
+    must:
+      - "'### <Domain>' then '@@ERD:Obj1,Obj2,Obj3|<caption>@@' (4 to 9 objects) then a table 'Object | Role | Key fields'."
+      - "Only objects of the inventory."
+  data.industry:
+    doc: tad
+    intent: "Industry cloud objects actually used, and for what."
+    facts: [namespaces, data.objects, modules.clouds]
+    modules: [industries]
+    must:
+      - "Table 'Object | Use'. Only objects referenced by the local metadata."
+  data.externalIds:
+    doc: tad
+    intent: "Role of each external ID: which system feeds it, matching key for upserts."
+    must:
+      - "One sentence per key family."
+  data.recordTypes:
+    doc: tad
+    intent: "Why record types exist and what differs between them."
+  data.cmdt:
+    doc: tad
+    intent: "Which business rules are configured in Custom Metadata (changed without deploying code)."
+    must:
+      - "Table 'Type | What it configures'."
+      - "Optional '> [!INTEGRATOR]' callout."
+  data.events:
+    doc: tad
+    intent: "Platform events and change data capture: publishers and subscribers."
+    modules: [platform-events]
+  data.dataCloud:
+    doc: tad
+    intent: "Data Cloud: data streams, data model objects, identity resolution, segments and activations used by the CRM."
+    modules: [data-cloud]
+  data.files:
+    doc: tad
+    intent: "How documents and files are stored (Salesforce Files, external document store, attachments)."
+  data.volumes:
+    doc: tad
+    intent: "Comment the volumes table (largest objects, growth drivers, large data volume measures)."
+    never:
+      - "Record-level data."
+  data.lifecycle:
+    doc: tad
+    intent: "Creation, update, archiving and deletion of data; history tracking; retention."
+    must:
+      - "When nothing is configured, state it as a fact to confirm, not as a defect."
+
+  # ------------------------------------------------------------------ 7 Application
+  application.principles:
+    doc: tad
+    intent: "Apex design principles observed (one trigger per object, handler pattern, selector and service separation, bulkification, user mode)."
+    facts: [counts.apex, naming.apex]
+  application.layers:
+    doc: tad
+    intent: "Code layers and naming conventions."
+    must:
+      - "Mermaid flowchart TB of the layers (LWC or Flow, controllers, services, selectors, integration) with a Figure caption."
+      - "Table 'Layer | Convention | Examples'."
+    figure: "flowchart TB"
+  application.domains:
+    doc: tad
+    intent: "Main classes grouped by functional domain."
+    must:
+      - "Table 'Domain | Main classes | Role'; at most 6 classes per row, the rest in the appendix ({{ref:annex-apex}})."
+  application.triggers:
+    doc: tad
+    intent: "Trigger framework and order of execution."
+    facts: [apex.triggers, signals]
+    must:
+      - "Table 'Object | Trigger | Handler | Events'."
+      - "A '### Order of execution' subsection when several automations act on the same object."
+  application.mechanisms:
+    doc: tad
+    intent: "The 1 to 3 cross-cutting mechanisms that drive the solution (ownership propagation, rules engine, provisioning...), each with a sequence diagram."
+    must:
+      - "Name the thresholds and switches visible in code (example: synchronous up to N records, then batch) with the class that implements them."
+  application.async:
+    doc: tad
+    intent: "Batch, queueable, schedulable and @future processing."
+    facts: [apex.classes, org.scheduledJobs]
+    must:
+      - "Table 'Job | Type | Trigger or schedule | Purpose'."
+      - "Mermaid flowchart of chaining when jobs chain."
+  application.flows:
+    doc: tad
+    intent: "Role of flows next to Apex, and the main active flows."
+    facts: [automation.flows]
+    must:
+      - "Table 'Flow | Type | Object | Purpose' for the active flows; the full list stays in the appendix ({{ref:annex-automation}})."
+  application.omnistudio:
+    doc: tad
+    intent: "How OmniStudio is used: OmniScripts for guided journeys, Integration Procedures for orchestration, Data Mappers for data access, FlexCards for display."
+    facts: [automation.omnistudio]
+    modules: [omnistudio]
+    must:
+      - "Mermaid flowchart OmniScript > Integration Procedure > Data Mapper / Apex / HTTP, then one '###' per family with a table."
+  application.ai:
+    doc: tad
+    intent: "Agentforce agents, Einstein features and prompt templates: topics, actions, grounding, guardrails, channels."
+    modules: [agentforce-ai]
+    must:
+      - "Table 'Agent or feature | Channel | Topics or use | Actions (Flow, Apex, prompt)'."
+  application.sequences:
+    doc: tad
+    intent: "2 to 4 key end-to-end sequences (sequenceDiagram), each with a short introduction."
+    must:
+      - "Only calls observed in code or metadata; participants named by component."
+    never:
+      - "Participants that are not in the inventory or the glossary."
+
+  # ------------------------------------------------------------------ 8 UI
+  ui.apps:
+    doc: tad
+    intent: "Applications, their audience and navigation (console or standard, utility bar, mobile)."
+    facts: [ui.apps]
+  ui.pages:
+    doc: tad
+    intent: "Key Lightning pages and their composition."
+    facts: [ui.flexipages]
+    must:
+      - "Table 'Page | Object | Custom components'."
+      - "Optional composition diagram for the main record page."
+  ui.lwc:
+    doc: tad
+    intent: "LWC organised by domain, with the 2 or 3 key components described."
+    facts: [ui.lwc]
+    must:
+      - "'### By domain' table 'Domain | Components | Role'; the full list is in the appendix ({{ref:annex-lwc}})."
+  ui.communication:
+    doc: tad
+    intent: "How components talk: events, Lightning Message Service, navigation, wire adapters, Apex."
+    facts: [ui.lwc, ui.messageChannels]
+  ui.aura:
+    doc: tad
+    intent: "Remaining Aura components and their role (stated neutrally)."
+  ui.sites:
+    doc: tad
+    intent: "Experience Cloud sites, public sites and Visualforce pages: audience, templates, authentication, purpose."
+    modules: [experience-cloud]
+  ui.omnichannel:
+    doc: tad
+    intent: "Telephony (call centers, CTI adapter or Service Cloud Voice) and Omni-Channel routing (channels, queues, skills, capacity), messaging channels."
+    facts: [integration.callCenters, misc.signals]
+    modules: [service-cloud]
+
+  # ------------------------------------------------------------------ 9 Integrations
+  integration.principles:
+    doc: tad
+    intent: "Integration principles (credentials externalised, the system of record stays master, idempotent upserts with external IDs, asynchronous for volume)."
+  integration.patterns:
+    doc: tad
+    intent: "Classify each flow with the Salesforce Integration Patterns."
+    must:
+      - "Table 'Pattern | Flows' using: Remote Process Invocation (Request and Reply, Fire and Forget), Batch Data Synchronization, Remote Call-In, UI Update Based on Data Changes, Data Virtualization."
+  integration.flows:
+    doc: tad
+    intent: "Catalogue of the integration flows."
+    must:
+      - "Table 'ID | Flow | Direction | System | Salesforce component | Pattern' with FLX-01, FLX-02..."
+    never:
+      - "Systems not in glossary.systems."
+      - "Flows that no component implements."
+  integration.systems:
+    doc: tad
+    intent: "One '###' per connected system, with a sequence diagram for the main exchange."
+    facts: [systems, integration.namedCredentials, apex.classes]
+    modules: [integration-platforms]
+    must:
+      - "For each system: purpose, Salesforce endpoints (named credential, authentication), main calls with their Apex class, flow or Integration Procedure."
+  integration.inbound:
+    doc: tad
+    intent: "Exposed APIs (Apex REST or SOAP): callers, payload in one line, security (integration user, permission set, connected app)."
+  integration.marketing:
+    doc: tad
+    intent: "Marketing integration: Marketing Cloud Connect or Account Engagement (synchronised objects, sends, tracking, consent)."
+    modules: [marketing]
+  integration.commerce:
+    doc: tad
+    intent: "Commerce: stores, catalogs, buyer groups, checkout integrations (payment, tax, shipping, inventory) and order management."
+    modules: [commerce]
+  integration.sso:
+    doc: tad
+    intent: "Authentication providers, SSO, registration handlers, connected apps."
+    facts: [integration.authProviders, integration.connectedApps]
+  integration.domains:
+    doc: tad
+    intent: "Why each allowed domain exists (CSP, CORS, remote sites)."
+
+  # ------------------------------------------------------------------ 10 Security
+  security.principles:
+    doc: tad
+    intent: "Security principles (least privilege, persona-based access, server-side checks, no secrets in code)."
+  security.auth:
+    doc: tad
+    intent: "How users log in and how their access is provisioned (SSO, registration handler, provisioning automation)."
+    must:
+      - "A sequence diagram when provisioning is automated."
+  security.personas:
+    doc: tad
+    intent: "Personas and the permission set groups that implement them."
+    facts: [security.permissionSetGroups, org.psgAssignments]
+    must:
+      - "Table 'Persona | Permission set group | Main rights'."
+  security.roles:
+    doc: tad
+    intent: "Comment the role hierarchy: structure and technical roots."
+  security.owd:
+    doc: tad
+    intent: "Default sharing choices and their rationale."
+  security.rules:
+    doc: tad
+    intent: "Sharing rules and queues: what they open and to whom."
+  security.app:
+    doc: tad
+    intent: "Application security in code: sharing keywords, user mode, FLS and CRUD checks, input validation."
+    facts: [counts.apex.withSharing, counts.apex.withoutSharing, apex.classes]
+    must:
+      - "Neutral facts with placeholders, for example '{{n:apex.withSharing}} classes declare with sharing'."
+    never:
+      - "Findings phrased as defects: they go to the Improvement Axes."
+  security.shield:
+    doc: tad
+    intent: "Shield and compliance capabilities in use: platform encryption, event monitoring, transaction security, field audit trail, data masking."
+    modules: [security-shield]
+  security.session:
+    doc: tad
+    intent: "Session and password settings in force."
+    facts: [security.session, security.passwordPolicies]
+  security.integrationUsers:
+    doc: tad
+    intent: "Technical users used by integrations and their permissions."
+  security.public:
+    doc: tad
+    intent: "Guest access and public exposure of sites and APIs."
+
+  # ------------------------------------------------------------------ 11-15
+  reporting.reports:
+    doc: tad
+    intent: "Reporting and dashboards: folders, audiences, KPI components."
+  reporting.analytics:
+    doc: tad
+    intent: "CRM Analytics or Tableau: apps, dataflows or recipes, datasets, embedding in Lightning pages, security predicates."
+    modules: [analytics]
+  operations.environments:
+    doc: tad
+    intent: "Environments (production, sandboxes and their purpose) and their refresh policy."
+    never:
+      - "Environments not confirmed by the client."
+  operations.release:
+    doc: tad
+    intent: "How a release is prepared and delivered: pipeline, order of deployment, manual steps."
+    must:
+      - "A sequence or flowchart when the release has phases."
+  operations.scheduled:
+    doc: tad
+    intent: "Scheduled processing to monitor in run."
+  operations.logging:
+    doc: tad
+    intent: "Logging, error handling and monitoring."
+  operations.tests:
+    doc: tad
+    intent: "Test strategy: test classes, data factories, mocks, coverage."
+    facts: [counts.apex.tests, org.coverage]
+  nfr.measures:
+    doc: tad
+    intent: "Non-functional requirements and the measures in place."
+    must:
+      - "Table 'Requirement | Measures in place' (security, performance, volume, availability, maintainability, traceability)."
+  nfr.wellArchitected:
+    doc: tad
+    intent: "Reading of the solution through Salesforce Well-Architected (Trusted, Easy, Adaptable)."
+    must:
+      - "Table 'Pillar | Strengths observed'. Optionally run the platform-architecture-analyze skill first."
+    never:
+      - "Scores or defects: keep them for the Improvement Axes."
+  decisions.adr:
+    doc: tad
+    intent: "Architecture decisions taken."
+    must:
+      - "Table 'ID | Decision | Rationale | Consequence' with ADR-01...; only decisions visible in the metadata or provided by the client."
+  outlook.roadmap:
+    doc: tad
+    intent: "Evolution perspectives, stated positively."
+    must:
+      - "Bullets; refer to the Improvement Axes document for the detailed register without quoting its findings."
+
+  # ------------------------------------------------------------------ Improvement Axes
+  axes.summary:
+    doc: axes
+    intent: "The 5 most important axes, and the overall health in one paragraph per pillar."
+    facts: [signals, counts]
+  axes.method:
+    doc: axes
+    intent: "Optional details on how the signals were obtained (Code Analyzer report, Well-Architected skill run, interviews)."
+  axes.trusted:
+    doc: axes
+    intent: "Qualify each Trusted signal: real risk, scope, remediation."
+    must:
+      - "One paragraph per signal kept, with its AX-nn reference."
+  axes.easy:
+    doc: axes
+    intent: "Qualify each Easy signal."
+  axes.adaptable:
+    doc: axes
+    intent: "Qualify each Adaptable signal."
+  axes.register:
+    doc: axes
+    intent: "The register of improvement axes."
+    must:
+      - "Table 'ID | Axis | Finding | Impact | Recommendation | Priority | Effort' with AX-01..., priority written <span class=\"b p1\">P1</span>."
+  axes.roadmap:
+    doc: axes
+    intent: "Sequencing of the axes over releases or quarters."
+    must:
+      - "A Mermaid gantt or a table 'Horizon | Axes'."

package/templates/tad/en/00-document-control.md

@@ -0,0 +1,7 @@
+# Document control {- #doc-control}
+
+@@ANNEX:doc-control@@
+
+## Version history {- #version-history}
+
+@@ANNEX:version-history@@

package/templates/tad/en/01-summary.md

@@ -0,0 +1,17 @@
+# Executive summary {#ch-summary}
+
+<!-- tad:pending summary.overview -->
+
+@@KPIS@@
+
+## Business capabilities covered {#summary-capabilities}
+
+<!-- tad:pending summary.capabilities -->
+
+## Key achievements {#summary-achievements}
+
+<!-- tad:pending summary.achievements -->
+
+## Architecture principles applied {#summary-principles}
+
+<!-- tad:pending summary.principles -->

package/templates/tad/en/02-purpose.md

@@ -0,0 +1,35 @@
+# Purpose, scope and references {#ch-purpose}
+
+## Purpose of the document {#purpose}
+
+<!-- tad:pending purpose.object -->
+
+## Scope {#scope}
+
+<!-- tad:pending purpose.scope -->
+
+## References {#references}
+
+<!-- tad:pending purpose.references -->
+
+## Method {#method}
+
+This document describes the architecture **as implemented** in the Salesforce organization of {{cfg:client.name}} ({{cfg:document.environment}}), as of {{cfg:document.date}}. It was produced from the metadata of the organization, retrieved in read-only mode, and from the inputs provided by {{cfg:client.name}} and {{cfg:integrator.name}}.
+
+- Inventories and counts cover the components built for {{cfg:client.name}}. Components delivered by managed packages and unused standard samples are excluded.
+- Each statement relies on the metadata, on a document provided by the project, or is explicitly marked as to be confirmed.
+- Authentication parameters (identifiers, secrets, certificates) and business data are never reproduced.
+
+<!-- tad:if facts.exclusions.applied -->
+The following components exist in the organization but are outside the documented architecture:
+
+@@ANNEX:exclusions@@
+<!-- tad:endif -->
+
+## Reading conventions {#conventions}
+
+- Technical names (objects, fields, classes, flows, components) are written in monospace, for example `Account`. Business labels are written in quotes, for example « Customer ».
+- Salesforce terms in common use (Lead, Queue, Record Type, Permission Set, Named Credential…) are kept as is.
+- Diagrams share one colour code:
+
+@@ANNEX:legend@@

package/templates/tad/en/03-context.md

@@ -0,0 +1,17 @@
+# Context and vision {#ch-context}
+
+## Business drivers {#context-drivers}
+
+<!-- tad:pending context.drivers -->
+
+## Actors and user populations {#context-actors}
+
+<!-- tad:pending context.actors -->
+
+## Functional scope {#context-scope}
+
+<!-- tad:pending context.scope -->
+
+## Key figures {#context-figures}
+
+@@ANNEX:key-figures@@

package/templates/tad/en/04-general.md

@@ -0,0 +1,29 @@
+# General architecture {#ch-general}
+
+## Context view {#general-context}
+
+@@FIGURE:context@@
+
+<!-- tad:pending general.context -->
+
+## Salesforce foundation and products {#general-products}
+
+@@ANNEX:products@@
+
+<!-- tad:pending general.products -->
+
+## Logical architecture in layers {#general-layers}
+
+@@FIGURE:layers@@
+
+<!-- tad:pending general.layers -->
+
+## Design principles {#general-principles}
+
+<!-- tad:pending general.principles -->
+
+## Naming conventions {#general-naming}
+
+@@ANNEX:naming@@
+
+<!-- tad:pending general.naming -->

package/templates/tad/en/05-functional.md

@@ -0,0 +1,7 @@
+# Functional architecture and business processes {#ch-functional}
+
+## Functional domains {#functional-domains}
+
+<!-- tad:pending functional.domains -->
+
+<!-- tad:pending functional.processes -->

package/templates/tad/en/06-data.md

@@ -0,0 +1,71 @@
+# Data architecture {#ch-data}
+
+## Modeling principles {#data-principles}
+
+<!-- tad:pending data.principles -->
+
+## Overview {#data-overview}
+
+@@ERD:auto|Main objects and their relationships@@
+
+<!-- tad:pending data.overview -->
+
+## Objects by domain {#data-domains}
+
+<!-- tad:pending data.domains -->
+
+<!-- tad:if modules.industryCloud -->
+## Industry cloud objects {#data-industry}
+
+<!-- tad:pending data.industry -->
+<!-- tad:endif -->
+
+## External IDs and integration keys {#data-external-ids}
+
+@@ANNEX:external-ids@@
+
+<!-- tad:pending data.externalIds -->
+
+## Record types and business processes {#data-record-types}
+
+@@ANNEX:record-types@@
+
+<!-- tad:pending data.recordTypes -->
+
+<!-- tad:if counts.cmdt.types -->
+## Configuration in Custom Metadata {#data-cmdt}
+
+@@ANNEX:cmdt@@
+
+<!-- tad:pending data.cmdt -->
+<!-- tad:endif -->
+
+<!-- tad:if modules.events -->
+## Platform events and change data capture {#data-events}
+
+@@ANNEX:platform-events@@
+
+<!-- tad:pending data.events -->
+<!-- tad:endif -->
+
+<!-- tad:if modules.dataCloud -->
+## Data Cloud {#data-cloud}
+
+<!-- tad:pending data.dataCloud -->
+<!-- tad:endif -->
+
+## Files and documents {#data-files}
+
+<!-- tad:pending data.files -->
+
+<!-- tad:if org.volumes -->
+## Data volumes {#data-volumes}
+
+@@ANNEX:volumes@@
+
+<!-- tad:pending data.volumes -->
+<!-- tad:endif -->
+
+## Data lifecycle {#data-lifecycle}
+
+<!-- tad:pending data.lifecycle -->