Asset Atlas spec, user guide, and a full screenshot refresh - #50
Merged
Conversation
- docs/specs/asset-atlas-spec.md: Phase A (v0.4.5, shipped) documented, plus the proposed path from picture to planning surface — Phase B focus mode (lens thresholds that select, not just color), Phase C transitive blast radius (click-to-pin, depth control, a who-to-notify rail computed client-side from shipped edges), Phase D plans started from the map (multi-select targets with live union blast radius, pre-filled plan creation). Explicit non-goals: no stored layout or annotations (derived-not-drawn is what keeps the map from rotting), no graph editing on the map, no runtime topology. Phases left unversioned, sequenced behind asset-record reconciliation. - docs/guides/asset-atlas.md: user guide — the three views, lenses, edge-style legend, blast-radius hover, where each pixel's data comes from, and a pointer at the spec's future phases. - Docs site: guide + spec cards added. - All eight pre-Atlas tour screenshots recaptured — they predated the Assets sidebar entry; every shot now shows the current shell. - README roadmap and app-spec link the new spec. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y7FhGxYjnJHJ7m9MpH2dgJ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the Atlas roadmap ideas as a proper spec, adds a user guide, and refreshes every docs-site screenshot to the current shell.
New spec —
docs/specs/asset-atlas-spec.mdPhase A (v0.4.5, shipped) summarized for reference, then the proposed path from picture → instrument → planning surface:
warning+,debt ≥ 25/50,active/quiet); matching nodes full-strength, neighbors half-dimmed for context, the rest collapse to dots. Grid/Table honor the same threshold as a plain filter.direct · +2 · full closure); downstream (who breaks) visually distinct from upstream (who I lean on); a "who to notify" side rail grouped by depth with owners and impact paths. Computed client-side by BFS over already-shipped edges — no new queries.get_asset_map) lands with C/D, not before.New guide —
docs/guides/asset-atlas.mdThe three views, the lenses, the edge-style legend, blast-radius hover, and a table of where every pixel's data is maintained — plus a pointer to the modeling guide for sparse maps.
Docs site & screenshots
Docs-only change (no app code); tests 201 passing.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Y7FhGxYjnJHJ7m9MpH2dgJ
Generated by Claude Code