Skip to main contentCrate vela_protocol
Source - access_tier
- v0.51: Access tiers — the dual-use deposition channel.
- agent_bench
- VelaBench v0.26 — agent state-update scoring
- aggregate
- v0.35: Consensus aggregation — the inference layer.
- ancestor_closure
- Ancestor-closure primitive for federated event sets.
- artifact_audit
- Artifact proof-readiness checks for frontier-owned files and pointers.
- artifact_to_state
- Import agent-produced artifact packets as reviewable frontier state.
- benchmark
- Benchmark extraction quality against a gold standard.
- bridge
- Bridge detection — find cross-domain hypotheses from multiple frontiers.
- bundle
- Content-addressed finding bundles: the atomic object of the Vela protocol.
- calibration
- v0.34: Calibration scoring over resolved predictions.
- canonical
- Canonical JSON serialization for content-addressed Vela primitives.
- carina_validate
- v0.75: Carina-primitive JSON Schema validation.
- causal_graph
- v0.44: Pearl level 2 — causal graph + do-calculus over the
frontier’s claim-to-claim link graph.
- causal_reasoning
- v0.40: Causal reasoning over the schema landed in v0.38.
- cli
- cli_style
- CLI output discipline for Vela.
- confidence
- Citation-grounded frontier confidence calibration.
- conformance
- Conformance test runner — validates an implementation against test vectors.
- counterfactual
- v0.45: Pearl level 3 — counterfactual queries over the claim graph.
- decision
- Validated frontier-owned decision projections.
- diff
vela diff — structural comparison of two frontiers.- discord
- Discord assignment and frontier support.
- discord_compute
- Compute discord assignments against live Project state.
- entity_resolve
- v0.19: bundled entity resolution.
- events
- Canonical replayable frontier events.
- export
- Export frontier findings in proof-first formats: CSV, JSON-LD, BibTeX, Markdown, Frontier JSON, and Packet.
- federation
- v0.39: Hub federation — peer registry + conflict detection.
- frontier_repo
- Canonical frontier repository layout helpers.
- impact
- Read-only dependency impact reports.
- ingest
- PDF text extraction utility used by the modern Scout agent.
- link
- Stage 4: LINK — infer typed relationships between findings.
- lint
- Statistical validation linter — catches common methodological red flags in findings.
- normalize
- Stage 3: NORMALIZE — deduplicate entities, constrain types to schema.
- observer
- Observer policies — named lenses over the frontier.
- packet
- Packet inspection and validation utilities.
- permission
- Permission metadata for the public frontier tool registry.
- project
- Stage 5: ASSEMBLE — build the project with stats and metadata.
- propagate
- Correction propagation through the frontier link graph.
- proposals
- Proposal-first frontier writes and proof freshness tracking.
- provenance_compute
- Compute provenance polynomials and Belnap status from an
event log.
- provenance_poly
- Provenance polynomials in the semiring N[X].
- queue
- Phase R (v0.5): a local queue of unsigned draft actions.
- reducer
- Pure separable reducer over canonical events.
- registry
- Phase S (v0.5): registry primitive — verifiable distribution.
- repo
- Git-native VelaRepo abstraction — load/save projects from either monolithic JSON
or a
.vela/ directory of individual finding files. - retry
- Retry with exponential backoff for transient network failures.
- review
- Review import compatibility for frontier proof packets and legacy review bundles.
- runtime_adapters
- External runtime adapters that normalize upstream artifacts into Carina packets.
- schema_registry
- Content-addressed schema/reducer artifacts.
- search
- Full-text search across findings in a frontier or VelaRepo.
- serve
- Read-only MCP/HTTP frontier server.
- sign
- Cryptographic signing for finding bundles — the trust infrastructure layer.
- signals
- Derived frontier signals.
- source_adapters
- Source adapter runs that turn live source records into artifact packets.
- sources
- Source registry and evidence atom projections.
- state
- Non-interactive frontier state transitions.
- state_integrity
- Structural integrity checks for accepted frontier state.
- status_provenance
- Belnap contextual status derived from support/refute provenance.
- tensions
- Unresolved contradiction analysis — “Where does science disagree with itself?”
- tool_registry
- Tool registry — tools defined as data, separate from execution.
Borrowed from Codex (MIT) tool-as-data pattern.
- validate
- Schema validation for finding bundles in a frontier or VelaRepo.
- workbench
- v0.48: local workbench — axum web app rendering the substrate
against the cwd’s
.vela/ repo.