Documented release
v47.8.0
contacts continuity hardening
Release date 2026-04-10
Outcome
Outcome
v47.8.0 is the contacts continuity hardening release. It keeps the durable CRM foundation from v47.7.0, then closes the public-twin and guest-contact gap so the same relationship record can carry twin exchanges, guest identifiers, direct messaging handoff, calendar continuity, and mobile-visible identity context without splitting the person across separate lanes.
Changes
What changed
guest visitors are saved as contact records
guest visitors are saved as contact records
Technical and authority boundary
guest visitors are saved as contact records
- Why
- v47.8.0 is the contacts continuity hardening release. It keeps the durable CRM foundation from v47.7.0, then closes the public-twin and guest-contact gap so the same relationship record can carry twin exchanges, guest identifiers, direct messaging handoff, calendar continuity, and mobile-visible identity context without splitting the person across separate lanes.
- Capability enabled
- guest visitors are saved as contact records
- Compatibility
- The v47.8.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.8.0 migration record remains the exact adoption boundary for this outcome.
the same visitor and thread continuity keys stay attached to that record
the same visitor and thread continuity keys stay attached to that record
Technical and authority boundary
the same visitor and thread continuity keys stay attached to that record
- Why
- v47.8.0 is the contacts continuity hardening release. It keeps the durable CRM foundation from v47.7.0, then closes the public-twin and guest-contact gap so the same relationship record can carry twin exchanges, guest identifiers, direct messaging handoff, calendar continuity, and mobile-visible identity context without splitting the person across separate lanes.
- Capability enabled
- the same visitor and thread continuity keys stay attached to that record
- Compatibility
- The v47.8.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.8.0 migration record remains the exact adoption boundary for this outcome.
later authenticated identity can enrich the same person instead of forking history 2
later authenticated identity can enrich the same person instead of forking history 2. Twin, Calendar, And Contact Continuity Stay Deterministic The operator should not have to mentally reconcile separate systems:
Technical and authority boundary
later authenticated identity can enrich the same person instead of forking history 2. Twin, Calendar, And Contact Continuity Stay Deterministic The operator should not have to mentally reconcile separate systems:
- Why
- v47.8.0 is the contacts continuity hardening release. It keeps the durable CRM foundation from v47.7.0, then closes the public-twin and guest-contact gap so the same relationship record can carry twin exchanges, guest identifiers, direct messaging handoff, calendar continuity, and mobile-visible identity context without splitting the person across separate lanes.
- Capability enabled
- later authenticated identity can enrich the same person instead of forking history 2. Twin, Calendar, And Contact Continuity Stay Deterministic The operator should not have to mentally reconcile separate systems:
- Compatibility
- The v47.8.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.8.0 migration record remains the exact adoption boundary for this outcome.
world action-ledger entries materialize contact events
world action-ledger entries materialize contact events
Technical and authority boundary
world action-ledger entries materialize contact events
- Why
- v47.8.0 is the contacts continuity hardening release. It keeps the durable CRM foundation from v47.7.0, then closes the public-twin and guest-contact gap so the same relationship record can carry twin exchanges, guest identifiers, direct messaging handoff, calendar continuity, and mobile-visible identity context without splitting the person across separate lanes.
- Capability enabled
- world action-ledger entries materialize contact events
- Compatibility
- The v47.8.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.8.0 migration record remains the exact adoption boundary for this outcome.
calendar projections continue to attach meeting events to the same contact
calendar projections continue to attach meeting events to the same contact
Technical and authority boundary
calendar projections continue to attach meeting events to the same contact
- Why
- v47.8.0 is the contacts continuity hardening release. It keeps the durable CRM foundation from v47.7.0, then closes the public-twin and guest-contact gap so the same relationship record can carry twin exchanges, guest identifiers, direct messaging handoff, calendar continuity, and mobile-visible identity context without splitting the person across separate lanes.
- Capability enabled
- calendar projections continue to attach meeting events to the same contact
- Compatibility
- The v47.8.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.8.0 migration record remains the exact adoption boundary for this outcome.
the contact history remains deduped by deterministic event keys 3
the contact history remains deduped by deterministic event keys 3. Mobile Contact Handling Stays Legible The mobile CRM view should explain who this person is:
Technical and authority boundary
the contact history remains deduped by deterministic event keys 3. Mobile Contact Handling Stays Legible The mobile CRM view should explain who this person is:
- Why
- v47.8.0 is the contacts continuity hardening release. It keeps the durable CRM foundation from v47.7.0, then closes the public-twin and guest-contact gap so the same relationship record can carry twin exchanges, guest identifiers, direct messaging handoff, calendar continuity, and mobile-visible identity context without splitting the person across separate lanes.
- Capability enabled
- the contact history remains deduped by deterministic event keys 3. Mobile Contact Handling Stays Legible The mobile CRM view should explain who this person is:
- Compatibility
- The v47.8.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.8.0 migration record remains the exact adoption boundary for this outcome.
guest and authenticated continuity status is visible in the snapshot
guest and authenticated continuity status is visible in the snapshot
Technical and authority boundary
guest and authenticated continuity status is visible in the snapshot
- Why
- v47.8.0 is the contacts continuity hardening release. It keeps the durable CRM foundation from v47.7.0, then closes the public-twin and guest-contact gap so the same relationship record can carry twin exchanges, guest identifiers, direct messaging handoff, calendar continuity, and mobile-visible identity context without splitting the person across separate lanes.
- Capability enabled
- guest and authenticated continuity status is visible in the snapshot
- Compatibility
- The v47.8.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.8.0 migration record remains the exact adoption boundary for this outcome.
visitor/thread keys are searchable and inspectable when needed
visitor/thread keys are searchable and inspectable when needed
Technical and authority boundary
visitor/thread keys are searchable and inspectable when needed
- Why
- v47.8.0 is the contacts continuity hardening release. It keeps the durable CRM foundation from v47.7.0, then closes the public-twin and guest-contact gap so the same relationship record can carry twin exchanges, guest identifiers, direct messaging handoff, calendar continuity, and mobile-visible identity context without splitting the person across separate lanes.
- Capability enabled
- visitor/thread keys are searchable and inspectable when needed
- Compatibility
- The v47.8.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.8.0 migration record remains the exact adoption boundary for this outcome.
follow-up actions stay available from the same contact surface
follow-up actions stay available from the same contact surface
Technical and authority boundary
follow-up actions stay available from the same contact surface
- Why
- v47.8.0 is the contacts continuity hardening release. It keeps the durable CRM foundation from v47.7.0, then closes the public-twin and guest-contact gap so the same relationship record can carry twin exchanges, guest identifiers, direct messaging handoff, calendar continuity, and mobile-visible identity context without splitting the person across separate lanes.
- Capability enabled
- follow-up actions stay available from the same contact surface
- Compatibility
- The v47.8.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v47.8.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
v47.8.0 is the contacts continuity hardening release. It keeps the durable CRM foundation from v47.7.0, then closes the public-twin and guest-contact gap so the same relationship record can carry twin exchanges, guest identifiers, direct messaging handoff, calendar continuity, and mobile-visible identity context without splitting the person across separate lanes.
Available outcomes
Capabilities now available
guest visitors are saved as contact records
guest visitors are saved as contact records
the same visitor and thread continuity keys stay attached to that record
the same visitor and thread continuity keys stay attached to that record
later authenticated identity can enrich the same person instead of forking history 2
later authenticated identity can enrich the same person instead of forking history 2. Twin, Calendar, And Contact Continuity Stay Deterministic The operator should not have to mentally reconcile separate systems:
world action-ledger entries materialize contact events
world action-ledger entries materialize contact events
calendar projections continue to attach meeting events to the same contact
calendar projections continue to attach meeting events to the same contact
the contact history remains deduped by deterministic event keys 3
the contact history remains deduped by deterministic event keys 3. Mobile Contact Handling Stays Legible The mobile CRM view should explain who this person is:
guest and authenticated continuity status is visible in the snapshot
guest and authenticated continuity status is visible in the snapshot
visitor/thread keys are searchable and inspectable when needed
visitor/thread keys are searchable and inspectable when needed
follow-up actions stay available from the same contact surface
follow-up actions stay available from the same contact surface
Primitive boundary
Primitives affected
- identity
- provenance
- verification
- public-witness
- local-truth
- continuity
- note
- governance
Compatibility
Compatibility
Archive compatibility evidence boundary
No dedicated compatibility record is bound to this projection.
Treat compatibility as unknown; version or date proximity is not evidence.
Migration
Migration
Required: unknown
No explicit migration source is bound; no migration is inferred from dates.
Qualification
Conformance
No immutable conformance evidence is assigned in this projection.
Control boundary
Governance
- Verification
- Unknown
- Declared change class
- No separate classification record
- Release approval
- No separate approval record
- Risk owner
- No separate assignment recorded
Publication, deployment, production smoke, and attestation remain independent evidence dimensions unless exact sources establish them.
Registry boundary
Registry
No registry is bound where the canonical release family does not carry one.
Archive projection
Audience, domain, and change-kind facets
- Audiences
- developers · businesses · creators · institutions · people
- Domains
- identity · provenance · verification · public-witness · local-truth · continuity · note · governance
- Change kinds
- capability
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Present
- Package publication
- Unknown
- Deployment
- Unknown
- Production smoke
- Unknown
- Signed attestation
- Unknown
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 2ee2b65ec90e9d71fa09911d19e05c717c1e95567b328c8b68c54cf9715a3ae7. Source-family inventory: complete.
SHA-256 b39c5d347c73a4c3284dc3b2237527491b1a61c59f41db72482627fb174c4ecbSHA-256 11613d3c4ada117909f05e9715aa9e863bd5145441476243b2afdaf3b7059359SHA-256 ade4e8a478cf9ae12ef47aeb03c193ed6ab839454e283f84ae6d6ac865cd6ad2SHA-256 f7398e292973912a52b1ec176819890dfe6365206ab83d76c5ee91251d3d6b28