Architecture

The project has two applications: the public Orders configurator and the manufacturer workspace. Orders owns submitted requests and catalogue-backed quoting. The workspace reads those requests, manages versioned configuration and supports the team’s review/conversation workflow.

Request flow

flowchart LR
  Widget["Public widget"] --> Orders["Orders service · CompanyStore"]
  Staff["Native staff form"] --> Bridge["Company-bound source bridge"]
  Bridge --> Orders
  Orders --> Bridge
  Bridge --> Workspace["Orders · Customers · Products · Configurator"]

The HTTP source binding names one workspace company and one Orders slug. Requests carry the recipient’s bridge credential and exact company header; redirects are rejected. RemoteCompanySource reads explicit resources through platform-state and sends staff commands through platform-orders. The workspace therefore reaches the owning order service through its admitted interface rather than sharing its database file.

platform_source.py and manufacturer_order.py retain corresponding read projections. Stable display numbers derive from the first estimate event where available; the legacy fallback has its own reference namespace. Presentation keeps original order IDs and source references intact.

State ownership

ManufacturerFulfillment explicitly models human-reported progress independently of the source’s reservations. A team status change is therefore not evidence that a warehouse integration reserved or dispatched stock.

Full snapshots and publication

flowchart LR
  Draft["Edited full document"] --> Version["Immutable version + SHA256"]
  Version --> Preview["Snapshot-pinned renderer"]
  Version --> Receiver["Orders configurator receiver"]
  Receiver --> Receipt["Matching ID · revision · SHA256"]

ManufacturerStore.save_document checks the expected revision and current membership inside a SQLite write transaction. It stores the canonical full document, content hash, author and summary, then advances the company’s current pointer. Conflicting edits return a conflict for review.

ManufacturerStore.restore reads the selected version’s exact stored canonical content and saves it as a new revision. Catalogue and configuration travel together. Restore therefore includes the old questions, product definitions and commercial values rather than reconstructing them from current defaults.

manufacturer_preview.renderer and html verify renderer bytes by SHA256, require the complete public picker bundle and pin its renderer manifest to the full snapshot hash. The preview injects the saved document into that renderer. Source checks and membership checks remain part of serving a saved preview.

Publisher.publish serializes publication and sends the saved version to the commissioned receiver. It accepts publication only when the receipt confirms ok, published, version ID, revision and content hash. A saved version remains pending when that matching receipt is unavailable. The Orders-side configurator_versions.Bridge validates the incoming document and records its applied version.

Staff command and attachment flow

manufacturer-new-order.js freezes the pending customer/items/file command with an idempotency key and saves it in IndexedDB. manufacturer_manual_orders.create derives attribution from the authenticated member; the browser supplies the order fields, while the server supplies the actor.

The Orders receiver checks CompanyStore.replay before current catalogue checks and file staging. CompanyStore._write binds the command digest to its key in the same transaction as the resulting order/audit records. An unchanged retry returns the committed result; changed input with the same key is rejected.

The staff path accepts 1–100 distinct catalogue items, integer quantities of 1–9999 and an optional original document up to 4 MB. order_files.stage validates file bytes before an order claims the file. Workspace file access rechecks exact company/order/file ownership; PDF page rendering is a separate bounded operation.

Specification parsing preserves the source file and cell references. spec_workbook.parse records receiving destinations and per-line allocations, including a confirmation requirement. spec_receipts.py retains the extraction receipt. Customer receiving allocations and the supplier’s selected dispatch warehouse remain separate fields throughout presentation.

Access and capabilities

Membership gates belong to ManufacturerWorkspace.member and the host middleware. Company reads, operator writes and owner settings/team actions have distinct checks. Public customer links use CustomerPortal, with their own scope and lifecycle.

The agent_editing and customer_research flags are company capabilities. The source release can run the manual workflow with both disabled. The shared UI’s canLoadAgentResources reads authoritative company capability metadata and skips hidden agent chats, agents and connection loaders for manual manufacturer sessions. The server keeps its existing admission gate; the UI gate avoids unnecessary denied requests. Other installed SDK verticals retain their original resource-loading behaviour.

English display prefers en and falls back to bg. English questionnaire writes merge the localized field, preserving its other language. Technical field names, status values and API IDs stay stable across that presentation change.

Optional services

The native first result exercises the recipient-owned public widget, Orders authority, bridge and workspace using authored sample data. It establishes that local workflow; paid model execution, outbound mail and external helpdesk delivery need their own commissioning and verification. The README owns startup and credentials; product decisions explains the interface.

made by atelier neyra

Source document ↗