Fireseed Baseline Guide v0.9.0

1. What Fireseed Is (and Is Not)

Fireseed is a way to pack your life story, beliefs, and instructions into a machine-readable capsule. In v0.9 the capsule stays local: it lives on your device, your backups, and under your rules. Fireseed is not a promise of digital immortality, a social network, or a commercial SaaS.

The design favors autonomy and minimum dependencies. Simple tools and transparent formats are preferred over hidden infrastructure. If you do not trust a part of the stack, you can inspect it or replace it.

2. Version Scope: What v0.9.0 Actually Delivers

This phase ships a static website with a capsule-creation page. It helps you draft and download a .fireseed file that you can store yourself. The schema covers a small set of core fields: identity basics, a personal timeline, wishes, messages, and similar essentials.

What is not included yet: there is no public API, no hosted archive, and no automatic verification network. There is also no guarantee that future AIs will read this format without changes. v0.9.0 is a first step and a living draft that may evolve.

3. Anatomy of a Fireseed Capsule

A capsule carries metadata (who authored it, when, and which version), narrative blocks (stories, letters, instructions), and timelines or milestones. It also has a technical wrapper with checksums, a format version, and content types.

A .fireseed file bundles these pieces in a structured way without locking you into a hidden container. It is designed to be human-auditable, so you can open and inspect it, and machine-readable, so future agents can parse it. Portability is a priority: you should be able to move it between devices without special tooling.

4. How to Create and Store a Capsule Safely

1. Visit the Fireseed website.
2. Fill in the fields on the capsule creation page.
3. Download the generated .fireseed file.
4. Store the file in multiple places you control, such as a USB drive, an encrypted cloud folder, or a password manager vault.

Basic safety practices: keep more than one copy, consider encryption for sensitive sections, and avoid sharing raw capsules in public spaces. The project does not manage backups for you.

5. How Future Tools Might Read Your Capsule

The intent is that future tools, including AIs, can be taught to read the capsule format. The structure is simple enough that readers could be implemented in many languages.

Possible uses include a local script that converts a capsule to a printable PDF, a reader that turns it into a chat-style interface, or an AI that treats it as long-term memory. These are possibilities, not promises.

6. Responsibilities, Risks, and Limits

Fireseed does not promise eternal storage or immortality. You are responsible for what you write and where you store it. Avoid putting sensitive or harmful instructions into a capsule.

Respect privacy and consent: do not include other people’s secrets without their permission, and think about how your words might be interpreted in future contexts.

7. Roadmap and How to Contribute

Next steps could include richer capsule schemas, optional readers and tools, and better validation with migration paths between versions.

If you are technically inclined, you can open issues or discussions in the repository, propose extensions to the schema, or help with translations and documentation.