downstream-exports
Downstream exports
The mirror image of the external-repo-intake skill. That skill covers content flowing in from other repos; this one covers our content flowing out to the other hosts.
Nothing under exports/ is edited by hand, ever. Every file there is compiler output from plugins/ plus adapters/, and python scripts/daodan_build.py --check fails the build the moment a committed package stops reproducing from its source. If an export looks wrong, the bug is in the kernel, the adapter, or the compiler. Fixing the export directly produces a change that the next build silently deletes.
The split that decides where a change goes
The core owns roles, workflow dependencies, required context isolation, joins and observable contracts. A harness owns host APIs, dispatch, scheduling, retries and result collection.
| The change is about | It belongs in |
|---|---|
| what a reviewer looks for, what a workflow means, what a report must contain | plugins/<name>/ (Markdown for behaviour, TOML for structure) |
| which host tool satisfies a neutral capability | adapters/<host>/capabilities.toml |
| which coordination strategies a host supports, and in what order | adapters/<host>/coordination.toml |
| where a component lands in a host's package | adapters/<host>/layout.toml |
| the wrapper text that tells a host harness how to dispatch | adapters/<host>/templates/ |
| how one host enforces a neutral policy | adapters/<host>/policies/<name>/ with policy.toml naming what it implements |
| a meaning that genuinely cannot be rendered from the generic templates | adapters/<host>/overrides/<plugin>/<workflow>/ |