okhp3-mermaid-data

Topics in the source

• okhp3-mermaid-data
• ER Diagrams
• Class Diagrams
• Schema Documentation Patterns
• Execution contract
• Cardinality Conventions
• Scope
• Validation

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Data modeling vocabulary, loaded after okhp3-mermaid-core. Entity-relationship modeling with cardinality notation. See references/erd-syntax.md for entity/attribute syntax and cardinality conventions (one-to-one, one-to-many, many-to-many - exact notation and when PK/FK annotations are included vs. omitted for Executive/Analyst audiences). Object structure, relationships, methods. See references/class-diagram-syntax.md. Distinguish an existing schema from a proposed model. Preserve source names and stated cardinality. Label inferred keys, constraints, and attributes as assumptions. Validate relationship direction, optionality, and duplication before delivery. Never invent columns or identifiers to fill missing source information. When a diagram is documenting an existing schema (vs. designing a new one), see references/schema-documentation-patterns.md for how much of the real schema to surface at each audience tier - Technical gets full field lists and types, Analyst gets entity names and relationships only, Executive rarely needs this diagram type at all (flag if an Executive-tier ER diagram is requested; it may be the wrong t

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