GuideShot docs
Safe input before beautiful output.
You will know where captured state can contain sensitive data and how to keep raw scenes, caches, and published artifacts safe.
The trust boundary
Project adapters are trusted repository code
Recipes remain data. Authentication, seed state, roles, and feature flags live in reviewed scenarios and dimensions where normal code ownership and secret handling apply.
Privacy layers
Apply protection as early as possible. A value masked before caching cannot leak through later recomposition.
- Allow only the exact application origins required for capture.
- Use synthetic users, workspaces, and tokens created for documentation.
- Mask sensitive targets before the raw capture enters the cache.
- Use composition redactions for fields that should disappear from the published artifact.
- Keep caches, traces, and detailed run reports private and access-controlled.