Expand description
The capability envelope: capabilities are declared in the manifest and
enforced by the binding. The binding (a stream/derived compute vs an Action compute)
declares which envelopes it accepts and rejects a transform that violates it — the
governance boundary expressed as types, so it is checkable, not trusted.
Structs§
- Capability
Envelope - The declared capability envelope of a transform.
Enums§
- Binding
- The binding a compute is used under — this decides which envelopes are legal.
- Envelope
Violation - A specific reason a binding rejects an envelope. Kept as distinct variants so the publish gate can report exactly what is wrong.
- Hardware
- Where a compute must run. A capability-aware scheduler routes by this; GPU is container-only for now.