DR-038 — Activity-carried ids, not per-app-type workspaces, for application-type build-out

Owner ruling: “workspace” is the WRONG abstraction for scoping application-type data. Each activity carries its own id (proposal id, form id, guide id, …) and structured data scopes to the ACTIVITY, not to a per-app-type *_workspaces table. Future application-type build-out (sales proposals, sector intelligence, product guides) MUST NOT mint new <domain>_workspaces tables/ids; existing workspaces-keyed procurement surfaces are legacy-shaped, migrated opportunistically as their domains are reworked (delivered for the form domain by ID-145’s form-first re-key; the entry originally cited ID-130 as the example).