Reverse spec drafted

Proposals directory

Permission-scoped cross-Project table for Client and Provider Proposal records.

Observed routeComing soon — no routeFuture Spec 06 →

Current maturityDisabled navigation placeholder without availability label

Evidence confidenceVerified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

Proposals appears in primary navigation as a non-routable # link. Unlike Messages, it is not labelled Coming soon. Direct navigation to /admin/proposals is unavailable. No global Proposal table, Proposal Profile, filters, creation flow or commercial state can be verified. Record-level Proposal tabs are also intentionally disabled elsewhere.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Navigation	Disabled # link without Coming soon label.	Verified live
Directory	No route or table exists.	Verified absent
Proposal Profile	No detail, version, recipient, line-item, acceptance or history surface exists.	Verified absent
Project projection	Record and Project Proposal modules are not implemented.	Known limitation

User journeys

Current flows

Find and operate Proposal

Open Proposals
Filter by relationship, Project, party, status and date
Open exact Proposal version
Review decision and lineage
Send, revise, accept, award or convert when permitted

State model

Current and expected states

Coming soon

Implied by disabled link but not labelled.

Draft through accepted/declined/expired

Not represented.

Superseded or converted

Not represented.

Product rules

Non-negotiable boundaries

Proposal is a versioned commercial record, not a generic file.
Client and Provider Proposals use shared primitives with relationship-specific visibility.
Sent and accepted versions are immutable.
Acceptance, award and Work Order creation are distinct auditable actions.
Providers see only their own Proposals and awarded work.

Dependencies

Spec 06 Commercial OperationsProjects and Work PackagesEntities and OffersDocument rendering and acceptancePermissions, Notifications and payments

Known current limitations · 3 mapped

What is missing, broken or unverified

Future Spec 06 owns closure →

No working route.
No Coming soon label.
No directory, profile, template, version, line item, send, acceptance or conversion behavior can be verified.

Future alignment

Required evolution

01Label the placeholder Coming soon immediately.
02Build the shared Proposals directory and Proposal Profile from Spec 06.
03Expose Project-scoped and Provider-owned projections from the same records.
04Connect accepted Proposals to Commitments, Work Orders, Invoices and Payments.

Current baseline

Acceptance record

The placeholder is not reported as an implemented directory.
Unavailable entry points are visibly labelled and non-interactive.
Future state preserves exact Proposal versions and audience boundaries.

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