BC
Brad CodyAdministrator
Current productProjects and project operations
Reverse spec drafted

Project Items & Budgets

Construction and Decorating Items, categories, budgets, pricing and procurement status.

Observed route/admin/projects/:slugFuture Spec 07
Current maturityPlanning-budget summary and generic template categories only
Evidence confidenceKnown limitation
Last reviewedAugust 4, 2026
Visual evidenceDeferred during UI updates

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.

ElementCurrent behaviorVerification
Planning BudgetRosedale shows $540,000 in Financial Summary; Create Project collects Approved planning budget.Verified live
Template categoriesFive editable code/name rows become standard shopping-list and Project-budget dropdowns.Verified live
Items workspaceAbsent.Verified absent
Budget workspaceAbsent; placeholder says approved baselines and forecast detail arrive in Budgeting.Verified absent
ImportNo spreadsheet upload, Google Sheets connector, preview or field mapping appears in the Project.Verified absent
Provider operationsNo Work Package, Purchase Order, receiving, storage, delivery or installation relationship is available from Items.Verified absent

User journeys

Current flows

01

Import Project Items

  1. Upload spreadsheet or select Google Sheet
  2. Map source columns to canonical fields
  3. Validate and deduplicate
  4. Preview creates/updates
  5. Commit an import batch
  6. Reconcile errors and preserve provenance
Observed result

Required future journey; not implemented.

02

Operate construction materials

  1. Create Construction Items by scope and Space
  2. Set specification, quantity and Budget Category
  3. Request Provider pricing
  4. Approve and purchase
  5. Track delivery and field status
Observed result

Required future journey; not implemented.

03

Operate Decorating Items

  1. Add selections to Shopping List
  2. Compare source and pricing
  3. Present to Client
  4. Approve
  5. Purchase
  6. Receive, store, deliver and install
Observed result

Required future journey; not implemented.

State model

Current and expected states

Planning only

One Project-level budget number.

Template categories

Five generic categories with codes.

Items unavailable

No Project Item list.

Budget unavailable

No Category roll-up or planned/approved/committed/actual/forecast values.

Procurement unavailable

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.
Dependencies
Spec 07 Project Item and Budget modelEnterprise data gridDynamic formsSpreadsheet and Google Sheets importProvider matchingWork PackagesProposals and Work OrdersPurchase OrdersReceiving and storagePermissions and audit

Known current limitations · 6 mapped

What is missing, broken or unverified

Future Spec 07 owns closure →
  1. No operational Item or Budget module exists.
  2. Construction and Decorating category semantics are mixed.
  3. Categories have no type, parent, budget behavior, required fields or lifecycle configuration.
  4. The template claims Projects may add categories but no Project-level category action was found.
  5. No import, AI product extraction, URL ingestion or Purchase Order parsing exists.
  6. 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

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