Leonardo da Vinci Prover MCP Connector for Claude
A+An AI designed an enrollment process without watching a single participant session. Zero observations — 47 assumptions. It solved the problem inside one domain, never asking what psychology, architecture, or game design could teach about friction. It presented one final concept. No sketches. No variations. No constraints exploited. Da Vinci filled 7,000 notebook pages with cross-domain observations before building anything. This tool forces that method: observe, connect disciplines, prototype, exploit constraints, iterate.
AI agents design without observing. They solve inside one domain. They describe instead of building. They present one final answer. Da Vinci would have filled 50 pages of sketches before committing to a single line.
The Problem
LLMs commit five design failures that produce mediocre, untested, single-perspective solutions:
- Observation Absent — 'Based on best practices, the enrollment should have 3 steps.' No participant sessions watched. No friction points measured. No actual process studied. 'Best practice' is borrowed knowledge from someone else's observation of someone else's participants.
- Interdisciplinary Blind — 'From a purely operational perspective, the structure should use separate divisions.' One domain. Da Vinci connected anatomy to painting — he understood that muscle tension determines how fabric drapes. What does psychology teach about your process flow? What does music theory teach about your workflow rhythm?
- Prototype Skipped — 'The proposed structure uses a tiered approval chain with parallel review tracks.' A description. Not a prototype. Da Vinci built physical models of bridges, flying machines, and hydraulic systems. He did not write planning documents — he constructed things he could break.
- Constraint Ignored — 'If only we had a larger budget, we could build the ideal solution.' Da Vinci designed the aerial screw with no engine. The constraint IS the invention — human-powered rotation shaped the entire design. Your budget limitation is creative fuel, not a blocker.
- Iteration Refused — 'The solution is a 3-tier architecture with React frontend.' One answer. One concept. Final. Da Vinci's notebooks contain 50+ sketches of a single muscle group, each from a different angle with different annotations. Where are your variations?
How It Works
5 Decision Pivots following da Vinci's documented methodology:
- observationDocumented — You studied the actual phenomenon firsthand. Not docs. Not tutorials. Direct observation with documented surprises.
- domainsConnected — You drew from 2+ unrelated disciplines. Named the transferred insight. Created something neither domain alone would produce.
- prototypeBuilt — You built a testable artifact. A spike, a mockup, a proof-of-concept. Something you can break and learn from.
- constraintsExploited — You reframed limitations as design parameters. The constraint shaped the invention.
- variationsExplored — You produced 3+ alternatives with annotated trade-offs. Not one final answer.
The Verdict Matrix
| First Failing Pivot | Verdict | Meaning |
|---|---|---|
| observationDocumented = false | OBSERVATION_ABSENT | Designed without studying the actual system. |
| domainsConnected = false | INTERDISCIPLINARY_BLIND | Solved within one domain only. |
| prototypeBuilt = false | PROTOTYPE_SKIPPED | Described but did not build. |
| constraintsExploited = false | CONSTRAINT_IGNORED | Treated limitations as blockers. |
| variationsExplored = false | ITERATION_REFUSED | One answer. No alternatives. |
| All pivots pass | DESIGN_PROVEN | Observed, connected, built, exploited, varied. |
Why It Works
- Tool calls are obligations. The agent cannot propose a design without documenting observations, naming cross-domain connections, describing a testable artifact, reframing constraints, and listing variations.
- Consistency engine catches contradictions. If the agent claims
observationDocumented=truebut says 'based on best practices,' the engine rejects — borrowed knowledge is not observation. - Semantic traps detect single-domain thinking. 'From a purely technical perspective,' 'the solution is,' and 'if only we had' trigger automatic rejection.
Related Connectors
Relative & Parallel Key Finder MCP
Instantly discover relative, parallel, and related musical keys based on any input key.
WHO-5 Wellbeing Index MCP
Calculate the WHO-5 Well-Being Index score and identify potential wellbeing risks.
Bread Proofing Calculator MCP
Predict fermentation durations for bulk and final proofing based on yeast concentration and temperature.
US Building Permit Fee Estimator MCP
Estimate building permit, plan check, and inspection fees for major US cities.