Engineering Manual | CORals OIP
Platform documentation
Engineering Manual
The governing guide for building CORals OIP as a transparent, evidence-driven organisational intelligence platform.
Version 1.0Printable reference
CORals OIP is built to turn heterogeneous organisational information into traceable knowledge, analytical evidence and human-centred decision support.
Engineering intent
Decisions before dashboards
Interfaces and visualisations exist to improve organisational decisions—not to display data for its own sake.
Evidence before intuition
Recommendations and explanations must be grounded in measurable evidence, documented assumptions and uncertainty.
Explainability before complexity
A simpler transparent solution is preferred unless additional complexity creates clear value.
Platform design
The platform is domain-oriented. Repositories own persistence; services own business capability; analytics consumes established business objects; applications consume services rather than tables.
| Layer | Responsibility |
|---|---|
| Knowledge & semantic layers | Stable concepts, evidence, relationships and business meaning. |
| Indicators, benchmarks & features | Canonical organisational measures, expected values and reusable analytical variables. |
| Statistics, prediction & causality | Evidence, forecasts and intervention effects—kept explicitly distinct. |
| Decision intelligence & advisor | Transparent alternatives and cited answers; people retain responsibility for decisions. |
Non-negotiable: preserve lineage. Data version, feature version, model version and timestamp must be available wherever they materially affect an output.
Working practice
- Use small, well-specified stories with acceptance criteria.
- Record long-lived architectural choices as ADRs.
- Test new infrastructure and document why complex logic exists.
- Treat the repository as the permanent project memory.
CORals OIP · Chrisitan Otto Ruge · cor@corals.no · VAT nr: 925 207 802 MVA
