specs: align layered ANS specs with RA v1 / TL V2 contracts; markdown…#26
Merged
Merged
Conversation
… lint
Field/format alignment of the layered specs (spec/ans-0..5 + examples) to the
authoritative API contracts, ahead of the reference implementation:
- RA request & Trust Card fields use the V1 RA names: agentDisplayName,
agentDescription, version, identityCsrPEM, serverCsrPEM, metaDataUrl, and the
new metaDataHash (SHA256:-prefixed).
- TL event / badge / envelope examples use the V2 TL response format: ansId
(distinct from the RA agentId by design), nested agent{host,name,version,
providerId}, identityCerts[]/serverCerts[] arrays, dnsRecordsProvisioned[]
objects, merkleProof, schemaVersion "V2", status {ACTIVE,REVOKED,DEPRECATED}.
- SHA256: hash prefixes throughout; PENDING -> PENDING_VALIDATION lifecycle;
ansId identifier row added.
- ANS-5 schema-integrity check keyed off metaDataUrl + the TL metadataHashes map.
- Add .github/linters/.markdown-lint.yml and clear markdownlint issues repo-wide
(table-delimiter padding, fence languages, heading levels, bare URL/email
wrapping, list indentation).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
| ], | ||
| "domainValidation": "ACME-DNS-01", | ||
| "dnssecStatus": "fully_validated" | ||
| "dnssecStatus": "fully_validated", |
There was a problem hiding this comment.
maybe a bit nitpicky might want to keep enum values Upper case as others are.
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
2 participants
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.
… lint
Field/format alignment of the layered specs (spec/ans-0..5 + examples) to the authoritative API contracts, ahead of the reference implementation: