Expand MVP RFC with architecture and planning details

[rovo79]

Summary

• extend the MVP RFC with dedicated sections for resources, tools, and flagship workflows
• document agent runner behavior, security defaults, DX expectations, testing strategy, milestones, versioning, and open questions
• add an ASCII architecture diagram and component overview to clarify system interactions

Testing

• not run

---

Codex Task

[rovo79]

@codex resolve the conflict

[chatgpt-codex-connector]

Summary

• Unified the developer experience and observability guidance into a single section, adding expectations for project scaffolds and Grafana-ready dashboards to reconcile conflicting edits in the RFC. rfcs/RFC-0001-driftcore-mvp.mdL87-L103

Testing

• ⚠️ Tests not run (not requested).

View task →

[rovo79]

@codex This branch has conflicts that must be resolved

[chatgpt-codex-connector]

Summary

• Added shared context framing the combined developer experience and observability expectations section to emphasize reproducibility and debugging signal requirements for the agent runner. rfcs/RFC-0001-driftcore-mvp.mdL87-L108

Testing

• ⚠️ Tests not run (not requested).

View task →

[rovo79]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Breezy!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".