oxFlow Wiki

Domain Model — Change Log

4 min read

Extracted from ../../foundation/concept-map.md.

  • v0.10 — Code + Code Option entities added to Layer 5 (Reference Data):

    • Closes the gap where entities/codes.md referenced a domain entity that didn’t exist in the catalogue
    • Adds #### Code 🟡 and #### Code Option 🟡 entries with attributes and relationships, mirroring the Categorization / Categorization Option pattern
    • Updates Layer 5 conceptual-layers table to list Code and Code Option
    • Adds three rows to the §3 cardinality reference table: Code → Code Option (1:M), Item → Code Option (M:0..1), Resource → Code Option (M:0..1)
    • Reflects business rules BR-125 / BR-125a / BR-126 / BR-127 / BR-128 and the Benchmark migration mapping (Workcentre on Items, Activity Code on Resources)

  • v0.9 — consistency pass:

    • “Risk Breakdown” → “Risks” terminology corrected in Content Block Definition seed values
    • Confirmed alignment with business-rules v0.9 (BR-047/048/049/049a rate-edit mechanics), entity specs Item v0.4 / Resource v0.4 / Worksheet v0.4 / Recipe v0.2

  • v0.8 — Price Book auto-creation on fork (BR-049):

    • Price Book entity description updated to note auto-creation trigger when a Worksheet Resource is forked
    • No new entities or relationships added; semantic clarification on Project-Specific Price Books
    • Reflects business rule BR-049 (Fork to new Resource action)

  • v0.7 — Flag and Modifier catalog integration (driven by Resource entity spec v0.3):

    • Added Flag Definition as admin-managed catalog entity in Layer 5 (Reference Data)
    • Added Modifier Definition as admin-managed catalog entity in Layer 5 (Reference Data)
    • Resource gains M:M relationships to Flag Definition (via flag instance) and Modifier Definition (via modifier instance)
    • Worksheet Resource gains snapshot support for flags and modifier defaults; can carry per-instance modifier overrides
    • Worksheet Resource gains M:M relationship to Modifier Definition (via override instance, optional)
    • Updated Layer 1 conceptual-layers table and §3 cardinality reference table
    • Reflects Resource entity spec v0.3 and business rules BR-023 (reworded), BR-027, BR-028, BR-029

  • v0.1 — initial draft from glossary v0.3

  • v0.6 — Item Status expansion (driven by Item entity spec v0.3):

    • Item states expanded from 3 → 5 (added Unpriced and Plugged)
    • Added plug_rate attribute note to Item entity
    • Estimate state gains Submit-block condition (any child Item Unpriced/Plugged blocks Submit)

  • v0.5 — gap-analysis pass:

    • Added Reference Rate as a new entity in Layer 5 (Reference Data); admin-defined anchor for Anomaly Review
    • Added Production Rate note to Variable entity (no new entity — Variable pattern)
    • Updated Layer 5 conceptual-layers table to include Reference Rate

  • v0.4 — consistency pass:

    • Cardinality row for Worksheet↔Resource clarified — shown as 1:M through the Worksheet Resource join, with a note that the transitive relationship is M:M
    • Open-item §9.5 cross-refs BR-045 (same terminology question)

  • v0.3 — alignment with business-rules v0.4 (BR-024 unification):

    • Price Book gains a source_type attribute (user-created / system-generated)
    • Subcontract Package Adjudication now outputs to a system-generated Price Book (not direct Resources on Items)
    • Resource loses its direct lineage to Subcontract Package Adjudication — lineage is now captured via the containing Price Book
    • Cardinality table updated: Price Book → Subcontract Package Adjudication M:0..1 (replaces Resource → Subcontract Package Adjudication)

  • v0.2 — BR review pass:

    • Item ↔ Worksheet locked at 1:1 (every Item has one; UI adapts for sparse cases)
    • Heading formatting — depth-based defaults in working view; admin-configurable in Publisher branding
    • Worksheet Resource / Recipe snapshot semantics documented — snapshots do not auto-sync; divergence flagged by Anomaly Review
    • Recipe → Worksheet Recipe relationship clarified as inverse “usages” view (impact analysis)
    • Total cost derivation fixed — Recipes are evaluated using input parameters; evaluated cost is what’s added
    • Unit cost added as a derived attribute (total cost ÷ quantity)
    • Current rate row removed from derived attributes — rates are stored, Adjudications change them directly
    • Subcontract Package state machine removed — state lives on Adjudication
    • Tender state transitions clarified (Won/Lost only after Submitted; Archived from Active or Submitted)
    • Minor attribute tweaks from BR edits (client reference on Tender, estimate numbering, schedule code on Item, Recipe notes)

Graph View