OPERATOR-BUILDERSYSTEMS DESIGNER

Justin Thompson

FUTURE DESCRIBER JT-01

Operational systems for the next industrial age.

I turn manufacturing and ecommerce complexity into operational software, data products, AI-assisted workflows, and cloud-enabled infrastructure.

Built from inside the work, not from the outside looking in.

Problem model, workflow, architecture, implementation direction, testing, rollout, and reliability—human-owned; AI-accelerated.

  • SASKATOON / CANADA
  • OPERATIONS + DATA
  • AI-NATIVE BUILD
  • GOOGLE CLOUD
  • COMMERCE SYSTEMS

PRIMARY INSTRUMENT / EVIDENCE TOPOLOGY

System Atlas

FIELD ONLINE
CHANNEL / ALL SYSTEMSOne control model, four operating systems.

Focus a capability or system to trace the evidence behind it.

EVIDENCE / 01 · 02 · 03 · 04

SELECTED SYSTEMS / 04

Software built around real operational constraints.

Four system families. Each began with the operating model—not a technology demo—and extends through product, data, implementation, and reliability.

MISSION FILE / FLOORLINE

Production Control Layer

Operational platform for a physical-goods production environment.

SELECTED SYSTEM / DETAILS GENERALIZED
Problem
Planning, handoffs, status visibility, and reporting were fragmented across disconnected tools and manual coordination.
System
A unified workflow and visibility layer connecting planning, execution, exception handling, and operational reporting.
Result
A clearer shared operating model with less coordination friction and more scalable production management.

Selected capabilities

  • Workflow planning and coordination
  • Execution and exception visibility
  • Reporting and business-system integrations
OWNERSHIP / DELIVERY SPAN

Problem framing / Workflow + product design / Architecture / Implementation direction / Testing + rollout

SCHEMATIC / 01ILLUSTRATIVE STATE
Illustrative work moving through coordinated planning, execution, verification, and feedback states.

MISSION FILE / LIFECYCLE

Product Lifecycle Intelligence

Decision-support platform for a multi-product ecommerce catalog.

SELECTED SYSTEM / DETAILS GENERALIZED
Problem
Lifecycle and inventory decisions were difficult to review consistently across multiple systems and data sources.
System
A lifecycle review and analytics layer combining product signals, structured approvals, and reliable background processing.
Result
More consistent decisions with analytical work separated from the interactive application experience.

Selected capabilities

  • Lifecycle review workflows
  • Sales and inventory decision support
  • Reliable analytical pipelines
OWNERSHIP / DELIVERY SPAN

Decision model / Workflow + UX / Data architecture / Cloud implementation / Production hardening

SCHEMATIC / 02ILLUSTRATIVE STATE
A generalized lifecycle loop informed by performance, availability, economics, and policy, with human judgment at the center.

MISSION FILE / HUMAN GATE

AI-Assisted Product Creation

Human-in-the-loop product setup for ecommerce.

SELECTED SYSTEM / DETAILS GENERALIZED
Problem
Turning mixed creative and product inputs into complete ecommerce records required repetitive interpretation and manual entry.
System
A reviewable workflow that uses deterministic rules and AI-assisted extraction to produce structured product drafts.
Result
A more consistent path from creative input to review-ready product data, with people retaining authority over consequential changes.

Selected capabilities

  • Document and image interpretation
  • Structured product-data generation
  • Human approval before external changes
OWNERSHIP / DELIVERY SPAN

Workflow model / Product + UX / AI/rules design / API architecture / Acceptance + verification

SCHEMATIC / 03ILLUSTRATIVE STATE
Mixed source material passes through interpretation, human review, structured modeling, and a controlled external change.

MISSION FILE / RISK FIELD

Inventory Risk Intelligence

Decision support for inventory risk across a multi-variant ecommerce catalog.

SELECTED SYSTEM / DETAILS GENERALIZED
Problem
Raw stock levels did not provide enough context to determine which inventory gaps required attention first.
System
An analytical layer that combines demand and supply context into a prioritized, auditable decision queue.
Result
Inventory risk becomes a structured sequence of decisions rather than a flat list of unavailable items.

Selected capabilities

  • Commerce-data ingestion
  • Context-aware forecasting
  • Prioritized reporting and auditability
OWNERSHIP / DELIVERY SPAN

Business logic / Forecasting model / Data architecture / Decision UX / Reliability + boundaries

SCHEMATIC / 04ILLUSTRATIVE STATE
Demand, supply, and contextual signals feed an auditable, freshness-aware decision queue.

CAPABILITY MATRIX / 06

From operational ambiguity to a working, reliable system.

Six connected disciplines, each tied to the selected systems above. The point is not a longer tool list; it is control across the whole implementation loop.

