card trees as a top-level primitive

We’ve been pushing Jank toward a simpler idea:

the card tree should be the primary object.

Not the decklist. Not the thread. Not the diff.

The tree.

The core thought

A deck is not just a flat list of cards.

It usually has structure:

Most tools flatten all of that into one list and make you carry the real reasoning in your head, in a Discord thread, or in scattered notes.

A card tree keeps the structure attached to the cards.

Instead of treating a deck as one blob, Jank can treat it as:

That lets one object support multiple views:

The important idea is that these are all projections of the same underlying object.

This model gives us a few things a plain decklist doesn’t:

You don’t lose the difference between:

That context stays in the object.

Forum discussion stops being loosely attached to a pasted list.

Instead, the discussion can hang off the actual tree — or an existing thread can become the discussion home for that tree.

The question is no longer just:

It becomes:

That’s a much better fit for how people actually iterate on lists.

The current Jank slice already supports a lot of this direction:

It’s still early, but the shape is there now.

We’re interested in tools that preserve thought, not just output.

A decklist is output. A card tree is closer to the reasoning process that produced it.

That makes it a better primitive for brewing, discussing, revising, and comparing ideas over time.

There’s still plenty to improve:

But the underlying bet feels right:

forum as the default experience, card tree as the real object, and deck/diff as views over that object.

That’s the direction.