Skip to content
Arka Platform

First-party addons — arka-deck

Audience: developer who wants to understand or modify an addon embedded in arka-deck.

Status

Section titled “Status”

Embedded addons are wired explicitly in the composition root. There is no active third-party marketplace today: any production addon stays first-party. The addon contract is stabilized to allow, eventually, external extensions.

Contents

Section titled “Contents”
  • cortex-lite.md — local Cortex runtime (sidecar), project materialization, agent context
  • cortex-actions.md — Cortex Actions panel, project favorites, suggestion worker
  • memory-local.md — local project memory, storage, before-turn augmentation
  • gouvernance-lite.md — Cortex-compatible local policies, snippets, followup
  • mission-guardian.md — mission state, leader and QA gates, evidence
  • squad-leader.md — squad composition, Leader Pack, squad-creator worker
  • squad-orchestration.md — multi-agent LangGraph orchestration, mission cycle
  • notion-connect.md — Notion connector, scopes, OAuth, audit trail

To write a new addon

Section titled “To write a new addon”

See the tutorial ../extension/ecrire-un-addon.md and the formal reference ../extension/contrat-addon.md.

Documentation status

Section titled “Documentation status”

The skeleton is in place. Fact sheets are migrated from docs/dev/addons/ during lot P3 (except mission-guardian.md which is new).