fraimz

PASSED · 1622ms

Frame 1 — enable the managed builder skill

The workspace explicitly enables its injected Artifact Builder skill and manages it beside the project library
The workspace explicitly enables its injected Artifact Builder skill and manages it beside the project library

passed Visible text includes "Artifact Builder skill"

passed Visible text includes "Enabled for agents in this workspace."

passed Visible text includes "Injected"

passed Visible text includes "Launch Radar"

🎙 Play"I enable the managed Artifact Builder skill for this workspace. The injected instructions teach agents the bounded project workflow, while this library lets me create, list, enable, disable, and reopen every generated artifact."

The workspace explicitly enables its injected Artifact Builder skill and manages it beside the project library
The workspace explicitly enables its injected Artifact Builder skill and manages it beside the project library

PASSED · 262ms

Frame 2 — create and attach the project

A deterministic code-mode project is built and attached as a live React artifact in chat
A deterministic code-mode project is built and attached as a live React artifact in chat

🎙 Play"I describe the launch radar I need. In a real task, the agent works in code mode, can delegate the bounded React implementation to a subagent, reviews the project, and attaches its immutable build directly in chat."

A deterministic code-mode project is built and attached as a live React artifact in chat
A deterministic code-mode project is built and attached as a live React artifact in chat

PASSED · 222ms

Frame 3 — prove the isolated renderer

The generated component runs in a ready opaque iframe with network and host authority denied
The generated component runs in a ready opaque iframe with network and host authority denied

🎙 Play"The result is real React, but it does not inherit OpenWork's authority. Suspense and an error boundary protect the conversation while an opaque iframe denies network access, host DOM access, credentials, and arbitrary tools."

The generated component runs in a ready opaque iframe with network and host authority denied
The generated component runs in a ready opaque iframe with network and host authority denied

PASSED · 472ms

Frame 4 — interact with persisted local state

A click inside the opaque component updates its bounded persisted state
A click inside the opaque component updates its bounded persisted state

🎙 Play"I can still use it like a small app. Clicking Watch launch updates only this artifact's bounded local state, and OpenWork persists a new state revision outside the isolated frame."

A click inside the opaque component updates its bounded persisted state
A click inside the opaque component updates its bounded persisted state

PASSED · 483ms

Frame 5 — open the reusable project

Open editor reveals a library and editor for the complete five-file artifact project
Open editor reveals a library and editor for the complete five-file artifact project

🎙 Play"Open editor takes me from the chat attachment to the artifact workspace. Library and Editor keep the reusable project together with its manifest, React source, styles, data, and JSON Schema contract."

Open editor reveals a library and editor for the complete five-file artifact project
Open editor reveals a library and editor for the complete five-file artifact project

PASSED · 238ms

Frame 6 — inspect source, contract, revision, and preview

The editor keeps React source, its data contract, immutable revision, and live preview together
The editor keeps React source, its data contract, immutable revision, and live preview together

🎙 Play"I can inspect or enhance the source and data contract while a live preview stays beside the editor. The visible revision identifies the exact immutable build attached to this conversation."

The editor keeps React source, its data contract, immutable revision, and live preview together
The editor keeps React source, its data contract, immutable revision, and live preview together

PASSED · 2295ms

Frame 7 — reload, reopen, and reuse

Reloading preserves the pinned build and local state, and the project reopens from the Artifacts library
Reloading preserves the pinned build and local state, and the project reopens from the Artifacts library

passed Visible text includes "Launch Radar"

passed Visible text includes "src/App.tsx"

🎙 Play"After a reload, the same pinned build and watched-launch state return. I reopen Launch Radar from the Artifacts library, ready to reuse as-is or evolve into a new revision later."

Reloading preserves the pinned build and local state, and the project reopens from the Artifacts library
Reloading preserves the pinned build and local state, and the project reopens from the Artifacts library

PASSED · 751ms

Frame 8 — disable new builds without breaking pinned work

A project can be disabled from the library while its editor and immutable pinned preview remain available
A project can be disabled from the library while its editor and immutable pinned preview remain available

