Answer — of the dossier's — rows
before you book a bench.

One product description — a drug, a stent, a functional food, a cosmetic — carried through Korea's CTD ledger per class, per section, with the guidance it came from. The other — come back named and dated, so a study budget is planned rather than discovered.

The dossier ledger rapl.readiness.manifest

wet‑lab only — computation supports — computation stands in — biology‑triggered —

—

point at any row to read it

—product classes

The contract

Described once. Judged everywhere.

rapl.regulatory.product_ir
— lines

One product description — composition, claims, capabilities, computed biology, provenance — travels to every surface above it, so a bench, a rule pack and a dossier all judge the same object. Rules are written in a closed vocabulary of — predicates and — actions: a regulation becomes data you can diff, review and replay, instead of code that can quietly do anything.

Lit classes carry dossier requirements today. The contract already describes — beyond them, so widening the ledger is a data change, not a schema migration.

The corpus

Three thousand documents, addressable by article.

rapl.data.sources
— source adapters

Korea MFDS/NIFDS guidance, collected and curated, then cut into chunks and pinned by sha256. Retrieval is lexical FTS5 by default, hybrid with a —‑dimension vector sidecar on request. RAPL retrieves and structures. It never generates — the connected agent does that, and the boundary is a test, not a promise.

The figures a corpus is supposed to keep at zero. They are the receipt, and they are re‑measured every time this page is built.

The one line it holds

— rows are marked wet‑lab, and stay marked.

Each is named, with the guidance it came from and the classes it binds — a schedule, not a shrug. That refusal is what makes the rest of this page worth reading: a ledger that never says wet lab cannot be believed when it says computed.