llm-wiki-archive

LLM-Wiki Archive

Goal

Make an LLM-Wiki durable, portable and reconstructable over long time horizons.

When to use

• The user wants a wiki to remain readable and rebuildable 5-10+ years from now, without depending on today's tooling.
• The user is exporting a vault to a git tag, zip/tarball, static export, offline drive, or public archive.
• The user needs to know whether an opaque store (vector DB, generated index) is safe to treat as source of truth or must be excluded/rebuilt.
• The user wants an ARCHIVE.md manifest documenting what's included, what's excluded, and how to rebuild indexes from Markdown/raw sources.
• The user is auditing portability risks such as external links without local copies, attachments outside the vault, or unsupported formats.

Inputs

• Vault/repository path.
• Desired archive target: git tag, zip/tarball, static export, offline drive, public archive.
• Retention and privacy constraints.
• Existing generated indexes or databases.

Procedure

1. Identify source of truth

Classify artifacts:

Artifact	Archive role
Markdown files	Primary human-readable source.
raw sources/assets	Primary evidence.
schemas/taxonomy	Rebuild instructions.
generated indexes	Rebuildable cache.
vector DBs	Usually exclude or export manifest only.
logs/reports	Audit history.

2. Check portability

Look for:

• opaque databases as only source of truth;
• external links without local copy or citation;
• attachments outside the vault;
• unsupported file formats;
• generated pages without source references;
• missing schema files.

3. Create archive manifest

Recommended ARCHIVE.md sections:

# Archive manifest

## Snapshot date

## Included folders

## Excluded generated caches

## How to read

## How to rebuild indexes

## Known gaps

## Integrity checks

4. Add integrity metadata

Generate or recommend hashes for raw sources, important pages and exported bundles.