Skip to content
Moduloa
← Five projects, one foundation
MOD-01 · Project 3 of 5

WAYBILL: supply chain routing

Four tasks

WAYBILL · for the route. Every route chosen by one published rule set, and written down with its reasons.

Each order would be routed by one published rule set, with no human in the loop, through qualified suppliers and certified hubs, on the path with the lowest landed cost that still meets the lead time. An order could split across hubs, every decision would be logged with its reasons, and when a route goes wrong the rule is fixed for everyone. Over time, this is what would let a product's supply chain form around its customers.

Why the name. A waybill travels with every shipment and says what is in it, where it is going and what it costs, so each carrier along the way works from the same paper.

Why it matters. Where a product is made, and from what, decides most of what it costs and how fast it arrives. A route a person picks cannot be checked. A rule can.

The shadow system it is designed to replace. The planner's spreadsheet and the email thread, where the real plan and its reasons live outside the system that is supposed to hold them. In the design, every route would be chosen by one published rule set and stored with its inputs and reasons, and the regulated exception, a customer's quality decision to add a hub, would be a signed record in the OS, not an email.

Research behind it, some. The intelligence layer arrives first · The barrier moves faster than the building · Speed came back, price did not · The coordination layer falls first · Tariffs are not a factory Many notes argue where production should sit, and the routing page works one example through. How a single order is routed, split and learned from has no note yet, and the cost input is empty.

On the site: The route · Routing · The shipment

Stage 0 · nothing is built · four open tasks · reviewed 5 October 2026

Inside it

What it is made of

The pieces of the work that live in WAYBILL. Each is written as designed: none of it runs yet.

Importer of record and cross-border routing

It decides which lanes can be delivered at all (B-04).

Whoever imports a product carries its duty and its compliance. In the EU the declarant owes the import duty, and under indirect representation so does the company it acts for; the declarant normally has to be established in the EU; and a consumer product may only be placed on the EU market when an economic operator established in the Union answers for it. Hubs and customers will not always share a customs territory, so who imports in each market would be settled before the first quote. No importer or customs representative has been appointed.

The duty it creates is a line in CHEQUER's price.

On the site: The shipment · The loop nobody closes

Sources Union Customs Code, Articles 18, 77(3) and 170(2) · General Product Safety Regulation (EU) 2023/988, Article 16(1) · Market Surveillance Regulation (EU) 2019/1020, Article 4

Regulated products, only to hubs certified for them

A rule the route reads before it compares cost (B-01).

A regulated product would be routed only to hubs certified for its domain and already qualified for that product. The legal manufacturer stays responsible: the EU Medical Device Regulation requires its quality system to cover the selection and control of suppliers and sub-contractors, and US medical device rules have incorporated ISO 13485 since 2 February 2026. For these products, adding a new hub is a decision the customer's quality system takes, not one the route takes alone.

The certification it reads is JACQUARD's, and adding a hub stays the customer's quality decision.

On the site: The route · The record (ISO 13485, clause 4.1.5)

Sources Medical Device Regulation (EU) 2017/745, Article 10(9)(d) · FDA, Quality Management System Regulation

The work

Tasks

Several people can work on the same task, each with its own deliverable. Ask to commit with the link on a task: name what you will deliver and a date no more than three months after it is accepted.

B-01Open

The routing problem, stated

Done when
A formal statement with EX-100 as the case: the decisions (a supplier for each line, a hub, a split), the constraints (qualification, domain certification, the 85 percent capacity cap, the lead time) and one objective. The site states the objective three ways (lowest landed cost within the lead time, best total cost, flexibility, risk and portability, or the customer's choice in the playthrough); the statement picks one and says why, or lists it as a decision for Moduloa.
Effort
About two weeks, part time

Ask to commit to B-01 →

B-03Open

Split and learn

Done when
A script reproduces the routing page's EX-100 choice from its inputs, logs its reasons and states where the choice would flip. It adds a written rule for splitting an order across hubs and one for how a bad outcome changes the next decision, and reports how much protection one, two and three hubs give.
Effort
Three to four weeks, part time

Ask to commit to B-03 →

The honest limits

What is open, and what would prove it

  • The site states the objective three ways: lowest landed cost within the lead time, best total cost and risk, or the customer's choice. B-01 settles one.
  • The routing page routes manufacturing, not logistics, and takes where suppliers are as an input. Choosing suppliers and hubs together is not specified.
  • Cost of production is the one input with nothing in it, and the network it would route across has no hubs yet.
  • Where the routing software lives is undecided: it is one of the three objects in the factory OS's open question, one OS or two.
  • No human in the loop stops at regulated products: there, adding a hub is the customer's quality decision.

On the register

  • P-07 · due 31 December 2036 · open · wages stop deciding where things are made
  • P-16 · due 31 December 2046 · open · production sits close to final demand
  • P-29 · due 31 December 2032 · open · an order is routed partly on a living, quality-fed hub score
← 2 · PYX4 · JACQUARD →
Reviewed 5 October 2026 · next review by 2 November 2026 · Questions go to seat 001, the founder · Corrections welcome
Ask Datum