--- title: KOURAN Node/Package-Independent SRAM/PHY Boundary Architecture | Garmo Labs url: https://garmolabs.com/ip/kouran-node-package-independent-sram-phy-boundary-architecture-ip-3649 description: Stable SRAM and streaming PHY wrappers isolate KOURAN digital logic from foundry/vendor memory and I/O hard macros so the architecture can target SKY130, N2, 18A-class and package-specific implementations. --- [Ip](https://garmolabs.com/marketplace) › IP-3649 Memory & coherency # KOURAN Node/Package-Independent SRAM/PHY Boundary Architecture Stable SRAM and streaming PHY wrappers isolate KOURAN digital logic from foundry/vendor memory and I/O hard macros so the architecture can target SKY130, N2, 18A-class and package-specific implementations. Source / reference evidence [Request evaluation](https://garmolabs.com/contact?products=ip-ip-3649) KOU Memory & coherency THE TECHNICAL ROLE ## A clear integration boundary. KOURAN Node/Package-Independent SRAM/PHY Boundary Architecture provides the documented physical integration / portability architecture responsibility: Stable SRAM and streaming PHY wrappers isolate KOURAN digital logic from foundry/vendor memory and I/O hard macros so the architecture can target SKY130, N2, 18A-class and package-specific implementations. Evaluate the exact KOURAN-IP-019 implementation and confirm its integration contract before using it inside the target design. 01 Stable SRAM and streaming PHY wrappers isolate KOURAN digital logic from foundry/vendor memory and I/O hard macros so the architecture can target SKY130, N2, 18A-class and package-specific implementations. TECHNICAL OVERVIEW ## The details matter. [Download the product brief](https://garmolabs.com/static/briefs/ip-ip-3649.pdf) Canonical identity IP-3649 Native implementation identity KOURAN-IP-019 Documented responsibility Stable SRAM and streaming PHY wrappers isolate KOURAN digital logic from foundry/vendor memory and I/O hard macros so the architecture can target SKY130, N2, 18A-class and package-specific implementations. Recorded evidence class Source / reference evidence Interface and physical parameters Bound to the selected source/configuration; not inferred from name or family. ### Before integration. KOURAN Node/Package-Independent SRAM/PHY Boundary Architecture provides the documented physical integration / portability architecture responsibility: Stable SRAM and streaming PHY wrappers isolate KOURAN digital logic from foundry/vendor memory and I/O hard macros so the architecture can target SKY130, N2, 18A-class and package-specific implementations. Evaluate the exact KOURAN-IP-019 implementation and confirm its integration contract before using it inside the target design. - Exact implementation and configuration manifest - Documented interfaces and clock/reset contract - Available reference or verification collateral - Recorded physical views where authorized and applicable - Integration acceptance criteria and unresolved gate list The selected release must confirm: - Source/configuration identity - Interface and dependencies - Verification evidence - Process/library where applicable - Authorized package and acceptance criteria Unpublished values are not inferred from family names or architecture targets. [Discuss the integration](https://garmolabs.com/contact?products=ip-ip-3649) Source / reference evidence ## Know the release. Know what it establishes. Service-interface RTL + SKY130/N2/18A flow collateral. This is a controlled-portfolio summary, not a fresh execution of the chip qualification flow. [Explore the evidence center](https://garmolabs.com/evidence) [Qualification record](https://garmolabs.com/qualification/ip-ip-3649) ### Release-specific qualification Evidence shown is our 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 BOUNDARY ARCHITECTURE; HARD MACRO CHARACTERIZATION EXTERNAL A PATH THAT FITS THE PROJECT ## Build with KOURAN Node/Package-Independent SRAM/PHY Boundary Architecture. 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](https://garmolabs.com/contact?products=ip-ip-3649&scope=evaluation) production ### Named-design rights for the agreed qualified release Agree deployment or design rights, deliverables and support. [Discuss this scope](https://garmolabs.com/contact?products=ip-ip-3649&scope=production) custom ### Target integration, verification or physical qualification Define the customer-specific work and acceptance criteria. [Discuss this scope](https://garmolabs.com/contact?products=ip-ip-3649&scope=custom) ## Keep exploring. Memory & coherency [## Physical Actuation Transaction Engine](https://garmolabs.com/ip/physical-actuation-transaction-engine-ip-2019) Atomic multi-actuator prepare/validate/commit/fallback engine Executed digital evidence IP-2019 · Executed digital evidence Memory & coherency [## Reconstructible Memory Controller](https://garmolabs.com/ip/reconstructible-memory-controller-ip-2016) Reconstruction-recipe memory controller with integrity gating Executed digital evidence IP-2016 · Executed digital evidence Memory & coherency [## SONJE Production Multi-Bank Memory Controller Architecture](https://garmolabs.com/ip/sonje-production-multi-bank-memory-controller-architecture-ip-3904) 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. [Talk to Garmo](https://garmolabs.com/contact) [Start exploring](https://garmolabs.com/developers) CANONICAL EVIDENCE RECORD · IP-3649 ### Source / reference evidence Source and/or executable reference evidence is recorded. This does not establish HDL or physical qualification unless separately stated. **Record integrity and qualification boundary**4323067db48a109de9bf33ae86f2006040728971c63c0d7c5321e55b96164310 Evidence ranking for evaluation prioritization; not a probability or certification. [How evidence priority is determined ](https://garmolabs.com/marketplace/evidence)