@felixfelicis/waxwing
v0.1.0
Published
Inspectable architecture diagrams for humans and coding agents.
Maintainers
Readme
Waxwing
Inspectable architecture diagrams for humans and coding agents.
Turn a structured system model into interactive diagrams with linked documentation, source evidence, and explicit unknowns. Export portable HTML and SVG with the model included.
Explore the live demo · Agent guide · Examples · Contributing

Waxwing is an early, personally maintained project. The formats are experimental; validation checks structure and consistency, not whether your evidence is true. Software version 0.1.0 is the first release; model formats retain their own draft versions.
Try it
Requires Node.js 20.19.0 or newer. No server or account is needed to view the exported diagrams.
npm install -g @felixfelicis/[email protected]Copy the full command above. The package name includes its publisher namespace;
once installed, the terminal command is simply waxwing.
Build the included example:
waxwing build-site "$(npm root -g)/@felixfelicis/waxwing/examples/waxwing/model.json" ./waxwing-demo --direction DOWNOpen waxwing-demo/index.html in your browser. The command above uses macOS/Linux
shell syntax; on Windows, run npm root -g and use its printed path in place of
$(npm root -g). This real example
models a pinned revision of Waxwing itself:
- Open Waxwing: from model to artifact and select Layout engine to inspect its claims.
- Follow Inside architecture layout to see the coordinator, validators, and ELK boundary.
- Open A successful architecture build for the explicit call order, then Read this example for the explanation and source links.
The graph describes dependencies; the workflow describes a scoped successful execution path. Both retain the underlying component identities and evidence.
Use it with your coding agent
Give your agent AGENT_GUIDE.md, access to the code you want to understand, and a concrete question:
Use the Waxwing agent guide to explain how this repository handles an incoming request. Inspect the code, create a partial architecture model with evidence linked to the source revision, and preserve unknowns. Validate the model and build an HTML diagram in a separate output directory.
The installed guide is at $(npm root -g)/@felixfelicis/waxwing/AGENT_GUIDE.md on macOS/Linux.
Use the guide from your installed version. It contains complete authoring examples and commands. You choose the
agent; Waxwing's layout and rendering do not call an LLM. There is no built-in
repository crawler or ingest command.
Build the model your agent produces:
waxwing build /path/to/model.json /path/to/outputOpen output/diagram.html. It contains the diagram, its inspector, registered
Markdown documents, and the source model. Share that HTML file as an attachment,
or use build-site to generate linked pages for static hosting.
What you can inspect
- Architecture and subgraphs: move between an overview and selected internals.
- Workflows and sequences: follow explicit ordering, replies, loops, and alternatives.
- Evidence and uncertainty: inspect why a claim exists and what remains unknown or disputed.
- Linked Markdown: navigate between explanations and specific diagram records.
- Recoverable source: extract the complete embedded model from supported exports.
waxwing recover /path/to/diagram.html /path/to/recovered-model.jsonRecovery preserves the parsed source model; it does not authenticate the original claims or certify that an exported drawing has not been altered.
Documentation and development
- Feature walkthroughs and CLI examples
- Agent authoring guide
- JavaScript module API
- Publishing multi-page exports
- Release notes and migration guidance
- Roadmap and contribution guide
From a source checkout:
git clone https://github.com/pavelnedved/waxwing.git
cd waxwing
npm ci
npm test
npm run test:packagetest:package installs a packed archive in a temporary directory and exercises
its CLI, module imports, and source recovery. It needs npm registry access.
No visual editing, automatic factual repair, or live infrastructure discovery is implemented. Difficult layouts can fail validation; see the current boundaries.
