Architecture Decision Records

View Source

This directory contains Architecture Decision Records (ADRs) for Conjure.

ADRs document significant architectural decisions made during the development of this project, providing context for future contributors and maintainers.

Index

IDTitleStatus
ADR-0001Use ADR format for architectural decisionsAccepted
ADR-0002Pluggable executor architecture via behavioursAccepted
ADR-0003ZIP format for .skill packagesAccepted
ADR-0004API-client agnostic designAccepted
ADR-0005Progressive disclosure for token efficiencyAccepted
ADR-0006XML format for system prompt fragmentsAccepted
ADR-0007YAML frontmatter in SKILL.mdAccepted
ADR-0008GenServer-based skill registryAccepted
ADR-0009Local executor without sandboxingAccepted
ADR-0010Docker as recommended production executorAccepted
ADR-0011Anthropic Skills API IntegrationProposed
ADR-0012Mix tasks for developer experienceProposed
ADR-0013Docker infrastructure and image distributionProposed
ADR-0014Centralized security moduleProposed
ADR-0015Configuration-driven skill loadingProposed
ADR-0016Test strategy for external dependenciesProposed
ADR-0017Skill caching and hot-reloadProposed
ADR-0018Artifact ReferencesProposed
ADR-0019Unified Execution ModelProposed
ADR-0020Backend Behaviour ArchitectureAccepted
ADR-0021Hybrid Multi-Backend SessionsProposed
ADR-0022Pluggable Storage StrategyProposed

ADR Format

Each ADR follows this structure:

# ADR-NNNN: Title

## Status
Proposed | Accepted | Deprecated | Superseded by [ADR-NNNN](link)

## Context
What is the issue that we're seeing that is motivating this decision?

## Decision
What is the change that we're proposing and/or doing?

## Consequences
What becomes easier or more difficult because of this change?

Creating New ADRs

  1. Copy the template from 0000-template.md
  2. Use the next available number
  3. Fill in all sections
  4. Update this README index
  5. Submit for review

References