@arcforgelabs/flow 2026.10.24 → 2026.10.25

package/README.md

@@ -1,6 +1,6 @@
 # Flow
 
-Flow is invoicing, bill approval and a financial dashboard for labs that make
+Flow is job management, invoicing, bill approval and a financial dashboard for labs that make
 work to order, first for dental labs. Seazona (the lab's case system) is a
 bundled integration, and Xero is an optional one. See `VISION.md`.
 

package/VISION.md

@@ -1,21 +1,24 @@
 # Flow — Vision
 
-Flow is invoicing, bill approval and a financial dashboard for a lab that
-makes work to order, first for dental labs. It is a complete application with
-its own database. It is not a sync engine between other products.
-
-It is for the person who bills the work and pays the suppliers. Finished feels
-like this: completed cases become invoices they check and send, supplier bills
-are reviewed and approved, and one dashboard shows cash, what is owed to the
-lab, what the lab owes, and the GST for the BAS period. Every invoice a
-customer was sent can be found again, exactly as it was sent.
+Flow is job management, invoicing, bill approval and a financial dashboard
+for a lab that makes work to order, first for dental labs. It is a complete
+application with its own database. It is not a sync engine between other
+products.
+
+It is for the lab manager, the staff who move the work, and the person who
+bills it and pays the suppliers. Finished feels like this: Flow opens on a
+job board that shows every job by stage, with due dates and late jobs marked;
+completed jobs become invoices they check and send; supplier bills are
+reviewed and approved; and one dashboard shows cash, what is owed to the lab,
+what the lab owes, and the GST for the BAS period. Every invoice a customer
+was sent can be found again, exactly as it was sent.
 
 Flow is open source so any lab can run its own installation.
 
 ## The core and its integrations
 
-The core is invoices, bills, payments, credit notes, contacts, the price list,
-the jobs it bills, approvals and the dashboard. The core holds its own copy of
+The core is jobs and the job board, invoices, bills, payments, credit notes,
+contacts, the price list, approvals and the dashboard. The core holds its own copy of
 every record it shows, so it works with no integration connected and an owner
 can build reports and features on its data.
 
@@ -33,6 +36,39 @@ data spine (`docs/DATA_SPINE.md`): its records come into a mirror, get a Flow
 identity, and become core records; Flow's writes leave through an outbox; a
 conflict goes to one review queue; one job queue runs the work.
 
+## Job management
+
+Flow links each job to its client and its invoice. That link is the heart
+of the product: a job card shows what was ordered, who it is for, and how it
+was billed and paid.
+
+Flow does a few parts of job management well now, and more later. It does
+not try to replace the lab's case system.
+
+- **Now:** update job cards and process a job's information for invoicing,
+  and update jobs from paper forms.
+- **Later:** full job management.
+
+The job board is Flow's main view: a standard board of jobs by stage (a
+column per stage, a card per job), with a list view of the same jobs. It
+shows every job from the case system and from Flow, with its practice, due
+date and department. Lab staff and the manager work from it.
+
+Two parts follow the board (#48):
+
+- **An intake reader.** A photo, a form or a note becomes a proposed job
+  action: update a job, create one, or add a note. A handwriting reader and a
+  low-cost decision model propose it; a person confirms it. Nothing changes
+  until a person accepts. The model steps are optional and cost money per
+  page, so the manager sees the month's cost.
+- **A practice portal.** Practice staff sign in to follow their own jobs,
+  on desktop first, with a simpler view on phones. The server limits each
+  person to their practice.
+
+Job management is a bundled module, built the same way as the integrations,
+and a lab can remove it. Where the case system cannot take a change through
+its API, the change becomes a short checklist for a person (#49).
+
 ## Standing decisions
 
 ### Why does Flow keep its own records?
@@ -58,7 +94,10 @@ not the product.
 The case system, Flow and the accounting system each own their own records,
 and the data moves both ways. Flow records which system each change came
 from. When two systems disagree, Flow never overwrites one silently: it opens
-an item in the review queue for a person.
+an alert in the review queue. The alert shows each system's value and writes
+nothing. A person fixes the record where they choose, then presses
+**Resolved, re-check**: Flow checks that one difference again, and the alert
+closes only when the systems agree.
 
 ### Why are approvals in Flow?
 
@@ -76,7 +115,8 @@ version; the sent one stays as it was, attributed to whoever sent it.
 Dental cases carry health information, which Australian privacy law treats as
 sensitive. Flow keeps the case number and the practice. It keeps a patient
 reference only when a practice needs one printed on its invoice, and it keeps
-no clinical notes or images.
+no clinical notes or images. A form photo the intake reader reads is not kept
+after its job is updated.
 
 ### Why does Flow keep its records in PostgreSQL only?
 
@@ -94,8 +134,9 @@ its own data, configuration and secrets.
 
 ## Out of scope
 
-- Case management, production tracking and scheduling. The case system owns
-  the case.
+- Replacing the case system, for now. The case system owns the case record.
+  Flow's job board shows and updates the work, and does not do clinical
+  case management or production scheduling.
 - Patient records, clinical notes, scans and images.
 - Acting as the general ledger. Accounting software owns the ledger and the
   bank feed.

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "@arcforgelabs/flow",
-  "version": "2026.10.24",
+  "version": "2026.10.25",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@arcforgelabs/flow",
-      "version": "2026.10.24",
+      "version": "2026.10.25",
       "license": "MIT",
       "dependencies": {
         "@clerk/backend": "3.23.2",
@@ -19,6 +19,7 @@
         "@fontsource-variable/lora": "5.3.0",
         "@fontsource-variable/nunito-sans": "5.3.0",
         "@fontsource-variable/playfair-display": "5.3.0",
+        "@fontsource-variable/plus-jakarta-sans": "5.3.0",
         "@fontsource-variable/space-grotesk": "5.3.0",
         "drizzle-orm": "0.45.3",
         "express": "5.3.0",
@@ -630,6 +631,15 @@
         "url": "https://github.com/sponsors/ayuhito"
       }
     },
+    "node_modules/@fontsource-variable/plus-jakarta-sans": {
+      "version": "5.3.0",
+      "resolved": "https://registry.npmjs.org/@fontsource-variable/plus-jakarta-sans/-/plus-jakarta-sans-5.3.0.tgz",
+      "integrity": "sha512-/l/4r0yyWK9JzAlmA0LiYgGgmJe/Gswt4jTJEzr5QhJfwMbvJZDmYWyW0M4X7yCK69BajMVlV/Lx8g7WDc1+sw==",
+      "license": "OFL-1.1",
+      "funding": {
+        "url": "https://github.com/sponsors/ayuhito"
+      }
+    },
     "node_modules/@fontsource-variable/space-grotesk": {
       "version": "5.3.0",
       "resolved": "https://registry.npmjs.org/@fontsource-variable/space-grotesk/-/space-grotesk-5.3.0.tgz",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arcforgelabs/flow",
-  "version": "2026.10.24",
+  "version": "2026.10.25",
   "description": "Invoicing, bill entry and a financial dashboard for labs, with Seazona and Xero integrations.",
   "license": "MIT",
   "repository": {
@@ -44,6 +44,7 @@
     "@fontsource-variable/lora": "5.3.0",
     "@fontsource-variable/nunito-sans": "5.3.0",
     "@fontsource-variable/playfair-display": "5.3.0",
+    "@fontsource-variable/plus-jakarta-sans": "5.3.0",
     "@fontsource-variable/space-grotesk": "5.3.0",
     "drizzle-orm": "0.45.3",
     "express": "5.3.0",

package/server/theme/font-families.js

@@ -6,6 +6,7 @@ export const MONO_FONT = 'jetbrains-mono';
 
 export const FAMILY_FONTS = {
   harbour: ['nunito-sans', 'playfair-display'],
+  meridian: ['plus-jakarta-sans', 'playfair-display'],
   beacon: ['atkinson-hyperlegible-next'],
   tide: ['ibm-plex-sans'],
   claw: ['instrument-sans'],

package/server/theme/themes.js

@@ -66,10 +66,64 @@ const HARBOUR = {
   },
 };
 
-// Picker order: Harbour (Flow's own), then the design directions Field leads
-// with (Beacon, Tide, Claw, Knot, Dash), then the other OpenClaw families.
+// Meridian: a dental laboratory's own look. Deep navy ink and filled buttons,
+// a champagne highlight, warm stone pages and white cards. Plus Jakarta Sans
+// for reading, Playfair Display at regular weight for page titles, square
+// corners and widely tracked uppercase labels. Dark mode turns the navy into
+// the page and the champagne into the accent.
+const MERIDIAN_SHAPE = {
+  '--t-body': "'Plus Jakarta Sans Variable', 'Plus Jakarta Sans', system-ui, -apple-system, 'Segoe UI', sans-serif",
+  '--t-display': "'Playfair Display Variable', 'Playfair Display', Georgia, 'Times New Roman', serif",
+  '--t-data': "'JetBrains Mono Variable', 'JetBrains Mono', ui-monospace, SFMono-Regular, Menlo, monospace",
+  '--t-radius': '0px',
+  '--t-radius-lg': '2px',
+  '--t-stroke': '1px',
+  '--t-label-size': '12px',
+  '--t-label-weight': '600',
+  '--t-label-spacing': '.16em',
+  '--t-label-case': 'uppercase',
+  '--t-display-weight': '400',
+};
+
+const MERIDIAN = {
+  label: 'Meridian',
+  description: 'Navy, champagne & stone',
+  source: 'flow',
+  light: {
+    '--t-bg': '#f6f3ef', '--t-s1': '#efe9e0', '--t-s2': '#e6ded1', '--t-paper': '#ffffff',
+    '--t-brd': '#e0dbd1', '--t-brd-hi': '#b8a685', '--t-stroke-color': '#d5cec2',
+    '--t-text': '#1d3444', '--t-strong': '#13242f', '--t-dim': '#4d6575', '--t-mute': '#526a7a',
+    '--t-accent': '#1d3444', '--t-accent-bg': '#faefdd', '--t-accent-brd': '#d4b07a',
+    '--t-brand': '#1d3444', '--t-brand-ink': '#f8dfb9',
+    '--t-primary': '#1d3444', '--t-on-primary': '#f8dfb9', '--t-ring': '#b08850',
+    '--t-warn': '#8a5a00', '--t-warn-bg': 'rgba(138, 90, 0, 0.08)', '--t-warn-brd': 'rgba(138, 90, 0, 0.32)',
+    '--t-danger': '#b42318', '--t-danger-bg': 'rgba(180, 35, 24, 0.07)', '--t-danger-brd': 'rgba(180, 35, 24, 0.40)',
+    '--t-success': '#22663f', '--t-success-bg': 'rgba(34, 102, 63, 0.08)',
+    ...MERIDIAN_SHAPE,
+    '--t-shadow': '0 1px 2px rgba(29, 52, 68, 0.06)',
+    'color-scheme': 'light',
+  },
+  dark: {
+    '--t-bg': '#14252f', '--t-s1': '#1d3444', '--t-s2': '#26404f', '--t-paper': '#192d3a',
+    '--t-brd': '#2c4555', '--t-brd-hi': '#56707f', '--t-stroke-color': '#334d5e',
+    '--t-text': '#ece5d8', '--t-strong': '#fbf4e8', '--t-dim': '#b9c3c9', '--t-mute': '#a3b2bb',
+    '--t-accent': '#f8dfb9', '--t-accent-bg': 'rgba(248, 223, 185, 0.12)', '--t-accent-brd': 'rgba(248, 223, 185, 0.45)',
+    '--t-brand': '#f8dfb9', '--t-brand-ink': '#1d3444',
+    '--t-primary': '#f8dfb9', '--t-on-primary': '#1d3444', '--t-ring': '#f8dfb9',
+    '--t-warn': '#e7b75c', '--t-warn-bg': 'rgba(231, 183, 92, 0.12)', '--t-warn-brd': 'rgba(231, 183, 92, 0.32)',
+    '--t-danger': '#f2877b', '--t-danger-bg': 'rgba(242, 135, 123, 0.12)', '--t-danger-brd': 'rgba(242, 135, 123, 0.45)',
+    '--t-success': '#86d3a1', '--t-success-bg': 'rgba(134, 211, 161, 0.12)',
+    ...MERIDIAN_SHAPE,
+    '--t-shadow': '0 1px 2px rgba(0, 0, 0, 0.30)',
+    'color-scheme': 'dark',
+  },
+};
+
+// Picker order: Flow's own (Harbour, Meridian), then the design directions
+// Field leads with (Beacon, Tide, Claw, Knot, Dash), then the other OpenClaw
+// families.
 const { beacon, tide, claw, knot, dash, ...otherOpenclaw } = OPENCLAW_FAMILIES;
-const FAMILIES = { harbour: HARBOUR, beacon, tide, claw, knot, dash, ...otherOpenclaw };
+const FAMILIES = { harbour: HARBOUR, meridian: MERIDIAN, beacon, tide, claw, knot, dash, ...otherOpenclaw };
 
 // --t-control: the edge of an input or an outlined button on --t-paper, the
 // text colour faded toward the paper only as far as it still reads at 3:1.