@rubytech/create-sitedesk-code 0.1.348 → 0.1.349

package/payload/platform/plugins/memory/references/schema-construction.md

@@ -1,39 +1,86 @@
-# Schema Reference — Construction
+# Schema Reference — Construction / Field Service
 
-Vertical schema for `businessType: "construction"` — small building firms and independent building contractors (the SiteDesk brand).
+Vertical schema for `businessType: "construction"` — building firms, contractors, and
+field-service operators (the SiteDesk brand). This is the **canonical, opinionated** SiteDesk
+service-delivery ontology, authored from JobLogic's proven field-service domain so that an
+operator's job maps onto shipped labels without inventing the model. JobLogic's term is the
+canonical label name for each concept.
 
-This reference extends the base schema. All base node types (Person, Organization, Invoice, PostalAddress, Event, etc.) remain valid. Load `schema-base.md` first.
+This reference extends the base schema. All base node types (Person, Organization, Invoice,
+PostalAddress, Event, etc.) remain valid. Load `schema-base.md` first.
 
 When loading this reference, confirm: "Using schema-base + schema-construction".
 
----
-
-## Additional Node Types
-
-| Entity | Neo4j Label | Schema.org Type | Required Properties |
-|--------|-------------|-----------------|---------------------|
-| Job | `Job` | `schema:Project` | `accountId`, `jobId`, `client`, `address`, `status` (quoting/active/complete), `contractValue` |
-| LineItem | `LineItem` | `cdm:LineItem` | `accountId`, `jobId`, `trade`, `description`, `contractValue` |
-| Valuation | `Valuation` | `schema:MonetaryAmount` | `accountId`, `jobId`, `valuationNumber`, `date`, `totalValue` |
-| Milestone | `Milestone` | `schema:Event` (subtype) | `accountId`, `jobId`, `name`, `completedDate` |
-| QuoteDocument | `QuoteDocument` | `schema:DigitalDocument` | `accountId`, `jobId`, `ref`, `totalPaymentDue`, `date`, `status` (draft/sent/accepted) |
-| VariationNote | `VariationNote` | `schema:DigitalDocument` | `accountId`, `jobId`, `variationNumber`, `description`, `totalPaymentDue`, `status` |
-| InboundInvoice | `InboundInvoice` | `schema:Invoice` | `accountId`, `supplier`, `confirmationNumber`, `totalPaymentDue`, `status` (pending/approved/processed) |
-| Worker | `Worker` (label on `Person`) | `schema:Person` (config) | `accountId`, `personId`, `name`, `engagement` (employee/cis), `dayRatePence`, `showCisDeduction`, `invoiceEmail` |
-| CheckIn | `CheckIn` | `schema:Action` | `accountId`, `personId`, `source`, `date`, `site`, `description`, `dayHundredths` |
-| WhatsAppGroup | `WhatsAppGroup` | `cdm:Channel` | `accountId`, `groupId`, `jobId`, `clientName` |
-
-`awardedDate` on `Job` is expected once `status` is `active` or `complete` — a job still `quoting` has no award date. Never write a sentinel value (`"pending"`, `""`) to stand in for an unknown date; omit the property until the real date is known.
-
-These entities model a general builder job folder: a `Job` has a generated client `QuoteDocument` that carries many `LineItem` rows organised by trade stage, supplier and sub-contractor invoices, and per-trade structure. A residential building job's line items typically span stages such as groundworks, sub-structure, superstructure, roof, structural alterations & envelope, first fix, drylining & plastering, floor screed, second fixing, knock-throughs, windows & doors, completion items and preliminaries, plus sub-contractor trades (scaffolding, roofing, electrical, plumbing, plastering, tiling, decorations). The schema carries no client, job, or pricing data of its own — those are per-account runtime values.
-
-### Distinctions from schema-trades
-
-`QuoteDocument` is the generated client quote artefact (the `Q-XXXX` document), distinct from schema-trades' `Quote` (a pre-acceptance Order estimate). `InboundInvoice` is a received/payable invoice with job + trade assignment, distinct from the base `Invoice`. A subcontractor company's received invoices use the same `InboundInvoice` model as any other supplier.
+Property fidelity: properties marked **(JobLogic-exact)** are taken from JobLogic's API field
+model; properties marked **(authored)** are modelled from JobLogic's vocabulary plus the
+field-service domain where the captured reference does not document the entity at field level.
 
-### Field-worker time and pay
+---
 
