Protected workflow

Foundation demo boundary

This demo contains no catalogue, supplier, listing, inventory, publishing, credential, or irreversible workflow behavior. It only renders shared UI states and fake/local shell context.

Fake/local onlyNo live integrationsNo credentialsHuman approval required

Parallel slice foundation

Blazor foundation shell

Shared workspace context, workspace updates, connected workflow primitives, and production page patterns for future vertical slices.

Workspace shell ScopedOne circuit-level subscription to workspace-filtered workspace updates.
UI primitives ReusablePage, status, metric, filter, timeline, action, and card patterns.
External actions DisabledNo credentials, live provider calls, or irreversible mutations.
Approval model SeparateApproval UI states are distinct from edit access.

Workspace context

Workspace and update context

The shell subscribes once per circuit to workspace-filtered update notifications.

Development authentication only

This local cookie sign-in is deterministic test support; production OAuth, OIDC, SSO, and invite flows are intentionally deferred.

Sign in as development member

Workspace updates

Workspace update states

Routes should render update status near the page header and pause version-sensitive actions while workspace views are saving or need refresh.

Workspace updates: saving
Developer evidence
Global position
11
Correlation
foundation-demo-pending
Workspace view updates
No projection names reported.
Workspace updates: up to date
Developer evidence
Global position
12
Correlation
foundation-demo-fresh
Workspace view updates
FoundationDemoProjection, TimelineProjection
Workspace updates: needs refresh
Developer evidence
Global position
13
Correlation
foundation-demo-stale
Workspace view updates
TimelineProjection

Connected workflow

Connected lifecycle primitives

Routes compose these render-only helpers from their current workspace views so users can see lifecycle position, related work, evidence, and the next safe step.

Next safe action

Review pipeline blockers

Review the product decision record before opening packaging, listing, or launch readiness work.

Safe next steps point to workspace records and never send supplier, payment, warehouse, or live store changes.

Source and evidence

Reviewed sourceSource summary

Supplier catalogue summary is workspace-restricted and stored behind the asset-store abstraction.

Approval boundarySafety

Human approval remains required before protected supplier, payment, warehouse, or commerce actions.

Back to product workflow
Safe-language policy examples
  • Bare live publish label: Blocked — Action wording uses "publish" without fake, preview, simulation, record, read-only, external record, or approval required context.
  • Preview record label: Allowed — Action wording is safe.
Reusable states Reusable UI state patterns Loading, error, access, review, conflict, and approval examples.

Reusable states

Reusable UI state patterns

Future slices should compose these states instead of inventing one-off loading, error, access, review, update-conflict, or approval panels.

Empty state

No workspace records yet

This workspace view has no records to show yet. Capture safe context or connect related work to begin the workflow.

Loading

Loading workspace view

Waiting for workspace updates, product context, and source evidence to become available.

Approval pending

Approval pending

A human approver is reviewing the redacted approval reference. The action remains disabled until approval is granted.

Approval reference
Stable safe reference recorded for this review.
Safe handling
Only redacted summaries and stable references are shown in approval views.
Developer evidence
Snapshot hash
sha256:2a5d9f31c6e0b842
Payload evidence
Redacted approval payload evidence remains available for audit review only.
Product page primitives Shared status, filter, and timeline patterns Expandable route-building examples keep the demo page scannable.

Product page primitives

Shared page, status, metric, filter, and timeline patterns

These primitives give every route the same hierarchy while preserving feature-owned workflow behavior.

Status panels pair copy with semantic tone

Use them for freshness, warnings, success, blockers, safety notes, and save outcomes.

Example filter bar

3 safe demo rows

Visible labels stay attached to inputs.

Demo timeline

  1. Workspace context resolved

    Shell state is scoped to the active workspace.

  2. Workspace updates changed

    Routes use the same badge and status pattern.

  3. Safety copy preserved

    No live provider calls or irreversible actions are introduced.

Assets File asset UI patterns Safe metadata, redaction, missing content, and approval warning examples.

Assets

File asset UI patterns

Future catalogue, generated-media, and commerce slices should render safe file metadata while raw bytes remain behind the file asset store.

File asset reference

Summer 2026 supplier catalogue.pdf

Safe metadata only. Raw file bytes stay behind the file asset store and are not embedded in events or projections.

Workspace-scoped restricted distributionNeeds human review
Media type
application/pdf
Size
4.8 MB
Pages
12
Provenance
1 provenance reference
Source coordinates
1 source coordinate

Safe summary

12-page handbag catalogue; supplier-provided pricing ranges pending review

Supplier portal credential

Summary only No raw private value is accepted by this component.

Credential values stay behind the configured secret boundary; this component never accepts the raw private value.

Asset availability

Asset content unavailable

The workspace can show safe metadata, but the raw file content is missing or unavailable.

Unavailable

Asset content unavailable for this workspace. Storage diagnostic redacted: [redacted reference] [redacted local path] [redacted provider payload] [redacted provider payload].