# Export Policy

Status: PENDING VERIFICATION

## Export Types

### Public SDK

Intent:

- publish architecture contracts and examples;
- attract technical feedback;
- accept tooling/tests/docs PRs.

Default source:

- files already moved or copied into explicit public-facing folders such as
  `Assets/_Project/Public/**`;
- stable docs rewritten or copied into the publication template, not selected
  from production `Docs/`;
- new placeholder samples created in the export repo, not copied from production.

Production `Assets/_Project/Scripts/**` is not broad-allowed. If a contract is safe
for public release, copy or rewrite it into a public-facing folder first, then export.

Default public SDK export copies zero production files. It is template-only until
specific files are promoted through `PUBLIC_API_PROMOTION.md`.

### Contributor Sandbox

Intent:

- runnable project for external work.

Default source:

- public SDK;
- placeholder art/audio/data;
- mock scenes;
- isolated test harness.

Current default contributor sandbox export copies zero production files. It is
template-only until specific paths move from
`profiles/contributor-sandbox.candidate` into
`profiles/contributor-sandbox.allow` after review.

### Private Contractor Slice

Intent:

- scoped collaboration with a trusted person.

Default source:

- minimum viable domain subset;
- placeholder foreign-domain interfaces;
- no whole-production history.

## Export Invariants

- Export destination must be outside `C:\hades\Hecton8`.
- Export starts from an empty or explicitly replaceable folder.
- Export does not copy `.git`.
- Export does not copy ignored build/cache folders.
- Export denylist wins over allowlist.
- Export profiles must pass `Test-H8ProfilePolicy.ps1` before any source file
  is copied.
- Selected source files must be clean in Git; staged or unstaged selected-file
  changes are rejected before copy.
- Git symlinks, gitlinks/submodules, and filesystem reparse points are rejected
  before copy. Link policy after copy is not enough because copy tools can
  dereference links.
- Export may overlay templates after copying allowed production files.
- Export gate runs after copy.
- Passing static gate does not prove runtime/build correctness.

## Publication Blockers

Any of these blocks publication:

- third-party asset or plugin folder present;
- baked `.h8bin` data present;
- binary plugin `.dll` present;
- source art/audio/model files present unless explicitly public-placeholder;
- internal specs present;
- agent logs or prompts present;
- old production Git history present;
- source path references private project layout as required dependency.

## Human Review Checklist

- Does this file need to exist publicly?
- Can the same collaboration happen with an interface, test, or mock?
- Does this reveal a production implementation that gives away too much?
- Does this reveal current content, progression, economy, or unreleased design?
- Does this depend on vendor content?
- Can it be rebuilt from public dependencies only?

If the answer is unclear, keep it private.
