For operations, supply chain, finance and compliance

Everything we have written down, in the order to read it.

Start with a scenario if you want to know whether this fits your week, or with a paper if you want the mechanism in full. The scenarios are short and name the records involved; the papers are long and say where every claim stands.

The long documents

4 documents

Runink FACE The evidence of your next loss is already in your systems. Scattered across a dozen systems that were never designed to talk to each other. FACE assembles it, works out what the combined picture means, and produces a specific, reviewable recommendation with the underlying records attached — for a named person to approve. 30 pages
Runink CORE One operations layer, on hardware you already own. The layer beneath a company's software that runs it, shows a named person what is happening across all of it from one screen, holds the connections that software uses to reach the company's own information, and carries changes from written to running. 21 pages
Runink PULSE A marketing engine that runs inside your own business. One application a marketing team operates directly. It audits your website and social presence, researches your market, prospects the public web for leads, and writes the material that carries somebody from first hearing of you to buying from you — staging every draft with a status and an approve against it, on channels that stay disarmed until you arm them. 23 pages
Runink CORE Continuous oversight, with a second opinion on every finding. Atlas watches a company's capital spending as it happens. CORE's automated assessors read Atlas's findings and score them before a person is asked to act on any of them. This is an architecture paper: it states on pages 11 to 13 exactly which half of the design runs today and which half is drawn, and every claim in it should be read against those pages. 23 pages

Worked scenarios

12 scenarios

Each one names the records it reads, what it drafts, and who approves it. All twelve are Runink FACE.

IoT Sentinel Cold Chain and Yard Safety A container drifts warm overnight and nobody opens the door until morning. What the yard camera already sees, read against the handover record and the paperwork the consignment travels with. Compliance Auditor Customer Data Privacy and Emissions Reporting Operating a system quietly writes personal data into its own logs, and the emissions report takes a quarter to assemble. What the software reads for each, what it hands to the person accountable, and where a check it could not run says so. Claims Agent Freight Claims and Port Charges Claims expire because assembling one takes a morning. The entry, the hold, the missing documents, the days held and the per-day charge arrive already gathered and joined, so a person only has to judge whether the case holds. Route Twin Re-Running the Route After the Day Has Changed The plan that was optimal at six in the morning is not optimal by ten. Nobody re-runs it, because re-running it means re-planning a day by hand. This is about making the second run cost nothing. Circular Economy Returns and What to Do With Them A returned item is worth the most on the day it comes back. The call on where it goes — shelf, refurbishment, recycling or disposal — is drafted at the scan, from a written-down policy that gives the same grade the same answer every time. Fulfillment Agent Stock Cover and Supplier Planning Most stockout warnings arrive after the safety stock is already gone, which leaves you paying for air freight. The point is to see it while there is still time to order normally. Voice-AI Dispatcher Talking to Drivers Without a Screen The person who knows a load is late is the one who cannot type. Asking and answering out loud gets the fact onto the record while the truck keeps moving, and the desk still makes the change. Hypothesis Engine Testing a Plan Before You Commit to It A port shuts and you have a day to pick a new route. State the change as a hypothesis and the rules it touches, and get back the case laid out — which rules it collides with, in what order, and what someone would have to believe for the plan to hold. The decision stays with the person accountable for it. Domain Graph The Picture Nobody Has Time to Assemble The facts are in four systems in four formats, and joining them takes a morning nobody has. So the picture that would let somebody act only ever gets assembled after the fact, for the meeting that reviews it. Demand Signal When Demand Turns Before the Plan Does A line starts moving weeks before the reorder point does. By the time the plan catches up the cover is gone, and the difference is paid in air freight. This is about reading the turn while it is still a forecasting problem. Compliance Agent Which Clause Governs This, and Who Checked A routine question settled by a paragraph takes a day and a half to answer, so it gets answered from memory instead. The clause and the record arrive together, cited. The reading is the software's. The judgement is not. Finance Domain Your Adjusters Spend the Day Gathering, Not Deciding The policy wording, the loss report, the reserve history and the authority limit for a claim that size sit in four places. They arrive joined, with a drafted next step and the reading it rests on. The underwriter still decides.

Shorter notes

Several dozen pieces on the operational problems behind the documents above — a customs entry held for a missing document, a freight claim still inside its filing window, a return that costs more to handle than the goods.

All articles

One next step

Easier to answer against one of your own records than to read another page.

Bring one lane, one claim, or one month of invoices. Half an hour, with whoever owns the problem in the room, and we walk that one example end to end. If it is not the shape this addresses, we will say so.

Book a consultation

The form opens with the library already named, so you are not starting by explaining where you came from.