# Future Work

Current Notarius behavior is documented in the canonical README, CLI,
configuration, operations, internal, and integration docs. This roadmap records
future work only.

## Candidate Product Work

- Additional input adapters, such as Markdown or note-export formats.
- Additional D&D extractors beyond spell casts.
- Add non-file reference producers, such as prior-run artifacts, derived
  summaries, or entity registries, without changing module-facing reference
  item contracts.
- Add token budgeting and model context-window management for reference content.
- Add per-slot or per-chunk inclusion policies so modules can avoid repeating
  large reference content in every prompt when that becomes important.
- Add structured or parsed references, such as typed roster schemas, when a
  module has a clear need for more than opaque UTF-8 text.
- Add reference caching, preprocessing, summarization, embedding, or retrieval
  if references become large enough to require preprocessing.
- Cross-lane entity normalization.
- Cross-chunk semantic deduplication.
- Configurable validator chains with production validator modules.
- Multiple effective LLM profiles in one run.
- Parallel execution where it preserves deterministic manifests and diagnostics.
- Additional output encoders.

## Candidate Architecture Work

- Evaluate replacing the local LLM adapter with an import from
  `gitea.maximumdirect.net/eric/scriptorium`, provided it preserves Notarius
  boundaries around provider plumbing, prompt ownership, diagnostics, and secret
  handling.

## Candidate Operational Work

- Packaged release artifacts for alpha distribution.
- A documented versioning and release process.
- Optional generated example output fixtures with a regeneration procedure.
- Additional diagnostics or reporting views if operator workflows need them.

## Non-Goals To Revisit Deliberately

- A general workflow language.
- Structural module selection through ad hoc run flags.
- Storing secrets in config files, diagnostics, manifests, or examples.