Atlas person calendar credentials
Which stored secret each of a person's calendars points at
1 Oct 2026 · branch p3-cred-r2-person-calendars · captured against propflow-stage · at 77a296a719b
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · A test person with a tour calendar and one calendar endpoint
A sandbox company's team member with two calendar connections. The first is the one tours book into, and its attachment id is the stored key. The second is a calendar endpoint. Its key encodes the calendar account's address, so it is withheld and the page says so. The two connections point at different credential references, which is what stage really holds, so neither shares a grant.
Masked for publishing: 7 × property-line, 1 × tester — PropFlow's own lines, as listed in config/phone-registry.json. Any other phone number on the page was left in place for the contact scan.
Asserted in the captured DOM — Connection credentials · calendar (tours book here) · calendar (endpoint) · withheld — the key carries the calendar account address
Sections 2–2
2 · Negative control: a person with no calendar
A Fairhaven Residential (TEST) person with no calendar connection gets a plain sentence, not an empty table.
Masked for publishing: 7 × property-line, 1 × tester — PropFlow's own lines, as listed in config/phone-registry.json. Any other phone number on the page was left in place for the contact scan.
Asserted in the captured DOM — Connection credentials · This person has no live calendar connection.
