@rubytech/create-maxy-code 0.1.348 → 0.1.350

package/payload/platform/neo4j/schema.cypher

@@ -447,7 +447,8 @@ DROP INDEX entity_search_admin IF EXISTS;
 CREATE FULLTEXT INDEX entity_search_admin IF NOT EXISTS
 FOR (n:LocalBusiness|Service|PriceSpecification|OpeningHoursSpecification|Organization
     |Listing|Property|Viewing|Offer|PostalAddress
-    |Job|LineItem|Valuation|Milestone|QuoteDocument|VariationNote|InboundInvoice|CheckIn|WhatsAppGroup
+    |Job|Quote|QuoteLine|Valuation|Milestone|VariationNote|Invoice|InboundInvoice|JobCost|WhatsAppGroup
+    |Customer|Site|Asset|Visit|Part|PurchaseOrder|PpmContract|Contact|PurchaseOrderLine|InvoiceLine|InvoicePayment|Credit
     |Person|UserProfile|Preference|AdminUser|AccessGrant
     |KnowledgeDocument|ConversationArchive|Section|Chunk|DigitalDocument|CreativeWork|Question|FAQPage|DefinedTerm|Review|ImageObject
     |Conversation|AdminConversation|PublicConversation|Message|UserMessage|AssistantMessage|ToolCall
@@ -1348,22 +1349,27 @@ CREATE INDEX postal_address_postcode IF NOT EXISTS
 FOR (a:PostalAddress) ON (a.postalCode);
 
 // ----------------------------------------------------------
-// Construction ontology (Task 650) — Job-centric model for the
-// sitedesk-code brand, documented at
+// Construction / field-service ontology — the canonical SiteDesk
+// service-delivery model, authored from JobLogic's field-service domain
+// (Task 1084; supersedes the Task 650 homegrown set). Documented at
 // platform/plugins/memory/references/schema-construction.md.
 //
 // Active vertical: brand.json#vertical = "schema-construction". Declared
 // here so a fresh deploy registers each label before its first write
 // (same fresh-install bootstrap contract as the estate-agent block above).
 //
-// Uniqueness constraints where a clean natural key exists; accountId-index-
-// only for child nodes whose uniqueness is a write-time MERGE (LineItem,
-// Milestone, CheckIn) — mirrors :ImageObject. :Worker is an
-// additional label on :Person (no standalone node), so it carries no line of
-// its own here, same as :Applicant in the estate-agent block.
-//
-// Search quality (Task 652). The four text-bearing labels — :Job (client +
-// address), :LineItem (trade + description), :QuoteDocument, :VariationNote
+// Top-level natural-key labels: Job, Customer, Site, Asset, Visit, Quote,
+// Invoice (customer, outbound), InboundInvoice (supplier, on a PO), Part,
+// PurchaseOrder, PpmContract, WhatsAppGroup. Child
+// write-time-MERGE labels (accountId-index only, mirrors :ImageObject):
+// QuoteLine, Valuation, Milestone, VariationNote, JobCost, Contact,
+// PurchaseOrderLine, InvoiceLine, InvoicePayment, Credit. :Engineer (on
+// :Person) and :Supplier (on :Organization) are additional labels on a base
+// node — no standalone line here, same as :Applicant in the estate-agent
+// block.
+//
+// Search quality (Task 652; renamed Task 1084). The four text-bearing labels —
+// :Job, :QuoteLine (trade + description), its :Quote, :VariationNote
 // (description) — carry a vector index on `.embedding` (below), so the
 // graph-write chokepoint auto-embeds them on write and they rank in the
 // vector half of memory-search. The four are mirrored in
@@ -1394,11 +1400,16 @@ OPTIONS {
   }
 };
 
-CREATE INDEX line_item_account IF NOT EXISTS
-FOR (li:LineItem) ON (li.accountId);
+// :LineItem -> :QuoteLine (Task 1084). A priced row of the client :Quote
+// schedule, not an incurred cost. The old-named indexes are dropped so a
+// database seeded before the rename does not keep a dead :LineItem index.
+DROP INDEX line_item_account IF EXISTS;
+DROP INDEX line_item_embedding IF EXISTS;
+CREATE INDEX quote_line_account IF NOT EXISTS
+FOR (ql:QuoteLine) ON (ql.accountId);
 
