Render a descendant-aware scope dashboard

[timeleft--]

Important

Bounded operator-use amendment - July 10, 2026

This is the sole active Rich Views implementation slice during the WisdomLoop spike. Its accountable user is Younes during daily context re-entry and review. Completion must be demonstrated in real use; it does not automatically authorize thought-detail, lineage, relationship, search, or broader renderer work.

Parent

Parent PRD: #51

What to build

Render a descendant-aware scope dashboard in the local FAVA reader.

The dashboard should let an operator open a known FAVA scope and quickly understand the shape of that scope and its child scopes without reading full thought bodies. It should emphasize compact records, counts, lifecycle state, source type, tags, agent provenance, confidence, and recent activity.

The dashboard should consume generated route metadata or a shared route helper rather than hardcoding thought URLs. Until canonical slug routes are introduced, dashboard links should use the /id/<UID>/ fallback route from #52 and must not use bare UID routes.

Acceptance criteria

• A scope dashboard route renders records from the requested scope and descendant scopes.

• The first viewport shows compact summary counts for thoughts, child scopes, active decisions, drafts or proposed records, and supersessions.

• The dashboard separates or filters by namespace, source type, validation status, tags, and agent.

• Thought summaries show human-readable titles while preserving ULID-backed identity and links.

• Dashboard links use generated route metadata or a shared route helper; they do not hardcode bare UID routes.

• Until canonical slug routes exist, dashboard thought links use /id/<UID>/.

• Dashboard rows or cards show status, source type, confidence, tags, age or created time, scope, and relationship count where available.

• Dashboard summaries use excerpts and do not render full Markdown bodies by default.

• Fixture coverage verifies descendant-scope inclusion, dashboard counts, and dashboard links using the expected route metadata.

• The dashboard is served through the local CLI server path from Serve the all-scope FAVA reader locally from the CLI #53.

• The operator uses the dashboard in at least five real context re-entry or review sessions and records whether it reduced raw-file opening or manual context reconstruction.

• The result records what remained hard to inspect and makes an explicit continue, revise, or stop decision before any later Rich Views issue is reactivated.

Blocked by

• Generate a minimal FAVA reader from source records #52
• Serve the all-scope FAVA reader locally from the CLI #53

[timeleft--]

Paused by MachineWisdomAI/WisdomLoop#35 and its five-task pilot. Minimum FAVA truth/readiness work in #72, #73, and #74 now precedes renderer and search expansion. The ready-for-agent label is removed so automated intake cannot start this work during the pilot.

Resume only if the pilot identifies human or agent retrieval as a measured bottleneck. The existing specification remains preserved as prior design context.