REG-{{YYYYMMDD}}-{{short-id}} — {{Asset short title}}
Per
docs/legal/regulatory-asset-intake.mdFilename regex:REG-\d{8}-[a-z0-9-]+\.md(no other characters). Records are append-only. To revoke, open a successor and add a “Superseded by” row at the bottom of this file.
Asset metadata
| Field | Value |
|---|---|
| Regime | eIDAS / DORA-IR / DORA-RoI / CRA / Other |
| Vendor / regulator | e.g. EBA, OASIS, named QTSP |
| Version pin (canonical) | exact regulator-published string, no abbreviation |
| Source URLs | one per line |
| Transitive references | URLs of any embedded schemas/standards |
| Candidate SHA-256 | sha256:<lowercase hex> of the candidate archive |
| Candidate bytes | size in bytes |
| Source date | YYYY-MM-DD of the regulator publication |
Proposed local path
docs/contracts/schemas/eu/<regime>/<vendor>/<version>/
(If a new top-level path is required, list the YAML inventory amendment needed first; that amendment is part of Gate 2.)
Runtime use
- Sprint discharged: filename of the sprint whose BLOCKED row this intake closes.
- Validator code path(s): file:method references in
src/.... - Current fail-closed posture: one paragraph on what the runtime does today before this asset is vendored.
- Post-intake behavior: one paragraph on what the runtime will do once the asset is present (typically: enable a previously-disabled schema-validation step or a previously-skipping check).
Gate 1 — Engineering candidacy
| Field | Value |
|---|---|
| Engineer | name + sprint role |
| Date submitted | YYYY-MM-DD |
| Outcome | pass (record proceeds to Gate 2) |
| Notes | any unresolved questions for downstream gates |
Gate 2 — Schema-governance review
| Field | Value |
|---|---|
| Reviewer | maintainer-of-record or named alternate |
| Date | YYYY-MM-DD |
| Re-computed SHA-256 | sha256:<hex> (must match the candidate digest above) |
| Outcome | pass / reject |
| Notes | path-namespacing decisions, partial-vendor concerns, transitive completeness |
Gate 3 — Legal review
| Field | Value |
|---|---|
| Reviewer | named legal reviewer |
| Date | YYYY-MM-DD |
| BUSL-1.1 compatibility | compatible / compatible-with-notice / reference-only / incompatible |
| Distribution license | SPDX expression or full text reference |
| Determination | approved-vendor / approved-with-notice / reference-only-no-vendoring / rejected |
| Attribution text | text that will go into NOTICE.md (may be a multi-line block here) |
third-party-licenses/ filename | new file path, if any |
| Notes | reasoning, restrictions, expiry conditions |
Gate 4 — Compliance / Vendor Integration
(Required only for vendor-qualified packages; skip for regulator-published-only assets.)
| Field | Value |
|---|---|
| Reviewer | named compliance / vendor-integration owner |
| Date | YYYY-MM-DD |
| Vendor agreement reference | contract id or document path |
| Jurisdiction | e.g. EU/DE |
| Profile | e.g. RFC 3161 + CAdES-LTA |
| Expiry / renewal date | YYYY-MM-DD |
| Verdict fixtures | path to the accepted/rejected verdict pairs that prove the validator wires correctly |
| Outcome | pass / reject |
Gate 5 — Vendoring + sprint update
(Filled in at merge time.)
| Field | Value |
|---|---|
| Implementer | name |
| Date vendored | YYYY-MM-DD |
| Local path | full path under docs/contracts/schemas/eu/.../ |
| YAML inventory entry | inline diff or anchor to the entry under assets: |
NOTICE.md change | line range / commit |
THIRD-PARTY-DEPENDENCIES.md change | line range / commit |
| Originating sprint Execution Log entry | sprint filename + date |
| Outcome | pass |
Linked artefacts
- YAML inventory entry:
docs/contracts/schemas/eu/eu-schema-taxonomy-assets-v1.yaml#assets[id="<asset-id>"] - NOTICE.md attribution lines: line range
third-party-licenses/files: paths- Originating sprint:
docs/implplan/SPRINT_...md - Validator code path(s): file:line references in
src/...
Supersedes / superseded-by
(Append-only history. Empty on first publication.)