Record / Homes & placesPermalink ↗
Planning session
A working map dataset of generated references. It can be kept with the brief for later review without becoming requirements or favourites.
- Viewer ID
zendo/planning-session- Identity
- planningSession.id; retained snapshots in planningSessions[].id
- Owner
- Concierge/Hermes planning workflow, linked to one guest and brief revision.
Fields 16
| Field | Contract |
|---|---|
schemaRequired | "zendo.planning-session/v1"Schema constraints{
"const": "zendo.planning-session/v1"
} |
idRequired | stringStable record ID; on Guest Profile, the legacy guest-ID alias. Schema constraints{
"type": "string"
} |
guestIdRequired | stringThe Guest this record concerns. Schema constraints{
"type": "string"
} |
briefIdRequired | stringActive trip reference for trip scope; null for reusable guest scope. Schema constraints{
"type": "string"
} |
briefRevisionRequired | integerSchema constraints{
"type": "integer",
"minimum": 1
} |
inputRequired | objectSchema constraints{
"type": "object"
} |
inputHashRequired | stringDigest of the profile/brief/reference input used to detect stale planning context. Schema constraints{
"type": "string"
} |
workspaceVersionRequired | integerSchema constraints{
"type": "integer",
"minimum": 1
} |
createdByRequired | objectSchema constraints{
"type": "object"
} |
createdAtRequired | stringSchema constraints{
"type": "string"
} |
methodRequired | stringSchema constraints{
"type": "string"
} |
retentionRequired | working | retainedWorking map or retained brief-linked review snapshot. Schema constraints{
"enum": [
"working",
"retained"
]
} |
pointsRequired | arraySchema constraints{
"type": "array",
"maxItems": 50,
"items": {
"$ref": "#/$defs/PlanningPoint"
}
} |
datasetHashRequired | stringIntegrity fingerprint of the exact generated point dataset; not signed external proof. Schema constraints{
"type": "string"
} |
keptAtOptional | stringSchema constraints{
"type": "string"
} |
keptByOptional | objectSchema constraints{
"type": "object"
} |
Scope & rules
- Generate replaces only the working map; keep freezes a separate brief-linked review snapshot.
- Working sessions survive local restart until regenerated or discarded. No automatic expiry is claimed.
- Keep preserves inputs, revisions, point sources, generating actor, method and dataset hash. No evaluation or training is executed.
- Changed profile/brief/reference inputs mark the working map stale. Historical snapshots retain their original meaning.
- Discard removes only the working dataset. Kept snapshots and operational history remain.
Relationships 2
plans forTrip brief 0..* → 1
contains generated referencePlanning point 1 → 0..*