CoolFace
Datasetpublic

teaql/agentic-software-conformance

TeaQL Agentic Software Conformance Machine-readable evidence for the TeaQL Harness: semantic-model evaluation, generated artifacts, seven language-native runtimes, executable examples, and cross-language conformance checks. This is an evidence dataset, not a leaderboard and not a collection of unverified model claims. Each row identifies its evidence level, exact source, verification date, revisions where available, command or gate, result, and important qualifications. The… See the full description on the dataset page: https://huggingface.co/datasets/teaql/agentic-software-conformance.

sourceHugging Faceapache-2.0updated 18d agoView on Hugging Face
0likes42downloads
Dataset Card

TeaQL Agentic Software Conformance

Machine-readable evidence for the TeaQL Harness: semantic-model evaluation, generated artifacts, seven language-native runtimes, executable examples, and cross-language conformance checks.

This is an evidence dataset, not a leaderboard and not a collection of unverified model claims. Each row identifies its evidence level, exact source, verification date, revisions where available, command or gate, result, and important qualifications. The canonical human-readable status remains the TeaQL Conformance repository.

Files

  • data/evidence.jsonl: one retained evidence record per line.
  • schema.md: field definitions and interpretation rules.

Evidence levels

  • local-source: executed against checked-out runtime/generator source.
  • public-package: executed after resolving a published package or tag.
  • repository-matrix: a compact index into detailed retained evidence; it is not a substitute for the linked commands and reports.

Intended use

The dataset is suitable for auditing agent-produced reports, constructing conformance dashboards, and evaluating whether a generated workspace is backed by reproducible evidence. It is deliberately small: evidence quality and traceability matter more than synthetic row count.

Limitations

Records describe the revisions and environments named in each row. They do not prove every database/provider combination, all generated applications, or future versions. A pass must never be carried forward to a newer artifact without a new execution record.