A zero-dependency Java 25 CLI application, built and packaged with zb. Cloned from the bce.design / airails.dev java-cli-app template.

Why it exists: <one or two sentences — the problem this CLI solves and for whom>

Aspiration (seeds the distilled ## Vision): <one aspirational sentence — the outcome this tool chases>

Intended capabilities (seed the BC carving — each becomes a business component):

• —
• —

• <e.g. reads stdin, writes results to stdout, errors to stderr with a non-zero exit>

Java 25+, zb, zunit

zb
java -jar zbo/app.jar

zb compiles, packages zbo/app.jar, and then runs zunit via the post.build.hook in .zb. zunit discovers *Test.java scripts in test/ and runs each with java --source 25 -ea against zbo/app.jar; a failing test fails the build.

Spec-driven BCE 👉 sbce.space: one capability spec ≡ one business component. The spec lives in the BC's package-info.java and is the boundary contract; a green test run is the only definition of done. The /sbce skill and its companions are installed from 👉 airails.dev.

Example — a "time in business hubs" TZ utility:

/sbce new "show the current time in business hubs"  # intent-level (PM/BA or dev): proposes the BC carving, confirm first
/sbce new hubtime                                   # structure-level (dev): the BC is already decided — authors the spec, scaffolds boundary/control/entity
/sbce apply hubtime                                 # converge: close the spec-vs-code gap until the test loop is green

Bare /sbce new (no argument) bootstraps from the ## About prose above — it is the inception seed a PM/BA can fill in.