The missing room
Fabric already has places that are supposed to be clear. fabri.cc is the map to useful software, infrastructure and services. Fabric Portland is the agency. SiteLodge is hosting. Lynx, Squidly, Piper and Snipe each have a narrow job. That clarity is good — and it creates a problem for work that is not ready, willing or able to fit inside a narrow box.
fbc.ad can be the missing room: the public workshop. A place for experiments, games, prototypes, research questions and small oddities that deserve daylight before they deserve a sales funnel.
The rule: fbc.ad does not need to make unfinished work look finished. It needs to make the status and the question clear.
A lab is not a graveyard
The easiest version of a “projects” site is a grid of old cards. That is not the goal. Status is part of the content here. ACTIVE EXPERIMENT should mean something different from PLAYABLE, BETA, PROTOTYPE and GRADUATED.
A project that pauses can stay visible without pretending to be maintained. A project that becomes a product can keep its lab record and point people toward its new home. The archive becomes a family tree rather than a pile of abandoned landing pages.
Questions belong beside outputs
The other reason for fbc.ad is to keep the questions visible. Krill is not interesting only because it has an interface. It is interesting because it asks whether public participation and compute can be inspectable. Daybook is not interesting only because it stores writing. It asks whether software can become more helpful by asking for less.
That is why “What we’re wondering” is a first-class section, not a decorative slogan. It gives unfinished thinking a durable URL.
What happens next
The site should get richer slowly. A new experiment earns a project page. A project with sustained thinking earns its own blog. Cross-project questions and field notes live here. The goal is not to make the lab look bigger than it is. The goal is to make the real work easier to find, understand and follow.