bclearer-pipeline-engineer

To enforce bclearer pipeline stage boundaries, validate that logic is placed only in canonical stages like 1c_collect, 2l_load, 3e_evolve, 4a_assimilate, and 5r_reuse. This prevents cross-stage contamination and ensures alignment with approved architecture designs.

The canonical bclearer pipeline layout separates logic into specific stages: 1c_collect, 2l_load, 3e_evolve, 4a_assimilate, and 5r_reuse. Adhering to this structure ensures conformance with platform-specific rules and prevents logic leaks across pipeline stages.

Handle BIE domain object implementation by delegating the work to the bie-data-engineer skill. This BIE domain delegation ensures specialized domain logic is managed appropriately, keeping the bclearer pipeline focused on stage-specific data flow and conformance.

Refactor bUnit type extraction by applying conformance checking and bclearer framework rules to restructure the code. This ensures the bUnit refactoring meets BORO-style code compliance and maintains strict interop service boundary enforcement.

Yes, bclearer pipeline conformance checking includes built-in verification checklists for code style, test coverage, and pipeline structure. This ensures implementations meet all bclearer framework requirements and pass reviews on the first attempt.

Logic leaks across bclearer pipeline stages happen when stage boundaries are not strictly enforced. You must validate stage logic placement and ensure no cross-stage contamination exists between canonical stages to achieve BORO-style code compliance.