You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(policy): add proposal provenance, operations, and guidance fields to proto #1096
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.
The MVP keeps summary/status fields string-typed where possible, but proposal operations should reuse the existing PolicyMergeOperation shape behind incremental policy updates.
Definition of Done
PolicyChunk includes source, intent_summary, human_summary, and validation_result.
PolicyChunk can carry agent-authored PolicyMergeOperation operations for approval-time merge.
RejectDraftChunkRequest includes optional guidance.
Generated Rust/Python bindings compile.
Existing clients continue to work when fields are empty.
Proto comments make clear that intent_summary is agent-supplied and not independently verified.
changed the title [-]feat(policy): add proposal provenance and guidance fields to proto[/-][+]feat(policy): add proposal provenance, operations, and guidance fields to proto[/+]on Apr 30, 2026
Activity
[-]feat(policy): add proposal provenance and guidance fields to proto[/-][+]feat(policy): add proposal provenance, operations, and guidance fields to proto[/+]feat(policy): plumb chunk_ids and rejection_reason through proposal p…
feat(policy): plumb chunk_ids and rejection_reason through proposal p…
feat(policy): plumb chunk_ids and rejection_reason through proposal p…
feat(policy): agent-driven policy management — the agent half (NVIDIA…