Skip to content

feat(#560): WallGuard Professional Workroom runtime product-state contract#655

Open
mdheller wants to merge 1 commit into
mainfrom
feat/issue-560-wallguard-workroom-runtime
Open

feat(#560): WallGuard Professional Workroom runtime product-state contract#655
mdheller wants to merge 1 commit into
mainfrom
feat/issue-560-wallguard-workroom-runtime

Conversation

@mdheller

Copy link
Copy Markdown
Member

Summary

Implements the WallGuard Professional Workroom runtime product-state contract for issue #560.

New files:

  • contracts/wallguard/professional-workroom-runtime-state.v0.1.json — runtime state fixture: wall_state, policy_version, participants with acknowledgment_state, 3 blocked attempts (retrieval/writeback/collaboration) with safe reason summaries, clean-room release request referencing Policy Fabric + Holmes + Core Ledger evidence
  • contracts/wallguard/reject.missing-wall-context.json — null wall_ref fails closed
  • contracts/wallguard/reject.restricted-payload-in-state.json — blocked attempt with restricted_payload_embedded=true is rejected
  • contracts/wallguard/reject.policy-authority-claimed.json — runtime_enforcement_implemented=true is rejected
  • tools/validate_wallguard_professional_workroom_runtime.py — full validator with policy gates

Policy gates enforced:

  • Fail closed when wall_ref is null/absent
  • Reject any blocked attempt where restricted_payload_embedded=true
  • Reject when runtime_enforcement_implemented=true
  • Clean-room release request must reference policy_decision_ref, holmes_evidence_ref, and core_ledger_evidence_ref
  • Non-claims must be non-empty

Makefile: validate-wallguard-professional-workroom-runtime wired into .PHONY and validate: aggregate.

Result: 1 valid + 3 reject, 4/4 pass.

Closes #560

Test plan

  • make validate-wallguard-professional-workroom-runtime passes 4/4
  • CI green

…tract

- Runtime-state fixture: wall_state, policy_version, participants with
  acknowledgment_state, blocked_attempts (cross_wall_retrieval/writeback/
  collaboration) with safe reason summaries, clean_room_release_request
  referencing Policy Fabric + Holmes + Core Ledger evidence
- Policy gates: fail closed on null/missing wall_ref; reject any blocked
  attempt with restricted_payload_embedded=true; reject when
  runtime_enforcement_implemented=true; enforce clean-room release evidence
  completeness
- 3 reject fixtures: missing-wall-context, restricted-payload-in-state,
  policy-authority-claimed
- Makefile target validate-wallguard-professional-workroom-runtime wired
  into .PHONY and validate: aggregate

Closes #560
from __future__ import annotations

import json
import sys
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.

WallGuard runtime Professional Workroom API and product state

1 participant