ArchMeta · Built 2026-09-09T17:39:23.802Z

Archmeta Application Interraction

Architect Software SystemArchMetaA platform for managing architecture documentation as code. Architects describe their organisation in a textual DSL stored in Git; the Kernel reads that repository into an in-memory graph and serves it over REST, the Viewer authors it, and the Publisher turns it into a static site. There is no database — Git is the source of truth, and the same commit always produces the same model. External SystemLLM (Claude)Where .arch files come from in practice. The authoring loop is AI-first, which is why the DSL keeps uniform, predictable shapes a model can emit reliably and why the diagnostics and report files matter — they are the feedback channel back to the generator. External SystemGit RemoteGitHub, GitLab or any origin the architect pushes to themselves. Deliberately outside the product: ArchMeta commits so that history exists, and leaves the decision to publish that … Stakeholder ContainerViewerThe single-screen React SPA that is the primary authoring tool: model canvas, BPMN modeler, Markdown editor and Explore in one shell, flanked by a management pane and a docked Inspector. Never reads the whole graph — every instance read is a point read, a search or a bounded neighbourhood — and never touches the filesystem. Edits stage; only a commit sends them to the Kernel. ContainerGenerated SiteThe deliverable: static HTML, CSS and JavaScript with a prebuilt search index. No server, no database, no API — it can be served from object storage, a CDN, an nginx container or a filesystem, which is the point. Authors and curates the modelGenerates .arch files withPushes when they choose toAuthors and curates inReads the published siteBrowses

Elements (7)

Architectarchimate:businessactor

architect

Describes the organisation in the DSL, usually by generating .arch files with an LLM and then adjusting them in the Viewer. Reloads the Kernel and reads the diagnostics to find out whether what they meant is what they wrote. The Viewer's edit mode is for curation, not bulk authoring.

ArchMetac4:softwaresystem

archmeta

A platform for managing architecture documentation as code. Architects describe their organisation in a textual DSL stored in Git; the Kernel reads that repository into an in-memory graph and serves it over REST, the Viewer authors it, and the Publisher turns it into a static site. There is no database — Git is the source of truth, and the same commit always produces the same model.

Also in:archmeta-application-c4-level1

LLM (Claude)c4:externalsystem

llm

Where .arch files come from in practice. The authoring loop is AI-first, which is why the DSL keeps uniform, predictable shapes a model can emit reliably and why the diagnostics and report files matter — they are the feedback channel back to the generator.

Git Remotec4:externalsystem

git-remote

GitHub, GitLab or any origin the architect pushes to themselves. Deliberately outside the product: ArchMeta commits so that history exists, and leaves the decision to publish that history to a human.

Viewerc4:container

archmeta.viewer

The single-screen React SPA that is the primary authoring tool: model canvas, BPMN modeler, Markdown editor and Explore in one shell, flanked by a management pane and a docked Inspector. Never reads the whole graph — every instance read is a point read, a search or a bounded neighbourhood — and never touches the filesystem. Edits stage; only a commit sends them to the Kernel.

Also in:archmeta-application-c4-l2-viewerdocker

Stakeholderc4:person

stakeholder

Reads the published site. Never installs anything, never sees the DSL, and cannot change the model — the site is static HTML with no back end, so there is nothing to give them access to.

Generated Sitec4:container

archmeta.static-site

The deliverable: static HTML, CSS and JavaScript with a prebuilt search index. No server, no database, no API — it can be served from object storage, a CDN, an nginx container or a filesystem, which is the point.

Also in:archmeta-application-c4-l2-web-generation

Relationships (8)

Authors and curates inc4:uses

architect → archmeta.viewer

Authors and curates the modelc4:uses

architect → archmeta

Pushes when they choose toc4:sendsto

architect → git-remote

Generates .arch files withc4:uses

architect → llm

archmeta → archmeta.static-siteArchMeta → Generated Sitearchimate:composition

archmeta → archmeta.static-site

archmeta → archmeta.viewerArchMeta → Viewerarchimate:composition

archmeta → archmeta.viewer

Browsesc4:uses

stakeholder → archmeta.static-site

Reads the published sitec4:uses

stakeholder → archmeta

← Home