docs.rs failed to build tandem-plan-compiler-0.5.4
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
tandem-plan-compiler-0.5.2
tandem-plan-compiler
Mission and plan compiler boundary for Tandem.
This crate is the extracted compiler layer that turns high-level Tandem goals into governed plan packages, runtime projections, and draft lifecycle behavior.
Boundary
Consumers should import from tandem_plan_compiler::api only.
apiis the curated embedding surface for hosts liketandem-server- the rest of the crate layout is implementation detail and may change during extraction work
What stays outside this crate
This crate does not own HTTP, storage engines, provider transport, MCP server
registries, or runtime-side AutomationV2Spec persistence. Those remain host
concerns and are supplied through traits or thin adapter modules.
What this crate owns
- mission and workflow planning
- planner revision flow
- draft lifecycle logic
- runtime projection IR
- shared output-contract seeds and policy defaults
- compiler-facing host traits