Not a repository list. An appraisal walkthrough. Each house is one repository, and every feature you can see is a fact the engine committed: stars set the footprint and the storeys, forks become the outbuildings somebody else built from your blueprint, and the transferability band becomes the fence at the front of the lot. The same repository draws the identical house every time — geometry is seeded from its name, never from chance.
Nine signals, nine architectural decisions. Every element in the drawing carries a
data-fact-id pointing at the
committed leaf it was derived from — so a claim about a house can always be traced back to the byte
that justified it, and never to a guess.
data-uncommitted="created_at" instead of a
data-fact-id. Everything else on the page is anchored to a Merkle leaf.The transferability band is the one signal a buyer cares about most and a star count never answers: can this asset actually change hands? It is reported as a band with named blockers, never as a single blended number.
| Band | Fence | Properties | Share | Meaning |
|---|
A repository list is something you can already read on GitHub. What you cannot read there is proportion: which assets are actually large, which are maintained, which are encumbered, and how much of a portfolio is one or two properties. A street answers that in a glance, and every glance is falsifiable — the drawing is a function of the committed fact set and nothing else.