Developer guide
Abada combines a Java/Spring transactional engine, a React/TypeScript Studio operator UI, a Java Agent Worker sidecar, a Java worker SDK, Docker-based infrastructure and this documentation site. Contributions must preserve the database-authoritative runtime, the frozen public contracts and the agentic governance boundaries (no model call inside a workflow transaction, no auto-apply optimization).
Required toolchain
Section titled “Required toolchain”| Component | Required tool |
|---|---|
| Engine, Agent Worker and SDK | Java 21 and engine/mvnw |
| Studio and documentation | Node.js 24.18.x and npm 11+ |
| Persistence tests | Docker Desktop/Engine for PostgreSQL Testcontainers |
| Local/production composition | Docker Compose v2 |
First contribution
Section titled “First contribution”- Read the contract. Identify the APL/BPMN, runtime, agent, Insight, API, worker, security or deployment promise affected by the change.
- Find the command boundary. Trace the controller or scheduler into its
core
@AtomicRuntimeCommandservice and repositories. - Add evidence. Write parser/unit tests and PostgreSQL behavior tests in proportion to the change.
- Implement narrowly. Prefer existing command, parser, DTO and repository patterns over speculative abstractions.
- Update the guide and contract. Architecture is part of the behavior; keep claims and tests aligned.
- Run the verification matrix. Execute every component check required by the changed surface.