# Iris depth review

This guide expands the eleven-slide Iris entry point into a forty-four-slide
learning path at source revision `1ceae52c7896a59ac74a4429d410f3218f0b91c6`.

The sequence follows one governed memory through seven questions:

1. Who proposed it and which evidence layer supports the behavior?
2. Which identity, category and scope constrain the record?
3. When may session context become durable profile memory?
4. Which gates, scores, conflict rules and budgets shape recall?
5. How do consent history, suppression and data rights change use?
6. How do member controls, cross-device continuity and inspection expose state?
7. Which durable effects and release evidence remain outside pure modules?

All fifty-five meaningful units in the two pinned V1 Iris pages are now
reviewed: six retain their earlier exact assignments in
`iris-memory-boundaries.json`, and forty-nine are bound by the generated
`v1-iris-depth.json` assignment. The one remaining source unit is a structural
heading. Parallel prose in the architecture and feature pages remains separately
assigned because each page is an independently reviewable source.

The diagrams describe records, gates, responsibilities, policy relationships and
recovery states. They do not assert separate deployed services. The pinned
contracts and Iris modules implement substantial local behavior, while callers
still own authentication, current permission derivation, durable persistence,
replica and downstream deletion, audit ingestion, member notice delivery and
cross-device execution. The feature page explicitly keeps customer edit, pause
and forget parity partial.
