The two-origin security boundary

Artifact Server displays HTML artifacts on a large canvas. Published HTML cannot access the trusted application session.

Trusted application origin

The application origin owns:

• browser authentication and membership
• projects, artifact metadata, versions, and manifests
• comments, sharing, access changes, and administrative actions
• the review interface and its controls

Isolated content origin

Each exact artifact version uses an isolated content hostname. Content-session cookies apply only to the content host. Exact-version browser access uses single-use bootstraps. The trusted application embeds review content through a separate sandboxed frame.

app.example.com                      trusted application
version-token.content.example.com    isolated artifact bytes

The boundary lets artifacts use their own scripts, styles, images, fonts, and media without inheriting the trusted Artifact Server application’s credentials or network authority.