Start

START Forward Execution Backlog

This is the sole canonical backlog for future work. It contains unchecked work that remains after the deepest red-team review and hardening pass (2026-08-01).

Known repository defects (recorded 2026-11-11; two added 2026-11-12; not fixed)

Verified against the tracked tree at this head. Each needs an owner decision before it is changed; none was modified by either review pass.

Dependency pins (verified 2026-11-12)

Education contract (blocked outside this repository)

Docs deep review (2026-08-02)

Scoped and implemented during the mega-deep documentation pass. Severity definitions: Minor = typo, broken link, formatting; Medium = stale section rewrite, doc restructure, added missing guide; Major = large doc system overhaul or cross-cutting refactor.

Major

Medium

Minor

Open / deferred

P0 — Release blockers

None open. The artifact boundary and the provider matrix moved to the 2026-11-12 completed section below. What still blocks a release is one publication gate each, tracked where it is worked: the provenance floor in P1 and the coverage floor in P2.

P1 — Data and product readiness

P2 — Public release gates

P3 — Post-release product exploration

None of these is blocked; each needs an owner decision from the repository maintainer before it becomes work.

Major — Scoped (deferred) — validated but intentionally NOT implemented

None currently. The one quality Major (mypy debt) was resolved in the 2026-08-01 comprehensive pass and is now enforced in CI.

Documented deferrals (validated but deliberately NOT modified this pass)

These were validated and intentionally left unchanged after a review decision; they are documented here so the reasoning is not lost.

Completed / Closed (2026-11-12 backlog truth pass)

Verified against tracked files at this head. Nothing here rests on a hosted run, because the estate’s Actions runs are billing-locked.

Completed / Closed (2026-08-01 comprehensive + wiring pass)

Additional improvements landed after the first comprehensive pass (all four gates green: pytest exit 0, ruff clean, black clean, mypy 0):

The earlier comprehensive + red-team passes (StageResult partial-failure, skip_existing freshness, post-clone git hardening, prompt-injection data framing, legacy 3_Intro cleanup, schema/io/repos/GUI/system hardening) remain complete as recorded below.

Implemented and verified (pytest, ruff, black, mypy all green) during the comprehensive pass. This adds to the earlier red-team hardening:

Implemented and verified (pytest, ruff, black all green; no new mypy errors) during the deep red-team pass. These are removed from the active backlog:

Definition of done

An item is complete only when implementation, tests, documentation, generated artifacts, and release validation are aligned. Remove completed items instead of adding a history section; add newly discovered future work here.