Guide

Architecture

The solution's architecture model in ArchiMate-compatible language: what it is made of, from capabilities down to repositories and running software, and how the parts relate.

For: Project lead, Team developer, Product owner, Admin

Elements

  • Every element has an ArchiMate type (Strategy, Business, Application or Technology layer, or Grouping and Location), a level — conceptual, logical or physical — a status (current, planned, retired) and an origin (written, discovered, imported).
  • Components, repositories and code modules appear by themselves: a component is a physical Application Component, a repository or code module an Artifact that realizes its component. Their name comes from the row; deleting the row retires the element.
  • Capabilities, value streams, resources and courses of action belong to the tenant — the organisation's capability map — and solutions support them. Other shared parts (a core banking system, an identity provider) can belong to the tenant too.
  • The form offers the usual types; Show every ArchiMate type opens the full language.
  • Discovered elements count separately until someone with architecture.approve verifies them.

Relations

  • Relations are ArchiMate's: composition, aggregation, assignment, realization, serving, access (read, write), influence, association, triggering, flow, specialization.
  • Corpole checks each one against ArchiMate's rules for the two element types and refuses an invalid one with the reason. The rules follow the specification's metamodel; Corpole uses ArchiMate-compatible language and is not a certified tool.
  • The chain from concept to code is built with realization: Business Object ← Data Object ← Artifact; Application Component ← Artifact (repository, code module).

Discovery

  • Your agent reads the repository and reports what it finds: infrastructure as code, deployment definitions, API definitions, connection settings (never secrets) and dependency manifests. In Claude Code run /corpole:architecture; other agents use the report_architecture tool.
  • It can also propose conceptual elements — capabilities, business processes, business objects — with the links it sees. Proposed capabilities go to the tenant.
  • Everything arrives discovered and waits under Discovered, waiting for review: verify or discard in bulk. A component's, repository's or module's element can only be verified.
  • When a run covers a whole source, Corpole compares it with the confirmed model: a confirmed part that is gone opens Architecture part missing (DRF-24); a new part where the model was confirmed opens Architecture part not in the model (DRF-25). They appear with the other drift signals on the Agents page.
  • A confirmed element keeps the name and type a person confirmed; a later run only refreshes its description.

Who changes what

  • A solution's elements: architecture.edit (the Architect role has it); verifying and retiring: architecture.approve.
  • The tenant's elements: tenant owners and admins, and account owners and admins.
  • Every change is in the change history (kind Architecture).