CaseHub extension — immutable audit ledger with hash chain, peer attestations, and EigenTrust reputation for Quarkus applications

Domain model and SPI interfaces — no JPA, safe for any module to depend on

Org-level parent POM and BOM for casehubio projects

Quarkus Native agent communication mesh — peer-to-peer channels, typed messages, shared data, presence

Enums, SPI interfaces, and exception types — no JPA, safe for any module to depend on

Generic work management implementations: WorkBroker, built-in WorkerSelectionStrategies, and ClaimSla policies. Jandex-indexed library — no deployment module needed. No JPA entities, no REST resources, no Quarkus-specific runtime dependencies beyond CDI.

Pure Java shared SPI contracts for work management. Zero runtime dependencies. CaseHub and quarkus-work depend on this without pulling in implementation details.

Human-scale WorkItem lifecycle management — expiry, delegation, escalation, audit trail. CaseHub platform module — human-scale WorkItem lifecycle management with optional integrations for Quarkus-Flow, CaseHub, and Qhorus.

HTTP-based outbound connectors: Slack, Teams, Twilio SMS, WhatsApp. No dependencies beyond CDI and java.net.http — usable in any Quarkus application.

HTTP-based outbound connectors: Slack, Teams, Twilio SMS, WhatsApp. No dependencies beyond CDI and java.net.http — usable in any Quarkus application.

Lightweight outbound message connectors for the CaseHub platform. Provides a unified Connector SPI with built-in implementations for Slack (Incoming Webhooks), Microsoft Teams (Adaptive Cards), Twilio SMS, WhatsApp Business API, and Email (quarkus-mailer). Zero heavy dependencies — HTTP-based connectors use java.net.http only.

In-memory repository implementations for use in unit tests of applications that embed CaseHub Work. No datasource or Flyway required.

Optional module linking WorkItems to external issue trackers (GitHub Issues, Jira, Linear, etc.). Provides a pluggable IssueTrackerProvider SPI, a REST API for managing links, and a GitHub implementation as the default. Add your own tracker by implementing IssueTrackerProvider with @ApplicationScoped @Alternative @Priority(1). See docs/workitems-vs-issue-trackers.md for guidance on when to use WorkItems vs issue trackers and best practices for using them together.

JPA entity classes and Hibernate Reactive repository implementations for the engine SPI

Reactor implementation — event handling, worker scheduling, context management, goal and milestone evaluation

Quartz-based implementation of JobScheduler SPI

the Case Hub

Public API for Case Hub — CaseHub base class, CaseHubDefinition, Workers, Goals, Milestones, and DispatchRules

Optional immutable audit ledger — hash-chained case lifecycle entries via casehub-ledger

JSON Schema and generated model classes for declarative YAML case definitions

Common classes for the Case Hub engine — CaseInstance, PlanItemInstance, etc.

In-memory store implementations for fast unit testing without a database

Email connector backed by quarkus-mailer. Separate module because quarkus-mailer is a Quarkus extension that stalls at augmentation time if not configured — keeping it separate makes it truly optional.

CDI bridge for suspending Quarkus-Flow workflows on WorkItems and resuming them when a human resolves the item.