blong-layer

You can organize Blong realm handlers into functional groups by structuring them into named server-side layers such as gateway, adapter, orchestrator, error, and test. This enforces a documented layer taxonomy and folder structure to ensure clear separation of concerns.

The best way to separate concerns is applying a layered architecture that groups handlers under gateway, adapter, orchestrator, error, and test directories. This aligns workstreams by functional concern to reduce conflicts and improve maintainability.

You control handler deployment activation by organizing handlers into layers that can be activated or deactivated per environment. This enables feature flags and safer rollouts by toggling specific functional groups within a Blong realm.

Yes, the one-file-per-handler pattern is supported and recommended to keep changes isolated. You place handlers under the appropriate layer directories alongside a server.ts file to maintain clear boundaries within the realm.

You need layered groups when your Blong realm requires improved modularity, clear responsibilities, and controlled activation across environments. It applies to realms with server-side layers needing a documented taxonomy and configuration patterns.

Yes, organizing Blong handlers into layers enforces a specific folder structure and configuration patterns. You must create a skill folder with a root SKILL.md, define frontmatter, and structure realms with server.ts placing handlers under layer directories.