Modules have boundaries.
Sales, jobs, stock, procurement, QA, accounting and customer interfaces may share identifiers without sharing unrestricted authority to edit each other's records.
SYSTEM ONLINE // PUBLIC ENGINEERING ARCHIVE
Eleven independent technical dossiers. The code is the map. Touch an illuminated sequence to open what sits behind the software.
01 / SYSTEM DESIGN
The purpose is not to put everything on one screen. It's to keep people, products, financial events, physical movements and decisions connected without making them all the same record. Select a node to inspect the responsibilities.
Quotes, jobs and invoices can reference the same customer identity without storing competing customer records.
Sales, jobs, stock, procurement, QA, accounting and customer interfaces may share identifiers without sharing unrestricted authority to edit each other's records.
A brand describes a customer-facing identity, a location describes operational geography, and a separate legal entity may need separate accounting, access and contractual boundaries.
A desktop or Companion interface can initiate a change; the authoritative connected service decides what is permitted and which durable record is written.
This map explains architectural intent and record relationships. It is not a live production database topology or a promise that all module interactions are released.
02 / RECORD OWNERSHIP
The hard part of interconnected software isn't drawing an arrow between two windows. It is resolving identity, data ownership, legal scope and historical versions correctly.
C-104Q-208J-321I-410Example identifiers above are fictional and illustrate relationships, not a record from a real DD installation.
Every relationship should point to the authoritative source record. Source links are explicit so a job, invoice or stock movement can be traced back to its origin.
An accepted quote or invoice must preserve its original commercial figures; changing today's price catalogue must not rewrite yesterday's sale.
Showing a record in another module does not grant that module permission to edit it. Data ownership and read permissions must be separately specified.
type SourceRef = {
recordType: 'quote' | 'job' | 'invoice';
recordId: string;
version?: string;
};
type JournalEntry = {
source: SourceRef;
actorId: string;
committedAt: string;
};03 / EVENT PROCESSING
A website order, desktop command or Companion submission can begin a chain of authorised changes. An event contract needs ownership, validation, idempotency, retry handling and a path back to the source.
Resolve the initiating actor and source, apply record scope, verify transitions, and reject unauthorised or contradictory requests.
Receipts, reversals and financial effects need boundaries that prevent partially written history when an operation fails.
Repeated webhook deliveries or recovered payment attempts should not blindly duplicate stock changes, invoices or charges. Idempotency keys and recovery references matter.
04 / COMMERCIAL ARCHITECTURE
The commercial model under development connects offers, accepted terms and reusable policies. Negotiated exceptions should remain attached to the customer and effective agreement—not mysteriously alter the product catalogue for everybody.
Scope, quantities, prices, proposed conditions and the specific version sent for acceptance.
Accepted parties, dates, exceptions, source clauses, applicability and effective versions.
Reusable rules and eligibility boundaries controlling how accepted terms apply to work.
Retain catalogue and accepted prices, quantities, applicable tax treatment and source terms as historical facts.
A customer-specific rate could apply only to certain items, quantities or effective dates. The applicable agreement clause should explain the difference.
Conflicting terms, version changes and manual exceptions need an auditable decision and a clear review path.
Status: This is the documented commercial architecture being built toward. It is not a claim that all agreement automation, clause resolution or policy rules are currently production-complete.
05 / IMMUTABLE HISTORY
A balance is the result of confirmed events, not a lonely number. Posted financial and physical movement history should retain its original source, with linked corrections rather than invisible rewrites.
Receipts, transfers, picks, production consumption and adjustments retain item, quantity, units, source, destination and triggering job or order as appropriate.
Invoice, GST, payment and accounting postings should reconcile to their original transactions. Reversals and corrections remain separately traceable.
Draft or unconfirmed operations can have different amendment rules. A proposed movement or stock reservation is not the same as physical stock movement.
This illustrates ledger integrity design, not a guarantee that every ledger, reversal workflow or permission gate is complete in every configuration.
06 / CONNECTED SYSTEMS
A connected website and operational backend are only useful if they agree about the source record, accepted transaction and failure state. Real integrations need explicit contracts rather than decorative arrows.
Provider events require authenticated origin checks, schema validation, a durable idempotency strategy and handling for out-of-order or repeated callbacks.
Payment recovery needs durable references and safe reconciliation. A recovered client must not create a second capture because a screen closed unexpectedly.
Carrier, dispatch, and freight integrations require account-specific credentials, valid product and shipment data, and clear handling when external services fail.
Stripe-powered payments and configured GoSweetSpot freight are examples mentioned in the existing technical guide. Integrations vary by deployment, permission and implementation status; this is not a live connection diagram.
07 / ACCESS BOUNDARIES
Identity, business scope, record scope and permitted action are different checks. A request may have a valid login but still be unauthorised to change another location's stock or another company's agreement.
Never represent a browser-only check as secure authority. APIs and providers need proper credential storage, limited scopes and server-side validation.
Separate brand, location and legal-entity context, and preserve actor identity and provenance when an authorised workflow updates data.
Backup, restoration, device loss and error recovery have to be accounted for in deployment and support. This exhibit never exposes real credentials or customer records.
08 / CUSTOMER APPLICATIONS
The documented delivery architecture is designed around individually identified customer applications. A shared engineering foundation can produce different module combinations and integration scopes without making all customers update together.
Common modules and components can evolve while individual customers receive only reviewed combinations and integrations that suit their operations.
Customer/build identity, release notes, package metadata, checksums and approvals provide a foundation for traceable updates.
A future distribution pipeline may use assigned domain paths and storage buckets, not one public installer with uncontrolled access.
Status: This is a design specification. Automated per-customer builds, buckets, manifests and approval gates are not all demonstrated production capabilities today.
09 / MOVING SYSTEMS
A safe import has to preserve what records mean, not just what their columns are called. A customer, product, tax transaction and inventory movement each have historical context that cannot be guessed from a CSV header.
A financial import that balances numerically but loses the original invoices or accepted terms is not a faithful migration.
Missing foreign keys, ambiguous customers and invalid quantities belong in a review queue, not silently assigned invented values.
Validation, backup, customer approval and a tested recovery path are part of the engagement rather than invisible implementation chores.
10 / SPECIALIST BUILDS
Denver's Desk is a substantial operational ERP. The team's websites, integrations and specialist applications are different services and products—not extra screens in a single web portal or mandatory add-ons to the ERP.
Product maturity, deployment and availability differ. Concept exhibits are not claims that every tool is generally available or connected to the ERP.
11 / THE SOURCE LAB
The moving code and binary field on this screen is animated with Canvas 2D. Our separate 3D Reactor exhibit uses genuine WebGL2 and GLSL fragment shaders. These snippets are educational specimens, not copied proprietary application source. Switch languages, inspect and copy.
// Event processing specimen — illustrative, not live DD source.
async function process(command: Command) {
const actor = await authorise(command);
return database.transaction(async tx => {
const prior = await tx.findByKey(command.idempotencyKey);
if (prior) return prior.result;
const change = await tx.apply(command, actor);
await tx.appendAudit(change);
return change;
});
}Idempotent commands and linked audit history help prevent duplicated operations after retries.
The separate 3D Reactor exhibit compiles real GLSL shader source in the browser. This code-matrix page uses Canvas 2D for its moving binary streams; both experiences can pause animation.
Tabs, search, explanations, diagrams and controls remain selectable, keyboard-operable HTML. The shader is decorative and never required to read the page.
Real feature status belongs in the Feature Atlas; implementation details and deployable code belong in the project repositories. This exhibit helps visitors understand the principles.
The original reference retains the full technical explanations, and the Feature Atlas provides individual feature details. This exhibit is a faster way into the material, not a replacement for careful verification.