Repository documentation

How this site, its 64 tools and Miraiva are built.

Architecture, product requirements, the generated catalogue and the rules for contributing — versioned with the code and readable on GitHub. Diagrams are written in Mermaid, so they render in the repository and stay editable.

64client-side tools
6tool categories
1health product (Miraiva)
0request-path servers

Start here

The README is the front door. The architecture document is the map. The PRD explains what is done and what is not.

Catalogue and product docs

The catalogue is generated from the same in-page array that renders the hub, so counts and links cannot drift.

Working on the repository

Every app is one HTML file plus a README and a ship declaration. The gate checks the couplings between an app and the rest of the site.

Document map

DocumentAudienceAnswers
README.mdEveryoneWhat is this, how do I run it, where is everything?
docs/ARCHITECTURE.mdEngineersHow does it work, where are the trust boundaries, how does it deploy?
docs/PRD.mdProduct / maintainersWho is it for, what is required, what is shipped, what is next?
docs/APP_CATALOG.mdBuyers / maintainersWhich tools exist, what is free, what does the paid pack add?
docs/product-index/Product / maintainersWhat does each product do, for whom, which epics and stories are done, partial or pending, and what needs fixing?
MIRAIVA_PRD.mdHealth product teamWhat are the health phases, gates and acceptance criteria?
BUILD_TRACKER.mdMaintainersWhat did the original 50-app programme decide, and why?
CONTRIBUTING.mdContributorsHow do I add a tool or a platform change safely?
SECURITY.mdSecurity researchersHow do I report an issue, and what is in scope?

Mermaid diagrams render directly in GitHub's file view. If you are reading the raw Markdown elsewhere, paste the diagram block into any Mermaid renderer; the source is plain text in the repository.