About DamageBDD

Steven Joseph founded DamageBDD to make behaviour-driven development easier to use in real delivery workflows. The initial problem was practical: keep a shared expectation executable without making every team assemble and maintain its own testing infrastructure.

The core remains straightforward: describe a behaviour, execute it through supported steps, and inspect the result. An HTTP client can submit work to a configured service; running that service requires its documented dependencies.

The project has grown into an evidence-native platform for building, operating, verifying and exchanging software and digital services. ECAI adds knowledge indexing and retrieval, erm adds local interaction, and the Nostr, Blossom and payment integrations connect identities, artifacts and work.

Software delivery often separates the requirement from the code, the report, the explanation and the acceptance decision. DamageBDD aims to keep those records connected so another person can inspect what was done and decide whether it meets the agreed scope.

That supports release acceptance, incident investigation, private knowledge workflows and specialised infrastructure. It does not make a passing test a universal proof of correctness or make every integration equally mature.

Start with the vision, platform map and capability matrix. Choose a small evaluation or run a feature from the manual. The implementation is in the DamageBDD repository.

For project discussion, use the published contact channels. For scoped contribution work, follow the contractor process; acceptance and payment terms belong on the individual work item.