Skip to content

WallGuard runtime clean-room synthesis and release gate #14

Description

@mdheller

Parent: SocioProphet/sociosphere#443
Depends on: #13
Depends on: SocioProphet/sherlock-search#63
Depends on: SocioProphet/memory-mesh#36
Depends on: SocioProphet/policy-fabric#93

Purpose

Implement the Holmes runtime gate for WallGuard clean-room synthesis and release.

Holmes must not make final policy decisions locally. It must consume retrieval/memory context labels, Policy Fabric WallGuard decisions, and receipt-bearing release permissions before producing or exporting derived content.

Runtime objective

Gate these paths:

  • same-wall synthesis
  • redacted synthesis
  • quarantined synthesis
  • clean-room derived output generation
  • public/firm-approved release
  • artifact export handoff

Required behavior

  • Same-wall synthesis keeps output wall_restricted unless Policy Fabric permits clean-room release.
  • Clean-room release requires explicit clean_room_release_allowed decision.
  • Clean-room release excludes restricted payloads and preserves residual restrictions.
  • Cross-wall synthesis is denied unless routed through an explicit clean-room release path.
  • Missing wall context fails closed.
  • Derived artifacts carry receipt refs, source label preservation, and residual restrictions.

Suggested files

  • tools/wallguard_clean_room_gate.py
  • examples/wallguard-runtime/*.json
  • tools/validate_wallguard_clean_room_runtime.py
  • Makefile target validate-wallguard-clean-room-runtime

Acceptance criteria

  • Same-wall synthesis fixture produces wall-restricted output with residual restrictions.
  • Cross-wall synthesis fixture is denied before payload mixing.
  • Clean-room release fixture requires explicit Policy Fabric release decision.
  • Bad clean-room release fixture fails when restricted payload is not excluded.
  • Missing wall context fixture fails closed.
  • Output evidence is suitable for Core Ledger and Prophet Platform without restricted payload leakage.
  • No dependency on cascade, presidio, OrchestraOS, or noncanonical/unlicensed code.

Non-goals

  • Do not implement Policy Fabric evaluator here.
  • Do not implement retrieval or memory runtime gates here.
  • Do not implement product UI here.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions