Skip to content
Moduloa
← On board · all open invitations
Open invitation · TOUCHMARK · APIs and the unit record

The platform engineer

Open

Builds the unit record in code: every unit, part lot and build step, open over an API to the customer whose product it is. Today it is only specified.

An open invitation, not a vacancy: several people can take it at once, and it carries no number until you commit to something specific. This page says what Moduloa hopes for and where a first contribution could start.

Say what you would deliver

Why it matters

Why Moduloa needs this

Every promise downstream leans on the record: marking mints an identity at every closed sub-assembly (M-06), the finished product carries a QR that opens its full history (M-07), and the quality page commits to a customer API that, like the resolver, is specified before it is built. None of it exists in code: there is no repository, no resolver and no running instance. Frogbyte, seat 002 on the register, will contribute to the factory OS data model, so this work would sit beside theirs: the resolver, the as-built record and the customer API that reads from it.

What we hope for

What you would bring

  • Append-only or event-sourced data design, where a record is corrected by a new entry and never edited.
  • Identifier and resolver standards: GS1 Digital Link, IEC 61406, ISO/IEC 15459.
  • Public APIs for outside customers: versioning, per-customer access to their own records, and keeping both stable for a product's whole life.
  • Shop-floor and enterprise interfaces: OPC UA, MTConnect, MES and ERP integration.
  • Security treated as a safety function where software meets machines.
On the task board

Tasks that suit you

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

Or your own

Other first deliverables

Each is specific enough that by its date anyone can tell whether it was delivered. Some are a task above in a smaller form. Name one, or a better one.

  1. A versioned schema for the as-built tree that M-06 describes, each node carrying part identity, lot or serial, step, station, executor, timestamp and blueprint version, checked against the EX-100 unit trace on the execution page.
  2. A minimal resolver for the fallback identity scheme in M-02, in an open repository: one https URL per part that returns supplier, part, revision and lot.
  3. An OpenAPI sketch of the customer read side of the unit record, including the access model M-07 leaves as future work.
The terms

What this is, and is not

What this is not

Not a job or a product with users: there is no hub and no unit to record yet, so the work is the specification and the first open code. On its own a seat carries no pay, no equity and no supplier position, and any paid work is agreed separately.

What you get

When your commitment is accepted, it shows on the task and on your seat card, and a first commitment takes the next permanent number on the register, with your name, a link and your date. When the work is delivered in the open you are aboard and a certificate is issued. Nothing is paid for a seat and none is for sale: on its own a seat carries no equity and no supplier position, and any paid work is agreed separately, on its own terms. The entry stays either way: a commitment not delivered by its date is marked lapsed and dated, never removed.

How to start

Pick a task that suits you and ask to commit to it, or name your own first deliverable: what you will deliver and a date no more than three months after it is accepted. Write to shk@moduloa.com, or use the link on any task, which opens the contact page with the subject filled in. It does not have to be large. It has to be specific enough that anyone can tell by its date whether it was delivered.

Say what you would deliver →

Before you write

Read these first

Also needed in TOUCHMARK · APIs and the unit record: The quality systems lead

Ask Datum