Conversation
…st into ADR-079/feature trustSelf policy field (trust own DID, resolved dynamically, no hardcoded entry); config IS the verify argument (no translation layer); revocation = signed W3C Bitstring status-list credential, resolution-agnostic (local storage:v1 v1; remote only behind an egress allowlist per the peerd lesson). Conformance gains a trustSelf case.
…n gate satisfied vault-seed re-vendored the updated credentials-contract-v1 and exercises verify(input, policy) directly (trust list gates acceptance, status-list revoke flips notRevoked). The ADR-079 promotion gate is closed.
…enrichment, credentials) Records the external-consumer evidence beyond Refarm dogfooding: vault-seed vendors + consumer-contract-tests records:v1/enrichment:v1, the reference vault composes source-web->records->enrichment with an empty gap ledger, a records YAML-LD codec round-trip lands, and a heartwood-signed credentials:v1 provider passes the full conformance. T1 (pi-agent runtime) is not a vault-seed-consumed contract, so no downstream proof applies.
…ility gap) The @context URL https://refarm.dev/contexts/records/v1 is stamped by the reference provider but no route serves a JSON-LD context document (public apps/site has no /contexts/). Works today as an opaque namespace; for real dereferenceable linked data Refarm must serve it (the pattern exists: sovereign-graph.jsonld, tractor schemas; apps/site is the natural host). Flagged by the vault-seed consumer, which uses it as RECORDS_BASE_CONTEXT.
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
Release candidate for the vault-seed-ready v0.1.0 package set.
This PR carries the promoted T3/T2 supply blocks that are now consumer-proven by the official vault-seed checkout, including credentials, records/enrichment/source-web, release handoff tooling, and supporting contract/reference packages.
The release-blocking linked-data gap is also closed: the public site now serves
/contexts/records/v1as a realapplication/ld+jsondocument covering the distributedRecordsManifestandKnowledgeRecordenvelope terms.Local validation
refarm resume --jsonrefarm check --next-action --jsonnode scripts/vault-seed-ready-handoff.mjs --pack --jsonpnpm run release:readinesspnpm run release:vault-seed:checkpnpm -C apps/site run testpnpm -C apps/site run type-checkpnpm -C apps/site run buildrefarm agent finish --lane after-edit --run --jsonrefarm agent finish --lane after-commit --run --jsonCI
28525674579passed for commita01bdc1c.Publication note
Publishing remains manual-approval gated. After merge and CI confirmation on
main, the next release step is npm auth/permissions plus the explicit publish command for the 18 vault-seed-ready packages.