base_installation

Katz 0.109

Base-level install marks a directory as a base and seeds shared application memory under `<base>/.reqlan/` ( application_memory ).
Entry points ( same helper create-base.ts ):
- Editor: `reqlan.createBase` / empty-state CTAs ( create_base_onboarding ) — only after discovery finds **zero** bases; never on extension install alone.
- CLI: `reqlan init directory` ( init ).
Idempotent: existing `.reqlan` is left alone ( `created: false` ).
On **new** base creation the sequence is:
1. Create `<base>/.reqlan/` marker directory ( presence = base ).
2. Seed base_config_seed ( `.reqlan/config.json` ).
3. Seed base_rqignore_seed ( `.reqlan/.rqignore` ).
4. Seed base_initialisation_ignore ( `.reqlan/.gitignore` for SQLite artifacts ).
5. Editor rediscovers bases and activates indexing for that base; SQLite `ideas-index.sqlite` appears when the index opens ( not necessarily written at marker creation ).
Child / nested bases follow base_nesting; each base owns its own `.reqlan` seeds and index.

Interactive page: base_installation