RM-010 · Ownership

Handoffs between functions with nobody named

19 of 25 handoffs — 76% of the population. Every cross-flow handoff carries an owning party. A handoff with that field empty belongs to neither side. This needs a commitment, not a feature.

Back to the register

Outstanding

handoffs of 25

State

Nothing has been done

No handoff has been given an owner since the register opened.

Who closes it

A commitment

This needs a commitment, not a feature

First seen

2026-08-17

These records carry no timestamp of their own, so the first observation is the day the register opened.

Platform date

2026-09-16

30 days away, and nobody has agreed to it

Where this entry came from

The query, run against the platform's own records

Every cross-flow handoff carries an owning party. A handoff with that field empty belongs to neither side.

These records carry no timestamp of their own, so the first observation is the day the register opened.

The records this counts

Who carries it

Taken from the records, never assigned

Nobody is named

By definition. These are the handoffs with no owner recorded, so there is nobody to name here either.

Thirty days from the first observation. The platform set this date; nobody has agreed to it.

What it would take to close this

2 steps, none of them blocked

1Put the priced gap in front of both function leadersHours

The platform already measures the wait, the rework and the re-entry cost on each handoff. It can put the same number in front of both sides.

The platform · The measurement already exists.

2Agree which function owns the gapOpen ended

A handoff with no owner is not a missing field. It is two functions that have never settled which of them carries the space between them.

Nobody is named on these handoffs · A negotiation, and it is the only step that matters.

1 step waits on somebody outside this platform. The same question across the whole register

Everything recorded against it

Each line is a record, not a note

The platform saw it2026-08-17

The platform · counted 19

Every cross-flow handoff carries an owning party. A handoff with that field empty belongs to neither side.

An owner was taken from the records2026-08-17

The platform

No owner could be taken from the records. By definition. These are the handoffs with no owner recorded, so there is nobody to name here either.

A date was set by the platform2026-08-17

The platform

Thirty days from the first observation, applied to every entry in the register without exception. Nobody has agreed to this date.

Measured again2026-08-17

The platform · counted 19

No handoff has been given an owner since the register opened.

Every line above was written by the platform. Nobody has touched this entry.

What it is tangled with

Dependencies taken from the steps, not asserted

Waits on

No other entry. Its first step can start today.

Holds up

No other entry is waiting on this one.

Alongside it in Ownership

This is the only entry in its register.

Nobody agreed to this date

Every date on this page came from the same rule: thirty days from the first time the platform could see the gap. The platform set it. Nobody has agreed to any of them, no counterparty has been told, and none of them is a commitment. They are here so that an entry cannot sit without a clock against it, and they should be replaced by real dates the moment somebody accepts one.