RonanRx · Card-backed system registry
Two connected maps. Five working documents.
The system map includes approved product direction through 2026-07-30. Implementation evidence is reconciled through 2026-07-30. Five companion documents separate binding product intent from implementation evidence: business.md in plain English, technical.md down to tables and schedules, as-built.md for what exists now, database.md's full census, and glossary.md's canonical names. Open items stay attached to the cards they affect.
Primary product map · generated from the registry
The RonanRx system map.
All 55 cards share one canonical registry: 49 appear in the default map, three appear in focused views, and three remain explicit scope boundaries. Open any node or connection to inspect its contract, workflow, rules, technical mechanism, and as-built evidence.
55 cards Open Machina
Explore the Doctor, Patient, and AI Agents + Data lanes. Select any node to open its in-place detail panel and continue into the full specification.
Open interactive map →source Canonical registry
Inspect the node, edge, workflow, and semantic-view contracts that generate Machina and the engineering diagram.
View registry JSON →Engineering view · system relationships
Engineering view: four tracks, current vs target.
This view traces patient, provider, agent, iOS, and operations relationships. Dotted edges distinguish target or cross-track behavior, and every §-stage opens business and technical details. Drag to pan, scroll to zoom, and select a §-node.
The working documents
If it's not in here, why do we have it?
All five documents cover ronanrx-core and RonanRX iOS.
Binding rules, technical design, implementation evidence, database
structure, and canonical names each have a distinct home.
business.md Plain-English requirements
Binding product rules and the approved target for every feature, including explicit gaps and card-level open items.
Read rendered →technical.md Strict technical spec
Tables and fields, code paths, integrations and env flags, cron schedules, unwired/legacy review holds, and evidence-gated schema review: what drift tooling should compare against.
Read rendered →database.md Database census
Frozen field census: 177 tables and 2,238 columns at historical staging f246ed27 on 2026-07-17. Current main and staging each contain 168 Rails public tables; the document labels the drift and keeps review-hold entries visible.
Read rendered →glossary.md Naming registry
One canonical name per concept, every alias mapped, banned terms flagged: the jargon register that keeps humans and coding agents aligned.
Read rendered →as-built.md Implementation evidence
What exists now, with evidence and implementation gaps kept separate from the binding Rules and Target contract.
Read rendered →.md Raw markdown
Download the generated and companion source files. Card-level open items remain explicit in the applicable documents.
business.md → technical.md → database.md → glossary.md → as-built.md →