nucleation

CLAIM-296: What a system has, what it knows it has, and what it can deploy within a task's deadline are different, and the last is a relation among the resource, the agent, its environment, the task, the deadline and the cue, not a property of any one of them

3 min read

Properties12
StatusActive
Version2
Rolethesis
Warrantinterpretive
Tagsagency, cognition, embodied-cognition
Linedistributed-agency
Bears onQUESTION-101 — When does whether a resource is available for an action depend on the organization of an agent–environment system rather than on what any one member knows or can do?
GroundsTHEORY-346 — When information stays in view at a known place, people consult it less and rely on memory more as the time to reach it rises, in a graded trend across added delays from 0 to 3.2 seconds, even where the memory is weak and the display perfect; in one copying task a model that prices memory and display access in time alone, with no preference for either source, fits how many items people encode per look
ComplementsCLAIM-306 — Under a deadline, search can establish presence by finding one item but absence only by exhausting the collection, so "If I can't find it, it isn't there" acts on an unfinished search as negation as failure acts on a finished one: a default stronger than either the closed-world assumption or negation as failure, safe only when the arrangement makes the full search finish within the deadline, CLAIM-312 — "If I can't find it, it isn't there" asserts operational unavailability, that the item will not be put to use before the deadline, not absence: a search that fails by the deadline establishes unavailability outright, and licenses absence only with a certificate that the unsearched remainder cannot hold the item, from exhaustion, from an invariant of the arrangement, or from a closed-world default
Corroborated byCLAIM-310 — Sorting schemes over objects with determinate properties never conflict as descriptions, since the product of any sortings refines them all; they conflict as arrangements, since a fixed number of bins realizes one partition when each item is stored once, and which costs least depends on what is searched for and on what stands out within a bin, THEORY-351 — In a two-pilot airliner cockpit, setting the approach speeds as bugs on the airspeed indicators, prepared 25 to 30 minutes ahead in a low-workload phase from a card selected by the displayed gross weight, turns recall and scale reading at the moment of use into a judgement of spatial proximity, so the cockpit system remembers the speeds without either pilot's memory being improved; this is argued by task analysis of mandated procedure, not measured
UsesTERM-055 — operational availability, of a resource for an action: the chance that an agent–environment system, given the cue it actually has, deploys the resource for the task before the deadline
Illustrated byCASE-085 — The medication in the ambulance: a drug the EMT knew was stocked could not be found during a resuscitation, the paramedic changed the request, and afterwards said "If I can't find it, it isn't there", CASE-094 — The LEGO bin: a brick owned in one copy and buried among hundreds of similar ones may as well not be owned, a black brick among white ones needs no bin of its own, and every brick can be found by going through the whole collection

Graph View

The claim

A17 §10: “Possessing a resource, possessing information about that resource, and possessing the capability to deploy it are distinct conditions. The last is relative to a task, a deadline, and the organization of the agent–environment system.” A16: the medic’s line “is literally false as a claim about inventory, but potentially correct as an operational equivalence.”

A17 §1 separated five levels in CASE-085: physical presence (yes), knowing it is present (yes, the unit had been checked), knowing where (not quickly enough), retrieving it in time (no), and its still serving the purpose (the medic changed the request). A18 noted these “are separate predicates, not a universal logical hierarchy: an item can be deployable by a practiced procedure even if no participant can explicitly state its location.”

A19 added the cue. “You possessed the information that the medication was present, but the request did not successfully elicit the information where to find it.” That some cue retrieves an item does not mean the cue now given does (QUESTION-096).

Why it is a distributed-agency claim

A17: availability “is not an intrinsic property of the medication, nor purely a subjective property of the person searching for it. The organization of the ambulance, the distribution of knowledge among team members, the unfolding clinical event, and the time remaining all participate in determining it.” That makes the capacity to deploy a resource a candidate capacity of the organized whole (QUESTION-101). Gibson’s affordances (LIT-1065) and Hutchins’s distributed cognition (LIT-1060) are the traditions, both registered unread.

What it does not say

  • Not that existence depends on observers. A17: “practical availability depends on an organized relation between the world, the agent, and the demands of the situation.”
  • Not that the failure in CASE-085 was the EMT’s. A17 §8: the operational reading “could be used to treat a failure of the entire retrieval system as merely a failure of an individual.”
  • Not why retrieval failed in CASE-085, or why the medic changed the request.

Note of 2026-10-15: the cockpit, where arrangement alone changes capacity

Hutchins’s “How a cockpit remembers its speeds” (LIT-1066, read in NOTE-867) is the closest the record now holds to a case for this claim. “Individual pilot memory has not been enhanced; rather, the memory function has now become a property of a larger system.” The pilots are unchanged; the speed card and the bugs change which processes are assembled, so what the crew can deploy in time changes with the arrangement alone, as QUESTION-101 asks. Two limits. It is a stylized task analysis with no measurements and no failure cases, and its task is anticipated, mandated and invariant, about information and not about locating an object. And it adds a factor this claim does not list: work done before the request, by leaving the result in the environment (see the note of the same date on TERM-055).

Note of 2026-10-28: bearing on QUESTION-101

At the owner’s ruling on the fourth status review, this claim bears on QUESTION-101 and does not answer it. It separates having a resource, knowing it is had and deploying it, and makes deploying relational. That frames what “available” means. It does not say when availability is the system’s and not a member’s, for a stated class of tasks, which is what the question asks.

Backlinks