Skip to content

feat(#579): org security postures + provenance-labelled inbound scree… - #681

Open
sneumannb5 wants to merge 2 commits into
byte5ai:mainfrom
sneumannb5:feat/579-org-security
Open

feat(#579): org security postures + provenance-labelled inbound scree…#681
sneumannb5 wants to merge 2 commits into
byte5ai:mainfrom
sneumannb5:feat/579-org-security

Conversation

@sneumannb5

@sneumannb5 sneumannb5 commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

What

Org security postures (#579): two-axis model (dangerous/auto/strict) with tighten-only org floor + provenance-labelled inbound screening (LLM judge or HTTP proxy) before the turn runs.

Why

Adds the ingress mirror to Privacy Shield: injection-screening tier + org-wide posture scopes can only tighten. Quarantine on enforce, fail-open-with-evidence when unscreenable, shadow mode to observe.

Test plan

  • typecheck @omadia/channel-sdk + @omadia/orchestrator — clean
  • securityPosture*.test.ts — 47/47; verifier suites — 126/126
  • core-decoupling ratchet held at 3294
  • full middleware suite after main merge

Risk / blast radius

  • New setup fields security_posture{,scope}, security_screen{mode,url} (defaults auto/enforce). No schema/migration.
  • Gate at every turn ingress; verifier re-runs exempt (screen once per user turn).
  • Limitation: attachment screening is descriptor-only until mid-turn body extraction lands — auto reachable but weak.

Naming-decisions still pending

  • Tool-approvals axis deferred — strict falls back to auto-screening; flip when approvals ship.

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

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