Memory & coherency

SONJE VMOL Metadata Contract

Associates architectural version, domain/permissions/epoch, sharing mode, tier/migration state, ECC/poison/scrub, dirty/persistence and QoS/deadline state with each logical line.

Source / reference evidence
Request evaluation
SONMemory & coherency
THE TECHNICAL ROLE

A clear integration boundary.

SONJE VMOL Metadata Contract provides the documented memory metadata architecture responsibility: Associates architectural version, domain/permissions/epoch, sharing mode, tier/migration state, ECC/poison/scrub, dirty/persistence and QoS/deadline state with each logical line. Evaluate the exact SONJE-IP-003 implementation and confirm its integration contract before using it inside the target design.

01

Associates architectural version, domain/permissions/epoch, sharing mode, tier/migration state, ECC/poison/scrub, dirty/persistence and QoS/deadline state with each logical line.

TECHNICAL OVERVIEW

The details matter.

Download the product brief
Canonical identity
IP-3879
Native implementation identity
SONJE-IP-003
Documented responsibility
Associates architectural version, domain/permissions/epoch, sharing mode, tier/migration state, ECC/poison/scrub, dirty/persistence and QoS/deadline state with each logical line.
Recorded evidence class
Source / reference evidence
Interface and physical parameters
Bound to the selected source/configuration; not inferred from name or family.
Source / reference evidence

Know the release.
Know what it establishes.

docs/ARCHITECTURE.md + rtl/memory/sonje_metadata_table.sv

Source basis: Bible v7.42 VERIFIED V29, IP-3879; 103.4 New canonical SONJE records - 58 net-new identities (table 798, row 4).. 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 / IMPLEMENTATION-BACKED METADATA CONTRACT; EXPANDED TABLE RTL UNEXECUTED

A PATH THAT FITS THE PROJECT

Build with SONJE VMOL Metadata Contract.

Technical scope, rights, support and release configuration are agreed before delivery.

evaluation

Review the exact recorded implementation and agreed test scope

Inspect the named release and establish technical fit.

Discuss this scope
production

Named-design rights for the agreed qualified release

Agree deployment or design rights, deliverables and support.

Discuss this scope
custom

Target integration, verification or physical qualification

Define the customer-specific work and acceptance criteria.

Discuss this scope

Keep exploring.

Memory & coherency

Physical Actuation Transaction Engine

Atomic multi-actuator prepare/validate/commit/fallback engine

Executed digital evidence
IP-2019 · Executed digital evidence
Memory & coherency

Reconstructible Memory Controller

Reconstruction-recipe memory controller with integrity gating

Executed digital evidence
IP-2016 · Executed digital evidence
Memory & coherency

SONJE Production Multi-Bank Memory Controller Architecture

Defines a parameterized banked controller that routes MCD-like line operations to independent banks using the proven line-store contract.

Executed digital evidence
IP-3904 · 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-3879

Source / reference evidence

Source and/or executable reference evidence is recorded. This does not establish HDL or physical qualification unless separately stated.

Source: Bible 7.42 VERIFIED V29 · 103.4 New canonical SONJE records - 58 net-new identities · table 798, row 4.

Record integrity and qualification boundary

b305c20d23fdc876009074ff536e9cd264ad328f97205399177249103d5844a8

Evidence ranking for evaluation prioritization; not a probability or certification.

How evidence priority is determined ↗