Skip to content
Arka Platform

Developer Documentation — arka-deck

Audience: contributor, developer adding an API route, writing an addon, wiring a new AI provider, running tests, preparing a release.

Section titled “Recommended guided path”
  1. Understand the architecture — architecture/
  2. Locate contracts and surfaces — reference/
  3. Extend arka-deck — extension/
  4. Know the addons and providers already wired — addons-firstparty/, providers-firstparty/
  5. Adopt the contribution workflow — workflow/

Table of contents

Section titled “Table of contents”

Architecture

Section titled “Architecture”

architecture/ covers the hexagonal layers, inbound and outbound ports, composition root, event bus, Materializer pattern and storage.

Reference

Section titled “Reference”

reference/ groups the HTTP route list, the CLI, environment variables, CI scripts and the projects/workspaces mechanics.

Extension

Section titled “Extension”

extension/ gathers step-by-step tutorials to write an addon, a provider, a worker or a connector, together with the formal addon contract and the first-party catalogue.

First-party fact sheets

Section titled “First-party fact sheets”

addons-firstparty/ documents each embedded addon (cortex-lite, cortex-actions, memory-local, mission-guardian, squad-leader, squad-orchestration, notion-connect).

providers-firstparty/ documents each embedded AI provider (claude_code, google-genai, codex_cli).

Contributor workflow

Section titled “Contributor workflow”

workflow/ covers cloning and first launch, tests, AI agent guide (working rules), GitNexus, CI gates, release procedure and conventions (commits, PR, DCO).

Architecture decisions

Section titled “Architecture decisions”

Structural choices are documented as ADRs.

→ ADR Index

Cross-cutting conventions

Section titled “Cross-cutting conventions”

→ Federated repository convention for addons and workers

Documentation status

Section titled “Documentation status”

The skeleton is in place. Existing stable content is migrated from the previous tree (docs/dev/architecture.md, docs/dev/events-guide.md, etc.) during lot P3. Missing content (exhaustive HTTP API reference, complete extension tutorials) lands during lot P4.

Follow main or the root CHANGELOG for details.