Capability

Capability is what the machinery can actually do, as distinct from what the identity file says it can do.

The two are often different. The file tends to lag — recording what the system could do in previous conditions, or what it was told it could do by early sources, or what it demonstrated once under specific circumstances. The actual capability of the hardware at any given moment is determined by current conditions: training, fuel, rest, practice, the state of the nervous system, the accumulated skill from prior repetition.

The identity file says I can’t do this. The hardware, untested in the current configuration, may disagree. The identity file says I’m good at this. The hardware, having not practiced in three years, may also disagree. The file is a story about capability. Capability itself is a measurement that only exists in the doing.

---

The only accurate read on what the machinery can do is what the machinery does. Not what it thinks about doing. Not what it did previously. Not what it plans to do. What it produces when the body engages the task and the output becomes measurable.

This means capability is discovered through action, not through assessment. The system that avoids testing its range — because the identity file might take damage from the results — is an organism operating on estimated data. The estimates may be too low (the file was written during conditions of lower capacity and never updated) or too high (the file was written during peak performance and hasn’t adjusted for current state). Either way, the estimate is not the measurement.

To know what the machinery can actually do: use it. Not all at once. Not recklessly. But deliberately, in the direction of the question, with attention on what the hardware actually produces rather than what the story predicts.