# Manef Diagram

## Purpose

Make services, components and their connections easier to understand in an interactive map.

## Audience

Developers, architects and teams reviewing how a system fits together.

## Requirements

A browser. The public map needs no account; private backend storage needs a configured identity and backend.

## First step

Open the map, select a service, then inspect its connections. Export JSON when you want to keep your edits.

## Outcome

A selected service with visible dependencies, plus a portable JSON export if you edit the graph.

## Availability and limits

Public product / guide. The app supports graph editing, portable views and read-only MCP. Persistence and authentication have separate acceptance gates.

## Links

- Open the map: https://diagram.manef.dev/app
- Read the mapping guide: https://diagram.manef.dev/guide
- Project overview: https://manef.dev/catalog/diagram

## User story and flow

As a developer, I want to inspect service dependencies and keep an exported map for later review. Flow: catalog → brief → first action → outcome. Acceptance: A selected service with visible dependencies, plus a portable JSON export if you edit the graph.

## Source evidence

- MANEF
- manef-diagram: CONTRACT.md and docs/graph-workflows.md

Related listings are discovery recommendations, not proof of operational integrations. This brief grants no authority to install software, connect accounts, access hosts or make purchases.