ANVIL Tenant Architecture — Phase D 2026-05-07

• ADR-023 — Tenant Restructure Decision
• Tree Blueprint — Where to Put Things
• Git Structure Rules
• Canonical Registry (Phase D Updated)

ADR-023 — Tenant Restructure Decision

Context

ADR-022 documented the mechanical filesystem sweep — orphans, broken refs, PHANTOM daemons. After completion CEO observed that the home tree, while mechanically clean, remained semantically misorganized:

"Zelim da sam ponosan file strukture, a ne da sam zabrinut."
"alai.no/ucenje" — Alem's personal Quran-19 scholarly site lives inside the ALAI commercial brand tree.

A 6-agent multi-perspective audit (Petter / Brad / Parisa / Lexicon / Kelsey / Skybound) produced ~84 findings, ~22 convergent across 3+ angles. The unanimous top finding: personal scholarly content under commercial brand surface = brand contamination + GDPR exposure + blocks divestment.

Beyond ucenje, the audit surfaced:

• BasicConsulting AS treated as separate legal entity in tree (vedtekter, share register expectations) when in fact it is a domain only owned by ALAI Holding AS (CEO clarified post-audit)
• ALAI-Tech-DOO is a real legal subsidiary (RS d.o.o., Bosnia/Serbia distribution of Bilko/Tok/Drop) but lived under ~/companies/ mixed with agent personas
• 12 agent personas (CodeCraft, Vizu, FlowForge, etc.) mislabeled as "companies" in ~/companies/
• Client work scattered across ~/projects/ mixed with ALAI internal engineering
• CEO personal data (CV 19×, NAV records, employment-verification PII) scattered across business trees
• ~/Public/ containing CEO PII (employment-verification, ownership cert, firmaattest) — local-network readable
• Lumiscare client .env files committed to git history (auth bypass flags)
• Planka .env at 644 perms; Snowit terraform.tfstate one accidental git add . from leak

Decision

Implement multi-tenant home tree with strict isolation per legal entity / personal scope / client scope:

~/business/                # legal entities (ALAI corporate group)
├── ALAI-Holding-AS/      # commercial parent (renamed from ~/ALAI/)
└── ALAI-Tech-DOO/        # RS d.o.o. subsidiary

~/personal/                # CEO natural-person scope (NEW)

~/clients-external/        # one canonical subdir per client (NEW)

~/system/                  # orchestration runtime
└── agents/personas/      # agent persona definitions (12)

~/projects/                # ALAI internal engineering repos ONLY (8 entries, was 23)

Backward compatibility:

• ~/ALAI symlinked to ~/business/ALAI-Holding-AS/ for 158 LaunchAgent paths grace period
• ~/companies symlinked to ~/system/agents/personas/ for 10+ daemon/tool refs grace period

Sub-decisions

Consequences

Positive

• 13 named clients in ~/clients-external/ (one tenant per subdir, no cross-contamination)
• 9 ALAI products in ~/business/ALAI-Holding-AS/products/ (no client-as-product misclassifications)
• 12 agent personas in ~/system/agents/personas/ (correct semantic home; no longer "companies")
• 2 legal entities under ~/business/ (Holding AS + Tech DOO; no third entity confusion)
• CEO personal scope isolated under ~/personal/ (cv, nav, scholarly, code, real-estate, legal-personal)
• ~/projects/ narrowed from 23 → 8 entries (ALAI internal engineering only)
• ucenje brand contamination resolved (ucenje.alai.no separate, alai.no/ucenje 301)
• 26 GB freed (ollama.tar.gz cleanup) + 16 GB freed (test scaffolds + companies archive)
• ~/Public PII quarantined to ~/personal/legal-personal/ (5 sensitive PDFs no longer local-network readable)
• ~/companies/ completely removed (anti-pattern eliminated)

Negative

