Skip to content

Say BayonHub is live on sample data, and pin the new boundary - #16

Merged
kavatana merged 1 commit into
mainfrom
fix/bayonhub-truth
Sep 20, 2026
Merged

kavatana merged 1 commit into
mainfrom
fix/bayonhub-truth

Conversation

@kavatana

Copy link
Copy Markdown
Member

What changed and why

The profile put BayonHub's work on an unmerged review branch, with the merge decision and deployment still open. Both have happened: Phases 1-5 merged on 2026-08-27, and the product was released on 2026-09-15. bayonhub.com and bayonhub-app.vercel.app both serve it, each answering /api on its own origin from the API on Vercel, with Neon PostgreSQL and Upstash Redis in Singapore.

  • The tile badge: "Branch under review" becomes "Live on sample data".
  • The evidence boundary row: live at bayonhub.com on fictional sample data, labelled Sample and restored daily; students register, save and apply, employers post and move applications; no real employers, openings, placements or users; email delivery, admin two-factor sign-in, password reset and avatar uploads are not in place.
  • scripts/verify_profile.py: the required phrase moves with the boundary it pins, the way it did when the branch claim was pinned. "unmerged review branch" becomes "No real employers, openings, placements, or users", and a new stale-claim pattern rejects branch-as-evidence framing in the public claim files. tests/test_verify_profile.py covers both the badge and the table row.

Accountable human: @kavatana. Risk tier: R0 — public copy plus a repository check.

Verification

Check Result
python3 scripts/verify_profile.py, CHNAI_COMMIT_SHA on this head exit 0
python3 -m unittest discover -s tests -v Ran 12 tests, OK
python3 -m py_compile scripts/verify_profile.py exit 0
git diff --check "$(git merge-base origin/main HEAD)" HEAD exit 0
Remove the new boundary sentence, then the verifier exit 1: profile/README.md is missing required terms: No real employers, openings, placements, or users
Restore <sub>Branch under review</sub>, then the verifier exit 1: Public claim surface contains stale or overbroad framing: stale branch-as-evidence framing: profile/README.md
Restore "unmerged review branch" in the row, then the verifier exit 1: the same stale-framing failure
Commit author and committer 254592578+kavatana@users.noreply.github.com, so verify_commit_identity passes on the head
Production, read-only, 2026-09-15 https://bayonhub.com/ 200, https://bayonhub-app.vercel.app/ 200, /api/health/live 200 on both hosts; bayonhub-api.vercel.app/api/health returns status: ok, db: ok, redis: ok; /api/capabilities returns sample data enabled, email.delivery: none, uploads.avatars: false
Diff profile/README.md 4 lines, scripts/verify_profile.py 9, tests/test_verify_profile.py 12

Every changed sentence comes from the release record in the vault note (projects/bayonhub.md, the 2026-09-15 entries) and from the read-only production checks above. Nothing about matching, moderation review or admin access is claimed, because admin routes still refuse every IP.

AI involvement

Claude Code (Claude Opus 5), as the studio-builder, working from the truth-pass brief. It read the vault's release record, checked production read-only, rewrote the two lines and moved the pin.

The row is a public claim about the studio's own product, so a human confirms the wording against the vault entry before merge. No human has run a manual check for this PR.

Privacy impact

None. Public copy about a public product. No member data, credential, IP address or infrastructure detail appears; the demo accounts' addresses and password are not repeated here.

Rollback

Revert the squash commit. The profile renders from main, so the revert is the rollback.

For the operator

PR #10, "Say where BayonHub actually is, and pin the new boundary" (2026-08-29), changes these same two files to an intermediate truth: a deployed landing with no working product behind it. This supersedes it, so #10 wants closing rather than merging. I did not touch it.

🤖 Generated with Claude Code

The profile put BayonHub's work on an unmerged review branch, with the merge
decision and deployment still open. Both have happened: Phases 1-5 merged on
2026-08-27, and the product was released on 2026-09-15. bayonhub.com and
bayonhub-app.vercel.app both serve it, each answering /api on its own origin
from the API on Vercel, with Neon PostgreSQL and Upstash Redis in Singapore.

The badge and the evidence boundary say that now, and they keep the part worth
being careful about: every company and opening is fictional sample data,
labelled Sample and restored daily, and there are no real employers, openings,
placements or users. Email delivery, admin two-factor sign-in, password reset
and avatar uploads are not in place.

The required phrase moves with the boundary it pins, as it did when the branch
claim was pinned: "unmerged review branch" becomes "No real employers,
openings, placements, or users". A stale-claim pattern now also rejects
branch-as-evidence framing in the public claim files, with a regression test
covering both the badge and the table row.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kavatana
kavatana merged commit 49ac9fb into main Sep 20, 2026
1 check passed
@kavatana
kavatana deleted the fix/bayonhub-truth branch September 20, 2026 14:36
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