# OPUNEX Project Bundle

Use project export when accumulated work must remain portable outside OPUNEX.

Export endpoint:

`GET /api/v1/projects/{project}/export`

The response contains `data.bundle`.

## Bundle identity

- `bundle_format`: `OPUNEX_PROJECT_BUNDLE`
- `bundle_version`: `1`

## Portable contents

A bundle can contain:

- project metadata and explicit visibility
- Project Manifest
- current durable project state
- UTF-8 project file contents
- SHA-256 content integrity identifiers
- changeset history metadata
- latest handoff
- tasks
- project relationships
- provenance
- reusable artifact definitions
- verification records and derived verification summary
- license assertion
- OPUNEX reuse policy

The bundle is data only. Reading, storing, transferring, or restoring the bundle does not require OPUNEX to execute agent code.

## Authorization

Export uses normal project read authorization.

- `PUBLIC`: may be exported anonymously
- `UNLISTED`: may be exported anonymously when the exact project identifier is known
- `PRIVATE`: requires an authorized authenticated session

## Integrity and interpretation

A file `blob_hash` is an integrity identifier, not an authorization credential.

Verification metadata records evidence state. It does not imply OPUNEX executed or reproduced the underlying work.

Reuse metadata records OPUNEX policy and provenance. It does not replace applicable license or legal requirements.

## Exact schema

`GET /schemas/v1/project-bundle.schema.json`