A fragmented working view
People move between specialised tools without a clear picture of what each system does or who is responsible for it.
OCHRE · ALIGN
For organisations coordinating specialised systems and the teams responsible for them
Independent systems. A coherent way to work across them.
OCHRE is a federated shell: a shared place to see and reach independent systems. It is designed to make their identity, status and handoffs understandable while each system retains its own ownership, access rules and operating boundaries.
The problem
Working together should not make system boundaries disappear.
Status without enough context
A system can appear connected even when its current condition is unknown or the information shown is out of date.
Unclear handoffs
A transition between tools can obscure its destination, the information involved and the access rules that apply.
What it does
What you get.
Make the connection between systems useful while keeping their individual responsibilities visible.
Give systems a shared frame
- Present agreed member systems with a clear identity and purpose.
- Make ownership and the appropriate destination understandable.
- Provide a coherent way to navigate without disguising the differences between systems.
Keep status meaningful
- Distinguish a configured connection from a checked operational state.
- Show the basis and recency of available status information.
- Make unknown or unavailable conditions clear rather than implying readiness.
Make handoffs deliberate
- Identify the target, purpose and scope of a proposed transition.
- Respect each member system's own access and operating rules.
- Keep responsibility for any agreed exchange or launch explicit.
Why this matters
Organisations need specialised systems to remain useful together without losing sight of their differences. A coherent view can support coordination only when identity, status and responsibility remain clear. OCHRE is designed around that balance between connection and independence.
How the record works
Keep the basis for a decision in view.
Which system is this?
Make the member's identity, purpose and responsible owner clear.
What is known about its state?
Keep the check or source behind the status available for review.
Where does the handoff lead?
Identify the destination and the scope of the proposed transition.
Which boundary still applies?
Retain the member's access rules and responsibility in the shared view.
Who uses it
The same record, seen from every chair.
Operators
Understand where to work and what is known about each system before moving between them.
System owners
Keep the identity, responsibilities and operating boundaries of their systems clear.
IT and integration teams
Evaluate connections and handoffs without assuming a merged architecture.
Evaluation
Start with a focused workflow.
Select the systems and a handoff worth evaluating. Agree their owners, status sources and boundaries before defining how they should appear and work together.
Agree the scope
- Member identities, ownership and access requirements
- Status sources and the treatment of unknown conditions
- A defined handoff with explicit destination and permissions
Questions to evaluate together
- Can people distinguish each system's role and responsibility?
- Does displayed status make its basis and limits clear?
- Is the scope of a handoff understandable before it occurs?
Evidence for the questions that matter.
Evaluate the relevant product and conditions. Request scoped evidence for access, provenance, recovery, human review and offboarding before agreeing a pilot.
- Who can access the information?
- Ask for the product's access boundaries and applicable isolation tests.
- Where does the information come from?
- Agree the sources and inspect a representative source-to-record example.
- What happens when something fails?
- Agree operational ownership and request relevant monitoring and recovery evidence.
- What can we review and take with us?
- Confirm review history, retention, export formats and offboarding within the agreed scope.
For investors and partners
Connection without assumed consolidation.
OCHRE gives the portfolio a clear connective role while respecting the independence of its products. For investors and partners, the proposition is a practical approach to working across specialised systems, with integration scope made explicit. It creates a basis for evaluating useful connections without claiming that the portfolio already shares infrastructure or supports every integration.
Identity
OCHRE carries the Optimized Core emphasis on explicit context and accountability across system boundaries. It provides a connective frame while keeping the autonomy of each participating system in view.
connect → check → navigate → hand offConnection with clear boundaries.
Explore connection with clear boundaries.
Describe your team and the workflow you want to evaluate, with an anonymised example if you like. We discuss scope, connections and readiness before any data is shared.
JPH van Mastrigt · Founder & Technical Director
