AI tool comparison
Context Engineering Reference vs MDV
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
Context Engineering Reference
Runnable 5-layer stack that enforces RAG output against retrieved context
75%
Panel ship
—
Community
Paid
Entry
Context Engineering Reference Implementation is an open-source project by Brian Carpio at OutcomeOps that makes a concrete claim: RAG is not enough. The project defines and implements a 5-layer context engineering stack — Corpus, Retrieval, Injection, Output, and Enforcement — where the final Enforcement layer is what separates it from standard retrieval-augmented generation pipelines. The enforcement layer actively verifies that generated content actually reflects what was retrieved, closing the loop on hallucinations that occur when an LLM "knows" something from pretraining that contradicts the retrieved document. The reference implementation runs against Amazon Bedrock and Claude using a Spring PetClinic codebase with Architecture Decision Records as the corpus — making it practical to study with real enterprise artifacts. Launched April 17 and already trending as a Show HN post, the project is winning the framing war around "context engineering as a discipline." As prompting has matured into prompt engineering, RAG is now maturing into something more rigorous. This is one of the cleaner articulations of that shift.
Developer Tools
MDV
Markdown that embeds live data, charts, and slides — docs that stay current
75%
Panel ship
—
Community
Free
Entry
MDV (Markdown Data Views) is a markdown superset that extends standard .md files with embedded live data, interactive charts, and presentation-ready slides. The goal is a single document format that serves simultaneously as developer documentation, a live dashboard, and a shareable slide deck — without requiring a separate tool for each use case. MDV files can embed SQL queries, API calls, and data transforms directly in markdown, with results rendering as tables, charts, or visualizations on the fly. The syntax extends frontmatter conventions that markdown users already know, keeping the learning curve minimal. Output can be previewed in a local server, exported as HTML, or converted to a slide deck — the same source file serves all three outputs. MDV surfaced on Hacker News with 44 points and active discussion around the concept of "living documents" — reports and runbooks that stay current because their data sources are live queries rather than screenshots. For developer-heavy teams who live in their editors and resist adopting heavyweight BI tools, MDV offers a markdown-native alternative that slots into existing documentation workflows.
Reviewer scorecard
“The Enforcement layer is the real insight here — I've seen so many RAG systems where the LLM just ignores the retrieved context and answers from weights anyway. Having a verifiable check that output actually uses retrieval is table stakes for production. This implementation shows exactly how to do it.”
“I've been writing separate README, dashboard, and slide deck for the same data for years. MDV collapsing those into one source-of-truth file is the kind of DRY solution I didn't know I needed. The frontmatter-extension approach means it works in existing markdown tooling. Shipping for internal docs immediately.”
“The 5-layer framing is useful for communication but it's mostly reorganizing concepts practitioners already know. The enforcement check adds overhead and the reference implementation is tied to Bedrock — not everyone wants another AWS dependency in their AI stack.”
“Embedding live SQL queries in documentation is a security and maintainability footgun. Who reviews the data access in a markdown file? The concept is compelling but the execution needs a clear story for access control, query sandboxing, and handling stale or broken data connections in production docs.”
“Naming and systematizing a practice is how it scales. 'Context engineering' as a discipline with a formal 5-layer model will shape how teams hire, design systems, and evaluate results — just as 'prompt engineering' gave teams a shared vocabulary for something they were already doing intuitively.”
“The next evolution of documentation is documents that are executable — that don't just describe the system but are the system. MDV is an early step toward that: markdown that isn't just readable by humans but queryable, renderable, and automatable by agents. Worth watching closely.”
“For teams building editorial AI tools or knowledge bases, the enforcement layer concept translates directly to brand safety and accuracy guarantees. Knowing your AI isn't wandering off into its own hallucinations is what makes these systems publishable.”
“Being able to write a client report in markdown that automatically pulls live data and renders as a slide deck is genuinely transformative for independent consultants and content creators. MDV could replace Notion, Google Slides, and a BI tool for a substantial percentage of small team workflows.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.