Visible credit
A Spark Code and future Contribution Trail make it easier to show who started, added, forked, and helped.
Contributor Benefit
Crooked Stack is not only about IP risk. It is also a place where early ideas and small contributions can become visible, credited, and easier to carry into real Builds.
Contribution is not all automatically free, and it is not all automatically revenue-sharing. Light help should get credit. Adopted work may get rewards. Commercial use of core contributions needs a separate agreement.
A Spark Code and future Contribution Trail make it easier to show who started, added, forked, and helped.
Repeated useful Bricks can become part of a future Carpenter Profile.
Good Bricks help contributors find builders, designers, writers, operators, and curious people nearby.
Adopted Bricks may lead to tips, bounties, paid invitations, or a role in a Build Team.
If a Spark moves toward commercial use, a Build Agreement can clarify roles, attribution, compensation, revenue share, equity, or licensing.
Credit. A light suggestion, reference, name, question, or small improvement is recorded with attribution.
Credit + possible reward. If a Brick is visibly adopted into a Spark, Fork, or Build direction, it may receive a tip, bounty, invitation, or other reward.
Separate agreement. Commercial use of a core contribution should clarify usage, attribution, compensation, or licensing before use.
Compensation / revenue share / equity by agreement. People materially building the project should define roles, ownership, payment, and upside in a Build Agreement.