AISS defines the structural identity model for autonomous agents.
The Proof of Continuity Protocol (PCP) is the embedded enforcement mechanism that guarantees identity persistence through deterministic continuity validation.
Open standard for cryptographic audit trails of autonomous AI agents.
AISS defines a cryptographic protocol for creating tamper-proof audit trails of AI agent decisions.
Problem: Agents make critical decisions (trading, medical, autonomous driving) but:
- Logs can be modified
- No proof of authorship
- Vulnerable to quantum attacks
Solution: AISS provides:
- β Cryptographic signatures (Ed25519, Dilithium3)
- β Hash-linked event chains (tamper-proof)
- β Fork detection & resolution
- β Post-quantum security (NIST FIPS 204)
PCP (Proof of Continuity Protocol) implements the continuity enforcement rules defined by AISS. It ensures canonical history selection, fork determinism, and replay protection across distributed agents.
Main document: SPEC.md
Contents:
- Agent Identity (Ed25519, Dilithium3)
- Event Structure (AISS-1.0, AISS-2.0)
- Canonical JSON (RFC 8785)
- Hash Chains (SHA-256)
- Signature Generation & Verification
- Fork Detection & Resolution
- Nonce Management (anti-replay)
- Timestamp Requirements (RFC 3161)
- Security Considerations
- Implementation Guidance
PiQrypt (Python): https://github.com/piqrypt/piqrypt
pip install piqryptimport aiss
# Generate identity
private_key, public_key = aiss.generate_keypair()
agent_id = aiss.derive_agent_id(public_key)
# Sign event
event = aiss.stamp_event(
private_key,
agent_id,
payload={"action": "decision", "confidence": 0.95}
)
# Verify
is_valid = aiss.verify_event(public_key, event)AISS helps meet requirements for:
- SOC2 Type 2 (audit controls)
- ISO 27001 (event logging)
- HIPAA (audit trail, encryption)
- GDPR (transparency, integrity)
- SEC/FINRA (trading audit)
- NIST PQC (post-quantum readiness)
aiss-spec/
βββ SPEC.md # Main specification
βββ schemas/
β βββ aiss-1.0.json # JSON schema (classical)
β βββ aiss-2.0.json # JSON schema (post-quantum)
β βββ aiss1_event.schema.json
β βββ aiss1_identity.schema.json
βββ examples/
β βββ event-simple.json
β βββ event-chain.json
β βββ event-hybrid-pq.json
βββ vectors/
β βββ ed25519-test.json
β βββ dilithium-test.json
βββ README.md
βββ LICENSE
Start with SPEC.md β covers all protocol details.
See examples/ for:
- Simple events
- Event chains
- Hybrid post-quantum signatures
Use test vectors in vectors/ to validate your implementation.
Open an issue or PR if you:
- Find a bug in the spec
- Want to propose an improvement
- Have implementation feedback
| Version | Classical | Post-Quantum | Security |
|---|---|---|---|
| AISS-1.0 | Ed25519 (RFC 8032) | - | 128-bit |
| AISS-2.0 | Ed25519 | ML-DSA-65 (NIST FIPS 204) | 256-bit PQ |
- 2026-2030: AISS-1.0 safe (Ed25519)
- 2030+: Migrate to AISS-2.0 (Dilithium3)
- 2035+: Ed25519 considered obsolete
Recommendation: Start with AISS-1.0, plan AISS-2.0 migration.
Official:
- PiQrypt (Python): https://github.com/piqrypt/piqrypt
Community:
- Add yours! Submit a PR to list your implementation.
Requirements:
- Conformant to SPEC.md
- Pass test vectors
- Open-source (any license)
# Every trade decision = signed event
event = aiss.stamp_event(priv_key, agent_id, {
"event_type": "trade_executed",
"symbol": "AAPL",
"action": "buy",
"quantity": 100
})
# β SEC/FINRA audit trail# Medical diagnosis = signed event
event = aiss.stamp_event(priv_key, agent_id, {
"event_type": "diagnosis",
"condition": "pneumonia",
"confidence": 0.94,
"patient_id_hash": "sha256:..." # HIPAA compliant
})
# β HIPAA audit trail# Driving decision = signed event
event = aiss.stamp_event(priv_key, agent_id, {
"event_type": "driving_decision",
"action": "brake",
"speed_kmh": 60,
"obstacle_detected": true
})
# β Black box for accidents- v1.0 (2026-02): Initial release (Ed25519, hash chains)
- v1.1 (2026-02): Fork resolution, nonce management
- v2.0 (2026-02): Post-quantum hybrid signatures
Backward compatibility: AISS-2.0 implementations MUST support AISS-1.0 events.
- Discussions: GitHub Discussions
- Issues: GitHub Issues
- Email: piqrypt@gmail.com
MIT License β see LICENSE
e-Soleau: DSO2026006483 (INPI, 19/02/2026)
If you use AISS in research or production, please cite:
@techreport{aiss2026,
title = {AISS: Agent Identity \& Signature Standard},
author = {PiQrypt Inc.},
year = {2026},
version = {1.1},
url = {https://github.com/piqrypt/aiss-spec},
note = {e-Soleau: DSO2026006483}
}Making AI Agents Accountable β¨