-A field worker's time and pay is the `:Worker`/`:CheckIn` model. `:Worker` is an operator-config label on the worker's `:Person` (engagement, day rate, whether the CIS deduction shows, the office invoice address); `:CheckIn` is one record per working day, linked to the worker by `(:Worker)-[:LOGGED]->(:CheckIn)` and unified for roll-up by the shared `personId`. The timesheet skill rolls the check-ins for a period into a per-worker timesheet, and for a CIS worker an invoice that is rendered and emailed, not stored as a node.
+## Top-level node types (operator-entry, natural key)
+
+| Entity | Neo4j Label | Schema.org Type | Required Properties | Fidelity |
+|--------|-------------|-----------------|---------------------|----------|
+| Job | `Job` | `schema:Project` | `accountId`, `jobId`, `status` | JobLogic-exact |
+| Customer | `Customer` | `schema:Organization` | `accountId`, `customerId`, `name`, `customerType` | JobLogic-exact |
+| Site | `Site` | `schema:Place` | `accountId`, `siteId`, `name`, `region` | JobLogic-exact |
+| Asset | `Asset` | `schema:Product` | `accountId`, `assetId`, `name`, `assetType`, `assetClass`, `condition` | authored |
+| Visit | `Visit` | `schema:Event` (subtype) | `accountId`, `visitId`, `status`, `startDate`, `purpose` | authored |
+| Quote | `Quote` | `schema:Order` (estimate) | `accountId`, `ref`, `status`, `totalPaymentDue`, `date` | authored |
+| Supplier invoice | `InboundInvoice` | `schema:Invoice` | `accountId`, `supplier`, `confirmationNumber`, `totalPaymentDue` | JobLogic-exact |
+| Part | `Part` | `schema:Product` | `accountId`, `partId`, `name`, `sku`, `partCategory` | authored |
+| Purchase Order | `PurchaseOrder` | `schema:Order` | `accountId`, `poNumber`, `status`, `completionStatus`, `dateRaised` | JobLogic-exact |
+| PPM Contract | `PpmContract` | `schema:Service` (contract) | `accountId`, `contractId`, `name`, `startDate`, `endDate` | authored |
+| WhatsApp Group | `WhatsAppGroup` | `cdm:Channel` | `accountId`, `groupId`, `jobId`, `clientName` | n/a (transport) |
+
+`Job.status` is one of JobLogic's job statuses: `New Job`, `Allocated`, `Attended`,
+`Parts To Fit`, `Awaiting Parts`, `Completed`, `Costed`, `Reqs. Invoice`, `Invoiced`, `Paid`,
+`Cancelled`, `Recall`. `Job.jobType` is the highest categorisation (Call out, Installation,
+Maintenance, Out of Hours, Reactive, Non-Productive); `Job.jobCategory` is the finer trade
+detail. `Site.region` is one of `East`, `North`, `South`, `West`. `PurchaseOrder.status` is one
+of `InProgress`, `Sent`, `Cancelled`, `NeedsApproval`; `PurchaseOrder.completionStatus` one of
+`NotApplicable`, `NotCompleted`, `PartiallyCompleted`, `FullyCompleted`. Never write a sentinel
+value for an unknown date — omit the property until the real value is known.
+
+Two distinct invoice documents. The received supplier invoice is `InboundInvoice` (keyed
+`(accountId, supplier, confirmationNumber)`), now linked to the `PurchaseOrder` it pays — a
+subcontractor company's received invoice uses the same model as any other supplier. The
+customer-facing outbound bill is the base `Invoice` (`schema-base.md`), whose billing chain is
+the child `InvoiceLine`, `InvoicePayment`, and `Credit`. The two labels carry different required
+fields (supplier vs customer), so they stay distinct rather than one label with a direction flag.
+
+## Child node types (write-time MERGE; reached via parent neighbourhood)
+
+| Entity | Neo4j Label | Required Properties | Fidelity |
+|--------|-------------|---------------------|----------|
+| Quote line | `QuoteLine` | `accountId`, `jobId`, `trade`, `description`, `contractValue` | authored |
+| Valuation | `Valuation` | `accountId`, `jobId`, `valuationNumber`, `date`, `totalValue` | authored |
+| Milestone | `Milestone` | `accountId`, `jobId`, `name`, `completedDate` | authored |
+| Variation | `VariationNote` | `accountId`, `jobId`, `variationNumber`, `description`, `totalPaymentDue`, `status` | authored |
+| Job cost | `JobCost` | `accountId`, `costType` | JobLogic-exact |
+| Contact | `Contact` | `accountId`, `contactId`, `name` | JobLogic-exact |
+| PO line | `PurchaseOrderLine` | `accountId`, `poNumber`, `lineId`, `description`, `quantity`, `pricePerUnit` | JobLogic-exact |
+| Invoice line | `InvoiceLine` | `accountId`, `invoiceId`, `lineId`, `description`, `quantity`, `amount` | authored |
+| Invoice payment | `InvoicePayment` | `accountId`, `invoiceId`, `paymentId`, `amount`, `date`, `paymentType` | JobLogic-exact |
+| Credit | `Credit` | `accountId`, `creditId`, `amount`, `date` | authored |
+
+`JobCost.costType` is one of `labour`, `material`, `travel`, `mileage`, `expense`,
+`subcontractor`, `scheduleOfRates` — the JobLogic cost-line taxonomy. A logged labour day (the
+old check-in) is a `JobCost` with `costType:'labour'`. `JobCost.priceCalculationType` is `0`
+(Non-Chargeable), `1` (Calculated Price), or `2` (Fixed Price), JobLogic's enum.
+
+`QuoteLine` is one priced row of the `Quote` contract schedule — the line a `Valuation` measures
+percent-complete against. It is **not** a `JobCost`: the quote line is the priced contract value,
+the job cost is the incurred cost. Per-line percent-complete a valuation records is carried
+valuation state, not a property of the line or the edge.
+
+## Additional labels on a base node
+
+`Engineer` is an additional label on the field engineer's `:Person` (`accountId`, `engineerId`,
+`name`, `engagement` (employee/cis), `dayRatePence`, `showCisDeduction`, `invoiceEmail`); there
+is no standalone `:Engineer`. `Supplier` is an additional label on a supplier's `:Organization`
+(`accountId`, `supplierId`, `accountNumber`); there is no standalone `:Supplier`. Both are set
+via `memory-update`, mirroring how the field worker was modelled before the JobLogic adoption.
 
 ---
 
@@ -42,55 +89,103 @@ A field worker's time and pay is the `:Worker`/`:CheckIn` model. `:Worker` is an
 MERGE keys per label:
 
 - `:Job` — `(accountId, jobId)`
+- `:Customer` — `(accountId, customerId)`
+- `:Site` — `(accountId, siteId)`
+- `:Asset` — `(accountId, assetId)`
+- `:Visit` — `(accountId, visitId)`
+- `:Quote` — `(accountId, ref)`
+- `:InboundInvoice` — `(accountId, supplier, confirmationNumber)` — the received supplier invoice
+- `:Invoice` — `(accountId, confirmationNumber)` — the base outbound customer invoice (schema-base.md)
+- `:Part` — `(accountId, partId)`
+- `:PurchaseOrder` — `(accountId, poNumber)`
+- `:PpmContract` — `(accountId, contractId)`
+- `:WhatsAppGroup` — `(accountId, groupId)`
+- `:QuoteLine` — `(accountId, jobId, trade, description)` — child of `:Quote`, write-time MERGE
 - `:Valuation` — `(accountId, jobId, valuationNumber)`
-- `:QuoteDocument` — `(accountId, ref)`
+- `:Milestone` — `(accountId, jobId, name)` — child of `:Job`, write-time MERGE
 - `:VariationNote` — `(accountId, jobId, variationNumber)`
-- `:InboundInvoice` — `(accountId, supplier, confirmationNumber)`
-- `:WhatsAppGroup` — `(accountId, groupId)`
-- `:LineItem` — `(accountId, jobId, trade, description)` — child of the `:QuoteDocument`, write-time MERGE only
-- `:Milestone` — `(accountId, jobId, name)` — child of `:Job`, write-time MERGE only
-- `:Worker` — `(accountId, personId)` — an additional label on the worker's `:Person`, set via `memory-update`
-- `:CheckIn` — `(accountId, personId, date)` — child of the worker's `:Person`, write-time MERGE only
+- `:JobCost` — `(accountId, costId)` — write-time MERGE; `jobId` is set when the cost is job-scoped, omitted for a worker-day labour roll-up
+- `:Contact` — `(accountId, contactId)` — write-time MERGE
+- `:PurchaseOrderLine` — `(accountId, poNumber, lineId)` — child of `:PurchaseOrder`
+- `:InvoiceLine` — `(accountId, invoiceId, lineId)` — child of `:Invoice`
+- `:InvoicePayment` — `(accountId, invoiceId, paymentId)` — child of `:Invoice`
+- `:Credit` — `(accountId, creditId)` — child of `:Invoice`
+- `:Engineer` — `(accountId, personId)` — additional label on `:Person`, set via `memory-update`
+- `:Supplier` — `(accountId, organizationId)` — additional label on `:Organization`
 
 ---
 
 ## Relationship Patterns
 
 ```
+(:Job)-[:FOR_CUSTOMER]->(:Customer)
+(:Customer)-[:HAS_SITE]->(:Site)
+(:Job)-[:AT_SITE]->(:Site)
+(:Site)-[:HAS_ASSET]->(:Asset)
+(:Job)-[:HAS_VISIT]->(:Visit)
+(:Visit)-[:ATTENDED_BY]->(:Engineer)
+(:Job)-[:HAS_QUOTE]->(:Quote)
+(:Quote)-[:HAS_LINE]->(:QuoteLine)
 (:Job)-[:HAS_VALUATION]->(:Valuation)
-(:Job)-[:HAS_MILESTONE]->(:Milestone)
-(:Job)-[:HAS_QUOTE]->(:QuoteDocument)
-(:QuoteDocument)-[:HAS_LINE_ITEM]->(:LineItem)
-(:Valuation)-[:VALUES]->(:LineItem)
+(:Valuation)-[:VALUES]->(:QuoteLine)
 (:Job)-[:HAS_VARIATION]->(:VariationNote)
-(:Job)-[:FOR_CLIENT]->(:Person)
-(:Job)-[:AT_ADDRESS]->(:PostalAddress)
-(:InboundInvoice)-[:ASSIGNED_TO]->(:Job)
-(:InboundInvoice)-[:FROM_SUPPLIER]->(:Organization)
-(:Worker)-[:LOGGED]->(:CheckIn)
+(:Job)-[:HAS_MILESTONE]->(:Milestone)
+(:Job)-[:HAS_COST]->(:JobCost)
+(:JobCost)-[:INCURRED_BY]->(:Engineer)
+(:PurchaseOrder)-[:HAS_PO_LINE]->(:PurchaseOrderLine)
+(:PurchaseOrderLine)-[:FOR_PART]->(:Part)
+(:PurchaseOrder)-[:FROM_SUPPLIER]->(:Supplier)
+(:InboundInvoice)-[:ON_PURCHASE_ORDER]->(:PurchaseOrder)
+(:Invoice)-[:HAS_INVOICE_LINE]->(:InvoiceLine)
+(:Invoice)-[:HAS_PAYMENT]->(:InvoicePayment)
+(:Invoice)-[:HAS_CREDIT]->(:Credit)
+(:PpmContract)-[:FOR_CUSTOMER]->(:Customer)
+(:PpmContract)-[:COVERS_SITE]->(:Site)
+(:Contact)-[:CONTACT_FOR]->(:Customer)
 (:WhatsAppGroup)-[:MAPPED_TO]->(:Job)
 ```
 