• 158 LaunchAgent paths still resolve via ~/ALAI symlink (TD: rewrite to canonical, ≥30d grace)
• 10+ tool/daemon refs to ~/companies/ resolve via symlink (TD: same grace, lower priority)
• _legacy-bc-2026-05-07/ content from BasicConsulting unwind required manual reconciliation into clients/Entur/ and clients/RPG/ (DONE, but added one-time manual step)
• 19 CV references across grant submissions remain in place (each is a submission artifact, not a duplicate to dedup)
• Some opaque-name decisions deferred (internal/ left as-is — well-organized but generic name)

Neutral

• Boot health unchanged (29/29 daemons loaded, 0 failing, before and after)
• Git histories preserved (used git mv for in-repo moves, plain mv for cross-repo)
• ALAI-Tech-DOO retains its own git repo and .alai/ orchestration metadata

Alternatives Considered

Implementation

References

• Multi-perspective audit: ~/system/specs/anvil-organizational-audit-2026-05-07.md
• Sub-agent reports: /tmp/anvil-org-audit/01-petter*.md … 06-skybound*.md
• Mechanical sweep ADR: ~/system/architecture/decisions/ADR-022-anvil-fs-sweep-2026-05-07.md
• Canonical registry: ~/system/specs/canonical-registry.md (post-D updates)
• Tree blueprint (NEW): ~/system/specs/anvil-tree-blueprint-2026-05-07.md
• Git structure rules (NEW): ~/system/specs/anvil-git-structure-2026-05-07.md
• Memory entries: project_alai_entity_identity_clarified_2026-05-07.md, project_anvil_phase_d_done_2026-05-07.md
• MC chain: #99710 (org audit parent), #99742 (Phase B.1), #99744 (Phase B.2), #99722 (Brønnøysund — closed), #99723 (BC clarification — pending close), #99724 (Lumiscare notification), #99725 (Telegram revoke)
• Live deployment: https://ucenje.alai.no, https://github.com/johnatbasicas/ucenje

Tree Blueprint — Where to Put Things

One rule: every file has exactly one canonical home determined by what it is + whose it is, not by who created it or when.

1. Top-level decision tree

For any new content, answer 4 questions in order:

Q1: Is it CODE / file content / data?  No → it's a process artefact, not a tree concern.
Q2: Whose data is it? (CEO personal / ALAI Holding AS / ALAI Tech DOO / a specific client / regenerable)
Q3: What kind? (product, client deliverable, internal tool, scholarly, financial record, brand asset, …)
Q4: What stage? (active draft, in-flight, completed deliverable, archive)

2. Routing matrix

3. Anti-patterns — explicitly forbidden

4. References

• ADR-023: ~/system/architecture/decisions/ADR-023-anvil-tenant-restructure-2026-05-07.md
• Canonical registry: ~/system/specs/canonical-registry.md
• Git structure rules: ~/system/specs/anvil-git-structure-2026-05-07.md

Git Structure Rules

1. Repo placement matrix

2. Required files per repo type

3. Commit conventions — Conventional Commits (mandatory)

