Repository navigation
Conversation
The profile said an unmerged review branch held the work and that a merge decision and deployment remained open. Both have happened: the retired classifieds product is removed on the default branch and a Khmer-first public surface for the current direction serves at bayonhub.com. What has not happened is the part worth being careful about, so the row now says it — the student, employer and admin flows are not demonstrated behind that page, and a landing page is not a working platform. That phrase replaces "unmerged review branch" in the verifier's required terms, because the check was doing its job and pinning a claim; the claim was simply no longer true. A check that guards a stale fact stops being a guard and becomes the reason the staleness survives. Verified both directions: the verifier fails when the new boundary is removed and passes when it is restored.
Member
Author
|
Superseded by #16, merged 2026-09-20. This PR's row describes BayonHub as an unmerged review branch; the product has been live on labelled sample data since 2026-09-15, so merging this would make the profile false again. |
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.
The profile said BayonHub's work sat on an unmerged review branch with a merge
decision and deployment still open. Both have since happened:
bayonhub.comserves a Khmer-first surface for the current directionThe row now says that, and says the part worth being careful about: the student,
employer and admin flows are not demonstrated behind that page. A landing
page is not a working platform.
On the verifier
scripts/verify_profile.pyrequired the literal phraseunmerged review branch.That check was doing exactly its job — pinning the evidence boundary so the copy
cannot quietly drift. The claim it pinned had simply stopped being true.
So the required term moves with the boundary rather than being deleted:
a landing page is not a working platform. A check that guards a stale fact isno longer a guard; it is the reason the staleness survives.
Verified in both directions — the verifier exits 1 when the new boundary is
removed from the README and 0 when it is restored.
Also
The commit uses the account no-reply address, which
verify_commit_identityrequires. Note that the current
mainHEAD does not: it carries a personaladdress and fails that check today, independently of this change.
All six product links published on the profile were probed and answer 200.