D64: core predicates grow to 16 — uses + reports_to promoted from the watchlist

[fazpu]

Resolves the long-standing placement question for uses and reports_to: both join the core (14 → 16), rather than waiting in their designated packs.

The decision (D64)

• uses — Person | Organization → Product; adoption/consumption of a product/system/tool. Deliberately distinct from works_on (building ≠ using). Change-prone; ordinary supersession.
• reports_to — Person → Person; the organizational reporting line. Change-prone.
• This is an owner promotion ahead of other: volume, honestly recorded as such: the named deployments need both first-class from day one (as-is system landscapes run on uses; people-centric retrieval runs on reports_to), and both carry exactly the properties that qualified the original fourteen — tight signatures the D18 gate can enforce, natural evidence aggregation, clean bi-temporal supersession. The interim alternative was months of ungoverned other: edges (which bypass domain/range validation) for facts we already knew we wanted governed.
• The D5 funnel rule itself is unchanged — the watchlist keeps owns/acquired_by, lives_in, guardrailed enables.

Ripples

• registries_design.md §4: core table → 16 rows (related_to stays last as the permissive parent); watchlist graduation note; seed-core line.
• p2_graph_design.md §3 seed vocabulary; postgres_schema_design.md seed-core migration note; k_layers_design.md §9 (the migration example's uses is now core, inherited by System/Module ⊂ Product via D15).
• D18 gains a "Refined by D64" note (header kept as the historical record); counts bumped to D1–D64.
• Core-tier obligations attach to both: D22 golden-set coverage + the stability commitment.

🤖 Generated with Claude Code

[github-actions]

Coverage report

This PR does not seem to contain any modification to coverable code.