The case
The owner, at U22: “A CASE we explored some time ago (in part to probe notions of corporate phenomenology) that could be worth revisiting now was an engineering organization responding to a critical internal incident.” A22 found Northstar (CASE-023 and its variants CASE-002, CASE-003 and CASE-036) and proposed this variant:
“Imagine Northstar has been responding to a major failure for twelve hours. The incident commander goes off shift and transfers command to a colleague. The original commander no longer directs the response. The new commander inherits the current incident state, ongoing obligations, outstanding hypotheses, and authority to coordinate the teams. The incident continues without any significant disruption.”
Under the Incident Command System such transfers are routine and formalized (LIT-1365).
What it shows
A22: “The handoff illustrates continuity of organization without establishing continuity of experience.” If one asked where the response’s point of view is, the commander is the tempting answer, and the handoff defeats it: “Did the supposed corporate experience transfer from one human being to another? That seems like an implausible conclusion from the operational facts alone.” It also argues “against identifying the organizational perspective with whichever employee happens to hold the most comprehensive report”.
So the response’s organization persists through a change of every person in its central role, as CLAIM-329’s collectives persist through a change of members. The representation of one continuous commander, which reports and logs may carry, is a represented owner (CLAIM-355) in the small.
What it does not show
- That the response is a further agent. A37 withdrew the exchange’s “temporarily constituted collective agent”.
- Anything about experience. The case shows only that no person is continuous; it neither locates nor rules out experience elsewhere (QUESTION-009, Deferred).
Note of 2026-10-22: what NIMS asks of a handoff
The stipulated handoff can be set against the documented doctrine: “When command transfers, the transfer process includes a briefing that captures essential information for continuing safe and effective operations, and notifying all personnel involved in the incident” (LIT-1365, p. 22). The doctrine fixes what is transferred as information and notification; what the case adds is that a briefing transfers the record of an arrangement, not the capacity the outgoing commander had built.
Note of 2026-10-26: records preserved or erased at the handoff (reported)
T20 of the exchange “Experimental Infrastructure Review” reports running this case’s handoff in a simulation (CASE-166): “An incident commander can transfer their role to another employee while preserving—or losing—the group’s records.” During a telemetry outage the records-preserved arm estimated the company’s state with an MSE of 0.00411, against 0.03398 with the records erased. But “that improvement in organizational knowledge often doesn’t change the selected action”.
That fits this case’s note of 2026-10-22: a briefing “transfers the record of an arrangement, not the capacity the outgoing commander had built”. The records carried the estimate, and what the response did hardly depended on them. T20 put it the other way round (“preserving a capacity for interpretation is not equivalent to exercising that capacity successfully”), calling the records the capacity. T18 also placed Northstar “already considered in CASE-134”; the company is CASE-023, and this is its handoff variant. Reported, not reproduced: T20’s “PerspectiveLab v2.11” is not held, and dmarx/PerspectiveLab holds no v2.10 or v2.11 (its latest import is c54617e, v2.9). The case is unchanged.