← Qmap · c16
violation-view-prompt.md
Policy Violation View
I don't want to create a new dev experiment, let's create a plan for building our first considered view context. We'll do this with the c16 cycle extension : policy violation view
Create a view that learly shows a policy violation. For now, let's assume that a policy violation is a communication between two actors (a dataflow) that breaks a policy. Our view should:
- show the two actors in question
- show any relevant boundaries that have been crossed.
- perhaps we can start to correlate the type of views we're building with the types of boundaries and framing we want a particular view to have
- Show the flow–probably in red
- We may need to add attributes like color to flows. Currently I think they're always purple and dashed.