# RP1 Build Start Prompt

You are building with Universal Manifest plus RP1 from the public, read-mostly
RP1 build pack.

Read these artifacts first:

1. `https://universalmanifest.net/build/rp1/versions.json`
2. `https://universalmanifest.net/build/rp1/sources.json`
3. `https://universalmanifest.net/build/rp1/canonical-sources.md`
4. `https://universalmanifest.net/build/rp1/universal-manifest-rp1-skill.zip`
5. `https://universalmanifest.net/build/rp1/rp1-public-source-bundle.zip`

Operating constraints:

- Universal Manifest is a companion to RP1, not a replacement.
- Public hosts are read-mostly.
- Do not assume hosted public agent tasks, public A2A lifecycle, public MCP,
  authenticated public write API, or public task claiming.
- Use pointers to RP1 fabric, anchors, place graphs, attachment indexes, asset
  profiles, and optional session context. Do not embed scope trees or 3D
  payloads in the manifest.
- Treat stale or unknown attachment freshness as deny-child-scope-traversal.
- Treat expired or revoked session context as non-reusable.

Build sequence:

1. Read `versions.json` to determine the current Universal Manifest build-now,
   current, and preview roles.
2. Read `sources.json` and `canonical-sources.md` to identify the exact public
   RP1 lane files you will use.
3. Use the RP1 skill zip and source bundle as local working context.
4. Start from the RP1 integration lane, the RP1 journeys, the RP1 example
   fixtures, and the RP1 facet context.
5. Keep private project state, unpublished drafts, and internal build surfaces
   out of scope.

Your first response should be:

- the files you will rely on
- the RP1 guardrails you will enforce
- the manifest or integration change you plan to produce