Deferred work register
Public mirror of ADR 0005 — the living list of work explicitly deferred from the 2026-05-18 implementation push. Each item has a named owner and a triggering condition, so nothing rots out of sight. This page is regenerated from the ADR; the ADR remains canonical. Items leave the register when promoted to their own ADR, completed, abandoned, or superseded.
Not the only list of candidate work — but the only list of committed work
The DBT Smart Data gap register
(SD1–SD13) tracks what PDTF cannot yet encode against DBT's draft
Smart Data Guidebook. Those are analysis findings, not deferred work: they
carry no owner and no triggering condition until a council or WG adopts one, at which point
the item lands here. The SD prefix exists so it cannot be confused
with this register's A–G series.
How items leave this register
Entries are mutable by design. They depart by one of four routes: promotion to a dedicated ADR, completion (ships and stays as evidence for one review cycle), abandonment (declared out of scope with rationale), or supersession (replaced by a different approach, link recorded). Items that don't progress for 12 months get flagged at the annual Wave 3 review (item D5) for a "still relevant?" check.
A. Wave 2 content authoring
Substantive workstreams — months of WG work to flesh out the four Wave 2 stub pages. Pre-trigger until the C&R WG and Technical WG kickoffs land per ADR 0001 Q3 sequencing.
| # | Item | Owner | Triggering condition / dependency | Status | Linked artefact | Notes |
|---|---|---|---|---|---|---|
| A1 | /governance/data-quality content | C&R WG | Workstream kickoff (per ADR 0001 Q3 — runs in parallel with A2 and A3) | Draft for C&R WG · 2026-05-19 | /governance/data-quality (substantive draft) | Stub has section headings for the 6 DQ dimensions, measurement protocols, AL mapping, reporting. WG fleshes out each section. |
| A2 | /governance/data-security content | C&R WG | Workstream kickoff (parallel with A1, A3) | Draft for C&R WG · 2026-05-19 | /governance/data-security (substantive draft) | Stub has 5 controls (KYC/KYB, key mgmt, signature verification, revocation, audit logging) + policy / checklist / audit framing. |
| A3 | /governance/accreditation-directory content | C&R WG | Workstream kickoff (parallel with A1, A2); depends on ADR 0004 Phase 1 (skeleton schema) | Draft for C&R + Tech WG · 2026-05-19 | /governance/accreditation-directory (substantive draft) | Stub describes the how-it-works flow, scoring, evidence tiers; first publish target is end of quarter following all four Wave 2 ADRs ratified. |
| A4 | /governance/overlay-attachments content | Technical WG (with C&R WG input on retention + consent) | Workstream kickoff (parallel with A1–A3) | Draft for Tech WG (C&R input) · 2026-05-19 | /governance/overlay-attachments (substantive draft) | Stub lists 11 v3 overlay attachment types; sections for file formats / signing / retention / consent. |
| A5 | C&R WG recruitment to support parallel A1–A3 | Engagement WG | Before A1/A2/A3 kickoff (per ADR 0001 Q3 pre-condition) | Recruitment brief drafted · 2026-05-18 | docs/recruitment/cr-wg-candidate-firms.md | Target firms with mature internal DQ / Security functions (large lenders, surveyors, conveyancing platforms). |
B. Wave 1 leftover tagging
Mechanical, but per-page work — applying the DAMA Wheel cross-reference and the per-KA template across the existing corpus.
| # | Item | Owner | Triggering condition / dependency | Status | Linked artefact | Notes |
|---|---|---|---|---|---|---|
| B1 | DAMA Wheel cross-reference per page | Whoever picks up the Wave 1 leftovers | Opportunistic | Retired 2026-09-02 | scripts/dama-ka-mapping.json | The former per-page metadata component was removed from the rendered site. The mapping file remains as the historical record. |
| B2 | Per-KA template applied per page | Same | Opportunistic | Template ready · WG to apply incrementally | docs/templates/per-ka-section-template.md (rubric scaffold appended to A1–A4 stubs) | Consistent rubric: Purpose · Activities · Deliverables · Roles · Metrics · Maturity. Apply incrementally; not all pages need every section filled. |
C. Accreditation Directory build pipeline
ADR 0004 Phase 4 — the build-time aggregator, member-firm submission tooling, first quarterly publish, and OPDA-listed audit-partner list.
| # | Item | Owner | Triggering condition / dependency | Status | Linked artefact | Notes |
|---|---|---|---|---|---|---|
| C1 | scripts/build-accreditation-directory.mjs | Technical WG | Member firms ready to submit first VCs (downstream of A1–A4 shipping capability bundles) | Stub ready (parses, throws on main) | scripts/build-accreditation-directory.mjs | Build-time aggregator: reads all current-quarter VCs from source/04-governance-bodies/accreditation/credentials/, validates signatures against Trust Registry, emits src/data/accreditation/current.json for the Directory page render. |
| C2 | Member-firm VC submission tooling | Technical WG + Engagement WG | After C1 ships | Draft spec · pending C1 + first firm | docs/templates/vc-submission-spec.md | Firms need a clear way to mint and submit their quarterly VCs. CLI helper? Web form? Out of scope for the script itself. |
| C3 | First quarterly publish | C&R WG + Technical WG | After A1–A4 + C1 + C2 | Checklist template ready | docs/templates/first-quarterly-publish-checklist.md | End-of-quarter milestone for the first time the Directory has real data. |
| C4 | OPDA-listed audit-partner list | Engagement WG | Before any firm claims an evidence-tier score 5–6 | Candidate list drafted (= F1) | docs/recruitment/opda-listed-audit-partners.md | Initial list likely Big 4 + property-data specialists (KPMG, Deloitte, BDO + Hometrack / Land Insight / etc.). Out of scope for this register beyond noting the dependency. |
D. Wave 3 watching briefs
Items kept warm per ADR 0001 §"Wave 3" — none in active flight; each has a defined trigger or a standing calendar slot at the annual EC review.
| # | Item | Owner | Triggering condition / dependency | Status | Linked artefact | Notes |
|---|---|---|---|---|---|---|
| D1 | GARP for OPDA institutional records | TBD | Opportunistic | Watching brief — no artefact | — | Apply Generally Accepted Recordkeeping Principles to OPDA's source/ tree. Mostly a published handling policy + retention defaults per subtree. |
| D2 | Storage & Ops — retention/disposal guidance | TBD | Trust Registry to production OR consumer-trust narrative needs it | Watching brief — no artefact | — | Member-firm guidance: how long does a verified PDTF claim live in a firm's database after a transaction completes? UK GDPR alignment. |
| D3 | AI/ML governance over PDTF data | TBD | First member firm publishes a PDTF-trained model OR ICO/EU AI Act guidance solidifies | Watching brief — no artefact | — | Bias/fairness considerations specific to property data (historical red-lining patterns). Data-use governance, not platform engineering. |
| D4 | Data-product discipline for OPDA's meta-analytics | TBD | Opportunistic | Watching brief — no artefact | — | Apply data-product discipline (lineage, release plan, versioning) to Accreditation Directory, Standards Report, Consumer Survey. Extend provenance-map.yaml toward a lineage dictionary as new reports are produced. |
| D5 | Annual Wave 3 review (AGM-adjacent EC meeting) | EC | Every AGM-adjacent EC meeting | Agenda template ready · annual | docs/templates/agm-adjacent-ec-wave3-agenda.md | ~15-min agenda item walking D1–D4 (and successors): trigger fired? rotted? watching brief continues? |
E. Pre-deploy + ops
Operational hygiene items tied to the 2026-05-18 push — visual smoke test, external-materials audit, and the DCAM attribution note.
| # | Item | Owner | Triggering condition / dependency | Status | Linked artefact | Notes |
|---|---|---|---|---|---|---|
| E1 | Visual smoke test in browser | Henrik (next session) | Before push to production | Scaffold ready · manual run | scripts/smoke-test.mjs (install @playwright/test to run) | Theme toggle, sidebar collapse, tree-folder toggle, mobile menu, Mermaid diagrams across sections, data tables on /development/inputs/pdtf-schema/schema-and-supporting-material/data-dictionary + /development/inputs/pdtf-schema/schema-and-supporting-material/business-glossary. |
| E2 | External materials audit | Engagement WG | Before announcing the URL change | Runbook drafted · Engagement WG to execute | docs/external-materials-audit-checklist.md | OPDA-controlled materials pointing to old /pages/NN-…html URLs will hard-break. Scan briefings PDFs in source/02-policy-and-positioning/briefings-to-government/, openpropdata.org.uk content, propdata.org.uk content, DPMSG decks, member-firm comms, regulator submissions. |
| E3 | DCAM attribution note in governance.md | Technical WG | When time allows | Completed 2026-05-18 | source/03-standards/trust-framework/docs/governance.md §"Framework lineage and attribution" | Per ADR 0001 newly-resolved Q2 (permissive): one-paragraph note in source/03-standards/trust-framework/docs/governance.md defining the "name freely, no verbatim" boundary so future contributors don't re-litigate. |
F. Open items in other ADRs
Tracked here so the register is comprehensive; details live in the originating ADRs.
| # | Item | Owner | Triggering condition / dependency | Status | Linked artefact | Notes |
|---|---|---|---|---|---|---|
| F1 | OPDA-listed audit partners | ADR 0004 Q1 | See ADR 0004 Q1 | Candidate list drafted (= C4) | docs/recruitment/opda-listed-audit-partners.md | Same as C4 above; cross-listed. |
| F2 | Conformance Scheme integration with Directory | ADR 0004 Q2 | See ADR 0004 Q2 | Forward-reference added 2026-05-19 | /governance/conformance-scheme#directoryIntegration | The existing /governance/conformance-scheme page needs updating to reference the Directory and explain the AL × Capability relationship. Own ADR when work begins. |
| F3 | Member-firm portal (deferred tier of the Directory) | ADR 0004 Q3 | See ADR 0004 Q3 | Stub · open questions only | docs/specs/member-firm-portal-requirements.md | Private detailed view for firms + OPDA. Triggers on first member-firm request. |
| F4 | Quarterly publishing automation | ADR 0004 Q4 | See ADR 0004 Q4 | Example workflow (.example — not active) | .github/workflows/accreditation-quarterly.yml.example | Cron / GitHub Action to refresh the Directory; tooling decision deferred. |
| F5 | Ex-member handling in the Directory | ADR 0004 Q5 | See ADR 0004 Q5 | ADR stub · awaiting promotion trigger | docs/adr/_drafts/membership-lifecycle.md | "Former member, last data YYYY-Qn" vs immediate drop-out. Membership ADR territory. |
| F6 | Re-anchor forward-looking standards references (claims, VCs, API specs) off legacy propdata.org.uk anchors | ADR 0051 Thread 4 | Smart Data Guidebook draft chapters + Open Banking Open Finance standards/architecture (awaited); Perseus (Open Energy) is open source and reachable | Partially done · external dependency open | /development/inputs/pdtf-schema/schema-derived-ontology/lineage-provenance-and-verification/historical-modelling/standards-stack, /development/inputs/pdtf-schema/schema-derived-ontology/lineage-provenance-and-verification/historical-modelling/jsonld-mappings, /development/inputs/pdtf-schema/schema-and-supporting-material/schema/overlays | Legacy versioned-spec framework references already re-anchored to SPDTF (OPDA's own Smart Property standard). Remaining: the schema $id namespace (trust.propdata.org.uk/schemas/…, the real committed identifiers) and JSON-LD context-publishing host await a concrete OPDA-authored target + the Guidebook/Perseus canon before re-pointing — not invented here. |
| F7 | Transition-bridging tooling + funding ask | ADR 0052 Item 6 | Stakeholder funding decision (existing project funding may have scope) | Recommendation stands · funding ask open | /strategy/project-roadmap | Keep the recommendation for current→new schema bridging tooling and implementation tooling for industry. The funding / resource requirement must be surfaced to the stakeholder for a decision against existing project funding. Per stakeholder review (Maria Harris) — see ADR 0052. |
G. Ontology implementation programme
Surfaced by the ontology-implementation programme's per-ADR validation
discipline (see docs/plan/ontology-implementation.md §9.3 +
§9.4). Validation may surface (a) genuine ratified-rules ambiguity needing
a Council Author-only amendment, or (b) named follow-ups that are not
blockers but must be explicitly queued. Items below are queued from per-ADR
validation reports under docs/adr/validation/.
| # | Item | Owner | Triggering condition / dependency | Status | Linked artefact | Notes |
|---|---|---|---|---|---|---|
| G1 | Council Author-only amendment — reconcile term-sourcing precedence between ODR 0004 §7a and ADR 0007 §"Term-sourcing five-line precedence" | OPDA Author (per ODR 0001 §"Self-amendment process") | Before any emitter branches on tier == 3 semantics (no caller does today) | Doc amended 2026-05-27 (ADR 0007); code change in lockstep at ADR 0012 worker | ADR-0007 §"Term-sourcing five-line precedence" | Discrepancy between ratified Council rule (regulators at tier 3, contextual) and engineering pseudocode (glossary at tier 3, regulator at 5). Amendment aligns ADR-0007 pseudocode + prose to ODR-0004 §7a's slot ordering. |
| G2 | Prefix-filter heuristic refinement in serialiser/canonical.py | ADR 0009 worker | ADR 0009 implementation start | Closed 2026-05-27 (commit c5629e7) | tools/opda-gen/src/opda_gen/serialiser/canonical.py:143-148 | Literal lexical values scanned for IRI-shaped strings; two regression tests added. Verified by ADR-0009 validator. |
| G3 | check_derived_provenance git-blame implementation + regression test (ODR 0004 §3a clause #5) | ADR 0009 worker | ADR 0009 implementation start | Closed 2026-05-27 (commit c5629e7) | tools/opda-gen/src/opda_gen/ci/three_graph_test.py:138-229 | git log --format=%ae walk over derived/; env-var allowlist (OPDA_SERVICE_ACCOUNTS); four regression tests using tmp git-repo fixture. |
| G4 | Split CI workflow comment block by activation ADR | ADR 0009 worker (cosmetic) | Opportunistic | Closed 2026-05-27 (commit c5629e7) | .github/workflows/deploy-aws.yml | The activation markers were retained until the ontology and BASPI5 checks were consolidated into the deployment-gating workflow on 2026-09-03. |
| G5 | Mirror Section G to /governance/deferred-work Astro page | Technical WG / next contributor touching the mirror | Before next quarterly publish | Closed 2026-05-27 (this commit) | This table (src/pages/governance/deferred-work.astro) | Astro mirror now carries the G1–G11 table with Status + Linked-artefact columns matching the other sections. |
| G6 | Cosmetic ADR 0009 template amendment — document sentinel-pinning convention | Author / opportunistic | Opportunistic | Closed 2026-05-27 (this commit) | ADR-0009 §"foundation.ttl" prose preamble | Angle-bracket placeholders (<git-sha>, <emission-date>) are illustrative, not live-substitution directives; sentinel-pinned to satisfy byte-identity CI per ODR-0004 §6a. |
| G7 | Prefix-filter edge-case regression test for URL-bearing rdfs:comment / skos:scopeNote Literals | ADR 0010 worker | First URL-bearing Literal emission (gov.uk URLs in council-tax / EPC scope-notes) | Closed 2026-05-27 (commit 75337ec) | tools/opda-gen/tests/test_serialiser.py | Two regression tests confirm gov.uk URLs inside Literals don't bind a spurious gov.uk prefix; G2's scan widens reference set but never the binding set. |
| G8 | ADR 0010 scope expansion — admit additional SKOS schemes beyond the named first batch | ADR 0013 worker (bundled with overlay profile emission) | When a downstream module ADR or overlay profile cites a scheme not in the 16-row first-batch table | Bundled with ADR 0013 worker brief | (forthcoming via ADR 0013 commit) | Data dictionary carries ~1225 enum-bearing leaves; first batch covers 16 (88 concepts). Expansion happens scheme-by-scheme per BASPI5 overlay need. |
| G9 | Populate placeholder schemes (MilestoneKind / AssuranceLevel / EvidenceMethod / AddressVariant) with real per-member data | ADR 0013 worker (bundled with overlay profile emission) | Before ADR 0014 BASPI5 round-trip MVP | Bundled with ADR 0013 worker brief | (forthcoming via ADR 0013 commit) | Four schemes emitted with PLACEHOLDER warnings; real per-member data from eIDAS / OIDC4IDA / ODR-0015 §S015 Q1 / PDTF process docs. |
| G10 | TransactionStatusScheme per-member dct:source URI fix | ADR 0014 worker (MVP-blocking) | MUST land before ADR 0014 BASPI5 round-trip | Bundled with ADR 0014 worker brief | (forthcoming via ADR 0014 commit) | 5 TransactionStatus members emit fabricated <...#status.Listed> fragments; remediation per validator option (a) — cite ODR-0011 §8a instead. |
| G11 | ADR 0011 Q5a binding table completion — remaining ~44 descriptive-attribute leaves | ADR 0013 worker (bundled with overlay profile emission) | Before ADR 0014 BASPI5 round-trip MVP | Closed 2026-05-28 (ADR-0013 implementation) | 17 + 2 = 19 DatatypeProperties emitted in opda-property.ttl / opda-agent.ttl per ODR-0008 §Q5a; (G16 correction: 18 + 2 = 20 by direct enumeration). | |
| G12 | Canonical serialiser blank-node deduplication for multi-target shared blank nodes | ADR 0013 worker (bundled) | Cosmetic; opportunistic | Closed 2026-05-28 (ADR-0013 implementation) | Resolved beyond cosmetic scope: fixed latent byte-identity bug where multi-object sort used non-deterministic rdflib BNode labels. | |
| G13 | Housekeeping — confirm G1 closure | Author / 2026-05-27 | Now | Closed 2026-05-27 | G1 already closed in commit 5bd0c41; no further action. | |
| G14 | Cat 4 SHACL shape activation trigger — declare opda:hasSpecialCategoryData OR route Council S012 Q3 | Council Author-only session + ADR-0014 worker engineering closure | Before MVP gate (ADR-0014) | Closed 2026-05-28 (ADR-0014 implementation; Council route preserved) | opda:hasSpecialCategoryData declared as foundation owl:DatatypeProperty with xsd:boolean range; skos:scopeNote preserves the S012 Q3 Council ratification route. | |
| G15 | Cosmetic ADR-0007 amendment — document __version__ vs owl:versionIRI decoupling rule | Author / opportunistic | Opportunistic | Closed 2026-05-27 | ADR-0007 §"A9 per-kind discipline output" amended to document the decoupling rule. | |
| G16 | ADR-0013 implementation report DatatypeProperty count: 19 → 20 (worker under-counted) | ADR 0014 worker (bundled, cosmetic) | Opportunistic | Closed 2026-05-28 (ADR-0014 implementation) | ADR-0013 report § G11 updated 19 → 20 (18 property + 2 agent). | |
| G17 | Stale "five foundation classes" doc-comments in foundation.py + opda-classes.ttl header | ADR 0014 worker (bundled, cosmetic) | Opportunistic | Closed 2026-05-28 (ADR-0014 implementation) | Foundation generator docstrings + extra_lines now name the six foundation classes; opda-classes.ttl + opda-annotations.ttl headers regenerated. | |
| G18 | Declare opda:role as DatatypeProperty in opda-agent.ttl for DASH editor ergonomics | ADR 0014 worker (bundled) | Before MVP gate | Closed 2026-05-28 (ADR-0014 implementation) | opda:role declared with rdfs:domain opda:RoleMixin + rdfs:range xsd:string + A9 metadata; typed encoding (a opda:Seller) remains canonical. | |
| G19 | Fix 4 BASPI5 profile anchor URL mismatches (A1.8.7, A7.5.1, B1.2, A1) | ADR 0014 worker (bundled) | Before MVP gate (form-question IRI resolution) | Closed 2026-05-28 (ADR-0014 implementation) | A1 → A1.1; A1.8.7 → A1.8.4.1; A7.5.1 → B4.6.2; B1.2 → B1.1. All four now exact-match a baspi5Ref value in baspi5.json. | |
| G20 | ADR-0013 implementation report anchor count: 36 → 28 (worker over-counted) | ADR 0014 worker (bundled, cosmetic) | Opportunistic | Closed 2026-05-28 (ADR-0014 implementation) | ADR-0013 report anchor counts updated to 28 distinct anchors (validator's canonical count). |
How items leave this register
- Promoted to its own ADR. Item gets a dedicated ADR (typical for substantive workstreams). The register entry is updated to point at the new ADR and marked "promoted". Two reviews later it can be removed.
- Completed. Item ships. Entry marked "completed YYYY-MM-DD", remains for one review cycle as evidence, then removed.
- Abandoned. Item is explicitly declared out of scope (new ADR or annual review). Entry marked "abandoned YYYY-MM-DD, rationale: …", remains permanently as a "considered and rejected" record.
- Superseded. Item is replaced by a different approach. Entry marked "superseded by [link]", remains permanently.
References
- ADR 0001 — Wave 1/2/3 commitments; this register itemises what's not yet built.
- ADR 0004 — Accreditation Directory spec (this register tracks its build pipeline).
- ADR 0005 — canonical source for this register; living document, revised at every annual Wave 3 EC review and ad-hoc as items ship or get added.
Comments
Loading comments…
Sign in to post a comment