Repository navigation
docs: name the credential the Facet KYA - #22
Merged
Merged
Conversation
The agent credential is the Facet KYA: an ES256 JWT with typ kya+jwt, issued by https://issuer.facet.llc by default or by another issuer the merchant trusts, sent as Authorization: Bearer. The spec, docs, schema descriptions, and both SDKs called it KYAPay. This renames it everywhere and stops listing KYAPay as an adopted standard, since identity is Facet's own layer. Spec and docs: SPEC.md Section 1 lists three composed open standards and names the Facet KYA among the things Facet defines. Section 6 selects rails per the stp claim in the Facet KYA. Section 8 drops the KYAPay reference. README states the Facet KYA contract (typ, bearer header, single use, default issuer, KYA-Issuers in agents.txt) and drops the KYAPay identity row. Its RFC 9421 row now says what Facet does with the standard: verify signed platform requests on UCP checkout. ARCHITECTURE, AUDIT, the examples, and the audit schema description use the new name. Renames with git mv, contents unchanged: test-vectors/kyapay/ to test-vectors/facet-kya/ (all 10 vectors R100) sdks/python/tests/test_kyapay_conformance.py to sdks/python/tests/test_facet_kya_conformance.py References are updated in both SDK test suites, the vector generator, the CI workflow, and the docs. Left as is on purpose: The typ values the TypeScript verifier docs list (kya+jwt, pay+jwt, kya-pay+jwt). Package names (@facet/sdk-js, facet-sdk) and schema $id values, none of which contain kyapay. Dated CHANGELOG entries; one new Unreleased entry records the rename and the path moves. Verification on Node 20 and Python 3.12 after a clean npm ci: npm run lint exit 0 npm test 2 files, 15 tests passed npm run build exit 0 pytest -v 15 passed CI vectors shape loop exit 0 on 15 files npm audit --audit-level=moderate fails with 3 advisories (vitest, @vitest/mocker, js-yaml). The output is identical on origin/main, and the lockfile is untouched here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Names the agent credential the Facet KYA across the spec, the docs, the schemas, and both SDKs.
stpclaim in the Facet KYA.typkya+jwt) minted byhttps://issuer.facet.llcor another issuer the merchant lists underKYA-Issuers:in agents.txt, sent asAuthorization: Bearer <KYA>, single use.test-vectors/facet-kya/, and the Python conformance test is nowsdks/python/tests/test_facet_kya_conformance.py. Anyone reading the vectors by path needs the new directory.typvalues and verifier behavior are unchanged.Verification
npm auditin the TypeScript SDK reports the same three findings as main (vitest and js-yaml), unchanged by this branch.