Trust and verification for edge infrastructure.
- Documentation: edgesentry.github.io/edgesentry-rs/en/
This repository is a Cargo workspace containing two crates:
| Crate | Description |
|---|---|
| edgesentry-audit | Ed25519 + BLAKE3 cryptographic audit trail for IoT devices and infrastructure |
| edgesentry-inspect | Edge-first 3D scan vs. reference deviation detection for construction and maritime inspection |
Implements three pillars of trust for IoT deployments:
- Identity — Ed25519 digital signatures to guarantee the authenticity of devices and data
- Integrity — BLAKE3 hash chains to ensure data immutability and forensic readiness
- Resilience — Store-and-forward offline buffering for narrow-bandwidth and intermittent-connectivity environments
Designed to support Singapore's Cybersecurity Labelling Scheme (CLS) Level 3/4, iM8, and Japan's Unified Government Standards.
| Document | Description |
|---|---|
| Introduction | Vision, three pillars of trust, motivation |
| Roadmap | Phased plan: Singapore → Japan → Europe, compliance mapping |
| Concepts | Tamper-evident design, AuditRecord, hash chain |
| Architecture | Device side vs cloud side, design flow |
| Library Usage | Start here — in-memory example, no Docker needed |
| Interactive Demo | End-to-end demo with PostgreSQL + MinIO |
| CLI Reference | CLI commands and lift inspection scenario |
| Contributing | Prerequisites, tests, static analysis, PR conventions |
| Build and Release | Release pipeline and version automation |
Detects structural deviations at the field edge by fusing 3D point clouds with reference design data — no cloud round-trip required during inspection.
3D sensor (LiDAR/ToF)
│ point cloud
▼
trilink-core::project ← 3D → 2D depth map / height map
│ depth map (image)
▼
AI inference ← anomaly detection (built-in model or HTTP endpoint)
│ bounding boxes + class
▼
trilink-core::unproject ← 2D detections → 3D world coords
│ world-space anomaly points
▼
Scan-vs-reference engine ← compare against reference design geometry
│ deviation heatmap + report
▼
Field display (tablet / AR) ← inspector sees deviation on site
│
▼ (upload report only)
Cloud audit store ← immutable evidence + digital twin update
| Domain | Constraint | How EdgeSentry-Inspect addresses it |
|---|---|---|
| Construction site inspection | Full unit scan-and-verdict within 30 min | Edge-only pipeline; no upload before verdict |
| Maritime structure inspection | Intermittent connectivity; autonomous robot | Local anomaly flag; cloud sync after mission |
| Document | Description |
|---|---|
| Background | Problem, pain points, and how it differs from existing solutions |
| Requirements | Inspection constraints, KPIs, and regulatory context |
| Scenarios | Step-by-step flows, construction and maritime case studies |
| Architecture | Edge-cloud split, AI inference modes, technology choices |
| Roadmap | Milestone plan; links to trilink-core issues for foundation work |
To report a vulnerability privately, use GitHub's private vulnerability reporting. See SECURITY.md for the full disclosure policy, supported versions, response SLAs, and scope.
This project is licensed under either of:
at your option.