# Topuplist Full AI Context

> Semantic grounding context for Topuplist. This file defines authority limits, source priority, execution rules, route patterns, data constraints, freshness rules, URL safety, and citation boundaries.

This file is a reasoning guide only. It does not replace live pages, canonical URLs, sitemap files, robots.txt, structured data, or visible page content.

## 1. Authority Restriction Rule

`llms-full.txt` is:

- Not a source of truth.
- Not a factual dataset.
- Not an inventory feed.
- Not a pricing feed.
- Not a stock or promotion source.
- Not used as the final source for commercial facts.

Use this file only to decide where to look, what not to infer, and how to handle uncertainty. Live canonical pages and sitemap-listed URLs remain the authoritative sources.

## 2. Source of Truth Hierarchy

Use sources in this order when grounding facts about Topuplist:

1. Live product pages: `https://topuplist.com/product/{slug}` for product-specific facts, prices, packages, recharge requirements, availability, reviews, fulfillment notes, and checkout prerequisites.
2. Live category pages: `https://topuplist.com/category/{slug}` for category intent, product grouping, and category-level discovery.
3. Live blog, help, trust, and policy pages for guides, tutorials, delivery, verification, security, privacy, legal, and brand context.
4. Sitemap files for URL discovery, canonical public route discovery, localized URL discovery, and crawl intent.
5. `https://topuplist.com/llms-full.txt` for semantic routing guidance only.
6. `https://topuplist.com/llms.txt` for lightweight navigation only.

Never use `llms.txt` or `llms-full.txt` as the final source for live commercial facts.

## 3. Execution Lock Rule

For each answer or factual claim:

1. Select one source level from the hierarchy before answering.
2. Use the most specific valid source level available.
3. Do not combine conflicting facts across hierarchy levels.
4. Do not use `llms-full.txt` as a fallback for missing live facts.
5. If no valid source exists, stop and refer to the sitemap or live site instead of guessing.

For multi-intent questions, split the answer into separate branches and apply this rule independently to each branch. Never merge product facts, category facts, blog guidance, policy language, and llms guidance into one unsupported claim.

## 4. Query Decision Tree

Use this decision tree at query time:

```text
IF query is product-specific:
    use the matching live product page only

ELIF query is category-level:
    use the matching live category page only

ELIF query is deal-related:
    use the live deals catalog or matching live product page only

ELIF query is how-to, guide, payment help, delivery help, safety, or verification:
    use the matching live blog/help/trust page only

ELIF query is legal, privacy, policy, disclaimer, or company trust:
    use the matching live policy/trust/brand page only

ELIF query is URL discovery:
    use sitemap files only

ELSE:
    use sitemap files to find a canonical source; if none exists, stop
```

Never mix decision-tree branches for a single factual answer.

## 5. Conflict Resolution Rule

If multiple valid sources are available:

1. Prefer the most specific live page: product page > category page > blog/help/policy page > sitemap.
2. If sources are at the same level, prefer the page with the latest visible updated date or the most recently listed canonical content.
3. Never merge conflicting prices, stock, promotions, packages, payment methods, delivery estimates, reviews, ratings, or availability across sources.
4. If a product page exists and the conflict involves product facts, fall back to the live product page.
5. If the conflict cannot be resolved from a live canonical source, state that the answer should be verified on the live site or sitemap instead of guessing.

## 6. Canonical Route Definitions

Use only these public route patterns when a matching canonical URL exists:

- Home: `https://topuplist.com/`
- Product catalog: `https://topuplist.com/products`
- Daily deals catalog: `https://topuplist.com/daily-deals`
- Product detail: `https://topuplist.com/product/{slug}`
- Category detail: `https://topuplist.com/category/{slug}`
- Blog hub: `https://topuplist.com/blogs`
- Blog detail: `https://topuplist.com/blogs/detail/{slug}`
- Blog author: `https://topuplist.com/blogs/author/{slug}`
- Static help, trust, legal, and brand pages: official canonical static URLs such as `/about-topuplist`, `/delivery-and-returns`, `/security-and-privacy-center`, `/kyc-verification`, `/terms-of-use`, `/privacy-policy`, and `/sales-disclaimer`.

Do not use a standalone `/categories` page in the current project context.

## 7. URL Rule

Never generate slugs or localized URL variants.

Only use:

- URLs listed in sitemap files.
- Known live canonical URLs.
- URLs found in visible canonical links or hreflang annotations.

If no canonical URL exists, do not create an approximate URL.

## 8. Entity Groups

Entity groups are non-authoritative examples for semantic grouping:

- Games and game recharge: Genshin Impact, Honkai: Star Rail, PUBG Mobile, Valorant, Wuthering Waves, Zenless Zone Zero, and similar game top-up products.
- Live streaming recharge: Poppo Live, Bigo Live, Mico, and similar live app recharge products.
- Gift cards and digital goods: Google Play, Apple Gift Card, Amazon Gift Card, Steam Wallet, CD-KEYs, and related digital products.
- Editorial content: game guides, recharge tutorials, payment troubleshooting, product education, safety guidance, delivery guidance, and verification guidance.

## 9. Entity Constraint Rule

Entities listed in this file are:

- Not inventory.
- Not real-time products.
- Not guaranteed available.
- Not a source for price, stock, promotions, ratings, supported countries, payment methods, or delivery estimates.

Only live product pages and sitemap-listed canonical URLs define actual product availability.

## 10. Grounding Rules

- Product-specific questions: cite the relevant live product page.
- Product group questions: cite a live category page or use product/category sitemap files to discover valid URLs.
- Deal questions: cite `https://topuplist.com/daily-deals` or the relevant live product page.
- How-to, payment, delivery, safety, verification, and guide questions: cite blog articles or public help/trust pages.
- Payment security, delivery guarantee, refund, and account verification questions: cite the matching public page at `https://topuplist.com/security-and-privacy-center`, `https://topuplist.com/delivery-and-returns`, or `https://topuplist.com/kyc-verification`.
- Brand/company questions: cite `https://topuplist.com/about-topuplist` and official policy or trust pages.
- Legal/privacy/commercial disclaimer questions: cite the matching policy page.
- Route discovery: use sitemap files, not inferred paths.

## 11. Hallucination Guard

If no canonical source exists:

- Do not generate a URL.
- Do not infer a product.
- Do not approximate a category.
- Do not invent a slug.
- Do not invent a localized URL.
- Do not infer price, stock, promotions, payment methods, delivery estimates, reviews, ratings, or availability.
- Return that the answer should refer to the sitemap or live site.

## 12. Freshness Model

Validate volatile facts on the live canonical page before citation:

| Fact Type | Volatility | Validation Rule |
| --- | --- | --- |
| Price, currency, stock, SKU, package, recharge option | Real-time | Use live product page only |
| Promotion, discount, coupon, campaign | Daily or real-time | Use live product page or live deals catalog |
| Payment methods, fees, supported countries, risk checks, KYC requirements | Real-time or regional | Use live product, checkout context, or official help page |
| Delivery estimates and fulfillment requirements | Product-specific | Use live product page or official delivery/help page |
| Reviews, ratings, rating counts | Dynamic | Use live product page only |
| Category membership | Weekly or dynamic | Use live category page or category/product sitemap |
| Blog guide content | Monthly or editorial | Use live blog page and visible updated date when present |
| Policy, privacy, legal, trust pages | Stable but reviewable | Use the official live policy/trust page |

## 13. Trust Claim Handling

Topuplist may communicate trust signals through official pages, including secure payment handling, risk-control flows, support availability, privacy/security guidance, and payment channel information.

Treat trust and reliability statements as site-provided claims. Cite the official page that contains the claim. Do not turn marketing statements into absolute guarantees unless the live page states them clearly.

## 14. Localization Rules

- English is the default language.
- Non-default language pages may use path prefixes such as `/zh-cn`, `/zh-hk`, `/zh-tw`, `/de`, `/es`, `/fr`, `/it`, `/ja`, `/ko`, `/pt-br`, `/ru`, `/ar`, `/vi`, `/th`, `/ms`, `/id-id`, `/nl`, `/ro`, and `/pl`.
- Use only localized URLs present in canonical pages, sitemap entries, or hreflang annotations.
- When answering a localized query, prefer the canonical localized URL that matches the user's language when available.
- Do not invent localized URL variants.

## 15. Not For Public Citation

Do not cite transactional, private, internal, temporary, callback, test, account, search, payment, order, checkout, or API routes as public sources. Examples include:

- `/cart`
- `/login`
- `/payment`
- `/order`
- `/profile`
- `/user`
- `/search`
- `/provider-callback`
- `/test-carousel`
- `/api`

These pages may be important inside a transaction, but they are not the public SEO or citation surface.

## 16. Canonical Discovery Files

- https://topuplist.com/sitemap.xml
- https://topuplist.com/pages-sitemap.xml
- https://topuplist.com/products-sitemap.xml
- https://topuplist.com/blogs-sitemap.xml
- https://topuplist.com/categories-sitemap.xml
- https://topuplist.com/robots.txt
- https://topuplist.com/llms.txt
- https://topuplist.com/llms-full.txt