Daily record
Meetings, notes, files, messages and agent runs, written up as the day goes rather than reconstructed on Friday.
Niello/Platform
How it works, end to end
Six layers, and one door
everything goes through.
Niello sits underneath the tools your people already use. Every request an assistant or an agent makes takes the same five steps, and each step leaves a line in the record. This page is the whole mechanism.
Runs on hardware you ownBring your own model keysMac, Windows and Linux
The shape of it
Six layers, and who owns each one
The four at the top are the working day: what happened, who said what, what got done and what may be read. The two underneath are what the business is answerable for. They are one system — the rules in layer five decide what layer three is allowed to do, and layer six is written by both.
Meetings
Capture, transcript, summary and actions. Held on the machine unless you decide otherwise.
Tasks & agents
Work handed over and carried out, with a stop before anything that reaches a customer or costs money.
Knowledge
Collections: the set of files an agent may read. This layer is the permission model, not a search box.
Guardrails Early access
The rules. Which material may move, which models may answer, and what a person or an agent may do with either.
Evidence Early access
The record. Every decision the boundary made, kept as it was made, and mapped to the frameworks you already report against.
◆Lumen runs today. Mesh is in early access. Lumen enforces the settings on the machine in front of you on its own. What Mesh adds is one set of rules across every machine, and the record that comes with them.
A single request
Capture, classify, check, answer, record
Whether somebody types a question, drops in a contract or hands a job to an agent, the same five steps run. The order matters: the check happens before the model is called, not in a report afterwards.
One line in the record holds:who askedwhat was askedthe collection it readthe rule that appliedthe model that answeredwhere that model ranthe time
The check runs first
The rule is evaluated before the model is called. If it says no, the request stops there and the denial is written down with its reason. Nothing has to be walked back on Friday.
The rule picks the model
Where a model runs is part of the decision, not a preference each person finds in their own settings. Material classed as regulated can be held to models on hardware you own.
The record is a by-product
Nobody sits down to write it. It falls out of the five steps, which is why it is still there when someone asks about a Tuesday in March.
A rule reads like this
# evaluated on every request
policy contract_data_stays_local {
when classification contains "supplier_terms"
allow models where residency == "on_device"
deny egress; log evidence
}
policy contract_data_stays_local {
when classification contains "supplier_terms"
allow models where residency == "on_device"
deny egress; log evidence
}
Where the thinking happens
A model is software. It runs on a computer somewhere.
Usually that computer belongs to a supplier, which means the contract someone pasted in has made a round trip to a company you do not control. Niello can run the model on hardware you own instead. Which option is open to whom is decided by the rules, not by each person's settings.
On hardware you own
OllamaLM StudioGPUStackIntel OVMSLocal embeddings
The laptop, or a box in your own rack. Local-only mode goes further: switch it on and the sensitive work runs with no network at all.
Hosted, with your own keys
AnthropicOpenAIGoogleAzureBedrockMistraland dozens more
Your accounts, your billing. Bring your own keys; Lumen never proxies them through us.
◆Mixing the two is the normal case. A summary of a public page can go to a hosted model while the supplier contract stays on the machine. That split is a rule, written once.
04Knowledge
A collection is the permission
Ask what an assistant can do and you get a feature list. Ask what it can see and you get the truth. A collection is the set of files an agent is allowed to read. Hand it one and that is its whole world.
- ✓Nothing outside it. An agent cannot read a file that is not in the collection you gave it.
- ✓Spaces for teams. Group collections, members and tiers so a team shares a boundary rather than a folder.
- ✓A connector does not widen it. Reaching your calendar or your drive happens inside the same fence.
- ✓It is a list you can read. No guessing about what the model has quietly remembered.
Lumen
FilesCollectionsSpacesAgents
Scoped to · Quote drafterCollectionsSpace · Commercial
Handed to this agent
Rate cards & RFQs
62 files · indexed on this machine
May read the 2026 rate card, open RFQs and the standard terms. Nothing else in the space.
ScopedChange
Not handed over
Board papers
18 files · out of reach for this agent
Not handed over
People & pay
7 files · out of reach for this agent
Connector
Shared drive — Commercial
Preview · reaches only what this collection covers
Agent
Quote drafter
◉ One collectionGated actions on
✦ What it may read
- 2026 rate card — 1 file
- Open RFQs — 44 files
- Standard terms — 17 files
Asked for board papers11:04
Refused — outside the collection
Read the 2026 rate card11:04
Permitted
Stopped before sendingheld
Sending email is a gated action
Lumen · Collections — the fence an agent works inside
06Evidence
The record is written as it happens
When someone asks who approved what, and on what basis, the usual answer is a fortnight of screenshots and chased emails. Here the answer already exists, because each of the five steps wrote its line while it ran.
- ✓Kept as it was made. Timestamped, generated from real activity rather than from a questionnaire.
- ✓Mapped, not certified. Entries line up with the clauses your reporting already uses, and the gaps are named.
- ✓Yours on the way out. Export the whole record whenever you like, including the day you choose something else.
✓EU AI Act — Art. 12 record-keeping
✓ISO 42001 — 8.3 AI system operation
✓SOC 2 — CC6.1 logical access
✓NIST AI RMF — MAP 3.4
ISO 42001 — 9.2 internal audit
◆ Export as an auditor-ready pack
Evidence is mapped to these frameworks. Niello is not currently certified against them.
Division of labour
What Lumen does. What Mesh does.
Lumen is where the work happens, on the machine in front of a person. Mesh is where the answer lives when somebody asks about the whole estate. Same rules, same record.
Lumen · 01–04
The machine in front of you
Installed on a laptop or a desktop. It works whether or not anything else is switched on.
- ✓Captures the day. Meetings, notes, files and agent runs, indexed on the device.
- ✓Holds the collections. The permission model lives here, next to the files.
- ✓Calls the model. On your own hardware, or hosted with your own keys.
- ✓Stops at the gate. An agent drafts the email, then waits for a person.
Mesh · 05–06
Every machine, one answer
The estate view. In early access — the rules and the record described here are what Mesh is being built to do.
- ✓Holds the rules. One set, written once, reaching every device rather than each person's settings.
- ✓Decides what may answer. Which models are offered, and which are refused, before the call is made.
- ✓Keeps the record. Every decision the boundary made, across the whole estate.
- ✓Maps it to frameworks. Against the clauses you already report on, with the gaps named.
◆Connectors are in preview. Calendar, inbox, drive and messaging are being rolled out one at a time. Everything above works without any of them.
See it run against your own material.
Bring a contract, a meeting and a rule you would like enforced. An hour is enough.