The idea
Evidence that never leaves the chain.
What it is
On-prem agent · signed packets
Systems · Sentinel
Evidence from the edge of ops.
Sentinel is the on-prem compliance agent: watch what your ground segment already produces, sign it into a hash chain, and stream proof into Caelex — continuous, attributable, hard to fake.
Not a camera
An agent
Reads allowed signals on your network — not a marketing widget.
Not a PDF dump
A chain
Linked, signed packets that break loudly if tampered.
Not opaque AI
Mapped proof
Facts tied to duties with an auditable trust path.
Pipeline
Collect → hash → sign → stream.
The same mental model as the product: continuous evidence, not a quarterly archive export. Illustrative path — deployment details are configured per customer.
Evidence path · illustrative
01
Collect
Ops signal on your network
02
Hash
Packet + previous link
03
Sign
Ed25519 agent key
04
Stream
Workspace chain + map
sha256:packet · prev=sha256:… · sig=ed25519:… · mapped → NIS2 · debris themes
The system
Four instruments. One chain.
Agent
On your side of the wall
Runs where the data lives — ground segment, not a third-party scraper of your secrets.
Chain
Hash-linked packets
Each packet links to the previous. Breaks are visible. Genesis is explicit.
Sign
Ed25519 by design
Tamper-evident evidence from collection to workspace — not a screenshot in Slack.
Map
Duty-aware
Signals tied to regulatory themes (NIS2, debris, supervision) — not a raw log dump.
Capabilities
What Sentinel can do.
Built for operators who need continuous, signed evidence — counsel and leadership reading the same chain.
01
On-prem deployment
Install in mission control or station networks. You choose what the agent may read; outbound is signed evidence, not free-form telemetry.
02
Cryptographic evidence
SHA-256 chains and Ed25519 signatures on every packet. Integrity checks run continuously in the workspace.
03
Cross-verification
Optional multi-agent agreement raises trust when independent paths confirm the same fact — without a single fragile source.
04
Regulation mapping
Attach collected facts to obligation themes — cyber, debris, reporting windows — with article-level context where the map is configured.
05
Trust scoring
0–1 trust from source quality, freshness, and verification depth. Auditable, not a black-box “AI confidence.”
06
Ops dashboard
Live feed of packets, chain health, and agent heartbeats — for ops and compliance to share one truth.
Deploy surface
Where ops already runs.
Where it runs
Your perimeter. Your keys. Your chain.
Sentinel is designed to sit where operational truth already exists — not to replace mission software. Scope of read access is contractual and technical, not open-ended.
Ground stations
TT&C and pass-side data paths that already touch the asset.
Mission control
Planning systems and status buses operators already trust.
CI / build pipelines
Where software and config changes become space-relevant evidence.
Secure enclave
When classification or export posture demands a harder perimeter.
The shift
Old habit
“Export the log for the audit.”
Sentinel habit
“The chain was already signing.”
Next
Put an agent on the edge of ops.
Deploy paths are scoped with your team. Software produces general evidence workflows — not legal advice.