ap2_mandate_verifier 0.1.0 → 0.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +109 -63
- data/docs/SUPPORT_CONTRACT.md +17 -1
- data/lib/ap2_mandate_verifier.rb +3 -0
- metadata +4 -3
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: fa2ea5451e11d660fac34e24d6ceb56364f40e35cceab36e1c07d065eee5c39b
|
|
4
|
+
data.tar.gz: 52a9bbc66525cff272c186da35fb1f3441d886a973a0e6c292477cff1ab3f61f
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: bfadcb64ea84e9215ed19936468894d93015c89961aad6a912acb780ab8c7d27902dcd5acf664d79700d50054341a957a573a91e172a45bd61f246df468a9d59
|
|
7
|
+
data.tar.gz: a39f11ead57b553dcf8c2b4b8dcba57ae2a0309d4183ecad9a7607988f2593fcdbe577ae81d9caf2b3232b62b2cc7f8d80471e40cbe025ffe7c658cb6b31010a
|
data/README.md
CHANGED
|
@@ -1,61 +1,93 @@
|
|
|
1
|
-
# AP2 Mandate Verifier — 0.
|
|
1
|
+
# AP2 Mandate Verifier — 0.2.0 release preparation
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
[Japanese / 日本語](README.ja.md)
|
|
4
4
|
|
|
5
5
|
A Rails-independent Ruby Gem for a deliberately fixed AP2 verification profile. **A valid signature alone never authorizes a purchase.** Successful checks produce immutable Evidence; the Host makes the final business decision.
|
|
6
6
|
|
|
7
|
-
##
|
|
7
|
+
## Start with the local demo
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
The [AP2 Mandate Verifier Demo](https://github.com/cuichangquan/ap2-mandate-verifier-demo) calls the real verifier on synthetic valid, tampered and expired examples, with Docker local-startup instructions; it is not a hosted demo site, production payments or Host authorization.
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
For a Japanese walkthrough of the three demo scenarios, see the [Zenn article](https://zenn.dev/ccq/articles/7f9643f96fe5c7).
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
## Choose your starting point
|
|
14
14
|
|
|
15
|
-
|
|
15
|
+
| Route | Start here |
|
|
16
|
+
| --- | --- |
|
|
17
|
+
| Docker demo: compare three synthetic cases | Follow the [demo README](https://github.com/cuichangquan/ap2-mandate-verifier-demo#readme) for local startup and valid / tampered / expired examples. Docker commands are maintained there. |
|
|
18
|
+
| Ruby without the demo: existing MRI 4.0.9 | Follow [installation](#distribution-and-installation), then the [saved synthetic example](#try-the-saved-synthetic-example) below. |
|
|
19
|
+
|
|
20
|
+
Both routes use the fixed-profile verifier, not payment execution or Host authorization. See the [supported contract](#supported-contract) for the scope. The goal is to make the choices understandable in about five minutes, not to promise a five-minute installation or build.
|
|
21
|
+
|
|
22
|
+
## Distribution and installation
|
|
23
|
+
|
|
24
|
+
[0.1.0 is published on RubyGems](https://rubygems.org/gems/ap2_mandate_verifier/versions/0.1.0). This is the fixed-profile, verifier-only stable release; the research prerelease pre3 is a separate artifact.
|
|
25
|
+
|
|
26
|
+
Use an existing MRI 4.0.9 environment and your chosen Gem isolation. Normal installation may fetch dependencies and build JSON native extensions. Stop on conflicts or unknown providers rather than relaxing pins.
|
|
16
27
|
|
|
17
28
|
```sh
|
|
18
29
|
ruby --version # MRI 4.0.9 required
|
|
19
30
|
gem install ap2_mandate_verifier --version 0.1.0
|
|
20
31
|
```
|
|
21
32
|
|
|
22
|
-
Bundler
|
|
33
|
+
Bundler Gemfile:
|
|
23
34
|
|
|
24
35
|
```ruby
|
|
25
36
|
gem "ap2_mandate_verifier", "= 0.1.0"
|
|
26
37
|
```
|
|
27
38
|
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
Bundler4.0.20は既存resolver基準でruntime依存ではありません / Bundler4.0.20 is the observed resolver baseline, not a runtime dependency.
|
|
31
|
-
RubyGemsの版制約だけではMRI engine、OSや実native/providerの出所を保証しません / Gem version constraints alone do not enforce the MRI engine, OS or native-provider provenance.
|
|
39
|
+
Fixed runtime dependencies: JSON 2.19.9, JWT 3.3.0, base64 0.3.0, OpenSSL gem 4.0.2 and Digest 3.2.1.
|
|
40
|
+
Bundler 4.0.20 is the observed resolver baseline, not a runtime dependency. Gem version constraints alone do not enforce the MRI engine, OS or native-provider provenance.
|
|
32
41
|
|
|
33
|
-
##
|
|
42
|
+
## Verification APIs: published 0.1.0 and unreleased 0.2.0
|
|
34
43
|
|
|
35
|
-
|
|
36
|
-
- ES256/P256、Open1→Closed1、固定3開示位置、単一Merchant/SKU/行、USD/EUR/JPY、empty links。未知/非対応形式は拒否 / ES256/P256, Open1→Closed1, three fixed disclosure positions, one Merchant/SKU/line, USD/EUR/JPY and empty links; unknown/unsupported forms are rejected.
|
|
37
|
-
- 厳格入力と有限上限、供給trust選択、Root原文署名と全域閉包、Agent/Merchant署名・委任・購入/Host binding、型/制約/期限をGemが検査 / The Gem checks strict bounded inputs, supplied trust selection, signed Root wire and full supported closure, Agent/Merchant signatures, delegation, purchase/Host binding, types, constraints and time.
|
|
38
|
-
- 入口は既存 `verify_research`。名前と `verified_research/scoped_research_verified`・Evidence v2契約を維持。安定版番号でも一般AP2対応やHost許可へ昇格しない / The existing entry, result names and Evidence v2 contract remain unchanged; a stable version does not imply generic AP2 support or Host authorization.
|
|
44
|
+
**The commands and saved example below remain the published 0.1.0 route using `verify_research`.** Repository metadata is now a 0.2.0 release candidate, with `verify_checkout` as its recommended full entry. This documentation does not announce a 0.2.0 publication or provide a registry installation command for it; installing 0.1.0 does not provide this method.
|
|
39
45
|
|
|
40
|
-
|
|
46
|
+
| Entry | Availability and contract |
|
|
47
|
+
| --- | --- |
|
|
48
|
+
| `verify_checkout(**inputs)` | Recommended full-verification entry for unreleased v0.2.0 source. Delegates directly to `ResearchResult.verify` without changing inputs or the verification pipeline. |
|
|
49
|
+
| `verify_research(**inputs)` | Full-verification entry in published 0.1.0; retained unchanged in v0.2.0, without a deprecation warning. |
|
|
50
|
+
| `verify(presentation_json:)` | Existing JSON syntax check only. Valid JSON returns `:unverified` / `:verification_not_implemented`, never successful Evidence. It is not a substitute for full verification. |
|
|
41
51
|
|
|
42
|
-
|
|
52
|
+
For a separately validated 0.2.0 candidate installation, replace only the call in the saved example with the recommended entry below. All seven values come from that example's `full` object; real integrations must supply the authenticated Host inputs described below. Use a registry install route only after publication is confirmed:
|
|
43
53
|
|
|
44
|
-
|
|
54
|
+
```ruby
|
|
55
|
+
result = AP2MandateVerifier.verify_checkout(
|
|
56
|
+
trust_json: full.fetch("trust_json"),
|
|
57
|
+
selection_json: full.fetch("selection_json"),
|
|
58
|
+
host_json: full.fetch("host_json"),
|
|
59
|
+
root_presentation: full.fetch("root_presentation"),
|
|
60
|
+
terminal_jws: full.fetch("terminal_jws"),
|
|
61
|
+
host_checkout_jws: full.fetch("host_checkout_jws"),
|
|
62
|
+
verified_at: full.fetch("verified_at")
|
|
63
|
+
)
|
|
64
|
+
```
|
|
45
65
|
|
|
46
|
-
|
|
66
|
+
Both full-verification entries require all seven inputs listed under [responsibility boundaries](#real-inputs-and-responsibility-boundaries): six original Strings and externally supplied integer Unix seconds. Seven inputs and seven supported shapes are different concepts. Neither entry broadens the fixed profile below or supplies missing trust, Host state or time. Missing or unknown keywords return `:unavailable` / `:research_verification_unavailable`, with `success? == false` and `evidence == nil`; positional arguments or invalid keyword expansion can raise before verification begins.
|
|
47
67
|
|
|
48
|
-
|
|
68
|
+
The [result handling](#understanding-the-result) is unchanged: success remains `ResearchResult` with `:verified_research` / `:scoped_research_verified` and immutable Evidence v2; rejected and unavailable results have no Evidence. Evidence is checked facts, **not purchase authorization**. Exceptions or missing results must also stop the caller. See the [API migration plan](docs/V0_2_0_API_PLAN.md) for design history; its earlier implementation gates do not describe the published 0.1.0 artifact or replace this availability distinction.
|
|
49
69
|
|
|
50
|
-
Supported
|
|
70
|
+
## Supported contract
|
|
71
|
+
|
|
72
|
+
- AP2 pinned source `b4587ac1d055888a73b4b21750973cffba961793`, registered profile `ap2.checkout.single_merchant_sku` v1: exact body/hash and seven supported shapes.
|
|
73
|
+
|
|
74
|
+
- ES256/P256, Open1→Closed1, three fixed disclosure positions, one Merchant/SKU/line, USD/EUR/JPY and empty links; unknown/unsupported forms are rejected.
|
|
51
75
|
|
|
52
|
-
|
|
76
|
+
- The Gem checks strict bounded inputs, supplied trust selection, signed Root wire and full supported closure, Agent/Merchant signatures, delegation, purchase/Host binding, types, constraints and time.
|
|
53
77
|
|
|
54
|
-
|
|
78
|
+
- Both full-verification entries above preserve `verified_research` / `scoped_research_verified` result names and the Evidence v2 contract; a stable version does not imply generic AP2 support or Host authorization.
|
|
79
|
+
|
|
80
|
+
See [SUPPORT_CONTRACT](docs/SUPPORT_CONTRACT.md) for exact required shapes, bounds and failure codes.
|
|
81
|
+
|
|
82
|
+
## Environment, compatibility and maintenance
|
|
83
|
+
|
|
84
|
+
The baseline is MRI 4.0.9 with fixed dependencies and the exact observed MBA/macOS arm64 and Ubuntu 24.04/x86_64 configurations. Distinguish [release-package/provider evidence](research/stable010_release_linux_package/README.md) from [historical environment records](docs/VERIFIER_CORE_COMPLETION_CRITERIA.md#初回の対応環境保証範囲owner採用済み). Other OS versions, engines, architectures and arbitrary provider updates are not covered.
|
|
85
|
+
|
|
86
|
+
Supported-input semantics and APIs do not change silently. Security-driven narrowing identifies reason, impact and migration; breaking API/required-field/profile changes are explicit. Dependency updates are not automatically compatible.
|
|
55
87
|
|
|
56
|
-
|
|
88
|
+
Maintenance covers the latest patch in the initial stable series, with manual monthly/advisory/pre-release review. No old-series backport, fixed support term, response/fix deadline or 24/7 promise. See [SECURITY](SECURITY.md) and [maintenance](docs/POST_RELEASE_MAINTENANCE.md); never report private keys, real Mandates or personal data.
|
|
57
89
|
|
|
58
|
-
|
|
90
|
+
## Try the saved synthetic example
|
|
59
91
|
|
|
60
92
|
This example reads the same public `FULL` input used by the successful installed-Gem checks. The input JSON is not packaged in the Gem. Fetch it from the pinned commit and verify its SHA256 first. It contains no private keys. Its trust/Host assertions are **synthetic test data**, not real Issuer enrollment, a current order or a live clock. `verified_at = 1800000000` is the saved scenario's fixed evaluation time.
|
|
61
93
|
|
|
@@ -100,66 +132,80 @@ else
|
|
|
100
132
|
end
|
|
101
133
|
```
|
|
102
134
|
|
|
103
|
-
この保存 `FULL` ケースの期待値は `status=:verified_research`、`code=:scoped_research_verified`、`success?=true` です。実入力・不支持入力・依存障害では同じ結果を期待しません。非成功ならEvidenceはnilです。例外やプロセス終了で結果がない場合も停止してください。Evidence全体やraw入力を安易にログへ出さないでください。
|
|
104
|
-
|
|
105
135
|
For this saved `FULL` case, the expected result is `status=:verified_research`, `code=:scoped_research_verified`, `success?=true`. This is not the expected outcome for arbitrary real inputs, unsupported forms or dependency failures. Non-success results have nil Evidence. Exceptions or process termination without a result must also stop the caller. Avoid logging complete Evidence or raw inputs.
|
|
106
136
|
|
|
107
|
-
##
|
|
137
|
+
## Understanding the result
|
|
108
138
|
|
|
109
|
-
|
|
|
110
|
-
| --- | --- |
|
|
111
|
-
|
|
|
112
|
-
| `
|
|
113
|
-
| `
|
|
114
|
-
| `root_presentation` | disclosure順と末尾`~`を維持した署名付きRoot提示原文String / Original signed Root presentation String, preserving disclosure order and trailing `~`. |
|
|
115
|
-
| `terminal_jws` | Agent terminal compact JWS原文String / Original Agent terminal compact JWS String. |
|
|
116
|
-
| `host_checkout_jws` | Hostが固定したMerchant Checkout compact JWT原文String / Original Merchant Checkout compact JWT String frozen by the Host. |
|
|
117
|
-
| `verified_at` | 外部の信頼時計から供給する整数Unix秒 / Integer Unix seconds supplied by an external trusted clock. |
|
|
139
|
+
| Outcome | `status` and predicate | Evidence and handling |
|
|
140
|
+
| --- | --- | --- |
|
|
141
|
+
| Successful scoped verification | `:verified_research`; `success? == true`; `code == :scoped_research_verified` | Present: checked facts, **not purchase authorization**. Host responsibilities still apply. |
|
|
142
|
+
| Rejected | `:rejected`; `rejected? == true` | Absent (`nil`). Stop; inspect `result.code` for the rejection reason. |
|
|
143
|
+
| Verification unavailable | `:unavailable`; `unavailable? == true` | Absent (`nil`). Stop; a dependency or verification failure does not by itself establish that the input is invalid. |
|
|
118
144
|
|
|
119
|
-
|
|
145
|
+
An exception, process termination or missing result must also stop the caller without authorizing a purchase. The example above deliberately stops on every non-success result. See [Result and Evidence](docs/SUPPORT_CONTRACT.md#result-and-evidence) for details.
|
|
120
146
|
|
|
121
|
-
|
|
147
|
+
## Real inputs and responsibility boundaries
|
|
122
148
|
|
|
123
|
-
|
|
149
|
+
| Keyword | Input contract |
|
|
150
|
+
| --- | --- |
|
|
151
|
+
| `trust_json` | Original JSON String for authenticated Host trust snapshot, profile and public-key registration. |
|
|
152
|
+
| `selection_json` | Independently selected tenant, profile version and role/identity/purpose/key references. |
|
|
153
|
+
| `host_json` | Authenticated current order binding, issued challenge, expected issuer and clock identity. |
|
|
154
|
+
| `root_presentation` | Original signed Root presentation String, preserving disclosure order and trailing `~`. |
|
|
155
|
+
| `terminal_jws` | Original Agent terminal compact JWS String. |
|
|
156
|
+
| `host_checkout_jws` | Original Merchant Checkout compact JWT String frozen by the Host. |
|
|
157
|
+
| `verified_at` | Integer Unix seconds supplied by an external trusted clock. |
|
|
124
158
|
|
|
125
|
-
|
|
159
|
+
See [SUPPORT_CONTRACT](docs/SUPPORT_CONTRACT.md#full-entry-and-required-inputs) for exact required shapes, types and limits. Do not register trust from the presented token or parse/re-encode/reorder signed wire input. Matching Host-only Buyer/account fields does not establish Issuer-signed identity authentication.
|
|
126
160
|
|
|
127
|
-
|
|
161
|
+
A successful result from either full-verification entry establishes scoped verification facts. The Host still must recheck latest trust/revocation/order version/challenge/time and atomically consume the nonce with order CAS. The Gem does not perform those operations. Serializing Evidence to JSON does not preserve or reconstruct authenticity through this API. Legacy `verify(presentation_json:)` checks only the JSON syntax boundary and never returns successful Evidence.
|
|
128
162
|
|
|
129
163
|
Before integration, consult the [Issuer onboarding checklist](docs/ISSUER_ONBOARDING_CHECKLIST.md) and [Issuer/Host minimum contract](docs/ISSUER_HOST_MINIMUM_CONTRACT.md). Real-Issuer trust and a specific Host's production GO are not established by this Gem version or verification success. The contract and Host/DB code under `research/` describe synthetic research designs and limited observations, not a production adapter.
|
|
130
164
|
|
|
131
|
-
`
|
|
132
|
-
host_checkout_jws/verified_atです。前3つのJSONは認証済みの独立Host入力として渡し、
|
|
133
|
-
提示tokenの自己申告から信頼を追加しません。raw nonceは入力専用、EvidenceにはSHA256だけを
|
|
134
|
-
投影します。Hash/JSONへ書き出したものを真正なEvidenceとして再入力するAPIはありません。
|
|
135
|
-
|
|
136
|
-
旧`verify`はJSON構文境界だけで、その他の低レベルverify入口と共にsuccess?=false/
|
|
137
|
-
evidence=nilを維持します。呼出し例のsuccess?を旧APIへ流用してはいけません。
|
|
165
|
+
Raw nonce values are input-only; Evidence projects their SHA256. Other low-level verification entries also keep `success?=false` and `evidence=nil`; do not apply the successful example to those entries.
|
|
138
166
|
|
|
139
|
-
##
|
|
140
|
-
|
|
141
|
-
一般AP2/全Schema、任意の実Issuer互換性、発行/提示/Receipt生成、Rails adapter、実決済、実Host/DB/失効運用、最悪CPU/RSS/並行性能・数値SLAは対象外です。無欠陥や全パス安全性を証明したとは主張しません。既知重大問題やGem自身の検査欠落をこの非保証表示で補いません。
|
|
167
|
+
## Exclusions and safe stopping
|
|
142
168
|
|
|
143
169
|
General AP2/full Schema, arbitrary real-Issuer interoperability, issuance/presentation/Receipt generation, Rails adapters, real payments/Host/DB/revocation operations, worst CPU/RSS/concurrency and numerical SLAs are outside scope. No defect-free/all-path safety proof is claimed; exclusions do not excuse known major defects or missing Gem checks.
|
|
144
170
|
|
|
145
|
-
Hostはtokenから独立した認証済みtrust/鍵/profile・最新失効/時計/注文/challengeを供給し、Evidence使用直前に再照合し、nonce原子消費＋注文CAS・PENDING回復・最終ALLOWを担当します。Gemの既存検査をHostへ移す意味ではありません。Evidenceは同一の信頼Rubyプロセス内の検査事実で、JSON/Hashから真正性を再構成しません。不明・拒否・不能・例外・結果なしは許可せず、Hostが外側の時間/メモリ/同時実行制限を設けます。
|
|
146
|
-
|
|
147
171
|
The Host supplies authenticated token-independent trust/keys/profile and current revocation/clock/order/challenge state, rechecks before use, atomically consumes nonce with order CAS, reconciles PENDING and decides ALLOW. Existing Gem checks remain Gem responsibilities. Evidence is in-process checked facts in trusted Ruby, not a transport credential. Unknown/rejected/unavailable/exception/missing results never authorize; the Host provides outer time/memory/concurrency limits.
|
|
148
172
|
|
|
149
|
-
##
|
|
173
|
+
## Evidence and history
|
|
174
|
+
|
|
175
|
+
A prior 0.2.0 candidate passed the limited Debian 12/arm64 packaging observation recorded in [PR #213](https://github.com/cuichangquan/ap2-mandate-verifier/pull/213): 13 payload files matched source/archive/installation, 10 product Ruby files loaded normally and 118 installed cases passed. This adds an observation, not a supported-platform guarantee. README.md and SUPPORT_CONTRACT are packaged; these documentation changes require a new artifact and separately approved build/install/13-payload/10-loaded/118-case validation. That final candidate is NOT_RUN. Prior 190/885 source checks were not rerun in the packaging attempt; publication remains a separate decision.
|
|
150
176
|
|
|
151
|
-
|
|
177
|
+
The published 0.1.0 archive is **34,304 bytes**, SHA256 `37b2a235b6fab2d9d9765ae985dd9db27afd3b2c5407fe263a6b65314550db32`. Official metadata, owner `cuichangquan`, downloaded distribution bytes and all 13 payload hashes were checked on 2026-10-26. See the [publication record](research/stable010_release_linux_package/README.md#rubygems-publication-verified). This repository README was reorganized after publication and differs from the packaged README; the published archive was not rebuilt.
|
|
152
178
|
|
|
153
179
|
See the [versioned validation record](research/stable010_release_linux_package/README.md) for this archive's external SHA, per-environment observations and limits. The archive hash is kept outside its payload to avoid self-reference. A hash identifies bytes, not Host trust or global safety.
|
|
154
180
|
|
|
155
|
-
[
|
|
181
|
+
[Earlier 0.1.0 candidate R1](research/stable010_candidate/README.md), [published pre3](https://rubygems.org/gems/ap2_mandate_verifier/versions/0.1.0.pre.3) and [pre2 Release](https://github.com/cuichangquan/ap2-mandate-verifier/releases/tag/v0.1.0.pre.2) are different archives. Historical NOT_RUN/stops/passes remain tied to their original bytes and time. Reusing 885 regressions (including 147) and Ruby4.0.1 independent comparisons is not a fresh 885 run or Linux independent Oracle.
|
|
156
182
|
|
|
157
|
-
[
|
|
183
|
+
[Historical research documentation](https://github.com/cuichangquan/ap2-mandate-verifier/blob/2546d112b4bd4eaaf0a55b502f1c40b1fd61be65/README.md#research-documentation) does not override the current contract or release status. Future SDK plans are described in [PRODUCT_VISION](docs/PRODUCT_VISION.md).
|
|
158
184
|
|
|
159
|
-
|
|
185
|
+
## Illustrated concepts (Japanese diagrams)
|
|
160
186
|
|
|
161
|
-
|
|
187
|
+
These existing diagrams contain Japanese text and illustrate broader AP2 concepts, not the exact fixed-profile implementation contract. The fixed-profile contract above takes precedence. Issuer trust and current revocation are supplied and maintained by the Host; the Gem does not independently establish live external trust or revocation. Arbitrary chains, issuance, Payment Mandates and payment execution shown conceptually are not supported features of this release.
|
|
162
188
|
|
|
163
|
-
|
|
189
|
+
### AP2 overview (Japanese)
|
|
164
190
|
|
|
191
|
+
|
|
165
192
|
|
|
193
|
+
### Delegation and Host responsibility boundaries (Japanese)
|
|
194
|
+
|
|
195
|
+
|
|
196
|
+
|
|
197
|
+
### Mandate anatomy (Japanese)
|
|
198
|
+
|
|
199
|
+
|
|
200
|
+
|
|
201
|
+
### SD-JWT and delegation concepts (Japanese)
|
|
202
|
+
|
|
203
|
+
|
|
204
|
+
|
|
205
|
+
### Fail-closed attack patterns and Host replay prevention (Japanese)
|
|
206
|
+
|
|
207
|
+
|
|
208
|
+
|
|
209
|
+
## License
|
|
210
|
+
|
|
211
|
+
MIT. See [LICENSE](LICENSE).
|
data/docs/SUPPORT_CONTRACT.md
CHANGED
|
@@ -1,10 +1,26 @@
|
|
|
1
|
-
# Fixed-profile AP2 verification — 0.1.0
|
|
1
|
+
# Fixed-profile AP2 verification — 0.1.0 baseline / 0.2.0 candidate
|
|
2
2
|
|
|
3
3
|
**Fixed-profile verification contract; Evidence is not Host ALLOW or payment permission.**
|
|
4
4
|
Distribution availability is determined by the official RubyGems version listing, not by this document. Specific Host production GO remains separate.
|
|
5
5
|
Owner adopted the existing verification API and bounded stable-release conditions below. Publication and a specific Host's production operation are separate decisions; this contract does not authorize either.
|
|
6
6
|
Published research-only pre3 remains unchanged. Its historical observations below do not certify this new archive.
|
|
7
7
|
|
|
8
|
+
## Unreleased 0.2.0 candidate API addition
|
|
9
|
+
|
|
10
|
+
Repository candidate metadata is 0.2.0; this is not a publication or validated-archive claim. Published 0.1.0 and its historical evidence below remain unchanged. The initial source-only NOT_RUN record was followed by the limited candidate observation below; it does not validate later packaged-document changes.
|
|
11
|
+
|
|
12
|
+
`verify_checkout(**inputs)` delegates directly to `ResearchResult.verify(**inputs)` without input transformation. It requires the same seven inputs listed below (six original Strings and externally supplied integer Unix seconds), fixed profile, bounds and trusted Host preconditions. `verify_research` is retained unchanged without deprecation warnings; `verify(presentation_json:)` remains syntax-only and never produces successful Evidence.
|
|
13
|
+
|
|
14
|
+
Both full entries preserve Result/ResearchResult, status/code and immutable Evidence v2. Missing or unknown keywords return `:unavailable` / `:research_verification_unavailable`, `success? == false`, `evidence == nil`. Positional arguments or invalid keyword expansion can raise before entry; exceptions and missing results never authorize an operation. Success remains `:verified_research` / `:scoped_research_verified`, checked facts rather than Host ALLOW. No profile, trust, revocation, Host or payment responsibility is broadened.
|
|
15
|
+
|
|
16
|
+
## Limited prior 0.2.0 candidate observation
|
|
17
|
+
|
|
18
|
+
[PR #213](https://github.com/cuichangquan/ap2-mandate-verifier/pull/213) records a separately approved build/install/audit at source HEAD `771eebb1094c19931aadafd32feaa70e2caa48f6` (same tree as merged main `9b981be68a1abaf318a7ae78497b3d74d8aefdda`). The retained local candidate was 32,256 bytes, SHA256 `0a126e170e482fea5138865d658f4c21687dc238e595236456f687ceb8aab211`; it is not a published download or this document's new artifact.
|
|
19
|
+
|
|
20
|
+
The limited Debian 12/arm64 observation used MRI 4.0.9 and the fixed Gem dependencies, OpenSSL library 3.0.22 / OS package `libssl3:arm64 3.0.22-1~deb12u2`. All 13 payload files matched source/archive/installed bytes, ordinary RubyGems require loaded 10 product Ruby files, and 118 logical cases passed: research42 + checkout42 + unavailable24 + legacy7 + input rejection2 + constructor rejection1. Saved inputs/independent expected values were reused; source190/885 were not rerun in this attempt. Earlier auxiliary-diagnostic STOP records remain preserved in PR #213.
|
|
21
|
+
|
|
22
|
+
This is an additional bounded observation, not adoption of Debian as a supported platform or proof of general runtime security, symbol binding, whole-wire accounting or resource performance. The 0.1.0 baseline and historical evidence below retain their own artifact identities. README.md and this contract are packaged; editing them creates different candidate bytes. The documentation-final candidate build/install, 13-payload/10-loaded identity checks and 118 installed cases are pending separate approval and NOT_RUN. Final dependency/provider advisory review and exact-artifact publication approval remain required. Real Issuer trust/revocation, actual Host operation, performance and production GO remain HOLD.
|
|
23
|
+
|
|
8
24
|
## Verification contract
|
|
9
25
|
|
|
10
26
|
Preserve `verify_research`, its seven keyword inputs, existing status/code and Evidence v2 identifiers, and legacy APIs' non-success behavior. No API rename, new trust enrollment, remote lookup, DB or payment operation is added. Fixed AP2 commit b4587ac1d055888a73b4b21750973cffba961793 and the exact profile v1 body/hash, seven supported shapes, ES256/P256 and existing bounds remain unchanged.
|
data/lib/ap2_mandate_verifier.rb
CHANGED
|
@@ -125,4 +125,7 @@ module AP2MandateVerifier
|
|
|
125
125
|
# All older methods continue to return non-success Result values.
|
|
126
126
|
def self.verify_research(**inputs) = ResearchResult.verify(**inputs)
|
|
127
127
|
|
|
128
|
+
# Fixed-profile checkout verification; Evidence is not Host ALLOW or payment permission.
|
|
129
|
+
def self.verify_checkout(**inputs) = ResearchResult.verify(**inputs)
|
|
130
|
+
|
|
128
131
|
end
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: ap2_mandate_verifier
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.
|
|
4
|
+
version: 0.2.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- AP2 Mandate Verifier contributors
|
|
@@ -80,8 +80,9 @@ dependencies:
|
|
|
80
80
|
- !ruby/object:Gem::Version
|
|
81
81
|
version: 3.2.1
|
|
82
82
|
description: Stateless verification of the fixed AP2 profile with immutable Evidence
|
|
83
|
-
using the
|
|
84
|
-
runtime; not Host authorization, payment permission or
|
|
83
|
+
using verify_checkout and the retained verify_research API. Requires trusted Host
|
|
84
|
+
inputs and the documented runtime; not Host authorization, payment permission or
|
|
85
|
+
general AP2 conformance.
|
|
85
86
|
executables: []
|
|
86
87
|
extensions: []
|
|
87
88
|
extra_rdoc_files: []
|