Expand description
Uniform capability model (act:core §3.1).
One envelope (CapabilityRequest) describes every capability class —
filesystem, http, sockets, inter-component, semantic, or plugin-provided.
The per-class difference lives in constraints (a provider-defined,
opaque-at-this-layer JSON predicate), not in separate Rust types.
Structs§
- Capabilities
- Capability declarations from the
std.capabilitiesmap inact:component. Serializes transparently as a CBOR/JSON map keyed by capability id. - Capability
Request - Uniform capability request — one entry per capability class in the
act:componentstd.capabilitiesmap.
Type Aliases§
- Constraint
- A provider-defined constraint predicate, opaque at the
act:corelayer. Each capability provider supplies the JSON Schema that validates it. E.g. filesystem{ "path": "...", "mode": "ro" }, http{ "host": "..." }, a semantic class{ "database": "staging_*" }.