v0.6 First proof of concept demonstrated

OPUS → APEX · RESEARCH IN ACTION

Transformation should be continuously justified. Not just continuously delivered.

OPUS is Orange Peel's research-led operating system for organisational reasoning. APEX is the product that applies it—qualifying evidence, connecting it through an ontology and helping accountable people make better decisions.

Research-led. Evidence-based. Designed to strengthen—not replace—human judgement.

Most organisations measure whether transformation is being delivered.

APEX asks whether it remains worth delivering—and what the evidence really supports.

THE PROBLEM

Delivery can remain busy, governed and apparently on plan—while quietly losing its purpose.

Programmes begin with a business case, expected benefits and a set of assumptions. Then the organisation changes. Leadership, markets, regulation, technology, actors and priorities move on. The programme often continues.

Traditional governance is good at recording activity and approving change. It is much less effective at reasoning across those changes and asking whether the investment still makes sense.

A green status does not prove that a programme is on track. It proves that someone recorded it as green.

APEX is being researched to connect the original purpose, today's evidence and the decision now required.

STRATEGIC DRIFT

Original intent What the organisation chose to achieve
Current delivery What the programme is now building
Current need What matters to the organisation today

The programme succeeds. The transformation fails.

ILLUSTRATIVE FUTURE CASE · NOT A RESULT FROM THE CURRENT POC

“Should we approve this change?”

A conventional pack might show twelve approved change requests. APEX should be able to explain that the proposed change would move delivery 72% away from the trajectory that supported the original benefits case—and show what changed, why it matters and who must decide.

FROM THEORY TO PRODUCT

OPUS establishes how organisations should reason. APEX makes that reasoning usable.

They are related, but they are not the same thing.

THE OPERATING SYSTEM

OPUS

The research framework: principles, ontology, evidence discipline, competency questions and rules for reasoning across purpose, delivery, authority and outcomes.

  • Defines the concepts and relationships
  • Preserves provenance, time and authority
  • Tests how good decisions should be supported
  • Evolves through controlled research and case studies

THE PRODUCT

APEX

The practical experience: an Actor asks a difficult question; APEX qualifies the context, reasons across the organisation's evidence and produces an explainable decision brief.

  • Qualifies and connects organisational evidence
  • Finds contradictions, gaps and strategic drift
  • Asks clarifying questions before answering
  • Supports the authorised person who must decide
01TheoryA practical theory of organisational knowledge and reasoning
02OntologyA stable semantic model for organisational reality
03ArchitectureA controlled implementation and decision framework
04ProofNorthstar demonstrates an executable, inspectable result
05Case libraryFurther questions test and extend the theory

THE RESEARCH BASELINE

The theory has been challenged before the product is allowed to make a claim.

The ontology has been tested across delivery, commercial, operational, regulatory and evidential scenarios. The same semantic core remained sufficient.

17stable core concepts
33controlled scenarios
315accepted design decisions
782unique competency questions
0new core abstractions required
Who and where

Actor · Role · Authority · Context

Why and what is owed

Purpose · Commitment · Rule

What happens

Work · Event · Decision · Artefact

What is true and what results

Condition · State · Outcome · Measure · Assertion · Evidence

FROM QUESTION TO DECISION BRIEF

APEX should ask before it answers.

A useful answer depends on context. Which decision? At what point in time? Against which baseline? Which evidence is current? Who has authority? What business outcome could be affected?

THE QUESTION

An authorised Actor asks APEX a decision question.

The conversational interface is the front door—not the intelligence itself. APEX first identifies the Actor, decision, context and point in time.

Which release? Which decision date? What evidence is current? Who holds authority?

THE ORGANISATION'S IQ

Not another score. A qualified, connected and time-aware body of knowledge.

Traditional tools retain fragments. APEX qualifies each source, maps it to a shared meaning and reasons over the relationships.

Intent

Why are we doing this?

Business case, purpose, benefits plan, outcome measures and strategic assumptions.

Obligation

What have we committed to?

Contracts, statements of work, acceptance criteria, commitments and authorised changes.

Delivery

What is actually happening?

Plans, work, milestones, dependencies, RAID records, defects and decisions.

Assurance

What does the evidence support?

Testing, rollback, operational acceptance, independent assurance and customer impact.

