Conformance tools

Three optional tools, choose your contract#

tessembly-tck checks basic compact/hold contracts; tessembly-document-tck checks documents; tessembly-filter-tck checks F1/F2 supply conditions. External developers connect these optional tools to real application ingress/egress. They are not included in the npm product runtime.

cargo build --locked --workspace
target/debug/tessembly-tck --report compact-report.json -- YOUR_HOST test-port
target/debug/tessembly-document-tck --report document-report.json -- YOUR_HOST doc-port
target/debug/tessembly-filter-tck --report filter-report.json -- YOUR_HOST test-port

Replace YOUR_HOST with a trusted executable; add .exe on Windows. Basic and filter suites use the same test-port with explicit feature IDs. These test actual format boundaries, not other validators, and do not certify arbitrary external applications.

An advanced-port request#

{"id":1,"protocol":"tessembly.document-test-port.v1","profile":"tessembly.rfc3.order.v1","op":"validate","text":"tessembly \"tessembly.rfc3.order.v1\"; supply(\"P7\"); draw(IN(1,3,T)&I<T);"}

Send one JSON request per line and receive one response. Bind id and profile unchanged. validate checks syntax/declarations, not successful execution. DOCUMENT.md defines roundtrip, project, decode, hold and resolve.

Zero results are not incomplete work#

Do not substitute another policy or hold state for unsupported input. Missing supply is NOT_CHECKED; bounded work is INCOMPLETE; a proved contradiction is UNSAT in its domain. Do not merge D/U or unrelated scopes.

The runner bounds output and runtime and checks malformed JSON, profiles and duplicate results. It runs a trusted command, not arbitrary code in a sandbox. Do not ship the test executables as library runtime dependencies.