01
Ask about any part of the codebase
Type a topic, like “How a like toggle works end to end,” and Panolayer writes a document from the architecture: the components, routes and functions involved, in the order a request moves through them.
Panolayer Studio · Living Documents
Docs you can check against the code.
Ask about any part of your codebase and Panolayer writes a document from the architecture it parsed, with its claims linked to the files and functions they describe. When the code changes, regenerate it in one click.
macOS 15 on Apple silicon · Free to start · No credit card required
The docs were right the day someone wrote them.
Then an agent refactored the like handler, renamed two files and changed what the route returns. Nobody updated the docs, because nobody noticed they’d gone stale. The next agent read them anyway.
How it works
From a question to a document you can check
02
Claims linked to the source
File and symbol names in the document link to the code they describe, and every document shows how many of its claims are linked, like “22 claims linked to source.” If a sentence looks wrong, you can check it against the code.
03
Your rules, next to the code they protect
Where a Guardian rule governs the code, the document quotes it, like “likes are tracked per viewer.” Anyone reading, person or agent, sees the constraint next to the code it covers.
04
Regenerate when the code changes
One click rebuilds a document from the current code, and its version number goes up, so you can tell a fresh document from an old one.
05
Keep the docs you already have
Panolayer finds the Markdown already in your repository, like README.md, AGENTS.md and everything under docs/, and lists it next to the documents it wrote, grouped by folder.
FAQ
Questions
Something else? Contact us and we’ll answer.
How is a living document different from a README?
A README is written once and drifts. A living document is written from the architecture Panolayer parsed from your code, links its claims to the source, and can be regenerated whenever the code changes.
Is it written by a model?
Yes. A model writes the prose, working from the structure Panolayer parsed from your source. That’s why the claims link back to the code: you can check any of them against what it describes.
What can I ask for?
Anything about the codebase: how a feature works end to end, the main features of the project, how the architecture fits together. Documents are tagged by area, like Architecture, API and Components.
How many can I make?
Free includes 2 living documents. Pro includes unlimited living documents, and sharing. See pricing.
Docs you can check against the code.
Free to start · No credit card required