Standards Alignment Table
How S3 Markets maps to emerging standards requirements
This table summarizes how S3 Markets is designed to support selected expectations from AIM v1.0, ISO 22095-3, and SBTi Corporate Net-Zero Standard v2.0 without making formal certification, endorsement, or approval claims.
| Standard / framework | Requirement or expectation | What it means | How S3 Markets supports it |
|---|---|---|---|
| AIM v1.0 | System of record | Intervention outcomes should be documented in a reliable system of record. | S3 functions as a digital registry for EAC issuance, transfer, allocation, retirement, and substantiation. |
| AIM v1.0 | Registry lifecycle | A registry should govern issuance, transfer, and retirement through defined procedures. | S3 records lifecycle events and creates a structured certificate history from creation through retirement. |
| AIM v1.0 | Documentation and assumptions | Systems of record should preserve key data, assumptions, methods, and evidence. | S3 links EACs to producer, facility, methodology, emissions-intensity, verification, and retirement data. |
| AIM v1.0 | Intervention assurance | Records should reflect the standards, audits, and assurance supporting the intervention. | S3 connects issuance to independent verification materials and supporting documentation. |
| AIM v1.0 | Unique records | Records should not duplicate the same intervention outcome. | S3 uses unique tokenized certificate records and lifecycle controls designed to prevent over-issuance and duplicate record creation. |
| AIM v1.0 | Reporting details | Buyers need registry name, record identifiers, and retirement evidence. | S3 produces unique EAC identifiers and retirement records that can support buyer disclosure and audit workflows. |
| ISO 22095-3 | Book-and-claim model | Administrative record flow can be separated from physical product flow. | S3 enables environmental attributes from low-carbon commodities to be tracked and transferred separately from physical delivery. |
| ISO 22095-3 | Transferable instruments / TIECs | A transferable instrument represents ownership of the right to claim specified characteristics. | S3 EACs are designed to represent defined low-carbon attributes and the right to make associated claims after retirement. |
| ISO 22095-3 | Retirement and end of life | The instrument must have a controlled end-of-life process once used for a claim. | S3 retirement logic makes final use explicit and prevents retired EACs from being transferred or claimed again. |
| ISO 22095-3 | Avoiding double counting | The system should prevent the same attributes from being claimed more than once. | S3 combines issuance controls, certificate uniqueness, contract safeguards, and retirement records to reduce double-counting risk. |
| ISO 22095-3 | Recordkeeping and transparency | The system should maintain reliable records and make relevant information available for review. | S3 maintains lifecycle records, supporting documentation, and auditable evidence for registry events. |
| SBTi CNZS v2.0 | CNZS-C28 | Secure tracking systems for certificate lifecycle | Certificates used for target implementation must move through transparent, secure systems that prevent double counting. | S3 operates a digital certificate registry that records issuance, transfer, allocation, and retirement events with immutable lifecycle history designed to support double-count prevention controls. |
| SBTi CNZS v2.0 | C28.1 | Registry transparency | Issuance, transfer, redemption/cancellation, and retirement must be recorded in a secure registry or equivalent system of record. | S3 maintains auditable event records for each certificate state transition and preserves transaction-level provenance from creation through retirement. |
| SBTi CNZS v2.0 | C25.7 | Unique identification and tracking | Market instruments should be uniquely identified (for example, serialized) and traceable; recognized registries should be used where available. | S3 assigns unique certificate identifiers and enforces one-record-per-instrument lifecycle tracking, with registry interoperability patterns for recognized external systems where required. |
| SBTi CNZS v2.0 | C25.6 | Unique attribution | Claims must remain attributable to the company and avoid over-attribution when more than one actor references the same action. | S3 links certificates to explicit ownership and claim context with retirement evidence, so attribution boundaries and co-claim disclosures are documented and reviewable. |
| SBTi CNZS v2.0 | C27.2 | Volume matching | Certificate volume matched to an activity cannot exceed the underlying activity volume reflected in inventory accounting. | S3 supports quantity-controlled matching workflows and allocation checks that prevent over-allocation of certificates beyond defined activity volumes. |
| SBTi CNZS v2.0 | C27.4 | Attribute preservation | Attributes should follow proportional physical-flow logic and cannot be stacked or concentrated in ways that overstate outcomes. | S3 preserves certificate metadata and transfer logic across lifecycle events to maintain proportional attribute integrity and avoid overstated downstream claims. |
| SBTi CNZS v2.0 | C28.2 | Third-party assurance readiness | Data and calculations supporting conformance should be independently assured where applicable. | S3 keeps structured, exportable audit trails, including certificate data, transfer history, retirement records, and supporting documentation, to facilitate external assurance and evidence review. |
System of record
What it means
Intervention outcomes should be documented in a reliable system of record.
How S3 Markets supports it
S3 functions as a digital registry for EAC issuance, transfer, allocation, retirement, and substantiation.
Registry lifecycle
What it means
A registry should govern issuance, transfer, and retirement through defined procedures.
How S3 Markets supports it
S3 records lifecycle events and creates a structured certificate history from creation through retirement.
Documentation and assumptions
What it means
Systems of record should preserve key data, assumptions, methods, and evidence.
How S3 Markets supports it
S3 links EACs to producer, facility, methodology, emissions-intensity, verification, and retirement data.
Intervention assurance
What it means
Records should reflect the standards, audits, and assurance supporting the intervention.
How S3 Markets supports it
S3 connects issuance to independent verification materials and supporting documentation.
Unique records
What it means
Records should not duplicate the same intervention outcome.
How S3 Markets supports it
S3 uses unique tokenized certificate records and lifecycle controls designed to prevent over-issuance and duplicate record creation.
Reporting details
What it means
Buyers need registry name, record identifiers, and retirement evidence.
How S3 Markets supports it
S3 produces unique EAC identifiers and retirement records that can support buyer disclosure and audit workflows.
Book-and-claim model
What it means
Administrative record flow can be separated from physical product flow.
How S3 Markets supports it
S3 enables environmental attributes from low-carbon commodities to be tracked and transferred separately from physical delivery.
Transferable instruments / TIECs
What it means
A transferable instrument represents ownership of the right to claim specified characteristics.
How S3 Markets supports it
S3 EACs are designed to represent defined low-carbon attributes and the right to make associated claims after retirement.
Retirement and end of life
What it means
The instrument must have a controlled end-of-life process once used for a claim.
How S3 Markets supports it
S3 retirement logic makes final use explicit and prevents retired EACs from being transferred or claimed again.
Avoiding double counting
What it means
The system should prevent the same attributes from being claimed more than once.
How S3 Markets supports it
S3 combines issuance controls, certificate uniqueness, contract safeguards, and retirement records to reduce double-counting risk.
Recordkeeping and transparency
What it means
The system should maintain reliable records and make relevant information available for review.
How S3 Markets supports it
S3 maintains lifecycle records, supporting documentation, and auditable evidence for registry events.
CNZS-C28 | Secure tracking systems for certificate lifecycle
What it means
Certificates used for target implementation must move through transparent, secure systems that prevent double counting.
How S3 Markets supports it
S3 operates a digital certificate registry that records issuance, transfer, allocation, and retirement events with immutable lifecycle history designed to support double-count prevention controls.
C28.1 | Registry transparency
What it means
Issuance, transfer, redemption/cancellation, and retirement must be recorded in a secure registry or equivalent system of record.
How S3 Markets supports it
S3 maintains auditable event records for each certificate state transition and preserves transaction-level provenance from creation through retirement.
C25.7 | Unique identification and tracking
What it means
Market instruments should be uniquely identified (for example, serialized) and traceable; recognized registries should be used where available.
How S3 Markets supports it
S3 assigns unique certificate identifiers and enforces one-record-per-instrument lifecycle tracking, with registry interoperability patterns for recognized external systems where required.
C25.6 | Unique attribution
What it means
Claims must remain attributable to the company and avoid over-attribution when more than one actor references the same action.
How S3 Markets supports it
S3 links certificates to explicit ownership and claim context with retirement evidence, so attribution boundaries and co-claim disclosures are documented and reviewable.
C27.2 | Volume matching
What it means
Certificate volume matched to an activity cannot exceed the underlying activity volume reflected in inventory accounting.
How S3 Markets supports it
S3 supports quantity-controlled matching workflows and allocation checks that prevent over-allocation of certificates beyond defined activity volumes.
C27.4 | Attribute preservation
What it means
Attributes should follow proportional physical-flow logic and cannot be stacked or concentrated in ways that overstate outcomes.
How S3 Markets supports it
S3 preserves certificate metadata and transfer logic across lifecycle events to maintain proportional attribute integrity and avoid overstated downstream claims.
C28.2 | Third-party assurance readiness
What it means
Data and calculations supporting conformance should be independently assured where applicable.
How S3 Markets supports it
S3 keeps structured, exportable audit trails, including certificate data, transfer history, retirement records, and supporting documentation, to facilitate external assurance and evidence review.
SBTi v2 recognizes chain-of-custody models including book-and-claim and mass-balance, subject to integrity guardrails. S3 registry controls are designed to operationalize those guardrails through traceable certificate lifecycle records and claim substantiation artifacts.
Standards alignment descriptions are provided for informational purposes and do not imply certification, endorsement, or approval by any standards body.
We Build Standards Aware Scope 3 Market Infrastructure
S3 Markets helps buyers and producers manage EAC issuance, transfer, retirement, and supporting evidence across hard-to-abate value chains.