Yggdrasil — A living map of your organization

01 · Discover

Your first living model starts with what already exists.

Ratatosk scans repositories, trackers, and connected systems, then hands precise candidates to Munin. No blank-canvas modelling project. No archaeology workshop.

48-hour bootstrap

YggdrasilRatatosk / BootstrapDiscovering

New model

Payments landscape

Repository, work tracker, and delivery pipeline.

run rtk-1042

ratatosk

$ ratatosk bootstrap ./payments --model payments

✓ built ModelSummary
✓ scanned 4 repositories
✓ found Payment API + 26 candidates
✓ resolved owners and dependencies

Munin planned ChangeSet #1042
37 operations · 34 high confidence · 3 review

02 · Orient

Start with the decisions, not an extraction log.

Munin turns discovery into an architectural briefing: what was found, what matters, what is uncertain, and where human attention is needed.

Post-run architectural briefing

YggdrasilMunin / BriefingComplete

Run rtk-1042

Payments architecture is ready to explore

Munin’s summary from 41 sourced facts.

18m 42s · just now

Auto-applied34high confidence

Review3ownership edges

Skipped2below threshold

Coverage86%repository surface

Munin’s summary

Payment API is the most connected service in this landscape. It serves Checkout, depends on Ledger and Fraud, and is owned by Payments Platform. Three cross-team ownership edges need confirmation.

01 Payment API is a critical integration hub02 Fraud Gateway has no verified owner03 One repository maps to two candidate components

03 · Trace meaning

Follow value all the way down to the component.

Customer to component is the spine. A failing touchpoint traces into the capability, applications, teams, and vendors behind it; an orphaned component has nowhere to hide.

Customer to component traceability

YggdrasilView / Checkout experienceAt risk

Customer to component

Why Payment API matters

Demand and supply in one defensible path.

view://checkout-impact

CustomerOnline shopperwho we serve

→

Point of contactPayment stephealth: at risk

→

CapabilityCollect paymentowner: Commerce

→

ApplicationPayment APIhealth: degraded

→

Infrastructurepayments-prodAWS · us-east-1

Blast radius Checkout · Orders · SubscriptionsOwnership Payments PlatformBusiness signal 31% payment attempts affected

04 · Explore

Ask a precise question and save the answer as a living View.

Filters define the roots, depth expands the graph, and Content controls which facts appear. Named Views preserve the same semantic URL for humans and AI.

View Browser · Named Views

YggdrasilView Browserpriya@platform

Collect paymentCapability

Payment APIOwner: Payments Platform
Health: Degraded

Ledger APIExternal

payments-prodEnvironment

/models/payments/views/?stereotype=component&owner=payments-platform&depth=3&mode=graph

05 · Ask

Let Munin work inside the model, not beside it.

Munin answers from ground truth, cites every element, and drives the View Browser around the answer. It can scope views, prefill changes, and narrate history without inventing architecture.

Grounded conversational navigation

YggdrasilView Browser / MuninGrounded

Scoped view

Cross-team dependencies on Payment API

3 elements · depth 2

Checkout WebCommerce→Payment APIPayments←Billing WorkerFinance Systems

06 · Ground AI

Give every agent live ground truth before it acts.

MCP exposes the same structural, behavioral, and state model behind the GUI. Your ADE can resolve ownership, dependencies, contracts, and freshness instead of guessing.

Live ground truth through MCP

YggdrasilMCP / Tool exchangeVerified

Organizational AI

Can I safely change Payment API?

One bounded query before planning.

182 ms

Agent tool call

traverse({ from: "payment-api", direction: "both", depth: 2, as_of: "now" })

Yggdrasil response

{ "owner": "Payments Platform", "dependents": 3, "contracts": ["checkout-v2"], "health": "degraded", "open_change": "CS-1042", "freshness_seconds": 241 }

07 · Shape

Curate the architecture without losing the graph.

A Draft-first diagram is a presentation of canonical Elements and Relationships—not a disconnected drawing. Drag from the model tree or ask Munin to patch the draft, then Save through a ChangeSet.

Draft-first diagram editor

YggdrasilDiagram EditorDraft

Payment Container Diagramtechnology · container

DiscardSave

Checkout WebContainer

calls

Payment APIContainer · Draft

depends_on

Ledger APIExternal

payments-dbContainer

08 · Govern

Automation moves fast. Human judgment stays in control.

Every write becomes a precise ChangeSet. High-confidence operations can apply automatically; ambiguous ones wait for Accept, Reject, or a corrective instruction Munin learns from.

ChangeSet review and curation

YggdrasilChangeSet / CS-10423 pending

Manual review

Ratatosk update · Payment API

Munin planned five graph operations from commit 9f8a2c1.

source: ratatosk

Accept all high confidenceReject all

01Update ElementPayment API · version 2.7.0 → 2.8.096%Accepted

02Link ElementPayment API → depends_on → Fraud Gateway74%

03Add to DiagramPayment API → Payment Integration Diagram68%

Use the integration view, not the container view. Apply instruction

09 · Compare

Return to any point in time and see exactly what moved.

Time travel makes architecture change visible. Compare releases, trace drift, and explain why today’s landscape differs from last quarter’s instead of debating old diagrams.

Time travel and architecture diff

YggdrasilHistory / PaymentsAug 14 → Sep 28

Time travel

Payment API · release comparison

Model A and B reconstructed from bitemporal history.

45 days

Sep 28

v2.8.0Fraud Gateway dependency added

Sep 12

v2.7.0Owner changed to Payments Platform

Aug 14

v2.5.2Baseline selected

Architecture diff3 changes

+depends_on · Fraud GatewayChangeSet CS-1042

~owner · Commerce → Payments PlatformChangeSet CS-991

+contract · checkout-v2ChangeSet CS-1007

10 · Compound

The model gets more trustworthy every time the system changes.

Ratatosk update reconciles only the delta. Every fact retains Provenance, confidence, and freshness; every Munin decision remains inspectable. The repository compounds instead of rotting.

Continuous update · Provenance · Freshness

YggdrasilRun / rtk-1098Applied

Incremental update

Payment API after merge 9f8a2c1

Evidence gathered, reconciled, and committed without a full rescan.

42 seconds

1Trigger classifiedcommit diff · 18 files

2Bounded scout6 reads · 3 MCP calls

3Delta reconciled2 add · 3 update · 0 delete

4Munin planned and appliedChangeSet CS-1098

Fact provenancePayment API → version 2.8.0

Source: GitHub · payments/api
Evidence: pyproject.toml · commit 9f8a2c1
Observed: 2026-09-28 14:38 UTC
Confidence: 96%
Freshness: 42 seconds

A living map of your organization.

Built from reality. Maintained by events.