Skip to content

The model names what a reader's sign-in keeps - #83

Merged
robertblust merged 1 commit into
mainfrom
readers-sign-in
Oct 25, 2026
Merged

robertblust merged 1 commit into
mainfrom
readers-sign-in

Conversation

@robertblust

@robertblust robertblust commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

Readers the owner invites now sign in to the chat at id.blust.ch, and guestgraph.io's privacy page draws what the site keeps and sends from this model, so the model holds it. The widget's three new keys are stored items: chat-signin, the access and ID tokens, kept until the reader signs out, the chat refuses the token or the visitor clears it; chat-choice, the chosen model and effort; and chat-pkce, in the tab only for the trip to the login and back. Two activities join the chat's: Signing a reader in, the name, email address and roles id.blust.ch keeps with Google Cloud in Zurich and the access token each message carries, and Counting a reader's month, the month's cost the chat keeps under a key it cannot turn back into the account.

Google Cloud's page names the readers' month, and the accounts blust.ch's identity service keeps in the same region; the question log's personal data says it holds nothing of a sign-in. The model has no system type, so id.blust.ch is named by the activity and the processor, as blust.ch's own model names it. The facts are read from guestgraph.io's privacy page, design v0.158.1's assets/chat.js, chat-server v0.38.1's README and lib/meter.mjs, and the README of robertblust/id-blust-ch. Both activities rest on legitimate interests, as the chat's do, which is the owner's to confirm with each entry.

The same entries go into the other two models in robertblust/mental-model#290 and companygraph/mental-model#142.

Verified: npx github:companygraph/meta-model#v0.94.0 check, sh conventions/conventions-check, sh conventions/conventions-sync check, each new and changed page read against its schema's writing rules, and design's pathOf and privacyStrings run on this branch against guestgraph.github.io's build/privacy.de.json.

🤖 Generated with Claude Code

Readers the owner invites now sign in to the chat at id.blust.ch, and guestgraph.io's privacy page draws what the site keeps and sends from this model, so the model holds it. The widget's three new keys are stored items: chat-signin, the access and ID tokens, kept until the reader signs out, the chat refuses the token or the visitor clears it; chat-choice, the chosen model and effort; and chat-pkce, in the tab only for the trip to the login and back. Two activities join the chat's: Signing a reader in, the name, email address and roles id.blust.ch keeps with Google Cloud in Zurich and the access token each message carries, and Counting a reader's month, the month's cost the chat keeps under a key it cannot turn back into the account.

Google Cloud's page names the readers' month, and the accounts blust.ch's identity service keeps in the same region; the question log's personal data says it holds nothing of a sign-in. The model has no system type, so id.blust.ch is named by the activity and the processor, as blust.ch's own model names it. The facts are read from guestgraph.io's privacy page, design v0.158.1's assets/chat.js, chat-server v0.38.1's README and lib/meter.mjs, and the README of robertblust/id-blust-ch. Both activities rest on legitimate interests, as the chat's do, which is the owner's to confirm with each entry.

Verified: npx github:companygraph/meta-model#v0.94.0 check, sh conventions/conventions-check, sh conventions/conventions-sync check, each new and changed page read against its schema's writing rules, and design's pathOf and privacyStrings run on this branch against guestgraph.github.io's build/privacy.de.json.

Process: Delivery
Phase: Implement
Track: Code
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@robertblust
robertblust merged commit 2a1852a into main Oct 25, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant