Reverse spec drafted

Applications Builder

Designer and Provider application forms, review configuration, documents, decisions and immutable versions.

Observed route/admin/settings/applicationsFuture Spec 05 →

Current maturitySubstantial versioned builder with a critical summary-mapping defect

Evidence confidenceVerified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

Applications Builder covers Designer Studio plus all nine Provider Categories. A Storage Application draft exposes Application form, Review checklist, Application details, Documents, Decision and Version history. It contains 35 fields across 11 sections, including four Storage-specific sections, and reports 21 Workspace Profile and 16 Matchmaking mappings. However, every locked Application details summary item currently resolves to Damage documentation and claims process, making the reviewer summary untrustworthy.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Category directory	Designer Studio and nine canonical Provider Categories are present.	Verified live
Application form	Locked Registry defaults plus custom sections/fields; Storage has 35 fields and 11 sections.	Verified live
Review checklist	Six locked required standards including identity, insurance, fit, references, mapping and risk review.	Verified live
Application details	Six intended summary items all resolve to the same incorrect submitted field.	Critical defect verified live
Documents	Business registration, insurance, optional references, facility evidence and security/inventory controls.	Verified live
Decision	Nine reason categories with checklist, applicant message and reviewer-note requirements.	Verified live
Version history	Published versions are described as immutable; draft is Version 1.	Verified UI contract

User journeys

Current flows

Publish Application version

Open Category
Edit draft form and stable mappings
Configure checklist, summary, documents and decision
Preview as applicant and reviewer
Run mapping validation
Publish immutable version

State model

Current and expected states

Draft in progress

Storage Applications Version 1.

Published

Action exists; no version published during review.

Discarded draft

Action exists.

Immutable history

Promised by UI.

Product rules

Non-negotiable boundaries

All nine Provider Categories remain explicit.
Every field has a stable key independent of display label.
Workspace Profile and Matchmaking mappings validate before publish.
Submitted Applications retain their exact schema version.
Decision requirements cannot be bypassed by label customization.

Dependencies

Spec 05Pipeline and forms engineWorkspace ProfileMatchmaking ProfileFiles and CredentialsNotificationsProvisioning

Known current limitations · 3 mapped

What is missing, broken or unverified

Future Spec 05 owns closure →

Critical review-summary field mapping defect.
Several default controls appear disabled as intended but mapping presentation is confusing.
Publish, applicant preview and version retention were not mutated or tested.

Future alignment

Required evolution

01Block publish when a summary item resolves to the wrong field.
02Add schema diff, migration preview and automated mapping tests.
03Use the same website signup schema and authenticated continuation.
04Register complete Application notifications and provisioning handoff.

Current baseline

Acceptance record

Every summary item resolves to its intended stable field.
All Category fields and mappings pass validation.
Published versions are immutable.
No Application was changed during evidence review.

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