Scope and boundaries
D2.7 proposes a lean, reusable foundation, with the operational platform on a separate development and maintenance track.
| Area | Proposed framework scope | Separate implementation track |
|---|---|---|
| Methodology | Configuration, entity context, fact intake, qualification, decisions and lifecycle | Working applications, user experience, workflow execution and deployment |
| Architecture | Component boundaries, responsibilities, interactions and interface contracts | Operational services, storage, reasoning engines and integrations |
| Taxonomy | Shared concepts, Incident Facts, Impact Facts, relationships and generic mappings | Detailed extensions, classifications and authority-specific reporting fields |
| Specifications | Generic models, decision models and reporting package specifications | Detailed legal requirements, thresholds, executable rules and national packages |
| Practical assets | Illustrative examples, templates, schemas, validation tests and selected reusable code | Production configurations, connectors, releases and regulatory maintenance |
Outside the core does not mean closed source. Separate publication of detailed regulatory or platform-specific material remains possible. The proposal calls for disclaimers on framework-specific and other changing content, supported by clear source and version information.
See source traceability and the reporting package template.