C1

Operational systems

Workflow, state, queues, handoffs, capacity, quality, exceptions, and adoption—modeled around the work as it actually happens.

PROOF SIGNAL

State and flow made explicit across production and lifecycle work.

Technical range
  • Process mapping
  • State machines
  • Capacity planning
  • Exception design
  • Rollout + training
C2

Product + UX

Information architecture, review flows, authority boundaries, and decision surfaces that remain legible under operational pressure.

PROOF SIGNAL

Complex production, lifecycle, and product setup paths shaped into usable control surfaces.

Technical range
  • Information architecture
  • Interaction design
  • Review workflows
  • Role + authority design
  • Operational visualization
  • Full-stack React + TypeScript
C3

Data + intelligence

Data models, pipelines, forecasting, analytical read models, caches, freshness, and explicit degraded states built for decisions.

PROOF SIGNAL

Heavy computation moved off the read path; uncertainty and freshness stay visible.

Technical range
  • PostgreSQL + SQL
  • BigQuery
  • Python + Pandas
  • ETL / ELT
  • Forecasting
  • Cache + read models
C4

AI + automation

Rules-plus-model extraction, human approval gates, bounded agents, and automation with a clear source of truth.

PROOF SIGNAL

Multimodal interpretation accelerates setup while consequential writes stay reviewable.

Technical range
  • Multimodal vision models
  • Document + image extraction
  • Deterministic rules
  • Human-in-the-loop gates
  • Codex + Claude workflows
  • OpenClaw orchestration
C5

Cloud + reliability

Thin interactive applications backed by scheduled and on-demand compute, scoped identities, observable jobs, and recoverable failure paths.

PROOF SIGNAL

Background work, analytical compute, and the read path are separated and monitored.

Technical range
  • Cloud Run jobs + services
  • Cloud Scheduler
  • BigQuery + Cloud Storage
  • Queues + retries
  • IAM + Secret Manager
  • Health + monitoring
  • Migrations + rollback
  • Playwright + pytest
C6

Commerce + integrations

Product, variant, inventory, lifecycle, workspace, messaging, and reporting systems connected without losing operational ownership.

PROOF SIGNAL

Commerce APIs and workplace tools become parts of one controlled workflow.

Technical range
  • Shopify GraphQL + REST
  • Google Workspace
  • Slack
  • Webhooks + APIs
  • OAuth
  • Operational reporting

OPERATING METHOD / CLOSED LOOP

The build starts before the code.

AI increases implementation velocity. It does not replace judgment about the operation, the architecture, or what safe completion means.

  1. 01

    Observe the work

    Learn the real workflow, failure modes, handoffs, constraints, and incentives.

  2. 02

    Define the control model

    Make states, ownership, data, exceptions, and authority explicit.

  3. 03

    Build the shortest useful loop

    Ship a narrow working system, instrument it, and watch real use.

  4. 04

    Harden and extend

    Automate safely, improve reliability, and move heavy work to the right infrastructure.

ORIGIN / OPERATOR TO BUILDER

Close enough to the work to know where software breaks.

I came into software through production, marketing, analytics, and operations rather than a conventional engineering path. That is the advantage.

For 13+ years I have worked close to physical production and ecommerce: scheduling work, managing inventory, reading demand, improving handoffs, and seeing where spreadsheets, systems, and human judgment stop lining up. I now build the systems I once wished the operation had.

My work sits between operator judgment and technical implementation. I use AI-native development workflows aggressively while keeping the problem model, architecture, acceptance criteria, review, rollout, and operational accountability human-owned.

  • BASESaskatoon / Saskatchewan
  • STUDYBusiness Economics / Honours
  • FIELDManufacturing + Ecommerce
  • MODEOperations + Data + AI
IDENT / JT-01ACCESS / PUBLIC
Justin Thompson seated in a studio workspace
SUBJECTJustin Thompson
CALLSIGNFuture Describer
STATUSOPERATIONAL
Dark album artwork with mirrored angular figures drawn in fine red lines
ALBUM ART / VARIATION STUDIESARCHIVE / OWNER-SUPPLIED

PARALLEL PRACTICE / THE BASEMENT PAINTINGS

Patience, weight, atmosphere.

Outside systems work, I make long-form instrumental music with The Basement Paintings, a Saskatchewan ambient/post-rock band formed in 2011. It is a sustained practice in collaboration, tension, scale, and listening closely enough for several people to build one thing together.

“Future Describer” began as a song title on our first album before it became my online callsign.

Visit The Basement Paintings (opens in a new tab)

FINAL TRANSMISSION / CHANNEL OPEN

Build the next control layer.

Available for selected systems, analytics, automation, and implementation work—especially where real operations and software need to meet.