Product guide

Build With Quality Archive

Users retaining supported BWQ records safely outside active operational apps

Free MVP / pilot — supported package types must match Archive validation

Release validation boundary: Publish exact supported platform/build only after Archive release validation.

Getting started

Choose a supported package/record
Import without changing the source app
Verify integrity
Retain the original package and metadata
Find/reference or deliberately restore/rehydrate when supported

Backup / update safety

Archive is itself a retention layer, not a replacement for every source app’s active backup. Keep independent copies of important archive packages.

Before reinstall/update: make a validated backup/export, confirm package identity, and do not delete the old working install until the new build and data are verified.

Known MVP limitations

Not live synchronization
Does not own active operational truth
Only supported package types should be claimed
Restore/rehydration claims require package-specific validation

Need the approved pilot package?

Platform does not publish an unvalidated binary link. Use pilot support until the owning repository has a signed/release artifact that passed its clean-install and upgrade validation.

Contact pilot support

Data ownership

The operational app remains authoritative for its own local data. Exchange may carry bounded facts with provenance, but receiving another participant's information does not itself overwrite receiver-owned records. Platform does not host normal construction operational databases.