Skip to content

docs: governance reset + operational status sync#45

Closed
ByteStreams-AI wants to merge 1 commit intomainfrom
chore/governance-sync
Closed

docs: governance reset + operational status sync#45
ByteStreams-AI wants to merge 1 commit intomainfrom
chore/governance-sync

Conversation

@ByteStreams-AI
Copy link
Copy Markdown
Owner

@ByteStreams-AI ByteStreams-AI commented May 6, 2026

Refs #44

Sync AGENTS and developer journal with the May 5 governance reset and staging/prod operating model, plus local Claude settings update.

Greptile Summary

Documentation-only sync following the May 5, 2026 governance reset: AGENTS.md and the developer journal are brought up to date with the new two-environment staging/prod topology, four governance rules, and a day's worth of voice-path bisect work.

Confidence Score: 4/5

Safe to merge — all three files are documentation or local settings with no functional code changes.

The only concern introduced by this PR is committing live Telnyx phone numbers (staging and production) into the repository for the first time. Everything else — the governance narrative, journal entry, and git fetch permission — is straightforward documentation housekeeping with no code impact.

AGENTS.md — contains the newly committed phone numbers; worth a quick decision on whether this is intentional given the repo's visibility.

Security Review

  • Live phone numbers newly committed: +1 629 250 3998 (staging) and +1 629 600 1047 (production) Telnyx numbers appear in AGENTS.md and developer/developer-journal.md for the first time. If the repository is or becomes public these numbers are discoverable and could attract abuse traffic.
  • Supabase project refs (mxhyvvgjtqllohpvrwon, klzznfagrtormretqsgb) are already widely present across the codebase pre-PR and are not a new exposure here.
  • No secrets, tokens, API keys, or credentials were introduced by this PR.

Important Files Changed

Filename Overview
.claude/settings.json Adds git fetch * to the allowed Bash commands list — a routine and low-risk addition.
AGENTS.md Adds May 5 governance-reset block (two-environment topology, four governance rules, new doc pointers) and a new known-issue #8 (Telnyx SIP Connection vs Voice API Application name collision). Introduces live Telnyx phone numbers into the repo for the first time.
developer/developer-journal.md Adds a detailed May 5, 2026 journal entry covering governance reset, staging env provisioning, prod branch setup, three rounds of voice-path bisect, and the Telnyx routing misconfig discovery. Pure narrative documentation with no code changes.

Reviews (1): Last reviewed commit: "update docs" | Re-trigger Greptile

Greptile also left 1 inline comment on this PR.

Comment thread AGENTS.md
See [docs/project-status.md](docs/project-status.md) for milestone tracking and [developer/developer-journal.md](developer/developer-journal.md) for the chronological narrative.
**May 5, 2026 governance reset.** After PR #28→#30 regressed the voice-call path twice in a single afternoon, the team installed an operational gate around shipping. New baseline:

- Two-environment topology: `main` deploys to a staging cloud (`mxhyvvgjtqllohpvrwon` Supabase + `*-staging.dialtone.menu` Workers + `+1 629 250 3998` Telnyx); `prod` deploys to production (`klzznfagrtormretqsgb` + `*.dialtone.menu` + `+1 629 600 1047`). Releases are PRs `main → prod` after staging verification. Branch protection on `prod` enforces PR + CI + linear history + squash-only.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 security Live Telnyx phone numbers committed to the repository

The staging (+1 629 250 3998) and production (+1 629 600 1047) Telnyx numbers are new additions to the repo via this PR. If the repository is public (or becomes public), these numbers are discoverable and could attract spam/robocall traffic or testing abuse. Supabase project refs (mxhyvvgjtqllohpvrwon, klzznfagrtormretqsgb) are already present across many other files so this is not a new exposure for those — but the phone numbers only appear in the files touched by this PR.

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