Accepted invitation record
acceptedInvite: invite-cousin-lina
Family space: family-space-atesora-demo
Accepted by: account-fixture-invitee
Invitation command
Accept invitation for Lina sample relative
Invitation acceptance now resolves a fixture account/profile binding, family membership placement, La Sala access decision, and audit preview without activating provider persistence.
fixture-persisted
Account and profile binding
boundLina sample relative is connected to account-fixture-invitee.
Binding mode: fixture-account-profile
Membership placement
fixture-active-membershipRole: contributor
Member: member-account-fixture-invitee-invite-cousin-lina
Permissions mapped: 20
La Sala access decision
allowedLina sample relative has fixture La Sala access after invitation acceptance, account binding, and membership placement.
Route: /sala
Audit preview
previewmembership.access.granted.preview
Provider activation still requires durable persistence, rollback behavior, and production route enforcement.
Invitation delivery boundary
fixture-onlyInvitation acceptance may now return a fixture acceptance record, account/profile binding, membership placement, La Sala access decision, and audit preview. It still does not send provider messages or write production data.
Provider mutation mode: fixture-only
Membership grant boundary
blocked-until-approved-runtime-laneReal delivery and membership placement require provider delivery configuration, token persistence, authenticated account binding, durable membership storage, route guard enforcement, audit records, revocation, and rollback.
Fixture invitations: 2
No live delivery
Delivery and grant requirement map
- Invitation draft and Steward review — fixture-preview-only
Show fixture invitation drafts and Custodio Familiar review language.
Future requirement: Future delivery requires a reviewed invite record, intended role, family-book scope, recipient contact, and Steward approval boundary.
Protected-care requirement: Connected relations, minors, protected people, and sensitive roles require explicit Steward review before delivery.
- Delivery provider — delivery-requirements-defined
Describe delivery requirements without sending email, SMS, push, or provider messages.
Future requirement: Future delivery requires configured provider credentials outside git, sender identity, retry limits, bounce handling, unsubscribe/abuse controls, and delivery audit evidence.
Protected-care requirement: Delivery content must reveal the minimum context needed and must not expose private family memories before acceptance.
- Token and expiration — delivery-requirements-defined
Preview fixture token shape and expiration expectations only.
Future requirement: Future acceptance requires single-use token lookup, expiration, revocation, replay protection, rate limiting, and safe failure states.
Protected-care requirement: Expired, revoked, or disputed invites must not reveal private family membership or family contents.
- Acceptance record — fixture-membership-access-result
Resolve a fixture acceptance record for the invited person without sending provider messages or writing production data.
Future requirement: Future acceptance requires single-use token lookup, expiration, revocation, replay protection, rate limiting, and safe failure states.
Protected-care requirement: Expired, revoked, or disputed invites must not reveal private family membership or family contents.
Invitation acceptance result
fixture-persistedFixture workflow
Fixture invitation acceptance workflow preview completed. Invitation acceptance now resolves a fixture account binding, membership placement, La Sala access decision, and audit preview.
Persistence: fixture. Provider mutation: fixture-only.