How a ContextPack Is Built

How a ContextPack Is Built A workflow diagram generated by Archify. 01 / Bounded walk 02 / Rank and clip 03 / Emit Markdown EX / Flood risk Walk Rank Emit Entry concept · the question you asked · Bounded walk › Walk · always first Entry concept the question you asked always first Outbound BFS · follows links out only · Bounded walk › Walk · hop cap 2 Outbound BFS follows links out only hop cap 2 Neighborhood · every reachable node · Bounded walk › Walk Neighborhood every reachable node Inclusion rank · root, verified, high-impact, title · Rank and clip › Rank Inclusion rank root, verified, high-impact, title Included set · ranked survivors · Rank and clip › Rank · node cap 20 Included set ranked survivors node cap 20 Read order · root, high-impact, verified, title · Emit Markdown › Emit · different key Read order root, high-impact, verified, title different key --undirected · walks hub catalogs too · Flood risk › Walk · prefer impact --undirected walks hub catalogs too prefer impact Excluded list · named, not guessed · Flood risk › Rank · ask by name Excluded list named, not guessed ask by name top 20 outbound edges optional flag overflow, still ranked reorder for the model start here rank the neighborhood Legend User UI Agent logic Policy Context / trace External system

Why outbound only

  • • A Catalog links to every child, so it is a hub
  • • Outbound from a concept stays inside one theme

Trust before title

  • • The entry concept is always first and always included
  • • Verified concepts outrank drafts

Two orders, two jobs

  • • Inclusion ranking decides who makes the cut
  • • Read order decides what the model sees first