# Anatomy · Reading

> The anatomy page publishes the client source of this site as it is on disk, parsed on every build, with every folder and file, its statistics, its syntax tree, its definitions and their calls, and the problems the parser found.

Canonical: https://banes-lab.com/anatomy
Page as Markdown: https://banes-lab.com/anatomy.md
Page as JSON: https://banes-lab.com/json/anatomy
This index as JSON: https://banes-lab.com/json/api/pages/anatomy/reading

## Entries

- [This page is derived](https://banes-lab.com/anatomy/reading/this-page-is-derived.md): This section covers what the rest of the page is made of.
- [The four parts, measured](https://banes-lab.com/anatomy/reading/the-four-parts-measured.md): The four parts named in a system is a graph on the architecture page are each measured here.
- [Containers on the spine](https://banes-lab.com/anatomy/reading/containers-on-the-spine.md): Every file on the tree tab carries its subject, its concern and, where the name declares one, its variant, read off the file name as described in placement is a…
- [What the diagnoses found](https://banes-lab.com/anatomy/reading/what-the-diagnoses-found.md): The diagnoses are the schema applied to the graph, and they look for a call cycle, a definition nothing consumes, a definition declared twice, a file that…
- [Reading a walk](https://banes-lab.com/anatomy/reading/reading-a-walk.md): A walk lays every meaningful syntax node of a file on a hexagonal grid in the order the parser met them, so a file is a path the eye can follow, going down when…