Ed25519 signing
Persistent local signing supports the v0.8 Design Partner baseline.
SECURITY + THREAT MODEL
Verification is useful only when its limits are explicit.
LoopGrid is designed to preserve the integrity and provenance of captured decision evidence. It does not turn an incorrect AI decision into a correct one, and it does not magically prove that every upstream system was honest.
WHAT LOOPGRID PROVES
Integrity and provenance of captured evidence.
- Protected evidence fields match their signed content commitments.
- Workspace-scoped chain relationships remain continuous for the exported history being verified.
- The evidence was signed by the key expected by the verifier when signer pinning is used.
- Human review, action and outcome events can remain linked to the original decision instead of overwriting it.
- Portable bundles can be checked without trusting the LoopGrid UI.
WHAT LOOPGRID DOES NOT PROVE
Correctness, completeness or legal compliance by itself.
- That the AI decision was correct or fair.
- That every upstream input supplied to LoopGrid was truthful.
- That every consequential action was captured unless the deployment topology enforces capture.
- That an external system performed an action merely because an agent claimed it did; observed-outcome integration matters.
- That using LoopGrid makes a system legally compliant.
TRUST BOUNDARIES
Sign outside the system being attested where the risk requires it.
The strongest deployment places signing keys outside the agent's own control. Out-of-band capture minimizes adoption friction; higher-risk workflows can use an inline policy / human-approval / MCP boundary where bypass risk needs stronger control.
AWS KMS boundary
A managed-signing path exists, but each real KMS/IAM boundary remains a deployment-specific validation item.
Signed checkpoints
Optional RFC 3161 timestamping can add an external time assertion where required.
v0.8 READINESS MATRIX
Say what is validated, and what still needs a pilot.
| Area | Status | Current statement |
|---|---|---|
| PostgreSQL / Docker persistence | Validated baseline | Persistence and restart recovery validated for Design Partner evaluation. |
| Signing-key persistence / chain continuity | Validated baseline | Current local signing path preserves chain continuity across restart. |
| Portable offline verification | Validated baseline | Bundles can be verified outside the running service with signer pinning. |
| OTLP/HTTP interoperability | Validated baseline | v0.8.1 accepts OTLP/HTTP protobuf + JSON, optional gzip, and returns standard OTLP responses. |
| Managed signing / production KMS | Per pilot | Validate the customer's actual KMS/IAM trust boundary before sensitive production use. |
| Timestamp trust | Per pilot | Choose and validate the timestamp authority/trust model for the deployment. |
| Scale / HA / operations | Per pilot | Load, recovery, monitoring, retention and incident controls depend on the environment. |
| Production GA | Not claimed | v0.8 remains a controlled Design Partner release. |