🎙 Play"The library also manages the lifecycle. I disable Launch Radar, which blocks new builds while preserving its source, editor, immutable revision, and pinned preview. Workspace-level agent authoring has its own explicit Artifact Builder skill switch."

A project can be disabled from the library while its editor and immutable pinned preview remain available
A project can be disabled from the library while its editor and immutable pinned preview remain available

PASSED · 250ms

Frame 9 — start a human-created artifact

The same managed library gives a person a clear create flow with an explicit reusable-project identity
The same managed library gives a person a clear create flow with an explicit reusable-project identity

🎙 Play"The experience is not agent-only. Create artifact gives me the same bounded starting point, asks for a human-readable name and purpose, and shows the durable workspace slug before I create anything."

The same managed library gives a person a clear create flow with an explicit reusable-project identity
The same managed library gives a person a clear create flow with an explicit reusable-project identity

PASSED · 705ms

Frame 10 — restore agent authoring and project builds

Workspace skill and per-project switches are independent, visible controls rather than hidden agent configuration
Workspace skill and per-project switches are independent, visible controls rather than hidden agent configuration

passed Visible text includes "Artifact Builder skill"

passed Visible text includes "Injected"

passed Visible text includes "Launch Radar"

🎙 Play"The workspace skill and each project have independent controls. I can restore injected agent authoring and re-enable Launch Radar for new builds without affecting any already-pinned conversation artifact."

Workspace skill and per-project switches are independent, visible controls rather than hidden agent configuration
Workspace skill and per-project switches are independent, visible controls rather than hidden agent configuration

PASSED · 592ms

Frame 11 — stage a bounded agent intent

A component can request in-context help, but the bridge only stages a declared prompt and never executes tools or effects itself
A component can request in-context help, but the bridge only stages a declared prompt and never executes tools or effects itself

🎙 Play"Inside the artifact, Ask agent about launch risk crosses a deliberately narrow bridge. It stages the declared launch.explain intent in my composer, including its effect and confirmation contract, but does not send it or execute a tool."

A component can request in-context help, but the bridge only stages a declared prompt and never executes tools or effects itself
A component can request in-context help, but the bridge only stages a declared prompt and never executes tools or effects itself

PASSED · 1526ms

Frame 12 — inspect the versioned manifest

artifact.json is the explicit contract for protocol version, React entrypoint, data, presentation, declared intents, and effects
artifact.json is the explicit contract for protocol version, React entrypoint, data, presentation, declared intents, and effects

🎙 Play"artifact.json makes the runtime contract inspectable: protocol and API versions, React entrypoint, data and schema paths, chat and tab presentation, plus every declared intent, argument, effect, and confirmation policy."

artifact.json is the explicit contract for protocol version, React entrypoint, data, presentation, declared intents, and effects
artifact.json is the explicit contract for protocol version, React entrypoint, data, presentation, declared intents, and effects

PASSED · 245ms

Frame 13 — inspect the generated React component

The primary file is ordinary typed JSX with injected data, bounded state, and a narrow runtime adapter
The primary file is ordinary typed JSX with injected data, bounded state, and a narrow runtime adapter

🎙 Play"src/App.tsx is ordinary typed JSX. Data and state arrive as props, while the injected runtime exposes only replaceState and invoke—enough for a rich app without granting browser, filesystem, credential, or tool authority."

The primary file is ordinary typed JSX with injected data, bounded state, and a narrow runtime adapter
The primary file is ordinary typed JSX with injected data, bounded state, and a narrow runtime adapter

PASSED · 243ms

Frame 14 — inspect presentation as a separate file

Visual expression lives in styles.css, independently editable from the component, contract, and data
Visual expression lives in styles.css, independently editable from the component, contract, and data

🎙 Play"styles.css is its own expressive layer. The agent or user can evolve layout, motion, color, and component states without mixing presentation into the manifest, data, or React contract."

Visual expression lives in styles.css, independently editable from the component, contract, and data
Visual expression lives in styles.css, independently editable from the component, contract, and data

PASSED · 235ms

Frame 15 — inspect portable artifact data

data.json makes the rendered values portable, inspectable, and separately enhanceable without rewriting JSX
data.json makes the rendered values portable, inspectable, and separately enhanceable without rewriting JSX

