Repository navigation
Say BayonHub is live on sample data, and pin the new boundary - #16
Merged
Merged
Conversation
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>
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
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.
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
/apion its own origin from the API on Vercel, with Neon PostgreSQL and Upstash Redis in Singapore.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.pycovers both the badge and the table row.Accountable human: @kavatana. Risk tier: R0 — public copy plus a repository check.
Verification
python3 scripts/verify_profile.py,CHNAI_COMMIT_SHAon this headpython3 -m unittest discover -s tests -vRan 12 tests,OKpython3 -m py_compile scripts/verify_profile.pygit diff --check "$(git merge-base origin/main HEAD)" HEADprofile/README.md is missing required terms: No real employers, openings, placements, or users<sub>Branch under review</sub>, then the verifierPublic claim surface contains stale or overbroad framing: stale branch-as-evidence framing: profile/README.md254592578+kavatana@users.noreply.github.com, soverify_commit_identitypasses on the headhttps://bayonhub.com/200,https://bayonhub-app.vercel.app/200,/api/health/live200 on both hosts;bayonhub-api.vercel.app/api/healthreturnsstatus: ok,db: ok,redis: ok;/api/capabilitiesreturns sample data enabled,email.delivery: none,uploads.avatars: falseprofile/README.md4 lines,scripts/verify_profile.py9,tests/test_verify_profile.py12Every 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