-Every `:Job` is the parent node for its valuations, milestones, quotes, and variations, satisfying the ≥1-adjacency write-gate doctrine. Line items are **not** a direct child of the `:Job`: a `:LineItem` is one row of the priced contract schedule, owned by the `:QuoteDocument` that priced it, and reached from the job through the quote — `(:Job)-[:HAS_QUOTE]->(:QuoteDocument)-[:HAS_LINE_ITEM]->(:LineItem)`. Each valuation links the lines it measures with `(:Valuation)-[:VALUES]->(:LineItem)`; the per-line percent-complete a valuation records is carried valuation state, not a property of the edge or the line. A `:Job` links to its client (`:Person`) and site (`:PostalAddress`); inbound supplier invoices link to the `:Job` they are assigned to and the `:Organization` that issued them.
+Every `:Job` is the hub for its visits, quotes, valuations, variations, milestones, and costs,
+satisfying the ≥1-adjacency write-gate doctrine. Quote lines are reached from the job through
+the quote — `(:Job)-[:HAS_QUOTE]->(:Quote)-[:HAS_LINE]->(:QuoteLine)` — and each valuation links
+the lines it measures with `(:Valuation)-[:VALUES]->(:QuoteLine)`. A job links to its customer
+and site; an asset hangs off the site it lives at. Costs link to the engineer who incurred them.
+Procurement is a `:PurchaseOrder` of `:PurchaseOrderLine`s for `:Part`s from a `:Supplier`; the
+received supplier invoice is an `:InboundInvoice` on that PO. A `:PpmContract` is a
+planned-maintenance agreement for a customer/site, distinct from a reactive `:Job`.
 
 ---
 
 ## Filesystem ↔ graph (base template)
 
-The graph is a disciplined projection of the operator's job folder: every node corresponds to a filesystem artefact, and the edges follow the folder containment. This mapping is the **base template** — the default a standard building-contractor job folder projects into. It is shipped-generic; the folder names, sheet names and trade list below are the common default, not any operator's data.
+The graph is the canonical ontology; the operator's job folder is a conforming projection of it.
+Every node corresponds to a filesystem artefact, and the edges follow the folder containment.
+This mapping is the **base template** — the default a standard field-service job folder projects
+into. It is shipped-generic; the folder names below are the common default, not any operator's
+data. On any divergence, the graph is canonical.
 
 A standard job folder, `{jobId} - {name}, {address} ({client})/`, projects as:
 
 | Folder / artefact | Node | Edge from the job |
 |---|---|---|
-| the job folder itself | `:Job` | — (the hub); `(:Job)-[:FOR_CLIENT]->(:Person)`, `(:Job)-[:AT_ADDRESS]->(:PostalAddress)` |
-| `Quotations/` — the client quote (`Q {jobId}`) and its priced schedule | `:QuoteDocument`; its priced rows → `:LineItem` | `(:Job)-[:HAS_QUOTE]->(:QuoteDocument)-[:HAS_LINE_ITEM]->(:LineItem)` |
-| `Finances/Valuations/` — one interim valuation per cycle | `:Valuation`; each measures the priced lines | `(:Job)-[:HAS_VALUATION]->(:Valuation)-[:VALUES]->(:LineItem)` |
+| the job folder itself | `:Job` | — (the hub); `(:Job)-[:FOR_CUSTOMER]->(:Customer)`, `(:Job)-[:AT_SITE]->(:Site)` |
+| `Quotations/` — the client quote and its priced schedule | `:Quote`; its priced rows → `:QuoteLine` | `(:Job)-[:HAS_QUOTE]->(:Quote)-[:HAS_LINE]->(:QuoteLine)` |
+| `Finances/Valuations/` — one interim valuation per cycle | `:Valuation`; each measures the priced lines | `(:Job)-[:HAS_VALUATION]->(:Valuation)-[:VALUES]->(:QuoteLine)` |
 | the variations register | `:VariationNote` | `(:Job)-[:HAS_VARIATION]->(:VariationNote)` |
-| `Contractors/<Trade>/{Enquiries,Quotes,Invoices,Superseded}` | `:Organization`; invoices → `:InboundInvoice` | `(:InboundInvoice)-[:ASSIGNED_TO]->(:Job)`, `(:InboundInvoice)-[:FROM_SUPPLIER]->(:Organization)` |
-| `Suppliers/<Supplier>/{Enquiries,Quotes,Invoices,Superseded}` | `:Organization`; invoices → `:InboundInvoice` | `(:InboundInvoice)-[:ASSIGNED_TO]->(:Job)`, `(:InboundInvoice)-[:FROM_SUPPLIER]->(:Organization)` |
-| `Drawings/`, `Health & Safety/`, `Emails/`, `Snagging/`, `Meetings/`, `Programs/`, `Materials/`, `Admin/` | ingested documents (`:KnowledgeDocument` + `:Section`) | linked to the `:Job` |
-
-A contractor who keeps the whole job in one master workbook holds the same model in sheets rather than folders: a cover/calculation sheet is the priced schedule (`:QuoteDocument` + `:LineItem`s), one sheet per valuation cycle is a `:Valuation` measuring those lines, a variations sheet is the `:VariationNote` register, and per-trade sheets are the sub-contractor packages. Folder and workbook are two views of one job; both project into this same graph.
-
-Operators vary this template — they rename folders, add trades, restructure their workbook. This template is the shipped-generic default the agent projects against; the graph follows this one canonical ontology, not a per-operator schema. Where a real folder does not fit the default, the agent maps it to the nearest canonical node rather than inventing a node or edge type absent from this reference.
+| `Costs/` — labour days, materials, travel, mileage, expenses, subcontractor | `:JobCost` (by `costType`) | `(:Job)-[:HAS_COST]->(:JobCost)-[:INCURRED_BY]->(:Engineer)` |
+| `Visits/` — attendance records | `:Visit` | `(:Job)-[:HAS_VISIT]->(:Visit)-[:ATTENDED_BY]->(:Engineer)` |
+| `Suppliers/<Supplier>/{Quotes,POs,Invoices}` | `:Organization:Supplier`; POs → `:PurchaseOrder`+`:PurchaseOrderLine`; received invoices → `:InboundInvoice` | `(:PurchaseOrder)-[:FROM_SUPPLIER]->(:Supplier)`, `(:InboundInvoice)-[:ON_PURCHASE_ORDER]->(:PurchaseOrder)` |
+| `Assets/` — serviced plant on the site | `:Asset` | `(:Site)-[:HAS_ASSET]->(:Asset)` |
+| `Drawings/`, `Health & Safety/`, `Emails/`, `Snagging/`, `Admin/` | ingested documents (`:KnowledgeDocument` + `:Section`) | linked to the `:Job` |
+
+A contractor who keeps the whole job in one master workbook holds the same model in sheets
+rather than folders: a cover/calculation sheet is the priced schedule (`:Quote` + `:QuoteLine`s),
+one sheet per valuation cycle is a `:Valuation`, a variations sheet is the `:VariationNote`
+register, a costs sheet is the `:JobCost` lines, and per-supplier sheets are the procurement
+packages. Folder and workbook are two views of one job; both project into this same graph.
+
+Operators vary this template — they rename folders, add trades, restructure their workbook. This
+template is the shipped-generic default the agent projects against; the graph follows this one
+canonical ontology, not a per-operator schema. Where a real folder does not fit the default, the
+agent maps it to the nearest canonical node rather than inventing a node or edge type absent from
+this reference.

