The public filepacks artifact is a deterministicDocumentation Index
Fetch the complete documentation index at: https://filepacks.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
.fpk archive.
It contains:
manifest.jsonas the first entry- payload files under
payload/
format_version: 1 manifests only.
What the artifact gives you
A.fpk file is designed to be:
- portable as one file
- inspectable through the manifest
- verifiable against the payload
- comparable against another artifact with deterministic rules
What’s inside a .fpk file
A .fpk artifact has a fixed layout:
manifest.json records the artifact name, file count, total size, per-file hashes, and a payload digest. Those values are what inspect, verify, and compare operate on — no payload extraction needed for most operations.
Why manifest-first packaging matters
The format is the trust anchor for the current OSS release:- the artifact is portable as one file
- the manifest is the canonical file inventory
- verification is local and deterministic
- comparison is manifest-driven, not filesystem-dependent
.fpk bytes, making the digest stable across machines and time.
Public artifact guarantees
.fpkis a POSIX tar archivemanifest.jsonmust appear exactly oncemanifest.jsonmust be the first entry- entries outside
manifest.jsonandpayload/are invalid - payload entries must be regular files
- directory entries must not be emitted
- payload paths must be normalized relative paths
Which artifact page to read next
| If you need… | Read |
|---|---|
| field-by-field manifest details | Manifest |
| archive layout and path rules | Format |
| determinism guarantees and why they matter | Determinism |