[{"data":1,"prerenderedAt":285},["ShallowReactive",2],{"cycle-doc-design-c147-peterson.md":3},{"cycle":4,"project":7,"path":10,"title":11,"toc":12,"ast":16},{"id":5,"title":6},"c147","Findings, a Common Tongue",{"id":8,"label":9},"design","Design","peterson.md","c147: for the Mark Peterson conversation",[13,14,15],"What changed since the session","What to show him","Questions only he can answer",{"type":17,"children":18},"root",[19,57,63,75,80,141,146,163],{"type":20,"tag":21,"props":22,"children":23},"element","p",{},[24,31,33,38,40,47,49,55],{"type":20,"tag":25,"props":26,"children":27},"strong",{},[28],{"type":29,"value":30},"text","Written:",{"type":29,"value":32}," 2026-11-13, in Phase 4. ",{"type":20,"tag":25,"props":34,"children":35},{},[36],{"type":29,"value":37},"For:",{"type":29,"value":39}," Mark, to take to Mark Peterson before review stop 3 (the to-do from the 2026-11-12 Product session ",{"type":20,"tag":41,"props":42,"children":44},"code",{"className":43},[],[45],{"type":29,"value":46},"f8d58bc9",{"type":29,"value":48},": \"Discuss the remediation and inbox direction with Mark Peterson\"). His answers come back as rulings in ",{"type":20,"tag":41,"props":50,"children":52},{"className":51},[],[53],{"type":29,"value":54},"review-3.md",{"type":29,"value":56},".",{"type":20,"tag":58,"props":59,"children":61},"h2",{"id":60},"what-changed-since-the-session",[62],{"type":29,"value":13},{"type":20,"tag":21,"props":64,"children":65},{},[66,68,73],{"type":29,"value":67},"The inbox is gone. On the person's machine, ",{"type":20,"tag":25,"props":69,"children":70},{},[71],{"type":29,"value":72},"Safety & Security → Findings",{"type":29,"value":74}," shows the same findings the security team sees, in the person's words: open ones first, prevented ones as one quiet line per thing, and what HQ asked. A finding is one record on both sides; the machine raises it, the person adds notes to it (ask IT, ask for access, \"this was a mistake\", acknowledge), and the plane resolves it. Gene's story is a finding's history: detected, a training suggested, the training finished, resolved.",{"type":20,"tag":58,"props":76,"children":78},{"id":77},"what-to-show-him",[79],{"type":29,"value":14},{"type":20,"tag":81,"props":82,"children":83},"ul",{},[84,119,130],{"type":20,"tag":85,"props":86,"children":87},"li",{},[88,90,97,99,105,106,112,113],{"type":29,"value":89},"Priya's machine, the person's view: ",{"type":20,"tag":91,"props":92,"children":94},"a",{"href":93},"\u002Fpages\u002Fnative\u002Fsafety?world=pilot",[95],{"type":29,"value":96},"Findings",{"type":29,"value":98}," · ",{"type":20,"tag":91,"props":100,"children":102},{"href":101},"\u002Fpages\u002Fnative\u002Fsafety-finding?world=pilot&findingId=F-b59d4b8618",[103],{"type":29,"value":104},"Dana's follow-up",{"type":29,"value":98},{"type":20,"tag":91,"props":107,"children":109},{"href":108},"\u002Fpages\u002Fnative\u002Fsafety-finding?world=pilot&findingId=F-698b534b89",[110],{"type":29,"value":111},"a prevented finding",{"type":29,"value":98},{"type":20,"tag":91,"props":114,"children":116},{"href":115},"\u002Fpages\u002Fnative\u002Fsafety-settings?world=pilot",[117],{"type":29,"value":118},"Settings",{"type":20,"tag":85,"props":120,"children":121},{},[122,124],{"type":29,"value":123},"The security team's view of the same record: ",{"type":20,"tag":91,"props":125,"children":127},{"href":126},"\u002Fpages\u002Fphase4\u002Fmock\u002Ffindings-design?status=open,resolved",[128],{"type":29,"value":129},"Findings (S2)",{"type":20,"tag":85,"props":131,"children":132},{},[133,135],{"type":29,"value":134},"The shape in one picture: ",{"type":20,"tag":91,"props":136,"children":138},{"href":137},"\u002Fcycles\u002Fdesign\u002Fsketches\u002Fc147-common-tongue",[139],{"type":29,"value":140},"The common tongue",{"type":20,"tag":58,"props":142,"children":144},{"id":143},"questions-only-he-can-answer",[145],{"type":29,"value":15},{"type":20,"tag":21,"props":147,"children":148},{},[149],{"type":20,"tag":150,"props":151,"children":152},"em",{},[153,155,161],{"type":29,"value":154},"Mark ruled 3 and 7 himself at review stop 3 (2026-11-13): a finished training closes its finding by the policy, and ",{"type":20,"tag":41,"props":156,"children":158},{"className":157},[],[159],{"type":29,"value":160},"chatgpt.com",{"type":29,"value":162}," is a different provider. They stay below as his rulings to confirm, not open questions.",{"type":20,"tag":164,"props":165,"children":166},"ol",{},[167,177,187,204,214,224,234,265,275],{"type":20,"tag":85,"props":168,"children":169},{},[170,175],{"type":20,"tag":25,"props":171,"children":172},{},[173],{"type":29,"value":174},"A prevented finding, for an auditor.",{"type":29,"value":176}," We record it as resolved the moment it's detected (\"Resolved: prevented\") and count it as the policy working. Is that what an auditor wants to see, or does a blocked attempt need its own review?",{"type":20,"tag":85,"props":178,"children":179},{},[180,185],{"type":20,"tag":25,"props":181,"children":182},{},[183],{"type":29,"value":184},"\"It does not count against you.\"",{"type":29,"value":186}," The person's view says so for prevented findings. Can a company keep that promise in its reports, or will someone always want a per-person count?",{"type":20,"tag":85,"props":188,"children":189},{},[190,195,197,202],{"type":20,"tag":25,"props":191,"children":192},{},[193],{"type":29,"value":194},"Closing a finding on a training",{"type":29,"value":196}," ",{"type":20,"tag":150,"props":198,"children":199},{},[200],{"type":29,"value":201},"(Mark ruled: the policy closes it; HQ can reopen. Confirm it holds for an auditor.)",{"type":29,"value":203}," When a person finishes the training a policy assigned, should the policy close the finding by itself, or does a person at HQ always close it? (Open call 5 from review stop 1.)",{"type":20,"tag":85,"props":205,"children":206},{},[207,212],{"type":20,"tag":25,"props":208,"children":209},{},[210],{"type":29,"value":211},"\"This was a mistake.\"",{"type":29,"value":213}," The person can say a finding is wrong; the plane resolves it as a false positive, or doesn't. Who reads those, and how quickly should they be answered?",{"type":20,"tag":85,"props":215,"children":216},{},[217,222],{"type":20,"tag":25,"props":218,"children":219},{},[220],{"type":29,"value":221},"How gentle HQ's words can be.",{"type":29,"value":223}," HQ's follow-ups are shown exactly as written, and the send form only suggests a gentler sentence. Is that enough, or should a follow-up always come with a reason the person can read?",{"type":20,"tag":85,"props":225,"children":226},{},[227,232],{"type":20,"tag":25,"props":228,"children":229},{},[230],{"type":29,"value":231},"The noise default per team.",{"type":29,"value":233}," The company sets how much qcontrol says, per team (Engineering on Teach me, Finance on Quietly). Who in a company sets that: security, IT, or each team's lead?",{"type":20,"tag":85,"props":235,"children":236},{},[237,242,243,248,250,255,257,263],{"type":20,"tag":25,"props":238,"children":239},{},[240],{"type":29,"value":241},"The provider list",{"type":29,"value":196},{"type":20,"tag":150,"props":244,"children":245},{},[246],{"type":29,"value":247},"(Mark ruled: a different provider. Confirm.)",{"type":29,"value":249}," Priya's Codex CLI talks to ",{"type":20,"tag":41,"props":251,"children":253},{"className":252},[],[254],{"type":29,"value":160},{"type":29,"value":256}," while the list approves ",{"type":20,"tag":41,"props":258,"children":260},{"className":259},[],[261],{"type":29,"value":262},"openai.com",{"type":29,"value":264},". Is a ChatGPT sign-in the same provider for a policy, or a different one?",{"type":20,"tag":85,"props":266,"children":267},{},[268,273],{"type":20,"tag":25,"props":269,"children":270},{},[271],{"type":29,"value":272},"A real allow list.",{"type":29,"value":274}," We added the harnesses' read-only tools (Grep, Glob, WebFetch) so ordinary search stops raising findings; Edit and TodoWrite still do. What does a real company's tool list look like on day one?",{"type":20,"tag":85,"props":276,"children":277},{},[278,283],{"type":20,"tag":25,"props":279,"children":280},{},[281],{"type":29,"value":282},"The audit line.",{"type":29,"value":284}," Is \"something went wrong, and it was corrected\" (the finding's history, read top to bottom) still all an auditor needs, now that it lives on the finding instead of in a message thread?",1794599393202]