OPS · assisted by NUMA → CORE → MY-HOUSE10

Rent it. Lend it. Book it. Keep ownership clear.

The visitor starts in MY-HOUSE. Beneath that experience, OPS guides the interaction with NUMA as its AI capability, while CORE carries the relevant service, rental, loan or payment consequence.

SCROLL TO MOVE THE CONSEQUENCE ↓

10House context

House context

The resident starts in MY-HOUSE. NUMA and OPS guide the experience while relevant shared rights and transactions gain a CORE consequence.

INTERACTION→CORE CONSEQUENCE→EVIDENCE

Rent & reserve

Room, facility or object availability, booking, payment, deposit and return conditions stay aligned for owner and renter.

INTERACTION→CORE CONSEQUENCE→EVIDENCE

A real situation, end to end · HOME-02

From radiator failure to a calm, accountable repair.

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.