# OpenVerifier v13.9.0-rc3 — licenses and notices

## Operator
OpenVerifier is independently operated and maintained by Louis Clybourn Jr. / Aurifex Inc.

## Compatibility boundary
Compatibility with public EMILIA Protocol artifacts or profiles does not mean EMILIA approval, certification, partnership, endorsement, or a canonical EMILIA Gate deployment.

## Upstream sources
- EMILIA Protocol repository: https://github.com/emiliaprotocol/emilia-protocol — Apache License 2.0.
- Gate Qualification v2: https://github.com/emiliaprotocol/emilia-protocol/blob/main/docs/protocol/gate-qualification-v2.md
- CAID action-type registry source: https://github.com/emiliaprotocol/emilia-protocol/blob/main/caid/registry/action-types.json — registry metadata identifies CC0-1.0. The rc3 exact-action verifier remains pinned to its reviewed local `payment.release.1` definition and does not silently follow upstream registry changes.
- CAID reference implementation: https://github.com/emiliaprotocol/emilia-protocol/blob/main/caid/impl/js/caid.mjs
- The Canonical Action Identifier (CAID), authored by Iman Schrock: https://datatracker.ietf.org/doc/draft-schrock-canonical-action-identifier/ — Internet-Draft / Work in Progress under applicable IETF Trust Legal Provisions. Citation does not imply IETF endorsement.
- ISO 4217 currency-code source: SIX Financial Information AG, Secretariat of the Maintenance Agency for ISO 4217, List One: Current Currency & Funds. The rc3 package preserves the same closed alphabetic-code pin independently reviewed in rc2 for offline membership validation; citation does not imply SIX or ISO endorsement.

## OpenVerifier / SYNC
- OpenVerifier: https://openverifier.org/
- SYNC Intent: https://apps.apple.com/app/id6760578170
- OpenVerifier public-surface material: Copyright © 2026 Aurifex Inc. This deployment bundle does not grant additional license rights beyond those stated by applicable source materials.

## Modification notice for v13.8.3
This public-surface revision changes terminology, attribution, source links, deployment metadata, signer-enrollment status text, and interoperability disclaimers. It does not change verifier decision logic or the reviewed v13.8 ZIP.

Frozen reviewed verifier artifact SHA-256: `e6d2324baf13d09d7c2cee74d905f74230bfddaf3fdcae343661bbeee1d6697d`.

## v13.9.0-rc2 additions
This is a new functional review candidate by Aurifex Inc. New files implement a
narrow native-receipt/action join, local preparation/review tools and tests.
rc2 additionally closes the independent-review currency-enum and ambiguous
SYNC signer-identity findings. It does not change the frozen p3 ZIP or the
separately reviewed v13.8 artifact.
Copyright (c) 2026 Aurifex Inc. No new licensing grant is inferred from this
patch; the original ownership, upstream licence and attribution boundaries
remain in force. No private iOS source is redistributed in this bundle.

The native signing profile was checked against the user-supplied SYNC app source:
CurrentRootView.swift, CurrentReceiptModels.swift, CurrentReceiptExporter.swift,
and SYNCCanonicalReceipt.swift. The new packet format is an OpenVerifier
review-candidate profile, not an EMILIA-published wire standard.


## Exact-action continuity terminology (introduced in rc3)

`Exact-action continuity` is OpenVerifier explanatory language for the verified
relationship between the material action protected by the human-reviewed SYNC
record and the same typed action represented by the signed Gate compatibility
projection. It is not asserted as an EMILIA protocol-state name, certification,
execution authorization, or provider/physical-outcome claim.

## Deployment attestation boundary

The included rc2 deployment-attestation JSON is an exact historical copy of the
separate record whose SHA-256 is
`53d6ba62ace7076bdb11542db79d9849773064aab93ff6072396ce9764c7b8ca`.
The hash identifies the record bytes. The record is unsigned and does not by
itself establish signer provenance or any claim outside its stated deployment
check.

## rc3 release-state completion

rc3 removes mutable package-review status from exact-action verification output
and uses timeless exact-action-continuity result labeling. Review and deployment
state remain separate operational records. Exact-action acceptance/refusal logic
and the stated claim boundary are unchanged.