Skip to main content

Platform Layer — File Map

Reference untuk scaffold platform layer (lihat decisions.md: “Platform layer scaffold added”). Semua file di bawah masih stub kosong — pakai tabel ini buat inget apa yang harus diisi tiap file pas mulai kerja. Prinsip: layer ini CONSUME core ARCLUX yang udah ada (engine/graph/ impact/parser), gak duplikasi. Lihat ARCHITECTURE_MAP.md.

packages/runtime/

packages/services/

packages/scheduler/

packages/environment/

packages/workspace/

packages/terminal/

packages/storage/

packages/networking/

packages/security/

packages/system/

packages/diagnostics/

packages/editor/

packages/language/

packages/orchestration/

apps/cli/commands/ (baru)

apps/web/app/api/ (baru)

packages/kernel/

packages/semantic-diff/

packages/notifications/

packages/package-manager/

Blueprint Integration — Alur Editor

Diagram asli (lihat decisions.md): Developer ketik → Editor → incremental analysis → Error/Symbol/Dependency → Diagnostics → Impact Engine → Affected Files → Notification → developer diarahkan ke file+line.

Blueprint Integration — Semantic Diff Pipeline

Diagram asli: Text Diff → Symbol Diff → AST Diff → Dependency Diff → Impact Diff → Architectural Diff. Catatan penting: semantic-diff TIDAK bikin parser/graph engine kedua. Semua tahap di atas WAJIB memanggil fungsi existing di packages/engine dan packages/diff, bukan reimplementasi. Kalau nemu diri lu nulis AST walking baru di sini, itu tanda salah arah — harusnya panggil packages/parser yang udah ada.

Blueprint Integration — Arsitektur Besar

ARCLUX ENGINE (existing, JANGAN diduplikasi) packages/engine, graph, impact, detectors, diff, search, rules, watcher ↓ dikonsumsi oleh PLATFORM LAYER (baru, layer ini) packages/runtime, kernel, services, scheduler, environment, workspace, terminal, storage, networking, security, system, package-manager, notifications ↓ dikonsumsi oleh DEVELOPER LAYER (baru, interface) packages/editor, language, semantic-diff, diagnostics
  • apps/cli/commands/* (baru)
  • apps/web/app/api/* (baru) Arah dependency SATU ARAH: Developer Layer → Platform Layer → ARCLUX Engine. Platform Layer tidak boleh reimplement logic yang udah ada di Engine. Engine tidak boleh depend balik ke Platform Layer (supaya engine tetap bisa dipakai standalone via CLI existing tanpa perlu platform layer nyala).

File existing yang perlu di-edit (bukan file baru, tapi kena sentuh)