doc_id: “FLYMAX-06-PRD-README” project_name: “FlyMax V2.0” title: “📝 v3.0 Specifications” doc_type: “PRD” category: “Product Requirements” version: “1.0.0” status: “active” scope: “valid” lifecycle_state: “active” created: “2026-03-09” updated: “2026-03-09” author: name: “George Joseph” role: “Technical Lead / Solution Architect” modified_by:

name: “George Joseph” role: “Technical Lead / Solution Architect” date: “2026-03-09” approved_by:
name: “” role: “” date: “” next_review_date: “2026-03-09”

📝 v3.0 Specifications

Section Purpose: Product Requirements Documents (PRDs) and Product Model definitions for the v3.0 direct-booking platform baseline.

📂 Documents in This Folder

Document	Description	Read Time
📋 Flight_Booking_Platform_PRD_v3.md	Flight Booking Platform PRD v3.0 — Verteil-powered direct booking and servicing platform with full platform ownership of checkout, payment, booking lifecycle, and support	~25 min
🏗️ Product_Model_v3_Flight_Platform.md	Product Model v3.0 — Governing product definition, scope rules, personas, capability domains, and commercial controls	~20 min

📖 Version Overview

v3.0 represents a substantive model shift from the v1.1 redirect-only meta-search baseline.

Key Differences from v1.1

Aspect	v1.1	v3.0
Business Model	Redirect-led, affiliate monetization	Direct booking, transaction-based
Booking Ownership	External (via redirect)	Platform-owned
Payment Processing	N/A	On-platform payment orchestration
Primary Supply	Multiple OTA/NDC routes	Verteil-first with extensibility
Support Model	Limited	Unified support ticketing
Commercial Controls	Ad-hoc	Governed markup, discounts, credits
Portal Scope	Consumer-only	Admin/Agent/Consumer triple-portal
Audience	End consumers	Consumers + Travel Agents (B2C + B2B2C)

🎯 Reading Order

Start with Product_Model_v3_Flight_Platform.md — Understand the governing product definition
Then read Flight_Booking_Platform_PRD_v3.md — Detailed requirements, features, and functional specs
Finally review Product_Scope_Approval_Register_v3.0.md — Commercial scope-freeze and approval tracking

🔑 Governing Statement

PRD v3.0 defines the Flight Booking Platform as a Verteil-powered, direct-booking, flight retail and servicing platform for Consumers, Agents, and Admin/Ops teams, with platform-owned checkout, payment, booking lifecycle continuity, markup/discount/credit governance, SSO and security controls, promotions, support ticketing, reporting, auditability, and flight-platform table-stakes required for market parity; only Multiple Providers and AI capabilities are deferred by default.

📋 Document Details

Flight_Booking_Platform_PRD_v3.md

Type: Product Requirements Document
Status: Draft for Review / Governing Baseline Proposal
Date: 2026-03-09
Owner: Product / Architecture / Program Office
Supersedes: PRD v2.0 (redirect-led baseline), Product Model v2.x references

Contents:

Executive summary and document intent
Product definition and classification
Why v3 exists and what changed
Product principles (10 core principles)
Goals, non-goals, and strategic outcomes
Scope model (current scope, later scope, exclusions)
Personas and stakeholders
Business and commercial model
Supply and platform ownership
28 detailed functional requirements (FR-01 through FR-28)
Business rules and policy requirements
Data model boundaries
Integration requirements
Reporting and KPI model
Non-functional requirements
Risks, assumptions, and constraints
Delivery phasing and release readiness gates
Open decisions requiring formal approval

Product_Model_v3_Flight_Platform.md

Type: Product Model Definition
Status: Proposed Governing Model
Date: 2026-03-09
Owner: Product / Architecture / Program Office
Supersedes: Product Model v2.3 and PRD v2.0 Product Overview baseline

Product_Scope_Approval_Register_v3.0.md

Type: Commercial Scope-Freeze Approval Register
Status: Pending Review/Approval
Date: 2026-03-09
Alignment Basis: Product Model v3.0 and PRD v3.0