> ## Documentation Index
> Fetch the complete documentation index at: https://corridor.udokaam.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Reading paths

> Four curated routes through the documentation: for investors, for CTOs and engineers, for chain ecosystem teams, and for liquidity partners.

Pick the route that matches what you need to decide. Each takes 15 to 30 minutes.

<Tabs>
  <Tab title="Investors">
    You want to know whether the market is real, whether the business earns, and whether the team can build it.

    <Steps>
      <Step title="The problem">
        [Why corridors cost so much](/market/the-problem): trapped capital, slow rails and manual reconciliation.
      </Step>

      <Step title="The market">
        [The global opportunity](/market/global-opportunity): \$31.6T of cross-border B2B payments, under 1% on stablecoins; then [First market: Africa](/market/africa-stablecoin-flows), where it starts.
      </Step>

      <Step title="The business">
        [Business model](/market/business-model): a ledger subscription from the first pilot, a take on routed volume, and revenue scenarios.
      </Step>

      <Step title="The proof">
        [Evidence](/status/evidence): every testnet transaction, and the [live console replay](https://corridorapp.udokaam.dev/console/).
      </Step>

      <Step title="What's next">
        [Roadmap](/status/roadmap): mainnet, design partners and the path to production.
      </Step>
    </Steps>
  </Tab>

  <Tab title="CTOs and engineers">
    You want to know whether the system is correct under failure, and how hard it would be to run.

    <Steps>
      <Step title="System overview">
        [Architecture overview](/architecture/overview) and the [core model](/architecture/core-model).
      </Step>

      <Step title="Money correctness">
        [Ledger](/architecture/ledger): double-entry, append-only, exactly-once external references, no-overdraft invariants.
      </Step>

      <Step title="Failure handling">
        [Saga engine](/architecture/saga) and [failure and compensation](/flows/failure-and-compensation).
      </Step>

      <Step title="Completeness">
        [Reconciliation](/architecture/reconciliation): three venues, one matcher, and a vault balance check that books gas from the chain.
      </Step>

      <Step title="Why it is built this way">
        The [architecture decision records](/decisions/index).
      </Step>
    </Steps>
  </Tab>

  <Tab title="Chain teams">
    You want to know how Corridor uses your chain, and whether it uses it well.

    <CardGroup cols={2}>
      <Card title="Tempo" img="https://mintcdn.com/corridorapp/YeOtjsXcStLLcZ_W/images/chains/tempo.svg?fit=max&auto=format&n=YeOtjsXcStLLcZ_W&q=85&s=e1151711829b954d04a0a3d5c8058c34" href="/integrations/tempo" width="64" height="64" data-path="images/chains/tempo.svg">
        The hub: TIP-20 memos, pathUSD, stablecoin gas via the Fee Manager.
      </Card>

      <Card title="Solana" img="https://mintcdn.com/corridorapp/YeOtjsXcStLLcZ_W/images/chains/solana.svg?fit=max&auto=format&n=YeOtjsXcStLLcZ_W&q=85&s=1f02bb5a523f35db49b138ad27b56989" href="/integrations/solana" width="64" height="64" data-path="images/chains/solana.svg">
        Partner liquidity: USDC with SPL Memo in one transaction.
      </Card>

      <Card title="Zcash" img="https://mintcdn.com/corridorapp/YeOtjsXcStLLcZ_W/images/chains/zcash.svg?fit=max&auto=format&n=YeOtjsXcStLLcZ_W&q=85&s=3bf73d9bfb3c2efd1b42dedb95729ff8" href="/integrations/zcash" width="64" height="64" data-path="images/chains/zcash.svg">
        The shielded lane: Ironwood batches, encrypted memos, scoped viewing keys.
      </Card>

      <Card title="Base and Across" img="https://mintcdn.com/corridorapp/YeOtjsXcStLLcZ_W/images/chains/base.svg?fit=max&auto=format&n=YeOtjsXcStLLcZ_W&q=85&s=b6fe4266150b59f85028b9279c8f5147" href="/integrations/across" width="64" height="64" data-path="images/chains/base.svg">
        Two-hop bridging out of the hub, and direct partner payouts on Base.
      </Card>
    </CardGroup>
  </Tab>

  <Tab title="Partners">
    You run a ramp or a payout rail and want to know what it takes to become a spoke.

    <Steps>
      <Step title="The network">
        [Hub and spoke](/architecture/hub-and-spoke): why one integration reaches every region.
      </Step>

      <Step title="The interface">
        [Partner interface](/integrations/partner-interface): six methods and a signed webhook.
      </Step>

      <Step title="A reference implementation">
        [Paj](/integrations/paj): offramp, onramp and webhooks against Paj's public API v2.
      </Step>

      <Step title="A full payout">
        [Payout EUR → NGN](/flows/payout-eur-ngn), end to end.
      </Step>
    </Steps>
  </Tab>
</Tabs>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.