Interactive explanation

Prompt-driven versus context-driven delivery

One change request, two approaches to AI-assisted delivery. See how a version-controlled specification and verification gates improve predictability.

One request

Prompt driven Each developer prompts in their own words Context driven Caravel works from a locked specification Change request Add step up authentication to the new payee journey Developer A "add MFA when apayee is added" Developer B "OTP step up onrisky payees" Developer C "reuse the loginflow for payees" Model fills the gaps Three differentimplementations PASS FAIL NO AUDIT EVENT Review compares against personal judgement, so the work goes round again Specification v1, locked Acceptance criteria and golden tests Knowledgebase v2.4 Templatestep up journey AnAnalyst ArArchitect DvDeveloper TsTester Run 1, run 2, run 3: verified against the same tests PASS PASS PASS Human arbitrates against the spec

Prompt driven: context per call

Each call resends the conversation so far

Context driven: context per call

Each gate passes a bounded package, not the history

Bars show context sent on each model call; the line shows the running total. Illustrative, same scale on both sides.

Explore a software change from intent to verified release
Change request: step up authentication on the new payee journey

    Illustrative scenario. Version numbers and identifiers are examples.

    Illustrative scenario. Example tests and token consumption are not measured Caravel results.

    The diagrams and outcomes are explanatory examples, not a forecast of productivity or guaranteed identical model output.