From 784a274557247ddb82e0ba91ca4b0cac4598efcd Mon Sep 17 00:00:00 2001 From: Robert Blust Date: Sun, 27 Sep 2026 18:18:07 +0200 Subject: [PATCH] The profile names the model's decisions and the site's vision GuestGraph's model gained eight decisions from the engine's specifications and guestgraph.io's home page now opens on the vision and values, and the chat answers a grouping as a table and a structure as a picture. The profile said none of it. The mental-model row and phase 10 name the decisions, the site row and its node in the second diagram name the vision, and the sentence under that diagram says how the chat answers. No phase is added. Verified: sh conventions/conventions-check and conventions-format pass. Co-Authored-By: Claude Opus 5.5 (1M context) --- profile/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/profile/README.md b/profile/README.md index 48297d9..ebc8cc8 100644 --- a/profile/README.md +++ b/profile/README.md @@ -11,8 +11,8 @@ Guest data lives scattered across the PMS, POS, booking engine, loyalty program, | [**engine**](https://github.com/guestgraph/engine) | The core: identity resolution engine, guest graph, REST API | | [**connector-apaleo**](https://github.com/guestgraph/connector-apaleo) | The first connector: reservations and bookings from Apaleo into the guest graph, a client of the engine's API | | [**service-conventions**](https://github.com/guestgraph/service-conventions) | The rules every service is held to by check: one parent build, one error shape, the architecture tests and the workflow, vendored by each service at a pinned release | -| [**guestgraph.github.io**](https://github.com/guestgraph/guestgraph.github.io) | The site at [guestgraph.io](https://guestgraph.io) โ€” landing page, the [model](https://guestgraph.io/model/) and its team, principles and surfaces, the API, billing, privacy, the [talks](https://guestgraph.io/talks/), and a chat that answers from the model | -| [**mental-model**](https://github.com/guestgraph/mental-model) | GuestGraph itself, described in [CompanyGraph](https://companygraph.io)'s vocabulary: vision, values, products, concepts and how the work is done | +| [**guestgraph.github.io**](https://github.com/guestgraph/guestgraph.github.io) | The site at [guestgraph.io](https://guestgraph.io) โ€” landing page with the vision and values, the [model](https://guestgraph.io/model/) and its team, principles and surfaces, the API, billing, privacy, the [talks](https://guestgraph.io/talks/), and a chat that answers from the model | +| [**mental-model**](https://github.com/guestgraph/mental-model) | GuestGraph itself, described in [CompanyGraph](https://companygraph.io)'s vocabulary: vision, values, products, concepts, the decisions the engine's specifications made and how the work is done | | [**mcp-guestgraph-io**](https://github.com/guestgraph/mcp-guestgraph-io) | [mcp.guestgraph.io](https://mcp.guestgraph.io), that model served to agents over MCP, and the chat beside it | **New here?** The [six-minute introduction](https://guestgraph.io/talks/intro/) is the fastest way in: why a returning guest looks like five strangers, what it costs to merge them wrongly, and how every decision stays explainable and reversible. DE ยท EN. @@ -59,7 +59,7 @@ Beside the product runs a second, smaller thing: GuestGraph's own model, the pro flowchart TB subgraph gg["guestgraph"] GGMM["mental-model
GuestGraph, described
in CompanyGraph's vocabulary"] - SITE["guestgraph.io
landing, the model pages,
the talk, the chat button"] + SITE["guestgraph.io
landing with the vision,
the model pages, the talk,
the chat button"] MCPGG["mcp.guestgraph.io
the model over MCP,
and chat.guestgraph.io"] end @@ -75,7 +75,7 @@ flowchart TB SITE -. "the chat button asks" .-> MCPGG ``` -An agent reaches the model at `https://mcp.guestgraph.io/mcp`, listed in the MCP Registry as `io.guestgraph/mental-model`, and a visitor asks it in their own words from the button at the foot of every page of guestgraph.io. How it is deployed is in [mcp-guestgraph-io](https://github.com/guestgraph/mcp-guestgraph-io#readme). +An agent reaches the model at `https://mcp.guestgraph.io/mcp`, listed in the MCP Registry as `io.guestgraph/mental-model`, and a visitor asks it in their own words from the button at the foot of every page of guestgraph.io, with a grouping answered as a table and a structure as a picture. How it is deployed is in [mcp-guestgraph-io](https://github.com/guestgraph/mcp-guestgraph-io#readme). ## ๐Ÿงฑ Principles @@ -98,7 +98,7 @@ Matching is layered by confidence: shared strong identifiers merge outright, pro 7. โœ… **Service conventions** โ€” every service has the same shape by check, not by hand, from [service-conventions](https://github.com/guestgraph/service-conventions) at a pinned release 8. โœ… **Shared runtime** โ€” one error shape and the few classes every service carries, vendored as source from the same release 9. โœ… **Removing a subscription** โ€” an operator takes a connection's Apaleo webhook subscription away and puts it back, so tearing a deployment down leaves nothing posting to a dead address -10. โœ… **GuestGraph's own model** โ€” [the project described](https://github.com/guestgraph/mental-model) in CompanyGraph's vocabulary: vision, values, strategies, products, the words it means something exact by and how the work is done, drawn on [guestgraph.io/model](https://guestgraph.io/model/), served to agents over MCP and answered from in the chat +10. โœ… **GuestGraph's own model** โ€” [the project described](https://github.com/guestgraph/mental-model) in CompanyGraph's vocabulary: vision, values, strategies, products, the words it means something exact by, the decisions its engine's specifications made and how the work is done, drawn on [guestgraph.io/model](https://guestgraph.io/model/), served to agents over MCP and answered from in the chat Connectors for more PMS, POS, and booking systems are next. What a phase decided, and the requirements waiting for a later one, are in the engine's [roadmap notes](https://github.com/guestgraph/engine/blob/main/docs/roadmap-notes.md), which feed each slice's specification.