7Q4N-0190Observation
V-204 in service
quote · shift log, 2 Feb, line 14
- valid from
- 2026-02-02 06:00Z
- recorded at
- 2026-02-03 08:10Z
- posting lane
- import · receipt
- signed
- ed25519 · prev 41ab…c3e0
The record for the life of an asset
The system of record for intelligence.
The ground people and agents stand on together: what is in the record, where it came from, on whose authority, and what it does not know. Syderial decides what a model is given, and limits what an agent can do to what that ground supports.
- 01Capture
- 02Bound
- 03Entail
- 04Compile
- 05Gate
- 06Receipt
The missing layer
Every important system has a system of record. Intelligence does not.
Money has accounting. Operations have ERP. Relationships have CRM. People have identity. Each acquired a record the moment it began to matter. Intelligence now matters, and it runs without one.
Assets outlive the people who knew them.
An oil field runs for decades. What each engineer, model and vendor claimed about it, and what that claim rested on, leaves with them.
The problem →What Syderial does
Governed continuity for people and agents.
People and machines each know part of an asset. Syderial is the ground both stand on as they maintain it and discover what is new together.
- 01
Decides what a model is given
Only what the person or agent is cleared to see, with its source and authority attached, cited and signed.
- 02
Limits what an agent can do
To what that ground supports. An action it doesn't support doesn't run, or waits for a person.
- 03
Records what happened
What the agent knew, what it was allowed to see and what it did, with receipts.
- 04
Admits what it doesn't know
When the record has nothing to say, the answer says so, with a receipt.
Context of record
Memory tools recall. Syderial keeps the record.
What Syderial serves to a model is the context of record: what is in the record, where each part came from, on whose authority, who could see it, and what changed.
Each line is a claim
A claim is a statement about the world with its evidence attached. It names who asserted it, the source, and the boundary it belongs to.
Two clocks on every entry
Valid from and valid to mark when a claim applied, according to its source. Recorded at marks when Syderial learned it. A row updated in place loses the old value; Syderial keeps both.
In the inference path
A harness points at a Syderial door as its provider. Every turn passes through the record on its way to the model and back, with its author.
The journal
The record is a journal. The chain of signed entries is the ledger.
Kept the way books are kept. Each entry is posted once, dated and signed. A correction is a new entry that cites what it corrects.
Posted once
Dated, signed, chained to the entry before. Never edited.
Lines with evidence
A quote of retained source, or a pointer to an entry.
Posting lanes
Reader, principal or import, each with a receipt.
Corrections
New entries that cite what they correct.
Imported journals
Existing journals and notes post as entries.
Information flow control
Context without boundaries becomes contamination.
Every claim and every request has a label with five axes: boundary, sensitivity, compartments, integrity, purpose. Information flows to a reader only when the reader’s clearance dominates the label on every axis. The same rule governs what an agent may do.
- Taint follows lineage: anything derived from untrusted input stays marked.
- A session that has read private data and untrusted input can't send anything out.
- Declassification takes two people. Chinese walls close conflicting compartments.
Six stations
Three doors. One signed record behind them.
Every turn passes through six stations on its way to the model and back. Any model can answer behind the doors, and the record stays the same.
- 01
Capture
Every turn, with its author.
Hooks in the agent harness capture every turn with the person or agent who wrote it. Existing journals and notes post as entries, and connectors keep each source's own record identity.
- 02
Bound
Labels on every fact, information flow on every read.
Every claim has a label. A reader sees it only when the reader's clearance dominates that label on every axis.
- 03
Entail
Evidence must support the claim.
A typed decider asks small, typed questions of each proposed line, then places it in one of four bands: commit, propose, quarantine or degraded. Nothing disappears without a trace.
- 04
Compile
A hashed packet, not a prompt dump.
Syderial answers each question from a bounded, hashed packet of the context of record, citing the signed spans the reader may see.
- 05
Gate
Policy before any tool call runs.
Syderial checks every tool call against its reach ceiling, then allows it, sends it for approval or denies it before anything runs. The same rule governs a read.
- 06
Receipt
Signed, hash-chained, independently verifiable.
Every commit is signed and chained to the one before it. Every answer returns a serving receipt. Replay and verification run in your console and offline.
Evidence you can check
Every commit is signed. Every answer returns a receipt.
Each commit is an Ed25519-signed event on a hash chain. Signing keys never leave a KMS. Each chain is anchored by independent RFC 3161 timestamp authorities, so it verifies outside your tenant and offline.
A superseded entry stays beside its replacement, both clocks intact. Nothing is edited in place.
Who it is for
For assets that run for decades.
Syderial is for the operator of a long-lived regulated asset in oil and gas, utilities, pharma or infrastructure, where a confidently wrong claim costs years.
What happens when the person who understood this asset leaves, and what does a wrong assumption about it cost?
The question we ask operators.
Early access
A model can’t reason over what it isn’t given. With Syderial, an agent can’t act beyond it.
Early access is for design partners: operators of long-lived regulated assets, one bounded workflow each.