Add fail-closed Artifact Inspector interaction contract

CHANGELOG.md

@@ -2,6 +2,16 @@
 
 ## Unreleased
 
+## 0.8.0 - 2026-08-30
+
+- Added Artifact Inspector as a versioned public interaction-model contract for grounded, artifact-primary review work.
+- Publishes the `artifact_inspector` surface, `artifact-inspector-ui` workflow profile, `artifact_centered` topology, and `judgmentkit.artifact-inspector.v1` presentation profile through the package and MCP APIs.
+- Carries the canonical work units, artifact identity, target model, active states, and scoped JudgmentKit authority through the workflow, handoff, and frontend boundaries.
+- Keeps legacy Workbench and marketing routing isolated from Artifact Inspector authority.
+- Keeps implementation review fail-closed at `review_required`; the primary artifact remains external and is not reviewed by JudgmentKit.
+- Keeps the Artifact Inspector surface and presentation profile at `proposed` promotion status while the runtime proof path remains deferred.
+- Defers trusted interactive runtime attestation to a separate release. This release does not expose an action or result that claims complete runtime boundary proof.
+
 ## 0.7.0 - 2026-08-08
 
 - Added the supported `judgmentkit.workbench.operational-v1` surface-presentation profile for grounded Workbench activity.

DESIGN.md

@@ -21,13 +21,15 @@ The interaction contract translates that activity into a surface: what the user
 
 ### Surface Type
 
-The surface type classifies activity purpose before frontend implementation: marketing, workbench, operator review, form flow, dashboard monitor, content/report, setup/debug tool, or conversation. It is interaction guidance, not a visual theme.
+The surface type classifies activity purpose before frontend implementation: marketing, workbench, operator review, artifact inspector, form flow, dashboard monitor, content/report, setup/debug tool, or conversation. It is interaction guidance, not a visual theme. Artifact Inspector applies only when one rendered artifact is primary, semantic locus selection is required, and supporting context is meaningful relative to that locus; layout vocabulary or a keyword alone is insufficient.
 
 ### Surface Presentation Profile
 
 A surface presentation profile applies governed design-system guidance after the surface type is grounded. It can shape density, type hierarchy, region hierarchy, action emphasis, status treatment, and responsive behavior without reclassifying the activity or replacing the interaction contract.
 
-The JudgmentKit default design system selects `judgmentkit.workbench.operational-v1` automatically for a Workbench supplied by the caller or recommended with medium or high confidence. `surface_profile: "none"` opts out, while the exact profile id locks that supported version. The neutral low-confidence Workbench fallback selects no profile. External design systems receive no JudgmentKit profile fallback.
+The JudgmentKit default design system selects `judgmentkit.workbench.operational-v1` automatically for a Workbench supplied by the caller or recommended with medium or high confidence. It selects `judgmentkit.artifact-inspector.v1` for a grounded Artifact Inspector. `surface_profile: "none"` opts out, while an exact profile id locks that version. The neutral low-confidence Workbench fallback selects no profile. External design systems receive no JudgmentKit profile fallback.
+
+Artifact Inspector has scoped visual authority rather than whole-surface JudgmentKit authority. JudgmentKit governs the inspector chrome and inspection overlay; the rendered artifact preserves its declared external authority. Reviews must report owned-scope, artifact-preservation, and boundary results separately and must not describe the external artifact as JudgmentKit-conformant. This contract release has no trusted interactive-attestation producer or verifier, so an otherwise valid implementation remains `review_required`.
 
 Profiles remain adapter-layer contracts. JudgmentKit may expose an optional component adapter downstream of the kernel, but a profile does not select it or turn it into kernel authority. Product vocabulary, product geometry, data, runtime state, authorization truth, and side effects stay with the implementing product.
 

README.md

@@ -38,11 +38,11 @@ JudgmentKit keeps the core deterministic and lets model assistance enter through
 2. Deterministic review packet: turns that evidence into a reviewable activity model candidate with guardrails.
 3. Model-assisted candidate review seam: accepts a model-proposed candidate through dependency injection or MCP and runs the same guardrails.
 4. Provider-neutral proposer adapter: builds a serializable activity-model request for an injected model caller and returns the proposed candidate to the review seam.
-5. Surface-type recommendation: classifies activity purpose as marketing, workbench, operator review, form flow, dashboard monitor, content/report, setup/debug tool, or conversation before workflow or frontend implementation guidance.
+5. Surface-type recommendation: classifies activity purpose as marketing, workbench, operator review, artifact inspector, form flow, dashboard monitor, content/report, setup/debug tool, or conversation before workflow or frontend implementation guidance.
 6. UI workflow candidate review seam: accepts a model- or agent-proposed workflow candidate and checks grounding, action support, handoff clarity, and disclosure containment before UI implementation.
 7. UI implementation contract gate: creates or accepts the repo authority for approved primitives, control semantics, required states, static checks, and browser QA.
 8. UI generation handoff gate: turns only ready workflow reviews plus an implementation contract into compact handoffs for the next UI generation pass.
-9. Frontend generation context adapter: combines a ready handoff, selected surface type, frontend context, and verification expectations, then applies supported presentation guidance such as the default Workbench operational profile without making styling or component inventory part of the kernel contract.
+9. Frontend generation context adapter: combines a ready handoff, selected surface type, frontend context, and verification expectations, then applies governed presentation guidance such as the supported default Workbench operational profile or the proposed Artifact Inspector profile contract without making styling or component inventory part of the kernel contract.
 10. Frontend implementation skill context: compiles repo-local frontend skill guidance into a gated MCP packet for agents that cannot read local skills directly, including the active `implementation_contract.design_system_source` for tokens, typography, icons, and component contracts.
 11. Optional provider adapters: provider configuration and network calls stay outside the kernel and feed proposed candidates back through the same review contract.
 
@@ -86,7 +86,9 @@ JudgmentKit also contains an unreleased optional React adapter candidate at `jud
 
 The Simple Design System (Community) file is JudgmentKit's component-and-variant reference denominator: 122 public families with 336 masters and six hidden families with 18 masters. Standalone icons and Simple Design System styling are excluded. JudgmentKit accounts for all 128 families and 354 masters, classifies every family, normalizes the 304 masters in documented variant sets across 105 semantic axes, and records the remaining 50 as singleton masters. Reference accounting, family disposition, variant semantics, runtime availability, and current evidence are reported separately.
 
-By default, `implementation_contract.design_system_source.mode` is `judgmentkit_default`: tokens, font roles, icon catalog policy, component contracts, the component implementation registry, and supported surface-presentation profiles come from JudgmentKit `/design-system/` exports. A sufficiently grounded or explicitly selected Workbench receives `judgmentkit.workbench.operational-v1` in frontend-generation context by default; `surface_profile: "none"` opts out without changing the Workbench interaction contract. If a complete `design_system_adapter` is supplied to `create_ui_implementation_contract`, the mode becomes `external_design_system` and that adapter owns tokens, typography, icons, and renderer components. Incomplete external adapters fail instead of falling back to JudgmentKit defaults, and neither JudgmentKit surface profiles nor the unreleased React adapter candidate cross that boundary implicitly.
+By default, `implementation_contract.design_system_source.mode` is `judgmentkit_default`: tokens, font roles, icon catalog policy, component contracts, the component implementation registry, and supported surface-presentation profiles come from JudgmentKit `/design-system/` exports. A sufficiently grounded or explicitly selected Workbench receives `judgmentkit.workbench.operational-v1` in frontend-generation context by default. A grounded Artifact Inspector receives `judgmentkit.artifact-inspector.v1`, which keeps one rendered artifact primary while applying JudgmentKit guidance only to declared chrome and overlay scopes. `surface_profile: "none"` opts out without changing either interaction contract. If a complete `design_system_adapter` is supplied to `create_ui_implementation_contract`, the mode becomes `external_design_system` and that adapter owns tokens, typography, icons, and renderer components. Incomplete external adapters fail instead of falling back to JudgmentKit defaults, and neither JudgmentKit surface profiles nor the unreleased React adapter candidate cross that boundary implicitly.
+
+Artifact Inspector uses an explicit mixed-authority contract: `inspector_chrome` and `inspection_overlay` are JudgmentKit-owned, while `primary_artifact` remains `external_not_reviewed`. Its profile component roles are semantic contract guidance, not implemented component-registry exports. This release has no trusted interactive-attestation producer or verifier; candidate-authored evidence and the existing static browser-composition runtime cannot satisfy the authority gate, so an otherwise valid implementation remains `review_required`.
 
 The default field-select composition contract is source-backed and documented in [`docs/select-field-composition.md`](https://github.com/mikeylong/judgmentkit/blob/main/docs/select-field-composition.md). It separates selected-value spacing, the reserved trailing indicator slot, and the indicator's placement inside that slot instead of treating a field's content padding as the chevron's physical edge inset.