Skip to content

docs: memory-doc drift — architecture.md lists 2 deleted modules, 9 flow docs describe removed surfaces, 26 point at moved paths, index hygiene #2494

Open

Description

@vybe

Summary

The memory docs have drifted from the tree in three distinct ways: architecture.md still catalogs two modules that no longer exist, nine feature-flow docs describe surfaces that were removed, and 26 more flow docs reference paths that moved or were renamed. Plus index hygiene: six flow docs are not linked from feature-flows.md and three index rows point at deleted docs. One sweep, three kinds of fix.

Context

Found by the forgotten-areas archaeology scan (doc path references cross-checked against the tree, resolving sub-project-relative paths first so frontend/MCP shorthand is not counted as missing). Complements #2238, which covers architecture.md count drift and invariant gaps but not these catalog entries or the feature-flow layer.

1. architecture.md names modules that are gone — FIX

  • routers/alerts.py — listed under Monitoring & Operations ("Cost threshold alerts"); the file does not exist.
  • services/scheduler_service.py — listed in the Services catalog and the Background Services table ("APScheduler-based scheduling"); the file does not exist. Scheduling lives in the standalone src/scheduler/ package.

2. Flow docs describing removed surfaces — ARCHIVE (move to docs/archive/feature-flows/ and drop from the index)

Doc What it describes Why it is obsolete
agent-network.md Vue Flow graph mode (AgentNetwork.vue, AgentNode.vue, SystemAgentNode.vue, collaborations.js) Graph mode decommissioned in #1689
alerts-page.md routers/alerts.py, Alerts.vue, stores/alerts.js, CostAlertsPanel.vue None of the five files exist
events-page.md views/Events.vue /events is a redirect to Operations (#1109)
agents-page-ui-improvements.md views/Agents.vue, AgentNode.vue Agents page retired into the Dashboard List view (ent#260)
session-tab.md SessionPanel.vue, e2e/session-tab.spec.js Session surface absorbed by the Workspace (ent#358)
tag-clouds.md TagClouds.vue Component gone
operating-room.md Alerts.vue, Events.vue, Executions.vue, Monitoring.vue, CostAlertsPanel.vue, stores/alerts.js Six of its referenced files are gone; the Operations view superseded it (#1109)
internal-system-agent.md views/SystemAgent.vue, SystemAgentTerminal.vue, views/Agents.vue Three referenced files gone (the /system-agent route still exists — check whether the doc should be rewritten instead of archived)
execution-queue.md services/execution_queue.py, services/scheduler_service.py, src/scheduler/agent_client.py All three gone; superseded by the capacity-management.md / backlog flows

3. Mechanical path drift — FIX in place (one /sync-feature-flows pass)

  • src/backend/db/schedules.py → now the package db/schedules/ (refactor(db): split db/schedules.py (2,928 lines) into CRUD / executions / analytics modules #1481): 13 docs (autonomy-mode.md, business-validation.md, cleanup-service.md, continue-execution-as-chat.md, … — full list from grep -l 'db/schedules.py' docs/memory/feature-flows/*.md)
  • src/backend/services/scheduler_service.py → src/scheduler/: activity-stream.md, scheduler-service.md, scheduling.md (plus execution-queue.md, archived above)
  • src/scheduler/agent_client.py: scheduler-service.md, scheduling.md
  • AgentNode.vue: agent-avatars.md, agent-lifecycle.md, autonomy-mode.md, autonomy-toggle-component.md (the remaining two are archived above)
  • Renamed/moved test files: tests/test_team_share_gate_unit.py (agent-sharing.md, unified-channel-access-control.md), tests/test_2322_cli_login_no_session.py (admin-login.md), tests/test_watchdog_unit.py (cleanup-service.md), tests/test_idempotency.py (effect-idempotency.md), tests/test_platform_prompt_unit.py (execution-context-injection.md), tests/unit/test_1165_setup_token_shared.py (first-time-setup.md), tests/test_self_execute.py (self-execute.md), tests/test_event_bus.py (websocket-event-bus.md)
  • One-offs: docker/base-image/hooks/claude-settings.json (agent-guardrails.md — registration moved to the managed-settings path, ent#345), src/backend/deps.py (execution-detail-page.md), src/backend/routers/site.py (public-agent-links.md), src/backend/staging-acceptance.py (backend-image-packaging.md), config/agent-templates/ruby-social-media-agent/template.yaml (agent-info-display.md), views/ApiKeys.vue (mcp-api-keys.md, mcp-orchestration.md)

4. Index hygiene (docs/memory/feature-flows.md) — FIX

  • Not linked from the index: activity-stream-collaboration-tracking.md, agent-custom-metrics.md, execution-list-page.md, gemini-runtime.md, onboarding-wizard.md, status-as-projection.md — index them or archive them
  • Index rows pointing at deleted docs: AUDIT-001-execution-origin-tracking.md, skills-crud.md, mcp-skill-tools.md
  • The template section at the bottom links a literal related-flow.md; make the placeholder obviously non-resolvable (e.g. <related-flow>.md) so link checks skip it

Acceptance Criteria

  • architecture.md no longer lists routers/alerts.py or services/scheduler_service.py; the Background Services row points at src/scheduler/
  • The nine obsolete flows are archived (or, for internal-system-agent.md, rewritten) and removed from the index
  • Every remaining backticked src/…, docker/…, config/…, tests/… path in docs/memory/feature-flows/*.md resolves to an existing file (a one-line check: extract backticked paths, test existence, allowing sub-project-relative shorthand)
  • Every file in docs/memory/feature-flows/ is linked from feature-flows.md, and every link resolves
  • /validate-architecture reports no new drift; the enterprise-docs guard workflow stays green

Technical Notes

Activity

  1. added
    complexity-mediumComplexity: medium (board points 5-8)
    status-readyGreenlit and ready for development (vetted; counterpart to status-incubating)
    on Sep 2, 2026
  2. vybe commented on Oct 12, 2026

    @vybe
    ContributorAuthor

    Groom 2026-10-13 (label-vs-reality pass), one question: #3472 edited some of the memory-doc lines this issue lists. What is still stale after it? If the residual is small, please narrow the title and re-size; if nothing remains, say so and it moves to status-in-dev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    complexity-mediumComplexity: medium (board points 5-8)priority-p2Importantstatus-readyGreenlit and ready for development (vetted; counterpart to status-incubating)theme-devexTheme: DevExtype-docsDocumentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions