Task: Bucket rescoring against sprint 23's mission
Table of Contents
This page documents a task in the Sprint 23 planning session story. It captures the goal, current status, acceptance, and any notes or results.
Goal
The deep backlog refinement (task Deep backlog refinement) verified every
item against the live codebase and discarded/merged what was stale,
but explicitly did not re-score bucket fit — this task does that
half. Score every surviving item's fit against sprint 23's mission
("Continue commissioning ores.refdata entities and codegen C++ drift
correction") and move it to next or deferred accordingly.
inbox is not a valid resting bucket for this pass: every item
currently in inbox must end this task filed into either next or
deferred, not left in inbox.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Sprint 23 planning session |
| Now | Nothing — inbox empty, 310 items rebucketed. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-07-11 |
Acceptance
- Every item in
inboxat task start ends the task filed intonextordeferred—inboxis empty of pre-existing items by the end (new captures filed during the run, if any, are the only exception). - Every
next=/=deferreditem is scored against sprint 23's mission and moved if the current bucket doesn't fit; items already correctly bucketed are left in place. :ID:preserved on every move (git mv, not delete+recreate).
Plan
(Implementation strategy. Written when work starts; key decisions
are distilled into the parent story's * Decisions at close, but the
plan itself stays — it is the historical record of what we did.)
Notes
Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario, run
through the QA Validation Runner panel) that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
PRs
| PR | Title |
|---|---|
Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
Result
Rebase conflicts resolved at PR time (2026-07-11)
Rebasing onto main before merge hit 3 conflicts, all resolved
without re-running the scoring pass:
github_style_history_diff_view.org— a concurrent session had already promoted this capture into a task under Consolidate history dialogs onto HistoryDialogBase and deleted the original (commit570f6fca1) before this branch rebased. My commit had only edited its bucket text; accepted upstream's deletion rather than resurrecting a file that no longer has a reason to exist.generic-dispatch-table-registrar-pattern.org— a genuinely new capture filed ininboxonmainafter this branch's scoring run started (unrelated to this task, picked up by git's rename heuristic as a false match against one of this commit's real moves). Scored it the same way as the rest — explicit "when the first second consumer appears" framing with no near-term plan — and moved it todeferred, keepinginboxempty as this task requires rather than leaving it stranded by the conflict.inbox.org(auto-generated index) — regenerated viaregenerate_backlog_indexes.pyrather than hand-resolving conflict markers in a generated file.
Run on 2026-07-11
Follow-on to Deep backlog refinement, which explicitly deferred this
half. Ran as a workflow: a discovery agent listed every surviving
item across inbox (208), next (224), deferred (56) = 488 total,
then 26 parallel batch agents (20 items each) scored each one's
next=/=deferred fit against sprint 23's mission ("Continue
commissioning ores.refdata entities and codegen C++ drift
correction"), with an explicit instruction that inbox is not a
valid recommendation — every inbox item had to resolve to next or
deferred.
Data-quality check before applying moves
489 scored entries came back for 488 discovered items. Diffed scored-vs-discovered paths and found two anomalies, both handled before applying anything:
- One agent expanded a directory item's path to its
story.orgchild (trade-import-service-layer/story.orginstead of the directory) — cosmetic, normalized back to the directory path. - One agent fabricated an entry with an empty
:ID:=/title (=pricing_model_parameter_table.org_dup_placeholder, a file that does not exist) recommendingnext→next(a no-op). Discarded outright rather than acted on — never trust a schema-shaped response without checking the file it claims to describe exists.
Moves applied
| From → To | Count |
|---|---|
| inbox → next | 123 |
| inbox → deferred | 85 |
| next → deferred | 88 |
| deferred → next | 14 |
| Total moved | 310 |
All 310 applied via git mv (:ID: preserved); 0 errors (no
missing source, no destination collision). 269 of the 310 also had
their intro-paragraph bucket text ("…in the X bucket of the
product backlog…") updated to match the new location and their
#+updated: timestamp refreshed. The other 41 are #+type: story
documents (stories carried into the backlog from a past sprint,
e.g. the commission_* template stories, entity_evaluation_skill)
that never had bucket text in the first place — their template says
"documents a story in Sprint N" or "…in the product backlog" with
no bucket label to update; their new folder location is the only
bucket signal they carry, same as before the move.
Full move list (310), for traceability
Every moved item, linked by :ID:, grouped by direction. Each row's
rationale is the scoring agent's one-line justification against
sprint 23's mission.
- inbox → next (123)
Item Rationale Recipe: how do I build the site locally? Small, well-scoped documentation task mirroring an existing recipe, easy to pick up soon. Add regression tests for onboarding.party wizard-completion checks Well-scoped regression-test backfill flagged in a recent PR review for a bug class that has recurred twice, real near-term urgency. Add postponed state to agile dashboard Concrete, well-scoped dashboard/agile tooling improvement with a clear rationale from sprint 20 experience, standalone and pickup-ready. Add regression tests for tenant provisioner system-settings seeding Concrete, well-scoped test coverage gap flagged during a recent PR review for the exact bug class just fixed, real urgency. Add a Videos page and link it from the Resources menu Small, fully-scoped site content/navigation task with a concrete implementation plan, easy to pick up soon. AppVersionHistoryDialog diff rows mislabelled Concrete, well-scoped bug fix with identified root cause and files, ready to pick up soon. Atomic batch-save endpoint for FX spot config + components Well-scoped robustness fix for a real UX/data-consistency gap flagged in PR review, standalone and reasonably prioritized. Bulk-regenerate synthetic generators to fix hardcoded r.version = 1 Concrete, well-scoped codegen bug fix causing real spurious version-conflict errors across ores.refdata entities, directly aligned with this sprint's codegen-drift-correction mission. Story: Add tenant discovery to CLI and compass Already a fully fleshed-out story with concrete tasks and clear developer-workflow value, ready for near-term pickup. CLI commands — top-level commissioning story Directly extends codegen commissioning for CLI entities, aligning with the sprint's codegen focus. Story: Codegen CI zero-diff invariant A codegen drift-correction guardrail that fits the sprint mission directly. codegen –component run generates all entities not just the target A concrete, well-scoped codegen bug directly relevant to the current codegen drift-correction focus. Codegen CLI legacy renderer emits empty files for minimal org models A specific codegen correctness bug fitting the sprint's codegen drift-correction theme. Generate messaging registrars via codegen A scoped codegen enhancement supporting the entity commissioning pipeline that the sprint is advancing. Downgrade profile/model-type incompatibility from error to skip in –component mode Small, well-defined codegen fix directly tied to the sprint's codegen correction work. Add regression tests for domain_entity SQL template fixes Well-scoped regression-test hardening directly supporting the codegen drift-correction effort this sprint. Story: Codegen model safety guardrails Guardrails against codegen model errors align closely with the sprint's codegen correction mission. Reconcile SQL codegen template drift on synthetic validation fn A direct codegen drift-correction item explicitly matching the sprint's stated mission. Story: Commission: business_centre A refdata entity commissioning story directly matching the sprint mission. Story: Commission: business_unit A refdata entity commissioning story directly matching the sprint mission. Story: Commission: contact_type A refdata entity commissioning story directly matching the sprint mission. Story: Commission: day_count_fraction_type A refdata entity commissioning story directly matching the sprint mission. Story: Commission: party_id_scheme A well-scoped refdata commissioning story directly aligned with the sprint's refdata mission. Story: Commission: portfolio Refdata commissioning story directly matching the sprint mission with clear, bounded scope. Add RESTRICTIVE party-isolation RLS policies for the four marketdata tables A real bug causing validate_schemas.sh –strict to fail has genuine urgency and should be picked up soon. compass add component stamps #+type: component instead of ores.codegen.component Small, well-defined codegen scaffolding bug that's cheap to fix and affects every fresh component scaffold. compass should own backlog index regeneration Small, standalone tooling improvement with a clear fix path, plausible for near-term pickup. Story: compass generate catalogue: auto-generate index org files from tagged content Well-scoped tooling story already tagged for sprint_22, a plausible near-term pickup. Story: Compass GitHub Actions support Well-scoped CI tooling story with clear value and defined scope, plausible for near-term work. compass needs to support a help command Small, well-defined DX gap (no help command) that's cheap to fix and broadly useful. ores.compass Product Backlog — next and deferred listing Standalone, reasonably scoped compass command addition mirroring existing functionality. compass show needs a full-content variant Small, well-defined CLI feature gap that's cheap to address and improves everyday tooling ergonomics. compass sprint close: automate carrying unfinished stories to inbox Well-scoped automation of an existing manual workflow step with concrete near-term value. compass sprint pull: move carried stories from inbox into a sprint Counterpart automation to the sprint-close carry, well-scoped and plausible for near-term pickup. Add a compass wait-for-CI command Well-scoped, standalone CI tooling addition that's practical to build soon. Component codegen output paths use dotted {component_full}, not the nested regrouped layout A concrete codegen path-mismatch bug affecting component scaffolding, directly relevant to the sprint's codegen focus. ores.controller.service crashes with corrupted UTF-8 byte after launching a service A production crash bug has real urgency and should be prioritized for near-term investigation regardless of sprint theme. HTTP entity endpoints — top-level commissioning story Directly matches the sprint mission of commissioning ores.refdata entities via codegen (HTTP layer commissioning). Currency combo boxes should group by classification (major/minor/exotic) Small, well-scoped UI improvement on an existing refdata entity that could be picked up soon regardless of theme. Story: Decommission legacy ores.codegen bash scripts Directly aligned with the sprint's codegen C++ drift correction theme, cleaning up legacy codegen tooling. Document history diff and complete its task record Small well-defined documentation/cleanup task completing existing work, plausible to pick up soon. Document pg_notify rename as breaking change in deployment runbook Small, well-scoped documentation fix addressing a real deployment risk that has real urgency. Enforce optimistic concurrency version checks at the DB layer (remove the version=0 bypass) Well-scoped bug/robustness fix removing an unsafe bypass at the DB layer, with real urgency. Enforce process parameter validation at save/feed-start time Well-scoped server-side validation hardening item that stands on its own and has real urgency. Story: Entity evaluation skill and runbook Supports commissioning of refdata entities by building an evaluation runbook/skill, aligned with sprint mission. Entity-org scaffold should pre-populate codegen knobs Directly supports the sprint's codegen drift-correction/commissioning theme by improving codegen scaffolding. Use entity display name (not key) in detail/history window titles Small, well-scoped, standalone UI fix that could plausibly be picked up soon. The My Account password change dialog does not have a show/h… Small, well-defined bug fix (missing show/hide password toggle) with real standalone urgency. Fix ClientXModel::fetch_* pagination no-op (offset/limit never applied to request) Well-scoped systemic bug in a shared codegen template with clear fix and regen sweep, urgent and standalone. Fix batch currency generation UX and audit-field leakage Small well-defined UX/correctness bug that could be picked up soon regardless of sprint theme. cpp_enum.hpp.mustache prints 8-bit enum underlying types as raw characters Concrete, well-scoped codegen template fix directly aligned with this sprint's C++ codegen drift-correction theme. Fix missing history-window close button wiring in 7 controllers Small, well-scoped bug fix with a known pattern to replicate across 7 controllers, real near-term candidate. ClientMarketFixingModel truncates series on unfiltered page fetch Known bug pattern already fixed elsewhere (PR #1498), well-scoped and urgent data-correctness fix. Two small ref-data UI bugs: (1) market tiers has an icon but… Small, well-defined UI bug fixes in refdata, directly touching the sprint's refdata entities. Fix trading_trade_party_roles pg_notify channel name Tiny, well-scoped naming-convention fix in SQL, low risk quick win. Fix window-key separator mismatch in Workspace/SystemSetting controllers Concrete bug silently disabling staleness propagation, well-scoped and worth near-term attention. Fix notification toast blocking FX chart Y-axis area Small, well-scoped UI z-order bug fix, plausible quick win regardless of sprint theme. FX Spot chart doesn't refresh on feed binding change Concrete bug causing a chart to silently show stale/no data, well-scoped and worth near-term fixing. Gate unordered_set include in the generator template on actual need Small, well-scoped codegen template cleanup directly aligned with this sprint's C++ codegen drift-correction theme. Add CONFIGURE_DEPENDS to file(GLOB) for .ui/source forms Small, well-defined CMake fix addressing a real developer-experience build-break annoyance, low effort quick win. No cycle guard in hierarchy CTEs and build_tree() Concrete, well-scoped defensive fix flagged by multiple PR reviews with a clear test-case plan, low severity but real and actionable. IAM's party_cache is never invalidated on party changes (promoted to story) A confirmed, reproduced bug causing stale data in production-like flows (IAM cache never refreshes on party save) – real urgency, well-scoped fix. Illustrative org-roam links in doc bodies break the site build A recurring, well-scoped CI-breaking doc-authoring foot-gun with a clear fix (lint check or exporter tolerance), worth picking up soon. Improve FX Spot Monitor widget UI/UX Concrete, well-scoped UX fixes (alignment, decimals, badge) from a completed review, a standalone item that could plausibly be picked up soon. Fix instruments not visible in UI A tagged bug carried forward from a prior sprint with no acceptance criteria filled in yet, but it's a real functional defect worth prioritizing soon. lookup_entity codegen path can't generate DQ artefact tables Directly touches ores.codegen/refdata entity generation gaps – fits the current sprint's codegen-drift-correction theme and is well-scoped. lookup_entity codegen tables never get an RLS policy A concrete security gap (11/11 lookup tables missing RLS) directly in codegen for refdata entities, matching the sprint's theme and urgent from a tenant-isolation standpoint. Lower default per-service DB connection pool size A small, well-scoped operational fix with observed real-world pain (connection exhaustion across worktrees), quick to apply and plausibly pickup-able soon. Merge regenerate_backlog_indexes into compass A small, well-scoped tooling consolidation refactor (move a script into compass as a subcommand) that is standalone and easy to pick up. Merge release notes collector script into compass Small, well-scoped tooling consolidation with a clear concrete plan that could be picked up soon. Migrate ores.refdata generators to change_reason_constants.hpp Directly fits the sprint's refdata/codegen drift-correction mission. Migrate remaining refdata entities to generated event-mapping registrar Directly matches the sprint mission of commissioning refdata entities and codegen drift correction. Move compass sql under the db command Small, well-defined CLI consistency fix that could be picked up soon regardless of sprint theme. Move Portfolio's Qt CRUD UI from ores.qt/trading to ores.qt/refdata Well-scoped, standalone consistency refactor with a clear precedent already established (Book/BookStatus). Component overview models are unloadable (bare #+type, missing names) Describes an active bug that currently breaks component generation, giving it real urgency. Rebuild org-roam DB independently from CMake Small, well-defined build/devx improvement that could plausibly be picked up soon. Write org-timestamps to the build output directory Small, well-defined build hygiene fix that is easy to pick up soon. Parameterize raw SQL in the synthetic organisation publisher Small, well-scoped security hardening fix flagged by a prior PR review, worth prioritising soon. Persist per-tag colour and add a tag create/edit dialog Well-scoped, standalone UI improvement that could plausibly be picked up soon. Promote cross-tenant read to a codegen flag Directly aligned with the sprint's codegen drift-correction theme and is a well-scoped, standalone improvement. Promote recurring custom repository methods to template variability flags Codegen template variability work fits directly into the current codegen/drift-correction sprint mission. publish_from_dq codegen facet: hand-writing artefact tables is a recurring cost A codegen facet reducing recurring hand-written maintenance cost, directly relevant to the codegen theme. Qt codegen: introduce to_display_key() helper to unify UUID/string key display Small, well-scoped codegen fix that overlaps with the sprint's codegen drift-correction focus. Story: Upgrade Qt to latest supported version to fix macOS 15 AGL removal Fixes a real platform-breaking bug (macOS 15 AGL removal) with genuine urgency, already scaffolded with tasks. Add recipes for doc list commands (compass list, search, etc… Small, well-defined documentation task that could plausibly be picked up soon regardless of sprint theme. Story: Refactor ores.codegen C++ generation Directly matches the sprint mission of codegen C++ drift correction and is already scaffolded with many in-flight tasks. Centralise test target boilerplate into a shared CMake macro Well-scoped, standalone build-system refactor that could be picked up soon independent of sprint theme. Register missing refdata *_changed_event types for NATS eventing Directly touches refdata entities, aligning with the sprint's refdata commissioning focus. Fix account registration NATS SSL error A concrete bug fix with real urgency, a strong near-term candidate regardless of sprint theme. Regression test for zero-volatility GMM component Small, well-defined test-coverage gap that is a reasonable near-term pickup. Reload Qt client caches after tenant provisioning completes Well-scoped correctness fix for tenant provisioning flow with plausible near-term priority. Remove legacy pgmq extension residue from ores.compute Small, well-defined cleanup task with no large prerequisites, reasonable to pick up soon. Rename _protocol.hpp messaging files for the NATS world Small, well-scoped rename cleanup that can be picked up any time regardless of sprint theme. sccache's cache is on GitHub's built-in actions/cache, capped… Concrete CI infra limitation with real urgency (cache capacity capped) that's standalone and actionable soon. sccache daemon inherits vcpkg lock fd from cmake A concrete build-system bug fix, well-scoped and worth prioritizing soon. Script the project version bump for sprint opening Small, well-defined automation improvement to an existing recurring workflow. Separate trade and instrument detail dialogs Well-scoped standalone UI refactor that could plausibly be picked up soon. Compass command to tail and grep service logs Small, well-defined tooling addition with clear near-term utility. Compass services restart command Small, self-contained compass tooling command, easy to pick up soon. Add shell introduction to Provisioning from the Shell chapter Small, well-scoped documentation fix with no dependency blockers. Shell entity commands — top-level commissioning story Directly relevant to the current codegen/commissioning sprint theme and well-scoped as a top-level tracking story. Apply -fvisibility=hidden to ores.shell (visibility-migration straggler) Small, well-defined leftover fix completing an existing migration, easy to pick up soon. Fix skill scaffold template missing #+type and empty #+filetags Small, concrete bug fix to a template, low-risk and quick to address. Do not upload Linux/macOS debug build packages as CI artifacts Small, well-scoped CI cost/efficiency fix that can be picked up any time. compass sprint charts –output-dir is ignored by the gnuplot render step Concrete, well-scoped bug fix in an actively used tooling command. Define and regenerate the standard codegen repository method set Directly aligns with the current sprint's codegen drift-correction mission. Standardise timeline bucket generation as a compass writer (for the snapshot skill) Well-scoped standalone refactor supporting an existing skill, plausible near-term pickup. Story: Improve site documentation discoverability An already-decomposed story with concrete tasks (catalogue menu/glossary links) that is standalone and ready to pick up. Sweep missing reflectors.hpp IWYU include across entity repositories A well-scoped, standalone codegen/refdata drift-correction sweep that directly matches this sprint's mission. Sweep remaining already-commissioned entities against latest codegen templates Directly matches the sprint's mission of commissioning refdata entities and correcting codegen C++ drift. Synthetic parties are created Active, bypassing the party setup flow A concrete, well-scoped bug/design-decision item (parties bypass provisioning flow) with real near-term relevance to refdata entity correctness. task start crashes after switching to a stale branch A concrete compass bug causing crashes and unstamped journals, a well-scoped fix with real urgency regardless of sprint theme. Unify junction entity timestamp type to db_timestamp alias A codegen template drift-correction item directly aligned with this sprint's C++ codegen drift-correction mission. contact_information entities lack a NATS handler — no sub-registrar A concrete codegen/refdata gap needing a decision and fix, well aligned with the sprint's codegen drift-correction focus. Timeline snapshot agent column shows #+todo: frontmatter instead of env name A concrete, well-scoped compass display bug affecting multiple snapshot entries, a small fix worth picking up soon. Replace hardcoded timestamp sentinels with MAX/MIN_TIMESTAMP constexprs A well-scoped codegen/template cleanup touching 137 entity headers, aligning with the sprint's codegen C++ drift-correction theme. Story: Unify entity timestamp handling — throw on failure, fix optional<db_timestamp> A well-scoped, standalone correctness fix (throw-on-failure semantics, optional<db_timestamp> bug) that touches entity commissioning directly relevant to ongoing refdata work. Use badges in the history dialog Small, well-defined UI improvement to an existing dialog that could be picked up soon regardless of sprint theme. Validate GMM simulate params at request boundary Standalone input-validation fix with real correctness/robustness urgency at a request boundary. Story: Verify Windows and macOS CI builds Concrete, actionable CI verification task with real near-term value independent of sprint theme. Cache-bust site asset links at build time Small, well-scoped build-time fix (cache-busting) that is easy to pick up soon. Warn when creating account without a role assignment Small, well-defined UX safeguard for account creation with clear near-term scope. System wizard single-tenant default hostname collides with seeded Root Tenant A concrete bug in the setup wizard with real user-facing impact, standalone and well-scoped. - inbox → deferred (85)
Item Rationale ab-notebook: reproducible interest rate curve bootstrapping Exploratory research/reproducibility idea with no concrete scoped action or near-term plan. Add a link to the Claude Code settings page in the LLM docum… Body is unfilled boilerplate (no What/Why detail) so it's not concrete enough to plan soon. Add compass pr comment command for PR conversation replies Body is unfilled boilerplate with only a title-level idea, not yet scoped enough for near-term pickup. compass add sprint: automatically wire the sprint into its version Body is unfilled boilerplate with no concrete detail beyond the title, a nice-to-have tooling automation with no near-term plan. regenerate_backlog_indexes.py only rewrites inbox.org, next.… Body is unfilled boilerplate; a minor tooling gap with no urgency and not yet scoped. Badge rendering inside QComboBox selected state Explicitly says to defer until the pattern is needed in more than one place, a nice-to-have UI polish item. Book cost_center should reference a real accounts entity Speculative data-modeling redesign requiring a new accounts-domain component that doesn't yet exist, a large prerequisite not in motion. Normalize book's cost_center into a real Cost Centre entity Explicitly deferred until proper ledger support lands, a prerequisite not yet in motion. Add EOD Cut to book Explicitly deferred until proper cut support exists elsewhere in the system, blocked on an unbuilt prerequisite. Model source-book primary/secondary/tertiary relationship Explicitly deferred pending a real notion of ledger book distinct from source book, a large unresolved prerequisite. Model book_status as a workflow state, not a flat enum Large speculative workflow-modeling redesign with no immediate plan, deliberately separated from the near-term bug fix task. Introduce clang-tidy and Lizard via PR-delta ratchet strategy A tooling-adoption strategy with no near-term plan and unrelated to the refdata/codegen sprint mission. Set up clang-tidy static analysis Overlaps with the ratchet-strategy item and is a speculative tooling setup with no urgency tied to the current sprint. Story: Clear component documentation debt Broad, open-ended documentation-debt cleanup with no defined scope or urgency. Add codegen templates to generate Qt plugin class A new feature template addition rather than drift correction, with no stated urgency for the current sprint. Codegen terminology is inconsistent and misaligned with MASD… A cosmetic terminology-alignment concern with no functional urgency or concrete near-term plan. Introduce type primitive registry to replace ad-hoc type flags in codegen A large speculative internal redesign of codegen's type system, not a near-term scoped task. Story: Codegen unified model — Phase 1: derive Qt fields from conventions A multi-phase architectural redesign of the codegen model, exploratory and not immediately actionable. Commission party, counterparty, and party_status together Explicitly blocked on unresolved composite/hierarchy and temporal-versioning prerequisites not yet in motion, so it cannot be picked up soon despite matching the refdata theme. Show blocked story dependency tree in compass where A nice-to-have visualization enhancement with no urgency and no current plan to implement. compass single-environment mode for plain clones A broader UX redesign for a use case (plain clones) not currently in active use, with no near-term plan. Consider extending compass to use vector database techniques… Purely exploratory research idea into an external library with no concrete near-term implementation plan. Story: Consolidate standalone scripts into compass A large speculative redesign requiring inventorying ~61 scripts and redesigning compass pillars, not a near-term scoped item. Custom jump distributions and cross-rate correlation matrices Speculative analytics/modeling enhancement with no near-term plan, unrelated to current commissioning work. Add tag badges and filter widget to agile dashboard Nice-to-have tooling polish for the agile dashboard with no urgency or link to current sprint work. Explore diffusion models for synthetic trade generation Exploratory research idea with no near-term plan or prerequisites in motion. Dissolve ores.qt.party plugin; migrate its entities into ores.qt.refdata Large speculative restructuring of Qt plugin architecture not currently in motion, beyond immediate commissioning scope. Document hand-patched ORE vendor files against future refresh Documentation for a future, not-yet-scheduled vendor refresh event; no near-term urgency. Story: Entity manual: add shell documentation per chapter Broad documentation backfill effort across many chapters, a nice-to-have with no immediate urgency. Entity sanity/consistency checks (did-you-really-mean-X) A broader UX/validation feature idea without concrete near-term scope or urgency. Add a connection type derived from the local .env Minor tooling convenience feature with no stated urgency or dependency on current sprint work. Evaluate adding screamer to ores.analytics Exploratory technology-evaluation idea with no near-term plan. Show per-environment operational status in compass fleet A speculative devops enhancement with no near-term plan and not related to the current sprint's focus. Fold sql_schema_artefact_create into the graph (needs content-predicate activation) Explicitly deferred from B8, blocked on a larger schema-path graph migration prerequisite not yet in motion. Add pixel-stride downsampling or MA smoothing to FX line chart Nice-to-have chart enhancement with no urgency and no near-term plan. Replace stacked MDI sub-windows with QSplitter panel for FX charts Larger speculative layout redesign, a nice-to-have UX improvement with no near-term urgency. Model FX settlement type per currency pair (physical vs. NDF, business-centre dependent) A larger speculative data-modeling redesign requiring a new junction model, not yet scoped for near-term work. Gaussian GenAI: synthetic market data generation paper Exploratory research paper reference with no concrete near-term implementation plan. GitHub-style diff view in history changes tab A larger UX feature (intra-line diff rendering) that's a nice-to-have with no urgency or near-term plan. Hoist duplicated Qt chart theme colours into a shared helper Small, well-understood tech-debt cleanup but purely cosmetic/non-urgent with no dependency, fine to pick up opportunistically later rather than in immediate planning. Implement jump/Poisson stochastic process component A speculative new feature explicitly scoped out of the prior GMM story to keep it focused, with no near-term plan pulling it back in. Improve UX of Librarian dataset detail dialogs A larger speculative redesign (full layout rework with sidebar/header restructuring) based on a review, more of a bigger initiative than a quick near-term pickup. Later promoted into a sprint 23 story. Investigate sitmo/cgmm for market data simulator Explicitly an exploratory research idea into a candidate library with no concrete near-term plan to act on it. Investigate open no-auth FX spot rate sources for seeding A research/investigation task with no urgency or blocking dependency, nice-to-have for seeding convenience rather than near-term work. Properties and options visible in org-mode (e.g. right-panel…) An empty, unfleshed-out capture with no details filled in (What/Why sections blank), not yet actionable or scoped for near-term planning. Make DB connection pool size runtime-configurable The durable but larger follow-on to the pool-size mitigation, touching config plumbing across 17 services – reasonable to defer once the quicker fix lands. Handle long lines in manual with line wrapping A minor documentation-styling nice-to-have with no urgency or blocking issue, fine to defer. Market Simulator option to show data in pips A nice-to-have UX enhancement to the synthetic market simulator with no urgency, better suited to a later polish pass. Three-level hierarchy in Market Simulator config tree A speculative UI restructuring anticipating future IR-rate config types that don't exist yet, a larger redesign without immediate need. Create MASD personas and link to cybernetic levels Explicitly blocked on resolving codegen/reference-implementation drift, a documentation initiative with a stated prerequisite not yet in motion. Add a memory for the meaning of key project directories: tmp… An empty, unfleshed-out capture (What/Why blank) with no urgency, not concrete enough for near-term planning. Write the ORE Studio development methodology manual Large speculative documentation effort with no near-term plan or urgency. Mine Karpathy's wiki-based system for compass ideas Open-ended research idea with no defined near-term deliverable. Move generic quant primitives to ores.analytics Architecture refactor with no immediate driver or urgency; can wait. Story: Move trade-instrument parsing out of ores.qt.api Stale story tied to a since-closed sprint (19) with an ABANDONED todo state option, indicating no active near-term plan. Detect and report NATS disconnection Carried forward from an old sprint with no active plan and not urgent enough to displace current work. ORE sample data Long-carried, open-ended data sourcing effort from a prior sprint with no concrete near-term plan. ores.diagrams — PlantUML/SVG diagram generator (C++, SQL, org-mode) Large speculative new component with no near-term plan. ores.diff: structured topology for nested entities Explicitly deferred by its own description until a first nested-entity consumer materialises. Work through all types required for ORE Example 1 Large, long-carried exploratory effort from a prior sprint with no active near-term plan. Tangle dataset manifest and methodology from org Nice-to-have documentation/tooling improvement with no urgency or near-term driver. Define what a product vision is before stating ORE Studio's Exploratory conceptual/vision work with no near-term plan or dependency on current sprint work. Accumulate a tagged face dataset for profile pictures Long-horizon data-accumulation idea with no urgency or current dependency. Persistent test-context widget for the Qt client, seeded at launch A nice-to-have developer-experience feature with no urgency and unrelated to the current sprint theme. Qt: instrument creation in TradeDetailDialog A sizeable standalone Qt feature unrelated to the current refdata/codegen sprint with no stated urgency. Redesign how currency_pair.deliverable/settlement_currency are derived A speculative larger redesign of derivation logic without an immediate plan or driving urgency. Rename compass to something like swiss knife A speculative naming/branding idea with no urgency or concrete near-term plan. Rename or split the project glossary A nice-to-have documentation reorganisation with no urgency and unrelated to the current sprint. Story: Rethink synthetic reference-data generation across entities An exploratory cross-entity redesign of synthetic generation with no concrete near-term plan. Compass search: self-improving mode for failed queries Speculative research feature (self-improving search) with no near-term plan or urgency. Split the user manual into Qt and Wt manuals Large speculative documentation restructuring with no near-term trigger or urgency. Consolidate message boxes into one non-modal, copiable, standard-button ORE Studio dialog A larger cross-application UI consolidation effort without an immediate driver, better suited to a future planning cycle. On-demand PR and CI overview panel on story cards A speculative dashboard UI feature unrelated to refdata/codegen with no urgency or near-term plan. story new: support content flags and first-task control A tooling nice-to-have improving compass ergonomics, not urgent and not tied to current sprint work. SVG diagram viewer — interactive JS wrapper for ores.diagrams SVGs Explicitly depends on a prerequisite (ores.diagrams) not yet in motion, making it a longer-horizon item. History and change-eventing for synthetic config entities A sizeable feature addition to synthetic config entities with no immediate urgency or direct tie to the current sprint theme. Synthetic FX generation should respect currency pair conventions A data-quality enhancement to synthetic generation that is standalone but not urgent and not aligned with the codegen/refdata drift focus. Synthetic service active configuration selection An open-ended mechanism-design item for the synthetic service with no concrete near-term plan. Task: Document the composite versioning approach and codegen recipe Explicitly blocked on the mechanism being fully implemented and proven first, so not yet actionable. Task: Qt composite history/version dialog Explicitly blocked_on another unfinished task providing the widgets it needs to build on. Codegen gap: service application.cpp eventing pipeline not generated for new entities Names a longer-term codegen target as the real fix, with the interim hand-wiring being a separate simple task; the described work here is exploratory template design without a concrete near-term plan. Story: Move trade import orchestration to service layer A larger architectural refactor for trade import with no direct tie to the current refdata/codegen sprint and no indicated urgency. Trim compass bearings: –limit and heading integration A tooling/UX improvement to compass bearings that is nice-to-have but not urgent or blocking current work. Unify Account and Administration menus into a single menu An exploratory UX investigation item ('investigate how other systems name these') with no concrete near-term plan. Wt entity UI — top-level commissioning story Explicitly scoped to be picked up only after all entities are commissioned, making it a large, prerequisite-blocked horizontal restructuring not ready for near-term planning. - next → deferred (88)
Item Rationale Add a dashboard for users Large, loosely-scoped UI feature backed only by rough screenshot mockups and open-ended notes, not ready for imminent planning. Add a generic tagging system A cross-cutting generic tagging capability spanning multiple entities is a speculative, larger-horizon design not yet scoped for near-term work. Add a message queue Adding a new message-queue infrastructure component is a significant architectural undertaking still at the exploratory/linked-article stage, not near-term ready. Add batch editing with staging workflow Exploratory UX idea still needing terminology and iconography decisions before it is even well-scoped. Add counterparty party scoping (librarian Phase 2) Explicitly blocked on the publication_params_schema story merging first, which is itself not yet in motion. Add database support for tests Open-ended exploratory infrastructure idea (test telemetry DB design) with no concrete near-term plan. Add entity related charts "Have a think" brainstorm of possible chart ideas with no concrete scope or plan yet. Add HBAC support for books and portfolios Large speculative access-control redesign (hierarchical RBAC with groups/ACL inheritance) with no near-term plan. Add heat map of user sessions Exploratory analytics idea blocked on a session table and further research ("mine github for ideas"). Add high-watermark support Still requires design analysis ("do some analysis with Claude on how best to do this") before it is a concrete, pickup-ready item. Add ISO 20022 Support Large speculative messaging-integration effort spanning multiple ISO 20022 message types with no concrete near-term plan. Story: Additional market data producers (e.g. Bloomberg) Future vendor-integration epic proving architecture genericity, with no concrete near-term driver. Add KYC workflow for counterparty onboarding Large compliance workflow requiring integration with a four-eyes authorisation framework not yet built, so it is not near-term ready. Add ores.compute or ores.grid Large speculative new-component epic (BOINC-style financial compute grid) with no near-term plan. Add party level currency and country restrictions Explicitly framed as a partial/experimental RLS framework exploration ("won't be able to do a full implementation right now"), not a near-term concrete item. Add purge button to all entities A cross-cutting UI/permission feature affecting all entities with no clear near-term driver or design decided yet, best refined later. Add self-registration and approval for production tenants A large speculative workflow (self-service tenant onboarding with approval queue) with no near-term plan or prerequisite in motion. Add sign-up approval workflow Vague, underspecified workflow feature (invite codes etc.) with no concrete near-term plan. Add skill to improve UI design Vague aspirational goal ('make UI more professional') with no scoped deliverable, better suited to longer-horizon exploration. Add sound assets A nice-to-have cosmetic feature (event sounds) unrelated to current priorities and not urgent. Add staging support Explicitly a preparatory step for a not-yet-built authorisation queue framework, i.e. blocked on a large prerequisite not in motion. Add support for row signing A speculative security/audit feature ('would be good to have') with no concrete scope or urgency. Add trace context propagation to messaging protocol Cross-cutting distributed-tracing infrastructure work with no near-term driver, more of a longer-horizon platform investment. Add "uptime" screen An exploratory UI idea referencing external inspiration with no concrete scope defined yet. Add version comparison and revert improvements Vague, unscoped set of 'improvements' to versioning/history with no concrete near-term plan. Add virtual portfolio tree support A large speculative reporting/aggregation redesign unrelated to the refdata sprint and not yet scoped. Analyse caching at dialog level This is an open-ended architectural exploration (immer-based workspace caching layer across Qt/Wt/shell clients) with no concrete near-term plan, fitting the deferred/large-speculative-redesign profile. Analysis on database name service A one-line exploratory question ('is this used?') with no scoped action, i.e. research with no near-term plan. Consider adding an "entity waterfall" Speculative UX feature ("it would be nice") with no concrete scope or plan, purely exploratory. Consider adding log command line options to qt Phrased as a "maybe" idea to explore rather than a committed near-term change. Consider adding MCP support Research-stage idea sourced from an external course with no defined scope or near-term plan. Consider using UUID in the database layer Large speculative cross-cutting redesign of the database layer's type representation, not shovel-ready. Story: Correlations and derived volatility surfaces Explicitly scoped as future work under a not-yet-started Market data generation epic, no near-term plan. Create a AAD build of ORE Explicitly flagged as "requires further investigation", a research prerequisite before any real work can start. Create named profiles A larger speculative UI/window-management feature with no immediate urgency or concrete near-term plan. Create shared object interfaces Large speculative redesign of the shared-object/DLL build architecture with no near-term trigger. Create span collection and export infrastructure Sizable new telemetry subsystem with no current driver or dependent work in flight. Create subsets of datasets Explicitly unresolved design question ("or maybe these are just separate datasets?") with no concrete scope. Currencies: Contractual Settlement (The "Agreements" Table) Speculative large modeling exercise for a new settlement/agreements domain concept, not yet designed or prioritized. Currencies: Party-Specific Settlement Rules Large speculative domain-modeling exercise for party-specific rules with no concrete near-term plan. Digital signatures Large speculative security feature with no near-term plan or scoping, unrelated to current work in flight. Evaluate change reasons for role permission tables Purely exploratory analysis item ('should we…') with no concrete implementation plan or urgency. Event Viewer advanced features Explicitly a collection of nice-to-have features beyond the initial implementation, not prioritized or urgent. Extend ores.workflow: trade-expiry workflow A large multi-step new financial workflow feature tied to a separate long-range plan, not near-term standalone work. Faker with seeds Terse, unscoped capture with no clear near-term plan or urgency, more of a nice-to-have testing infra idea. Financial workflows: trade-expiry and barrier-event Large speculative financial-workflow feature with no concrete scope, unrelated to current refdata/codegen focus and not urgent. Fine-tune grants for each service account Terse capture describing a broad security hardening effort with no immediate scope or urgency signaled. Fix "informations" plural naming in contact information entities Cosmetic naming cleanup with no urgency and only a one-line description, not blocking anything. FX trade UX improvements: tabs, currency pairs, rate computation Multi-part UX redesign of FX forward product, unrelated to current sprint and sizable enough to be speculative rather than immediately actionable. General session dialog Vague one-line capture with no defined scope or urgency, needs clarification before it can be planned. Generate C++ code for FPML Large speculative codegen effort with no concrete scope beyond a title, more exploratory than near-term despite codegen theme overlap. Generate protocol docs via codegen Thin, unscoped capture describing a nice-to-have tooling idea with no near-term plan. Replace hardcoded permission strings with per-component constants A codebase-wide refactor with clear scope but no urgency or blocking issue, better suited to a later cleanup pass. Implement entity history in shell Terse, unscoped feature capture with no near-term plan or urgency indicated. Implement four-eyes authorisation framework Large speculative authorization-framework redesign with only a title, clearly a longer-horizon initiative. Improve error message boxes Vague, unscoped UX nice-to-have with no urgency or detail to act on soon. Investigate dashql for ideas Purely exploratory research into a third-party project for inspiration with no concrete plan or scope. Local versus remote connectivity Large speculative architectural change (dual local/remote and sqlite support) with no near-term plan or prerequisites in motion. Long-running bundle publishes need progress reporting and async execution Requires a nontrivial async-execution and progress-reporting redesign spanning server and client, not a near-term standalone pickup. Make UI/UX look more professional Vague, open-ended aesthetic overhaul with no concrete scope or near-term plan. Management of roles Explicitly calls for analysis of the best design approach before any implementation, i.e. exploratory with no near-term plan. Mine dexter for ideas Purely exploratory idea-mining task with no concrete near-term deliverable. Missing shell functionality Broad, open-ended ambition to exercise the entire comms protocol via CLI, lacking a concrete near-term scope. Modes of operation Explicitly needs a stakeholder discussion before any design decision, i.e. exploratory with no near-term plan. Notification of deletes Describes an open design problem ("one way to do this is…") requiring further exploration before implementation, not yet well-scoped. Add party explorer Still a bare template with no fleshed-out What/Why and no connection to the refdata/codegen sprint mission, so it's speculative UI exploration rather than near-term work. Portfolio types Just a one-line idea to generalise virtual/non-virtual portfolios into a type with no acceptance criteria or scoping, and unrelated to the current refdata/codegen focus. Add pricing model parameter validation table Still an unfilled template (What/Why sections blank) representing a larger speculative validation-table redesign with no near-term plan. Recipes do not show variables in org-babel A nice-to-have documentation/tooling polish item with no urgency and no concrete plan of attack (just links to explore). Redesign Qt ImageCache invalidation strategy Explicitly noted in the capture itself as blocked pending a move to workspaces, a large prerequisite not yet in motion. Reduce duplicated Qt code and clean up technical debt A grab-bag of loosely related cleanup ideas with no single well-scoped deliverable, more of a nice-to-have eventually list. Reduce messaging handler boilerplate Still an unfilled template with no concrete What/Why detail, a speculative architecture refactor with no near-term plan. Remember dialog sizes and positions Small nice-to-have UX polish item with no urgency and no scoping beyond a one-line idea. Restore detached window state after login A well-described but large, speculative UX feature (multi-monitor detached window persistence) with no urgency and not tied to current priorities. Restore detail and history windows after login Explicitly described as significantly more complex than the list-only restore, making it a larger speculative UI feature with no near-term plan. Retrieve NAT'ed IP address from local IP A speculative 'would be nice' infra idea with no defined scope or urgency. Review of Wt An open-ended exploratory review/research item rather than a scoped actionable task. Service command-line configuration dialog with bitemporal support A sizable new feature (dialog plus bitemporal audit history) with no near-term urgency or alignment to the current sprint. Standardise Qt window behaviour and UI consistency Described only as 'several inconsistencies' with no enumerated scope, indicating a broad speculative UI redesign rather than a scoped near-term item. Tracing: OpenTelemetry identifiers across Qt and NATS Tagged as analysis/background research with no concrete near-term implementation plan. Trade-aware market data filtering for report execution A sizable workflow redesign proposal (filtering market data fetch by trade relevance) with no near-term scoping or urgency indicated. Triage existing sprint capture.org files Blocked on the per-file capture workflow being in place first, and is agile-process cleanup with no urgency, so it is a longer-horizon item. UML class diagrams are missing relationships between classes… A documentation nice-to-have with no urgency or direct sprint connection; not standalone/prioritized enough for near-term pickup. Understanding Settlements and SSI An open-ended research/analysis task on a complex domain topic with no concrete scope or near-term plan, fitting the exploratory-deferred criteria. Unify compute wrapper nodes as replicated services A speculative infrastructure redesign of compute wrapper nodes with no immediate driver or scoping, better suited to longer horizon. Update timestamps to use timezone Vague, unscoped placeholder capture with no concrete plan or urgency evident from its content. User interface options An open-ended tracking list of future UI configuration points rather than a scoped near-term item. Users should be able to add picture to profile A nice-to-have UI feature with no urgency and no direct bearing on current priorities. - deferred → next (14)
Item Rationale Add serialisation tests for analytics domain types Small, well-scoped, standalone test-coverage item that could be picked up soon regardless of sprint theme. api and core are not namespaces — fix naming A concrete, well-defined naming/correctness fix with real near-term value, not a speculative idea. Convert CODE_OF_CONDUCT.md and CONTRIBUTING.md from Markdown to org Small, well-scoped documentation conversion that could plausibly be picked up soon. Implement missing equity instrument types Concrete, well-scoped domain-coverage gap that is a real near-term candidate. Support expiry date shorthand with calendar integration Concrete, well-defined feature with clear near-term applicability, not merely speculative. Implement missing FX instrument types A well-scoped, standalone list of concrete missing instrument types that could be picked up as normal feature work regardless of sprint theme. Replace optional JWT verifier with explicit modes A small, well-defined security/clarity fix (optional -> enum mode) that is standalone and could be picked up soon. Rename the Knowledge Graph menu item to Knowledge Small, concrete, well-scoped UI/nav change that could be picked up quickly regardless of sprint theme. Simplify verbose handler log names Small, well-defined codegen/logging cleanup affecting generated templates, standalone and low-risk to pick up soon. Review pricing engine type tenant vs party design A small, well-defined design review question about an existing entity's FK/tenant defaulting, plausible to pick up soon. Rename the modeling/ directory to docs/ in all components A small, mechanical, well-scoped rename across components that could be done quickly whenever convenient. Replace parent entity combo box with server-side searchable widget This is a well-scoped, standalone fix for a real data-truncation bug (silent 1000-row limit) with clearly identified affected code sites, making it a plausible near-term pickup regardless of sprint theme. Setup code quality actions Flags a real security gap (secret scanning didn't catch a planted test password) plus a broken CI build, giving it genuine urgency as a near-term infra fix. Windows WiX installer: break through the v3 size and file-count limits This is an active, currently-blocking packaging issue on Windows builds with prior attempted fixes documented, giving it real urgency for near-term work.
Outcome
| Bucket | Before | After |
|---|---|---|
| inbox | 208 | 0 |
| next | 224 | 273 |
| deferred | 56 | 215 |
inbox is empty of pre-existing items, satisfying the acceptance
criterion. Notably, more items ended up in deferred (215) than
next (273 is still larger, but deferred nearly quadrupled) —
consistent with inbox having accumulated years of speculative/
research/nice-to-have ideas never triaged, most of which are
genuinely long-horizon rather than near-term candidates.
Scope note
Scoring rubric explicitly did not require sprint-23-theme fit as
the sole next criterion — a well-scoped bug fix or standalone
improvement was scored next on its own merits (urgency, standalone
scope, readiness), not only if it matched the refdata/codegen theme.
This avoided the failure mode the skill's own Step 5 warns against:
demoting everything that isn't this sprint's specific theme to
deferred, which would make next useless for the following
sprint's planning session.
No per-item spot-check of all 310 moves was performed given the volume — this is a scope/thoroughness trade-off worth flagging, not a silent gap: a sample-based trustworthiness check (à la the deep refinement's discard check) would be a reasonable addition for a future run at this scale.