# LightOp Kernel Knowledge

This directory backs the `lightop-kernel-knowledge` skill. For LightOp/DCU
work, use evidence in this order:

1. Local LightOp source, wrappers, bindings, config tables, tests, and
   benchmarks.
2. ROCm/DCU official docs and upstream source: SourceFind DCU/DTK docs,
   ROCm/HIP, MIOpen, rocBLAS, hipBLASLt, Composable Kernel, Triton AMD,
   PyTorch ROCm, SGLang/vLLM AMD paths, the Hygon HIP optimizer reference,
   protected DCU Toolkit AMD knowledge-base pointer, plus bundled MR evidence
   from SourceFind LightOp and DCU Toolkit flash-attention-cutlass.
3. The bundled CUDA-oriented PR corpus, only as cross-platform inspiration
   after translating and validating the idea on DCU.

The existing corpus is still available:

- PR pages under `sources/prs/`
- Source reference pages under `sources/refs/`
- PR evidence bundles under `evidence/pull-bundles/`
- Candidate ledgers under `candidates/`
- Metadata under `data/`
- Query and materialization scripts under `scripts/`

Run local PR queries from this directory:

```bash
python3 scripts/query.py "<keywords>" --compact --limit 30
python3 scripts/query.py "lightop dcu <operator>" --repo sourcefind-lightop --compact --limit 20
python3 scripts/query.py "flash attention dcu" --repo flash-attention-cutlass --compact --limit 20
python3 scripts/query.py "hygon dcu mmac" --type source-reference --compact --limit 20
python3 scripts/query.py "amd knowledge base dcu" --type source-reference --compact --limit 20
python3 scripts/search-pr-diffs.py <term1> <term2> [--any] [--limit 100]
python3 scripts/get_page.py <page-id>
```

When CUDA evidence shapes a LightOp implementation, record that it is
inspiration, cite the source path/URL and commit/version, and explain the DCU
translation: HIP API, CU/wavefront/LDS/MFMA/resource/config differences.

Protected source pointers, such as the DCU Toolkit AMD knowledge base, are
index entries only until authenticated content is synced. Do not cite them as
direct implementation evidence without the imported file path, commit/version,
and license/notice details.

Validate the bundled corpus with:

```bash
python3 scripts/validate.py
```