docs: reflect shared core-postgres migration (v1.0.2) - #6
Merged
Conversation
Update README, docs/architecture.md, AGENTS.md, and .env.example comments so they describe the post-consolidation database topology: Branchy stores its durable state in a `branchy` schema and delegates Telegram identity/presence to a shared `core` schema (`core.person`/`core.chat`) via `core.touch`. In production this lives in the shared `core-postgres`, reached on a single pool with `search_path=branchy`; local `docker compose` seeds a minimal `core` schema (deploy/core-init.sql) so migrations boot. The durable Postgres outbox messaging is unchanged (the outbox is a `branchy` table). Docs-only; no code changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GAeQtwgsRecG7D3Lc6RVuV
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation-only update reflecting the completed database consolidation (branchy is live on the shared
core-postgresas of v1.0.2). No application code, migrations, Dockerfiles, or compose service logic changed.What changed
branchyschema (subscriptions, outbox, OAuth/runtime state) plus delegated identity in the sharedcoreschema (core.person/core.chat, upserted viacore.touch); Quick Start notes the bundled compose seeds a localcoreschema; theDATABASE_URLconfig row documentssearch_path=branchy.core-postgres, thebranchyschema, FK-into-coreidentity, and the localcore-init.sqlseed; a new Decisions bullet covers the single pool,search_path=branchy, schema-qualifiedcore.touch, and the retiredbranchy-postgres.branchy/coresplit,search_path=branchy,core.touch, and the local seed; warns against recreating the droppedtelegram_users/telegram_chatstables.DATABASE_URLexplaining the schema layout andoptions=-csearch_path%3Dbranchy.The durable Postgres outbox / reliable-delivery messaging is preserved (the outbox is a
branchytable). Release notes are not duplicated —CHANGELOG.md(v1.0.2 / v1.0.3) remains the source of truth.Verification
Every DB claim was checked against the repo:
migrations/001_init.sqlheader + FKs intocore.*,internal/db/db.go(SELECT core.touch(...)),deploy/core-init.sql,docker-compose.yml(options=-csearch_path%3Dbranchy),internal/config/config.go(singleDATABASE_URL, noCORE_DATABASE_URL), and the CHANGELOG. The production role namebranchy_coreis not present in the repo (deploy-time credential) — it is stated per the migration authoritative context, not verifiable from source.🤖 Generated with Claude Code