Search Results

## §6 — Recommended Winner + Rationale (D4 / AC#4) **Pre-condition gate:** /tmp/forged-99124-evidence.jsonl contains 42 records (≥40 required). Verified: `wc -l /tmp/forged-99124-evidence.jsonl → 42` at 2026-05-04T21:20Z. ### winner: Mem0 self-hosted ### ru...

## §7 — Migration Plan (D5 / AC#5) Winner = Mem0 self-hosted. No migration away from existing deployment required. Plan = activation of Phase 2 items from stop-hook-l3-memory-spec.md. **LightRAG data export (for reference — required if future winner changes)...

## §8 — Pillar #9 Interplay + OAuth (D6 / AC#6) ### Topic 1 — Memory-layer location (laptop vs VM vs hybrid) **Decision:** Mem0 = laptop-only (ANVIL) for now. Qdrant port 6333 and Ollama port 11434 are both ANVIL-local. vm-alai-support (Pillar #9) does not h...

## §9 — Validation Harness — 20-Query Golden Set (D7 / AC#7) **Chip-huyen SC-3:** 20 queries from recall-eval-v2.sh lines 76-114 appear verbatim below. **Execution:** OUT OF SCOPE for MC #99124 — Phase 2 child MC. Scoring function fields per query: recall@10...

## §3 Proposed Convention ### 3.1 Root location All skill outputs, evidence artifacts, and forge deliverables write under: ``` ~/projects//// ``` Where: - `` — client slug (e.g., `bilko`, `drop`, `intesa`) or `alai` for internal ALAI work. - `` — one of: s...

## §4 Tool Support ### 4.1 `output-path.js` helper **Location:** `~/system/tools/output-path.js` **CLI interface:** ```bash node ~/system/tools/output-path.js resolve \ --client alai \ --skill task-postflight \ --mc 99292 ``` Returns: absolute path ...

## §5 Migration Phases Migration is additive. No existing file is moved. No existing convention is broken. Each phase adds structure; nothing removes it. ### Phase 1 — Week 1: Tool exists, new invocations opt in **Deliverable:** `~/system/tools/output-path....

## §6 Enforcement Three options, ranked by intrusiveness: ### Option A — Lint-on-mc-ready (least intrusive) [RECOMMENDED] A `pre-mc-ready` bash hook intercepts `mc.js ready ` calls. It reads the MC outcome/evidence field and checks whether any path referenc...

## §7 Per-Skill Examples ### 7.1 task-postflight **Current behavior:** Evidence written to `/tmp/postflight-/` (when it exists at all). Outcome is terminal output only. Brief (the AC list) exists only in the MC description, not alongside the output. **After...

ANVIL Filesystem Sweep — Overview & Outcomes What and Why The ANVIL Filesystem Sweep (MC #99637) was a comprehensive cleanup and canonicalization effort to resolve structural drift in ALAI's Mac Studio orchestration host filesystem. After 4+ months of agent a...

Canonical Path Registry Purpose: Industry-standard ITIL CMDB / Spotify Backstage pattern. Catalog of canonical paths, their owners, scope, and anti-drift rules. This is the authoritative source for "where does X belong" questions in ALAI's filesystem hierarch...

ADR-022: ANVIL Filesystem Canonical Map and Cleanup Status: Accepted (2026-05-07) Deciders: Alem Basic (CEO) via Phase 2 gap report Consulted: Petter Graff (architect), FlowForge (devops), Proveo (validator) Date: 2026-05-07 Context ALAI's ANVIL (Mac Stud...

ANVIL Filesystem Drift Detection Daemon — Design Specification Purpose: Automated weekly detection of canonical path registry violations, CLAUDE.md scope drift, and filesystem chaos re-introduction. Prevents split-brain recurrence after ANVIL FS Sweep (ADR-02...

ANVIL-FS Phase 3 Wave 3-A — E2E Validation Report Date: 2026-05-07 Operator: Proveo (Angie Jones) Parent MC: #99637 Validation MC: #99703 Validation Overview Method: 10-probe end-to-end validation covering inventory diff, daemon health, boot health, disco...

Status: Accepted 2026-05-07Cross-reference: This follows the ANVIL Filesystem Sweep (Mechanical) — ADR-022. Phase D addresses organizational/tenant concerns.ContextADR-022 documented the mechanical filesystem sweep — orphans, broken refs, PHANTOM daemons. Afte...

⚠️ READ FIRST when deciding any new pathPurpose: Single answer to "where does this go?" — read FIRST before any new path creation, repo clone, or directory move.One rule: every file has exactly one canonical home determined by what it is + whose it is, not by ...

Purpose: Standard git hygiene for the multi-tenant tree. Read BEFORE git init, gh repo create, or any commit decision.1. Repo placement matrixRepo typeCanonical homeGitHub org/ownerVisibility defaultALAI product (Bilko, Drop, Tok)~/business/ALAI-Holding-AS/pro...

Note: This is a live snapshot of the canonical paths registry. Manual sync from ~/system/specs/canonical-registry.md. Last updated: 2026-05-07 (ANVIL Phase D)Purpose: Industry-standard ITIL CMDB / Spotify Backstage pattern. Catalog of canonical paths, their ow...