module-dev

ADHD module development follows a standardized SOP covering planning, scaffolding, implementation, configuration, testing, and verification. It enforces mandatory pre-reads, anti-hallucination constraints, module structure, and naming conventions across foundation, runtime, and dev layers.

You scaffold an ADHD framework module by following the explicit SOPs for planning, implementation, configuration, and testing. The process requires applying pre-coding checks, anti-hallucination constraints, and proper layer taxonomy to ensure safe, package-based imports.

Anti-hallucination constraints in module architecture require developers to follow explicit pre-coding checks and reference workflows. These constraints prevent common integration issues by enforcing proper module structure, naming conventions, and standardized layer taxonomy across the ADHD framework.

Yes, the module development SOP supports MCP-aware workflows within the ADHD framework. It promotes safe, package-based imports and robust error handling while guiding developers through scaffolding and verification across foundation, runtime, and dev layers.

Scaffolding modules without standardized conventions introduces severe onboarding friction and integration issues. It bypasses critical anti-hallucination constraints and pre-coding checks, leading to inconsistent module architecture and unsafe imports across ADHD framework layers.