# Cosmos Luminosity Portal architecture and naming

Use when Margarita asks to describe, expand, rename, or technically update the former Cosmos Luminosity encyclopedia.

## Canonical naming

- Public/system name: **Cosmos Luminosity Portal** / **портал Cosmos Luminosity**.
- Treat “энциклопедия” as deprecated public and internal product language for this project. Existing historical filesystem paths such as `/home/spazio/cosmos_luminosity_encyclopedia/` may remain unchanged when renaming them could break services, scripts, imports, or links.
- A page is a **страница портала**, an entry is a **узел портала**, and the whole environment is a **живой многомерный портал**.
- Hacking Foundation is a foundational chapter/layer inside the portal, not the name of the whole portal unless Margarita later changes this.

## Core concept

The portal is the digital embodiment of the Cosmos Luminosity meta-system. In an earlier era the material might have become a book, but a linear book cannot transmit its interconnected volume. The portal supports:

- cross-linked articles and knowledge nodes;
- video, audio, AudioBoosts, visual art, art objects, practices, tools, symbolic systems and research;
- curated routes and free personal navigation;
- a visible personal route/history;
- gamification through **Lumos**;
- progressive levels and materials that open with readiness, completed routes, or Lumos thresholds;
- personal Digital Guides / Kosmobots;
- preparation for contemporary life amid AI, uncertainty, rapid change and the need for adaptive inner renewal.

Lumos thresholds, rewards, exchange mechanics and access rules are concepts under development; never invent exact numbers or finalized mechanics without Margarita’s approval.

## Default content workflow

1. Search existing portal pages first and enrich the most relevant page.
2. For portal-wide architecture, update or create `content/cosmos-luminosity-portal.md` and link it from `content/index.md`.
3. Keep cross-links to the meta-system, Hacking Foundation, meaning-making, creator-level transition and Digital Guides.
4. When Margarita says “переименуем везде”, update both content and visible application language:
   - frontmatter titles and summaries;
   - headings and body copy;
   - navigation labels, search labels and editor messages;
   - HTML title/meta description;
   - server/editor prompts and startup labels.
5. Preserve technical path names when renaming creates breakage risk; explicitly report this exception.
6. Search again for deprecated naming. Ignore occurrences contained only inside unchanged historical paths.
7. Run syntax checks for edited JS/server files, then start a temporary instance on another port and verify the portal page through the live API. Stop the temporary process afterward.

## Verification checklist

- `node --check public/app.js`
- `node --check server.mjs`
- Search content, public UI and server code for `энциклопед`, `encyclopedia`, and `Encyclopedia`.
- Confirm the API returns the `cosmos-luminosity-portal` page and that key concepts such as Lumos are present.
- Confirm no temporary test server remains running.

## Pitfalls

- Do not perform a blind global replacement across virtual environments, imported packages, binary/media folders, or historical paths.
- Do not rename the project directory merely to achieve textual consistency; stability of services and links comes first.
- Preserve sidebar rendering and keyboard navigation when editing compact React-without-JSX code; use a syntax check immediately after every structural patch.
- Do not flatten the portal back into “a wiki” or “an online book.” Those are partial analogies; the intended product is a multidimensional adaptive environment with routes, media, levels and participation.