Record / Homes & placesPermalink ↗
Context reference
A place and why it matters, with explicit guest-profile or trip scope.
- Viewer ID
zendo/context-reference- Identity
- context.referencePoints[].id
- Owner
- Concierge confirms; Hermes may propose.
Fields 18
| Field | Contract |
|---|---|
idRequired | stringStable record ID; on Guest Profile, the legacy guest-ID alias. Schema constraints{
"type": "string",
"maxLength": 120
} |
guestIdRequired | stringThe Guest this record concerns. Schema constraints{
"type": "string",
"maxLength": 120
} |
scopeRequired | guest | briefGuest-profile or active-trip ownership of a place reference. Schema constraints{
"enum": [
"guest",
"brief"
]
} |
briefIdRequired | string | nullActive trip reference for trip scope; null for reusable guest scope. Schema constraints{
"type": [
"string",
"null"
]
} |
labelRequired | stringSchema constraints{
"type": "string",
"minLength": 1,
"maxLength": 120
} |
categoryRequired | Work | Lifestyle | Transport | OtherSchema constraints{
"enum": [
"Work",
"Lifestyle",
"Transport",
"Other"
]
} |
latRequired | numberSchema constraints{
"type": "number",
"minimum": 49.15,
"maximum": 49.4
} |
lngRequired | numberSchema constraints{
"type": "number",
"minimum": -123.35,
"maximum": -122.9
} |
notesRequired | stringOrdinary freeform notes in the owning record. Schema constraints{
"type": "string",
"maxLength": 2000
} |
statusRequired | suggested | confirmedSchema constraints{
"enum": [
"suggested",
"confirmed"
]
} |
placeIdOptional | string | nullSchema constraints{
"type": [
"string",
"null"
]
} |
sourceRequired | objectSchema constraints{
"type": "object"
} |
createdByRequired | objectSchema constraints{
"type": "object"
} |
updatedByRequired | objectSchema constraints{
"type": "object"
} |
confirmedByRequired | object | nullSchema constraints{
"type": [
"object",
"null"
]
} |
relationshipOptional | pinned | relevant | profile-context | itinerary-optionPinned guest preference, relevant trip place, or unclassified older profile context. Schema constraints{
"enum": [
"pinned",
"relevant",
"profile-context",
"itinerary-option"
],
"description": "Reference role. itinerary-option is a brief-scoped candidate place, not a reservation, scheduled visit or durable guest favourite."
} |
preferenceEvidenceOptional | object | nullThe guest’s expressed interest as recorded by the concierge; not authenticated guest approval. Schema constraints{
"type": [
"object",
"null"
],
"description": "Guest-stated interest, recordedBy/recordedAt and guestConfirmation null. Required by service for new profile pins."
} |
planningOriginOptional | object | nullServer-verified source session, point and dataset lineage. Schema constraints{
"type": [
"object",
"null"
],
"description": "Planning session/point IDs, dataset hash, original source/evidence and generating actor, assigned by service."
} |
Scope & rules
- Guest scope is reusable and has no brief ID. Trip scope binds to the active brief.
- Suggested context is not treated as a confirmed fact.
- Creator, source and confirming concierge are separate attributions.
- New profile pins require a concierge-recorded statement of the guest’s expressed interest. Hermes cannot pin profile favourites.
- Earlier guest references remain profile-context until explicitly reviewed; no liking is inferred by migration.
- Explicit promotion from a planning point carries its source session and dataset lineage.
- Trip-scoped itinerary-option references are candidates, not scheduled visits, reservations or profile favourites.
Relationships 2
can referencePlace document 0..* → 0..1
may be promoted fromPlanning point 0..* → 0..1