dtcs 0.11.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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106

# Conformance certification

Offline conformance profiles and a certification suite per [SPEC.md](../SPEC.md) Chapter 23. Phase 0.10 introduced the machinery; Phase 0.11 deepens Analyzer assertions and runtime catalog coverage.

## Profiles

The reference implementation declares eight implementation classes:

| Profile ID | Class |
|------------|-------|
| `parser` | Parser |
| `validator` | Validator |
| `analyzer` | Analyzer |
| `planner` | Planner |
| `optimizer` | Optimizer |
| `compiler` | Compiler |
| `runtime` | Runtime |
| `integrated-platform` | Integrated Platform (primary) |

Analyzer profile capabilities include `compatibilityAnalysis`, `evolutionAnalysis`, and `lineageAnalysis`.

## Assertion kinds

Manifest cases under `tests/conformance/manifest.json` (mirrored in `src/conformance/manifest.json`) use these assertion kinds:

| Kind | Meaning |
|------|---------|
| `parseValid` / `parseInvalid` | Document parses (or fails to) |
| `validateValid` / `validateInvalid` | Validation success / failure (+ optional `codes`) |
| `analyzeValid` | Static analysis produces no error diagnostics |
| `compatLevel` | Compatibility level vs `comparisonFixture` equals `level` |
| `evolveValid` | Evolution analysis vs `comparisonFixture` succeeds |
| `planValid` | Plan lowering succeeds |
| `optimizeEquivalent` | Optimizer preserves semantics |
| `matchSupported` | Capability match succeeds against `dtcs:reference` |
| `compileValid` | Compilation succeeds |
| `runtimeOutput` | Runtime output matches fixture (`input`, `expectedOutput`) |
| `runtimeInvalid` | Runtime fails with expected diagnostic `codes` |
| `securityProbe` | Automated Ch 24 probe (`probeId`) |

## Declare capability

Emit the Ch 23 §9 implementation capability declaration:

```bash
dtcs conformance declare
dtcs conformance declare --profile integrated-platform --json
```

```python
import dtcs

declaration = dtcs.conformance_declare()
profile_only = dtcs.conformance_declare("parser")
```

## Run offline tests

```bash
dtcs conformance run --profile integrated-platform
dtcs conformance run --profile analyzer
dtcs conformance run --profile all --json
```

```python
report = dtcs.conformance_run("integrated-platform")
assert report["passed"]
```

| Exit code | Meaning |
|-----------|---------|
| `0` | All selected profile tests and security probes passed |
| `1` | One or more tests failed |

## Interpreting reports

JSON reports include:

- `implementationId`, `implementationVersion` — reference implementation identity (`0.11.0`)
- `profiles` — profiles exercised in this run
- `results` — per-test outcomes (`id`, `profile`, `passed`, optional `message`)
- `security` — automated Ch 24 checklist probes
- `passed` — overall result

Failed tests list the profile, test id, and a diagnostic message. Security probes document residual manual review items (for example deployment-specific network policy).

## CI integration

```bash
cargo test --test phase_0_10 --locked
cargo test --test phase_0_11 --locked
dtcs conformance run --profile all
./scripts/security-checklist.sh
```

Also see [ci-integration.md](ci-integration.md).

## Bindings

| Surface | Conformance support |
|---------|---------------------|
| Rust | `dtcs::conformance_run_all()`, `dtcs::conformance_declare()` |
| Python | `conformance_declare()`, `conformance_run()` |
| WASM / Node | `conformanceDeclare()` only; full `run` requires CLI or Python |

See [security-checklist.md](../adoption/security-checklist.md) for Ch 24 requirements and [docs/api/python.md](../api/python.md) for the Python API reference.