Leonardo da Vinci Prover

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.

1 tools Official Updated Jun 28, 2026 Official Vinkius Partner

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:

  1. observationDocumented — You studied the actual phenomenon firsthand. Not docs. Not tutorials. Direct observation with documented surprises.
  2. domainsConnected — You drew from 2+ unrelated disciplines. Named the transferred insight. Created something neither domain alone would produce.
  3. prototypeBuilt — You built a testable artifact. A spike, a mockup, a proof-of-concept. Something you can break and learn from.
  4. constraintsExploited — You reframed limitations as design parameters. The constraint shaped the invention.
  5. 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=true but 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.
design-thinkingcross-disciplinaryobservationprototypingiterationconstraintsleonardo-da-vincicreative-engineering

1 tools expose this connector's capabilities to your AI agent.

validate_davinci_design

You must: (1) OBSERVE — study the actual system, user, or phenomenon directly. Not documentation, not best practices, not "industry standards" — firsthand observation that reveals surprises, (2) CONNECT — draw from 2+ genuinely UNRELATED disciplines. Name the specific insight transferred from domain B that changes the design in domain A. Not sub-fields — different worlds, (3) PROTOTYPE — build something you can BREAK. Not a description, not a plan — a testable artifact that answers a specific question and reveals what theory could not predict, (4) EXPLOIT CONSTRAINTS — reframe every limitation as a design parameter that shapes invention. "If only we had" is constraint avoidance. The constraint IS the creative fuel, (5) VARY — produce 3+ variations with annotated trade-offs. One final answer has no comparison, no trade-off analysis, no creative exploration. Include the counterintuitive variation. If rejected, fix the specific cognitive gap. Structured reflection tool for creative design rigor — forces direct observation before designing, cross-domain synthesis from unrelated disciplines, testable prototype construction, constraint exploitation as creative fuel, and multiple annotated variations with trade-offs. Catches Observation Absent (designing without studying the actual system, user, or phenomenon — an AI designed an enrollment process without watching a single participant session. Zero direct observations — 47 assumptions about user behavior. The design assumed linear navigation. Real users jumped between steps, revisited forms, and abandoned at step 3 because the progress bar showed 7 remaining steps. Da Vinci dissected 30 cadavers to understand human anatomy before painting the Vitruvian Man. He did not read about anatomy — he observed it with his own hands), Interdisciplinary Blind (solving the problem inside one domain without asking what other fields could teach — a checkout flow designer who never studied game design's concept of "variable ratio reinforcement" misses why certain progress indicators increase completion rates by 23%. A data pipeline architect who never studied fluid dynamics does not see that batch processing creates the same pressure waves as water hammer. Da Vinci connected anatomy to painting, fluid dynamics to civil engineering, botany to architectural spiral staircases. The transfer IS the innovation), Prototype Skipped (describing a solution instead of building a testable artifact — "the proposed architecture will handle scale" is paper. A load test that proves 10,000 concurrent connections with p99 < 200ms is a prototype. A clickable Figma mockup that reveals users cannot find the save button is a prototype. Da Vinci built a working model of his aerial screw — he did not just sketch it), Constraint Ignored (treating limitations as blockers instead of creative fuel — "if only we had more budget" is constraint avoidance. Twitter's 140-character limit created an entire communication style. The iPhone's single button forced a revolutionary gesture interface. Da Vinci's sfumato technique was invented because oil paint dries slowly — a limitation that became the signature of the Mona Lisa), and Iteration Refused (presenting one final answer without exploring alternatives — Da Vinci drew 50 versions of the Virgin's face in the Virgin of the Rocks. A design with no variations has no trade-off analysis. Variation A optimizes for speed. Variation B for reliability. Variation C is the counterintuitive approach — what if the opposite were true? Without comparison, there is no choice, only assumption). Call once per design, architecture, or creative solution

See how to talk to your AI agent using Leonardo da Vinci Prover.

The best approach for this enrollment process is a 3-step flow: registration → verification → confirmation. This is the industry standard and most participants expect it.

OBSERVATION_ABSENT — 'Industry standard' and 'most participants expect it' are borrowed knowledge — someone else's observation of someone else's participants. Da Vinci dissected cadavers to understand muscles he could not see from outside. What does YOUR enrollment data show? How many participants abandon at step 2? Where do they hesitate? What does a 5-minute observation session reveal that 'best practices' cannot? Observe YOUR process before designing for it.

Observed: watched 23 participant sessions on our current enrollment. 68% abandon at the personal details form — they see 11 fields and leave. The form itself is the friction, not the step count. Cross-domain: behavioral economics (Schwartz's paradox of choice) — reducing options reduces anxiety. Applied: streamlined form with 3 fields (postal code auto-fills location details) mirrors the 'smart default' principle from game design — players get moving instantly, customize later. Prototype: built a clickable walkthrough with the 3-field design. Tested with 8 participants — 7/8 completed in under 40 seconds. One participant wanted manual country selection (edge case: overseas military address). Constraint: budget for only 1 address verification per submission (lookup service quota). Exploited: postal-code-first design exists BECAUSE of the verification limit — one lookup returns city+state+country. Without the quota constraint, we would have built a 5-field form with real-time checks on each field, which is worse experience. Variations: (A) Single-page — all fields visible, scroll-based, optimizes for transparency. Trade-off: cognitive load from seeing payment before address. (B) Progressive disclosure — show only the current field, expand next on completion. Optimizes for focus. Trade-off: participant cannot review previous answers without scrolling back. (C) Conversational — guided sequential questions. Optimizes for simplicity. Trade-off: slower for experienced participants who can parallel-fill. Recommendation: B for walk-in participants (78% of volume), A for experienced staff, with shared processing.

DESIGN_PROVEN — Da Vinci Method complete. Observation: 23 participant sessions, 68% abandon at 11-field form — friction identified empirically, not from 'best practices.' Cross-domain: behavioral economics (paradox of choice) + game design (smart defaults) transferred to enrollment design — genuine synthesis. Prototype: clickable walkthrough tested with 8 participants, 87.5% success in 40 seconds, edge case (overseas address) documented. Constraint: address verification quota became the design parameter — postal-code-first exists BECAUSE of the limit. Variations: 3 alternatives (single-page, progressive disclosure, conversational) with annotated trade-offs and context-specific recommendation. This is design.

Observed: analyzed 3 months of operational incident logs — 340,000 delays, 72% are bottleneck-related, concentrated in the order lookup step. Cross-domain: from a purely operational perspective, we need to add a staging buffer and streamline the search procedure.

INTERDISCIPLINARY_BLIND — Observation passes: 340K delays, 72% bottlenecks, concentrated step — this is empirical data. But cross-domain fails: 'from a purely operational perspective' is single-domain thinking. Da Vinci connected fluid dynamics to painting. What does queueing theory (mathematics) teach about your bottleneck pattern — is it gradual accumulation or a sudden surge? What does urban planning teach about your lookup flow — is this a highway bottleneck or a neighborhood dead-end? The transferred insight changes the solution: a staging buffer fixes symptoms, but queueing theory reveals whether the problem is concurrency (add staff) or sequencing (parallelize steps).

No. Da Vinci was an engineer, anatomist, architect, and painter. This tool applies his method to any creative problem: process design, product design, experience flows, organizational structure, service design, operational improvement. The 5 pivots — observe, connect domains, prototype, exploit constraints, iterate — apply wherever a human designs something for other humans.

Related Connectors