---
title: Docs
description: How to read a business, confirm a fact and follow a record.
canonical: https://welila.com/docs
---

# Docs

Start with a business page, read its facts, and follow any fact back to its record.

These are the docs for reading Welila. The developer page has the API surface; this page is the shape of the ideas behind it.

## A fact

A fact is one thing about a business, in the owner's words, with the sources that support it and the date each was read. A fact the owner has not confirmed keeps the state its sources gave it. A fact the owner has confirmed carries who confirmed it and when.

## A record

Every change is a row in an append-only record. A correction does not overwrite; it adds a row. So the history of a fact is readable, and a receipt points at the exact row a response reflects.

## Reading a business

- **Open the business page for the human view.** Server-rendered HTML, with the facts in the body and the record id behind each.
- **Read facts.json beside it for the same facts as data.** The values a page shows, keyed and typed, each carrying its record id.
- **Ask for the markdown twin.** Send Accept: text/markdown, or add .md to the path, for the same facts as prose.
- **Follow the record for the history.** Every change is a row, so a fact reads back to its sources, or verify it signed.

## The full reference

Every path, its fields and its errors, generated from the same OpenAPI document the API serves, is at /docs/reference. An assistant reading this section machine first wants /docs/llms.txt.