Guided
Plain-language orientation, familiar controls, minimal governance machinery in the way.
Build 09 · experience-depth prototype
One SIW. More depth as the user wants it.
The Experience Depth model uses progressive disclosure rather than separate casual and expert products. Build 09 prototypes presentation-depth preference, local interaction signals, privacy-respecting usage metrics, and the future account/security boundary entirely in the local browser. These signals are not competence, role, identity, or authority determinations.
Local prototype onlyCurrent depth: GuidedNo production sign-in connected
Experience-depth progressive disclosure
The interface may offer more depth. It does not infer role, competence, or authority.
Choose a presentation-depth default now. Build 09 counts a small set of non-content interactions locally and may offer Explorer depth after repeated use of deeper inspection tools. That suggestion is an interface convenience only, not an assessment of expertise, competence, role, authorization, or standing.
Explorer
More evidence, lineage, comparison, relationship, and inspection actions surfaced by default.
Advanced
Technical state, receipts, schemas, release references, and implementation detail become easier to reach.
Current default: Guided. This preference is stored only in this browser.
Privacy-preserving product metrics
Learn where people struggle without recording what they are thinking about.
This Build 09 demonstration stores only aggregate counters in this browser. It does not store inquiry text, document contents, search terms, form values, or private workspace material.
0Page views
0Advanced interactions
0Media opens
0Diagram opens
0Proof-path opens
Production direction
Aggregate event type, product surface, app version, coarse timing, and a rotating pseudonymous session can answer most usability questions. Raw inquiry content should remain out of the analytics stream unless a user deliberately submits feedback that includes it.
Identity & security boundary
Registration, authentication, authorization, and governed standing are different things.
Build 09 does not pretend to authenticate anyone. This site remains a review surface; production identity/session infrastructure is still a future application boundary.
Browser / SIW UIno secrets in client code
→Server sessionsecure cookie / token boundary
→Enterprise identityOIDC · SAML as needed
→ProvisioningSCIM / directory lifecycle
→SIW authorizationrole, scope, standing remain app-level
X.500/X.509 can matter in enterprise directory and certificate/PKI environments, but the public SIW login UX should not depend on a proprietary identity stack. The goal is standards-based federation and replaceable identity providers.
Semantic boundary
Experience depth is not authority.
Guided, Explorer, and Advanced describe presentation and interaction depth. They are not authorization classes.
Authority-neutral profile rule
A user may be highly proficient and unauthorized, or authorized and unfamiliar with the interface. Local proficiency signals may affect explanation depth, defaults, or assistance only. They must not create standing, expand scope, confer permission, or substitute for a current authority check.