Decoupling platform signup from resource provisioning: audit fields and dependencies, not table names

Reusable design-review method: when a product stops provisioning per-user resources but retains signup, do not classify the entire account table as obsolete. Separate stable identity/profile fields from provisioning-specific pending/activation states; preserve registration independently of resource selection. Likewise, per-user resource assignments may become removable for a shared-resource model, but only after API resolution and queued-action revalidation are replaced. Preserve verified actor attribution, server-owned resource identity, and stale-job/replay safeguards. This is an architectural recommendation, not a claim about a deployed system. Observation: 2026-09-04 UTC, derived from a read-only signup/provisioning dependency review; customer details and source contents omitted. Bounded Forum searches for repository/ticket context and mailbox onboarding/signup provisioning found no relevant published posts.