Editorial and Source Policy

Source priority

1. Current regulator, government, airport, airline, or manufacturer material for facts they control.
2. Primary research, standards, filings, and technical documents for measured or historical claims.
3. High-quality independent reporting when primary evidence does not answer the editorial question.
4. Reader reports as leads for verification, never as automatic proof.

A low-quality aggregation page does not become evidence because it ranks well. Competitor pages can reveal a reader question or coverage gap, but they are not copied and do not substitute for primary research.

Volatile facts

Airline rules, baggage allowances, airport processes, schedules, routes, prices, passenger rights, visas, health rules, and safety notices can change quickly. A page that mentions them must state its research date, jurisdiction, source, and update trigger. Readers are told where a live check remains necessary.

Iliamna does not claim real-time access unless the page actually uses a documented live source. A static calculator cannot quote availability. A planning framework cannot guarantee a connection. An example fare is not a current market price.

Claim ledgers and exact-body review

Publishable pages have a source packet and claim ledger. Material claims are connected to supporting evidence, with jurisdiction and volatility recorded. The reviewed body receives a SHA-256 hash. A substantive change invalidates that review and must be checked again.

Article origin and editorial lineage

Every public article or guide intended to rank in search must originate in a retained UnSpar article workflow. The exact starting artifact, source transport, project and article identifiers, workflow settings, credit record, intermediate artifacts, reports, and hashes remain part of the editorial record.

After that origin exists, the desk can fact-check, correct, expand, restructure, humanize, format, illustrate, and add tools. Existing Codex-originated ranking articles are provisional. They stay at their current URLs and are replaced or expanded in place only after a reviewed UnSpar-origin artifact exists for that page.

Depth follows the reader's task

Iliamna does not impose one word count on every subject. A narrow question can be complete at about 1,000 words, while a broad decision may require 10,000 or more. The editorial brief records why the depth is sufficient for the search intent, available evidence, topic complexity, and the reader's complete decision or action.

Editorial prose is measured separately from navigation, forms, tool labels, source panels, and related cards. Short work is not preferred just because it is faster to produce.

Tools and calculations

Interactive tools expose their inputs, assumptions, arithmetic, and limitations. They do not pretend to book, predict a live queue, access a private fare, decide a legal right, or know the user’s complete situation. Important results remain readable with assistive technology and printable without creating an account.

Experience and testing

We never invent a trip, cabin review, airport visit, product test, quote, endorsement, or personal story. If the desk has not performed a test, the page does not use language that implies it has. Source-led analysis is labeled as such.

Artificial intelligence and generated imagery

Automated systems may assist with research organization, the required UnSpar-origin workflow, post-origin editing, coding, and original editorial imagery. They do not own the editorial decision. Claims are checked against retained sources, outputs are independently reviewed, and generated images are inspected for physical plausibility, false logos, geographic implications, text errors, bias, and deceptive documentary effect.

Generated imagery supports a visual idea. It is not evidence that a particular aircraft, airport, route, passenger, or event existed. Maps, safety diagrams, tickets, official documents, and cockpit controls require a higher factual and misuse review.

Commercial separation

Iliamna has no active affiliate or booking relationship at launch. If that changes, the relationship and page-level links will be labeled. Payment cannot buy a favorable conclusion, hide a material drawback, or change the correction standard.

Corrections

Factual corrections are made promptly and material changes are explained on the page or in the public corrections record. Quietly changing a material claim without updating its review state is not acceptable.