> For the complete documentation index, see [llms.txt](https://token-engineering-commons.gitbook.io/tec-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://token-engineering-commons.gitbook.io/tec-handbook/hatch-101/faq/legal.md).

# Legal

\-          What is the difference between Commons Stack and the Token Engineering Commons?

Commons Stack is developing an open-source design framework for creating Commons. Commons are economies that reward value creation where business models fail to so. The Commons Stack is responsible for building out the baseline technical and cultural processes associated with Hatching a Commons.&#x20;

The Token Engineering community is utilizing this product in order to launch the Token Engineering Commons (TEC).  The TE community is the first of hopefully many communities that will partner with Common Stack to launch their Commons.

\-          What are the legal implications of joining the Trusted Seed within my specific country?

The legal structure of the Trusted Seed is designed for the most litigious legal environments (for example, within the United States -- where communities like this can be easily seen as general partnerships with heavy legal liability for individuals). The TEC is using it to protect its Hatchers from legal situations that could arise from normal good faith actions within the Hatch process of our Commons.  That being said, it is always a good idea to keep an eye out for regulatory changes within your local and national jurisdictions.

\-          Do I have to report to anyone in my country that I am a member of this association?

No.  The legal structure proposed allows the membership to be treated in a similar manner as a membership at your local gym.  There should be no reporting requirements for anyone.  With that being said, it is always a good idea to keep an eye out for regulatory changes within your local and national jurisdictions.

\-          Does information exist about what actions are covered by the legal protection of the Swiss Association? Is it clear where I have breached the Terms & Conditions?

The rules are located in our Terms & Conditions that members must agree to when applying to the Swiss Association. You should act in good faith and not perform any illegal actions. You always act as an individual in the jurisdiction in which you live.

\-          Is there a list of what will be covered by the Legal protections?

There is not a defined list, but good faith participation in approved DAOs will generally be covered.

\-          Are there any resources available that could help me understand relevant legal issues?

Here is a summary of our legal strategy:

<https://forum.tecommons.org/t/tec-legal-strategy-proposal-vote/193>

The Statutes:

&#x20;<https://ipfs.web3.party/ipfs/QmcGNi9dcVgLJGtxJzjU2CyrrmVKkLnNPEK8JJC2a98zC5>

And the Terms, which is the one that is most interesting to read:

&#x20;<https://ipfs.web3.party/ipfs/QmYDmtmDYUPR6wjukzaNytibeNnYs41s2co4tNzkUYdd5n&#x20>;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://token-engineering-commons.gitbook.io/tec-handbook/hatch-101/faq/legal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
