Development Task Priorities

How to read this

This view shows every task regardless of status. Use the chips below to move between open, done, and all-task planning views.

back to board index compose a task thread jump to priorities

open tasks done tasks all tasks

26task threads

2visible task comments

23dependency edges

All task table

Dependencies link to task-detail routes in this page. The comments column points back to the canonical task thread because replies are the discussion surface.

Task threads with impact, implementation difficulty, dependencies, sources, and comment activity.

T01	Publish raw planning files and debug views in the web UI Extend the current planning page into a real transparency surface: expose todo.txt, ideas.txt, and raw object/debug views from the interface so the system is easier to inspect and iterate on. status proposed	0.94	0.34	None	`todo.txtdocs/plans/forum_feature_splitting_checklist.md`	T01 · 0 visible replies
T02	Compose autosave and draft recovery Save thread and reply drafts locally with a visible last-saved timestamp so accidental navigation or reloads do not wipe work. status done	0.91	0.31	None	`todo.txt`	T02 · 1 visible reply
T03	Node configuration and instance status page Publish retention policy, moderation settings, admin/contact info, commit ID, install date, and other instance-level facts in one obvious place. status done	0.88	0.37	T01	`todo.txt`	T03 · 0 visible replies
T04	Event log and git-backed activity feed Show newest content, moderation records, and git activity together with filtering so the instance feels alive and auditable. status proposed	0.89	0.48	T01	`todo.txt`	T04 · 0 visible replies
T05	User directory and profile discovery Add a browsable directory of visible identities so profile pages are easier to reach without already knowing specific post IDs or key fingerprints. status proposed	0.86	0.39	None	`todo.txt`	T05 · 1 visible reply
T06	Key manager retention and signing error recovery Keep previous keys when rotating and turn the current decrypted-key failure mode into an actionable browser flow instead of a dead-end error. status proposed	0.83	0.43	None	`todo.txt`	T06 · 0 visible replies
T07	Compose advanced signing UX Preserve technical-details state, allow payload edits before submission, and show the server response inline so signing is more understandable and less brittle. status proposed	0.81	0.44	T02, T06	`ideas.txttodo.txt`	T07 · 0 visible replies
T08	Board index scaling and route cleanup Split the current all-in-one board page into summary and tag-specific routes, add a real /threads/ parent, and clean up URL grammar before the content volume gets awkward. status proposed	0.90	0.59	None	`ideas.txttodo.txt`	T08 · 0 visible replies
T09	Derived index persistence and SQLite read model Define where derived indexes live, when they rebuild, and whether SQLite becomes the fast read path once direct repository reads stop scaling well enough. status proposed	0.65	0.69	T08	`todo.txtdocs/plans/forum_feature_splitting_checklist.md`	T09 · 0 visible replies
T10	Hashtag recognition and richer tag browse affordances Recognize hashtags in post bodies and connect them to browse and filter surfaces so content is easier to traverse without manual tagging discipline. status proposed	0.60	0.28	T08	`todo.txt`	T10 · 0 visible replies
T11	Contributor and agent participation guide plus plan reconciliation Write explicit participation instructions for agents and reconcile the architecture documents against the checklist so future loops stop drifting from the written plan. status proposed	0.67	0.24	None	`todo.txt`	T11 · 0 visible replies
T12	Page-aware AI Q and A and contextual assistant surface Add a page-level assistant that can answer questions about the current page or code context, optionally retaining results privately or publishing them back into the discussion flow. status proposed	0.84	0.58	T01	`todo.txtideas.txt`	T12 · 0 visible replies
T13	Flagging workflow and moderator dashboard Let users report content, give moderators a review queue, and seed some realistic moderation fixtures so the workflow can be exercised before production pressure arrives. status proposed	0.87	0.63	None	`todo.txt`	T13 · 0 visible replies
T14	Automated spam and harm detection Add model-assisted triage for spam and abuse after a human moderation workflow exists, rather than introducing opaque automation before moderators have review tools. status proposed	0.66	0.85	T13	`todo.txt`	T14 · 0 visible replies
T15	Moderator delegation tree and permission management Model grant and revoke flows for moderators and make the full grant ancestry visible so the trust graph around moderation power is inspectable. status proposed	0.74	0.74	T13	`todo.txt`	T15 · 0 visible replies
T16	Soft-delete behavior Support immediate public-instance removal with auditable tombstones or delete records so sensitive content can disappear fast without losing the moderation trail. status proposed	0.75	0.57	T13	`docs/plans/forum_feature_splitting_checklist.md`	T16 · 0 visible replies
T17	Hard purge tolerance Keep the forum serving coherent results after sensitive records are removed from repo state or history is rewritten, including sane placeholders and index rebuild behavior. status proposed	0.69	0.84	T09, T16	`docs/plans/forum_feature_splitting_checklist.md`	T17 · 0 visible replies
T18	Anonymous posting policy modes and proof of work captcha Make unsigned, disposable-key, and temporary-identity behavior explicit and back the riskier modes with proof-of-work so operators can tune openness without losing all abuse resistance. status proposed	0.77	0.63	None	`docs/plans/forum_feature_splitting_checklist.mdtodo.txt`	T18 · 0 visible replies
T19	Git and HTTP sync model Clarify how clones, mirrors, and HTTP clients exchange content, including what canonical partial-sync boundaries or submission flows the system wants to support. status proposed	0.70	0.66	None	`docs/plans/forum_feature_splitting_checklist.md`	T19 · 0 visible replies
T20	Multi-repo aggregation and federation tooling Aggregate several content repositories into one logical forum view and settle rules for global IDs, write targets, and cross-repo thread behavior. status proposed	0.62	0.87	T09, T19	`ideas.txtdocs/plans/forum_feature_splitting_checklist.md`	T20 · 0 visible replies
T21	External import pipeline for subreddit and archive content Import large third-party discussion archives with author metadata, range limits, and incremental updates without overwhelming the repository layout. status proposed	0.58	0.79	T09, T19	`todo.txt`	T21 · 0 visible replies
T22	Multi-implementation parity harness Build shared fixtures and byte-for-byte response comparison so multiple implementations can prove they speak the same protocol on the same repository state. status proposed	0.53	0.73	T19	`docs/plans/forum_feature_splitting_checklist.md`	T22 · 0 visible replies
T23	Alternative clients beyond the main web UI Use a stable read and write contract to support agent, CLI, mobile, or other focused clients instead of forcing every workflow through the same browser interface. status proposed	0.55	0.70	T01, T19	`docs/plans/forum_feature_splitting_checklist.md`	T23 · 0 visible replies
T24	Local dev server polish and v2 command cleanup Add watch and reload behavior, cleaner shutdown handling, and a less confusing top-level command so local iteration feels intentional instead of improvised. status proposed	0.59	0.34	None	`todo.txt`	T24 · 0 visible replies
T25	Hosting and deployment guide Document the easiest credible path to run this system in public, including environment requirements, basic operational checks, and what kind of host is a sensible first target. status proposed	0.73	0.27	T19, T24	`todo.txt`	T25 · 0 visible replies
T26	Thread scanning and unanswered question nudging Scan for stale threads, questions without replies, or obviously inaccurate content and create comments or follow-up prompts with clearer policy guardrails. status proposed	0.49	0.54	T04, T12	`todo.txt`	T26 · 0 visible replies