Skip to content
Arka Platform

Architecture — arka-deck

Audience: developer who wants to understand how arka-deck is structured, where the business logic lives, how components communicate and where to add code.

Contents

Section titled “Contents”
  • overview.md — overview: hexagonal layers, diagram, ESLint import rules, technical stack
  • ports-inbound.md — exhaustive list of inbound (driving) ports; role, main methods
  • ports-outbound.md — exhaustive list of outbound (driven) ports; role, typical implementations
  • composition-root.md — createCoreContainer, createWebContainer, instantiation order, addon wiring
  • event-bus.md — publish/subscribe, event naming conventions, patterns and anti-patterns
  • materializers.md — agent artifact materialization pattern (agents, hooks, skills) to local files
  • stockage.md — local SQLite, filesystem allowlist, AES-256-GCM secrets, anti-symlink

Principles

Section titled “Principles”
  • The core/ is isolated: it knows neither I/O, nor composition, nor addons (see ADR 0001).
  • Addons consume core ports; they never depend on each other (see ADR 0002).
  • Agent artifacts produced by arka-deck go through Materializers, never through direct writes (see ADR 0003).

Documentation status

Section titled “Documentation status”

The skeleton is in place. The content of overview.md is migrated from docs/dev/architecture.md during lot P3. The other files are written during lot P4 from the source code and from the technical audit results.