Scryr — Actionable architecture

The architecture grimoire

Scryr

Actionable architecture.

Turn the page ↓

01 / The old world

AI agents have transformed software.

Why do software diagrams still look like this?

● ● ● architecture-final-v7-updated.mmd

graph TD
  A --> B & C & D
  B -- maybe? --> F
  C --> A --> E --> C

02 / A living map

Make your codebase
a spellbook.

A system you can read, explore, and interrogate—not a picture that starts going stale the moment it is exported.

Open the grimoire ↗

03 / Runtime evidence

Examine what is happening now.

Bring metrics into the architecture. Trace latency, traffic, and errors back to the service that produced them.

northwind-api● LIVE

Requests / minute24,891+12.4%

p95 latency 184mserror rate 0.08%

deploy-production.ymlFAILED

⌁feat: route checkout through payments-v27f3a1c8 · 4 minutes ago

✓Build42s

✓Test1m 08s

×Deployexit 1

×stripe-integrationHealth check failed after revision 38503

04 / Delivery evidence

Examine what build broke.

Connect CI/CD history to the map. See the commit, pipeline, and affected service in one place.

05 / Source of truth

Generate it from a typed Python file.

◆ index.scry

from scryr import Diagram, Manifest, Info, Metrics, CICD

api = Manifest(
    name="northwind-api",
    info=Info(
        owner_team="Commerce",
        language=ProgrammingLanguage.python,
    ),
    metrics=Metrics(provider=MetricsProvider.prometheus),
    cicd=CICD(provider=CICDProvider.github_actions),
)

Diagram(name="Northwind", manifests=[api])

Create your spellbook →Generate with an agent