evaluation
Review the exact recorded implementation and agreed test scope
Inspect the named release and establish technical fit.
Discuss this scopeSecurity & cryptography
SONJE-P64 PASID / IOMMU / Authority-Version-Lock Access Guard RTL
Enforces PASID, domain, epoch, permission, expected-version and lock eligibility together at P64 memory acceptance.
Executed digital evidence
SONSecurity & cryptography
THE TECHNICAL ROLE
A clear integration boundary.
SONJE-P64 PASID / IOMMU / Authority-Version-Lock Access Guard RTL provides the documented memory security rtl responsibility: Enforces PASID, domain, epoch, permission, expected-version and lock eligibility together at P64 memory acceptance. Evaluate the exact SONJE-P64-IP-004 implementation and confirm its integration contract before using it inside the target design.
01
Enforces PASID, domain, epoch, permission, expected-version and lock eligibility together at P64 memory acceptance.
FUNCTION AT A GLANCE
SONJE-P64 PASID / IOMMU / Authority-Version-Lock Access Guard RTL
01
Enforces PASID, domain, epoch, permission, expected-version and lock eligibility together at P64 memory acceptance.
Documented function grouping, not a wiring diagram, interface contract or physical layout. Confirm the selected release before integration.
Explore related engineering tasks ↗TECHNICAL OVERVIEW
Download the product briefThe details matter.
- Canonical identity
- IP-3938
- Native implementation identity
- SONJE-P64-IP-004
- Documented responsibility
- Enforces PASID, domain, epoch, permission, expected-version and lock eligibility together at P64 memory acceptance.
- Recorded evidence class
- Executed digital evidence
- Interface and physical parameters
- Bound to the selected source/configuration; not inferred from name or family.
Executed digital evidenceKnow the release.
Know the release.
Know what it establishes.
rtl/p64/security/sonje_p64_access_guard.sv + formal/p64 access proof + P64 evidence
Source basis: Bible v7.42 VERIFIED V29, IP-3938; 104.6 New canonical SONJE-P64 records - 17 net-new implementation identities (table 801, row 5).. This is a controlled-portfolio summary, not a fresh execution of the chip qualification flow.
Release-specific qualification
Evidence shown is the Bible record for this canonical implementation, not a fresh tool rerun. External foundry acceptance, silicon measurements, standards certification and unlisted interface/physical parameters are not inferred. Exact delivery and rights are agreed before licensing.
Canonical record: P1 / 128-CASE LOCAL MATRIX PASS + SAT GATE OBSERVED PASS
A PATH THAT FITS THE PROJECT
Build with SONJE-P64 PASID / IOMMU / Authority-Version-Lock Access Guard RTL.
Technical scope, rights, support and release configuration are agreed before delivery.
production
Named-design rights for the agreed qualified release
Agree deployment or design rights, deliverables and support.
Discuss this scopecustom
Target integration, verification or physical qualification
Define the customer-specific work and acceptance criteria.
Discuss this scopeKeep exploring.
Security & cryptography
Chiplet Admission Firewall
Chiplet admission, quarantine and trust-boundary engine
Executed digital evidenceIP-2014 · Executed digital evidence
Security & cryptography
SONJE Memory-Fabric Authority / Epoch Enforcement Architecture
Checks requesting domain, read/write permission masks and revocation epoch at the point where memory work is accepted.
Executed digital evidenceIP-3895 · Executed digital evidence
Security & cryptography
ORAX Trust FW-100
Trust/security product
Executed digital evidenceIP-2000 · Executed digital evidence
Your next big idea.
Let’s build it together.
Start with a chip, a software release or a single IP block.
CANONICAL EVIDENCE RECORD · IP-3938How evidence priority is determined ↗
Executed digital evidence
Executed digital verification and/or synthesis are recorded for this implementation; physical qualification is a separate gate.
Source: Bible 7.42 VERIFIED V29 · 104.6 New canonical SONJE-P64 records - 17 net-new implementation identities · table 801, row 5.
Record integrity and qualification boundary
0e275f8371512b6083f6c87a176b3389f1b2175f34087babeaf290e3d0beb8b0
Evidence ranking for evaluation prioritization; not a probability or certification.