conceptual-model

A conceptual model defines your system's core entities, attributes, relationships, and business rules. You need it during early requirements gathering to establish a shared vocabulary and concrete blueprint before proceeding to database or API design.

To generate conceptual model documentation, provide user stories or an existing model as input. The system extracts core entities and relationships, then produces a v2.0.0 JSON artifact containing domain rules, data flows, and glossary metadata.

Yes, you can use a conceptual model to align stakeholders before database design. It captures domain rules, data flows, and glossary terms to create a shared vocabulary, ensuring all teams understand the core entities and business rules.

The best way to structure entities and relationships is to define core nouns with explicit foreign keys and cardinality. This approach captures domain rules and data flows, generating a unified model that guides architecture, database design, and API contracts.

Yes, the conceptual model generator outputs a v2.0.0 compatible JSON file. Running the v2 generator on your existing conceptual model produces a structured artifact in your docs directory containing entities, relationships, and glossary metadata.

A conceptual model does not directly define API contracts. It serves as an early planning blueprint that captures business rules and data flows; you must perform further downstream design work to translate the conceptual entities into actual API specifications.