Crooked Stack木匠盖歪楼

FAQ

Clear records, honest boundaries.

Crooked Stack is an open idea workshop. It keeps source records and Contribution Trails, but its real value is organizing a contribution economy around early-stage ideas.

Can Crooked Stack prevent someone from taking my idea?

No platform can honestly guarantee that a public idea will never inspire someone else or be independently developed outside the platform. Crooked Stack is not an idea vault.

What we provide is traceability: Spark Codes, timestamps, creator records, Contribution Trails, Fork records, and Build history. Within the Crooked Stack ecosystem, Forks must preserve attribution, and commercial use of specific recorded contributions should require separate agreement.

If your idea is a trade secret, confidential business concept, or unprotected patentable invention, do not submit it publicly.

How can contributors benefit?

Contributors can benefit through credit, creative portfolio value, tips, bounties, paid sprint invitations, brand challenges, Build Team invitations, and project roles.

If a Build becomes commercial, Core Bricks used commercially and Build Team participation should clarify compensation, revenue share, equity, licensing, or paid roles through a separate Build Agreement.

Does every Brick get revenue share?

No. A light suggestion may receive credit or appreciation, but it does not automatically become a commercial right.

A Light Brick receives credit. An Adopted Brick may receive credit plus a possible reward. A Core Brick used commercially should trigger a separate agreement. Build Team participation should be governed by agreement.

What if someone earns money from a similar idea?

If someone sees a public Spark and independently builds a similar direction outside the platform, Crooked Stack cannot realistically prevent that. Abstract ideas are hard to exclusively own.

But if a project is built inside the Crooked Stack ecosystem, uses adopted Bricks, uses specific contributor expressions, or enters the platform's Build workflow, then it must respect attribution and Build Agreement rules.

Why would people share ideas here?

Because many Sparks are not protected commercial secrets. They are half-formed ideas that might otherwise stay buried in someone's notes.

Crooked Stack helps users get visibility, Bricks, collaborators, attribution, and a path toward real-world Builds. The value is not absolute theft prevention. The value is being seen, being helped, being recorded, and being able to move forward.

Is this like GitHub for ideas?

Crooked Stack borrows the contribution logic of open-source communities, but adapts it for creative ideas.

Ideas are not code. So we need more than Forks. We need attribution, sharing modes, contribution trails, and commercialization boundaries.

What is Crooked Stack's IP?

Crooked Stack does not claim ownership over users' raw ideas. The platform's defensible value is the contribution economy around early-stage ideas: the brand, community trust, contribution graph, source records, Fork history, Build workflow, future Carpenter Profiles, reward systems, Build Agreements, and Verified Builds.

Sharing Modes

Public Spark

Publicly visible and open for community Bricks, Forks, and discussion with attribution.

Protected Spark

Future feature. Only a short public summary is visible. Full details are shared by request or invitation.

Private Spark

Future feature. Visible only to invited collaborators. May require NDA or platform-mediated agreement.

Crooked Stack currently supports Public Sparks only. Protected Spark and Private Spark are planned future features for sensitive or commercially promising projects.

Contribution Levels

Contributions are not all automatically free, and they are not all automatically revenue-sharing. The level depends on how the Brick is used.

Light Brick

Credit. A light suggestion, reference, name, question, or small improvement is recorded with attribution.

Adopted Brick

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.

Core Brick used commercially

Separate agreement. If a core contribution is used in a commercial Build, usage, attribution, compensation, or licensing should be clarified before commercial use.

Build Team

Compensation / revenue share / equity by agreement. People materially building the project should define roles, ownership, payment, and upside in a Build Agreement.