PKC Typed Edges: From Evidence to Release

PKC Typed Edges: From Evidence to Release A data-flow diagram generated by Archify. 01 / Evidence 02 / Judgment 03 / Exposure 04 / Product 05 / Outcome Discovery · competitor scan · 01 / Evidence Discovery competitor scan Experiment · JWT vs cookie · 01 / Evidence Experiment JWT vs cookie DecisionRecord · use JWT · 02 / Judgment · ADR DecisionRecord use JWT ADR Assumption · short TTL is OK · 02 / Judgment Assumption short TTL is OK Risk · token replay · 03 / Exposure Risk token replay Feature · user auth · 04 / Product · hub concept Feature user auth hub concept Acceptance · expires in 15 min · 05 / Outcome Acceptance expires in 15 min Design · auth middleware · 05 / Outcome Design auth middleware Release · v0.1.0 · 05 / Outcome Release v0.1.0 informs evidence validates evidence mitigates never reversed decides governs assumes weaker than an ADR exposes threat verified_by criterion designed_by shape lands_in ships Legend primary data policy / PII data store data flow

Two edge forms, one graph

  • • A body Markdown link is the universal edge every human can read
  • • links[].rel in frontmatter types that same target

Direction is a claim

  • • Decision mitigates Risk, and a Risk never mitigates anything
  • • The capture script writes the mitigates edge on the decision, not the risk

Inbound edges still reach you

  • • pack() reads inbound edges as well as outbound
  • • A concept pointing at a Feature is reachable from that Feature's pack