View

Working public standard

Boundary First UX

A semantic interaction and representation standard for making complex systems navigable while preserving identity, provenance, context, consequence, and repair across changing views.

At a glanceWorking Public Standard · Launch Candidate

Boundary First UX is already a substantial working standard with a flagship sequence, semantic stack, motion laws, accessibility obligations, renderer independence, and proposed conformance structure.

Next publication gate

Stabilize conformance language and complete accessibility/human validation before stable launch.

Continue from here
Working public standardOpen Boundary First UXResearch contextBoundary First UX research object
More context · 1

Its source explicitly labels it a launch candidate. Stable release still requires conformance decisions, responsive/accessibility validation, and evidence that the interaction grammar works for people beyond the authoring context.

Working public standard · launch candidate

Design the boundary, not the screen.

BFUXReturn to object

Every interface is a bounded representation of a larger system. Boundary First UX makes those boundaries explicit so users can change resolution, perspective, and context without losing identity, provenance, consequence, or closure.

Same semantic objectNormative detail instrument
Representation boundary

Every interface is a boundary.

The design problem is not only what appears on the screen. It is what the representation admits, excludes, compresses, reveals, makes actionable, and preserves as context changes.

Local simplicity without global amnesia.
North starOh. I can see the system now.
inside current representationoutside current representation
Useful local viewidentity · state · task

Partiality is visible. The outside is not erased merely because it is not currently rendered.

Core laws

Five obligations govern every BFUX representation.

01Bound every view
02Preserve identity through transformation
03Make hidden structure tangible
04Preserve consequence and path
05Closure is earned
Flagship proof

The Green Project Was Inside a Larger System

A locally valid project view hides a ten-year maintenance obligation outside the project boundary. The user discovers the obligation, reframes toward consequence, traces it through handoff and funding, promotes the representation into lifecycle context, repairs ownership, and reaches scoped closure.

  1. 01Orient
  2. 02Inspect
  3. 03Reveal
  4. 04Reframe
  5. 05Stress
  6. 06Trace
  7. 07Promote
  8. 08Repair
  9. 09Closure
TrustOrient → Inspect
DiscoveryReveal → Reframe → Stress → Trace
ReconstructionPromote → Repair → Closure
Timeline proofWhat ends here?

The project ends. The system does not.

Authorization
Design
Install
Acceptance
Closeoutproject boundary

Project closeout occurs while a ten-year maintenance obligation begins and household service consequence persists.

Expand the two-year project view into a twelve-year lifecycle while preserving the original project interval.

Renderer independence

Boundary First semantics belong to the represented world, not to any one renderer.

semantic stateidentity · provenance · consequence · closure
Projection 01World / spatial renderer
Projection 02Non-spatial instrument
Projection 03Timeline renderer
Views do not own semantic truth. Renderers receive semantic state and emit declared intentions.
Semantic stack

Renderer is the outermost layer, not the source of truth.

  1. 01semantic world
  2. 02bounded context / contexture
  3. 03interaction grammar
  4. 04task instrument
  5. 05audience projection
  6. 06renderer / visual language
Interaction grammar

A compact semantic grammar beneath many visual worlds.

World actions
Orient
Traverse
Inspect
Reveal
Reframe
Trace
Gate
Stress
Repair
Promote
Workbench operators
Distill
Condense
Overlay
Calibrate
World events
Leak
Crack
Overflow
Stall
Orphan
Drift
Collision
Closure
Conceptual tangibility

Physical metaphor is admissible only when it carries operational semantics.

Art direction

scientific instrument + civic infrastructure + museum cutaway + drafting table + playful game logic

Every physical metaphor must have operational semantics.
Screen depth
behind

outside current representation

on

current representation

inFront

surfaced consequence, evidence, or action

Motion semantics
lateral

Traverse

throughScreen

Reveal

worldRotation

Reframe

zoomBeyondFrame

Promote

ContinuityConservationCausalityPersistenceReversibilityContainment
Pattern catalog

Reusable interactions remain named, inspectable, and composable.

01Guided Atlas Passage02Focus Contexture03Semantic Resolve04Context Rotation05Typed Edge Resolution06Visible Partiality07Provenance-Preserving Collapse08Resolution Breadcrumb09Closure Gate10Repairable Reset11Multi-Resolution Comparison12User-Drawn Boundary13Hidden-Structure Reveal14Stress-to-Defect15Consequence Trace16Context Promotion17Representational World Shift18Semantic Depth Reveal19Instrumented Repair
Accessibility

Accessibility is paradigm correctness.

keyboard completereduced-motion parityscreen-reader semanticsnon-spatial alternativesvisible context and provenanceno color- or position-only essential informationno motor-precision gate
An accessible representation is a lawful projection, not a fallback copy.
Conformance console

Conformance is a set of inspectable obligations, not a visual score.

The current levels are candidates. They are deliberately presented as proposed states rather than badges that imply certification.

  1. 01

    Is the represented containment boundary explicit?

  2. 02

    Is partiality visible rather than hidden?

  3. 03

    Are identity and provenance preserved through transformations?

  4. 04

    Do transitions have declared semantics?

  5. 05

    Can consequences be traced?

  6. 06

    Can state be recovered after a transformation?

  7. 07

    Can hidden structure be revealed without destroying context?

  8. 08

    Are defects diagnosable and repairable?

  9. 09

    Is the experience semantically complete through accessible routes?

  10. 10

    Is closure scoped and earned?

Standard / demonstration / lab

NOW BREAK IT

Standard → Demonstration → Experimental Lab

StandardNormative semantic contract
DemonstrationReference performance
Experimental labExperimentation without automatic promotion
Sandbox contact may produce evidence, defects, or reusable methods. It never promotes an object directly to capability, program, or canon without the corresponding review gate.
Claim boundary

What Boundary First UX is not.

component librarymandatory skingraph-only interfacegeneric gamification3D for its own sakerequirement for visually complex UIclaim that existing design systems are obsolete