Resolve a workspace’s application availability: Capability Test Specification
Coverage
The category map distinguishes authored scenarios from unresolved proof obligations. A bound scenario names an existing executable suite; its recorded result remains unrun.
Interactions With Related Capabilities
Restore contract coverage after withdrawing a withhold. The commercial source of the restored result is the surviving contract.
Reflect a cancellation without extending stale coverage. The failed read preserves the earlier copy; the successful cancellation removes its contribution to access.
Separate licensing from operational resumption. The commercial standing remains traceable while availability follows the operational change.
Keep application availability separate from personal authority. The standing read does not itself grant the person permission to use a protected action.
Observe an access change across cache refresh. The refresh request refers to the changed scope; access reflects the current decision after refresh or expiry.
Evidence and Boundaries
Pinned assertion sources support the listed executable bindings. Proposed cases retain the proof required beyond those boundaries. Structured obligations name incomplete object, transition and permission trace; row-level concurrency proof does not establish complete workflow serialization.