package/payload/platform/plugins/memory/references/schema-trades.md

@@ -1,36 +1,34 @@
 # Schema Reference — Trades
 
-Vertical schema for `businessType: "trades"` — home services, construction, and tradespeople (plumber, electrician, builder, decorator).
+Vertical schema for `businessType: "trades"` — home services and tradespeople (plumber,
+electrician, builder, decorator). Trades and construction share the **one canonical SiteDesk
+service-delivery ontology** authored from JobLogic (see `schema-construction.md` for the full
+label set, properties, idempotency keys, relationships, and the filesystem↔graph template).
+There are no trades-specific labels that diverge from the canonical model.
 
-This reference extends the base schema. All base node types (Person, Organization, Order, Event, Invoice, Service, etc.) remain valid. Load `schema-base.md` first.
+This reference extends the base schema. All base node types (Person, Organization, Order, Event,
+Invoice, Service, etc.) remain valid. Load `schema-base.md` first.
 
 When loading this reference, confirm: "Using schema-base + schema-trades".
 
 ---
 
-## Additional Node Types
+## Canonical labels for the trades case
 
-| Entity | Neo4j Label | Schema.org Type | Required Properties |
-|--------|-------------|-----------------|---------------------|
-| Quote | `Quote` | `schema:Order` + `cdm:Opportunity` | `accountId`, `quoteNumber`, `customer` (id), `lineItems`, `validUntil`, `totalPrice` |
-| SiteVisit | `SiteVisit` | `schema:Event` (subtype) | `accountId`, `address` (id), `engineer` (id), `startDate`, `purpose` |
-| Inspection | `Inspection` | `cdm:Case` (subtype) | `accountId`, `address` (id), `findings`, `recommendations`, `photos` |
-| Certification | `Certification` | `schema:DigitalDocument` | `accountId`, `type` (gas safe, NICEIC, etc.), `issuedDate`, `expiryDate` |
-| Material | `Material` | `schema:Product` | `accountId`, `name`, `sku`, `unitCost`, `supplier` (id) |
+A tradesperson's work maps onto the same canonical labels as a contractor's:
 
-### Quote vs base Order
+| Trades concept | Canonical label | Notes |
+|----------------|-----------------|-------|
+| The job / call-out | Job | `jobType` distinguishes Call out / Installation / Maintenance / Reactive |
+| Customer and the work address | Customer, Site | site is the work location, distinct from the customer |
+| An attendance / site visit | Visit | the lifecycle attendance record on a job (was the homegrown SiteVisit) |
+| The estimate / quote | Quote, QuoteLine | priced estimate and its lines |
+| Parts and materials used | Part, JobCost (costType material) | catalogue part vs the incurred material cost on a job |
+| Serviced equipment on site | Asset | boiler, AC unit, alarm panel, etc. |
+| A planned-maintenance agreement | PpmContract | recurring service contract, distinct from a reactive Job |
 
-`Quote` is the trades-specific label for estimates and quotes before acceptance. Use `Quote` (not `Order`) when the work is proposed but not yet confirmed. Once a quote is accepted, create a base `Order` node linked to it, or update the Quote's `orderStatus` to reflect acceptance.
+Trade certifications (Gas Safe, NICEIC, Part P) a person holds are recorded as a credential on
+that person's `:Person` node via the base credential model, not as a separate construction label.
+Inspection findings are recorded as notes/documents on the `:Visit` or `:Asset` they concern.
 
----
-
-## Relationship Patterns
-
-```
-(:Order)-[:REQUIRES_VISIT]->(:SiteVisit)
-(:Order)-[:USES_MATERIAL]->(:Material)
-(:SiteVisit)-[:AT_ADDRESS]->(:PostalAddress)
-(:Certification)-[:HELD_BY]->(:Person)
-```
-
-The `(:Certification)-[:HELD_BY]->(:Person)` relationship tracks which staff member holds a trade certification (e.g., Gas Safe, NICEIC, Part P).
+See `schema-construction.md` for the authoritative definition of every label above.

package/payload/platform/services/claude-session-manager/dist/canonical-tool-names.generated.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"canonical-tool-names.generated.d.ts","sourceRoot":"","sources":["../src/canonical-tool-names.generated.ts"],"names":[],"mappings":"AAQA,+EAA+E;AAC/E,eAAO,MAAM,gBAAgB,EAAE,SAAS,MAAM,EAkB7C,CAAA;AAED,gEAAgE;AAChE,eAAO,MAAM,yBAAyB,EAAE,SAAS,MAAM,EAqMtD,CAAA"}
+{"version":3,"file":"canonical-tool-names.generated.d.ts","sourceRoot":"","sources":["../src/canonical-tool-names.generated.ts"],"names":[],"mappings":"AAQA,+EAA+E;AAC/E,eAAO,MAAM,gBAAgB,EAAE,SAAS,MAAM,EAmB7C,CAAA;AAED,gEAAgE;AAChE,eAAO,MAAM,yBAAyB,EAAE,SAAS,MAAM,EAkPtD,CAAA"}

package/payload/platform/services/claude-session-manager/dist/canonical-tool-names.generated.js

