Industry · Risk and compliance
We caught regulator changes on day one for a compliance team
The problem
Sanctions, registry and regulator changes are found by hand, and often after the deadline.
How we solved it
Gated feeds from government and licensed sources, checked for where they came from, whether you may use them, and whether they are current.
The result
The change reaches the team the day it is published.
Read the full story
What was going on
Every morning, an analyst worked through a list of government and regulator websites, checking each one by hand for anything new. When a sanctions list or company registry changed overnight, the team only found out when someone happened to look, and sometimes that was after the deadline to act.
What we did
- We set up a Quarry feed for every source the team watched: sanctions lists, company registries and regulator notices.
- Every update passes three checks before it gets in: where it came from, whether the team is licensed to use it, and whether it is still current. A stale source is flagged, never served quietly.
- Changes arrive in one format, inside the client’s own systems, ready for the compliance team to act on.
What changed
The change reaches the team the day it is published. Nobody spends the morning refreshing websites, and every update can be traced back to its source.
Quarry
Industry · Commodities
We gave an agri trader live prices and tariffs
The problem
Prices, tariffs and crop data sit on portals that break the scrapers built to read them, and trading rules shift with the season.
How we solved it
Maintained feeds plus collectors running inside their own systems, with trading rules versioned over the record.
The result
Traders work from current data, and the rules move with the market.
Read the full story
What was going on
The trading desk lived on prices, tariffs and crop reports published on government and market portals. Their scrapers broke whenever a portal changed its layout, and the trading rules, which shift with the season, sat in spreadsheets only a few people could edit.
What we did
- Quarry replaced the fragile scrapers with maintained feeds, plus collectors running inside the trader’s own systems for the sources nobody else covers.
- When a portal changes, the feed is fixed on our side. The desk just keeps receiving data.
- In Assembler, the trading rules became versioned rules over that data. A seasonal change is a new version of a rule, not a new spreadsheet.
What changed
Traders work from current data, and the rules move with the market. When a rule changes, everyone can see which version made which call.
Quarry + Assembler
Industry · Trade
We turned five inboxes into one clearing flow for a trade house
The problem
Each party holds one piece of the picture, and the clearing record is assembled by hand from all of them.
How we solved it
Outside data brought in and joined into one record, then cleared by versioned rules with every step logged.
The result
One path through the process instead of five inboxes.
Read the full story
What was going on
Clearing a single trade meant chasing data from every party involved. Each one held a piece of the picture, and someone stitched the clearing record together by hand from five different inboxes.
What we did
- Quarry brought in the outside data each party publishes, in one format.
- Smelter joined every piece into one record of the trade, with each value keeping a note of where it came from.
- Assembler runs the clearing steps as versioned rules, and writes every step to a log the client owns.
What changed
One path through the process instead of five inboxes. When someone asks why a trade cleared, the answer is already in the log.
All three
Industry · Retail
We gave a retailer one set of numbers
The problem
Sales, stock and supplier systems each hold a version of the truth, and none of them agree.
How we solved it
Every source is read where it sits and resolved into one record, with each value keeping its source.
The result
One set of numbers for the week, with nothing copied out.
Read the full story
What was going on
Sales, stock and supplier systems each reported a different number for the same week. Analysts exported all three into spreadsheets and argued over which one was right, and the meeting started from the argument, not the decision.
What we did
- Smelter reads each system where it sits. Nothing is copied into a new warehouse.
- Records that describe the same product, store or supplier are matched and resolved into one record.
- Every value keeps its source, so anyone can see which system a number came from.
What changed
One set of numbers for the week, with nothing copied out. The team starts from the same figure, and can check where it came from.
Smelter
Industry · Finance
We reconciled two finance firms without sharing their data
The problem
Two organisations have to agree on figures that neither is allowed to share.
How we solved it
Both sides compute over the record without exposing raw data to each other.
The result
Reconciliation without a data-sharing agreement.
Read the full story
What was going on
Two firms had to agree on shared figures at the end of every period. Neither was allowed to show the other its raw data, so reconciliation ran on emailed summaries and a great deal of trust.
What we did
- Each firm’s data stays inside its own environment.
- Smelter lets both sides compute over the record together, so the figures are compared without either side exposing its raw data.
- Where the numbers differ, both sides see the difference, not each other’s books.
What changed
Reconciliation without a data-sharing agreement. The figures are agreed, and the private data stays private.
Smelter
Industry · Hiring
We made every interview provable for Nexaryth
The problem
Verification steps are run by hand, and afterwards there is no way to prove what happened.
How we solved it
Versioned rules and agents run the checks, with every action written to a log the client owns.
The result
A trail you can show, for every interview.
Read the full story
What was going on
Nexaryth runs verified interviews for remote hiring. Its identity and integrity checks were done by hand, and afterwards there was no reliable way to prove what had been checked, by whom, or when.
What we did
- Each check became a versioned rule in Assembler, with AI agents running the steps a person used to do.
- Every action, by a person or an agent, is written to a log Nexaryth owns.
- When a check changes, it becomes a new version, so past interviews still show the rules they were run under.
What changed
A trail you can show for every interview: what was checked, when, and under which version of the rules.
Assembler
Industry · Logistics
We let a freight forwarder change its process without engineers
The problem
The process changes constantly, and every change waits for an engineering slot.
How we solved it
Rules and workflows are changed in the model, not shipped as a release.
The result
The operations team changes the process the day they decide to.
Read the full story
What was going on
A freight forwarder’s process changes all the time: new carriers, new documents, new approval steps. Every change to its CRM waited in line for an engineering slot, so the operations team worked around the system instead of in it.
What we did
- In Assembler, the process became rules and workflows the operations team can read and change themselves.
- A change is a new version, switched on without a software release.
- If a change goes wrong, it is rolled back in one step.
What changed
The operations team changes the process the day they decide to. Engineering is free for everything else.
Assembler