IV-122: serve Structured through the Construct staging gateway - #11
Merged
Conversation
Prompt: Keep component specimens in a compact multi-column layout, let masonry absorb vertical gaps, distinguish category and type filters, and use neutral gray for the non-primary nav button.
Prompt: Can you have staging on the live domain? You can add clerk auth for access and make sure samir@interspace.ventures has access. Should be staging.structured.glass.
Prompt: Audit the mobile design, replace icon-only navigation with a clear hamburger menu, left-align mobile hierarchy, fix broken narrow-width components, remove ghost and link from the button specimen, replace real-app placeholder copy with a coherent fictional science-fiction theme, and advise whether Structured should be surfaced through Exobase.
Prompt: why do the clerk sign ins get redirected to clerk auth urls though? I want them to be embedded on our site with our domains etc. this should be true for every Exobase app. Shouldn’t be a random url
Prompt: Clerk sign-ins and invitations should be embedded on each application domain rather than starting on a random Clerk-hosted URL.
Prompt: Add a subtle background grid, make gallery Category and Type selectors visually distinct from the background, and use one, two, or three gallery columns for mobile, laptop, and wide screens.
Allow the Structured staging renderer to serve the Construct gateway only when a constant-time server credential matches, while keeping direct browser access behind the existing staging boundary. User prompt: Approved
…ruct-page-upstream
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
1 participant
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.
Summary
stagingline with the renderer currently serving Structured staging/structured/base path and staging-only provider configurationSecurity boundary
The public Construct route authorizes the exact Exo grant
construct-page:structuredwithresource:read. This upstream change only accepts traffic that Construct has already authorized. Incorrect or absent secrets continue through the existing Structured staging auth boundary.Validation
BASE_PATH=/structured/asset paths verifiedorigin/stagingand the currently deployed renderer branch are ancestors of this headThe final post-merge validation was re-requested; pnpm 11 under local Node 26 stalled before emitting output, so GitHub CI remains an additional release gate.
Linear: https://linear.app/interspace/issue/IV-122
Staging only. No production deployment or redirect is included.