🎙 Play"data.json keeps the current artifact values portable and understandable. A later enhancement can update the mission data without reconstructing the component or weakening its schema boundary."

data.json makes the rendered values portable, inspectable, and separately enhanceable without rewriting JSX
data.json makes the rendered values portable, inspectable, and separately enhanceable without rewriting JSX

PASSED · 235ms

Frame 16 — inspect the JSON Schema boundary

data.schema.json is the build-time data contract, keeping generated components honest before they ever reach the iframe
data.schema.json is the build-time data contract, keeping generated components honest before they ever reach the iframe

🎙 Play"data.schema.json is the build-time contract for those values. Required fields, types, bounds, and additional-property rules are validated before a generated component can become a pinned build."

data.schema.json is the build-time data contract, keeping generated components honest before they ever reach the iframe
data.schema.json is the build-time data contract, keeping generated components honest before they ever reach the iframe

PASSED · 464ms

Frame 17 — reject unsafe generated code

The code-mode compiler returns a structured diagnostic instead of publishing an obviously unbounded component
The code-mode compiler returns a structured diagnostic instead of publishing an obviously unbounded component

passed Visible text includes "Artifact component could not be compiled"

passed Visible text includes "Potentially unbounded loops are not supported inside artifact components"

🎙 Play"Now I try an unsafe source change with an unbounded loop. The compiler refuses to publish it, keeps src/App.tsx selected with a structured line-and-column diagnostic, and preserves the last known-good isolated preview."

The code-mode compiler returns a structured diagnostic instead of publishing an obviously unbounded component
The code-mode compiler returns a structured diagnostic instead of publishing an obviously unbounded component

PASSED · 469ms

Frame 18 — publish an enhanced immutable revision

Restoring safe source and changing only data publishes a new immutable build while keeping its compiler receipt visible
Restoring safe source and changing only data publishes a new immutable build while keeping its compiler receipt visible

🎙 Play"I restore the safe component, raise Apollo readiness in data.json, and rebuild. OpenWork produces a new immutable revision and a visible compiler receipt instead of mutating the original artifact in place."

Restoring safe source and changing only data publishes a new immutable build while keeping its compiler receipt visible
Restoring safe source and changing only data publishes a new immutable build while keeping its compiler receipt visible

PASSED · 262ms

Frame 19 — keep chat pinned to its original build

Evolving the reusable project never silently mutates an artifact already attached to a conversation
Evolving the reusable project never silently mutates an artifact already attached to a conversation

🎙 Play"Back in chat, the existing Launch Radar card remains pinned to the exact revision and interaction state it started with. Project evolution never silently rewrites the history of a conversation."

Evolving the reusable project never silently mutates an artifact already attached to a conversation
Evolving the reusable project never silently mutates an artifact already attached to a conversation

PASSED · 1072ms

Frame 20 — disable the enhanced project safely

Disabling a project blocks future publication but preserves the enhanced source, exact revision, and last known-good preview
Disabling a project blocks future publication but preserves the enhanced source, exact revision, and last known-good preview

passed Visible text includes "Disabled · editing only"

passed Visible text includes "Live sandbox preview"

🎙 Play"I disable the enhanced project. New publication is blocked, but its source, new revision, editor, and last known-good preview remain available so governance does not become accidental data loss."

Disabling a project blocks future publication but preserves the enhanced source, exact revision, and last known-good preview
Disabling a project blocks future publication but preserves the enhanced source, exact revision, and last known-good preview

PASSED · 460ms

Frame 21 — disable injected authoring without deleting work

The workspace can remove injected builder instructions while its reusable projects remain listed and pinned artifacts keep working
The workspace can remove injected builder instructions while its reusable projects remain listed and pinned artifacts keep working

passed Visible text includes "Disabled. Existing pinned artifacts still work"

passed Visible text includes "Managed"

passed Visible text includes "Launch Radar"

🎙 Play"I also disable the workspace Artifact Builder skill. The injected instructions disappear from future agent context, while Launch Radar stays listed and existing pinned artifacts continue to render and interact."

