From README to architecture: reading a connected project
Explore an original fictional project through its specification, architecture, plan and decision log.
Read the articleTHE READING SIDE
Reading projects, reviewing agent documents, and keeping context. Practical examples and reference files from the people building Aero Markdown.
FEATURED STORY · 4 MIN READ
Explore an original fictional project through its specification, architecture, plan and decision log.
Read the storyA FEW THINGS TO READ
A closer look at the files and ideas around the reader.
Explore an original fictional project through its specification, architecture, plan and decision log.
Read the articleAn original synthetic document for checking tables, code, Mermaid, math, local images and relative links. A reference, not a ranking.
Read the articleA practical reading workflow for local plans, reports, and READMEs, with a clear distinction between reloading a file and opening a new one.
Read the articleLocal files, relative links, and a document that stays available on your Mac.
Read the articleChoose a source view for changing Markdown and a rendered page for reading it. A practical distinction for READMEs, reports, and linked documentation.
Read the articleMove one documentation folder, then one file, and see which relative Markdown links and images break. A small, reproducible file-path experiment.
Read the articleDesign a Markdown documentation folder that still works when moved or shared: a root entry page, relative links, local assets and a simple manifest.
Read the articleA before-and-after example of an AI agent implementation report rewritten so a human can review it: summary, changes, evidence and open risks.
Read the articleA reproducible protocol for opening, searching and navigating a very long Markdown file, so a reader comparison measures behaviour instead of guessing speed.
Read the articleA checklist for reviewing an AI implementation plan before you approve it, applied to two fictional plan versions with different scope and risks.
Read the articleWhen code changes but the Markdown still describes yesterday: a fictional example of documentation drift and a review path back to the source code.
Read the articleA consent-aware protocol and sample package for testing whether someone can follow a Markdown specification handoff. No participant results are claimed.
Read the articleHow Aero Markdown is designed to render Markdown offline: bundled highlighting, Mermaid and KaTeX, local files only, and where the browser tool differs.
Read the article