Files
DemonGatanjieu-Anomalous_Mo…/docs/architecture
DemonGatanjieuandClaude Opus 5.5 47ca8a764a Walk a newcomer through the AI workbench once, and say a line under what shows up later
Step 5 of the lower-barrier plan: notes, never paragraphs on the page. The first time the workbench
shows a task, once its window has settled, the spotlight tour walks through New task, Connect an AI,
the gates, the list, a task's menu, the timeline and the message box (ui_ai_tour.js); the home
section's "How it works" runs it again. What only shows up after the AI has done something gets
one line with Got it the first time it appears: under a run's verdict, beside the undo of the AI's
canvas changes, under a private task's message box with Hide. Seen ones are remembered in this
browser only.

The tour engine now skips a target folded to nothing (a tab not shown) and lights only the visible
part of a tall one (the timeline), cut to its scrolling box and the window. The task menu button
has a class of its own to be found by.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 02:57:47 +08:00
..

Architecture Topic Guide

Start with the repository-root ARCHITECTURE.md, then open only the topic needed for the current task.

  • ui-flows.md: the UI map's hand-written part, in Chinese: what each part of a page is for, what a click does and why, and one name per thing (a glossary the structure check enforces). Where a word on screen is drawn and what it calls comes from the code: node tools/ui_map.mjs find <words> (tools/ui_map.mjs, its index tools/ui_map_scan.mjs; build writes the whole map to the untracked docs/ui-map.md).
  • backend.md: Python routes, filesystem safety, persistence, scan state, model sidecars, and backend performance.
  • frontend.md: extension bootstrap, UI ownership, localization, media lifecycle, panel state, and graph mutations.
  • recipes.md: Workflow Recipes, packages, galleries, Parameter Notebooks, prompt roles, and recipe-to-model transitions.
  • material-library.md: saved prompts and node values (material files), keeping an output image, and dragging prompts onto the canvas.
  • recipe-model-lifecycle.md: authoritative model fields, Hash synchronization, local matching, partial append, and note privacy.
  • model-resolution.md: model provenance, Model Check, hash injection, model scanning, and recovery policy.
  • ../decisions/README.md: concise records of product and architectural decisions that still explain current behavior.

These documents describe current contracts rather than implementation history. For exact changes, use Git history. For user-visible releases, use CHANGELOG.md. For recurring implementation traps, use lessons.md.