Tacit Source. Human knowledge. Licensed for machines.
How it works

From a licensed way of working to a machine that runs it, and back to a count.

One interface, published on the same terms to every maker, kit company and fleet owner — including the one owned by the same group Tacit Source is part of.

The sequence

Five steps, from the registry to the invoice.

  1. 01
    Licensed from the corpusEven Steven licenses an admitted, built way of working into the corpus Tacit Source holds. Nothing reaches the registry that was not built from a hand's own admitted sessions, under their own consent.
  2. 02
    Released against a published interfaceA named way of working is released to a machine through the release interface — the same specification any maker, kit company or fleet owner is given, cross-licensed on the same terms.
  3. 03
    Chosen by a person, on the dayBefore a job, a person on the crew chooses whose way of working runs, by name. The choice is the authorization the machine may not move without.
  4. 04
    Counted from the same actThat choice starts the count. Tacit Source's count line and Even Steven's ledger read the same record, so the clearance and the invoice cannot be adjusted apart from each other.
  5. 05
    Exposed back to the hand, at sourceThe hand sees the count line that names them, directly from the system that wrote it — not a figure Even Steven retypes on their behalf.
The interface

Published, not proprietary to any one maker.

Tacit Source's release interface and count interface are built and tested against each other — closed on both sides, with fixtures both sides reproduce byte for byte. The specification itself is not yet public: it is held back until counsel has the patent particulars and any recipient signs an NDA. What is ruled is the intent — publish it, so any machine, any maker, same interface, same terms, proves the neutrality of the registry rather than asserting it.

A registry that only its own family can build against is not a registry. A registry published on identical terms to a competitor is what makes it trustworthy.

By counterparty

What each one actually does.

Makers

Build to the interface

Build a machine that accepts a released way of working and reports its count, against the published specification, on the same terms as any other maker.

Kit companies

Supply the release path

Build the physical and software path that lets an existing machine accept a released way of working without becoming a new machine.

Fleet owners

License a way of working

Choose a named way of working for a job, on your own machine, and pay for the hours it runs — on the same record the hand can check.

Want the interface particulars?

Tell us which one you are, and what you're building.