-CREATE VECTOR INDEX line_item_embedding IF NOT EXISTS
-FOR (li:LineItem) ON (li.embedding)
+CREATE VECTOR INDEX quote_line_embedding IF NOT EXISTS
+FOR (ql:QuoteLine) ON (ql.embedding)
 OPTIONS {
   indexConfig: {
     `vector.dimensions`: 768,
@@ -1415,14 +1426,20 @@ FOR (v:Valuation) ON (v.accountId);
 CREATE INDEX milestone_account IF NOT EXISTS
 FOR (m:Milestone) ON (m.accountId);
 
-CREATE CONSTRAINT quote_document_account_ref_unique IF NOT EXISTS
-FOR (q:QuoteDocument) REQUIRE (q.accountId, q.ref) IS UNIQUE;
+// :QuoteDocument -> :Quote (Task 1084) — JobLogic's canonical term for the
+// priced estimate/contract. New constraint+index names (IF NOT EXISTS matches
+// by name); old names dropped so the rename takes on pre-seeded databases.
+DROP CONSTRAINT quote_document_account_ref_unique IF EXISTS;
+DROP INDEX quote_document_account IF EXISTS;
+DROP INDEX quote_document_embedding IF EXISTS;
+CREATE CONSTRAINT quote_account_ref_unique IF NOT EXISTS
+FOR (q:Quote) REQUIRE (q.accountId, q.ref) IS UNIQUE;
 
-CREATE INDEX quote_document_account IF NOT EXISTS
-FOR (q:QuoteDocument) ON (q.accountId);
+CREATE INDEX quote_account IF NOT EXISTS
+FOR (q:Quote) ON (q.accountId);
 
-CREATE VECTOR INDEX quote_document_embedding IF NOT EXISTS
-FOR (q:QuoteDocument) ON (q.embedding)
+CREATE VECTOR INDEX quote_embedding IF NOT EXISTS
+FOR (q:Quote) ON (q.embedding)
 OPTIONS {
   indexConfig: {
     `vector.dimensions`: 768,
@@ -1445,22 +1462,31 @@ OPTIONS {
   }
 };
 
-// Task 802 renamed the key property invoiceNumber -> confirmationNumber
-// (Schema.org canonical). The constraint gets a NEW name because
-// CREATE ... IF NOT EXISTS matches by constraint name: re-using the old
-// name would silently skip creation on databases seeded before the rename,
-// leaving the key unprotected. The old-name DROP retires the stale
-// invoiceNumber constraint on those databases; both statements are
-// idempotent on fresh installs.
+// Two distinct invoice documents (Task 1084). :InboundInvoice is the received
+// supplier invoice, keyed (accountId, supplier, confirmationNumber) and now
+// linked to a :PurchaseOrder. The customer-facing outbound invoice is the base
+// :Invoice (schema-base.md), registered here so it surfaces on /graph and in
+// search alongside the construction spine; its billing chain is the child
+// :InvoiceLine / :InvoicePayment / :Credit. The two labels coexist because they
+// carry different required fields (supplier vs customer). The Task-802 DROP of
+// the old invoiceNumber-keyed constraint is retained for pre-rename databases.
 DROP CONSTRAINT inbound_invoice_account_supplier_num_unique IF EXISTS;
 CREATE CONSTRAINT inbound_invoice_account_supplier_confirmation_unique IF NOT EXISTS
 FOR (ii:InboundInvoice) REQUIRE (ii.accountId, ii.supplier, ii.confirmationNumber) IS UNIQUE;
-
 CREATE INDEX inbound_invoice_account IF NOT EXISTS
 FOR (ii:InboundInvoice) ON (ii.accountId);
 
-CREATE INDEX checkin_account IF NOT EXISTS
-FOR (ci:CheckIn) ON (ci.accountId);
+CREATE INDEX invoice_account IF NOT EXISTS
+FOR (i:Invoice) ON (i.accountId);
+
+// :CheckIn -> :JobCost (Task 1084). A logged labour day is an incurred labour
+// cost (costType:'labour'); JobCost also carries material/travel/mileage/
+// expense/subcontractor/scheduleOfRates lines. Clean natural key (costId).
+DROP INDEX checkin_account IF EXISTS;
+CREATE CONSTRAINT job_cost_account_costid_unique IF NOT EXISTS
+FOR (jc:JobCost) REQUIRE (jc.accountId, jc.costId) IS UNIQUE;
+CREATE INDEX job_cost_account IF NOT EXISTS
+FOR (jc:JobCost) ON (jc.accountId);
 
 CREATE CONSTRAINT whatsapp_group_account_groupid_unique IF NOT EXISTS
 FOR (wg:WhatsAppGroup) REQUIRE (wg.accountId, wg.groupId) IS UNIQUE;
@@ -1468,6 +1494,59 @@ FOR (wg:WhatsAppGroup) REQUIRE (wg.accountId, wg.groupId) IS UNIQUE;
 CREATE INDEX whatsapp_group_account IF NOT EXISTS
 FOR (wg:WhatsAppGroup) ON (wg.accountId);
 
+// JobLogic service-delivery spine (Task 1084). Top-level natural-key labels.
+CREATE CONSTRAINT customer_account_customerid_unique IF NOT EXISTS
+FOR (c:Customer) REQUIRE (c.accountId, c.customerId) IS UNIQUE;
+CREATE INDEX customer_account IF NOT EXISTS
+FOR (c:Customer) ON (c.accountId);
+
+CREATE CONSTRAINT site_account_siteid_unique IF NOT EXISTS
+FOR (s:Site) REQUIRE (s.accountId, s.siteId) IS UNIQUE;
+CREATE INDEX site_account IF NOT EXISTS
+FOR (s:Site) ON (s.accountId);
+
+CREATE CONSTRAINT asset_account_assetid_unique IF NOT EXISTS
+FOR (a:Asset) REQUIRE (a.accountId, a.assetId) IS UNIQUE;
+CREATE INDEX asset_account IF NOT EXISTS
+FOR (a:Asset) ON (a.accountId);
+
+CREATE CONSTRAINT visit_account_visitid_unique IF NOT EXISTS
+FOR (v:Visit) REQUIRE (v.accountId, v.visitId) IS UNIQUE;
+CREATE INDEX visit_account IF NOT EXISTS
+FOR (v:Visit) ON (v.accountId);
+
+CREATE CONSTRAINT part_account_partid_unique IF NOT EXISTS
+FOR (p:Part) REQUIRE (p.accountId, p.partId) IS UNIQUE;
+CREATE INDEX part_account IF NOT EXISTS
+FOR (p:Part) ON (p.accountId);
+
+CREATE CONSTRAINT purchase_order_account_ponumber_unique IF NOT EXISTS
+FOR (po:PurchaseOrder) REQUIRE (po.accountId, po.poNumber) IS UNIQUE;
+CREATE INDEX purchase_order_account IF NOT EXISTS
+FOR (po:PurchaseOrder) ON (po.accountId);
+
+CREATE CONSTRAINT ppm_contract_account_contractid_unique IF NOT EXISTS
+FOR (pc:PpmContract) REQUIRE (pc.accountId, pc.contractId) IS UNIQUE;
+CREATE INDEX ppm_contract_account IF NOT EXISTS
+FOR (pc:PpmContract) ON (pc.accountId);
+
+// Child write-time-MERGE labels (accountId-index only; uniqueness is the
+// writer's MERGE key, mirrors :ImageObject / :Milestone).
+CREATE INDEX contact_account IF NOT EXISTS
+FOR (ct:Contact) ON (ct.accountId);
+
+CREATE INDEX purchase_order_line_account IF NOT EXISTS
+FOR (pol:PurchaseOrderLine) ON (pol.accountId);
+
+CREATE INDEX invoice_line_account IF NOT EXISTS
+FOR (il:InvoiceLine) ON (il.accountId);
+
+CREATE INDEX invoice_payment_account IF NOT EXISTS
+FOR (ip:InvoicePayment) ON (ip.accountId);
+
+CREATE INDEX credit_account IF NOT EXISTS
+FOR (cr:Credit) ON (cr.accountId);
+
 // ----------------------------------------------------------
 // Voice Mirror (Task 356 + Task 462) — authorial-voice capture + application
 // ----------------------------------------------------------

package/payload/platform/plugins/.claude-plugin/marketplace.json

@@ -59,6 +59,11 @@
       "source": "./graph-viewer",
       "version": "0.1.0"
     },
+    {
+      "name": "joblogic",
+      "source": "./joblogic",
+      "version": "0.1.0"
+    },
     {
       "name": "linkedin-extension",
       "source": "./linkedin-extension",

package/payload/platform/plugins/admin/hooks/__tests__/fs-schema-guard.test.sh

@@ -0,0 +1,68 @@
+#!/usr/bin/env bash
+# Regression test for fs-schema-guard.sh.
+#
+# Covers:
+#   1. Non-Write/Edit/NotebookEdit tool                    -> ALLOW (early exit)
+#   2. Write to projects/Acme/a.txt (flat)                 -> ALLOW
+#   3. Write to documents/a.pdf (loose)                    -> ALLOW
+#   4. Write to output/deep/nested/x.png (tool-owned)      -> ALLOW (any depth)
+#   5. Write to projects/Acme/deploy/sources/a.txt         -> BLOCK over-deep
+#   6. Write to projects/Acme/deploy/a.txt                 -> BLOCK over-deep
+#   7. Write to whim/x.txt (novel top-level)               -> BLOCK top-level
+#   8. Write to an absolute path outside the account dir   -> ALLOW (not our concern)
+#   9. NotebookEdit over-deep (notebook_path)              -> BLOCK over-deep
+#  10. Empty stdin (cannot inspect)                        -> BLOCK fail-closed
+#  11. Allowed-set parse matches the documented set        -> assertion
+set -u
+
+HOOK="$(cd "$(dirname "$0")/.." && pwd)/fs-schema-guard.sh"
+[ -x "$HOOK" ] || { echo "FAIL: $HOOK not executable" >&2; exit 1; }
+
+# A scratch account dir with a seeded SCHEMA.md (copied from the shipped template).
+REPO_ROOT="$(cd "$(dirname "$0")/../../../.." && pwd)"
+TEMPLATE="$REPO_ROOT/templates/account-schema/SCHEMA.md"
+[ -f "$TEMPLATE" ] || { echo "FAIL: template missing at $TEMPLATE" >&2; exit 1; }
+ACCT=$(mktemp -d)
+trap 'rm -rf "$ACCT"' EXIT
+cp "$TEMPLATE" "$ACCT/SCHEMA.md"
+mkdir -p "$ACCT/projects/Acme" "$ACCT/documents" "$ACCT/output"
+
+PASS=0; FAIL=0
+# Run one case in the account dir as cwd.
+#   $1 name  $2 stdin  $3 expected_exit  $4 expected_log_re ("" = none)
+run_case() {
+  local name="$1" stdin="$2" exp="$3" re="$4" ef actual
+  ef=$(mktemp)
+  ( cd "$ACCT" && printf '%s' "$stdin" | bash "$HOOK" >/dev/null 2>"$ef" )
+  actual=$?
+  local sc; sc=$(cat "$ef"); rm -f "$ef"
+  local ok=1
+  [ "$actual" -eq "$exp" ] || ok=0
+  if [ -n "$re" ] && ! printf '%s' "$sc" | grep -Eq "$re"; then ok=0; fi
+  if [ $ok -eq 1 ]; then echo "PASS: $name (exit=$actual)"; PASS=$((PASS+1));
+  else echo "FAIL: $name (exit=$actual, want $exp; log want /$re/)" >&2; FAIL=$((FAIL+1)); fi
+}
+
+mkenv() { printf '{"hook_event_name":"PreToolUse","tool_name":"%s","tool_input":{"%s":"%s"}}' "$1" "$2" "$3"; }
+
+run_case "non-write allow"       "$(mkenv Bash command 'ls')"                                  0 ""
+run_case "flat project allow"    "$(mkenv Write file_path 'projects/Acme/a.txt')"              0 ""
+run_case "loose document allow"  "$(mkenv Write file_path 'documents/a.pdf')"                  0 ""
+run_case "tool-owned deep allow" "$(mkenv Write file_path 'output/deep/nested/x.png')"         0 ""
+run_case "over-deep block"       "$(mkenv Write file_path 'projects/Acme/deploy/sources/a.txt')" 2 "fs-guard. blocked path=projects/Acme/deploy/sources/a.txt reason=over-deep"
+run_case "over-deep one block"   "$(mkenv Write file_path 'projects/Acme/deploy/a.txt')"       2 "reason=over-deep"
+run_case "top-level block"       "$(mkenv Write file_path 'whim/x.txt')"                       2 "fs-guard. blocked path=whim/x.txt reason=top-level"
+run_case "outside acct allow"    "$(mkenv Write file_path '/etc/passwd')"                      0 ""
+run_case "notebook over-deep"    "$(mkenv NotebookEdit notebook_path 'projects/Acme/deploy/n.ipynb')" 2 "reason=over-deep"
+run_case "empty stdin block"     ""                                                            2 "no stdin"
+# JSON null file_path must coerce to empty (allow), not the literal string "None".
+run_case "null path allow"       '{"hook_event_name":"PreToolUse","tool_name":"Write","tool_input":{"file_path":null}}' 0 ""
+
+# Allowed-set parse == documented set.
+EXPECT="projects contacts documents url-get output generated extracted uploads agents specialists sites public cache secrets state logs tmp SCHEMA.md account.json AGENTS.md .claude .git"
+GOT=$(awk '/^```allowed-top-level$/{f=1;next} /^```$/{f=0} f' "$ACCT/SCHEMA.md" | tr '\n' ' ' | sed 's/ *$//')
+if [ "$GOT" = "$EXPECT" ]; then echo "PASS: allowed-set parse"; PASS=$((PASS+1));
+else echo "FAIL: allowed-set parse: got [$GOT]" >&2; FAIL=$((FAIL+1)); fi
+
+echo "----- $PASS passed, $FAIL failed -----"
+[ $FAIL -eq 0 ]

package/payload/platform/plugins/admin/hooks/fs-schema-guard.sh

@@ -0,0 +1,108 @@
+#!/usr/bin/env bash
+# fs-schema-guard — PreToolUse Write/Edit/NotebookEdit path guard.
+#
+# Enforces the seeded account-dir file schema (see <accountDir>/SCHEMA.md):
+#   - the target's first path segment must be in the allowed top-level set
+#     (parsed from the fenced ```allowed-top-level block of the account's
+#     SCHEMA.md — our own structured data, not CLI prose);
+#   - a target under an operator-data bucket (projects/ contacts/) may be at
+#     most <bucket>/<entity>/<file> deep; documents/ may be at most
+#     <bucket>/<folder>/<file> deep. Tool-owned dirs pass at any depth.
+#
+# The hook governs the account dir only. A path resolving outside the account
+# dir (cwd) is allowed — platform-source writes are PLATFORM_BOUNDARY's concern.
+#
+# Exit codes: 0 = allow, 2 = block (stderr shown to the agent). Fail closed when
+# the tool call cannot be inspected (tty or empty stdin). Every block logs
+#   [fs-guard] blocked path=<rel> reason=<top-level|over-deep>
+# No task numbers / internal refs in any operator-visible string.
+
+set -uo pipefail
+
+# Fail closed if attached to a terminal (no JSON envelope coming).
+if [ -t 0 ]; then
+  echo "Blocked: fs-schema-guard received no stdin (cannot inspect the write). Failing closed." >&2
+  exit 2
+fi
+INPUT=$(cat)
+if [ -z "$INPUT" ]; then
+  echo "Blocked: fs-schema-guard received no stdin (cannot inspect the write). Failing closed." >&2
+  exit 2
+fi
+
+field() {
+  printf '%s' "$INPUT" | python3 -c "
+import sys, json
+try:
+    d = json.load(sys.stdin)
+    v = (d.get('$1', {}) or {}).get('$2', '') if '$1' else d.get('$2', '')
+    print(v if isinstance(v, str) else '')
+except Exception:
+    print('')
+" 2>/dev/null || echo ""
+}
+
+TOOL_NAME=$(field '' tool_name)
+case "$TOOL_NAME" in
+  Write|Edit) FILE_PATH=$(field tool_input file_path) ;;
+  NotebookEdit) FILE_PATH=$(field tool_input notebook_path) ;;
+  *) exit 0 ;;
+esac
+[ -z "$FILE_PATH" ] && exit 0
+
+ACCOUNT_DIR="$PWD"
+
+# Resolve to an account-relative path; allow anything outside the account dir.
+REL=$(FILE_PATH="$FILE_PATH" ACCOUNT_DIR="$ACCOUNT_DIR" python3 -c '
+import os, sys
+fp = os.environ["FILE_PATH"]; acct = os.environ["ACCOUNT_DIR"]
+ab = fp if os.path.isabs(fp) else os.path.join(acct, fp)
+ab = os.path.normpath(ab); acct = os.path.normpath(acct)
+if ab == acct or not ab.startswith(acct + os.sep):
+    print("")  # outside the account dir (or the dir itself)
+else:
+    print(os.path.relpath(ab, acct))
+' 2>/dev/null || echo "")
+[ -z "$REL" ] && exit 0
+
+# Parse the allowed top-level set from the account's seeded SCHEMA.md.
+ALLOWED=""
+if [ -f "$ACCOUNT_DIR/SCHEMA.md" ]; then
+  ALLOWED=$(awk '/^```allowed-top-level$/{f=1;next} /^```$/{f=0} f' "$ACCOUNT_DIR/SCHEMA.md")
+fi
+# Fail open on a missing/empty schema (an un-seeded legacy account must not have
+# every write blocked). A re-provision seeds SCHEMA.md, after which the guard
+# applies.
+[ -z "$ALLOWED" ] && exit 0
+
+SEG0=${REL%%/*}
+
+# Top-level check.
+if ! printf '%s\n' "$ALLOWED" | grep -qxF "$SEG0"; then
+  echo "[fs-guard] blocked path=$REL reason=top-level" >&2
+  echo "Blocked: '$SEG0' is not an allowed top-level entry in this account's data directory. The layout is fixed by SCHEMA.md — place operator data under projects/, contacts/, or documents/, and route any reorganisation through the data-manager specialist." >&2
+  exit 2
+fi
+
+# Over-deep check for operator-data buckets. Count path segments.
+depth=$(printf '%s' "$REL" | awk -F/ '{print NF}')
+case "$SEG0" in
+  projects|contacts)
+    # Allowed: <bucket>/<entity>/<file> = 3 segments max; <bucket>/<file> = 2 ok.
+    if [ "$depth" -gt 3 ]; then
+      echo "[fs-guard] blocked path=$REL reason=over-deep" >&2
+      echo "Blocked: $SEG0/ is flat — one folder per entity, then files. '$REL' nests a subtree under an entity folder, which has no basis in the graph ontology. Keep files directly under $SEG0/<name>/, or route a reorganisation through the data-manager specialist." >&2
+      exit 2
+    fi
+    ;;
+  documents)
+    # Allowed: documents/<file> = 2, documents/<folder>/<file> = 3 max.
+    if [ "$depth" -gt 3 ]; then
+      echo "[fs-guard] blocked path=$REL reason=over-deep" >&2
+      echo "Blocked: documents/ holds files or one folder deep. '$REL' nests deeper, which has no basis in the graph ontology. Route a reorganisation through the data-manager specialist." >&2
+      exit 2
+    fi
+    ;;
+esac
+
+exit 0

package/payload/platform/plugins/admin/hooks/lib/maxy-mcp-plugins.txt

@@ -5,6 +5,7 @@ contacts
 email
 graph
 graph-viewer
+joblogic
 memory
 outlook
 quickbooks

package/payload/platform/plugins/admin/skills/platform-architecture/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: platform-architecture
 description: Use when grounding any documented-surface claim about what Maxy ships — plugins, skills, specialists, install/deploy flows, internals. This is the install catalogue, not evidence of what is enabled on the current account. For install state on this account, call `capabilities-here`; for documented surface, cite the `Source:` URL inline.
-content-hash: sha256:0d3d43e2f324aa4f5ab8b192aecd67c30a96b4610c7226a18e7bfb515ffd5b88
+content-hash: sha256:33a6a5683cd3a9f34b0fcbd1d108c7fe20aece1d7d64ecc6da321ff0a8742f08
 brand: maxy-code
 product-name: Maxy
 ---
@@ -1556,7 +1556,7 @@ Every node also carries a provenance stamp — which agent wrote it, in which se
 
 ## Vertical schemas
 
-On top of the base graph, each brand boots one optional **vertical** — an extra set of entity types tailored to a trade. The vertical is named by `brand.json#vertical` and defined in a `schema-<name>.md` reference; the memory plugin loads it at startup and validates every write against base + the active vertical. Real Agent boots `schema-estate-agent` (Listing, Property, Viewing, Offer). SiteDesk boots `schema-construction`, which adds the building-contractor entities — `Job`, `LineItem`, `Valuation`, `Milestone`, `QuoteDocument`, `VariationNote`, `InboundInvoice`, `WhatsAppGroup` — grounded in real builder job folders so a job's quote, valuations, variations, and received supplier and subcontractor invoices all hang off one `Job` node. The default Maxy brand boots no vertical (base graph only).
+On top of the base graph, each brand boots one optional **vertical** — an extra set of entity types tailored to a trade. The vertical is named by `brand.json#vertical` and defined in a `schema-<name>.md` reference; the memory plugin loads it at startup and validates every write against base + the active vertical. Real Agent boots `schema-estate-agent` (Listing, Property, Viewing, Offer). SiteDesk boots `schema-construction`, the canonical JobLogic-derived field-service ontology, which adds the service-delivery entities — `Job`, `Customer`, `Site`, `Asset`, `Visit`, `Quote`, `QuoteLine`, `Valuation`, `VariationNote`, `JobCost`, `Part`, `PurchaseOrder`, `Invoice`, `InboundInvoice`, `PpmContract`, `WhatsAppGroup` (with `Engineer` and `Supplier` as additional labels on `Person`/`Organization`) — grounded in real builder job folders so a job's customer, site, quote, valuations, variations, costs, and received supplier invoices all hang off one `Job` node. The default Maxy brand boots no vertical (base graph only).
 
 ## Public-facing summaries for customer-readable subjects
 
@@ -1880,6 +1880,39 @@ A QuickBooks connection goes stale if it sits unused for about 100 days, or if y
 
 Switching your Intuit app from sandbox to production requires passing Intuit's own production security review. That is between you and Intuit; it is not something the agent does for you.
 
+---
+# JobLogic
+Source: https://docs.getmaxy.com/joblogic.md
+
+# JobLogic
+
+Connect JobLogic, the field-service management system, so the agent can read and update your jobs end to end — customers, sites, jobs, engineers, visits, quotes, invoices, assets, and timesheets — over JobLogic's REST API.
+
+This connector is built for one team that already runs JobLogic as its system of record. Your field staff send a voice note or message to Maxy from the field; Maxy works out what they mean and makes the JobLogic update for them. Your staff never touch the JobLogic API themselves, so only Maxy's own connection talks to JobLogic.
+
+## What you do once
+
+**1. Ask JobLogic for API access.** Raise a ticket with JobLogic Support for API credentials. Ask for a test (UAT) account first, then production. They give you a client ID, a client secret, and your company tenant id.
+
+**2. Whitelist your connection.** JobLogic only accepts API calls from network addresses you have registered with them. Maxy makes its calls from the machine it runs on, so that machine's public address is the one to register. If the machine moves between networks its address can change, so either run it from one place with a stable address, send its traffic through a fixed address, or ask JobLogic whether production needs this at all. If the address is not registered, calls are refused and the agent will tell you the connection was blocked.
+
+**3. Hand the keys to the agent.** Tell the agent your client ID, secret, tenant id, and whether they are test or production. The agent stores them on your install only and never repeats them back.
+
+## What the agent does after that
+
+Everything else is automatic. The agent keeps the connection alive on its own, refreshing access behind the scenes, and can:
+
+- **Read** anything — "what jobs are open for this site", "show this engineer's visits this week", "list unpaid invoices".
+- **Write** from a field instruction — create or reschedule a visit, log labour and materials against a job, set a job's status, approve a quote, raise an invoice, add a note or a photo to a job.
+
+Because JobLogic's credential belongs to the company rather than to a person, the agent stamps each update with the engineer who reported it. You give the agent a list that maps each staff member's phone number to their JobLogic engineer record once, and it does the rest.
+
+Each create carries a safety key, so if a message is retried or a reply goes missing the same instruction never creates a duplicate record.
+
+## Testing
+
+Do all your testing against the JobLogic test (UAT) environment first. Switch to production only once the test environment behaves the way you expect and your production keys and whitelisting are in place.
+
 ---
 # Calendar and Booking
 Source: https://docs.getmaxy.com/calendar-booking.md
@@ -1898,7 +1931,7 @@ Open `/calendar` on your Maxy address (the same sign-in as the dashboard). It sh
 
 Use **Today** and the arrows to move around, and the view buttons to switch. The calendar reads everything time-bound in your graph: meetings imported from a calendar export or created by a booking, appointments Maxy schedules for you in chat, and tasks that have a due date (shown on their day).
 
-Click any entry to open its details: the full title, time, location, and who is attending, with each attendee on its own line (name, and email beneath it). For a booked meeting you can also edit its title, time, or location, or delete it, and the grid updates straight away. You can **Download** a booked meeting as a calendar file (`.ics`) to add it to Apple, Google, or Outlook calendars; an **Include attendees** toggle next to the button decides whether the file carries the attendee list (off by default). The private note is never written into the downloaded file, since the file can travel outside your admin. In the edit view you can add an attendee (give a name, an email, or both) and remove one; adding someone who is already a contact reuses that contact rather than making a duplicate, and removing them takes them off the meeting but keeps the contact. The edit view also has a private note for that meeting, a place for your own reminders that only you and your team ever see; it never appears on the public booking page or anywhere outside your admin. Appointments Maxy schedules and due-dated tasks are shown for detail only and are changed where they are created, not here. New meetings are still made by a booking or by asking Maxy in chat, not from the calendar.
+Click any entry to open its details: the full title, time, location, and who is attending, with each attendee on its own line (name, and email beneath it). For a booked meeting you can also edit its title, time, or location, or delete it, and the grid updates straight away. You can **Download** a booked meeting as a calendar file (`.ics`) to add it to Apple, Google, or Outlook calendars; when the meeting has attendees, Download asks whether to include them in the file before it saves, and a meeting with no attendees downloads straight away. The private note is never written into the downloaded file, since the file can travel outside your admin. In the edit view you can add an attendee (give a name, an email, or both) and remove one; adding someone who is already a contact reuses that contact rather than making a duplicate, and removing them takes them off the meeting but keeps the contact. The edit view also has a private note for that meeting, a place for your own reminders that only you and your team ever see; it never appears on the public booking page or anywhere outside your admin. Appointments Maxy schedules and due-dated tasks are shown for detail only and are changed where they are created, not here. New meetings are still made by a booking or by asking Maxy in chat, not from the calendar.
 
 Everything on the calendar comes from records the rest of Maxy already uses, scoped to your account.
 

package/payload/platform/plugins/docs/references/calendar-booking.md

@@ -12,7 +12,7 @@ Open `/calendar` on your Maxy address (the same sign-in as the dashboard). It sh
 
 Use **Today** and the arrows to move around, and the view buttons to switch. The calendar reads everything time-bound in your graph: meetings imported from a calendar export or created by a booking, appointments Maxy schedules for you in chat, and tasks that have a due date (shown on their day).
 
-Click any entry to open its details: the full title, time, location, and who is attending, with each attendee on its own line (name, and email beneath it). For a booked meeting you can also edit its title, time, or location, or delete it, and the grid updates straight away. You can **Download** a booked meeting as a calendar file (`.ics`) to add it to Apple, Google, or Outlook calendars; an **Include attendees** toggle next to the button decides whether the file carries the attendee list (off by default). The private note is never written into the downloaded file, since the file can travel outside your admin. In the edit view you can add an attendee (give a name, an email, or both) and remove one; adding someone who is already a contact reuses that contact rather than making a duplicate, and removing them takes them off the meeting but keeps the contact. The edit view also has a private note for that meeting, a place for your own reminders that only you and your team ever see; it never appears on the public booking page or anywhere outside your admin. Appointments Maxy schedules and due-dated tasks are shown for detail only and are changed where they are created, not here. New meetings are still made by a booking or by asking Maxy in chat, not from the calendar.
+Click any entry to open its details: the full title, time, location, and who is attending, with each attendee on its own line (name, and email beneath it). For a booked meeting you can also edit its title, time, or location, or delete it, and the grid updates straight away. You can **Download** a booked meeting as a calendar file (`.ics`) to add it to Apple, Google, or Outlook calendars; when the meeting has attendees, Download asks whether to include them in the file before it saves, and a meeting with no attendees downloads straight away. The private note is never written into the downloaded file, since the file can travel outside your admin. In the edit view you can add an attendee (give a name, an email, or both) and remove one; adding someone who is already a contact reuses that contact rather than making a duplicate, and removing them takes them off the meeting but keeps the contact. The edit view also has a private note for that meeting, a place for your own reminders that only you and your team ever see; it never appears on the public booking page or anywhere outside your admin. Appointments Maxy schedules and due-dated tasks are shown for detail only and are changed where they are created, not here. New meetings are still made by a booking or by asking Maxy in chat, not from the calendar.
 
 Everything on the calendar comes from records the rest of Maxy already uses, scoped to your account.
 

package/payload/platform/plugins/docs/references/joblogic.md

@@ -0,0 +1,28 @@
+# JobLogic
+
+Connect JobLogic, the field-service management system, so the agent can read and update your jobs end to end — customers, sites, jobs, engineers, visits, quotes, invoices, assets, and timesheets — over JobLogic's REST API.
+
+This connector is built for one team that already runs JobLogic as its system of record. Your field staff send a voice note or message to {{productName}} from the field; {{productName}} works out what they mean and makes the JobLogic update for them. Your staff never touch the JobLogic API themselves, so only {{productName}}'s own connection talks to JobLogic.
+
+## What you do once
+
+**1. Ask JobLogic for API access.** Raise a ticket with JobLogic Support for API credentials. Ask for a test (UAT) account first, then production. They give you a client ID, a client secret, and your company tenant id.
+
+**2. Whitelist your connection.** JobLogic only accepts API calls from network addresses you have registered with them. {{productName}} makes its calls from the machine it runs on, so that machine's public address is the one to register. If the machine moves between networks its address can change, so either run it from one place with a stable address, send its traffic through a fixed address, or ask JobLogic whether production needs this at all. If the address is not registered, calls are refused and the agent will tell you the connection was blocked.
+
+**3. Hand the keys to the agent.** Tell the agent your client ID, secret, tenant id, and whether they are test or production. The agent stores them on your install only and never repeats them back.
+
+## What the agent does after that
+
+Everything else is automatic. The agent keeps the connection alive on its own, refreshing access behind the scenes, and can:
+
+- **Read** anything — "what jobs are open for this site", "show this engineer's visits this week", "list unpaid invoices".
+- **Write** from a field instruction — create or reschedule a visit, log labour and materials against a job, set a job's status, approve a quote, raise an invoice, add a note or a photo to a job.
+
+Because JobLogic's credential belongs to the company rather than to a person, the agent stamps each update with the engineer who reported it. You give the agent a list that maps each staff member's phone number to their JobLogic engineer record once, and it does the rest.
+
+Each create carries a safety key, so if a message is retried or a reply goes missing the same instruction never creates a duplicate record.
+
+## Testing
+
+Do all your testing against the JobLogic test (UAT) environment first. Switch to production only once the test environment behaves the way you expect and your production keys and whitelisting are in place.

package/payload/platform/plugins/docs/references/memory-guide.md

@@ -144,7 +144,7 @@ Every node also carries a provenance stamp — which agent wrote it, in which se
 
 ## Vertical schemas
 
-On top of the base graph, each brand boots one optional **vertical** — an extra set of entity types tailored to a trade. The vertical is named by `brand.json#vertical` and defined in a `schema-<name>.md` reference; the memory plugin loads it at startup and validates every write against base + the active vertical. Real Agent boots `schema-estate-agent` (Listing, Property, Viewing, Offer). SiteDesk boots `schema-construction`, which adds the building-contractor entities — `Job`, `LineItem`, `Valuation`, `Milestone`, `QuoteDocument`, `VariationNote`, `InboundInvoice`, `WhatsAppGroup` — grounded in real builder job folders so a job's quote, valuations, variations, and received supplier and subcontractor invoices all hang off one `Job` node. The default Maxy brand boots no vertical (base graph only).
+On top of the base graph, each brand boots one optional **vertical** — an extra set of entity types tailored to a trade. The vertical is named by `brand.json#vertical` and defined in a `schema-<name>.md` reference; the memory plugin loads it at startup and validates every write against base + the active vertical. Real Agent boots `schema-estate-agent` (Listing, Property, Viewing, Offer). SiteDesk boots `schema-construction`, the canonical JobLogic-derived field-service ontology, which adds the service-delivery entities — `Job`, `Customer`, `Site`, `Asset`, `Visit`, `Quote`, `QuoteLine`, `Valuation`, `VariationNote`, `JobCost`, `Part`, `PurchaseOrder`, `Invoice`, `InboundInvoice`, `PpmContract`, `WhatsAppGroup` (with `Engineer` and `Supplier` as additional labels on `Person`/`Organization`) — grounded in real builder job folders so a job's customer, site, quote, valuations, variations, costs, and received supplier invoices all hang off one `Job` node. The default Maxy brand boots no vertical (base graph only).
 
 ## Public-facing summaries for customer-readable subjects
 

package/payload/platform/plugins/joblogic/.claude-plugin/plugin.json

@@ -0,0 +1,21 @@
+{
+  "name": "joblogic",
+  "description": "JobLogic field-service connector (bespoke, one account) — OAuth client_credentials, tenant-scoped read/write across the job lifecycle.",
+  "version": "0.1.0",
+  "author": {
+    "name": "Rubytech LLC"
+  },
+  "mcpServers": {
+    "joblogic": {
+      "type": "stdio",
+      "command": "node",
+      "args": [
+        "${CLAUDE_PLUGIN_ROOT}/lib/mcp-spawn-tee/index.js",
+        "${CLAUDE_PLUGIN_ROOT}/mcp/dist/index.js"
+      ],
+      "env": {
+        "MCP_SPAWN_TEE_NAME": "joblogic"
+      }
+    }
+  }
+}