Agree the journey before multiplying the pages.
Explore how an approved content contract, parallel design and validation work, and early journey review could reduce rework on a travel website.
Establish the baseline
- Agency brand and approved imagery
- Destinations and sample itineraries
- Enquiry fields and delivery destination
Evidence to retain
- Approved journey and content contract
- Reusable components and validation checks
- Review findings and accepted revisions
Why work this way?
The process, and what it could improve.
Cost
Resolve the journey before multiplying pages.
Review one destination-to-enquiry slice with approved content. Reuse the accepted components and field definitions across the remaining pages.
- What to compare
- Design, model, asset and review costs per accepted journey, including discarded concepts and content corrections.
- The tradeoff
- Reusable components only save work after the underlying journey is agreed. Repeating an assumption multiplies rework.
Resolve the journey before multiplying pages.
Compare the same scope and acceptance criteria. Include setup, coordination, failed attempts and human review alongside the successful model call.
Design the work
One problem. A coordinated agent team.
A model reasons. A harness runs its agent session and tool loop. Orchard coordinates the work, context and handoffs across them.
Orchestration phase 1: Split the work. Preserve the question.
Implementation lead
01Design destination and itinerary pages around the agency’s expertise and visual identity.
Counterproposal agent
02Propose a search/enquiry-led journey and identify where visual storytelling hides the next action.
Independent reviewer
03Test the selected journey on mobile, with keyboard navigation and synthetic enquiry delivery.
Rules · skills · hooks · MCP configuration
Adapted to each harnessSplit the work. Preserve the question.
One objective, distinct responsibilities
Build a travel-agency website by testing an editorial design against a task-focused enquiry journey.
editorial prototype + content modelalternative journey + usability tasksPlaywright results + accessibility findingsModel families and pairings are illustrative. Assignments here are manual examples, not measured model comparisons or automatic cost optimization.
Inspect the example work orderJSON
An illustrative work-order format for this scenario. Changing an example session updates this document; no agents run from this page.
{
"example": "travel-agency-website",
"objective": "Build a travel-agency website by testing an editorial design against a task-focused enquiry journey.",
"boundary": "Approved destination content and enquiry scope. No invented inventory, prices, or live booking claims.",
"sessions": [
{
"role": "proposer",
"model_family": "Claude",
"harness": "Claude Code",
"task": "Design destination and itinerary pages around the agency’s expertise and visual identity.",
"expected_artifact": "editorial prototype + content model"
},
{
"role": "challenger",
"model_family": "GPT",
"harness": "Codex CLI",
"task": "Propose a search/enquiry-led journey and identify where visual storytelling hides the next action.",
"expected_artifact": "alternative journey + usability tasks"
},
{
"role": "reviewer",
"model_family": "Gemini",
"harness": "Gemini CLI",
"task": "Test the selected journey on mobile, with keyboard navigation and synthetic enquiry delivery.",
"expected_artifact": "Playwright results + accessibility findings"
}
],
"project_contract": [
"Rules",
"Skills",
"Hooks",
"Tool configuration"
],
"shared_context": [
"Brand and content",
"Design decisions"
],
"evidence_required": [
{
"label": "The next step is clear",
"evidence": "Complete a destination-to-enquiry task on each proposed layout."
},
{
"label": "The interface is usable",
"evidence": "Check keyboard access, mobile overflow, labels and error states."
},
{
"label": "The enquiry arrives correctly",
"evidence": "Send a synthetic enquiry through the approved sandbox routing and inspect the record."
}
],
"release_owner_gate": "The agency owner accepts the content, journey and enquiry destination before the tested build is published."
}Chapter 1: Find the agency’s point of view.
Chapter 01 / 04
Find the agency’s point of view.
Turn its audience, specialties, destinations, and imagery into a content plan. Explain why someone should plan a trip with this team.
Research and design agents + agency owner
Brand and journey brief
Audience → destinations → itinerary → enquiryThe process principle
Reuse accepted decisions, not untested assumptions.
Scope of this exampleThis is an enquiry-site concept. Live availability, prices, payments, and bookings require approved providers and separate integrations.
A fictional agency concept. No live trips, prices, availability, or bookings are offered in this preview. Accessible forms guidance






