Salsa stores generated graph Mermaid strings

Platform spec ADR

Salsa stores generated graph Mermaid strings

Back to Graph visualization ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• Contracts and edge cases LSP beskid.getGraph payload, CLI flags, and graph edge-case policy. article Standard Reviewed Sat May 30
• Design model GraphSpec IR, GraphKind, GraphPayload, and revision fingerprints. article Standard Reviewed Sat May 30

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKarea · 4 SpecSection(s) · 0 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	yes	yes
implementation-anchors	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Graph visualization

  Parent feature hub

• Feature
  Stage ordering and lowering

  Salsa ADR 0005 parent

Context

LSP getProjectGraph rebuilt domain graphs from disk on every call. CLI printed a flattened ASCII tree from CompilePlan, losing multi-hop structure.

Decision

1. graph_fingerprint and graph_mermaid are #[salsa::tracked] queries in beskid_queries::graph.
2. LSP and CLI must read graphs through compilation_db, not ad-hoc rebuilds.
3. Invalidation follows ManifestGenerationId, FileText, and assembly/composition revision inputs per graph kind.

Consequences

• Extension and CLI share the same cached Mermaid revision.
• Manifest or lock edits invalidate project/workspace graphs without full process restart.

Status

Accepted — extends ADR D-COMP-BUILD-0021.