╔═════════════════════════════════════════════════════════════════════╗
║                     INTERDEAD :: REPOSITORIES                       ║
╠═════════════════════════════════════════════════════════════════════╣
║ ○ InterDead Reference Library (public)                              ║
║   Public reference library: documents and notes that are safe       ║
║   to share outside the private workspace.                           ║
║                                                                     ║
║ ○ InterDeadIT (website / entry point)                               ║
║   The website: the public entry point into the InterDead meta-verse.║
║   Hosts the “About” and related public-facing materials.            ║
║                                                                     ║
║ > InterDeadCore (identity + EFBD core)                              ║
║   Core modules used by the website: identity/auth and EFBD logic.   ║
║   Published as packages and consumed by InterDeadIT.                ║
║                                                                     ║
║ ○ PsyFramework (research / tooling)                                 ║
║   Research and tooling repo referenced by the project; supporting   ║
║   framework work that may be mentioned from public docs.            ║
╠═════════════════════════════════════════════════════════════════════╣
║                           INTERDEADCORE                             ║
║═════════════════════════════════════════════════════════════════════║
║ InterDeadCore is the monorepo for shared InterDead domain packages. ║
║ It keeps identity and EFBD scoring logic decoupled from             ║
║ presentation, follows hexagonal architecture boundaries, and        ║
║ ships reusable building blocks for downstream runtimes. Each        ║
║ package is versioned independently, while the repository maintains  ║
║ shared data contracts and operational notes so adapters remain      ║
║ consistent across deployments. This layout differs from InterDeadIT,║
║ which hosts a single website surface while consuming these packages ║
║ as dependencies.                                                    ║
║═════════════════════════════════╦═══════════════════════════════════║
║    ECHO OF AN UNFADING MEMORY   ║   INTERDEAD WIKI (ALL LANGUAGES)  ║
╠═════════════════════════════════╬═══════════════════════════════════╣
║ READ (EN)                       ║ READ (EN)                         ║
╠═════════════════════════════════╬═══════════════════════════════════╣
║ READ (RU)                       ║ READ (RU)                         ║
╠═════════════════════════════════╬═══════════════════════════════════╣
║ READ (UK)                       ║ READ (UK)                         ║
╠═════════════════════════════════╬═══════════════════════════════════╣
║ READ (JA)                       ║ READ (JA)                         ║
║═════════════════════════════════╩═══════════════════════════════════║
║                            CONTACT                                  ║
╠═════════════════════════════════════════════════════════════════════╣
║ Zhovten Games — LinkedIn                                            ║
╚═════════════════════════════════════════════════════════════════════╝

Packages:

• @interdead/identity-core: Discord-authenticated identity kernel with pluggable storage.
• @interdead/efbd-scale: EFBD scoring domain for adaptive horror design.

Stack

• TypeScript domain packages
• Cloudflare Workers + D1 + KV (host-provided bindings)
• Hexagonal architecture with ports-and-adapters

Local dev

• Install dependencies per package: npm install inside identity-core/ and efbd-scale/.
• Run tests per package: npm test (and npm run typecheck where available).

Deployment (high-level)

• Packages are released independently from the monorepo.
• Downstream repositories (such as InterDeadIT) explicitly upgrade package versions.
• See release details in the documentation index below.

Conventions

• Keep adapters thin and let domain services own the business logic.
• Use object-oriented aggregates and shared base errors to keep responsibilities separated.
• Preserve ports-and-adapters layering so packages remain swappable across runtimes.

Engineering standards

Engineering standards: Canonical project-wide engineering ideals and development standards are maintained in the InterDead Reference Library (public): https://github.com/Zhovten-Games/InterDeadReferenceLibrary/tree/main/standards/development. This repository follows that canon; local notes here must not override or fork the shared standards.

Docs

Start here: docs/README.md

Key references:

• Architecture overview
• Ports and events
• Data contracts
• Release flow