Sigil
Sigil is L1fe's blockchain and peer-to-peer infrastructure for high-trust agent evidence. Sigil deployment is for agents that need chain-adjacent or on-chain verification properties: identity anchoring, compact receipts, settlement, or proof submission.
Most Forge agents do not need Sigil. Use it when the business requirement is stronger than ordinary logs and signed audit trails.
What Sigil needs from Forge
Forge contributes:
- OAS identity and lineage
- signed audit entries
- deterministic runtime boundaries where possible
- ACT-scoped tool authority
- WASM-compatible packaging path
- telemetry evidence for replay or verification
What should not be on chain
Keep these off chain unless a specific protocol requires otherwise:
- private keys
- raw prompts containing sensitive data
- provider credentials
- full user data payloads
- large media or vector artifacts
Publish hashes, attestations, or compact evidence where possible.
Readiness rule
Treat Sigil deployment as an L2 runtime target. The agent should already pass the lower-level conformance and release-gate checks before chain integration is considered.