Prioritized learning backlog

Implemented and bounded

The fictional Northstar sample supports conversational task-title and code matching, ambiguity prompts, direct Status and Owner controls, readable previews for task updates, bulk completion, Reset, and Undo, Confirm/Cancel/Escape behavior, versioned local persistence, briefing views, responsive layout, and technical checks. Clear chat only clears the conversation transcript; it does not modify task data. These are implemented prototype flows, not production commitments.

Next: test the safety premise

1. Run the proposed five-participant study. It is the dependency for feature work because it tests whether people distinguish a proposal from an applied NTH-104 update and can recover a mistake.
2. Score the study protocol and revise preview language, task naming, or recovery controls if two participants repeat a critical misunderstanding.
3. Test keyboard-only and screen-reader use of the same preview contract before adding new interaction breadth.

Deferred pending evidence and controls

Filtering is deferred until sessions show which board views people cannot obtain from the current workspace. An audit-history prototype is deferred until the local safety pattern is understood. Live task-system integration, open-ended AI, permissions, notifications, due-date editing, and shared state require privacy, authorization, reliability, support, operational cost, and evaluation decisions. This ordering supplies no dates, assignees, release commitments, or adoption claims.