# Distributor Follow-Up Roadmap

Current distributor notification behavior is documented in:

- [Configuration reference](../config.md)
- [Operations guide](../operations.md)
- [Troubleshooting](../troubleshooting.md)
- [App orchestration internals](../internal/app-orchestration.md)
- [Distributor adapter internals](../internal/distributor-adapter.md)
- [Distributor integration contracts](../integrations/distributor/api.md)

This roadmap tracks only future work that is not implemented.

## Deferred Enhancements

- Support a non-failing distributor notification policy such as
  `failure_policy: warn`.
- Upload additional generated artifacts, such as metadata, briefing snapshots,
  data packages, or preflight output.
- Poll distributor status after upload acceptance and expose downstream
  publication failures.
- Add durable retry queues for upload failures.
- Add distributor-specific CLI controls if operators need per-run behavior that
  configuration cannot cover cleanly.

## Boundaries To Preserve

- Keep public CLI syntax stable unless a separate CLI design changes it.
- Keep managed workspace artifact paths and RunIDs stable.
- Keep distributor dependency types behind `internal/adapters/distributor`.
- Keep raw token values out of errors, CLI output, metadata, docs, examples,
  and persisted artifacts.
- Upload explicitly selected generated files; do not make distributor scan the
  weatherreporter workspace.
- Leave destination routing, Markdown-to-HTML transformation, public URLs, and
  nginx layout to distributor.