Verification register Security & Identity
Current reading
Readiness band and full integer triple
AI-assisted assembly · derived results
Readiness band
Ready
Primary summary from verified readiness
- Confidence
- 82% · stale
- Computed at
- 2026-10-09T21:13:08.600738+00:00
- Claimed
- 55
- Reported
- 55
- Verified
- 55
- Gap
- 0
Public ambition and stated capability
Observed practitioner reporting
Independently supported evidence
Claimed and verified align
Evidence strength Strong
Decision
What the current evidence supports
Agent-assisted assessment · independently reviewed · 2026-10-09
Use Era conditionally for existing integrations; evaluate the announced transition before starting a long-lived deployment.
- Why
- Production operation is established, but EraVM retirement, privileged upgrades and incomplete current-version assurance create material operational dependencies.
- Next
- Follow Era-specific migration instructions, validate application compatibility and withdrawal behavior, and review audits matching the deployed protocol.
Constraints
Blockers
- EraVM retirement requires application-specific migration planning.
- Emergency upgrades can bypass the normal exit window.
- Permissioned sequencing and batch approval create censorship and availability dependencies.
- Historical audits do not establish correctness of every current upgrade.
- Delayed code publication limits immediate independent inspection.
Evidence summary
Derived counts
AI-assisted assembly
- Total
- 10
- Tier 1
- 7
- Tier 2
- 3
- Tier 3
- 0
- Supports
- 3
- Contradicts
- 4
- Context
- 3
- Latest observed
- 2026-09-04
Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.
Publication record
Revisions
Revision 3
- 2026-08-20 Reading moved from ready to ready.
- 2026-09-22 Reading moved from ready to ready.
- 2026-09-30 Reading moved from ready to ready.