Supplier-first platform
Refarm supplies the blocks downstream projects should not rebuild.
The current public-site candidate tracks the reusable package lane: contracts, DS helpers, source/records/enrichment, credentials, handoff manifests, and release evidence for consumers such as vault-seed.
Current selection
vault-seed-ready contains 18 candidate packages
This lane is a local candidate channel, not a public npm promise. It exists so official consumer checkouts can assimilate reusable Refarm blocks before release automation is enabled.
- @refarm.dev/artifact-contract-v1
- @refarm.dev/channel-policy-v1
- @refarm.dev/credentials-contract-v1
- @refarm.dev/dispatch-surface
- @refarm.dev/ds
- @refarm.dev/effort-contract-v1
- @refarm.dev/enrichment-contract-v1
- @refarm.dev/heartwood
- @refarm.dev/identity-contract-v1
- @refarm.dev/identity-heartwood
- @refarm.dev/process-handoff
- @refarm.dev/records-contract-v1
- @refarm.dev/release-engine
- @refarm.dev/silo
- @refarm.dev/source-contract-v1
- @refarm.dev/source-web
- @refarm.dev/storage-contract-v1
- @refarm.dev/storage-memory
Publication posture
Local handoff ready; npm publish waits for release approval
The active 2026-07-01 local handoff is materialized with tarballs, manifest files, and distribution evidence for official consumer assimilation. Public publish still waits on develop stabilization, GitHub Actions confirmation, release PR flow, and explicit operator approval.
Operator map