Skip to content

feat(policy): return draft chunk ids from policy proposal submit #1094

Closed

Description

@zredlined

Description

Extend the sandbox-origin policy proposal submit response so callers receive the draft chunk IDs that were created or updated. This lets policy.local follow the exact proposal and read rejection guidance.

Context

Parent: #1062
RFC artifact: https://github.com/NVIDIA/OpenShell/blob/feat/agent-driven-policy-management/rfc/0001-agent-driven-policy-management.md

This is part of the locked Agent-Driven Policy Management MVP. GitHub issues are the development source of truth; Linear is only a roadmap pointer.

Today SubmitPolicyAnalysisResponse returns counts and rejection reasons only, while the gateway assigns UUIDs.

Definition of Done

  • Proto response includes returned chunk IDs for accepted/upserted proposals.
  • Gateway populates IDs for newly created and updated chunks.
  • policy.local proposal submit returns those IDs to the agent.
  • Existing callers remain source-compatible.
  • Tests cover server-assigned IDs and upserted existing chunks.

Activity

  1. added
    area:policyPolicy engine and policy lifecycle work
    area:gatewayGateway server and control-plane work
    on Apr 30, 2026
  2. changed the title [-]feat(policy): return draft chunk ids from policy analysis submit[/-] [+]feat(policy): return draft chunk ids from policy proposal submit[/+] on Apr 30, 2026
  3. added 6 commits that reference this issue on May 12, 2026
    55357df
    f2dfa8a
    7dd74f4
    899683a
    9883a70
    6c5c659
  4. added a commit that references this issue on May 14, 2026
    ea2fddb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:gatewayGateway server and control-plane workarea:policyPolicy engine and policy lifecycle workstate:agent-readyApproved for agent implementation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions