Classified Initial-Load Reset

Context

An incorrect initial import needs a workspace-specific recovery path that retains identity and access configuration. Reset behavior differs from complete deletion.

Decision

Reset only a loading implementation workspace using classified removal participants, and verify remote reset support before recording destructive work.

Alternatives Considered

Restore the cluster to before the import: A shared cluster restore would affect unrelated workspaces. Delete and rebuild the workspace: Rebuilding would discard identity, access and upload context needed for another import. Write a separate reset per application: A second independent removal implementation would duplicate purge responsibilities.

Consequences

Every Platform participant needs an emptied-or-retained classification. Application reset policies restore different amounts of configuration. Failure requires another reset request and has no separate requester notice.