Companion Publications

This section is informative.

The artifacts accompanying this draft support implementation, validation, and review. Their authority follows Normative and Informative Content; the specification’s prose governs disagreements.

The Standard Library has connector and filter-package manifests, samples, and fixtures under the library artifact directory. Its contracts and edition identity are defined under Versioning and Artifact Identity. The suite’s test connectors supply controlled test inputs, not catalog integrations.

The requirement registry supplies IDs and metadata, and the transition ledger tracks their lifecycle under Requirement Identifiers. The case index maps cited IDs to portable cases. These artifacts support traceability; the authoritative requirement attachments remain in this specification.

Conformance Suite

The portable suite contains validation, expression, digest, trigger, execution-trace, and run-record cases. Its case formats and citation rules are normative; individual cases provide evidence under Conformance. Passing the applicable cases does not establish compliance with requirements the cases do not exercise.

The runner interface exchanges JSON lines with an implementation adapter. The implementation supplies its conformance claim, and the runner selects applicable cases and compares the reported observations with their expectations. Suite self-checks validate fixtures, schemas, digests, and citations; they do not test an executor.

The regular-expression cases include ordinary Unicode 17.0.0 simple folds and case pairs whose simple-fold status differs between Unicode 16.0 and 17.0.

Machine-Readable Schemas

The draft includes structural schemas for Workfiles, connector manifests, and conformance claims. They assist validation but cannot establish all expression, scope, dependency, or execution requirements. Filter-package manifests and schema overlays currently have prose definitions without dedicated machine-readable schemas.

The run record schema defines the structural shape of Run Record Document; its prose and canonical encoding rules remain authoritative. The repository also contains a draft structural schema for locks. It is a tooling representation; the portable contract remains Resolution and Pinning, which does not prescribe that wire format.