Open RFCs

This page collects the open design questions that affect the framework's future direction. Many of them are captured in detail in the infrastructure-layer design doc.

The 12 open design questions are documented at:

• Infrastructure layer §10 — open questions and recommendations.

Highlights worth flagging here:

• Build-time vs eval-time TechSpec resolution → recommendation: eval time (build-time freezes specs at framework release; staleness is exactly what we're avoiding).
• MCDA weights problem-specific or framework-default → recommendation: default with per-problem override.
• Same category supporting concurrent technologies in one project → recommendation: yes (real systems use Postgres + DynamoDB simultaneously).
• SDK breaking changes between bundled and live-fetched → recommendation: pin majors in registry, allow live fetch to advance minors only.
• TechSpecs language-specific or shared → recommendation: language-specific (boto3 vs aws-sdk-go-v2 idioms differ enough that shared-and-rendered is worse).

PRs welcome on any of the 12.

See also

• Infrastructure layer — full open-questions list.
• Roadmap — what's currently in flight.