Decision envelope
The accountable context around one consequential AI decision or agent action.
DEVELOPER QUICKSTART
Record one consequential decision. Verify the evidence.
LoopGrid is SDK/API-first. Start locally, capture one decision path, export the evidence and verify it outside the application.
01 · INSTALL
Choose an SDK.
Python
pip install loopgrid
TypeScript / JavaScript
npm install @cybertechsoft/loopgrid
The current public release supports local and self-hosted evaluation. Point the SDK at your LoopGrid service; deployment-specific security and operational controls are documented on the Security page.
02 · RECORD
Capture the decision path, not just the model call.
from loopgrid import LoopGrid
grid = LoopGrid(
base_url="http://localhost:8000",
api_key="lg_dev_…"
)
grid.record_decision(
decision_type="customer_refund",
privacy_mode="redacted",
agent={"id": "support-agent-04"},
proposed_action={
"tool": "stripe.refunds.create",
"amount": 720
}
)A production workflow can append policy evaluation, human review, external action and observed outcome as signed history rather than rewriting the original decision.
03 · CORE CONCEPTS
The evidence model.
Append-only events
Reviews, corrections, actions, outcomes and replays are added as new history.
Cryptographic proof
SHA-256 commitments, workspace-scoped chain links and signing protect integrity/provenance.
Privacy modes
FULL, REDACTED and PROOF-ONLY let teams choose how much source data LoopGrid retains.
04 · INTEGRATION PATHS
Use the path that fits the system you already run.
| Path | Use |
|---|---|
| REST | Direct evidence API integration |
| Python SDK | Python services and AI backends |
| TypeScript SDK | Node / TypeScript services |
| OpenTelemetry / OTLP | OTLP/HTTP protobuf + JSON trace ingestion, optional gzip |
| MCP proxy | Evidence around tool calls and higher-risk action boundaries |
| GitHub Actions | Verify exported evidence in CI with signer pinning |
05 · OTLP + CI
Use standard telemetry transport. Verify the result independently.
LoopGrid v0.8.1 accepts OTLP/HTTP binary protobuf or JSON on /v1/traces. Many OpenTelemetry SDKs use http/protobuf by default; JSON remains supported for compatibility.
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://127.0.0.1:8000/v1/traces export OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=http/protobuf export OTEL_EXPORTER_OTLP_TRACES_HEADERS="X-LoopGrid-Key=lg_live_...,X-LoopGrid-Workspace=default"
For CI verification, use the published Marketplace Action against an exported evidence ZIP. Pin an expected public key when signer identity matters.
- uses: actions/checkout@v7
- uses: loopgridio/loopgrid-evidence-verify@v1.0.0
with:
evidence: ./evidence/evidence.zip
trusted-public-key: ./keys/loopgrid-production-public-key.pemVerification establishes integrity/provenance under the expected key for captured records. It does not by itself prove that the underlying decision was correct, that every upstream statement was true, or that capture was complete.
06 · NEXT
Understand the trust boundary before sensitive production use.
Read the public threat model, current readiness matrix and known per-pilot hardening items before treating v0.8 as a production control.