Fog: add 400 reviewed formal nodes

research/fog-of-knowledge/NEMESIS.md

@@ -131,6 +131,10 @@ These neutral values must be proposed explicitly by the author: `status: reporte
 
 Unknown metadata remains explicit. If a candidate claims acceptance, chronology or frontier standing that its sources do not establish, the author must submit a new candidate revision with justified or neutral metadata. The compiler does not rewrite the captured source, summary or assertion scope to make a candidate pass. The complete revised representation still requires both independent review roles.
 
+#### Owner waiver: code-provenance public results (2026-10-18)
+
+`data/evidence-policy.json` (`owner_waivers`, id `code-provenance-frontier-public-results`) records the repository owner's approval on 2026-10-18 at 10:19 CT: the deterministic code provenance receipt (`code:nemesis-provenance/1`, role set `["provenance"]`) counts as review for frontier public-result nodes only. Such a node carries `frontier: true`, `status: frontier`, `era: frontier` and `public_frontier` with category `public-result`, `capability_status: publicly-described`, `disclosed_at` set to the exact publication date stated in the retained source, and `source_ids` naming that retained source. Its summary attributes the paper and quotes the finding sentence verbatim from the retained abstract; its sources include the DOI or arXiv link, and the retained record's licence must permit reuse (CC BY or CC0/public domain). The waiver also covers that node's `related` or `refines` edges to existing same-family concepts, each with its own exact abstract span naming the concept, and `narrower` placements only where the abstract itself classifies the result as a kind of the parent. Direct children per parent stay well below 150. No semantic model review is claimed for these records, and the frontier/era values are a recency placement, not a claim of acceptance, priority or current leadership. Open questions and company-tool records keep their existing rules.
+
 ### edges.jsonl
 
 One relationship per line.

research/fog-of-knowledge/SCIENTIFIC_COMPILER.md

@@ -117,3 +117,7 @@ The tab separates recorded open questions from evidence-reviewed public disclosu
 ```
 
 Categories are `open-question`, `public-result`, or `company-tool`; disclosure status is `publicly-described` or `undisclosed`. A disclosed date must be an exact ISO calendar date or null. Metadata sources must be canonical citations and exact assertion support. A company/tool assertion and each capability require public-source support and both review roles. A date is not proof of current world leadership. Undisclosed private capabilities are never inferred. Legacy frontier questions remain visibly unreviewed; no commercial disclosures have been fabricated to populate the tab.
+
+### Owner waiver: code-provenance public results (2026-10-18)
+
+`data/evidence-policy.json` (`owner_waivers`, id `code-provenance-frontier-public-results`) records the repository owner's approval on 2026-10-18 at 10:19 CT: the deterministic code provenance receipt (`code:nemesis-provenance/1`, role set `["provenance"]`) counts as review for frontier public-result nodes only. Such a node carries `frontier: true`, `status: frontier`, `era: frontier` and `public_frontier` with category `public-result`, `capability_status: publicly-described`, `disclosed_at` set to the exact publication date stated in the retained source, and `source_ids` naming that retained source. Its summary attributes the paper and quotes the finding sentence verbatim from the retained abstract; its sources include the DOI or arXiv link, and the retained record's licence must permit reuse (CC BY or CC0/public domain). The waiver also covers that node's `related` or `refines` edges to existing same-family concepts, each with its own exact abstract span naming the concept, and `narrower` placements only where the abstract itself classifies the result as a kind of the parent. Direct children per parent stay well below 150. No semantic model review is claimed for these records, and the frontier/era values are a recency placement, not a claim of acceptance, priority or current leadership. Open questions and company-tool records keep their existing rules.

research/fog-of-knowledge/app.js

@@ -1294,7 +1294,7 @@ function drawCurrentChildren(parent,center){
   if(!all.length&&token.kind==="node"){
     const node=nodeById.get(token.id);
     const p=polar(center.x,center.y,token.r+DEPTH_GAP,token.angle);
-    drawFrontierMarker(parent,p,node?.frontier?"RECORDED OPEN QUESTION":"UNMAPPED NEXT LAYER");
+    drawFrontierMarker(parent,p,node?.public_frontier?.category==="public-result"?"RECENT PUBLIC RESULT":node?.frontier?"RECORDED OPEN QUESTION":"UNMAPPED NEXT LAYER");
   }
 }
 function drawKnowledgeNode(parent,node,p,token,isCurrent,role,onClick,relation=""){
@@ -1368,7 +1368,7 @@ function drawFrontierMarker(parent,p,label){
   g.append(mk("path",{d:"M -70 8 Q -36 -18 0 3 Q 34 25 72 -7",class:"fogWisp"}));
   g.append(mk("path",{d:"M -62 26 Q -25 4 12 24 Q 42 38 68 19",class:"fogWisp secondary"}));
   g.append(textNode(0,-4,label,"frontierTitle"));
-  g.append(textNode(0,14,label==="RECORDED OPEN QUESTION"?"Recorded open question":"Nemesis can map what comes next","frontierSub"));
+  g.append(textNode(0,14,label==="RECORDED OPEN QUESTION"?"Recorded open question":label==="RECENT PUBLIC RESULT"?"Recorded public result":"Nemesis can map what comes next","frontierSub"));
   parent.append(g);
 }