TT7-03 · CREATORS · INCLUSION · DISTRIBUTION
Get listed without giving anything up.
The creator inclusion & distribution policy: a four-tier ladder that always starts at "a card and a link" — no fees, no exclusivity, no code to write, and a withdrawal that is one sentence and always faster than joining.
LAST UPDATED 2026-09-21 · DRAFT · NOT YET IN FORCE
Website terms (TT7-01) and the privacy notice (TT7-02) live on the legal page: legal.html
TT7-03 · v0.9 · 2026-09-21 · COVERS: EVERY FORM OF CREATOR COOPERATION, FOCUS ON L0 INDEX INCLUSION · SUPERSEDED BY: THE DEVELOPER AGREEMENT FOR L2/L3 · RELATED: TT7-01, TT7-02
Draft for consultation · awaiting legal review · not in force. Publishing it in draft state is deliberate — you should be able to read the rules before they bind anyone. 【TBD: …】 marks an item the operating entity or counsel must confirm before this document takes effect.
SUMMARYRead this first — seven sentences, non-binding
- At the shallowest tier you give us exactly two things: your work's material, and the URL you want users to open. No code to write, no packaging, no signing, no real-name verification.
- No fees. We charge you nothing and take no cut of your work.
- No exclusivity. You can be on any other platform, directory or store at the same time. We neither require nor accept exclusive arrangements.
- Your work stays yours. We only get the right to display and link per the material you provide — no ownership of your work, ever.
- One sentence withdraws. No reason needed, no liability of any kind. Withdrawal is processed faster than inclusion.
- Inclusion is not our endorsement of you, nor your endorsement of us. Your entry is explicitly labeled "Indexed · author-authorized" — never dressed up as an official recommendation.
- We don't touch your users. We don't host your logins, read your site's data, scrape your content, or bypass any restriction you set.
CH.01Definitions
| Term | Meaning |
|---|---|
| Inclusion | With a creator's authorization, bringing information about their work into TrayTool's display and distribution system |
| Creator / you | A person or organization that holds rights in a listed work, or is authorized by the rights holder to handle inclusion |
| Work | A creator's web app, online tool, content site, plugin or other digital creation |
| Target site | The URL the creator designates, which opens when a user clicks the listed entry |
| Index inclusion | The shallowest tier defined by this policy: an entry pointing to the target site, built and displayed solely from the creator's material |
| Index entry (also index plugin) | The display unit produced by index inclusion — an information card plus a door to the target site. It contains no code or content of the creator's work |
| Authorization record | The written record proving the creator consented: their confirmation wording, the date, and the scope granted |
| Recommender | A community member who suggests a work to us without being its rights holder |
| Curator | A user who combines listed entries into editions or capability chains and shares them |
| Platform | We — 【TBD: full legal name of the operating entity】 — together with traytool.com and the TrayTool desktop software we operate |
CH.02The four tiers of cooperation
| Tier | Name | What you do | What you get | Badge | Available today |
|---|---|---|---|---|---|
| L0 | Index inclusion | Provide material + target site + one sentence of consent | Shown in the website's inclusion directory and the community listing; users open your site in one click; plugin library after directory sync ships | Indexed · author-authorized | ✅ Site & community now; library see 2.2 |
| L1 | Manifest co-building | On top of L0, co-write a capability list with us: what your work can do, and each capability's parameters | Your capabilities appear on TrayTool's command surface and can be orchestrated by the local agent | Indexed · author-authorized + capability declared | ⏳ Local orchestration live; external AI calls await P2 |
| L2 | Signed publishing | Register as a publisher (email verification suffices) and sign your plugin packages | You control your own publishing and updates; three distribution channels optional | ⬤ Signed · your publisher name | ⏳ Awaits P1 (runtime loading) & P3 (distribution) |
| L3 | Pioneer co-creation | On top of L2, take part in feedback before the plugin contract freezes | First year: zero fees on official payment channels; early notice of contract changes; priority publisher page at launch | Same as L2 | ✅ Invitation-based, applications open |
2.1What this policy actually specifies
L2 and L3 involve signing, publisher identity and money; a separate Developer Agreement will govern them when published (see TT7-01 chapter 3: until then, descriptions of L2/L3 on this site are not contractual commitments).
This policy fully specifies L0 and L1, plus the principles common to all four tiers (chapters 5, 6, 7 and 10).
2.2An honest account of what works today
| Where your index entry appears | Status |
|---|---|
| The inclusion directory on traytool.com | ✅ Live once listing is confirmed |
| The community's shared inclusion list | ✅ Same as above |
| The plugin library in the TrayTool desktop app | ⏳ The library is live, but its directory currently ships bundled with host versions; automatic directory sync from the platform is not delivered yet. Until then index entries do not enter the library — see the note below |
| Share links of user editions | ⏳ Share-link installation is planned for phase P3 |
| Invoked by external AI assistants via MCP | ⏳ L1 and above only; the MCP server is planned for phase P2 |
CH.03Index inclusion (L0)
3.1What you provide
Required (four items)
| # | Item | Note |
|---|---|---|
| R1 | Work name | The name you want displayed |
| R2 | Target site | One URL that opens when users click; must start with https:// |
| R3 | One-sentence description | Within 【TBD: 40 characters recommended】, stating what it does |
| R4 | Consent confirmation | Reply in the appendix A format, or state consent in your own words as the rights holder |
Optional (provide as needed — listing works without them)
| # | Item | If not provided |
|---|---|---|
| O1 | Icon or cover image | A text mark generated from the work name |
| O2 | Screenshots (up to 【TBD: 3 recommended】) | Text information only |
| O3 | A longer introduction | Only the one-sentence description shows |
| O4 | Category tags (e.g. "writing", "e-commerce", "game dev") | We pre-categorize from the description and ask you to confirm |
| O5 | Display credit (a pen name or team name is fine) | No author shown; work name only |
| O6 | Good use cases, recommended first path | Not shown |
| O7 | Limitations users should know ("signup required", "mainland China only", "partial features paid") | Not shown — but we strongly recommend providing it; it reduces user misunderstanding |
3.2Form & scope of the authorization
Form. Authorization must be given in a retainable written form: email, a private message on a social platform, or a public reply or DM in a community — all fine. Verbal or phone consent does not count as authorization under this policy. After we receive it we reply with a confirmation message restating what you authorized (appendix B). The listing takes effect when you receive that confirmation. If anything in it differs from your intent, say so — your correction governs.
Scope of the base authorization. Consenting to index inclusion grants us the following non-exclusive, free, revocable-at-any-time license:
| # | License |
|---|---|
| G1 | Display your entry in the inclusion directory on traytool.com |
| G2 | Display your entry in the plugin library of the TrayTool desktop app |
| G3 | List your entry in the community's shared inclusion list |
| G4 | Let TrayTool users add your entry to their editions and share it via share links |
| G5 | To serve G1–G4, copy, scale or crop the images you provided within necessary bounds (without changing their content) |
Uses that need separate consent. None of the following is included in the base authorization; each requires your separate, explicit agreement:
| # | Use |
|---|---|
| X1 | Naming and introducing your work in our promotional material, social posts or demo videos |
| X2 | Mentioning your work in media interviews, partnership talks or fundraising material |
| X3 | Including your work in an official edition or capability chain (as opposed to users combining it themselves) |
| X4 | Using your work's name or marks as the title of any campaign or feature |
3.3What we will do
| # | We will |
|---|---|
| W1 | Build the entry from your material and send you a preview to confirm before it goes live |
| W2 | Label the entry "Indexed · author-authorized" with the listing date |
| W3 | Open the target site you designated on click — in your choice of: (1) the user's system browser, or (2) TrayTool's controlled window (see 3.5) |
| W4 | Check periodically that the target site is still reachable; on failure, notify you and mark the entry "link unavailable" rather than deleting it |
| W5 | Sync entry updates you submit within 【TBD: 3 business days recommended】 |
| W6 | Remove the entry within the chapter 6 deadlines upon withdrawal |
| W7 | If a third party complains about your entry, notify you first, then handle per chapter 7 (except in urgent cases) |
3.4What we will not do
| # | We will not | Basis |
|---|---|---|
| N1 | Host, read, autofill or forward any login credential, password or verification code for your site | Credential rules A1, A2 |
| N2 | Read any user data inside your site; sessions in the controlled window belong to your site alone | Credential rule A3 |
| N3 | Scrape your site's content, copy its pages, or mirror it | — |
| N4 | Bypass any access control, paywall, region restriction, rate limit or anti-scraping measure your site sets | TT5-03 §6.2 red line ③ |
| N5 | Inject ads, promo content, tracking code, or anything altering your pages' look or behavior | — |
| N6 | Dress your entry up as "official recommendation", "featured" or "certified" without your separate consent and the facts to back it | TT2-02 §4.1 |
| N7 | Suggest any cooperation, investment, employment or endorsement between us beyond this policy | — |
| N8 | Use your work for any purpose listed in 3.2.3 without your separate consent | — |
| N9 | Charge you anything, or make payment a condition of listing, ordering or placement | — |
| N10 | Demand exclusivity, or downgrade your display because you appear on other platforms | TT2-02 E3 |
| N11 | Give your contact details to any third party, or use them for pushes unrelated to inclusion | TT7-02 §4.2 |
| N12 | Retaliate against your withdrawal in any way, or comment on it publicly | — |
3.5The boundaries of the controlled window
If you choose to open the target site in TrayTool's controlled window (3.3, W3 option 2), the window follows these rules:
| Rule | Detail |
|---|---|
| Navigation scope | Limited to your target site's domain plus the resource domains you confirm (fonts, images, script CDNs you use) |
| Out-of-scope links | Links to other domains are handed to the user's system browser — no cross-domain navigation inside the window |
| Credentials | Per 3.4 N1/N2: the host can detect at most the "logged in or not" state — never the credentials themselves |
| Page content | Per 3.4 N5: nothing is injected |
| You may switch to the system browser anytime | One sentence; the change takes effect within 【TBD: 3 business days recommended】 |
3.6Fees & ordering
Index inclusion charges nothing. If that ever changes, the change applies only to listings started after the change announcement — existing entries are unaffected.
The directory's default ordering follows 【TBD: a neutral rule such as listing date or alphabetical order recommended】. Paying for placement is not accepted.
If ordering based on real usage data (such as open counts) is ever introduced, the rules will be announced in advance and applied equally to every entry.
CH.04Compliance requirements for target sites
4.1 Your warranties
By agreeing to be listed, you warrant that:
- You are the rights holder of the work and the target site, or are authorized by the rights holder to handle inclusion;
- The material you provide (name, description, images) does not infringe any third party's copyright, trademark or other lawful rights;
- Your target site operates lawfully and contains no illegal content.
4.2 Our baseline checks
Before inclusion we run the following baseline checks. These checks exist to hold the platform's floor, not to judge the quality of your work, and they are not a guarantee of your work's safety (see TT7-01 §7.2).
| # | Check | If it fails |
|---|---|---|
| C1 | The target site is reachable and served over https:// | We ask you to fix it |
| C2 | The authorization confirmation comes from an account or email with a visible connection to the work (e.g. a public contact on the work's page, the credited account) | We ask you to add proof, or confirm from the connected account |
| C3 | The target site shows no obviously illegal content and is not flagged as malicious by mainstream security services | Not listed; we tell you why |
| C4 | Your description honestly represents the work, without exaggeration that could mislead users | We agree on a revision with you |
4.3 Cases where we do not list
| Case | Handling |
|---|---|
| Authorization from the rights holder cannot be confirmed | Listed on hold until it can be confirmed |
| The target site's terms of service explicitly forbid third-party directory listing or window embedding | Only system-browser opening may be chosen; if even links are forbidden, we do not list |
| Requires bypassing access controls to be usable | Not listed (red line, no exceptions) |
| Contains illegal content, malicious code, or is fraudulent in purpose | Not listed (red line, no exceptions) |
| Impersonates another's work or brand | Not listed, and the impersonated party is notified (if contactable) |
CH.05Division of rights & responsibilities
| Matter | Responsible party | The platform's role |
|---|---|---|
| The work's function, quality and safety | Creator | No pre-review; provides trust-label mechanisms so provenance is visible |
| Lawfulness of the work's content | Creator | Handles complaints per Chapter 7 |
| The work's handling of its users' data | Creator | We never touch that data (3.4 N2) |
| Intellectual property in the work | Creator (the platform claims no rights) | — |
| Accuracy of the material shown on the entry | Creator provides; the platform displays as-is | Updated promptly per your corrections |
| Whether an entry's presentation follows this policy | Platform | — |
| Whether the controlled window behaves per §3.5 | Platform | — |
| The safety of the TrayTool host itself | Platform | — |
CH.06Withdrawal, corrections & takedown
6.1 How to withdraw
Using the same channel you authorized through (or any channel you can prove is connected to the work), tell us one sentence: "please take it down." Appendix C offers a reference format, but you are not required to use it.
| Item | Rule |
|---|---|
| Is a reason required? | No |
| Is prior notice required? | No |
| Any liability or cost for you? | None |
| Does it affect future re-application? | No |
6.2 Processing deadlines
| Action | Deadline |
|---|---|
| Acknowledge receipt of the withdrawal | Within 【TBD: 1 business day recommended】 |
| Remove from traytool.com and the community listing | Within 【TBD: 3 business days recommended】 |
| Remove from the plugin library | After directory sync ships, same deadline as the website; before that, index entries never enter the library, so this does not apply |
| Delete your material and contact details | Per TT7-02 §4.4 |
6.3 Entries already added to users' chain groups
This section applies once directory sync ships and index entries enter the plugin library.
| Case | Handling |
|---|---|
| A user previously added your entry to a chain group or share link | The entry shows as "Withdrawn by author" in that user's host and no longer opens your site |
| Do we remotely delete files on users' machines? | No. The platform's power stops at "stop distribution + label inside the host" (TT2-02 §3.4.3 red line) |
An index entry itself contains none of your work's code or content (Chapter 1, "index entry"), so "no remote deletion" leaves nothing of your work behind on anyone's device — only a dead card labeled "Withdrawn by author."
6.4 Corrections
You may request correction of any information on your entry at any time — name, description, images, category, target site, opening method, display credit. Corrections take effect within 【TBD: 3 business days recommended】.
6.5 Platform-initiated takedown
| Case | Measure | Prior notice to you? |
|---|---|---|
| Target site unreachable for an extended period (【TBD: 30 consecutive days recommended】) | Entry suspended from display | ✅ Prior notice, with time to fix |
| Target site flagged as malicious by security services | Entry suspended immediately | Notice immediately after |
| Authorization found not to come from the rights holder | Entry taken down immediately | Notice to the authorizing party after |
| Infringement or illegality established via the Chapter 7 process | Handled per that finding | ✅ You were informed in the process |
Whenever we take down an entry on our own initiative, we state the reason in writing. You may contest a takedown; we will review and reply within 【TBD: 7 business days recommended】.
CH.07Third-party complaints & notice-and-takedown
Anyone who believes a listed entry infringes their lawful rights may submit a notice per TT7-01 Chapter 11.
The handling process:
| Step | Action |
|---|---|
| 1 | On receipt, preliminarily verify the notice is complete |
| 2 | Notify you of the complaint's substance and give you a response window of 【TBD: 5 business days recommended】 (in urgent cases display may be suspended first) |
| 3 | Decide based on both parties' material: keep / annotate / suspend display / take down |
| 4 | Inform both parties in writing of the outcome and reasons |
The target site operator's objection takes precedence: if the person objecting is the target site's operator themselves and differs from the authorizing party, we suspend display per the operator's wishes, then verify the authorization source.
We will periodically publish complaint and disposition statistics (counts and types, without case details).
CH.08Recommenders & curators
8.1 Recommenders
Community members may recommend works they believe deserve listing.
| Rule | Explanation |
|---|---|
| A recommendation is not an authorization | Recommenders cannot consent on a creator's behalf. On receiving a recommendation we still contact the creator directly and obtain authorization per Chapter 3 |
| Recommenders do not liaise on our behalf | Unless the recommender is themselves a known contact of the creator and the creator agrees to communicate through them |
| Recommender credit | With the creator's consent, an entry may show "Recommended by @someone" |
| No monetary rewards or rebates for recommendations | See §8.3 |
8.2 Curators
When users combine listed entries into chain groups and share them:
| Rule | Explanation |
|---|---|
| A curator's combination is their personal creation | The platform does not endorse their combination choices |
| After a creator withdraws | The entry shows as "Withdrawn by author" in all chain groups (§6.3) |
| If a creator does not want to appear in certain kinds of groups | Tell us; we annotate the entry "Author prefers not to appear in ×-type groups" and surface the note on share pages |
8.3 Why recommendations carry no rewards
CH.09Moving to deeper tiers
Any upgrade (L0 → L1 → L2 → L3) must be proposed or explicitly agreed by you. We may introduce deeper cooperation to you, but never as a condition of keeping your listing.
When upgrading to L1 (capability co-building), you will jointly confirm with us a capability list, specifying every capability of your work that can be invoked and its parameters.
| Additional L1 rules | Explanation |
|---|---|
| The capability list must be confirmed by you item by item | We will never declare any capability you have not confirmed |
| Capability invocations follow the host's security pipeline | Treated the same as any other local capability: three-level risk gate plus audit logging (T5A-05: no exemptions) |
| You may delete any capability at any time | Same as Chapter 6 — one sentence |
| The phrase "callable by external AI" | Before the MCP server ships (P2), we will not describe your entry this way |
Rules for L2 and L3 are set out in the Developer Agreement published at that time. Until it is published, for creators already in the L3 pioneer program, your entitlements are governed by our written exchanges with you.
CH.10The platform's commitments
These commitments apply at every tier. They are the most important part of this policy:
| # | Commitment |
|---|---|
| P1 | We apply one identical set of rules to every creator — no distinction by a work's fame, a creator's influence, or any commercial relationship |
| P2 | Any amendment to this policy that is unfavorable to creators applies only to listings started after the amendment announcement |
| P3 | Any amendment will be announced 【TBD: 30 days recommended】 in advance and every listed creator will be individually notified |
| P4 | All historical versions of this policy remain retrievable |
| P5 | Inclusion counts we publish count only entries that are authorized and currently displayed — recommended, pending or withdrawn entries are never counted |
| P6 | We will not use phrases like "an established ecosystem" or "hundreds of works" in any external material when they do not correspond to real authorized entries (TT2-01 §7.3) |
CH.11Effect & governing law
This policy takes effect between you and us on the day you receive our listing confirmation message (§3.2.1), and remains in force until you withdraw or the entry is taken down under Chapter 6.
Governing law and dispute resolution follow TT7-01 Chapter 13: 【TBD】.
Where this policy conflicts with TT7-01 or TT7-02 on matters of inclusion, this policy prevails.
APPENDIX AAuthorization (reference format)
You may copy the text below and fill in the brackets — or reply in your own words. All that matters is that you clearly express two things: "I agree" and "I am the rights holder."
BASE — REPLY WITH THIS
I agree that TrayTool lists my work as an "index entry" under the Creator Inclusion & Distribution Policy. Work name: [ ] Target site: [ https:// ] Opening: [ System browser / TrayTool controlled window ] (if unsure, choose system browser) Display credit: [ the name you want shown, or "no credit" ] I confirm I am the rights holder of this work (or am authorized by the rights holder to handle this). I know I can withdraw at any time with one sentence.
EXTRA LICENSES — OPTIONAL, TICK EACH ITEM; UNTICKED MEANS NOT LICENSED
[ ] Allow TrayTool to name and introduce my work in its promotional material and social media (X1) [ ] Allow my work to be mentioned in media interviews and partnership discussions (X2) [ ] Allow my work to be included in official chain groups or feature chains (X3)
APPENDIX BListing confirmation message (ours)
WHAT WE SEND BACK BEFORE YOUR ENTRY GOES LIVE
Received, and thank you for the trust. Here is our restatement of what you authorized — please check it: · Work: [work name] · Target site: [URL] · Opening: [system browser / controlled window] · Display credit: [credit / no credit] · Extra licenses: [each item; or "none — base inclusion only"] Entry preview: [preview link or screenshot] Once you confirm, the entry goes live by [date]. If anything above does not match your intent, just tell us — your correction governs. Any time you want it taken down, reply "please take it down." No reason needed. — TrayTool · [contact person] · [official contact channel]
APPENDIX CWithdrawal (reference format)
ONE SENTENCE
Please take down my TrayTool listing: [work name].
APPENDIX DPre-publication checklist
| # | Check | Status |
|---|---|---|
| D-01 | All 【TBD】 items replaced | ☐ |
| D-02 | Practicing lawyer has reviewed, focusing on Ch.3 §3.2 (license scope), Ch.5 (division of responsibility), Ch.6 (enforceability of withdrawal deadlines) | ☐ |
| D-03 | The "available now" column of §2.2 matches the website's honesty baseline and actual delivery status, item by item | ☐ |
| D-04 | The §3.4 red-line list has been issued as an internal operating standard to everyone handling inclusion | ☐ |
| D-05 | Location and format for archiving authorization records are settled (TT7-02 §4.4) | ☐ |
| D-06 | The §6.2 withdrawal deadlines are achievable, verified by internal drill | ☐ |
| D-07 | Every promise in TT7-05 and TT7-06 maps to a clause in this policy (see TT7-04 Appendix B cross-reference) | ☐ |
APPENDIX EChange log
| Version | Date | Change |
|---|---|---|
| 0.9 | 2026-09-21 | Draft for consultation, first version |