Skip to content

docs: record data-layer D3b quality-report progress#48

Merged
StackOverFlow11 merged 1 commit into
mainfrom
docs/progress-data-layer-d3b
Jun 19, 2026
Merged

docs: record data-layer D3b quality-report progress#48
StackOverFlow11 merged 1 commit into
mainfrom
docs/progress-data-layer-d3b

Conversation

@StackOverFlow11

Copy link
Copy Markdown
Owner

Summary

Docs-only progress sync recording Data Layer D3b (the default-off data-update quality-report hook) as implemented. No code change.

PR #47 merge status

MERGED into main (mergeCommit b21b5f6). D3b code accepted by Codex; this PR only updates documentation to match.

Changed files (3, docs only)

  • docs/data/data_layer_contracts.md — D3b recorded as implemented alongside D3 (default-off data-update quality-report hook; report-only Markdown artifact under output.report_dir; structural checks only; no job failure; no filtering/repairing; no cache/feed/backtest semantic change). The old "D3b deferred" wording is removed; D4-D6 stay explicitly unimplemented.
  • CLAUDE.md — PR feat(data): D3b default-off data-update quality-report hook #47 added to the merged-PR list; D3b progress bullet; quality gate 625 → 643 passed; roadmap next data-layer step is D4 CoverageLedger storage scaling / batch writes (D5 concurrency / endpoint schema registry remain unimplemented).
  • AGENTS.md — made byte-identical to CLAUDE.md.

D3b scope (as recorded)

Strict data_update.quality config (enabled=false default ⇒ every existing config unchanged); supported quality endpoints market_daily / adj_factor / stk_mins_1min; report written under output.report_dir with bounded/redacted findings + symbol count only; no extra API call beyond the frames the updater already warmed; report-only — no job failure, no cache/feed/backtest behavior change.

D4 / scaling / concurrency / schema registry — NOT started

Confirmed. This is a publish + docs-sync task only; no D4 / CoverageLedger storage scaling / batch writes / concurrency / schema registry / fail_on_hard was started.

Verification (Step 4)

  • git diff --name-only main...HEAD → only AGENTS.md, CLAUDE.md, docs/data/data_layer_contracts.md (docs only).
  • cmp -s AGENTS.md CLAUDE.mdidentical.
  • git diff --check main...HEAD → clean; merge-marker scan → NO_MERGE_MARKERS.
  • stale-text scan: no 625 passed, no "D3b deferred/unimplemented" residual; 643 passed recorded; D4-D6 not claimed implemented.
  • docs-only ⇒ full pytest not required (D3b suite already green at 643 on feat(data): D3b default-off data-update quality-report hook #47).

PR #38 untouched

Confirmed: #38 OPEN base=feat/i5c-mmp-minute-factor — not merged, closed, retargeted, or edited.

- data_layer_contracts.md: D3b recorded as implemented alongside D3 (default-off
  data-update quality-report hook; report-only Markdown artifact; structural
  checks only; no job failure, no filtering/repairing, no cache/feed/backtest
  semantic change); the old "D3b deferred" wording removed; D4-D6 stay
  explicitly unimplemented.
- CLAUDE.md / AGENTS.md (kept byte-identical): PR #47 added to the merged-PR
  list; D3b progress bullet (strict data_update.quality config, enabled=false
  default, endpoints market_daily/adj_factor/stk_mins_1min, report under
  output.report_dir, bounded/redacted findings + symbol count only, no extra API
  call beyond warmed frames, no job failure / no cache or backtest behavior
  change); quality gate 625 -> 643 passed; roadmap next data-layer step is D4
  CoverageLedger storage scaling / batch writes (D5 concurrency / endpoint schema
  registry remain unimplemented).

Docs only — no qt/ data/ tests/ config/ change.
@StackOverFlow11
StackOverFlow11 merged commit 6048a57 into main Jun 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant