box-factory-architecture

Component selection depends on your use case's scope and interaction needs. Skills handle isolated tasks with return-based delegation, agents coordinate multi-step workflows, commands execute direct operations, and hooks integrate at system boundaries. Box Factory architecture guides this choice based on isolation requirements and progressive disclosure needs.

Progressive disclosure loads knowledge and dependencies only as needed during execution rather than upfront. This reduces cognitive overhead and enables cleaner component interactions by filtering knowledge deltas—delivering only context relevant to each component's immediate task.

Delegation follows return-based patterns where parent components invoke sub-agents with specific tasks and receive results back for integration. Box Factory architecture defines isolation boundaries that prevent tight coupling, enabling clean multi-component workflows where each component handles its isolated responsibility.

Components interact through defined boundaries that enforce return-based delegation and prevent direct state mutation. Isolation ensures debugging visibility, enables independent testing, and supports knowledge-delta filtering so each component receives only the context it requires.

Yes. Box Factory principles apply across new plugins and refactored existing architectures. The framework addresses isolation, delegation patterns, progressive disclosure, and cross-component interactions, making it suitable for retrofitting multi-component workflows and improving architecture clarity.

Isolation creates clear component boundaries that make debugging straightforward—failures surface at specific interaction points rather than cascading through tightly coupled code. Return-based delegation provides explicit data flow, making it easier to trace issues and understand which component caused them.