Cursor Build Prompt¶
Build the Rust reference implementation of DPCS.
The repository contains a single SPEC.md document with the full 26-chapter DPCS draft specification.
Treat SPEC.md as authoritative.
Processing pipeline through ROADMAP 0.13.0:
DPCS Document -> Parser -> COM -> Validator (+ resolve) -> Plan -> Capabilities -> Binding
(+ Compatibility / Registry documents+HTTP / Conformance / Packages / Schema emit / Reports / TUI)
(+ AnalysisContext / parallel+incremental validate / Criterion benches)
(+ SPEC_COVERAGE.md / diagnostics.catalog.json)
Implemented:
- Rust workspace (
dpcslib,dpcs-cli) - Canonical Object Model
- YAML and JSON parsing
- Diagnostics model (including DiagnosticReport + catalog)
- Phase-based validation (including extensions, security, governance)
- Pipeline graph validation
- Data Flow / Control Flow validation
- Contract reference resolution and nested pipelines
- Pipeline Plan (with nested provenance)
- Capability profiles and matching
- Orchestrator binding scaffolds +
dpcs_semantics.json(Airflow, Dagster, Prefect, Temporal, Kubernetes) - Compatibility analysis
- Registry document validation + reference HTTP client/server (ADR-0005)
- Conformance claims and Appendix E suite
- Pipeline packages (
.dpcspkg) - JSON Schema / OpenAPI helpers
- Python and WASM bindings (PyPI / npm
@eddiethedean/dpcs/ Wasmer) - Report module (Markdown / HTML / Mermaid / DOT) and rich CLI
--format/--out - Interactive TUI inspector (
tuifeature) - Performance:
AnalysisContext,parallelvalidate,ValidationCache, synth + Criterion - CLI
- Tests and fixtures
- SPEC coverage matrix and stable public API documentation
Do not implement execution runtimes or production-grade operator libraries.
Use Rust best practices and keep names aligned with SPEC.md.