# Adopt durable team records

Practices: typed-records, atomic-claims, durable-handoffs.

Inventory the existing backend and schemas before adoption. Use the [kit definitions](https://hamedtaheri.com/playbook/v0.1.0/kit/definitions.json) to assess compatibility. Preserve local identity rules, ownership, statuses and custom fields. Add missing compatible definitions only when setup is authorized.

Read the [full team-kit architecture](https://hamedtaheri.com/playbook/v0.1.0/reference/kit-architecture.md) and [JSON schema map](https://hamedtaheri.com/playbook/v0.1.0/reference/kit-architecture.json) when assessing collections, entity types, document categories, relations or guidance. It is a source snapshot of AI Coding Memory 1.2.0, not the portable starter schema or a live installation receipt. Do not infer an edge from a field or a diagram: explicitly write and verify approved relationships. Use structured, fully paginated filters for complete work lists. Supporting specs/plans/handoffs are document content, not additional entity types in this kit.

Records need stable typed keys, versioned writes, scope-restricted retrieval and evidence references. Read before changing status/owner; a conflict means re-read and resolve, not retry with stale assumptions. Verify writes and say unsaved when they fail.

The local adapter demonstrates create, get, guarded update and task claim. It has no semantic recall or production permission model. Use it only for the documented private disposable exercise. The [provider mapping](https://hamedtaheri.com/playbook/v0.1.0/kit/personize-mapping.md) describes additional qualification for hosted storage.

At a handoff record goal, work references, revision, attempts, verified acceptance, unresolved questions and next step. Record human decisions with their authority. Suggestions are not tasks until the human accepts them. Keep transcripts, secrets and customer data out of the public reference and contribution export.