<type>(<scope>): <subject> (MC #<id>)

<body — what changed and why>

Co-Authored-By: <persona-name> <noreply@alai.no>

type ∈ feat | fix | chore | docs | style | refactor | perf | test | ci | build

4. .gitignore standards

Universal (every repo)

# OS
.DS_Store
Thumbs.db

# Editor / IDE
.vscode/
.idea/
*.swp
.aider*
.claude-scratch/

# Secrets — NEVER COMMIT
.env
.env.*
!.env.example
*.pem
*.key
id_rsa*
*.p12
.bw-session

# Logs
*.log
logs/

# Build outputs
dist/
build/
out/
target/
.next/
.nuxt/
.output/
.turbo/

Node-specific

node_modules/
npm-debug.log*
yarn-debug.log*
yarn-error.log*

Terraform / IaC (CRITICAL after Parisa finding)

*.tfstate
*.tfstate.*
*.tfplan
.terraform/
.terraform.lock.hcl
crash.log

5. Anti-patterns — explicitly forbidden

6. References

• ADR-023: ~/system/architecture/decisions/ADR-023-anvil-tenant-restructure-2026-05-07.md
• Tree blueprint: ~/system/specs/anvil-tree-blueprint-2026-05-07.md
• Canonical registry: ~/system/specs/canonical-registry.md
• ZAKON PI2 (deploy verification): ~/system/rules/zakon-pi2-deploy-verification.md
• Conventional Commits spec: https://www.conventionalcommits.org/en/v1.0.0/

Canonical Registry (Phase D Updated)

Tree Ownership Table

One row per major tree. These are the canonical locations — creating parallel structures elsewhere violates the registry.

Phase D Additions (2026-05-07) — Final Tenant-Isolated Structure

~/business/
  ├── ALAI-Holding-AS/   (was ~/ALAI; symlink kept for 158 daemons grace)
  └── ALAI-Tech-DOO/     (RS d.o.o. subsidiary, real legal entity)

~/personal/              (NEW — CEO scope, 9 typed dirs)
~/clients-external/      (NEW — 13 named clients + 1 variants umbrella)
~/companies              SYMLINK → ~/system/agents/personas/  (10+ daemon backward compat)
~/system/agents/personas/  (12 personas)
~/projects/              (8 ALAI eng repos only)

Renamed for Disambiguation (Phase D)

• ~/business/ALAI-Holding-AS/architecture/ → product-architecture/ (was conflicting with ~/system/architecture/)
• ~/business/ALAI-Holding-AS/services/ → service-catalog/ (was conflicting with ~/system/services/)
• ~/business/ALAI-Holding-AS/templates/ → doc-templates/ (was conflicting with ~/system/templates/)
• ~/business/ALAI-Holding-AS/ufs/ → products/unified-form-service/ (deployed at forms.alai.no)

4-Way CLAUDE.md Scope Rules

CLAUDE.md files exist at 4 different scope levels. Each loads based on current working directory (CWD).

What MUST NOT Recreate

These paths were archived during ANVIL FS Sweep. Recreating them silently reintroduces filesystem chaos and split-brain drift.

From ~/system/ (archived):

• ~/system/archive/, ~/system/deprecated/, ~/system/deployments/, ~/system/plans/
• ~/system/clients/ (migrated to ~/business/ALAI-Holding-AS/clients/)
• ~/system/infrastructure/, ~/system/internal/, ~/system/legal/, ~/system/org/
• ~/system/pipeline/, ~/system/processes/, ~/system/products/, ~/system/sales/, ~/system/web/

Post-D additions (MUST NOT recreate):

• ~/companies/ as a real directory tree (it's a symlink only, for backward compat)
• ~/ALAI/ as a real directory (it's a symlink only)
• ~/projects/personal/ (use ~/personal/)
• ~/projects/client/ (use ~/clients-external/)
• ~/projects/Basicconsulting/ (now at ~/business/ALAI-Holding-AS/brand-surfaces/basicconsulting.no/)
• ~/companies/BasicConsulting/AlemPersonal/ (CEO content moved to ~/personal/)

Live Deployments (post-D)

• https://ucenje.alai.no ← ~/personal/scholarly/ extracted to johnatbasicas/ucenje repo + Cloudflare Pages
• https://alai.no/ucenje/* → 301 → https://ucenje.alai.no/ (verified live)

References

• Decision Records: ~/system/architecture/decisions/ADR-022-anvil-fs-sweep-2026-05-07.md, ADR-023-anvil-tenant-restructure-2026-05-07.md
• MC chain: #99710 (org audit parent), #99637 (mechanical sweep parent)
• Memory: project_anvil_phase_d_done_2026-05-07.md, project_alai_entity_identity_clarified_2026-05-07.md