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

# Architecture Guides

> How sync architectures work, and practical guidance for using PowerSync to build apps for specific use cases, industries and architectural patterns.

## Fundamentals

> [card] [Offline-First Architecture Terms](https://docs.powersync.com/resources/architecture-guides/offline-first-architecture.md)
>
> Outbox, idempotency key, delta sync, tombstones, last-write-wins: the building blocks of any offline-first sync architecture. Learn what each one means, and which ones PowerSync handles for you.

## By Use Case

> [card] [AI Chat](https://docs.powersync.com/resources/architecture-guides/ai-chat.md)
>
> Store AI chats as database rows, with sync handling chat history and multi-device sessions. You get a robust app with less backend code.

## By Industry

> [card] [Retail Point-of-Sale (POS)](https://docs.powersync.com/resources/architecture-guides/offline-first-pos.md)
>
> Your POS must keep checkout running when the network goes down. PowerSync removes most of the outbox, retry and update plumbing needed to implement an offline-first POS system.

## By Software Philosophy

> [card] [Local-First Software](https://docs.powersync.com/resources/architecture-guides/local-first-software.md)
>
> Local-first software is a term coined by the research lab Ink & Switch in a 2019 manifesto essay. In local-first software, the device holds the primary copy of the data. See which of the manifesto's seven ideals PowerSync helps you meet.


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