{
  "title": "Account-review application: platform and extension design",
  "type": "populated_reference_design",
  "date": "2026-10-20",
  "purpose": "Give an account team one workspace for a recurring performance review and an on-demand company investigation.",
  "users": [
    "Account lead: chooses the account and review period.",
    "Analyst: checks returned measures and the interpretation.",
    "Manager: records a review decision and the next investigation."
  ],
  "record_model": {
    "account": "The internal account ID is the application key.",
    "external_entity": "Link external company identifiers only after entity matching. Keep an unmatched state.",
    "period": "Every measure and source capture retains its own date and applicable reporting period.",
    "review": "Retain the requested task, workflow run, result and review state as separate records."
  },
  "workflows": [
    {
      "id": "performance-review",
      "trigger": "User request or configured recurring schedule",
      "inputs": [
        "Selected account and period",
        "Approved warehouse view",
        "Finance-approved measure definitions"
      ],
      "steps": [
        "Retrieve the selected measures.",
        "Calculate the defined account movements.",
        "Use an execution agent to inspect comparisons and formulate follow-up questions.",
        "Show the result and source values in the review workspace."
      ],
      "application_extensions": [
        "Warehouse configuration and account mapping",
        "Business-specific calculation service",
        "Review interface and review-state storage"
      ],
      "acceptance": [
        "Account and period match the requested inputs.",
        "The calculation reconciles to the accepted source view.",
        "Missing data is shown as missing.",
        "The displayed finding links to the returned records."
      ]
    },
    {
      "id": "company-investigation",
      "trigger": "User selects a company investigation from the account review",
      "inputs": [
        "Matched legal entity",
        "Selected company filings and external context",
        "The question arising from the review"
      ],
      "steps": [
        "Retrieve the selected external records.",
        "Run the defined company analysis.",
        "Return findings and source references.",
        "Attach the investigation to the correct review record."
      ],
      "application_extensions": [
        "Legal-entity resolution and exception handling",
        "Selected source integrations",
        "Account-linked findings view"
      ],
      "acceptance": [
        "The findings refer to the matched legal entity.",
        "Publication and observation dates are retained.",
        "An unsupported question remains open.",
        "The result is associated with the intended account and workflow run."
      ]
    }
  ],
  "responsibility_matrix": [
    {
      "layer": "Enterprise systems",
      "responsibility": "Own the account, warehouse and other business records."
    },
    {
      "layer": "Evidence OS",
      "responsibility": "Provide selected data, execution-agent and workflow services used by the application."
    },
    {
      "layer": "Custom data and domain services",
      "responsibility": "Map entities, implement business-specific calculations and prepare the records required by each step."
    },
    {
      "layer": "Application",
      "responsibility": "Provide user access, account context, review screens, result state and system handoffs."
    }
  ],
  "integration_readiness": "Select and validate each source connection during the build. A documented integration design is not an assertion that the complete connection or account workflow is already deployed.",
  "handoff_example": {
    "destination": "An agreed account-review record or work item.",
    "implementation": "Define the external object, fields, access and duplicate handling before implementing a write operation.",
    "acceptance": "The intended system receives one correctly mapped result; a failed delivery remains visible."
  },
  "delivery": [
    "Define the first workflow and acceptance records.",
    "Configure selected platform services and build the application extensions.",
    "Test both workflows through the interface and required systems.",
    "Agree deployment, custom-code rights, platform licences and operating ownership."
  ],
  "basis": [
    "/evidence-os/build/",
    "/custom-technology/integration/",
    "/integrations/snowflake/",
    "/integrations/salesforce/",
    "/solutions/company-intelligence/"
  ],
  "status": "Reference design for a custom build; not a customer case study or a production-agent run."
}
