Skip to technical topics
DENVER'S DESK THE ENGINEERING ROOM
DENVER'S DESK / ENGINEERING EXPERIMENT 001 PROCEDURAL GEOMETRY, NOT A VIDEO INITIALISING VISUAL ENGINE

THE SOFTWARE UNDER THE SOFTWARE / AN INTERACTIVE SPECIMEN

PULL THE
SYSTEM
APART.

A business system isn't a dashboard. It's the invisible machinery connecting decisions, events, money, materials and history.

So we built a ridiculous little GPU-powered machine to explain it. Turn it, separate its layers, interrupt its flow, then watch the model recover. The object is a metaphor—not live customer data or a map of DD's production infrastructure.

ENGINEERING STATE01 / INTEGRITY

Everything has an owner.

A reliable application keeps one authoritative identity for each record, even when several modules need to see it.

INVARIANT / SOURCE RECORDS STAY CANONICAL
300,000+Lines of Denver's Desk code reported roughly three months earlier — historical team estimate, not a current audited total.
DD // IMPOSSIBLE MACHINEFIG. 01 / ARCHITECTURE AS MATTER
DRAG TO ORBIT / ARROW KEYS TO ROTATEX +000° / Y +000°
THE WORKBENCHDo something to the system.SIMULATED BEHAVIOUR / REAL SHADER
COMPRESSEDEXPLODED
OPEN TECHNICAL ATLAS ↓

THE ATLAS / FIND WHAT MATTERS

Information at the speed
of curiosity.

Pick a lens. Search for a particular engineering concept. Inspect the diagrams, code specimens and operational relationships directly.

Evidence labels matter: design intent, illustrative examples and verified released features are not interchangeable.

01 / SYSTEM DESIGN

One operational platform.
Several different responsibilities.

DESIGN PRINCIPLES

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.

INSPECTOR / CUSTOMER

Customer identity is a source, not a copy.

Quotes, jobs and invoices can reference the same customer identity without storing competing customer records.

INVARIANTStable identifiers and explicit ownership.
01 / MODULARITY

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.

02 / CONTEXT

Business ≠ brand ≠ location.

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.

03 / AUTHORITY

Local and server states differ.

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

Never duplicate
the source of truth.

TECHNICAL FOUNDATION

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.

PARTYCustomerC-104
→
PROPOSALQuoteQ-208
→
DELIVERYJobJ-321
→
FINANCEInvoiceI-410

Example identifiers above are fictional and illustrate relationships, not a record from a real DD installation.

CANONICAL IDs

One identity. Several references.

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.

VERSIONING

Past agreements stay past agreements.

An accepted quote or invoice must preserve its original commercial figures; changing today's price catalogue must not rewrite yesterday's sale.

SEPARATION

A field is not an authority.

Showing a record in another module does not grant that module permission to edit it. Data ownership and read permissions must be separately specified.

ILLUSTRATIVE / TYPE RELATIONSHIPS
type SourceRef = {
  recordType: 'quote' | 'job' | 'invoice';
  recordId: string;
  version?: string;
};
type JournalEntry = {
  source: SourceRef;
  actorId: string;
  committedAt: string;
};

03 / EVENT PROCESSING

One action.
Many consequences.

MODEL / RECOVERY PRINCIPLES

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.

EVENT SPECIMEN / SELECT A CASE
  1. Receive request with source ID
  2. Validate identity, rules and scope
  3. Persist authorised changes together
  4. Record the outcome and audit source
01 / VALIDATE

Verify before changing.

Resolve the initiating actor and source, apply record scope, verify transitions, and reject unauthorised or contradictory requests.

02 / COMMIT

Atomic where required.

Receipts, reversals and financial effects need boundaries that prevent partially written history when an operation fails.

03 / RECOVER

Retry ≠ repeat.

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

A price tells you what.
An agreement tells you why.

ARCHITECTURE IN DEVELOPMENT

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.

01 / PROPOSE

Commercial Offer

Scope, quantities, prices, proposed conditions and the specific version sent for acceptance.

02 / ACCEPT

Commercial Agreement

Accepted parties, dates, exceptions, source clauses, applicability and effective versions.

03 / GOVERN

Operational Policies

Reusable rules and eligibility boundaries controlling how accepted terms apply to work.

ORIGINAL FIGURES

Capture commercial snapshots.

Retain catalogue and accepted prices, quantities, applicable tax treatment and source terms as historical facts.

EXCEPTIONS

Resolve scope explicitly.

A customer-specific rate could apply only to certain items, quantities or effective dates. The applicable agreement clause should explain the difference.

GOVERNANCE

Don't hide policy conflict.

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

History that
stays history.

INTEGRITY PRINCIPLE

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.

ILLUSTRATIVE MOVEMENT JOURNALNO LIVE DATA
R-108Goods receivedOriginal receipt · 24 units+24
C-109Linked correctionQuantity corrected by 2 units−2
CONFIRMED BALANCE22 UNITS
STOCK JOURNAL

Physical movement is explicit.

