Abuelo Tomás

Explain that living-person page ownership depends on future account/profile binding.

Future requirement: Future ownership requires verified account identity, profile-person match, consent, and safe conflict handling.

Governance: Account identity alone must not claim a Página de Vida without product-approved ownership checks.

Describe future review rights without showing active approve, hide, remove, or edit controls.

Future requirement: Future review requires queues for additions about a living person, owner decisions, audit trail, and safe rollback.

Governance: Living people should control how visible additions about themselves appear on their own Página de Vida.

Explain future self-care actions as requirements only.

Future requirement: Future controls require permission checks, reason capture, family-context preservation, conflict handling, and audit events.

Governance: Personal controls affect that person's page; they must not redesign or take over La Sala.

State that Página de Vida is person-centered while La Sala remains the collective family return space.

Future requirement: Future flows must route eligible vivencias back to one or both spaces without turning either space into a social feed.

Governance: Living-person ownership does not create control over the collective family space.

Preserve the rule that visible additions for deceased-person pages require Custodio Familiar review.

Future requirement: Future deceased-person additions require Steward review, decision audit, protected-care handling, and conflict escalation.

Governance: Deceased-person visible additions remain governed by Custodio Familiar approval.

Describe conflict and revocation requirements without active workflow mutation.

Future requirement: Future ownership and review decisions require durable audit, revocation paths, appeal/conflict handling, and protected-care escalation.

Governance: Family privacy and personal dignity must be protected when ownership or visibility is disputed.

Explain that visible additions for deceased-person pages require future Custodio Familiar approval.

Future requirement: Future approval requires Steward identity, family-book scope, decision record, reason capture, and safe rollback.

Governance: No authorized contributor may bypass Custodio Familiar review for visible deceased-person additions.

Preview what kinds of additions may require review without changing visibility.

Future requirement: Future eligibility requires source attribution, related person match, privacy scope, sensitivity classification, and conflict checks.

Governance: Only appropriate, sourced, permissioned additions may become visible on a deceased-person Página de Vida.

Show fixture contributor and draft context only.

Future requirement: Future additions require contributor account binding, relationship context, edit history, and audit events.

Governance: Family members may contribute, but attribution and review must remain visible to the Steward decision path.

Describe sensitive-case handling without approving or rejecting material.

Future requirement: Future review requires sensitivity flags, protected-care escalation, family conflict handling, and scoped visibility decisions.

Governance: Sensitive memory, records, relationships, or disputes must be handled as protected family care, not routine publishing.

Explain disagreement paths without opening a real dispute workflow.

Future requirement: Future conflict handling requires durable comments, decision history, temporary hold states, escalation, revocation, and appeal rules.

Governance: Conflicts around deceased-person memory must preserve dignity, family privacy, and Steward accountability.

Keep living-person self-review and deceased-person Steward review distinct.

Future requirement: Future workflows must route living-person additions to personal controls and deceased-person visible additions to Steward approval.

Governance: Living-person self-review does not replace Custodio review for deceased-person visible additions.