Linked.Archi Tools¶
The semantic assets documented on this site describe how architecture knowledge is represented. The tools below produce and consume it: converters lift models out of the notation tools that authored them, and agent skills answer questions against the graph that results.
| Tool | Role | Where it lives |
|---|---|---|
| Converters | Turn ArchiMate, BPMN, PlantUML, Structurizr/C4, Backstage and LeanIX sources into RDF aligned to the https://meta.linked.archi/ namespaces |
Documented here, with JAR, bundle and Docker downloads |
| Agent Skills (APM) | Give a coding agent the graph's conventions and a tested SPARQL template library, so it can query and investigate the converted graph | GitLab repository — linked-archi/linked-archi-tools/ai-tools/linked-archi-apm |
Converters — models to RDF¶
Each converter is a self-contained command-line tool. Dataset-aware output formats preserve named graphs, triple-only formats flatten them, and a provenance graph records the run, its inputs and the graphs it emitted. Because every notation is aligned to the same foundational ontology, the landscape can be queried through common core types while each source language keeps its own semantics.
Type mappings are configuration rather than code, so a custom metamodel needs no converter change. See Converters for the available converters, output conventions, downloads and the RDF contract they share.
Agent Skills (APM) — questions against the graph¶
linked-archi-apm
packages the graph's conventions as agent skills. There is no application: the artifact is the context and the
query templates, so a coding agent in an ordinary IDE can work as an architecture analyst against converter
output.
| Skill | Use it to |
|---|---|
linked-archi-source |
Materialize verified RDF from HTTPS, a pinned Git revision, or a read-only GitLab MCP into an immutable local cache |
linked-archi-profile |
Establish, verify and derive the profile that tells the other skills what a dataset calls things |
linked-archi-connect |
Attach local RDF files or a read-only SPARQL endpoint, and report honestly what loaded |
linked-archi-query |
Answer a question from a tested, profile-resolved template library |
linked-archi-analyse |
Run a multi-query investigation and answer as a traceable evidence bundle |
linked-archi-validate |
Run SHACL in-process, or summarize a report somebody else produced, and report coverage beside the verdict |
Three properties matter for architecture work:
- Refusal over silence — every template declares the roles and capabilities it needs. When a dataset cannot support one, the answer names the reason and suggests alternatives instead of returning an empty result that reads like a finding. Qualified relationships, named graphs, and absent ownership or cross-source identity all trip up generic text-to-SPARQL quietly, producing queries that run and mislead.
- Vocabulary as data — profiles bind semantic roles to concrete terms, prefixes, graph layout and
taxonomy terms. A profile can be derived from a converter type-mapping file or a published
arch:Metamodelmanifest, so a custom ontology needs no code change.la-profile verifyprobes the dataset and reports drift between claimed and observed terms. - Read-only and traceable — update, insert, delete and load are rejected before any backend is touched, and every result carries a provenance footer naming the template, query hash, dataset, profile version, timestamp and row count.
Installation, the template catalogue and the analysis patterns are documented in the repository. The skills install with APM or by copying the skill directories into whatever a client reads.