Problem
Documented capabilities and knowledge can become operationally invisible. The opposite failure is equally dangerous: finding or surfacing something is treated as permission and ability to use it in every possible way.
GDSA
GDSA governs the path from durable existence to proportionate discoverability, routing, context-sensitive surfacing, relevance recognition, action-class-scoped authorized use, verified outcome and durable learning.
Lifecycle
durable -> discoverable -> routable -> surfaced -> relevant -> activation candidate -> authorized for action class -> used -> verified -> learned
Protections
durable != discoverable
surfaced != relevant
relevant != authorized
authorized != executed
execution != verified outcome
Composition
SRCB can establish a bounded context model before GDSA routes deeper. ORBIT and CARD/POINTER support orientation and routing, while Dialogue Lifecycle keeps relevance, decision, authority and execution gates distinct.
Scope
GDSA governs discoverability, relevance and bounded activation semantics. It is not a storage backend, scheduler or authorization provider, and it keeps availability, authorization, execution and verified outcome as separate states.