# Mapping the starter to Personize

This is a mapping/qualification guide. The local package does not create entities, guidelines or organization records, and this adapter has not been live-qualified as part of the package.

1. Use the adopter's authorized organization and current tool/API schemas. Read its guidelines and collection definitions first. Obtain the actual actor's confirmed identity; never copy the author's private team settings.
2. Map portable `project`, `task`, `session` and related types to deployed entity types and custom key fields. A common deployed session type is `ai_session`; portable `session` is not a claim that every backend uses that exact name.
3. Create records with content and the backend's stable identity. Set structured fields in a subsequent supported update. Do not use display names to merge records.
4. Map guarded updates to `expectedVersion` or an atomic precondition on the deployed update operation. Verify one winning claim under two competing agents before enabling concurrent execution.
5. Link sessions to work and projects using the organization's allowed relation names. Verify evidence-document links after creation.
6. For retrieval, map typed keys and project scopes, apply relevant guideline filters, honor content budgets and complete pagination where the task requires all results.
7. Test with synthetic records first: create/read, duplicate identity, version conflict, competing claim, wrong-scope retrieval, handoff, failed write and approved finding export. Record actual backend/tool versions and results.

On installations exposing `memory_save` and `memory_update_properties`, use their current argument contracts rather than assuming the portable fields are already registered. Schema installation must preserve customized fields and must not modify another person's work without authority.

Do not ship organization IDs, real work emails, API keys, raw transcripts or customer records in a downloadable kit. Provider credentials and runtime configuration belong in the adopting team's private environment. Qualify privacy, authorization and atomicity on the chosen deployment; the local demonstrator cannot establish those properties for the hosted backend.