Project Items & Budgets
Construction and Decorating Items, categories, budgets, pricing and procurement status.
/admin/projects/:slugFuture Spec 07 →Current-state summary
The live Project shows one Planning Budget value and promises future Budgeting. Project Builder defines five generic Item & Budget Categories—Design Fees, Furniture, Lighting, Art & Accessories and Logistics & Installation—but the Project has no Items, Categories, Budget, Shopping List, Purchase Order, receiving, storage, delivery or installation module. Construction and Decorating Items are not separated, and no spreadsheet or Google Sheets import is available from the Project.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Planning Budget | Rosedale shows $540,000 in Financial Summary; Create Project collects Approved planning budget. | Verified live |
| Template categories | Five editable code/name rows become standard shopping-list and Project-budget dropdowns. | Verified live |
| Items workspace | Absent. | Verified absent |
| Budget workspace | Absent; placeholder says approved baselines and forecast detail arrive in Budgeting. | Verified absent |
| Import | No spreadsheet upload, Google Sheets connector, preview or field mapping appears in the Project. | Verified absent |
| Provider operations | No Work Package, Purchase Order, receiving, storage, delivery or installation relationship is available from Items. | Verified absent |
User journeys
Current flows
Import Project Items
- Upload spreadsheet or select Google Sheet
- Map source columns to canonical fields
- Validate and deduplicate
- Preview creates/updates
- Commit an import batch
- Reconcile errors and preserve provenance
Operate construction materials
- Create Construction Items by scope and Space
- Set specification, quantity and Budget Category
- Request Provider pricing
- Approve and purchase
- Track delivery and field status
Operate Decorating Items
- Add selections to Shopping List
- Compare source and pricing
- Present to Client
- Approve
- Purchase
- Receive, store, deliver and install
State model
Current and expected states
One Project-level budget number.
Five generic categories with codes.
No Project Item list.
No Category roll-up or planned/approved/committed/actual/forecast values.
No Purchase Order or Item lifecycle.
Product rules
Non-negotiable boundaries
- Items are canonical records; Shopping Lists, purchase views and installation lists are projections.
- Construction Items and Decorating Items share a core Item model but use distinct field and workflow configurations.
- Budget Categories calculate from Items and commercial records instead of unrelated manual totals.
- Every import is previewable, attributable, reversible through governed reconciliation and idempotent.
- Vendor means the product-supplying Provider Category; Provider is the general network term.
- Expected arrival, Receiving Record, Storage Location, Delivery Manifest and installation evidence remain connected to the source Item.
Known current limitations · 6 mapped
What is missing, broken or unverified
Future Spec 07 owns closure →- No operational Item or Budget module exists.
- Construction and Decorating category semantics are mixed.
- Categories have no type, parent, budget behavior, required fields or lifecycle configuration.
- The template claims Projects may add categories but no Project-level category action was found.
- No import, AI product extraction, URL ingestion or Purchase Order parsing exists.
- No receiving, storage, delivery or installation connection exists.
Future alignment
Required evolution
- 01Build typed Item and Budget workspaces in Spec 07.
- 02Add spreadsheet and Google Sheets import with field mapping.
- 03Support AI-assisted URL, quote and Purchase Order extraction with confirmation.
- 04Connect Items to Provider Work Packages and the full procurement chain.
- 05Expose Category budgets and Item pricing in one explainable financial model.
Current baseline
Acceptance record
- Planning budget and five template categories are documented.
- Missing operational modules are explicit.
- Construction, Decorating and Provider terminology follows the glossary.
- No future import or procurement capability is claimed as current.
Reverse-spec completeness
Documentation coverage
The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.
Purpose and user outcome
DocumentedRoles and access
DocumentedRoutes and entry points
DocumentedPage and component anatomy
DocumentedFields and displayed data
DocumentedPrimary actions
DocumentedForms and validation
DocumentedStates and transitions
DocumentedEmpty, loading and error states
DocumentedResponsive behavior
PartialAccessibility behavior
PartialActivity and audit events
PartialData sources and persistence
DocumentedNotifications and automation
PartialKnown defects and limitations
DocumentedReusable component dependencies
DocumentedFuture-spec conflicts
PartialVisual and repository evidence
DeferredAcceptance of current baseline
Documented