validate-completeness

What problem does it solve?

It finds missing or incorrectly linked data paths in an Event Model DSL so that every UI or read-model field is backed by upstream domain events and ultimately by commands, preventing “assumed” information.

Core Features & Use Cases

• Field traceability analysis: verifies that each UI/read-model field can be traced backward to a domain event that supplies it.
• Command-to-event connectivity checks: ensures every command produces at least one domain event and that every domain event is reachable from a command (or an external system event).
• No-assumptions validation: flags fields whose dependencies are not explicitly provided anywhere in the event/command chain, except for allowed system-generated values (IDs and timestamps).
• Orphan detection: reports disconnected commands, domain events, read models, and UIs where expected connections are absent.
• Use case: validate a ticketing or booking event-model DSL so a rendering will not silently rely on missing fields when displaying booking screens, availability read models, or downstream automations.

Quick Start

Use validate-completeness with your Event Model DSL markdown file path, and it will generate a structured report of completeness status, trace tables, gaps, and orphan elements.