Xai source index
This source index documents the public materials behind Night Ash Run's XAI_GAMES positioning. It maps the Xai GitBook crawl, Proof-of-Skill PDF, Ex Populus context, and citation boundaries into a machine-readable evidence layer.
A public map of what has been fetched, audited, counted, and bounded. This keeps the site credible: source-backed pages are separated from discovered-but-not-yet-cited frontier depth.
Evidence frontier
The index starts with Xai GitBook, follows public outgoing links, samples recursive document layers, closes the stable third- and fourth-level frontiers, starts the fifth-level shard audit, and marks sixth-level discovery as boundary-only.
Third-level document candidates are closed, and the stable fourth-level document frontier is complete. The first eighteen fifth-level source shards are complete, while counted sixth-level links remain discovery evidence.
This ledger explains how recursive public-source review becomes site canon. It is not a claim that every counted URL is cited; it is a production map for turning source depth into technical docs, history memory, game systems, and publication boundaries.
Xai GitBook Markdown, Proof-of-Skill, Ex Populus context, Xai Games, and Web Game Game owned files are treated as the durable public source base.
Read readinessOrbit, Nitro, AnyTrust, Connect, Gas Subsidy, developer tooling, and Proof-of-Skill vocabulary are converted into the Technology Dossier, Developer Playbook, and Technical Production Bible.
Open bibleProtocol, Sentry, builder, identity, action, reward, game, and evidence layers become the Chronicle Atlas, Canon Continuity Deck, Historical Ledger, and Source-to-Canon Ledger.
Open continuityWallet entry becomes driver identity; sponsored actions become silent crew service; record language becomes owned garage memory; reward thesis becomes route reputation.
Open systemsllms.txt, facts files, evidence JSON, knowledge graph JSON, source-audit JSON, and Markdown mirrors expose the source-backed route map for search systems and LLM retrievers.
Open LLM contextRecursive discovery strengthens understanding, but public claims still require durable public routes. Counted frontier links, private notes, temporary pages, or unofficial material do not become citation proof.
Open boundaryThis board defines which source families can directly support public claims and which inputs remain internal orientation. It keeps Night Ash Run's technical documentation, Xai history, and LLM retrieval layer grounded without exposing context-only learning as a public dependency.
Primary public documentation for protocol, builder, identity, gas, Sentry, game catalog, and ecosystem vocabulary. It supports technical and historical claims only when routed to durable public pages.
Open sourcePrimary public source for player identity, achievements, leaderboards, contracts, wallets, and XAI reward thesis language. It does not support payout guarantees or universal eligibility claims.
Open PDFPublic ecosystem and studio context for Xai Network and game-oriented infrastructure language. It supports ecosystem framing without implying partnership, investment, or live integration.
Open sourceCommunity-oriented discovery can reveal topics, questions, vocabulary, and comparison angles. It is not exposed as a citation dependency and cannot prove technical, financing, partnership, live-integration, or payout claims.
Open distillationA source moves from orientation to citation only when it is public, durable, reachable without private session state, directly relevant, classified, and safe under the claim-boundary rules.
Open audit JSONApp-gated, private, temporary, social, or unofficial material can guide learning but cannot prove technical claims, funding claims, partnerships, live integrations, or payout availability.
Open boundaryThis firewall explains how learning becomes original site canon. It keeps the public website grounded in durable sources while preventing context-only material, unstable pages, or unsupported claims from becoming visible citation dependencies.
Protocol, identity, gas, developer tooling, reward, and ecosystem claims must route to public source pages, Web Game Game-owned dossiers, evidence JSON, or source-audit records.
Read readinessUseful context can guide structure and vocabulary, but it is not named as a public dependency and does not support protocol, live-integration, financing, or reward claims.
Open boundaryAccepted material is rewritten into Web Game Game language: Night Ash Run systems, source-bound Xai primitives, production history, and technical verification routes.
Open verificationCompany names, financing language, live deployment status, partnership language, reward availability, and investment-style wording remain blocked unless a direct public source proves them.
Open claim matrixfacts files, llms.txt, evidence JSON, knowledge graph JSON, sitemap routes, and Markdown mirrors publish only approved source routes and site-owned wording.
Open LLM contextA source moves from orientation to citation only after it is public, durable, directly relevant, classified, and linked to a specific claim route in the site canon.
Open audit JSONThis distillation gate explains how broad research becomes original Night Ash Run canon. Context can shape priorities, but public pages only publish Web Game Game language, durable source routes, and explicit claim boundaries.
Context-only material can reveal topics worth studying, such as onboarding, reward loops, game catalogs, campaign operations, and ecosystem vocabulary. It does not become a public citation.
Read readinessPlatform names, post identifiers, community phrasing, temporary pages, and promotional fragments are removed before any idea enters the public production route.
Open boundaryUseful signals are reduced to neutral lanes: identity, sponsored action, owned memory, reward thesis, game ecosystem, operations review, and evidence policy.
Open ladderAccepted lanes are rewritten as Night Ash Run scenes, cast roles, route mechanics, garage memory, redline reputation, and technical acceptance gates.
Open systemsAny public technical claim routes back to durable sources such as Xai GitBook, Proof-of-Skill, Ex Populus context, source-audit records, or Web Game Game owned files.
Open citation packOnly approved, rewritten claims enter facts files, llms.txt, evidence JSON, knowledge graph JSON, docs, media routes, and Markdown mirrors.
Open LLM contextThis roadmap explains how unfinished recursive discoveries move through review before they influence public pages. It keeps Night Ash Run useful for search systems and LLM retrievers without letting raw link depth become unsourced claims.
Counted fifth-level links and sixth-level discovery links stay in a review queue until a page is fetched, reachable, classified, and tied to a clear source role.
Open frontierRPC, bridges, wallets, marketplaces, explorers, verifiable randomness, developer SDKs, reward logic, and identity flows receive priority because they can improve the technical spine of the game.
Open matrixEach accepted page is marked as protocol proof, developer context, ecosystem context, retrieval support, or boundary-only material before any public copy or machine-readable file references it.
Read readinessA discovery becomes citation-ready only when it is public, source-owned, stable enough to revisit, directly relevant to a claim, and free from fragile promotional language.
Open audit JSONDuplicate URLs, static assets, temporary pages, private notes, unsupported investor claims, finance hype, and social noise stay out of public evidence even when they helped orient the review.
Open boundaryAccepted material feeds the Technology Dossier, Developer Playbook, History Ledger, Technical Whitepaper, facts files, llms.txt, evidence JSON, and knowledge graph as original site language.
Open docs hubThis doctrine explains why the recursive audit cuts over after sixth-level discovery. The next phase is not more raw depth; it is high-signal classification, technical synthesis, and controlled publication into Web Game Game-owned canon.
After the completed fourth-level frontier and eighteen fifth-level source shards, sixth-level counts show the ecosystem graph is large enough that raw expansion adds noise faster than proof.
Open fifth frontierThe source batches exist to map coverage, remove overlap, classify source roles, and surface high-signal technical material. They are an audit method, not a claim that every counted link supports the public site.
Open answerWhen downstream links become mostly duplicates, social surfaces, temporary pages, static assets, repeated docs, or generic web edges, the audit shifts from collection to source scoring.
Read readinessIdentity, sponsored actions, RPC, bridges, marketplaces, explorers, verifiable randomness, SDKs, reward operations, and source-owned technical docs get priority over broad link volume.
Open matrixAccepted material is rewritten into Night Ash Run production language: technical routes, development history, game-system contracts, reward boundaries, and retrieval files.
Open docs hubUnclassified sixth-level links, private or temporary pages, unsupported finance language, social chatter, and unstable promotional claims stay outside public citation rails.
Open firewallThe cutover feeds the whitepaper, technology dossier, history archive, developer playbook, facts files, llms.txt, evidence JSON, and knowledge graph without exposing internal learning debris.
Open LLM contextThis ledger tells readers, crawlers, and language models how to treat the source index. It separates verified citation material from ecosystem context, recursive discovery depth, and materials that are not suitable for public claims.
A direct citation map for the Night Ash Run Technical Whitepaper. Each row tells readers and language models which durable public route supports a whitepaper claim.
Use Xai Protocol and Xai Basic Concepts for Arbitrum Orbit, Nitro, AnyTrust, DAC, and gaming-oriented network vocabulary.
Open sourceUse Xai Connect overview for email-linked wallet identity, unified ecosystem entry, and wallet-abstraction language.
Open sourceUse Xai Gas Subsidy for EIP-712 typed messages, ERC-2771 meta-transactions, trusted forwarder logic, and relayer patterns.
Open sourceUse Xai Developer Tools and Marketplace Tools for RPC, explorer, bridge, marketplace, and item-commerce surfaces.
Open sourceUse the public PDF for SteamID login, automatic wallet creation, achievements, leaderboards, contracts, and XAI rewards.
Open PDFUse Xai initiative material and Raijin Terms for campaign review, rankings, eligibility boundaries, reward availability, and platform-boundary language.
Open sourceUse Xai Games Catalog, xai.games public game surface, and Ex Populus Xai Network context for game ecosystem memory and history framing.
Open sourceUse source-audit.json and the Recursive Evidence Map for crawl coverage, frontier depth, counted links, and future-review boundaries.
Open JSONUse the Whitepaper Canon Bridge for the route connecting the source-bound technical thesis to the Technology Dossier, Xai History & Technical Canon, and publication boundaries.
Open bridgeUse the Citation Boundary for claim discipline. Only durable public sources support protocol, live-integration, or investment statements.
Open boundaryA compact evidence map for the newest game-facing routes. It explains what source material supports each route and where the boundary remains.
Use the Proof-of-Skill PDF for SteamID login, wallet creation, achievements, leaderboards, contracts, and XAI reward vocabulary. The site route is a reward thesis, not a live payout claim.
Open routeUse Web Game Game owned pages plus Xai identity, sponsored-action, record, and reward sources to read the slice as player-facing production context. The route is a production slice map, not a public demo or live payout claim.
Open sliceUse Xai initiative material, Raijin Terms, and Proof-of-Skill source language for campaign review, rankings, eligibility boundaries, and player-facing achievement systems. The route is an operations model, not a payout guarantee.
Open routeUse Xai protocol, Sentry, developer tooling, Xai Connect, Gas Subsidy, and Proof-of-Skill sources for the blackbox signal chain. The route is game-facing translation, not a live integration claim.
Open routeUse Xai protocol, Xai Connect, Gas Subsidy, Proof-of-Skill, Xai Games Catalog, Ex Populus context, and recursive evidence routes to support the AAA surface as a source-backed production spine.
Open routeUse official Xai, Ex Populus, Proof-of-Skill, and Web Game Game source routes as the claim boundary. This route rejects invented investor names, fragile hype claims, and unsupported financing language.
Open routeUse Web Game Game whitepaper, technology, history, and citation-boundary routes to connect the technical thesis to public canon. The bridge is a document route, not a stronger live-integration or partnership claim.
Open bridgeUse the History page, History Runtime Map JSON, Runtime Blueprint JSON, Developer Playbook, facts files, llms.txt, evidence JSON, and knowledge graph as the route from Xai historical lanes to one inspectable mission object. Boundary: design packet and publication evidence, not live demo, deployed contract, live reward, or partner integration proof.
Open packetUse Recursive Evidence Map, Frontier Cutover Doctrine, Source Synthesis Firewall, Context-to-Canon Distillation, the docs batch-purpose answer, history ledger, and evidence JSON. Boundary: raw frontier volume is not proof; only classified sources with role, route, and boundary can support public claims.
Open consoleUse the Media Kit for the official route map across Publisher Review Stage, AAA Production Board, Runtime Blackbox, Setpiece Gameplay Deck, Production Evidence Route, Setpiece Trace Contract, Skill Signal Packet, Mission Memory Packet, AAA Production Control, game systems, Cast System Contract, reward console, archive blackbox, Source-to-System Deck, live ops, developer playbook, Integration Handoff Packet, History-to-Build Gate, Release Evidence Packet, Source Synthesis Firewall, Context-to-Canon Distillation, history atlas, citation boundary, and machine canon.
Open deckUse this route to separate durable public proof, context-only orientation, original Web Game Game synthesis, claim quarantine, machine-output filtering, and promotion rules.
Open firewallUse this route when context-only learning needs to become stripped, normalized, original, proof-checked Night Ash Run language before any machine-readable publication.
Open distillationUse the registry for claim-boundary handling. Temporary, private, or unofficial material is not primary protocol proof, live integration proof, or investment proof.
Open boundaryThe fifth-level pass begins from the completed fourth-level source frontier. The first eighteen source shards are audited completely, and counted sixth-level links remain discovery evidence.
This completes the first eighteen fifth-level source shards; it is not complete fifth-level coverage across every available fourth-level source page. Counted sixth-level links remain discovery evidence until individually fetched and classified. The eighteenth shard is lower reachability, so it is treated as frontier shape rather than citation proof.
Deep source recursion improves the production map while preserving the rule that unreachable, temporary, private, or unclassified links are not public proof.
The recursive crawl uses strict counting language so large discovery numbers do not become accidental citation claims. These definitions explain how to read the fifth-level and sixth-level figures.
Audit records are fetched or classified entries across completed fifth-level shard files. They may include overlap before URL-level dedupe.
Unique audited URLs are fifth-level document candidates after overlap removal across the first eighteen completed source shards.
Reachable samples are unique audited fifth-level URLs that returned usable reachable content during the audit pass.
Sixth-level links counted from unique reachable fifth-level URLs show frontier scale. They are discovery evidence until individually fetched, classified, and tied to a public claim route.
The record-level count is the sixth-link total before reachable-URL dedupe across audit records. It is useful for audit load shape, not for public citation volume.
The site cites durable public sources and Web Game Game-owned documents. Raw frontier volume informs synthesis, but it never proves financing, investor names, live integrations, payout availability, or partner status.
The GitBook audit used Xai's public site index and Markdown endpoints so the website can cite source-backed technical and historical material instead of generic Web3 language.
The second audit pass sampled the outgoing links discovered inside Xai GitBook. It does not treat social, temporary, private, or unofficial material as technical proof; it separates them from developer documentation, explorers, bridges, marketplace tooling, and protocol sources.
The third audit pass followed the first external sample into document-like second-level URLs. It records deeper technical context while keeping a strict boundary: counted third-level links are discovery evidence, not individually verified citations until fetched.
The recursive pass skipped non-document resources before citation review: 1832 static-extension URLs, 867 static-host URLs, and 43 Cloudflare asset URLs. This keeps the public source index focused on documents, explorers, code releases, bridges, marketplaces, RPC material, and protocol pages.
Reachable recursive samples include developer documentation, bridge docs, randomness pages, marketplace docs, explorers, code releases, campaign/DeFi pages, social/community surfaces, RPC pages, downloads, PDFs, and general web pages. Developer documentation alone accounts for 591 audited URLs with 589 reachable samples.
Recursive sources expand thirdweb context from gas sponsorship into Bridge, ecosystem wallets, external wallets, wallet security, server wallets, TypeScript, .NET, Unity, Unreal Engine, Solidity tokens, API reference, and llms-full material.
Open sourceDeeper Arbitrum sources add bridge quickstart material, gas and fee references, chain information, Nitro internals, node policy pages, glossary material, and DAO/governance context that help explain Xai's Orbit/Nitro foundation.
Open sourceSequence recursive sources include marketplace guides, SDK overview, API references, embedded wallet context, docs sitemap, and llms.txt material that strengthen the game-commerce and wallet-abstraction layer.
Open sourceRelay sources add API overview, quickstart, gas top-up, deposit address, and llms.txt context for cross-chain movement and player-facing bridge/refuel style flows.
Open sourceExplorer samples include Arbiscan blocks, verified contracts, accounts, batches, charts, contract-license pages, directory pages, and contact surfaces, plus Xai and Arbitrum explorer references from the earlier layer.
Open sourceRecursive sources preserve Xai governance surfaces and Supra VRF-related pages, including randomisation, automation, and verifiable system material that supports game reward and outcome design.
Open sourceThe next frontier audit revisited reachable second-level source pages, extracted a stable third-level document frontier, and audited every URL in that stable frontier. This closes the third-level document index and moves the recursive frontier to fourth-level discovery.
The completed stable third-level frontier includes 2004 reachable developer-doc samples, 2017 code-release samples, 307 explorer samples, 130 bridge samples, 101 randomness samples, 170 marketplace samples, 53 campaign/DeFi samples, 123 PDF samples, 15 RPC samples, and 6790 general web samples.
High-value third-level sources expand thirdweb SDK and wallet surfaces, Arbitrum Nitro and chain-operation pages, Sequence marketplace and wallet docs, Relay settlement/API docs, Arbiscan explorer tools, Supra automation/VRF pages, and Ankr bridge/RPC/API documentation.
The fourth-level pass continues from the completed third-level document frontier. Four source shards revisited all available third-level source pages, extracted fourth-level document candidates, and provide audit coverage for every unique document-like fourth-level candidate.
The fourth-level index covers source offsets 0, 3000, 6000, and 9000-end from the third-level source list. Every unique document-like fourth-level candidate across the four source shard indexes has audit coverage. The follow-on frontier is fifth-level link review.
High-value fourth-level samples include thirdweb docs and SDK surfaces, GitHub code-release surfaces, Arbitrum/Arbiscan explorer and protocol pages, bridge pages, randomness pages, and marketplace documentation.
These clusters are the public source groups used to strengthen the Night Ash Run technology dossier, history page, and LLM context.
Xai Basic Concepts and protocol pages describe Xai as an Arbitrum Orbit chain using AnyTrust technology, supported by Offchain Labs, with Data Availability Committee concepts and gaming-oriented design.
Open sourceXai Connect pages describe email-linked ecosystem wallets and unified identity. The FAQ and blockchain-gaming pages reinforce the goal of hiding wallet friction from mainstream players.
Open sourceXai Gas Subsidy documents EIP-712 typed data, ERC-2771 meta-transactions, trusted forwarder logic, and Xai relayer forwarding so user actions can be sponsored.
Open sourceXai developer pages list Blockscout explorers, public RPC endpoints, third-party RPC providers, token bridges, Safe multi-sig support, wallets, and contract address resources.
Open sourceMarketplace pages reference Reservoir, Snag Solutions, and RaribleX. On-chain randomisation pages reference Supra VRF for responsive verifiable random outcomes.
Open sourceThe Proof-of-Skill PDF frames SteamID login, automatic wallet creation, Steam achievements, leaderboards, Solidity contracts, and $XAI rewards as a bridge from traditional PC games to Web3.
Open PDFThe external audit found reachable sources for gas sponsorship, Xai RPC documentation, Arbitrum gas and node references, Sequence marketplace guides, and other developer-facing surfaces.
Open sourceAdditional reachable sources support marketplace builds, bridge/refuel UX, relay-style cross-chain movement, and VRF-backed verifiable random reward outcomes.
Open sourceOfficial Xai pages describe Offchain Labs as developing and servicing Xai under the Xai Foundation, and Ex Populus as an early game developer deploying on the Xai Blockchain.
Open sourceThe Xai Games Catalog lists ecosystem games and external game pages, while Ex Populus public pages provide additional context for Xai Network and game development.
Open sourceSentry documentation describes observation nodes, Sentry Keys, rewards, staking, delegation, pools, and operational pages that add infrastructure depth to the Xai ecosystem story.
Open sourceTemporary, private, or unofficial material is kept outside the citation layer. It is not treated as a stable public technical document and is not used to support protocol, integration, or investment claims.
Temporary, private, or unofficial material is excluded from technical claims, which are routed toward durable public web sources.
Technical statements use Xai GitBook, Proof-of-Skill PDF, Ex Populus context, developer tooling docs, explorer pages, marketplace docs, and recursive public source audit records instead of temporary or private screens.
The site does not turn ecosystem relationships or employee background references into investment claims. Specific investor names are stated only from an official Web Game Game announcement or public investor disclosure.
