Skip to main content
The 10-week consolidated plan (W1-W10) closed 2026-04-29. This page is the honest ledger of what remained — reconciled against the codebase on 2026-07-03. Most of the original residuals have since shipped; they are listed at the bottom for the record.

​
Distribution splits

Intentionally in-repo until a separate distribution channel (PyPI for the client SDK, a hosted leaderboard for the benchmark) is authorized.

​
Operator-enabled features (by design, not gaps)

Code-complete and deliberately dormant until an operator enables them. These are lazy-load / feature-gate designs, not TODOs.

​
Genuinely open code-side items

​
Graduated since W10 close (for the record)

Everything below was listed as a residual at W10 close and has since shipped — see the changelog for dates and details:
  • Real cosign sign-blob signing on provenance bundles (placeholder removed)
  • Stuck-processing outbox row reaper (/api/v1/cron/outbox-reaper)
  • Multi-input / multi-output ONNX models with per-input dtypes
  • ONNX out-of-band blob store (file:// and s3://) replacing the JSON-column cap
  • LIME + counterfactual auto-run from /api/v1/fairness/evaluate
  • Multi-stage four-eyes approvals (approval_request_stages + stage state machine)
  • Negotiation apply-mode and multi-turn sessions wired into /recommend and dedicated routes
  • Lagrangian cross-offer constraints (CRUD API + realtime pipeline wiring)
  • Bandit arm sampling on realtime /recommend (banditArmIndex in responses)
  • Slack webhook for nightly negotiation-eval failures
  • kaireon_outbox_pending_count Prometheus gauge
  • Cross-offer dual-loader consolidation (2026-07-03: the batch loader read a row shape the API never wrote — API-created constraints silently never applied on batch; single canonical loader now serves both paths)

​
Why residuals exist (honest answer)

For operator-authorized items: we deliberately do not create new GitHub repos, modify production secrets, or flip production flags from inside an automated coding session. For the open code-side items: each is called out inline in the corresponding source file. None block production rollout; they are next-iteration enhancements gated on tenant demand or a downstream feature landing first.