Add Gate demo ecosystem bridge - #38
Merged
Merged
Conversation
SemeAIPletinnya
marked this pull request as ready for review
August 1, 2026 04:58
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.
Cross-agent recovery
Recovered the one-file Gate demo bridge left by the interrupted Axiom premium task. No Gate logic, API behavior, receipt contract, or deployment configuration is changed.
Objective
Connect the existing
gate.semeai.techdemo surface back to the public SemeAI product ecosystem without turning the API surface into decorative UI.What changed
demo/saas_visible.html.Governance preserved
receipt_id: unchanged.Validation
python -m pytest— 104 passed.git diff --check— PASS.Deployment and rollback
After required checks and review pass, merge to
masterand use only the repository's existing GitHub Pages/deployment mechanism for the demo surface. No DNS, API, or infrastructure mutation is part of this PR. Rollback is a normal revert/redeploy of this isolated HTML change.