# Ad Space Manifest 1 integration

> Implement a deterministic publisher-hosted `/adspace.json` resource. JSON is normative; agents assist with authoring but consumers do not need an LLM.

1. Read the [Manifest 1 specification](https://adspaceatlas.com/standards/adspace/1) and [immutable schema 1.0.0](https://adspaceatlas.com/standards/adspace/1.0.0/schema.json).
2. Give the [versioned implementation prompt](https://adspaceatlas.com/standards/adspace/1.0.0/agent-prompt.md) to a coding agent working inside the publisher repository.
3. Inspect the publisher's actual framework and implement the exact public route `https://<publisher-host>/adspace.json`.
4. Begin from the [minimal example](https://adspaceatlas.com/standards/adspace/1.0.0/minimal.json); add only documented facts. See the [complete example](https://adspaceatlas.com/standards/adspace/1.0.0/example.json) for optional structures.
5. Run deterministic validation with the [interactive validator](https://adspaceatlas.com/standards/adspace/1/validate) and the [conformance bundle](https://adspaceatlas.com/standards/adspace/1.0.0/conformance/index.json).
6. Test the final URL for HTTPS, status 200, `application/json`, valid UTF-8, and the one-megabyte decompressed limit.
7. Stop for publisher review. Do not deploy or [offer the exact URL to the Atlas](https://adspaceatlas.com/standards/adspace#offer-the-url) without explicit authorization.

Unknown properties and vocabulary terms are forward-compatible within Manifest 1. Unknown future same-major schema releases receive a compatibility warning. Never remove or reinterpret data merely because a local consumer does not understand it.