Home today
Home is a personal household launchpad and signed-context surface. It exposes navigation configuration and five published actions; it does not currently provide populated domain content or a local workspace database.
Read the signed household context
Get signed user identity, active context, selected household and memberships through bootstrap. A missing selected household is null. Personal activeContextId is null; it must not be treated as a workspace id. Identity comes from Auth.
Understand widget engagement
The widget returns navigation and refresh controls. With an organization and configured service credentials it attempts one Nexus app_engagement event. Usage failure does not block the widget. The returned resource scope is not independent evidence of a workspace grant or a usage delivery receipt.
Discover workspace lifecycle separately
Auth owns platform workspace listing, creation, rename and default selection. Home publishes only a delegated archival request requiring organization context, workspace:delete and an admin grant. Personal registration does not make organization archival available.
Verify privacy scope
Organization privacy actions require an authenticated matching organization and the exact privacy permission. Export reports empty Home stores and excludes platform identity. Erasure acknowledges no local stores, retaining canonical Auth identity, workspaces and backups under policy; it is not organization-wide deletion.
Execute and verify each action
Use action discovery, validate the exact input, inspect the plan, authorize its documented effects and verify the returned scope. Worked responses use synthetic identities and simulated Auth and Nexus transport. Native machine guidance is separately retrievable.
Action reference
Evidence
Actual Home Worker response with synthetic identity and identifiers. Auth grants, platform archival and Nexus usage transport are simulated; Home has no local database. This does not prove live platform archival or Nexus delivery. No request credentials are captured. Captured requests use synthetic principals and identifiers. Registration supports the personal household context; organization privacy and archival require an actual authorized organization context and cannot be inferred from personal access.