01 · Capture
Your application supplies the record.
Send the decision, its reason and relevant input references. Keep the context you need for a later review.
How it works
Capture. Seal. Inspect.
02 · Seal
BuildSeal signs the captured version.
The record is hashed and signed. A record ID connects it to the evidence workflow and its verification link.
03 · Inspect
A reviewer checks the evidence.
Open the link to inspect package integrity, signature, timestamp and record-binding results. Signer trust is shown separately.
Try the real service
See a record before integrating.
Explore a live memory write or create a record for a small file. Each flow links to the service records behind the result.
Live decision memory
A decision, a guess and a cancellation.
See whether a firm decision is recorded, a tentative input preserves it and a cancellation links to its replacement.
Supported cache-rule scenario; real model calls and service records.
Live file record
Keep a reference to an exact file version.
Select a small file, create its fingerprint receipt and inspect the returned proof.
BuildSeal
LIVE FILE RECORD
Try it with a file version.
Create a real record for a file version, then inspect the checks reported by the service.
Verification scope
Clear evidence. Explicit limits.
What the record can support
- Detect changes to the captured content through hash checks.
- Check a signature against the signing key.
- Inspect the reported timestamp and record-binding checks.
- Give a reviewer a stable reference to the recorded version.
What it does not establish
- That a statement is true or a decision is correct.
- That an external action happened as described.
- That a signer is trusted merely because its signature is valid.
- That a chain of records was checked by the public lookup.
The hosted page displays service-reported checks. Independent package verification requires a compatible verifier and an expected signer key.
Logging requirements and official references
Requirements depend on the system and its role. A signed record alone does not establish regulatory compliance. Refer to the European Commission for the current AI Act implementation timeline.
European Commission · Official implementation timeline ↗ · AI Omnibus · Official update ↗
Pilot access
Bring one decision flow.
Tell us what your application decides, what evidence it captures and who needs to review it. We can discuss the record format, access and verification scope for a pilot.
Pilot access is arranged directly. Self-service accounts and API-key issuance are not yet available.
Advanced architecture
Records across memory writes and agent handoffs.
Explore the deeper mechanisms: recorded context and memory (VEDM), evidence assessment for write authority (A10), and commitment outcomes with separate proof finalization (A9).
Developer entry point
Connect your application.
Send decision records from your server. Use the live request below to inspect the API contract and its actual response.
Access and deployment details
Keep API keys on your server. The browser demonstration uses a fixed demo actor. Configure storage, access, retention and sharing before submitting sensitive data.