INDUSTRY · AGRIBUSINESS

Every shipment keeps the proof of where it came from.

Buyers and regulators, in Europe first, now ask exporters to prove where their product was grown. Nieme gathers the farm maps, the registry records and the purchase documents, and prepares the traceability dossier for each shipment, for the compliance lead to approve.

Functions it combinesFinanceLegalCommerceAccounting
Signals

What Nieme has observed in the systems you connected. Observations, not instructions — nothing here has been authorized.

SignalsMost recent · newest first by when Nieme received them.
A new export contract is filed12 min ago

The contract for 3,000 tonnes of soy lands in the shipments folder; field updates come from the agronomists' group.

Google Drive

Project: Exports 2026Raised as a Signal
A document changed2h ago

A document changed in a connected folder.

Google Drive

No ProjectWatching only
A message arrived5h ago

A message was observed in a selected channel.

Slack

No ProjectWatching only

A new export contract is filed

The contract for 3,000 tonnes of soy lands in the shipments folder; field updates come from the agronomists' group.

Google Drive

Raised as a Signal

Observed event

Source
Google Drive
What happened
A new export contract is filed
When Nieme saw it
12 min ago

Nieme recorded that this event happened. Observation alone authorizes nothing.

Why it matters

Nieme's reason

the source is selected for this Project

Status

Raised as a Signal. Nieme proposes the work; a person decides.

BRIEF.ON · OPERATION.ON
Traceability dossier for contract 2026-118
Workforce · RolesBudget · —Deadline · —Assurance · —Outputs · —
Save Draft
OPERATION DRAFTSaved draft · e07a4c19
Ready to approveReady for Review.
OBJECTIVE
Traceability dossier for contract 2026-118

This title is independent of the Objective.

Assemble the traceability dossier for the 3,000 tonnes of soy in contract 2026-118: map every lot to its supplying farm, attach the registry record and map for each farm, and list anything missing against the buyer's requirements.
One or more files — documents, specs, or code files

Produces each declared file as a governed Artifact of this one Operation, reviewed together.

SOURCE PACKAGE

Project: Exports 2026

From Signal · a contract added to the shipments folder

Selected Operation Sources (4) — explicitly chosen

GOOGLE DRIVE
Contract 2026-118.pdfPreview

Drive · Shipments · changed Sep 23, 14:10 · admitted Source

GOOGLE DRIVE
Supplying farms — registry recordsPreview

Drive folder · 14 farms · admitted Source

GOOGLE DRIVE
Farm mapsPreview

Drive folder · 14 maps · admitted Source

WHATSAPP soon
Agronomists' field groupPreview

Group · field updates · admitted Source

Traceability dossier for contract 2026-118

Exports 2026 · operation.on

REVIEW Immutable approved Operation
Objective
Prepare the traceability dossier for contract 2026-118
Role
Nieme Generalist v1
Success criteria
Each declared file stands on its own, the set is consistent, and nothing leaves before a person accepts it.
DELIVERABLES2 produced
  • PDFdossier-2026-118.pdf3.4 MBproduced
  • XLSXgap-list-2026-118.xlsx21 KBproduced
Delivered where the work lives, once acceptedApproved by the compliance lead 40f193
Evidence 40f193b2 · one decision pending AcceptRequest changesReject
TODAY

Where the work breaks now

Without a record

  • The proof is scattered across the supply chain.Farm maps, registry records and invoices sit with different people and systems.
  • Every buyer asks again.Each shipment's dossier is assembled from scratch, under deadline.
  • A gap is found late.A missing document surfaces when the buyer or the auditor asks for it.

With Nieme

  • Gathered from where it already is.Nieme reads the dossier folders and ties every lot to its farm and its documents.
  • Checked against the requirement.The rule that applies is stated up front, and every gap is listed before anything is sent.
  • Approved before it leaves.The compliance lead accepts each dossier, and the next shipment starts from it.
ONE PIECE OF WORK, END TO END

From an export contract to a traceability dossier ready for the buyer

  1. 01 · Observed

    A new export contract is filed

    The contract for 3,000 tonnes of soy lands in the shipments folder; field updates come from the agronomists' group.

    Google DriveWhatsAppsoon
  2. 02 · Governed

    The dossier is opened

    Objective, the supplying farms, their registry records and maps, and the buyer's requirements are admitted.

    operation.onpolicy.on
  3. 03 · Executed

    The dossier and the gap list

    A traceability dossier per lot and a list of what is missing, with the farm it belongs to.

    PDFXLSX
  4. 04 · Reviewed

    The compliance lead approves

    Accept, request changes or reject. Nothing goes to the buyer before this.

    Review
  5. 05 · Carried forward

    The next shipment starts from this one

    Farms already verified, and the documents behind them, are there for the next contract.

    Evidence
WHAT STAYS ON RECORD

The work outlives the session that did it.

Every step above writes to one record. Swap the model, the agent or the person who executes, and the objective, the sources, the authority and the decision stay attached to the work.

ONE RECORD
operation.on
objective
Prepare the traceability dossier for contract 2026-118
context
Export contract · 14 supplying farms · registry records and maps · buyer requirements
authority
Approved by the compliance lead
executor
The model chosen for document work
evidence
A dossier per lot and a gap list, each item tied to its farm and document
decision
Accepted after two farms sent missing maps

The fields Nieme stores for every Operation.

OTHER USE CASES

Ship grain.
Prove origin.

We start with one export contract and the farms behind it. The dossier and its gaps come back before the buyer asks.

Rather talk to a person? Email the founder.