@@ -14,6 +14,7 @@ export const MAXY_MCP_PLUGINS = [
     "email",
     "graph",
     "graph-viewer",
+    "joblogic",
     "memory",
     "outlook",
     "quickbooks",
@@ -109,6 +110,51 @@ export const CANONICAL_MAXY_TOOL_NAMES = [
     "mcp__plugin_graph_graph__maxy-graph-get_neo4j_schema",
     "mcp__plugin_graph_graph__maxy-graph-read_neo4j_cypher",
     "mcp__plugin_graph_graph__maxy-graph-write_neo4j_cypher",
+    "mcp__plugin_joblogic_joblogic__joblogic-asset-create",
+    "mcp__plugin_joblogic_joblogic__joblogic-asset-get",
+    "mcp__plugin_joblogic_joblogic__joblogic-asset-list",
+    "mcp__plugin_joblogic_joblogic__joblogic-asset-update",
+    "mcp__plugin_joblogic_joblogic__joblogic-attachment-url-generate",
+    "mcp__plugin_joblogic_joblogic__joblogic-connection-status",
+    "mcp__plugin_joblogic_joblogic__joblogic-credentials-set",
+    "mcp__plugin_joblogic_joblogic__joblogic-customer-create",
+    "mcp__plugin_joblogic_joblogic__joblogic-customer-get",
+    "mcp__plugin_joblogic_joblogic__joblogic-customer-list",
+    "mcp__plugin_joblogic_joblogic__joblogic-customer-update",
+    "mcp__plugin_joblogic_joblogic__joblogic-engineer-get",
+    "mcp__plugin_joblogic_joblogic__joblogic-engineer-list",
+    "mcp__plugin_joblogic_joblogic__joblogic-engineer-map-list",
+    "mcp__plugin_joblogic_joblogic__joblogic-engineer-map-set",
+    "mcp__plugin_joblogic_joblogic__joblogic-invoice-create",
+    "mcp__plugin_joblogic_joblogic__joblogic-invoice-get",
+    "mcp__plugin_joblogic_joblogic__joblogic-invoice-list",
+    "mcp__plugin_joblogic_joblogic__joblogic-invoice-payment-create",
+    "mcp__plugin_joblogic_joblogic__joblogic-job-approve",
+    "mcp__plugin_joblogic_joblogic__joblogic-job-create",
+    "mcp__plugin_joblogic_joblogic__joblogic-job-get",
+    "mcp__plugin_joblogic_joblogic__joblogic-job-list",
+    "mcp__plugin_joblogic_joblogic__joblogic-job-set-status",
+    "mcp__plugin_joblogic_joblogic__joblogic-job-update",
+    "mcp__plugin_joblogic_joblogic__joblogic-jobcost-create",
+    "mcp__plugin_joblogic_joblogic__joblogic-jobcost-update",
+    "mcp__plugin_joblogic_joblogic__joblogic-note-create",
+    "mcp__plugin_joblogic_joblogic__joblogic-quote-approve",
+    "mcp__plugin_joblogic_joblogic__joblogic-quote-create",
+    "mcp__plugin_joblogic_joblogic__joblogic-quote-get",
+    "mcp__plugin_joblogic_joblogic__joblogic-quote-list",
+    "mcp__plugin_joblogic_joblogic__joblogic-site-create",
+    "mcp__plugin_joblogic_joblogic__joblogic-site-get",
+    "mcp__plugin_joblogic_joblogic__joblogic-site-list",
+    "mcp__plugin_joblogic_joblogic__joblogic-site-update",
+    "mcp__plugin_joblogic_joblogic__joblogic-timesheet-create",
+    "mcp__plugin_joblogic_joblogic__joblogic-timesheet-list",
+    "mcp__plugin_joblogic_joblogic__joblogic-timesheet-update",
+    "mcp__plugin_joblogic_joblogic__joblogic-visit-cancel",
+    "mcp__plugin_joblogic_joblogic__joblogic-visit-create",
+    "mcp__plugin_joblogic_joblogic__joblogic-visit-deploy",
+    "mcp__plugin_joblogic_joblogic__joblogic-visit-get",
+    "mcp__plugin_joblogic_joblogic__joblogic-visit-search-planner",
+    "mcp__plugin_joblogic_joblogic__joblogic-visit-update",
     "mcp__plugin_memory_memory__conversation-archive-derive-insights",
     "mcp__plugin_memory_memory__conversation-archive-enrich-rejection",
     "mcp__plugin_memory_memory__conversation-archive-list-chunks",

package/payload/platform/services/claude-session-manager/dist/canonical-tool-names.generated.js.map

@@ -1 +1 @@
-{"version":3,"file":"canonical-tool-names.generated.js","sourceRoot":"","sources":["../src/canonical-tool-names.generated.ts"],"names":[],"mappings":"AAAA,mCAAmC;AACnC,kEAAkE;AAClE,yDAAyD;AACzD,kFAAkF;AAClF,EAAE;AACF,yEAAyE;AACzE,6DAA6D;AAE7D,+EAA+E;AAC/E,MAAM,CAAC,MAAM,gBAAgB,GAAsB;IACjD,OAAO;IACP,KAAK;IACL,SAAS;IACT,UAAU;IACV,OAAO;IACP,OAAO;IACP,cAAc;IACd,QAAQ;IACR,SAAS;IACT,YAAY;IACZ,WAAW;IACX,YAAY;IACZ,UAAU;IACV,SAAS;IACT,UAAU;IACV,MAAM;IACN,WAAW;CACZ,CAAA;AAED,gEAAgE;AAChE,MAAM,CAAC,MAAM,yBAAyB,GAAsB;IAC1D,yCAAyC;IACzC,yCAAyC;IACzC,yCAAyC;IACzC,yCAAyC;IACzC,uCAAuC;IACvC,wCAAwC;IACxC,yCAAyC;IACzC,sCAAsC;IACtC,yCAAyC;IACzC,wCAAwC;IACxC,oCAAoC;IACpC,yCAAyC;IACzC,qCAAqC;IACrC,uCAAuC;IACvC,2CAA2C;IAC3C,4CAA4C;IAC5C,qCAAqC;IACrC,yCAAyC;IACzC,4CAA4C;IAC5C,oCAAoC;IACpC,sCAAsC;IACtC,0CAA0C;IAC1C,uCAAuC;IACvC,sCAAsC;IACtC,sDAAsD;IACtD,mDAAmD;IACnD,6CAA6C;IAC7C,wCAAwC;IACxC,yCAAyC;IACzC,qCAAqC;IACrC,uCAAuC;IACvC,sCAAsC;IACtC,wCAAwC;IACxC,+BAA+B;IAC/B,qCAAqC;IACrC,sCAAsC;IACtC,yCAAyC;IACzC,4CAA4C;IAC5C,uDAAuD;IACvD,+CAA+C;IAC/C,2CAA2C;IAC3C,gDAAgD;IAChD,oDAAoD;IACpD,4CAA4C;IAC5C,+CAA+C;IAC/C,+CAA+C;IAC/C,gDAAgD;IAChD,6CAA6C;IAC7C,6CAA6C;IAC7C,iDAAiD;IACjD,oDAAoD;IACpD,+CAA+C;IAC/C,2CAA2C;IAC3C,2CAA2C;IAC3C,+CAA+C;IAC/C,+CAA+C;IAC/C,+CAA+C;IAC/C,8CAA8C;IAC9C,+CAA+C;IAC/C,6CAA6C;IAC7C,+CAA+C;IAC/C,+CAA+C;IAC/C,6CAA6C;IAC7C,6CAA6C;IAC7C,sCAAsC;IACtC,2CAA2C;IAC3C,2CAA2C;IAC3C,sCAAsC;IACtC,4CAA4C;IAC5C,uCAAuC;IACvC,4CAA4C;IAC5C,8CAA8C;IAC9C,qCAAqC;IACrC,sCAAsC;IACtC,uCAAuC;IACvC,qCAAqC;IACrC,sCAAsC;IACtC,uCAAuC;IACvC,qDAAqD;IACrD,sDAAsD;IACtD,uDAAuD;IACvD,wDAAwD;IACxD,iEAAiE;IACjE,kEAAkE;IAClE,6DAA6D;IAC7D,8CAA8C;IAC9C,wDAAwD;IACxD,gDAAgD;IAChD,qDAAqD;IACrD,sDAAsD;IACtD,wDAAwD;IACxD,wCAAwC;IACxC,wCAAwC;IACxC,iDAAiD;IACjD,wDAAwD;IACxD,0DAA0D;IAC1D,0CAA0C;IAC1C,6CAA6C;IAC7C,wCAAwC;IACxC,mDAAmD;IACnD,+CAA+C;IAC/C,mDAAmD;IACnD,0CAA0C;IAC1C,kDAAkD;IAClD,8CAA8C;IAC9C,oDAAoD;IACpD,kDAAkD;IAClD,+CAA+C;IAC/C,mDAAmD;IACnD,2CAA2C;IAC3C,qDAAqD;IACrD,+CAA+C;IAC/C,sDAAsD;IACtD,gDAAgD;IAChD,2CAA2C;IAC3C,gDAAgD;IAChD,0CAA0C;IAC1C,0CAA0C;IAC1C,kDAAkD;IAClD,yCAAyC;IACzC,kDAAkD;IAClD,2CAA2C;IAC3C,yCAAyC;IACzC,2CAA2C;IAC3C,4CAA4C;IAC5C,mDAAmD;IACnD,uDAAuD;IACvD,qDAAqD;IACrD,oDAAoD;IACpD,oDAAoD;IACpD,gDAAgD;IAChD,kDAAkD;IAClD,mDAAmD;IACnD,6DAA6D;IAC7D,2DAA2D;IAC3D,2DAA2D;IAC3D,+DAA+D;IAC/D,+DAA+D;IAC/D,+DAA+D;IAC/D,0DAA0D;IAC1D,6DAA6D;IAC7D,6DAA6D;IAC7D,8DAA8D;IAC9D,8DAA8D;IAC9D,8DAA8D;IAC9D,qDAAqD;IACrD,sDAAsD;IACtD,2DAA2D;IAC3D,iDAAiD;IACjD,sDAAsD;IACtD,uDAAuD;IACvD,yDAAyD;IACzD,oDAAoD;IACpD,mDAAmD;IACnD,wDAAwD;IACxD,iDAAiD;IACjD,wDAAwD;IACxD,kDAAkD;IAClD,oDAAoD;IACpD,iDAAiD;IACjD,wCAAwC;IACxC,gDAAgD;IAChD,0DAA0D;IAC1D,sCAAsC;IACtC,kDAAkD;IAClD,gDAAgD;IAChD,kEAAkE;IAClE,uDAAuD;IACvD,oDAAoD;IACpD,oDAAoD;IACpD,qDAAqD;IACrD,oDAAoD;IACpD,kDAAkD;IAClD,gDAAgD;IAChD,yCAAyC;IACzC,uCAAuC;IACvC,oCAAoC;IACpC,qCAAqC;IACrC,uCAAuC;IACvC,qCAAqC;IACrC,qCAAqC;IACrC,sCAAsC;IACtC,oCAAoC;IACpC,iCAAiC;IACjC,kCAAkC;IAClC,mCAAmC;IACnC,oCAAoC;IACpC,oCAAoC;IACpC,kDAAkD;IAClD,kDAAkD;IAClD,mDAAmD;IACnD,+CAA+C;IAC/C,gDAAgD;IAChD,gDAAgD;IAChD,kDAAkD;IAClD,oDAAoD;CACrD,CAAA"}
+{"version":3,"file":"canonical-tool-names.generated.js","sourceRoot":"","sources":["../src/canonical-tool-names.generated.ts"],"names":[],"mappings":"AAAA,mCAAmC;AACnC,kEAAkE;AAClE,yDAAyD;AACzD,kFAAkF;AAClF,EAAE;AACF,yEAAyE;AACzE,6DAA6D;AAE7D,+EAA+E;AAC/E,MAAM,CAAC,MAAM,gBAAgB,GAAsB;IACjD,OAAO;IACP,KAAK;IACL,SAAS;IACT,UAAU;IACV,OAAO;IACP,OAAO;IACP,cAAc;IACd,UAAU;IACV,QAAQ;IACR,SAAS;IACT,YAAY;IACZ,WAAW;IACX,YAAY;IACZ,UAAU;IACV,SAAS;IACT,UAAU;IACV,MAAM;IACN,WAAW;CACZ,CAAA;AAED,gEAAgE;AAChE,MAAM,CAAC,MAAM,yBAAyB,GAAsB;IAC1D,yCAAyC;IACzC,yCAAyC;IACzC,yCAAyC;IACzC,yCAAyC;IACzC,uCAAuC;IACvC,wCAAwC;IACxC,yCAAyC;IACzC,sCAAsC;IACtC,yCAAyC;IACzC,wCAAwC;IACxC,oCAAoC;IACpC,yCAAyC;IACzC,qCAAqC;IACrC,uCAAuC;IACvC,2CAA2C;IAC3C,4CAA4C;IAC5C,qCAAqC;IACrC,yCAAyC;IACzC,4CAA4C;IAC5C,oCAAoC;IACpC,sCAAsC;IACtC,0CAA0C;IAC1C,uCAAuC;IACvC,sCAAsC;IACtC,sDAAsD;IACtD,mDAAmD;IACnD,6CAA6C;IAC7C,wCAAwC;IACxC,yCAAyC;IACzC,qCAAqC;IACrC,uCAAuC;IACvC,sCAAsC;IACtC,wCAAwC;IACxC,+BAA+B;IAC/B,qCAAqC;IACrC,sCAAsC;IACtC,yCAAyC;IACzC,4CAA4C;IAC5C,uDAAuD;IACvD,+CAA+C;IAC/C,2CAA2C;IAC3C,gDAAgD;IAChD,oDAAoD;IACpD,4CAA4C;IAC5C,+CAA+C;IAC/C,+CAA+C;IAC/C,gDAAgD;IAChD,6CAA6C;IAC7C,6CAA6C;IAC7C,iDAAiD;IACjD,oDAAoD;IACpD,+CAA+C;IAC/C,2CAA2C;IAC3C,2CAA2C;IAC3C,+CAA+C;IAC/C,+CAA+C;IAC/C,+CAA+C;IAC/C,8CAA8C;IAC9C,+CAA+C;IAC/C,6CAA6C;IAC7C,+CAA+C;IAC/C,+CAA+C;IAC/C,6CAA6C;IAC7C,6CAA6C;IAC7C,sCAAsC;IACtC,2CAA2C;IAC3C,2CAA2C;IAC3C,sCAAsC;IACtC,4CAA4C;IAC5C,uCAAuC;IACvC,4CAA4C;IAC5C,8CAA8C;IAC9C,qCAAqC;IACrC,sCAAsC;IACtC,uCAAuC;IACvC,qCAAqC;IACrC,sCAAsC;IACtC,uCAAuC;IACvC,qDAAqD;IACrD,sDAAsD;IACtD,uDAAuD;IACvD,wDAAwD;IACxD,sDAAsD;IACtD,mDAAmD;IACnD,oDAAoD;IACpD,sDAAsD;IACtD,iEAAiE;IACjE,2DAA2D;IAC3D,yDAAyD;IACzD,yDAAyD;IACzD,sDAAsD;IACtD,uDAAuD;IACvD,yDAAyD;IACzD,sDAAsD;IACtD,uDAAuD;IACvD,2DAA2D;IAC3D,0DAA0D;IAC1D,wDAAwD;IACxD,qDAAqD;IACrD,sDAAsD;IACtD,gEAAgE;IAChE,qDAAqD;IACrD,oDAAoD;IACpD,iDAAiD;IACjD,kDAAkD;IAClD,wDAAwD;IACxD,oDAAoD;IACpD,wDAAwD;IACxD,wDAAwD;IACxD,qDAAqD;IACrD,uDAAuD;IACvD,sDAAsD;IACtD,mDAAmD;IACnD,oDAAoD;IACpD,qDAAqD;IACrD,kDAAkD;IAClD,mDAAmD;IACnD,qDAAqD;IACrD,0DAA0D;IAC1D,wDAAwD;IACxD,0DAA0D;IAC1D,sDAAsD;IACtD,sDAAsD;IACtD,sDAAsD;IACtD,mDAAmD;IACnD,8DAA8D;IAC9D,sDAAsD;IACtD,iEAAiE;IACjE,kEAAkE;IAClE,6DAA6D;IAC7D,8CAA8C;IAC9C,wDAAwD;IACxD,gDAAgD;IAChD,qDAAqD;IACrD,sDAAsD;IACtD,wDAAwD;IACxD,wCAAwC;IACxC,wCAAwC;IACxC,iDAAiD;IACjD,wDAAwD;IACxD,0DAA0D;IAC1D,0CAA0C;IAC1C,6CAA6C;IAC7C,wCAAwC;IACxC,mDAAmD;IACnD,+CAA+C;IAC/C,mDAAmD;IACnD,0CAA0C;IAC1C,kDAAkD;IAClD,8CAA8C;IAC9C,oDAAoD;IACpD,kDAAkD;IAClD,+CAA+C;IAC/C,mDAAmD;IACnD,2CAA2C;IAC3C,qDAAqD;IACrD,+CAA+C;IAC/C,sDAAsD;IACtD,gDAAgD;IAChD,2CAA2C;IAC3C,gDAAgD;IAChD,0CAA0C;IAC1C,0CAA0C;IAC1C,kDAAkD;IAClD,yCAAyC;IACzC,kDAAkD;IAClD,2CAA2C;IAC3C,yCAAyC;IACzC,2CAA2C;IAC3C,4CAA4C;IAC5C,mDAAmD;IACnD,uDAAuD;IACvD,qDAAqD;IACrD,oDAAoD;IACpD,oDAAoD;IACpD,gDAAgD;IAChD,kDAAkD;IAClD,mDAAmD;IACnD,6DAA6D;IAC7D,2DAA2D;IAC3D,2DAA2D;IAC3D,+DAA+D;IAC/D,+DAA+D;IAC/D,+DAA+D;IAC/D,0DAA0D;IAC1D,6DAA6D;IAC7D,6DAA6D;IAC7D,8DAA8D;IAC9D,8DAA8D;IAC9D,8DAA8D;IAC9D,qDAAqD;IACrD,sDAAsD;IACtD,2DAA2D;IAC3D,iDAAiD;IACjD,sDAAsD;IACtD,uDAAuD;IACvD,yDAAyD;IACzD,oDAAoD;IACpD,mDAAmD;IACnD,wDAAwD;IACxD,iDAAiD;IACjD,wDAAwD;IACxD,kDAAkD;IAClD,oDAAoD;IACpD,iDAAiD;IACjD,wCAAwC;IACxC,gDAAgD;IAChD,0DAA0D;IAC1D,sCAAsC;IACtC,kDAAkD;IAClD,gDAAgD;IAChD,kEAAkE;IAClE,uDAAuD;IACvD,oDAAoD;IACpD,oDAAoD;IACpD,qDAAqD;IACrD,oDAAoD;IACpD,kDAAkD;IAClD,gDAAgD;IAChD,yCAAyC;IACzC,uCAAuC;IACvC,oCAAoC;IACpC,qCAAqC;IACrC,uCAAuC;IACvC,qCAAqC;IACrC,qCAAqC;IACrC,sCAAsC;IACtC,oCAAoC;IACpC,iCAAiC;IACjC,kCAAkC;IAClC,mCAAmC;IACnC,oCAAoC;IACpC,oCAAoC;IACpC,kDAAkD;IAClD,kDAAkD;IAClD,mDAAmD;IACnD,+CAA+C;IAC/C,gDAAgD;IAChD,gDAAgD;IAChD,kDAAkD;IAClD,oDAAoD;CACrD,CAAA"}

package/payload/premium-plugins/sitedesk/plugins/sitedesk-job/skills/timesheet/SKILL.md

@@ -21,13 +21,13 @@ maths ([references/roll-up.md](references/roll-up.md)), and the two documents
 ## Two surfaces
 
 - **Worker setup (per worker, once).** Capture the worker's engagement, day rate, UTR (CIS only),
-  whether the 20% deduction shows, and the office invoice address. Store it as the `:Worker` config
+  whether the 20% deduction shows, and the office invoice address. Store it as the `:Engineer` config
   on his `:Person`. The worker logs his days through the receive-only `worker-checkin` agent; the
   platform's multi-channel transport delivers those messages into one session.
 
 - **Roll-up (operator-run, per period).** For a worker (or all workers) and a period:
   1. Read his check-ins for the period by `personId` — structure the worker's delivered messages
-     into `:CheckIn` records (one per working day) at this point.
+     into `:JobCost` records (one per working day) at this point.
   2. Run `rollup.mjs compute <worker.json> <checkins.json>` — never compute by hand.
   3. Render the timesheet (and, for CIS, the invoice) from the computed figures.
   4. Run `rollup.mjs reconcile <computed.json> <netPence> <dayHundredths>` — both gates must pass.

package/payload/premium-plugins/sitedesk/plugins/sitedesk-job/skills/timesheet/references/checkin-contract.md

@@ -2,30 +2,35 @@
 
 This skill ships these shapes, never a worker's data.
 
-## `:Worker` (operator config, one per worker)
+## `:Engineer` (operator config, one per worker)
 
-`(:Worker { personId, accountId, name, engagement: "employee"|"cis", dayRatePence,
+`(:Engineer { personId, accountId, name, engagement: "employee"|"cis", dayRatePence,
             utr?, showCisDeduction: bool, invoiceEmail, createdAt })`
 
 `personId` ties the worker to his `:Person`. `dayRatePence` is integer pence. `utr` is present
 only for `engagement: "cis"`. `invoiceEmail` is the office invoice address. Captured by the
 operator at runtime (see [setup.md](setup.md)), never written into this tree.
 
-## `:CheckIn` (one per working day, keyed to the worker, not the transport)
+## `:JobCost` (one labour cost per working day, `costType: "labour"`)
 
-`(:CheckIn { personId, accountId, source, receivedAt,
+`(:JobCost { costId, costType: "labour", personId, accountId, source, receivedAt,
              date, site, description, dayHundredths, createdAt })`
 
-`personId` is the unifying key — the roll-up reads every `:CheckIn` for the worker regardless of
-which channel produced it. `source` records the channel the message arrived on (`web`, `whatsapp`,
-…). `dayHundredths` is 100 for a full day; a smaller value only when the operator enabled part-day
-handling. One `:CheckIn` per working day.
-
-Each `:CheckIn` is linked to its worker's `:Person` with the canonical edge
-`(:Worker)-[:LOGGED]->(:CheckIn)` — the edge type is fixed by `schema-construction.md`; write no
-edge type absent from it. The edge satisfies the write-doctrine adjacency requirement (a node is
-written with at least one relationship); `personId` carries the same identity for roll-up reads.
+A logged labour day is an incurred labour cost. `costType` is `"labour"` and `costId` is the
+write-time MERGE key (`(accountId, costId)`) — use a deterministic id such as `${personId}-${date}`
+so re-delivery of the same day stays idempotent. `personId` is the roll-up read key: the roll-up
+reads every labour `:JobCost` for the worker regardless of which channel produced it. `source`
+records the channel the message arrived on (`web`, `whatsapp`, …). `dayHundredths` is 100 for a
+full day; a smaller value only when the operator enabled part-day handling. One labour `:JobCost`
+per working day.
+
+Each `:JobCost` is linked to the engineer who incurred it with the canonical edge
+`(:JobCost)-[:INCURRED_BY]->(:Engineer)` (an additional label on that worker's `:Person`), and to
+its job with `(:Job)-[:HAS_COST]->(:JobCost)` — the edge types are fixed by
+`schema-construction.md`; write no edge type absent from it. The edge satisfies the write-doctrine
+adjacency requirement (a node is written with at least one relationship); `personId` carries the
+same identity for roll-up reads.
 
 These records come from the worker's delivered messages. The platform's multi-channel transport
-delivers those messages into one session; the step that turns them into `:CheckIn` records is this
+delivers those messages into one session; the step that turns them into `:JobCost` records is this
 skill's roll-up (structure at roll-up — see [roll-up.md](roll-up.md)).

package/payload/premium-plugins/sitedesk/plugins/sitedesk-job/skills/timesheet/references/documents.md

@@ -7,7 +7,7 @@ operator's data; every figure comes from the roll-up engine, displayed never rec
 ## Timesheet — data regions (all required)
 
 - **Header** — worker name, period, office.
-- **Day schedule** — one row per `:CheckIn`: date, site, description, day count (full/part).
+- **Day schedule** — one row per `:JobCost`: date, site, description, day count (full/part).
 - **Day total** — the sum of the day counts. This is the figure the `reconcile` day gate checks.
 
 ## Invoice — data regions (all required)

package/payload/premium-plugins/sitedesk/plugins/sitedesk-job/skills/timesheet/references/roll-up.md

@@ -7,7 +7,7 @@ are computed by `rollup.mjs`, never by hand. The engine carries no operator cont
 
 A worker's daily messages arrive over whatever channel and the platform delivers them into one session.
 At roll-up time, read the worker's messages for the period and structure each working day into one
-`:CheckIn` (see [checkin-contract.md](checkin-contract.md)): `date`, `site`, `description`,
+`:JobCost` (see [checkin-contract.md](checkin-contract.md)): `date`, `site`, `description`,
 `dayHundredths`. One message-day = one check-in. Structuring happens here, in the operator-run step,
 not in the unattended receive path — so the operator can review before anything is sent.
 

package/payload/premium-plugins/sitedesk/plugins/sitedesk-job/skills/valuation/SKILL.md

@@ -33,8 +33,8 @@ valuation reconciles and is filed.
 
 ## Two surfaces
 
-- **Job setup (once).** Create or update the `:Job` and the `:QuoteDocument` the job is priced
-  from; seed the contract-works schedule as `:LineItem`s **on that `:QuoteDocument`** (not on the
+- **Job setup (once).** Create or update the `:Job` and the `:Quote` the job is priced
+  from; seed the contract-works schedule as `:QuoteLine`s **on that `:Quote`** (not on the
   `:Job`) from the generic contract-stage template
   ([references/contract-template.md](references/contract-template.md)), then take the operator's
   adjustments to descriptions, contract values and provisional sums; record the contract sum, VAT
@@ -81,18 +81,18 @@ fixed document is the defect.
 
 The job uses the existing construction-schema nodes **and relationships** as defined in
 `schema-construction.md`, the authority for both the node labels and the edge types; this skill
-invents neither. `:Job` is the hub: it links to its client `:Person` (`FOR_CLIENT`), site
-`:PostalAddress` (`AT_ADDRESS`), `:QuoteDocument` (`HAS_QUOTE`), `:Valuation`s (`HAS_VALUATION`)
+invents neither. `:Job` is the hub: it links to its `:Customer` (`FOR_CUSTOMER`), its `:Site`
+(`AT_SITE`), `:Quote` (`HAS_QUOTE`), `:Valuation`s (`HAS_VALUATION`)
 and `:VariationNote`s (`HAS_VARIATION`).
 
-Line items are owned by the quote, not the job: a `:LineItem` is one row of the priced contract
-schedule, held under the `:QuoteDocument` (`(:QuoteDocument)-[:HAS_LINE_ITEM]->(:LineItem)`) and
+Line items are owned by the quote, not the job: a `:QuoteLine` is one row of the priced contract
+schedule, held under the `:Quote` (`(:Quote)-[:HAS_LINE]->(:QuoteLine)`) and
 reached from the job through the quote. Each issued valuation links the lines it measures with
-`(:Valuation)-[:VALUES]->(:LineItem)`.
+`(:Valuation)-[:VALUES]->(:QuoteLine)`.
 
 The nodes are idempotent on their natural keys — `:Valuation` on
 `(accountId, jobId, valuationNumber)`, `:VariationNote` on `(accountId, jobId, variationNumber)`,
-`:LineItem` on `(accountId, jobId, trade, description)`. Per-line `% complete`, per-line comment
+`:QuoteLine` on `(accountId, jobId, trade, description)`. Per-line `% complete`, per-line comment
 and per-variation `% complete` are **carried cycle state**, not fixed node properties — they live
 in `engine-state.json` and the `:Valuation` snapshot body, never as new labels or properties; the
 `VALUES` edge only identifies which lines a valuation measures, it does not carry the percentage.

package/payload/premium-plugins/sitedesk/plugins/sitedesk-job/skills/valuation/references/contract-template.md

@@ -2,7 +2,7 @@
 
 Job setup seeds the contract-works schedule from a generic new-build stage list. This template
 is **stage names only**: it carries no values, no rates, no quantities, and no client data. Its
-sole purpose is to give the operator a familiar starting skeleton of `:LineItem` rows to adjust.
+sole purpose is to give the operator a familiar starting skeleton of `:QuoteLine` rows to adjust.
 
 A standard new-build sequence:
 
@@ -22,7 +22,7 @@ A standard new-build sequence:
 
 ## How it seeds a job
 
-At setup, each stage name becomes one `:LineItem` with an empty contract value. The operator
+At setup, each stage name becomes one `:QuoteLine` with an empty contract value. The operator
 then adjusts: renames or removes stages that do not apply, adds stages the job has, and sets
 each line's contract value and any provisional sums — all from the operator's own contract, none
 of it carried here. A job whose schedule looks nothing like a new-build (a refurbishment, a

package/payload/premium-plugins/sitedesk/plugins/sitedesk-job/skills/valuation/references/issue-flow.md

@@ -80,9 +80,9 @@ an unrelated purge, so nothing keys off it. Carry the per-line and per-variation
 
 Connect the `:Valuation` to its job with the canonical edge `(:Job)-[:HAS_VALUATION]->(:Valuation)`
 — never an invented type such as `VALUATION_FOR`. Link the lines this valuation measures with
-`(:Valuation)-[:VALUES]->(:LineItem)`, reading those lines through the quote
-(`(:Job)-[:HAS_QUOTE]->(:QuoteDocument)-[:HAS_LINE_ITEM]->(:LineItem)`) — line items belong to the
-`:QuoteDocument`, never written directly onto the `:Job`. The edge types are fixed by
+`(:Valuation)-[:VALUES]->(:QuoteLine)`, reading those lines through the quote
+(`(:Job)-[:HAS_QUOTE]->(:Quote)-[:HAS_LINE]->(:QuoteLine)`) — line items belong to the
+`:Quote`, never written directly onto the `:Job`. The edge types are fixed by
 `schema-construction.md`; write no edge type absent from it. Account scope is the `accountId`
 property, never an ownership edge.