Bootstrap Digital Registries 3.0.0-alpha.2

[jeremi]

Summary

• restructures the active specification around a shared Registry Core and Consultation Retrieve as the target Base Registry Profile
• adds concise adopter-facing pages for all eight API families and an editable SVG overview
• defines six Core and three Consultation Retrieve DRAFT requirements with aligned data structures, service semantics, workflow, and verification rows
• records the disposition of all previous DRS-1 through DRS-37 requirements
• isolates generated CRUD contracts, tests, examples, and historical pages so they cannot be mistaken for current conformance artifacts

Why

The previous specification combined a domain-neutral Registry scope with the behaviour of a generated CRUD/database-builder product. That made product-specific storage, UI, and endpoint assumptions appear mandatory across registries with different institutional responsibilities and trust models.

This prerelease establishes a smaller interoperability foundation. It separates Registry operations, common metadata, semantic models, and protocol bindings while retaining the useful intent and attribution of earlier work.

Adopter and implementer impact

• architects can identify the minimum proposed Registry behaviour and the boundaries with neighbouring Building Blocks
• adopters can assess additional capability families without treating them as current obligations
• implementers have nine deterministic DRAFT requirements and matching verification intent for the first vertical slice
• existing implementations can use an adaptor and are not required to replace their internal storage or administration model

This remains an alpha. It does not publish a canonical OpenAPI contract or executable conformance suite, and no implementation can claim conformance from this revision.

Validation

• git diff --check
• 91 of 91 active documentation links validated
• SVG validated as XML and rendered without clipping
• archived JSON and YAML contracts parsed successfully
• 9 of 9 DRAFT requirements mapped to verification rows
• all 37 previous DRS requirements present in the migration ledger
• independent read-only consistency review completed with a GO assessment

Follow-up

• define the canonical Consultation Retrieve schema and OpenAPI binding
• publish domain-neutral examples and executable contract tests
• align conditional capability applicability and protocol-native bindings with Support optional capability profiles and protocol-native API bindings cfr-architecture#7