Skip to content

RE design: rebuild the inventory from the project owner's assessment - #114

Merged
dwolfson merged 1 commit into
mainfrom
re/inventory-classic-to-next
Sep 17, 2026
Merged

dwolfson merged 1 commit into
mainfrom
re/inventory-classic-to-next

Conversation

@dwolfson

Copy link
Copy Markdown
Owner

Summary

Docs-only. Adds INVENTORY-CLASSIC-TO-NEXT.md, rebuilding the classic-vs-/next feature inventory from the project owner's own hands-on assessment rather than a vocabulary-comparison script (which missed Automate, Understanding, Activity, work lists and RFAs).

Recovered from re/restore-unbuilt-stages-defect-doc, where it landed as a follow-on commit while that branch was checked out in the shared main checkout (already merged as #112) — split out here since it's unrelated content, no code changes.

🤖 Generated with Claude Code

My screen was worse than useless and this replaces it. It compared
subsystem vocabulary counts between index.html and next/, found sixteen
candidates, and missed Automate, Understanding, Activity, work lists and
RFAs -- four of which appear in /next as labels, and one of which appears
44 times while being unreachable. A count of occurrences cannot tell
wired from present. The method that worked is the one the owner used:
open the UI and try to do the job.

Now organised by the owner's ten points, with citations where I verified
and a note where I did not.

Decision (project owner, 2026-09-17): roughly half done on repositories,
and other resource types are not worth looking at until repositories are
finished.

One thing I could add. Work lists are orphaned at exactly one point:
web/routes/work_lists.py exists, next/worklist.js is 89KB and exports
renderWorkListPane at :170, renderWorkListNav is called at app.js:609,
and the state fields exist -- but renderWorkListPane is never called
anywhere in app.js and is not among the names imported at :26. Complete
at both ends, unwired in one place.

Also records that item 10, RFAs, is the only deferral in the list a user
can actually see -- app.js:601 links out to the current UI and says so.
It is the model the six stages in DEFECT-UNBUILT-STAGES-RENDER-AS-BUILT
were supposed to follow, and until that defect lands no statement about
/next's completeness can be read off the UI at all.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FHWHqQMuENjYSCHTVDPg9i
Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
@dwolfson
dwolfson merged commit 457efd0 into main Sep 17, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant