[{"data":1,"prerenderedAt":65},["ShallowReactive",2],{"cycle-doc-qmap-c16-violation-view-prompt.md":3},{"cycle":4,"project":7,"path":10,"title":11,"toc":12,"ast":13},{"id":5,"title":6},"c16","View Contexts",{"id":8,"label":9},"qmap","Qmap","violation-view-prompt.md","Policy Violation View",[],{"type":14,"children":15},"root",[16,24,29],{"type":17,"tag":18,"props":19,"children":20},"element","p",{},[21],{"type":22,"value":23},"text","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",{"type":17,"tag":18,"props":25,"children":26},{},[27],{"type":22,"value":28},"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.\nOur view should:",{"type":17,"tag":30,"props":31,"children":32},"ul",{},[33,39,52],{"type":17,"tag":34,"props":35,"children":36},"li",{},[37],{"type":22,"value":38},"show the two actors in question",{"type":17,"tag":34,"props":40,"children":41},{},[42,44],{"type":22,"value":43},"show any relevant boundaries that have been crossed.\n",{"type":17,"tag":30,"props":45,"children":46},{},[47],{"type":17,"tag":34,"props":48,"children":49},{},[50],{"type":22,"value":51},"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",{"type":17,"tag":34,"props":53,"children":54},{},[55,57],{"type":22,"value":56},"Show the flow–probably in red\n",{"type":17,"tag":30,"props":58,"children":59},{},[60],{"type":17,"tag":34,"props":61,"children":62},{},[63],{"type":22,"value":64},"We may need to add attributes like color to flows. Currently I think they're always purple and dashed.",1794599378825]