Skip to content

Portal: unified-design surfaces (Policies, Users, Components, Agent Builder, Editor deploy) + Settings rebuild#6696

Open
reecebrowne wants to merge 9 commits into
mainfrom
portal-surfaces
Open

Portal: unified-design surfaces (Policies, Users, Components, Agent Builder, Editor deploy) + Settings rebuild#6696
reecebrowne wants to merge 9 commits into
mainfrom
portal-surfaces

Conversation

@reecebrowne

Copy link
Copy Markdown
Contributor

Builds the remaining developer-portal surfaces from the unified design and rebuilds Settings, on top of the portal scaffold merged in #6686. All tier-aware, mock-driven (MSW), componentised with Storybook coverage. Touches only frontend/portal + frontend/shared — the editor is untouched.

New surfaces

  • Policies — org-wide governance across the five categories (Ingestion / Security / Compliance / Routing / Retention) with a designer + per-doc-type overrides
  • Users — members, roles, invite, tier-scaled SSO/SCIM access
  • Components — embeddable @stirling/* SDK catalogue with per-action pricing
  • Getting Started — three-step funnel (use case → analyse a document → API key + snippets)
  • Agent Builder — agent lifecycle (scenarios, tool modes, evals/golden-sets, versions), reached from Sources
  • Editor deployment — deploy/pair/operate the editor (targets, pairing, health, credential rotation, air-gapped bundle), reached from Infrastructure

Reworks

  • Documents → review/approval queue (confidence, extractions, audit drawer, zero-standing-access elevation); the doc-type catalogue is retained as a second tab
  • Pipelines → golden-set pass column + "Promoted from the Editor" section
  • Infrastructure → new Models tab; deeper Security (managed / BYOK / HYOK + SOC 2 / ISO 27001 / HIPAA / GDPR / PCI attestations)
  • Home → "What runs on your PDFs" policy summary + tier-aware processing-status strip + pipeline-fork wizard

Settings & shared

  • New shared SettingsShell (grouped left-nav + content pane), modelled on the editor's account-settings modal so both apps can converge on one layout
  • Portal Settings rebuilt on it as scoped sections — Account / Workspace / Admin (Authentication, Active sessions, Early access)

Brand

  • Adopt the editor's brand mark + favicon; sidebar reads Stirling Processor; app-switcher labels the active app "Processor"

Mock contract

  • Every surface follows the 3-layer pattern (typed api/* → MSW handler → fixtures); new endpoints documented in MOCKS.md. The read contract is backend-ready; writes are marked // TODO(backend): <METHOD> <path>.

Verification

  • tsc (portal + shared) ✓ · eslint ✓ · dpdm (no circular) ✓ · build:portal ✓ · storybook:build ✓ · Prettier ✓

Deferred (noted, not in scope)

  • Unified shell / auth / role→surface routing / Workspace=Plan (architectural epic)
  • Tier rename (Editor / Processor / Bespoke) and the Usage flat-pricing + PAYG quick-amounts + Bespoke modal
  • Editor adopting the shared SettingsShell; converting marked write-stubs into live api/ seams

…er; rework Documents into a review queue; add Infrastructure Models tab

Build out the portal surfaces from the unified design — all tier-aware,
mock-driven (MSW), componentised with Storybook coverage:
- Policies: org-wide governance across the five categories (Ingestion,
  Security, Compliance, Routing, Retention) with a designer + per-doc-type
  overrides
- Users: team members, roles, invites, tier-scaled SSO/SCIM access controls
- Components: embeddable @stirling/* SDK widget catalogue with per-action pricing
- Getting started: three-step funnel (use case -> analyse a document ->
  API key + snippets)
- Agent Builder: agent lifecycle — scenarios, tool modes, evals/golden sets,
  version history
- Documents: reworked from a doc-type catalogue into a review/approval queue
  (confidence, extractions, audit, zero-standing-access elevation); the
  catalogue is retained as a second tab
- Infrastructure: new Models tab (catalogue + routing rules)

Wire routes, nav, icons and mock handlers; document the new endpoints in MOCKS.md.
…eployment

- Home: surface the five policy categories ("What runs on your PDFs") with
  configure/turn-on links into Policies, a tier-aware processing-status strip,
  and a pipeline-fork wizard over starter templates
- Pipelines: golden-set pass column on the deployed fleet + a "Promoted from
  the Editor" section with promote-to-policy
- Infrastructure → Security: encryption key management (managed / BYOK / HYOK)
  and compliance attestations (SOC 2, ISO 27001, HIPAA, GDPR, PCI)
- Editor deployment: a portal surface to deploy, pair, and operate the editor
  (targets, pairing methods, health, credential rotation, air-gapped bundle),
  reached from Infrastructure
- App switcher labels the active app "Processor"
Extract a reusable two-pane settings layout (grouped left-nav rail + content
pane with sticky header and footer) into shared/components, modelled on the
editor's account-settings modal so both apps can present settings the same way.

Rebuild the portal Settings on it: replace the flat horizontal tabs with
grouped scopes — Account (Profile, Appearance, Notifications), Workspace
(General), Admin (Authentication, Active sessions, Early access) — splitting the
former Preferences/Admin tabs into their own sections.
@dosubot dosubot Bot added size:XXL This PR changes 1000+ lines ignoring generated files. enhancement New feature or request labels Jun 16, 2026
@stirlingbot stirlingbot Bot added Documentation Improvements or additions to documentation Front End Issues or pull requests related to front-end development and removed enhancement New feature or request labels Jun 16, 2026
@stirlingbot

stirlingbot Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

🚀 V2 Auto-Deployment Complete!

Your V2 PR with embedded architecture has been deployed!

🔗 Direct Test URL (non-SSL) http://54.175.155.236:6696

🔐 Secure HTTPS URL: https://6696.ssl.stirlingpdf.cloud

This deployment will be automatically cleaned up when the PR is closed.

🔄 Auto-deployed for approved V2 contributors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Improvements or additions to documentation Front End Issues or pull requests related to front-end development size:XXL This PR changes 1000+ lines ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant