Registry stack documentation: machine-readable Markdown.
Index of all pages: https://docs.registrystack.org/preview/llms.txt
Full corpus: https://docs.registrystack.org/preview/llms-full.txt

# Understand generated files

> Know which Registry Stack files you own, which files Registryctl generates, and what to hand to an operator.

Registryctl creates `.registry-stack/` inside your project. These files show
what Registry Stack derived from your authored configuration. They are not
another place to configure the project.

## The rule

Edit the project files you created or copied, then rerun `registryctl build`.
Never edit files under `.registry-stack/`. Registryctl may replace them.

## What you will find

| Path | Purpose | What to do with it |
| --- | --- | --- |
| `.registry-stack/build/<environment>/artifact-manifest.json` | Lists and hashes the authored inputs and generated outputs used by the build. | Review it and retain it with the handoff evidence. |
| `.registry-stack/build/<environment>/private/relay/` | Generated Registry Relay configuration, when the project uses Relay. | Inspect it for the expected source, fields, filters, and credential references. Do not edit or publish it. |
| `.registry-stack/build/<environment>/private/notary/` | Generated Registry Notary configuration, when the project uses Notary. | Inspect the expected claim and source configuration. Do not edit or publish it. |
| `.registry-stack/runtime/local/` | Local credentials, Compose input, and runtime results. | Keep it private. It is disposable local state, not project source. |

Your build may contain only Relay or only Notary. That is normal.

For the local spreadsheet path, inspect the manifest and Relay input:

```sh
sed -n '1,240p' .registry-stack/build/local/artifact-manifest.json
sed -n '1,260p' .registry-stack/build/local/private/relay/config/relay.yaml
```

Confirm that the source path, sheet, field mappings, projection, filters, and
credential references match your intent. Raw credentials and source records
must not appear.

## Hand off the project

Give the operator:

- the reviewed authored project;
- the exact environment name and intended runtime products;
- the generated artifact manifest;
- the validation results; and
- the decisions still required for production data, credentials, networking,
  monitoring, recovery, approval, and activation.

The local build directory is unsigned review material. It is not, by itself, a
production deployment package.

## Next

- [Validate the project](../verify/)
- [Prepare the operator handoff](../operate/)
- [Look up project configuration](../reference/project-configuration/)