FGO
Futures
For Indie Designers
Derived from an open pattern
CC0 pattern
No catalog, no protected library. Just a set of pattern instructions released into the commons. A weave structure, a cut system, maybe parametric rules for sizing or drape. Published as CC0. Not as a “drop,” not as IP. Just placed into the substrate.
That act does one thing: it removes negotiation from the start of the pipeline. Anyone—another designer, a small workshop, a digital fabrication lab—can pick it up and begin. No licensing step, no permission loop. The pattern becomes a starting state, not a finished product.
From there, the pipeline splits immediately into two tracks: open design evolution and localized realization.
On the open side, others fork the pattern. Adjust tension ratios. Change panel geometry. Translate it into knit instead of weave. Feed it into simulation tools. Train small models on variations of it. None of these forks need to reference the original in a legal sense, but they often will in a social or cryptographic sense—signatures, hashes, lineage markers. Not required, but useful.
This creates a living graph of design evolution. No central authority, no canonical version. Just branches that gain or lose attention. On the realization side, a workshop decides to produce a run. Now the problem is no longer “who owns the design,” but “how do we execute it in material.”
They choose:
- fiber (cotton, wool, synthetics, blends)
- source (local, recycled, imported)
- loom type (manual, semi-automatic, CNC)
- finishing process (dye, wash, treatment)
These decisions are not encoded in the CC0 pattern. They are context. This is where differentiation actually happens.
At this point, a digital thread starts forming alongside the physical process.
global designer network
this is this object, with this path
derived from an open pattern, shaped by local decisions, carrying its own cryptographic identity. Now, instead of “this is my design,” the claim becomes: “this is this object, with this path.”
Looms in rows
The workshop can sell the garment directly. Buyers are not purchasing exclusivity over the pattern. They’re acquiring: the physical object, its provenance, its relation to a broader design graph, optional access to future interactions tied to it.
custom modifications
A token or key associated with the garment doesn’t need to represent ownership of the design. It can represent: membership in a maker’s network, access to future runs or variations, entry into private coordination spaces, the ability to request custom modifications.
Design iteration
Now bring in compute. Design iteration can happen through simulation, generative tools, or small models trained on CC0 pattern spaces. Because the base layer is open, these tools don’t need to negotiate data access. They operate entirely within the commons domain.
model operates on CC0 pattern
adjusting fit, uploading body measurements, experimenting with personal variations—that input is private. It belongs to a different domain. So the system must enforce: model operates on CC0 patterns → fine, user-specific adjustments remain local or confidential, no silent absorption of those adjustments into global training state
Openly remixable design graph
layer of the
The output can be a new pattern instance, optionally released into the commons, or kept private for personal production. That transition—private → public—is explicit. Not automatic.
Production doesn’t have to be centralized. Small CNC looms, automated cutters, distributed fabrication labs can take pattern instructions and produce locally. The same CC0 pattern can be instantiated in different places with different materials.
Coordination happens through:
- shared pattern graphs
- reputation signals from prior runs
- verifiable traces of production quality
No need for a central brand to orchestrate everything. The network itself routes demand:
- a designer publishes a pattern
- a workshop produces a high-quality run that run gains attention
- others either buy from that workshop or produce their own variation
The system doesn’t collapse into a single supplier unless one outperforms all others consistently. Now, confidentiality re-enters at the interaction layer. A wearer might use the garment to access services:
- private communities
- custom fitting systems
- repair or modification networks
Those interactions should not feed back into the commons or into global logs. The garment proves eligibility (possession, authenticity, membership) without exposing full identity or behavioral history. So: CC0 pattern → fully open, garment identity → specific, traceable, wearer interaction → bounded, non-propagating
No leakage between them unless explicitly chosen. This also changes how trends form. Instead of top-down releases, you get: base patterns circulating clusters of variations forming around certain, aesthetics or techniques, workshops specializing in particular instantiations, communities forming around those clusters.
Indie designers don’t need to defend a fixed “collection.” They operate more like nodes in a graph:
- publish patterns
- fork others
- collaborate implicitly through shared substrate build reputation through realized outputs and relationships
Over time, you get a stack that looks like this:
- commons layer: CC0 patterns, openly remixable design graph: evolving lineage of variations
- production layer: distributed workshops instantiating patterns
- identity layer: cryptographic traces attached to objects
- interaction layer: confidential, context-bound use by wearers