CURRENT IMPLEMENTATION · PARTIAL MODEL
Waxwing, explained by Waxwing
How does Waxwing turn a source model into an inspectable artifact?
A curated model of real source code, not automatic discovery or a complete call graph.
Graphs
Waxwing: from model to artifactWhich responsibilities turn source models into inspectable exports?Inside architecture layoutWhere are model meaning and generated geometry checked?Workflows
A successful architecture buildIn what order does the CLI prepare the three export contents?Documents
Read this exampleMarkdown documentModel scope
- timeframe
- current
- environment
- Waxwing Node.js implementation; static source inspection
- snapshot
- 00f30217513433cbb1fb83318ed469e19f890621
- coverage
- partial
- question
- How does Waxwing turn a source model into an inspectable artifact?
- includes
- Architecture-model path and selected direct function calls.
- excludes
- Sequence dispatch, workflow layout internals, all validation branches, performance measurements, and filesystem failure recovery.
- abstraction
- A curated model of real source code, not automatic discovery or a complete call graph.
Navigation categories organize this export; they do not add architectural relationships.