Documentation Index
Fetch the complete documentation index at: https://docs.manthan.systems/llms.txt
Use this file to discover all available pages before exploring further.
Replay store
Switch from MemoryReplayStore to RedisReplayStore
MemoryReplayStore loses all replay protection state on process restart and does not work across multiple processes. Any duplicate execution that crosses a restart boundary will not be detected.
Key management
Store private keys in a secrets manager - not in source code
Use environment variables or a secrets manager (AWS Secrets Manager, HashiCorp Vault, GCP Secret Manager)
Back up your public key - you need it to verify all historical attestations
AwsKmsSigner from @parmanasystems/execution:
Policy bundles
Compile and sign all policies before deployment
Verify bundle integrity on every deployment
Never modify a policy.json after its bundle has been signed - create a new version instead
Audit persistence
Store attestations in a persistent database
Never delete attestations - they are your audit trail
Store the public key alongside attestations for long-term verification
@parmanasystems/audit-db for PostgreSQL-backed attestation storage with full querying support.
Monitoring and alerting
Alert on governance execution errors - policy not found, invalid signals, replay violations
Alert on
INV-013 replay violations - these may indicate double-submission attacks or misconfigured retry logicMonitor replay store health - if Redis is unavailable, execution will be blocked (fail-closed)
Multi-process deployments
Use RedisReplayStore - MemoryReplayStore does not share state across processes
If using @parmanasystems/server, ensure all instances share the same Redis instance
Verification at read time
Re-verify attestations when reading from the database for compliance-critical operations