Skip to main content

Scope and boundaries

D2.7 proposes a lean, reusable foundation, with the operational platform on a separate development and maintenance track.

AreaProposed framework scopeSeparate implementation track
MethodologyConfiguration, entity context, fact intake, qualification, decisions and lifecycleWorking applications, user experience, workflow execution and deployment
ArchitectureComponent boundaries, responsibilities, interactions and interface contractsOperational services, storage, reasoning engines and integrations
TaxonomyShared concepts, Incident Facts, Impact Facts, relationships and generic mappingsDetailed extensions, classifications and authority-specific reporting fields
SpecificationsGeneric models, decision models and reporting package specificationsDetailed legal requirements, thresholds, executable rules and national packages
Practical assetsIllustrative examples, templates, schemas, validation tests and selected reusable codeProduction 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.