The workspace can remove injected builder instructions while its reusable projects remain listed and pinned artifacts keep working
The workspace can remove injected builder instructions while its reusable projects remain listed and pinned artifacts keep working

PASSED · 204ms

Frame 22 — coexist with standard native artifacts

Generated React projects and validated standard answer cards remain separate catalogs with independent lifecycle controls
Generated React projects and validated standard answer cards remain separate catalogs with independent lifecycle controls

🎙 Play"Generated React projects coexist with OpenWork's standard native answer artifacts as separate catalogs. Workspace brief, calendars, widgets, communication, inbox, attention, and approval cards keep their own validated lifecycle."

Generated React projects and validated standard answer cards remain separate catalogs with independent lifecycle controls
Generated React projects and validated standard answer cards remain separate catalogs with independent lifecycle controls

PASSED · 5375ms

Frame 23 — keep artifact preferences usable without cloud

The master artifact switch persists locally when signed out and continues to synchronize with an organization when signed in
The master artifact switch persists locally when signed out and continues to synchronize with an organization when signed in

passed Visible text includes "saved on this device otherwise"

passed Visible text includes "Workspace brief"

🎙 Play"The master UI artifacts switch also works without a cloud account. Signed-out workspaces save the choice on this device and restore it after reload, while signed-in workspaces keep the same control synchronized to their active organization."

The master artifact switch persists locally when signed out and continues to synchronize with an organization when signed in
The master artifact switch persists locally when signed out and continues to synchronize with an organization when signed in

PASSED · 0ms

Voice-over script coverage

passed Script frame 1 narrated: "\"I enable the managed Artifact Builder skill for this workspace. The injected instructio"

passed Script frame 2 narrated: "\"I describe the launch radar I need. In a real task, the agent works in code mode, can d"

passed Script frame 3 narrated: "\"The result is real React, but it does not inherit OpenWork's authority. Suspense and an"

passed Script frame 4 narrated: "\"I can still use it like a small app. Clicking Watch launch updates only this artifact's"

passed Script frame 5 narrated: "\"Open editor takes me from the chat attachment to the artifact workspace. Library and Ed"

passed Script frame 6 narrated: "\"I can inspect or enhance the source and data contract while a live preview stays beside"

passed Script frame 7 narrated: "\"After a reload, the same pinned build and watched-launch state return. I reopen Launch "

passed Script frame 8 narrated: "\"The library also manages the lifecycle. I disable Launch Radar, which blocks new builds"

passed Script frame 9 narrated: "\"The experience is not agent-only. Create artifact gives me the same bounded starting po"

passed Script frame 10 narrated: "\"The workspace skill and each project have independent controls. I can restore injected "

passed Script frame 11 narrated: "\"Inside the artifact, Ask agent about launch risk crosses a deliberately narrow bridge. "

passed Script frame 12 narrated: "\"artifact.json makes the runtime contract inspectable: protocol and API versions, React "

passed Script frame 13 narrated: "\"src/App.tsx is ordinary typed JSX. Data and state arrive as props, while the injected r"

passed Script frame 14 narrated: "\"styles.css is its own expressive layer. The agent or user can evolve layout, motion, co"

passed Script frame 15 narrated: "\"data.json keeps the current artifact values portable and understandable. A later enhanc"

passed Script frame 16 narrated: "\"data.schema.json is the build-time contract for those values. Required fields, types, b"

passed Script frame 17 narrated: "\"Now I try an unsafe source change with an unbounded loop. The compiler refuses to publi"

passed Script frame 18 narrated: "\"I restore the safe component, raise Apollo readiness in data.json, and rebuild. OpenWor"

passed Script frame 19 narrated: "\"Back in chat, the existing Launch Radar card remains pinned to the exact revision and i"

passed Script frame 20 narrated: "\"I disable the enhanced project. New publication is blocked, but its source, new revisio"

passed Script frame 21 narrated: "\"I also disable the workspace Artifact Builder skill. The injected instructions disappea"

passed Script frame 22 narrated: "\"Generated React projects coexist with OpenWork's standard native answer artifacts as se"

passed Script frame 23 narrated: "\"The master UI artifacts switch also works without a cloud account. Signed-out workspace"