Guide scope and source of truth

This site is a reader-oriented map of Abada’s technical architecture. It does not replace the detailed Markdown contracts in the repository.

When documents disagree

Do not broaden a product claim. Treat the runtime semantics, BPMN support, deployment support, API v1, worker protocol and security documents as the contract. Fix the implementation or narrow the guide and update its tests in the same change.

Documentation layers

flowchart TD
    S[Specification and ADRs] --> C[Versioned contracts]
    C --> G[Curated architecture and developer guide]
    C --> T[Executable tests and compatibility manifests]
    T --> E[Release evidence]
    G --> E

• Specifications and ADRs record normative requirements and decisions.
• Contracts define supported behavior and compatibility promises.
• This site connects the contracts into understandable workflows.
• Executable tests prove claims at parser, API, persistence and cluster boundaries.
• Release notes and the roadmap record the evidence for each gate.

Direct entry points

Architecture overview

Developer guide

Authoritative contracts

Documentation authoring

Deferred user documentation

Task-user, process-modeler and operator journeys will form a separate user guide. Deferring that track keeps the current milestone focused on stabilizing the architecture vocabulary, developer workflows and executable contracts before turning them into product tutorials.