The neighbors, with sources

Each claim names the neighbor that comes closest, so it can be checked. A “—” means not found in its public README or tree, not proven absent.

Capabilities

✅ yes · ◐ partial · — not found

What no neighbor combines

1. 1

   Architecture is data, and one declaration has three effects

   Closest: a-pavithraa offers an architecture choice, as prose inside one skill. Seed4J generates hexagonal structure, but nothing reads the architecture once an agent starts writing.

2. 2

   Write territory as data, enforced by one hook

   Closest: loiane's enforce-files-in-scope.sh enforces scope per active task, a genuinely similar idea. Here territory is per class and stored as data, and shell writes and the end-of-turn sweep are covered.

3. 3

   A spec pipeline with one owner per layer, frozen when approved

   Closest: loiane and plinth have Spring-aware SDD pipelines; Spec Kit and OpenSpec are the generic references. None has design steps for Spring Security, outbound HTTP, Kafka and jobs, or freezes the spec with a hook.

4. 4

   Updates with provenance and migration notes

   Closest: Spec Kit, OpenSpec, BMAD and Spec Kitty have an upgrade command. None found detects local edits by hash before overwriting.

5. 5

   A deterministic, per-run execution trail

   Closest: None found among the neighbors.

6. 6

   A harness that validates itself in CI

   Closest: None found. The neighbors validate the generated code, not their own instruction files.