Cr_oss — The Atlas
Cr_oss's docs bound to its code: the README and the code-verified architecture analysis, drift-checked against the tree.
Journeys
What Cr_oss is and how it's shaped
A first pass for someone new to the repo: the product, then the code-verified topology and source layout.
4 stops →Following a redline through the engine
The path a draft takes from baseline-plus-current text to email-safe redline HTML — the doc section first, then the modules that do the work.
4 stops →Getting Started
The product front door. What Cr_oss is — a privacy-first Outlook compose add-in for Word-style track changes, with no backend, login, or analytics — its two workflows (draft redline and live editor), and how to sideload the manifest or run it locally.
- Cr_oss — Track Changes for Outlook You want to know what Cr_oss does or how to install and run it — start here, before the architecture analysis.
Architecture
The code-verified account of how Cr_oss actually fits together: the serverless task-pane topology, the src/ layout (a 16-module redline engine and a 7-module Office.js wrapper layer), both workflows traced through their hooks, and the adaptive diff → block-align → format-preserving render pipeline. Every claim cites the file behind it, and the Atlas drift-checks the measured numbers against the tree.
- Cr_oss — Architecture & Technology Analysis You're about to change the redline engine, the Office.js layer, or either workflow and need the real, code-backed mental model rather than the README sketch.
Docs Tooling
The documentation islands built around this repo plus the Atlas's own build log: the static Repository Explorer and the Skills & Prompts Explorer, indexed here search-only — open each island's own site for the full experience.
- Authoring spec — curated explorer data fragments
- Cr_oss Repository Explorer
- Cr_oss Skills & Prompts Explorer
- Documentation Build Log You're re-running or updating the Atlas and want to know which commit the current curation reflects, or what changed in the last doc build.