Skip to main content

Crate traverse_contracts

Crate traverse_contracts 

Source
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-telemetry FR-001). No caller of UsageTelemetrySink takes on a network or configuration dependency merely by calling it: NoOpUsageTelemetrySink is the default and performs no I/O of any kind.
violations

Structs§

CapabilityContract
CapabilityReference
Condition
ConnectorContract
ConnectorError
ConnectorInvocation
ConnectorOperationEnvelope
ConnectorOutput
ConnectorRequirement
DataFlowPolicy
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.
DependencyReference
Entrypoint
EventClassification
EventContract
EventPayload
EventProvenance
EventReference
EventValidationContext
EventValidationEvidence
EventValidationResult
Execution
ExecutionConstraints
FieldDataClassification
Declares the classification of one field, addressed by a JSON Pointer (RFC 6901) into the capability’s inputs.schema or outputs.schema.
IdReference
ManifestRiskPolicy
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
ProducedValidationEvidence
Provenance
PublishedContractRecord
PublishedEventRecord
ReliabilityMetadata
Reliability semantics a caller MUST honor when invoking this capability.
RiskMetadata
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.
SchemaContainer
SideEffect
UseCase
One authored use case that demonstrates a concrete input/output path for a capability.
ValidationContext
ValidationError
ValidationEvidence
ValidationFailure
ValidationResult

Enums§

BinaryFormat
DataClassification
DependencyArtifactType
DeterminismClass
Whether repeated invocation with the same inputs is guaranteed to agree.
EffectClass
What kind of effect invoking this capability has on the world.
EgressPolicy
Which connectors classified data produced/accepted by this capability may legally flow to. Denied means no external connector egress is permitted regardless of what connectors the capability is otherwise wired to.
EntrypointKind
ErrorSeverity
EventProvenanceSource
EventType
EvidenceStatus
EvidenceType
ExecutionTarget
FilesystemAccess
HostApiAccess
Lifecycle
NetworkAccess
PayloadCompatibility
ProvenanceSource
ServiceType
UMA service type classification — governs placement routing and event routing.
SideEffectKind
ValidationErrorCode

Traits§

ConnectorPlugin

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.1 rules.
validate_event_contract
Validates a parsed event contract against the governed v0.1 rules.
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.