Tamaga protocol

Follow one travel question from evidence to action.

Consider a fictional cultural route. Its page advertises guided visits from May to October. The site operator’s current timetable covers May to September. A visitor asks about October, while the local partner is still checking whether a visit can be arranged.

The public description, published schedule and individual enquiry each carry part of the answer. Someone needs to connect them before the organization can give a reliable response.

The Tamaga Protocol provides seven steps for working through that connection: establish the question, examine its sources, identify who can decide, and carry the resulting answer into the places where people use it.

Seven steps

  1. Step 1: Define the question and the useful outcome

    Start with a decision somebody needs to make. Identify the person asking, the relevant circumstances and what would help them proceed.

    For the cultural route, the question is: Can we confirm this guided visit in October? The visitor needs to know whether to plan around it. The organizer needs to establish what is possible before making a commitment.

    Keep the scope close to that decision. A short scope note can identify the visit, dates, relevant pages and people involved. Expand the investigation when another dependency becomes material.

  2. Step 2: Identify what the answer depends on

    List the places, services, people and records needed to answer the question. Explain their relationships in ordinary language before deciding how software should represent them.

    In this example, the route includes a cultural site. The site operator maintains its visiting timetable. A local partner coordinates a guide. The organizer receives the visitor’s enquiry and communicates the outcome.

    Keep these distinctions clear: a page describes the visit, a timetable establishes scheduled visiting periods, and an enquiry records what somebody has requested. Updating one does not automatically resolve the others.

  3. Step 3: Establish what each source supports

    Identify the material behind each consequential statement. Record who maintains it, when it applies and what remains unresolved.

    The current timetable supports scheduled guided visits from May to September. It does not settle whether a separate October visit can be arranged. The existing May–October page needs attention, while the October enquiry still requires an answer from the relevant people.

    Use Source Confidence when sources differ or their meaning is uncertain. Retain the source version and the reason for your interpretation. Keep restricted information and media within their permitted uses.

  4. Step 4: Name who can establish or change the answer

    Separate maintaining the explanation from making the underlying decision.

    In this fictional arrangement, the site operator can confirm opening and visiting conditions. The local partner can establish guide availability. The organizer can confirm the visit once those dependencies are resolved.

    One editor can maintain the public information and the investigation record. Decisions belonging to an operator or partner still need their involvement.

    For the October enquiry, record what has been requested, what remains outstanding and who will respond. Receipt of the enquiry should remain distinct from confirmation of the visit.

  5. Step 5: Follow the answer into its uses

    Examine the relevant pages, translations, partner descriptions, messages and other accessible versions. Compare the meaning they convey, including their dates and conditions.

    For the route page, supported wording could explain:

    Scheduled guided visits run from May to September. For an October visit, ask the organizer to check the arrangements before making plans.

    Then follow the visitor’s path. A route introduction can lead to current visiting information. That explanation should make the scheduled period clear and provide an appropriate enquiry route for other dates.

    A newsletter or video can introduce the same journey differently while retaining the condition that matters and linking to the maintained explanation.

    A small comparison table is often enough to record the versions reviewed, the differences found and any material you could not inspect.

  6. Step 6: Decide how changes will reach the right places

    Identify who maintains the source, who updates its public uses and what should trigger another review.

    For the cultural route, a revised timetable should prompt a check of the route page, translations and relevant partner material. The October enquiry also needs its own follow-up when the operator and guide arrangements are known.

    Use Claim Ledgers to keep supported wording connected with its evidence, uses and correction history. Record outstanding changes, including updates requested from a partner.

    Keep the record in a form you can maintain. A single editor can carry several responsibilities while recording the actions that belong elsewhere.

  7. Step 7: Make the changes and check the complete path

    Prioritize changes by their consequence for the visitor and the work they depend on. Correct supported wording promptly; keep unresolved arrangements visible.

    For the October enquiry, check that:

    • The route page explains the scheduled visiting period.
    • Its translations and reviewed summaries preserve that meaning.
    • The enquiry reaches the person handling the arrangements.
    • The visitor receives a clear outcome when the necessary decisions have been made.

    Revising the page does not confirm the visit. Equally, confirming one October visit does not establish a regular October schedule.

    Use the findings to decide what implementation is needed. A content correction may be sufficient. Repeated problems may justify a reusable record, clearer relationships or a maintained workflow. Choose the structure after establishing the need.

Keep a usable record of what you decided

The result should let you recover the question, supporting material, responsibilities, affected uses and outstanding actions without repeating the investigation.

For a narrow question, this can fit in one small document. Revisit it when a source changes, a decision is resolved or the same uncertainty appears again.

The travel knowledge infrastructure explanation develops the broader argument. The glossary definition provides a concise reference.

An open ivory dossier connects an entrance photograph, an independent comparison leaf, and a physical plan retaining the same entrance steps.
Conceptual illustration: retain the source evidence, comparison and implementation decisions together. The dossier supports the method; it does not itself establish approval or complete an operational action.
AI-generated illustration · Tamaga

Bring one question and show where the answer lives

Share a representative page, the question it needs to answer and the sources or practical knowledge available. We can work through the dependencies and identify a useful first change.

Discuss your travel knowledge question

For a hotel-specific examination of one public promise, the Seven-Version Snapshot offers a separate, scoped diagnostic.