Operate in OPS
NUMA and OPS support conversation, planning, documents, tasks, decisions and daily operations in the context where the work happens.
INTERACTION→CORE CONSEQUENCE→EVIDENCE
OPS → CORE03
Daily work becomes shared consequence.
OPS prepares and performs the work. CORE receives the authorised result that other parties must be able to trust.
SCROLL TO MOVE THE CONSEQUENCE ↓
03Operate in OPS
Approve the handoff
A relevant commercial result crosses only when an entitled person or governed workflow confirms the exact scope and consequence.
INTERACTION→CORE CONSEQUENCE→EVIDENCE
A broken radiator becomes one provable service chain.
Follow one authorised result from the first signal to durable evidence.
- 01Signal
Requests a local maintenance service.
- 02OPS context
Builds the request from conversation and photos.
- 03Human authority
The home owner confirms problem, property scope, photos, access conditions and request wording before seeking service.
- 04Bounded handoff
OPS publishes only the approved service order to CORE; household conversation and unrelated home data remain private.
- 05CORE record
Publishes an approved bounded service order.
- 06Shared consequence
Provider can quote and fulfil.
- 07Durable evidence
Service evidence links request version, approved scope, provider responses, appointment, custody and repair outcome.
System boundaryOPS keeps the operational context. NUMA may assist inside that context. Only the approved, scoped and attributable result crosses into CORE.
Record in CORE
CORE validates identity, authority, contract and event order before it changes shared transaction state.
INTERACTION→CORE CONSEQUENCE→EVIDENCE
Share the receipt
Every accepted handoff returns an attributable receipt. Rejection or correction remains visible rather than disappearing into a silent sync.
INTERACTION→CORE CONSEQUENCE→EVIDENCE
Relevant viewpointsOne world.
One world.
Several authorised truths.
Open a scenario to see the operational action and ledger event.
Completes a sale in OPS Point of Sale.
Stock, payment and fulfilment move together.
SALE.CONFIRMED
Returns an earlier purchase.
Stock, tax and refund stay explainable.
RETURN.ACCEPTED
Changes a temporary store price.
Old and new sales retain their own truth.
PRICE.VERSIONED
Publishes an assortment to selected channels.
One assortment can sell without losing brand identity.
ASSORTMENT.PUBLISHED
Sells a CORE product in an owned webshop.
Stock and settlement recognise the channel sale.
CHANNEL.SALE