Restored architecture, account and verification requirements from the Move Team design-system reference.
Source captured 31 October 2026. Requirements below are preserved guidance. References to implementations and checks describe the dated Move reference, not fresh verification of every ecosystem service. Public documentation does not grant access to restricted operations or records.
DISTINCT EXPERIENCES
Customers stay in their app.
Customers register and work through their public app. The restricted operations portal manages shared services for approved strategic partners, team, support and internal roles. Shared infrastructure does not grant access to another app’s records.
Website purpose and access boundary
Website
Experience
Access boundary
business.zuporta.com
Zuporta public and customer experience
App-specific onboarding, membership and records
plaindecision.com
Plain Decision public and customer experience
The customer’s authorized results and features
ecosystem.plaindecision.com
Restricted operations
Explicit grants, active scope, native MFA and session checks
accounts.plaindecision.com
Proposed neutral account address
Not assumed provisioned or approved for callbacks
Other ecosystem apps
Dedicated customer experiences
Same service contracts, separately assigned permissions
How an app chooses its brand and policies
The server resolves a registered app from its fixed deployment configuration and validated origin. That configuration supplies stable app ID, approved domains, brand wording, callbacks, return destinations, onboarding, versioned terms, service settings and app policy. A browser-supplied app ID, role, tenant or return URL never grants authority.
Unapproved callbacks and incomplete terms keep account activation unavailable. Identity remains mapped by verified issuer and subject. Matching email addresses do not merge accounts.
SEVEN GROUPS · ONE GOVERNANCE FOUNDATION
The ecosystem map stays intact.
Each group keeps its purpose and customer experience. The shared layer supplies permitted functions through secured interfaces.
MOVE
Eld
Zuporta
plain.decision
Prutas and Utanon
Laag
Wayfarer
Dagan
Dedicated apps → secured service interfaces → 16 shared services
Central governance supplies common controls. Each app supplies its own policy values. Every protected action checks the person, app, organization, venture and permission.
Preuve.ai is the native validation dashboard within Plain Decision. “Fully unlocked validation dashboard” means the customer’s authorized results and features; it does not unlock internal operations or other customers’ records.
A 72-hour approval timeout escalates or expires the request. It never approves automatically.
SHARED ACCOUNT · SEPARATE PERMISSIONS
Register once is the target.
For a new pilot, use one identity system for customers, support and admins, with different organization, app and role permissions. Supabase is the default. Branding, onboarding, terms, memberships and records remain app-specific.
Adopted new-pilot default
Supabase: one identity, scoped access
Use Supabase for login, records and files. Enforce organization, app and role permissions for every protected operation. Support and admin capabilities require explicit grants; a role label in the interface never grants access.
Alternative when justified
Retain a working Clerk installation
Use Clerk when already working or when its benefit is documented. Do not split providers by user type. Existing installations remain intact while any proposed migration proves identity continuity, compatibility, current billing and account entitlements, security and rollback.
No new identity provider, automatic migration or account linking is implemented here. Customers and strategic partners do not gain internal privileges through public-app login or business ownership.
Callbacks, sessions and logout
Use provider-supported authorization, exact approved callbacks, state/CSRF protection, PKCE S256 and nonce where applicable. Keep refresh tokens and secrets server-side, out of URLs and frontend bundles. accounts.plaindecision.com remains a proposal.
App logout: clear and invalidate the selected app’s session and private UI state. Ecosystem logout: revoke relevant provider and app sessions across participating apps, then confirm completion. A cleared cookie alone is not proof of global revocation. Existing access-token lifetime and offline tabs may delay complete rejection unless sensitive operations check revocation online.
Internal actions still require the applicable MFA, active-grant and session checks. Preserve existing authorization controls during any transition. Reusing an identity does not reuse another app’s permissions.
Updated Move Team catalogue, preserved ecosystem map, shared feedback and form behavior, safe scope display and a server-only app configuration contract. Local checks are recorded in the review package.
Requires separate test evidence
Real registration, recovery, cross-domain session reuse, provider logout/revocation, deployment acceptance and physical-device checks. No SSO or production-readiness claim is made.
Required security checks cover guests, internal page/API/database denial, cross-organization and cross-venture isolation, role tampering, callback rejection, revoked sessions and removed staff grants. Existing intake, referral, CRM and shared-service behavior must retain its own regression evidence.
Security advisories need context
Private tables with RLS and no client policies may intentionally deny direct access. Inspect grants and privileged-function authorization before changing a warning. Preserve identity mappings and authorization helpers; never remove a control just to clear an advisory.
A service request carries an operation, app context, tenant and venture scope, input and an idempotency key where needed. The server resolves identity and validates scope against authoritative membership, policy and grants. Browser claims cannot supply authority. Responses return only permitted records, scoped pagination, clear refusal codes and minimal audit references. Sensitive input and tokens stay out of logs and analytics.
Use explicit unavailable, unauthenticated, permission-denied, stale-policy, conflict and retry states. Null commercial policy disables dependent behavior; it never implies a free price or an approved rate.
Source records and ownership
This implementation guide retains the original source permissions and earlier research distinctions. Jet’s direct October 31 adoption of Visual & Tool Map Standard v1.0 defines this update; linked Notion records continue to own their other approved requirements.
This catalogue documents the design foundation. Authentication, data, subscriptions and access retain their separate controls. Human usability studies and independent product acceptance remain separate.