Roadmap

Purpose

This area documents requested, planned, and proposed features that are not yet part of the current working specification.

It exists to separate:

• current behavior, which belongs in docs/documentation/spec
• accepted architectural decisions, which belong in docs/documentation/adr
• historical material, which belongs in docs/documentation/legacy
• future-facing proposals, which belong here

Status Model

Each roadmap proposal should declare one of these statuses:

• requested
• planned
• accepted
• rejected
• superseded

File Convention

Use one feature proposal per file:

• RFC001_<topic>.md
• RFC002_<topic>.md

Recommended Structure

Each RFC should describe:

• purpose
• status
• context
• motivation
• proposal
• expected impact
• dependencies or follow-up work

Current Proposals

• RFC001_cli_help_status_section.md
• RFC002_pre_parser_grammatical_normalization.md
• RFC003_transition_success_learning_graph.md
• RFC004_llm_normalization_interface_layer.md
• RFC005_olia_inference_and_mapper_completion.md
• RFC006_container_dataset_identifier_to_physical_name_contract.md
• RFC007_atomic_container_dataset_creation_and_rollback.md
• RFC008_wrap_context_creation_questions_in_a_panel.md