BC
Brad CodyAdministrator
Current productShared components and patterns
Reverse spec drafted

Modal, drawer and full-page editor

Rules for choosing focused dialogs, side drawers or full-page editors by complexity and risk.

Observed routeShared componentFuture Spec 16
Current maturityConsistent visual pattern with safety and scale gaps
Evidence confidenceVerified
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

Current-state summary

Internal Note, Task, Project Opportunity, Project Vision and Task Template dialogs share centered overlays, strong titles, supporting copy, close controls, sectioned content and Cancel/primary actions. Long forms can exceed the viewport, and the Task Edit defect shows that shared appearance does not guarantee correct command mode or loaded record identity.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

ElementCurrent behaviorVerification
Overlay and frameCentered white surface over dimmed application.Verified
HeaderTitle, explanation and close action.Verified
BodySupports simple composers and large sectioned forms.Verified
FooterCancel and primary action commonly anchored.Verified
Mode identityTask Edit incorrectly opens blank Create mode.Critical defect

User journeys

Current flows

01

Create or edit safely

  1. Open explicit mode
  2. Load target identity/version for Edit
  3. Trap focus and announce title
  4. Change fields
  5. Validate
  6. Confirm destructive impact when relevant
  7. Save command
  8. Return focus to invoker
Observed result

Visual flow exists; edit identity and accessibility need enforced shared behavior.

State model

Current and expected states

Opening/loading

Not consistently separated.

Idle

Common form state.

Dirty

Unsaved-close warning is unverified.

Saving/error

Not consistently evidenced.

Conflict

Not represented.

Product rules

Non-negotiable boundaries

  • Create, Edit, View and Confirm are explicit modes.
  • Edit loads immutable target identity and current version before enabling save.
  • Focus is trapped and restored.
  • Escape/close respects unsaved changes.
  • Long workflows use full-page or stepped patterns when a modal becomes unmanageable.
Dependencies
Shared dialog primitiveDynamic formsCommands and optimistic concurrencyAccessibilityUnsaved-change service

Known current limitations · 4 mapped

What is missing, broken or unverified

Future Spec 16 owns closure →
  1. Critical Task Edit mode defect.
  2. Long forms can be unwieldy.
  3. Focus, keyboard, mobile and conflict behavior are not fully verified.
  4. Unsaved-change protection unverified.

Future alignment

Required evolution

  • 01Enforce dialog mode and record identity centrally.
  • 02Use full-page editors for complex builders.
  • 03Add consistent validation, saving, error, conflict and focus behavior.

Current baseline

Acceptance record

  • The dialog announces its purpose and target.
  • Edit never opens blank Create state.
  • Keyboard and screen-reader use is complete.
  • Cancel cannot silently discard dirty work.

Reverse-spec completeness

Documentation coverage

The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.

Purpose and user outcome

Documented

Roles and access

Documented

Routes and entry points

Documented

Page and component anatomy

Documented

Fields and displayed data

Documented

Primary actions

Documented

Forms and validation

Documented

States and transitions

Documented

Empty, loading and error states

Documented

Responsive behavior

Partial

Accessibility behavior

Partial

Activity and audit events

Partial

Data sources and persistence

Documented

Notifications and automation

Partial

Known defects and limitations

Documented

Reusable component dependencies

Documented

Future-spec conflicts

Partial

Visual and repository evidence

Deferred

Acceptance of current baseline

Documented