Platform
Review prompts from the Rootcastle Prompt Archive
Trace a downloaded prompt to a pinned source, distinguish integrity from publisher authentication and preserve the inputs needed to reproduce a composed prompt.

Treat a prompt as research material
A retrieved prompt can contain useful domain vocabulary or questions for a review. Read its text the way you would read an external document. A composed prompt should keep the user’s goal, tool permissions and reviewed references distinguishable.
The upstream implementation uses a fixed origin, bounded downloads and scan results to guide selection. Check the provenance and license before incorporating a public reference. Use fictional or redacted task examples when testing a composition you plan to share.
Read the verification fields
An SHA-256 digest can tie the bytes you received to a manifest and help detect cache changes. The documented archive model uses HTTPS origin and digests; detached publisher signature verification is tracked separately. Record the origin, manifest digest, content digest, version and cache state in your review evidence.
Record whether the cache was fresh or an offline fallback. A pinned reproducible composition needs the same reference bytes and review context. If the source changed and you want to update, inspect the diff and explicitly save the new pin.
Keep vended text inside the review boundary
External examples can imitate higher-priority messages or propose tool calls. Keep them clearly delineated as references. Review any requested command, service destination or permission outside the prompt composing step. Confirm the workspace contains only the material you intend to give an external tool.
A useful smoke test supplies benign reference text, a stale snapshot and a reference with contradictory instructions, then checks the resulting provenance and expected handling. Inspect the output artifacts and keep snapshots for comparison.
Document the result
Save the prompt version and reason for selection along with the composed output. If another reviewer needs to repeat it, give them the input brief and the reference identities. Keep command execution or workspace changes in separately reviewed steps.
Repository sources
References are pinned to the same upstream commit as the public catalog.