# filepacks

> filepacks creates portable, inspectable artifacts for agent workflows, evals, and regression comparisons.

## Docs

- [Agent workflows](https://filepacks.com/docs/agent-workflows.md): Use filepacks as durable evidence for agent runs, eval harnesses, and repeated review loops.
- [Determinism](https://filepacks.com/docs/artifacts/determinism.md): Why filepacks artifacts are byte-stable and why that matters for review, CI, and agent workflows.
- [Format](https://filepacks.com/docs/artifacts/format.md): Archive layout, path rules, and format constraints for valid .fpk artifacts.
- [Overview](https://filepacks.com/docs/artifacts/index.md): What lives inside a .fpk artifact and why the format is designed for trustworthy review.
- [Manifest](https://filepacks.com/docs/artifacts/manifest.md): The format_version 1 manifest fields, validation rules, and how they map to inspect, verify, and compare.
- [CI/CD Integration](https://filepacks.com/docs/ci-cd-integration.md): Use filepacks in CI to preserve generated output as deterministic evidence and compare it against an explicit baseline.
- [Compare](https://filepacks.com/docs/cli/compare.md): Structurally compare two .fpk artifacts by manifest path, size, and hash.
- [Overview](https://filepacks.com/docs/cli/index.md): The four public CLI commands, when to use each one, and how the CLI maps to @filepacks/core.
- [Inspect](https://filepacks.com/docs/cli/inspect.md): Read the summary metadata from an existing .fpk artifact.
- [Pack](https://filepacks.com/docs/cli/pack.md): Create a deterministic .fpk artifact from a directory of regular files.
- [Verify](https://filepacks.com/docs/cli/verify.md): Validate that an artifact still matches its manifest before you trust or compare it.
- [CLI workflows](https://filepacks.com/docs/cli/workflows.md): Practical command patterns for first-time use, review loops, CI jobs, and repeated artifact comparisons.
- [Concepts](https://filepacks.com/docs/concepts.md): Core filepacks terms, what they mean in practice, and how they fit into the four-command workflow.
- [Diffing](https://filepacks.com/docs/diffing.md): How to read compare results and use structural diffing in review workflows.
- [FAQ](https://filepacks.com/docs/faq.md): Common questions about what filepacks does, where it fits, and how to use the current OSS surface well.
- [Overview](https://filepacks.com/docs/index.md): Turn generated directories into deterministic .fpk artifacts that humans and agents can inspect, verify, compare, and hand off.
- [Installation](https://filepacks.com/docs/installation.md): Install filepacks for command-line use or add @filepacks/core to your own tooling.
- [Programmatic API](https://filepacks.com/docs/programmatic-api.md): Use @filepacks/core to pack, inspect, verify, and compare .fpk artifacts from Node.js tools and automation.
- [Quickstart](https://filepacks.com/docs/quickstart.md): Go from a generated directory to a verified and comparable .fpk artifact in a few minutes.
- [Troubleshooting](https://filepacks.com/docs/troubleshooting.md): Common filepacks problems, what they mean, and how to recover quickly.
- [Use cases](https://filepacks.com/docs/use-cases.md): Practical ways to use filepacks for evals, agent runs, CI evidence, review handoff, and regression comparison.
- [Why filepacks](https://filepacks.com/docs/why-filepacks.md): Why deterministic artifacts are easier to review, compare, and trust than loose output directories.

## OpenAPI Specs

- [openapi](https://filepacks.com/docs/api-reference/openapi.json)

## Optional

- [GitHub](https://github.com/robertonevarez/filepacks-oss)