Extracted from ../entities/price-book.md.


🟡 Working:

  • Archived Price Book visibility / queryability — exact UI mechanism for browsing archived Price Books during Estimate build-up. Toggle proposed; confirm with UX.

🟢 Resolved (BR-review decisions, v0.2):

  • BR-053 scope application — LOCKED. Resources inherit Price Book’s scope (date range, region, Tender link); no finer-grained per-Resource scope in v1. Categorization can add orthogonal tagging.
  • Auto-archive on scope_end_date expiry — LOCKED. When scope_end_date < today, Price Book logically transitions to Archived (query-time check). Read-only; existing Resources continue to reference with snapshot semantics.
  • System-generated Price Book update in place — LOCKED. On re-adjudication (BR-067), existing system-generated Price Book updated in place (same ID, new rates/Resources); no new Price Book created.
  • Project-Specific vs Tender scope — CLARIFIED. project_id references Tender (not separate Project entity, Beta scope). Label retained for industry convention.
  • Multiple Price Books per Supplier for same date range — LOCKED. Allowed (e.g., different product categories); names must be unique workspace-wide.