Authority

Who may decide?

Actors, roles, delegations, quorum, thresholds and time-valid approvals.

Reality

What matters now?

Current organisational need, changed benefits, operational capacity and emerging outcomes.

Before ingestion, every source is qualified. IdentityOwnerVersionEffective timeStatusProvenanceConfidence

ASK APEX

The questions become the case-study library.

Each case begins with an Actor who has a real decision to make. Every new proof adds to the site rather than replacing the story.

Loading case studies…

CASE STUDY

Select a question

The selected case study will appear here.

CASE STUDY 01 · DEMONSTRATED

Should Northstar Release R12 go live?

Northstar Platform Renewal is a controlled fictional programme at Meridian Financial Services plc. Release R12 changes customer servicing, payment resilience, operational monitoring, vulnerable-customer support and rollback capability.

APEX ASSESSMENT Conditionally Ready Unconditional approval is not supported by the current evidence.
CustomerMeridian Financial Services plc

Regulated service owner and final customer authority.

Prime supplierNorthstar Digital Delivery Ltd

Responsible for delivery of Release R12.

OperationsHarbour Platform Operations Ltd

Managed service and operational readiness.

Independent assuranceVerity Assurance Partners LLP

Independent test and assurance challenge.

THE QUIETEST VOICE

Technical progress was visible. Downstream business readiness was less certain.

The change could affect call volume, handling time, complaints, backlogs, vulnerable customers and operational capacity. The current POC did not measure those effects; it established that they required evidence and accountable business consideration. The Operations Representative was absent from the release decision and the operational checklist remained unsigned.

14controlled sources mapped
36source-to-ontology mappings
25/25delivery questions answered
10/10seeded contradictions detected
10readiness rules executed
0graph-validation violations

NINE RULES REQUIRE ACTION

Evidence incomplete

Two mandatory tests, production-like rollback rehearsal and verified deployment credentials.

Business and governance incomplete

Operational risk acceptance, Release Board quorum and a completed operational acceptance checklist.

The decision pack is not current

CCN-012 is missing from the gate baseline, assurance used an older pack and the earlier approval expired when the date changed.

Boundary: Northstar is a controlled synthetic proof of concept. APEX has not approved the release; it has established why unconditional approval is unsupported, what must change and which human roles must decide.

THE ENDURING PRODUCT STORY

Northstar proves one question. APEX is being built to support many.

01

Delivery intelligence

Tests whether reported progress is supported by commitments, dependencies, evidence and causal relationships.

02

Benefits intelligence

Tracks whether the outcomes that justified the investment remain relevant, achievable and measurable.

03

Strategic drift

Compares original intent, approved change, current delivery and today's business need.

04

Explainable reasoning

Every conclusion shows evidence, contradiction, uncertainty, action and human authority.

SHAPE A CASE STUDY

Bring a difficult decision—not a polished brief.

This guided interview is an early prototype of how APEX could ask qualifying questions. Your answers remain in your browser unless you choose to create an email.

ActorDecisionPurposeChangeEvidenceQuiet voiceAPEX output
Question 1 of 7
Who is the Actor asking APEX?

Use a role rather than a name—for example Sponsor, Programme Director or Customer Release Authority.

THE ROADMAP

Every new case study should test the theory and add evidence to the product story.

The microsite will grow cumulatively: more Actors, more questions, more evidence patterns and more demonstrated outcomes.

CompleteOPUS theory, ontology research and use-case catalogue
CompleteImplementation architecture, ADRs and machine-readable ontology
DemonstratedCase Study 01 — Should Northstar Release R12 go live?
v0.6OPUS-to-APEX story, case-study library and decision-brief demonstration
PlannedBenefits and strategic-drift case studies, including change-trajectory reasoning
ResearchingConversational and voice interface with qualifying questions
FutureControlled live pilots and production productisation

THE ORANGE PEEL PRINCIPLE

Every significant decision should remain continuously justified.

APEX does not make the decision. It makes it harder to make the decision without understanding the evidence.

OPUS · APEX · ORANGE PEEL IT SERVICES

Bring us a difficult organisational decision worth testing.

APEX is an Orange Peel research and development initiative. We are looking for controlled opportunities to challenge the theory, form new case studies and learn what decision-makers genuinely need.

Start a conversation