Receipts, transfers, picks, production consumption and adjustments retain item, quantity, units, source, destination and triggering job or order as appropriate.

FINANCIAL JOURNAL

Posted numbers are explained.

Invoice, GST, payment and accounting postings should reconcile to their original transactions. Reversals and corrections remain separately traceable.

DRAFT ≠ POSTED

Different states, different rules.

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

Integrations shouldn't
invent another truth.

CONTRACT-BASED INTEGRATION

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.

PUBLIC FRONT ENDWebsite / storeOrder event
→
AUTHORITATIVE APIValidate & mapIdentity / schema
→
OPERATIONSOrder / job / stockState transition
→
PROVIDERPayment / freightCallback / webhook
WEBHOOKS

Validate, deduplicate, recover.

Provider events require authenticated origin checks, schema validation, a durable idempotency strategy and handling for out-of-order or repeated callbacks.

PAYMENTS

Restart should not mean repay.

Payment recovery needs durable references and safe reconciliation. A recovered client must not create a second capture because a screen closed unexpectedly.

FREIGHT & SERVICES

Configuration matters.

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

Being logged in isn't
permission to do everything.

SECURITY DESIGN

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.

CHECKQUESTIONFAIL CLOSED WHEN…
AuthenticationWho sent this?Identity cannot be verified
Business scopeWhich legal operation?Business context is unavailable
Role & actionWhat may they change?Permission is not granted
Record ownershipWhose data is this?Target is outside authorised scope
Audit & recoveryWhat actually happened?No traceable outcome is available
CREDENTIALS

Keep secrets outside UI.

Never represent a browser-only check as secure authority. APIs and providers need proper credential storage, limited scopes and server-side validation.

DATA BOUNDARIES

Scope must travel with requests.

Separate brand, location and legal-entity context, and preserve actor identity and provenance when an authorised workflow updates data.

OPERATIONS

Backups are a responsibility.

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

Not one binary.
Not one customer.

PLANNED DISTRIBUTION MODEL

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.

01ASSEMBLECommon code foundation + approved configuration
02ASSIGNCustomer/build ID, release identity and notes
03VERIFYTests, checksums, approved artifacts
04DISTRIBUTEAuthorised path and storage boundary
05UPDATESelective release only when eligible
FOUNDATION

Shared engineering, tailored delivery.

Common modules and components can evolve while individual customers receive only reviewed combinations and integrations that suit their operations.

VERSION HISTORY

Know what each build contains.

Customer/build identity, release notes, package metadata, checksums and approvals provide a foundation for traceable updates.

PROVISIONING

Authority is customer-specific.

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

Migration is not
copy and paste.

MAPPING & VERIFICATION

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.

01 / DISCOVERInventory source systems, identities, files and relationships.
02 / MAPDefine canonical IDs, fields, units, ownership and exceptions.
03 / REHEARSEImport to a controlled environment, detect duplicates and test joins.
04 / RECONCILECheck totals, documents, transaction history and unresolved differences.
05 / APPROVEObtain human sign-off and agree the cutover/rollback decision.
06 / HAND OVERDocument mappings, exceptions, training and recovery ownership.
NO HISTORICAL REWRITE

Preserve source meaning.

A financial import that balances numerically but loses the original invoices or accepted terms is not a faithful migration.

EXCEPTIONS

Don't hide unresolved records.

Missing foreign keys, ambiguous customers and invalid quantities belong in a review queue, not silently assigned invented values.

CONTROLLED RELEASE

A cutover is a decision.

Validation, backup, customer approval and a tested recovery path are part of the engagement rather than invisible implementation chores.

10 / SPECIALIST BUILDS

One studio.
Different kinds of software.

PRODUCT BOUNDARIES

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

We don't just
draw code windows.

LIVE SHADER + CODE SPECIMENS

The moving field behind the opening screen is drawn by a real GLSL fragment shader using WebGL, with a lightweight CSS fallback. These snippets are educational specimens, not copied proprietary application source. Switch languages, inspect and copy.

transaction-boundary.tsILLUSTRATIVE / READ-ONLY
// 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.

GLSL / GPU

Visuals are actually rendered.

The opening graphic uses vertex and fragment shader source compiled in the browser. Rendering stops when the graphic isn't visible or motion is paused.

DOM / ACCESSIBILITY

The atlas stays real HTML.

Tabs, search, explanations, diagrams and controls remain selectable, keyboard-operable HTML. The shader is decorative and never required to read the page.

REAL WORK / REAL PROOF

Source visuals are not the product.

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.

END OF ENGINEERING ATLASStill curious? Good.

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.

FULL UNABRIDGED REFERENCE ↗FEATURE ATLAS ↗TALK TO THE TEAM ↗
THE RIGHT KIND OF OVERENGINEERED

Complexity where it earns its place.
Clarity where people need it.

The best engineering is rarely obvious from the screen. It's in what happens after a failed request, a corrected receipt, a disputed price or a customer who needs a system nobody else thought to build.

SEE WHAT WE BUILD ↗