Evidence
Sources, observations, requirements, tests and decisions enter with provenance.
ORANGE PEEL IT
APEX
APEX turns evidence into governed knowledge that can be trusted, challenged and reused.
APEX keeps evidence, provenance, decisions and confidence connected so that people and applications work from the same governed knowledge.
THE PROBLEM
Information is easy to collect. Knowing what to trust is harder.
Most organisations have plenty of information. The harder problem is knowing what is true, what is current, what conflicts, and what can safely be acted on.
APEX does not tidy away inconvenient evidence.
Conflicting or incomplete evidence is preserved rather than hidden. APEX records uncertainty instead of inventing certainty.
One governed source. Many useful views.
Applications consume projections of governed knowledge. The projection can change; the governed evidence and decisions remain authoritative.
HOW IT WORKS
From evidence to something useful.
Govern
Claims are qualified. Uncertainty and contradictions remain visible.
Connect
Semantic relationships turn isolated records into governed knowledge.
Project
Applications receive the view they need without creating another source of truth.
OPUS + APEX
Method above. Governed knowledge underneath.
OPUS is the operating method: Objective, Reasoning, Decision, Execution and Evidence. APEX provides the governed knowledge model underneath it.
PRINCIPLES
APEX is designed to show its workings.
Evidence before assertion
Claims should not outrun their evidence.
Provenance before confidence
Confidence means little if nobody can see where it came from.
Preserve uncertainty
Unknown is a valid state. It is better than invented certainty.
Preserve contradictions
Conflicting evidence remains available for examination.
No shadow truth
Applications consume Core; they do not quietly become another authority.
Generated artefacts are projections
Documents and sites can be regenerated from governed knowledge.
Material claims remain traceable through requirements, decisions, tests, evidence and governed transactions.
WHAT IT POWERS
Core knowledge becomes useful through applications.
Application
Workbench
Workbench turns governed project knowledge into briefs, requirements, architecture, tests, decisions and traceability.
Utility
Catalogue
Catalogue projects the products, capabilities, dependencies, maturity and evidence already held in Core.
Utility
Graph
Graph makes the evidence chain inspectable rather than asking users to trust an answer blindly.
WHAT IS PROVEN
A baseline we can reproduce.
The current OrangePeelIT Kernel reconstructs deterministically from its retained seed and generic APEX engine. Replaying the same governed transactions inserts nothing new.
APEX distinguishes what has been proven from what remains partial, unknown or unproven.
- Governed records
- 221
- Transactions
- 9
- Graph nodes
- 221
- Reference arcs
- 532
- Replay insertions
- 0
Architecture and traceability
Core stores governed transactions and materialises semantic state. Applications do not create a second authoritative truth.
Material claims remain traceable through requirements, decisions, tests, evidence and governed transactions.
Standards
Standards are applied where they are useful and evidenced. Alignment, validation, conformance and certification are treated as different claims.
Current limitations
APEX distinguishes what has been proven from what remains partial, unknown or unproven.