Collections Manage

Canonical folder for collection/table inventory and collection-management evidence.

Current canonical handbook: knowledge/dev/laws-new/newlaws/collections-manage/collections-usage-handbook.md

Related DOT handbook: knowledge/dev/laws-new/newlaws/dot-manage/dot-usage-handbook.md

Rule: Directus/Postgres/schema changes are DOT-only. No manual SQL, no psql, no Directus generic collection creation for schema/table work.

Purpose: Before designing staging/workbench/temporary LEGO stores, check this handbook to know which collections/tables already exist, which are production-critical, and which are safe/unsafe to reuse.

Current expected verdict: No new collection/table is created by this handbook. And — confirmed by the inventory — no run-scoped, disposable, delete-fast R2-B2 staging workbench collection/table/schema exists (the closest, sandbox_tac, is persistent, read-denied, and owner-unknown). The missing piece is an authorized run-scoped staging-schema DOT (Macro-9B), exactly as the DOT handbook §15 concludes.

Contents:

• collections-usage-handbook.md — living manual: §0–§18, full 382-object inventory (4 schemas: public/iu_core/cutter_governance/sandbox_tac), 685-view family summary, production-critical / staging / dangerous / need-triage sections, and §17 future collection_operator_catalog candidate.
• reports/macro9a1-collections-usage-handbook-execution-report-2026-06-19.md

Evidence date: 2026-06-19 (fresh read-only query_pg + list_docker + KB; 0 mutating calls to the substrate).

Engineering PASS ≠ Owner authority PASS. Default HOLD.