Skip to content

Say where BayonHub actually is, and pin the new boundary - #10

Closed
kavatana wants to merge 1 commit into
mainfrom
fix/bayonhub-evidence-boundary
Closed

kavatana wants to merge 1 commit into
mainfrom
fix/bayonhub-evidence-boundary

Conversation

@kavatana

Copy link
Copy Markdown
Member

The profile said BayonHub's work sat on an unmerged review branch with a merge
decision and deployment still open. Both have since happened:

  • the default branch's latest commit removes the retired classifieds product
  • bayonhub.com serves a Khmer-first surface for the current direction

The 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.py required the literal phrase unmerged 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 is
no 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_identity
requires. Note that the current main HEAD does not: it carries a personal
address and fails that check today, independently of this change.

All six product links published on the profile were probed and answer 200.

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.
@kavatana

Copy link
Copy Markdown
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.

@kavatana kavatana closed this Sep 20, 2026
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