ALAI Companies × Products × File-System Catalog v1.0-draft

ALAI Companies × Products × File-System Catalog

Status: v1 draft, observed state 2026-05-23 Source of truth: This file. Machine-readable mirror: ~/system/specs/companies-products-catalog.json Maintenance: Update on entity/product creation, deprecation, or relocation. Drift detection should be wired into the existing blueprint-fleet-watchdog. Note: This catalog reflects what is on disk now. Items marked TBD require CEO clarification before they can be authoritative.

Legal entities operated by ALAI

CEO clarification 2026-05-23:

Entity	Jurisdiction	Tree path	Owned by ALAI Holding?	Pravno-vlasnički odnos	Financial passthrough
ALAI Holding AS	Norway (NO)	`~/business/ALAI-Holding-AS/`	— (parent itself)	Parent entity	Yes
ALAI Tech DOO	Serbia (RS)	`~/business/ALAI-Tech-DOO/`	Yes — legal owner	Subsidiary of Holding. Drop Srbija + Bilko Srbija operate legally under this DOO (CEO 2026-04-16 consolidation memo `project_drop_srbija_legal_entity`)	Yes
SnowIT BA	Bosnia and Herzegovina	`~/tenants/SnowIT-BA/`	"Naše" operationally — NOT legal ownership. Tech-provider relationship only.	Separate legal entity. ALAI is tech provider with zero financial share per directive 2026-05-15 (MC #100723)	No
Client entities	Various	`~/clients-external/<client>/`	No (direct clients)	ALAI invoices them	Yes (ALAI bills them)

Reference: ~/system/specs/canonical-registry.md (tree ownership) + memory notes project_snowit_legal_boundary_2026-05-15, project_drop_srbija_legal_entity.

Products by entity

ALAI Holding AS — products under `~/business/ALAI-Holding-AS/products/`

Product	Path	Blueprint	Status / notes
BasicFakta	`products/BasicFakta/`	yes	Vercel-hosted SaaS, basicfakta.no
Bilko	`products/Bilko/`	yes (530 lines, 2026-05-20)	Multi-country Balkan accounting SaaS. Single Kotlin/Ktor backend + single Postgres + CF Worker brand routing (4 jurisdictions: HR / RS / BA_FED / BA_RS) per v3 plan APPROVED 2026-05-11. Brand hostnames: bilko.cloud (HR), bilko.rs (RS), bilko.company (BA), bilko.io (primary). Market priority HR→BA→RS (CEO 2026-05-09). Active productization MC #101789.
Bilko-overnight-john	`products/Bilko-overnight-john/`	yes (530 lines, byte-identical to Bilko per md5 `16f4d113...`)	TBD — duplicate of Bilko. Archive or merge candidate
Drop	`products/Drop/`	yes (208 lines, 2026-05-07)	Norway fintech remittance, PSD2 licensure pending
DropSrbija	`products/DropSrbija/`	yes (386 lines)	Separate codebase from Drop. RS-market operations run legally under ALAI Tech DOO (CEO 2026-04-16). Filesystem currently under Holding/products/ — relocation to `~/business/ALAI-Tech-DOO/products/DropSrbija/` is a candidate, not decided. Scope question (separate product vs Drop multi-tenant) remains MC #99883.
Gotiva	`products/Gotiva/`	yes (556 lines)	GCP Cloud Run multi-service
Lobby	`products/Lobby/`	yes (396 lines)	—
Plock	`products/Plock/`	yes (512 lines)	—
SnowIT	`products/SnowIT/`	no (no BP, no CLAUDE.md, no README)	TBD — likely legacy stub. Real SnowIT lives in `~/tenants/SnowIT-BA/`. Candidate to delete or convert to pointer file
Tok	`products/Tok/`	yes (637 lines, 2026-04-27)	PSD2 fintech, CI dead since 2026-03 (MC #10452)
unified-form-service	`products/unified-form-service/`	no (README only)	TBD — product, internal library, or experiment?

Stray non-directory artifacts (Phase-D tree violation — should be moved):

products/pbz-banking-dossier-100274.md
products/mojafirma-ux-teardown-100279.md

ALAI Tech DOO — products under `~/business/ALAI-Tech-DOO/products/`

Filesystem directory is currently empty. Per CEO directive 2026-04-16 (memo project_drop_srbija_legal_entity), Serbian-market operations of ALAI products operate legally under ALAI Tech DOO even when their code lives elsewhere on disk.

Important distinction: "operating under Tech DOO" is a legal/financial classification, not a code-layout decision. The Bilko architecture v3 plan (~/system/specs/bilko-multi-market-architecture-plan-v3-2026-05-11.md, APPROVED 2026-05-11) chose a single backend with country dispatch via JWT org.country claim. "Bilko Srbija" is therefore not a separate product directory — it is the RS market segment of a single Bilko codebase.

Product	Legal entity for RS operations	Filesystem location	Code-layout status
Drop Srbija	ALAI Tech DOO	`~/business/ALAI-Holding-AS/products/DropSrbija/`	Separate product directory. Relocation to `~/business/ALAI-Tech-DOO/products/DropSrbija/` is a candidate but not decided. Drop and DropSrbija are different codebases.
Bilko (RS market segment)	ALAI Tech DOO	`~/business/ALAI-Holding-AS/products/Bilko/` (shared with HR + BA markets)	Not a separate directory. Single backend dispatches per `org.country='RS'` per v3 plan. Brand hostname `bilko.rs` routes via CF Worker `bilko-edge-proxy` to the shared backend `bilko-api-demo`.

Reference: ~/business/ALAI-Holding-AS/products/Bilko/docs/architecture/MULTI-COUNTRY-ARCHITECTURE.md is the v1 plan (Option D, 3 separate apps) and is marked SUPERSEDED in its own header. Do not use it as a guide.

SnowIT BA (operated tenant) — `~/tenants/SnowIT-BA/`

Subdirectories present:

calendar
clients
company
contacts
forms (and others not enumerated in this draft)

Known products / brand assets associated with SnowIT BA per memory project_lumiscare_ownership (2026-03-25):

LumisCare — owned by Snowit.ba per CEO 2026-03-25. TBD — physical artifacts currently sit at ~/clients-external/lumiscare-variants/ (6 variants: lumiscare, alpha, beta, gamma, delta, epsilon). Open question: should they relocate under ~/tenants/SnowIT-BA/products/ or remain in clients-external?

Direct ALAI clients — `~/clients-external/`

Client	Path	CLAUDE.md
adnan-cesko-dj	`clients-external/adnan-cesko-dj/`	yes
FreeMyEV-v2	`clients-external/FreeMyEV-v2/`	yes
KenanHot	`clients-external/KenanHot/`	yes
klofta-il	`clients-external/klofta-il/`	yes
knowit-minvei-krav	`clients-external/knowit-minvei-krav/`	yes
lumiscare-variants	`clients-external/lumiscare-variants/` (6 sub-variants)	no
merdzanovic-ba	`clients-external/merdzanovic-ba/`	yes
nordfit	`clients-external/nordfit/`	no
rendrom	`clients-external/rendrom/`	yes
virtual-serbia	`clients-external/virtual-serbia/`	yes

Engineering repositories — `~/projects/`

Internal tooling and code repositories (not customer products):

alai-cli, alai-system, autocoder, bih-tenders, bookstack-api, hexadb, internal, pa

These are NOT in scope for the products catalog. Listed here for completeness so the catalog doesn't pretend they don't exist.

Open questions blocking authoritative status

SnowIT — is ~/business/ALAI-Holding-AS/products/SnowIT/ legacy stub for deletion, or does it hold any non-redundant artifact vs ~/tenants/SnowIT-BA/?
LumisCare — confirm: SnowIT-BA product (relocate variants), or direct ALAI client (keep in clients-external)?
Bilko-overnight-john — byte-identical to Bilko (md5 match). Archive or keep as backup?
lumiscare-variants — if LumisCare belongs under SnowIT, do all 6 variants relocate?
unified-form-service — product, library, or experiment? Determines whether it stays under products/ or moves to ~/projects/.
Stray .md files in products/ root — move to docs/scratch/ or delete?

Each of these is one short CEO sentence; until they are answered the catalog stays v1 draft.

Why this catalog exists

Prior reports (blueprint-fresh-analysis, ops-coverage-audit) implicitly enumerated companies and products and produced inconsistent answers — one phantom-included LumisCare/Lexicon, the other omitted SnowIT/unified-form-service. The discrepancy was not a hallucination by one report; it was a symptom of no shared catalog. This file is intended to be that shared file.

Drift detection wiring (recommended)

Add to ~/system/daemons/blueprint-fleet-watchdog.js: scan all ~/business/*/products/, ~/tenants/*/, ~/clients-external/*/ once per cycle and flag any directory not listed in companies-products-catalog.json.
Add to ~/system/rules/zakon-blueprint-enforcement.md: new product directory creation must also append a row to this catalog.

(Wiring not done in this commit — listed as a follow-on action.)