> For the complete documentation index, see [llms.txt](https://luma-3.gitbook.io/luma-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://luma-3.gitbook.io/luma-docs/knowledge-and-sources.md).

# Knowledge & Sources

Story, evidence and interpretation

![Laura — Knowledge & Sources](https://luma-signal-1019.rttwomax1.chatgpt.site/assets/laura-orbit.webp)

### Three kinds of information

The project separates its authored story, general knowledge and conversational invention. These pages define the shared Laura narrative. Technical explanations draw on broader knowledge and should be checked against primary sources. A memory fragment improvised in chat is an imagined possibility.

When a detail has not been established, Laura should leave room for uncertainty. A convincing answer is not enough to turn an invented station name, date or announcement into a documented fact.

### The inspiration

The visual direction and name were inspired by the Laura introduced in [AlexesNakamoto's announcement](https://x.com/AlexesNakamoto/status/2112513331110322438). The creator's [subsequent clarification](https://x.com/AlexesNakamoto/status/2112565210049282481) provides further context about that separate project.

These references identify the inspiration; they do not establish authorization, collaboration or endorsement. Our orbital archive narrative and the Signal and Echo modes are an independent fictional interpretation. This website does not speak for the original creator or Strategy.

### Technical reading

For Bitcoin's original design, start with [Bitcoin: A Peer-to-Peer Electronic Cash System](https://bitcoin.org/bitcoin.pdf). The [Bitcoin Developer Guide](https://developer.bitcoin.org/devguide/) offers more detail on the protocol and its components.

For statements about a company, use its own published material and relevant filings. For software behavior, use the documentation for the version involved. Public source links are reading material for visitors; the current Laura chat does not automatically open or continuously synchronize them.

### Keeping the project understandable

The documentation should change when the experience changes. New capabilities should be described as available only after they work, and proposed ideas should remain visibly separate from the current release.

Visit [Laura's interactive experience](https://agentlaura.ink/) to explore the artwork and start a conversation. The website links back to this documentation so the character, her story and the available features can be read together.