Skip to content

Add fail-closed Artifact Inspector interaction contract - #55

Merged
mikeylong merged 4 commits into
mainfrom
codex/artifact-inspector-contract
Aug 30, 2026
Merged

Add fail-closed Artifact Inspector interaction contract#55
mikeylong merged 4 commits into
mainfrom
codex/artifact-inspector-contract

Conversation

@mikeylong

Copy link
Copy Markdown
Owner

Summary

  • add the Artifact Inspector surface, workflow profile, artifact-centered topology, canonical work units, and scoped authority contract
  • preserve the reviewed activity, topology, artifact, target model, state groups, profile, and authority through handoff, frontend context, and skill compilation
  • bind each serialized Artifact Inspector boundary to a private stage-specific packet seal so caller mutation and cross-packet mixing fail closed
  • preserve legacy Workbench and marketing routing, including queue-primary selected-case detail
  • keep implementation review intentionally fail-closed at review_required; the external primary artifact remains external_not_reviewed, and this release exposes no trusted-runtime pass or attestation action

Validation

  • focused Artifact Inspector routing, workflow, authority, and surface-profile suites
  • kernel, Workbench profile, site, MCP, visual-composition browser runtime, and component suites
  • node tests/ui-generation-handoff.test.mjs passed; its 84 serial browser-backed reviews take roughly three minutes and produce no intermediate output
  • git diff --check

The single local npm test attempt was stopped at an artificial two-minute cutoff while the slow UI-handoff group was still progressing. That group subsequently passed in isolation; hosted CI remains the authoritative full-suite gate.

Deferred boundary

Genuine trusted interactive-runtime attestation is intentionally deferred to a separate project. It must supply a runnable state driver, real input and accessibility traces, focus return, occlusion, semantic re-anchoring, native-action precedence, the complete viewport/state matrix, and opaque candidate-and-contract-bound proof before Artifact Inspector can ever pass authority review.

@vercel

vercel Bot commented Aug 30, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
judgmentkit-ai Ready Ready Preview Aug 30, 2026 9:38pm

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 30, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-30T21:15:36.977386Z fa489cc PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fa489ccfe4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/index.mjs
Comment on lines +5556 to +5559
if (
topologyContract &&
(!entryWorkUnitId || !workUnitIds.includes(entryWorkUnitId))
) {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Require the canonical entry work unit during review

When an Artifact Inspector candidate sets entry_work_unit_id to any declared unit other than the canonical orient unit, this check still marks the workflow ready_for_review. The unchanged sealed packet is then rejected by createUiGenerationHandoff, whose stricter validation requires orient, so callers receive a ready result they cannot advance. Compare the entry against the registry value at the workflow-review boundary.

Useful? React with 👍 / 👎.

Comment thread src/index.mjs
Comment on lines +5577 to +5582
if (
topologyContract &&
(completionWorkUnitIds.length === 0 ||
invalidCompletionIds.length > 0 ||
!completionWorkUnitIds.includes("verify_result"))
) {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Validate the canonical completion set during review

A candidate with completion_work_unit_ids: ["verify_result"] passes this condition and is returned as ready_for_review, even though the canonical topology also requires orient and the later handoff validator requires the exact canonical set and ordering. Consequently, an unmodified reviewed packet is blocked at createUiGenerationHandoff; validate the completion IDs against the registry here rather than merely requiring one verify_result reference.

Useful? React with 👍 / 👎.

@mikeylong
mikeylong merged commit d9e62e7 into main Aug 30, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant