Design-first, spec-driven documentation for TileOPs. tileops/manifest/ and the documents below are the authoritative spec; code conforms to the spec, not the other way around.
| Document | Scope |
|---|---|
| architecture.md | System modules (M1–M8), data flow, agent production loop, directory structure. |
| manifest.md | tileops/manifest/ spec: signature, workloads, roofline fields, source. |
| ops-design.md | Op interface execution guide — how to add a new op. |
| ops-design-reference.md | Op interface detail reference: interface tables, codegen, naming, protocol. |
| roofline.md | tileops/manifest/ roofline field spec: performance model, authoring, and per-consumer contracts (validator, benchmark, M5, op codegen). |
| Document | Scope |
|---|---|
| trust-model.md | Trust boundaries between manifest → test → implementation → benchmark; workloads layer contract. |
| testing.md | Test and benchmark framework: core abstractions, tolerances, reporting rules. |
| tileops-skills.md | Developer decision guide: which repo-provided skill to use for which task, with composition diagram. |
Empirical performance guidance lives under perf/. Each op category has a checklist plus the evidence backing it.
- perf/elementwise.md — elementwise kernel performance checklist
- perf/elementwise-evidence.md — reasoning and measurements
- TileOPs.github.io — auto-generated documentation site (API reference, perf tables, support matrix).