dft-gpaw

To route GPAW DFT requests, specify your task intent and prerequisites so the router can dispatch your request to the matching subskill for static SCF, relaxation, DOS, or band-structure workflows.

GPAW workflow orchestration maps user intent to specific subskills, ensuring prerequisites are validated and enforcing a consistent handoff to the submission layer with a uniform output contract.

Yes, you need to validate prerequisites before starting a GPAW band-structure calculation, as the router checks minimal requirements and enforces guardrails before dispatching to the submission skills.

Yes, you can use this router for GPAW static SCF and relaxation tasks, as it dispatches requests directly to the dft-gpaw/static and dft-gpaw/relax subskills based on your specified intent.

The best way to manage context across GPAW DFT tasks is using this router, which collects minimal shared context and preserves an explicit output contract across all dispatched subskills.

Your GPAW DFT workflow might fail to hand off to the submission layer if minimal prerequisites are not met, as the router enforces consistent handoffs and guardrails before processing.