Functions Can Carry Metadata Too
What a missed callable-owned version field taught us about generic runtime observation.
Scope: Engineering or methodology note based on a September 17, 2026 snapshot. Source-level behavior is not a public availability or universal compatibility claim. Any scenarios are illustrative, not customer outcomes.
A library can expose a function as its public global and attach metadata to that function. An observer that records only ordinary objects can miss useful data without noticing that its model was too narrow.
Kalu’s harvested runtime-global work addresses that case. Function-valued descriptors can act as data owners, with their own identity and admitted properties, while the collector still avoids invoking the function or its accessors.
Do not confuse callable with opaque
Consider a synthetic global function with an own version field and a nested metadata object. Calling the function is unnecessary to observe those stored fields. Treating the entire callable as unreadable would discard evidence the collector can safely account for.
The current source distinguishes that useful data ownership from intrinsic function metadata and host-native callable boundaries. Those exclusions are recorded as policy, not quietly interpreted as evidence that the properties never existed.
Aliases and cycles still matter
A callable can be referenced from several places or point back into an object graph. The collector needs identity handling so an alias does not become a duplicate object and a cycle does not become an unbounded traversal.
Descriptor failures and unread regions remain visible. A healthy version field should not hide a failed neighboring observation, and a failed neighbor should not force the collector to invent a value.
Preserve the general lesson
The value of the harvest is not a special rule for one library’s version field. It is a more accurate generic model of own-data observations. Later interpretation can look for relevant evidence without teaching the collector to execute package-specific behavior.
This article describes source-level work and its documented fixtures. It is not a claim that every global metadata scheme is supported or that runtime evidence alone establishes an exact package patch.
For a recovery assessment, a missed field can reveal more than a missing heuristic. It can reveal that the observer’s data model excluded a legitimate shape. The durable fix is to improve the model while retaining the no-invocation boundary, not to add a one-off getter call that makes the demonstration pass.