Referenced by5
Labels10

Referencing ideas

IdeaStatusTagsSummaryKatz
baseA base is a container for ideas, ideasets, and files. It forms the boundary of one ideas graph and is consumed by the CLI and the extension. Marker: a directory is a base only when it owns a `.reqlan` folder ( [app_memory_doc.application_memory] ). No bare workspace folder is treated as a base until the user creates `.reqlan` there ( [create_base_onboarding] ). Aligns with [ontology_base]. Discovery and registry: [base_discovery], [base_registry]. Marker path helpers: [application_memory_impl].0.322
create_base_onboardingWhen discovery finds **zero** bases under any VS Code workspace folder ( root or child ), the extension prompts the user to create a reqlan base at the workspace-folder root. Do not auto-create `.reqlan`. Command `reqlan.createBase` creates `<folder>/.reqlan/` ( empty directory is a valid marker ) via [create_base_impl], then calls [base_registry] `refresh` so the new marker is registered and the returned [base] descriptor matches discovery ( [refresh_rediscovers_bases] ). With multiple workspace folders and no bases, prompt against the first folder. Headless create-base helper: [create_base_impl] ( also used by CLI `init` ).0.172
refresh_rediscovers_basesdoneManual Refresh ( command `reqlan.refreshIndex`, activity-bar / Ideas Summary Refresh buttons ) and Clear & rebuild must **always rediscover** `.reqlan` markers under workspace roots before soft-sync or rebuild. Do not skip discovery when bases are already registered — a new nested or sibling base created on disk must appear after Refresh. Discovery and registration live in [base_registry] ( `refresh` → `rediscover` → optional `ensureBaseReady` for the active base ). The extension adapter ( [editor_index_adapter] ) calls that analytical API; it must not invent a parallel discovery walk. Create Base follows the same refresh path after [create_base_impl] so the new marker is visible immediately ( [create_base_onboarding] ). Related: [multi_base_environment], ["../extension/index-host/graph-analysers.rq".indexing_trigger_manual], ["../extension/index-host/sqlite-artifact-lifecycle.rq".event_driven_base_access].0.075
indexing_trigger_filesaveindexing should be triggered by. rq file create / change / delete via watchers, and by allowlisted source files that may contain comment references.0.106
indexing_trigger_manualIndexing should be triggered by manual indexing commands ( Refresh / Clear & rebuild ). Refresh and Clear & rebuild always rediscover bases first via ["../../bases/base.rq".refresh_rediscovers_bases] / ["../../../packages/analytical/src/index-store/base-registry.ts"] `refresh`, then soft-sync or rebuild the active base.0.092

Reference labels

"../../../packages/analytical/test/base-registry-refresh.test.ts:refresh rediscovers a base created after an empty discovery", "../../../packages/analytical/test/base-registry-refresh.test.ts:refresh rediscovers a nested base added after first discovery", "../../packages/analytical/test/base-registry-refresh.test.ts:refresh after createBase registers the new base", "../../packages/analytical/test/base-registry-refresh.test.ts:refresh rediscovers a base created after an empty discovery", "../../packages/analytical/test/base-registry-refresh.test.ts:refresh rediscovers a nested base added after first discovery", ../../../packages/analytical/test/base-registry-refresh.test.ts:refresh rediscovers a base created after an empty discovery, ../../../packages/analytical/test/base-registry-refresh.test.ts:refresh rediscovers a nested base added after first discovery, ../../packages/analytical/test/base-registry-refresh.test.ts:refresh after createBase registers the new base, ../../packages/analytical/test/base-registry-refresh.test.ts:refresh rediscovers a base created after an empty discovery, ../../packages/analytical/test/base-registry-refresh.test.ts:refresh rediscovers a nested base added after first discovery