The tables the reasoner reads

Reference tables a node consults to answer a question of fact — what a code means, what its unit ceiling is, what one billing unit is worth. A node reaches them through the table_lookup operator, naming the table and the column it wants.

The reasoner Policy library

This is not the policy library. The Knowledge Center holds versioned policy prose and the retrieval over it — it governs the determination, in the version in force at the date of service. These tables do not govern anything: they are looked up. A node asks the code guide what 99215 is; it asks CPP-014 whether the record supports billing it. The engine keeps them in separate stores for the same reason.

Tables

3 consulted by a node in this batch

Rows

across every active version

Signed off

smi is not

Missing row behaviour

Fails closed

on that lookup, not on the walk

Every table

Active version shown

Table	Key	Rows	Version	Sign-off	Source
Billable Code Groups bcg	code	16	v1	Signed off Payment Integrity · 2026-02-01	CMS National Correct Coding Initiative, practitioner PTP edits, 2026 Q2
Medically Unlikely Edits mue	code	15	v1	Signed off Payment Integrity · 2026-04-01	CMS Medically Unlikely Edits, practitioner services, 2026 Q2
Specialty Medical Injectable dates smi	code	2	v1	Unsigned highest version wins	CMS Part B ASP pricing file 2026 Q2
Service Procedure Code Guide spcg	code	15	v1	Signed off Policy Operations · 2026-01-15	CMS HCPCS/CPT descriptors 2026 · internal review-type mapping

Signed-off wins, else highest version. An unsigned newer version sits on disk beside a signed one without displacing it, so a table can be prepared and reviewed without changing what tonight's run reads. Both properties are cgn-sop-reasoner's, taken from the engine itself; what is a stand-in is the store — these are YAML files read once at import, where the platform keeps a row-hashed version ledger in Postgres and mirrors sign-off to Genesis AuthZ.