Expand description
Declarative adapter metadata: support level, capabilities, evidence, environment declarations, conflicting options and profile presence (spec §3, §8, §21, §22, §28; SP2 design §4.2).
Structs§
- Adapter
Evidence - Where an adapter’s mechanism was verified (spec §28, extended with version and source).
- Adapter
Metadata - Everything about an adapter that does not depend on a launch.
- Capability
Claim - One capability claim and the evidence-scoped reason for it.
- Conflict
Option - An agent option proven to control the same mechanism the adapter uses (spec §21).
- EnvOverride
- A variable an adapter’s plan may set, and whether its value must never be printed (spec §22).
Enums§
- Capability
- An isolation property a profile may provide (SP2 design §4.2 definitions).
- Capability
State - How strongly a capability holds (spec §3).
- Mechanism
- How an adapter points its agent at the profile: the cross product of {variable, flag} x
{directory, file}. This is the complete, closed set — it is the same vocabulary the probe harness
speaks (
sandbox/probes/common.sh,env:/envfile:/flagdir:/flagfile:), so a fifth variant here would be a mechanism no probe can exercise. - Profile
Presence - Whether a profile exists for an adapter (spec §8).
- Support
Level - How far an adapter is proven, separately from its capabilities (spec §3, §37).