Expand description
Capability contract parsing and validation for Traverse.
Re-exports§
pub use proposal::CanonicalProposal;pub use proposal::DEFAULT_MAX_CONCURRENT_NODES;pub use proposal::DEFAULT_MAX_FAN_OUT;pub use proposal::DEFAULT_MAX_JOIN_WIDTH;pub use proposal::DEFAULT_MAX_QUEUE_DEPTH;pub use proposal::ManifestReference;pub use proposal::MappingSource;pub use proposal::ParallelSchedule;pub use proposal::ParallelScheduleError;pub use proposal::ParallelScheduleErrorCode;pub use proposal::ParallelScheduleFailure;pub use proposal::ParallelScheduleLimits;pub use proposal::ProposalEdge;pub use proposal::ProposalLimits;pub use proposal::ProposalMapping;pub use proposal::ProposalNode;pub use proposal::ProposalValidationError;pub use proposal::ProposalValidationErrorCode;pub use proposal::ProposalValidationFailure;pub use proposal::SnapshotDigests;pub use proposal::WorkflowProposal;pub use proposal::canonicalize_proposal;pub use proposal::compute_parallel_schedule;pub use proposal::proposal_digest;pub use proposal::proposal_snapshot_digest;pub use usage_telemetry::NoOpUsageTelemetrySink;pub use usage_telemetry::UsageEvent;pub use usage_telemetry::UsageEventKind;pub use usage_telemetry::UsageTelemetrySink;pub use violations::ViolationRecord;
Modules§
- proposal
- Runtime workflow proposal types, canonicalization, and digesting.
- usage_
telemetry - Provider-neutral usage-telemetry port (spec
088-runtime-usage-telemetryFR-001). No caller ofUsageTelemetrySinktakes on a network or configuration dependency merely by calling it:NoOpUsageTelemetrySinkis the default and performs no I/O of any kind. - violations
Structs§
- Capability
Contract - Capability
Reference - Condition
- Connector
Contract - Connector
Error - Connector
Invocation - Connector
Operation Envelope - Connector
Output - Connector
Requirement - Data
Flow Policy - Field-level data classification and egress policy for this capability’s declared inputs/outputs (spec 109 FR-005, FR-011). Schema compatibility alone never authorizes disclosure of a classified field.
- Dependency
Reference - Entrypoint
- Event
Classification - Event
Contract - Event
Payload - Event
Provenance - Event
Reference - Event
Validation Context - Event
Validation Evidence - Event
Validation Result - Execution
- Execution
Constraints - Field
Data Classification - Declares the classification of one field, addressed by a JSON Pointer
(RFC 6901) into the capability’s
inputs.schemaoroutputs.schema. - IdReference
- Manifest
Risk Policy - An application manifest’s declared narrowing of a capability’s egress surface (spec 109 FR-005: “a manifest may only tighten these requirements”). Every other risk dimension is an immutable fact about the capability’s own behavior and has no manifest-side override.
- Owner
- Produced
Validation Evidence - Provenance
- Published
Contract Record - Published
Event Record - Reliability
Metadata - Reliability semantics a caller MUST honor when invoking this capability.
- Risk
Metadata - Portable, immutable capability authority metadata across four independent dimensions (ADR-0041). A capability’s own contract is the only place these values may be declared; an application manifest may narrow how a capability is actually wired (for example connector selection) but can never override or weaken these classifications.
- Schema
Container - Side
Effect - UseCase
- One authored use case that demonstrates a concrete input/output path for a capability.
- Validation
Context - Validation
Error - Validation
Evidence - Validation
Failure - Validation
Result
Enums§
- Binary
Format - Data
Classification - Dependency
Artifact Type - Determinism
Class - Whether repeated invocation with the same inputs is guaranteed to agree.
- Effect
Class - What kind of effect invoking this capability has on the world.
- Egress
Policy - Which connectors classified data produced/accepted by this capability may
legally flow to.
Deniedmeans no external connector egress is permitted regardless of what connectors the capability is otherwise wired to. - Entrypoint
Kind - Error
Severity - Event
Provenance Source - Event
Type - Evidence
Status - Evidence
Type - Execution
Target - Filesystem
Access - Host
ApiAccess - Lifecycle
- Network
Access - Payload
Compatibility - Provenance
Source - Service
Type - UMA service type classification — governs placement routing and event routing.
- Side
Effect Kind - Validation
Error Code
Traits§
Functions§
- default_
risk_ metadata - Conservative migration default for contracts published before spec 109: the most restrictive classification on every dimension, so a capability never becomes silently automatic-eligible just because it predates risk metadata.
- governed_
content_ digest - governed_
event_ content_ digest - is_
automatic_ eligible - Spec 109 FR-006: whether a proposal using only this capability’s declared risk classes is eligible to run without an authorization token. Every caller that gates automatic execution MUST consume this single function rather than re-deriving the rule from individual fields.
- parse_
connector_ contract - Parses a connector contract from raw JSON text.
- parse_
contract - Parses a capability contract from raw JSON text.
- parse_
event_ contract - Parses an event contract from raw JSON text.
- reference_
connector_ contracts - validate_
connector_ contract - Validates a parsed connector contract.
- validate_
contract - Validates a parsed capability contract against the governed
v0.1rules. - validate_
event_ contract - Validates a parsed event contract against the governed
v0.1rules. - validate_
manifest_ risk_ policy - Validates that a manifest’s declared risk policy only narrows the capability’s immutable, contract-declared egress surface — it MUST NOT permit a connector the contract does not already allow.