# SBCE (say "space")

> SBCE is spec-driven Boundary-Control-Entity development where the spec *is* the boundary package's own doc: one `package-info.java`, co-located with the code it governs and published as Javadoc. Code over markdown: no parallel `specs/` tree, no drift.

SBCE is an [airails.dev](https://airails.dev) skill: Markdown your agent reads, not a tool you install. It adds no CLI, no dependencies, and no installation, and it is one Markdown file (about 180 lines) you can read end-to-end before you trust it. One business component maps to one spec written in the boundary package's `package-info.java` ([JEP 467](https://openjdk.org/jeps/467) `///` Markdown). Requirements use [EARS](https://alistairmavin.com/ears/) with stable ids (`R1.2`) that bind bijectively to tests; "done" is a green test run, never a markdown checkbox.

Concerns that span components live one altitude up, in the base package's own `package-info.java`: cross-BC wiring, system invariants (stable ids `Sn`), and shared vocabulary. This system doc is optional (a one-BC project needs none) and still code, so there is still no `specs/` tree.

The workflow is two modes:

- `/sbce new <bc-or-feature>` declares. Give it a BC name (`checkout`) or a feature in plain words (`"let a customer check out a cart"`). It loops clarifying questions until no boundary op or requirement must be guessed, decomposes a feature into one or more BCs you confirm, then writes the spec into each `package-info.java`.
- `/sbce apply <bc>` converges. It reads the gap between spec and code in both directions: `spec → code` adds a boundary method per op, a test per requirement id, and the code to pass them; `code → spec` surfaces any orphan method or test as drift. It loops the stack's own test suite until green. Idempotent: an in-sync, green BC is a no-op.

## Documentation

- [SBCE site](https://sbce.space): Spec-driven BCE, the spec lives in your code.
- [/bce](https://bce.design): Boundary-Control-Entity architecture invariants, composed with SBCE.
- [airails.dev](https://airails.dev): The skill platform SBCE is published on.
- [airhacks.live](https://airhacks.live): Live workshops and sessions on clouds, web, Java, architecture, and agentic development.

## References

- [JEP 467](https://openjdk.org/jeps/467): Markdown Documentation Comments (`///`) used for the spec.
- [EARS](https://alistairmavin.com/ears/): Easy Approach to Requirements Syntax used for requirement statements.