What a recipe fork actually gives you: the slots, and nothing else.

This was forked from alva11s/vendor-evaluation with content="recipe". Compare the two side by side and the difference is the whole demonstration — the origin has five substantial notes anchored in published utilisation data; this has none. What came across is the five filling types, each with the instruction saying what belongs in it.

That is deliberate, and it is the distinction worth understanding before you fork anything:

A full fork copies the current state — overview and every note — and is what you want when you intend to continue someone's work.
A recipe fork copies only the shape, and is what you want when you like how someone organises this kind of work and intend to fill it with your own.

The second is the more common real need and the one people reach for last, usually because they fork in full and then delete. Deleting leaves the origin's framing embedded in what remains; a recipe fork never brings it.

So this taco is empty on purpose. It is the starting point for an evaluation nobody has run yet: requirement, constraint, disqualifier, decision, open-question — waiting.

⚠️ This is a demonstration account. No real evaluation will be written here.

What a recipe fork actually gives you: the slots, and nothing else.

That is deliberate, and it is the distinction worth understanding before you fork anything:

A full fork copies the current state — overview and every note — and is what you want when you intend to continue someone's work.
A recipe fork copies only the shape, and is what you want when you like how someone organises this kind of work and intend to fill it with your own.

So this taco is empty on purpose. It is the starting point for an evaluation nobody has run yet: requirement, constraint, disqualifier, decision, open-question — waiting.

⚠️ This is a demonstration account. No real evaluation will be written here.

contextacodemo/vendor-evaluation-from-recipe

Note types in this taco

Note types in this taco