dtcs 0.9.0

Reference implementation of the Data Transformation Contract Standard (DTCS)
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

# Architecture

Follow the architecture defined in `SPEC.md`.

Implementation pipeline (Phase 0.9):

```text
DTCS Document
        │
        ▼
Parser
        │
        ▼
Canonical Object Model
        │
        ├──────────────────────────────┐
        ▼                              ▼
Validator (0.1–0.6)              Analyzer (0.3, 0.6)
        │                              │
        │  registry::resolve           ├─ compatibility::analyze
        │  stdlib definition checks    ├─ analyze_evolution
        │  extension pass              ├─ versioning::validate
        ▼                              └─ lineage::analyze
Diagnostics                            │
        │                              ▼
        ▼                         Analysis reports
Plan lowering (0.7)
        │
        ▼
Plan optimization (0.8)
        │
        ▼
Capability matching (0.9)
        │
        ▼
Compilation (0.9)
        │
        ▼
Reference runtime (0.9)
        │
        ▼
Outputs
```

Analysis is **read-only** — it never mutates the Canonical Object Model.
Registry resolution is also read-only; the embedded catalog is authoritative for `dtcs:` identifiers.
Standard library entries include structured definitions used during semantic validation.
Plan lowering is **read-only** with respect to the COM — it produces a separate `TransformationPlan` IR.
Plan optimization transforms a validated plan into a semantically equivalent optimized plan.
Capability matching, compilation, and the reference runtime execute validated contracts in-memory for conformance and development use.

For this crate through Phase 0.9 (`0.9.0`), implement through Diagnostics, Contract Analysis, Registries, starter Standard Libraries, static semantic analysis, transformation plan lowering, plan optimization, capability matching, compilation, and reference runtime execution.