Skip to content

vision: scope-signal engine + .aytree-index (enumeration feature gap) #21

Description

@Zychs

Vision

README Enumeration and Scope Detection Engine: directory enumeration, scope-signal detection (names + content patterns), dynamic scope model, non-intrusive .aytree-index metadata (timestamps, content hashes, extracted scopes), incremental read-triggered rescans.

Reality

Ingest today is local-git reflog + FS walk via picker (src/ingest/local-git.js). No .aytree-index writer/reader, no scope-signal tagging pipeline, no incremental rescan contract in modular shell.

Notes

  • Optional power layer server/aytree_server.py has /api/tree scan — not the same as the index metadata model.
  • Keep local-truth law: no remote-dependent indexing (VERSIONING.md §2).

Exit

Written minimal index schema + one write/read path; status words for this engine move off implied-present README tone (or README stays honest if still deferred).

Refs

README.md Core Components · ARCHITECTURE ingest diagram · VERSIONING local truth

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestvision-varianceGap between README/GHM2 vision and current code

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions