okhp3-database-cartographer

Topics in the source

• okhp3-database-cartographer
• Scope
• Architecture: two jobs, two tools, one handoff
• Step 1 -- Interrogate
• Step 2 -- Diff against the locked spec
• Step 3 -- Diagram
• Security and safety
• Output

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Interrogates a live database of largely unknown or partially-documented structure and turns it into two things: a schema inventory with severity-classified findings against whatever spec you point it at, and a Mermaid ER diagram. It does the surveying and the cartography does not happen in the same tool -- interrogation and diagramming are deliberately decoupled (see "Architecture" below), because the best tool for connecting to a database and the best tool for drawing a diagram are never the same tool. | In scope | Out of scope | |---|---| | Reflecting live structure from Postgres, MySQL/MariaDB, MSSQL, SQLite, Oracle | Data quality / row-level profiling | | Reflecting MS Access (.accdb/.mdb), flagged as the fragile path | Migration script generation | | Diffing live structure against a locked spec, P1/P2/P3 findings | Firestore/NoSQL (deferred to a future version) | | Generating a Mermaid ER diagram from the reflected schema | Writing to or modifying the target database | If the task is "does this database's structure match what we documented" or "what does this database actually look like," this is the right skill. If the ta

This is an excerpt. Refer to the complete source and its current requirements.