Show the source.
Proposed answers should identify where information came from, how fresh it is, and what is missing. Confidence should be explained, not implied.
The AI approach
A second perspective. Your final decision.
AI should help you see the options more clearly. We are designing Vortiek to organize, explain, and propose, with you in control of what happens next.
Vortiek / In development
Illustrative conversation / Not a live assistant
“My inbound flight is delayed. What should I check about my connection?”
Start with the information behind the suggestion.
A planned assistant would bring relevant flight updates together, identify their sources and observation times, and explain what is still unknown. It would distinguish a possible next step from confirmed availability.
Keep the decision with the traveler.
A proposal to change a trip should explain the action and its consequences, then wait for your explicit approval. No booking or account-change functionality is offered today.
Keep permissions narrow.
Future tools should receive only the information and access needed for a specific user-approved task. Data access, retention, and deletion controls are launch requirements.
Ask before acting.
The design requires explicit confirmation before bookings, payments, filings, account changes, or other binding actions. A suggestion is not an authorization.
Make limitations visible.
AI can be incomplete or wrong. Airlines and other providers control travel outcomes. Consequential decisions should be checked with the relevant provider.
Confidence method
Confidence is a disclosure system, not a promise.
The prelaunch method uses four qualitative factors. It does not publish a production formula or prediction-accuracy claim. The purpose is to show why evidence is strong, limited, conflicting, or insufficient.
Source identity
A traveler-provided record, an official provider source, and a secondary source do not carry the same authority. The interface should name the source class, not hide it behind a score.
Freshness
Each observation needs a time and an expected refresh cadence. A stale result is visibly downgraded or withheld, even when it once came from an authoritative source.
Agreement
Independent observations that agree can strengthen a conclusion. Conflicts must stay visible and prevent a confident single answer.
Scope match
Evidence for the exact flight, route, program, date, cabin, or traveler context is stronger than evidence from a neighboring case. Similar is not the same.
Worked example
A fresh signal can still lead to a limited conclusion.
This example explains the intended reasoning pattern. It is not generated from a live trip, connected airline feed, or released Vortiek model.
Question
“My inbound aircraft is late. Will I miss my connection?”
Evidence available
- An official schedule update observed eight minutes ago.
- The inbound aircraft is shown behind schedule.
- The published itinerary still shows the original connection.
Material unknowns
- The final arrival and departure gates.
- Taxi time and operational recovery.
- The airline's current reaccommodation options.
Explained result
Limited confidence that the trip needs attention. Insufficient evidence to say the connection will be missed or to promise a specific remedy. Confirm the latest details and available options with the airline.
Hard stops
Some uncertainty should stop the answer.
These conditions prevent a clean-looking result from outrunning its evidence.
Critical source missing
Return “insufficient evidence” instead of manufacturing a score.
Freshness boundary exceeded
Cap or withhold the conclusion and show the last observation time.
Sources conflict
Present the conflict and the next verification step. Do not average disagreement into false certainty.
Consequential action proposed
Explain the action and its effects, then wait for explicit human approval.
Authority and recourse
The airline and program remain authoritative.
Travel conditions, availability, and rights can change. A Vortiek explanation should link back to the relevant provider and make the next verification step clear. U.S. travelers can also consult the Department of Transportation's aviation consumer resources.
The principles come first.
The evidence must follow.
Vortiek is prelaunch. Models and providers are not final. Production launch requires documented data flows, evaluations, permissions, human review, monitoring, and incident processes. These are design principles, not a claim of certified production capability.
Follow the journey
Travel intelligence worth understanding.
Vortiek is in development. Be part of the conversation as we work toward launch.