What the registration checkbox accepts

GNOTH terms

GNOTH terms · version 2026-09 · source: truevectors/gnoth, docs/beta/GNOTH_Beta_Agreement.md

GNOTH Beta Evaluation Agreement

Draft for review by counsel. Not legal advice. Bracketed items are for TrueVectors to complete before sending.

This Beta Evaluation Agreement (the "Agreement") is between [TrueVectors legal entity name], [address] ("TrueVectors") and the person or organisation named in the license token issued under it (the "Participant"). It governs the Participant's use of the GNOTH beta software during the beta trial that precedes GNOTH's commercial release, planned for April 2027.

By installing the license token (gnoth license install <token>) or otherwise running the Software, the Participant accepts this Agreement. If the Participant does not accept it, the Participant must not install or run the Software.

1. Definitions

• Software means the GNOTH beta release provided by TrueVectors: the release package (a Python wheel containing compiled bytecode), the license token, the hooks and MCP server it installs into a project, the local dashboard, and any updates TrueVectors provides during the Term.
• License Token means the signed token TrueVectors issues to the Participant by name, carrying the Participant's name, the plan, an expiry date and, where set, a beacon address.
• Outputs means everything the Software produces on the Participant's machine: captured sessions, reflections, findings, the catalogue of traits, the compiled rules block written into the Participant's project files, and the dashboard.
• Confidential Information means the Software, its design, behaviour, prompts, predicates, categories and vocabulary, its documentation, the fact and terms of this beta, the Participant's Outputs insofar as they reveal how the Software works, and any non-public information TrueVectors provides. It does not include information that is public through no fault of the Participant, that the Participant already lawfully held, or that the Participant independently develops without use of Confidential Information.
• Feedback means suggestions, bug reports, findings about the Software's behaviour, and any other comments the Participant gives TrueVectors about the Software.

2. What TrueVectors provides

TrueVectors will provide the Participant with the Software and one License Token. TrueVectors may provide updated releases and replacement tokens at its discretion. TrueVectors has no obligation to provide support, maintenance, updates, or a commercial version, and may end the beta at any time.

3. License

Subject to this Agreement, TrueVectors grants the Participant a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to install and run the Software on machines the Participant controls, for the sole purpose of evaluating it and giving Feedback, during the Term.

4. Restrictions

The Participant will not, and will not allow anyone else to:

1. copy, distribute, sell, lease, lend, host, or otherwise make the Software or the License Token available to any third party, or share the License Token with anyone; 2. decompile, disassemble, reverse engineer, or otherwise attempt to derive the source code, prompts, predicates, catalogue design, or algorithms of the Software, except to the extent that applicable law expressly permits despite this restriction; 3. modify, adapt, translate, or create derivative works of the Software, or remove or alter any proprietary notice; 4. circumvent, disable, or interfere with the License Token check, the expiry, or the beacon described in section 6; 5. use the Software to build, train, or improve a competing product, or use knowledge of its behaviour, categories, or vocabulary to do so; 6. publish, post, share, or otherwise make available to anyone outside the Participant's own organisation any benchmark, comparison, screenshot, screen recording, video, transcript, or description of the Software, its interface, or its Outputs, in any medium, including social networks, forums, articles, messaging groups, and AI assistants, without TrueVectors' prior written consent. The Participant acknowledges that the Software is a pre-release research preview, that any such material misrepresents it as soon as it is superseded, and that this restriction is material to TrueVectors' willingness to grant this licence; 7. use the Software in production systems, for any purpose other than evaluation, or in violation of applicable law or of the terms of the AI coding tools it is used with.

5. Ownership

The Software, the License Token, and all intellectual property rights in them belong to TrueVectors and its licensors. Nothing in this Agreement transfers any ownership. TrueVectors reserves all rights not expressly granted.

The Participant owns the Participant's own code, conversations, and project files. The Outputs are the Participant's to use within the Participant's own projects during and after the Term, subject to section 7.

6. What the Software sends to TrueVectors, and what it does not

The Participant should understand this section before installing.

The beacon. If the License Token carries a beacon address, the Software sends TrueVectors one small message, at most once per day per machine, when it runs. That message contains only: the Participant's name as it appears in the License Token, the plan, the token's expiry date, the Software version, the operating system name, the command that ran (for example serve or hook), and a one-way hash derived from the machine's name and home directory so repeated messages from the same machine can be recognised. The beacon never blocks the Software; if it cannot reach TrueVectors, the Software runs anyway.

Optional rule reporting, off unless the Participant turns it on. The Software can report which rules fired, never what they said. A rule is one entry in a fixed vocabulary TrueVectors publishes with the Software; a report carries, for each rule, its identifier and four counts, together with the Software version, the operating system name, the editors and models in use, and how many conversations and classes the store holds. It carries no class text, no quotation, no path, no file name, no session identifier, and not the Participant's name. It is sent under a reporter identifier salted with a random value generated on the Participant's machine and never sent, so the identifier itself cannot be derived from, or matched to, the machine hash in the beacon described above. TrueVectors does not claim the reports are anonymous in every respect: a report carries the operating system name, the Software version, and the editors and models in use, and the beacon carries the operating system name, the Software version and the Participant's name. None of those fields is unique to a person, but across a small number of Participants the two records could in principle be associated by their shape and timing. TrueVectors does not attempt such association, and does not attribute rule reports to a Participant.

This is off by default and takes effect only when the Participant enables it with gnoth telemetry rules; gnoth telemetry off ends it. gnoth telemetry --show prints the exact report that would be sent, so this paragraph can be checked rather than trusted. TrueVectors uses these reports to learn which behaviours recur across machines, models and editors, and improvements derived from them reach every Participant as free updates to the Software.

What never leaves the machine. Whether or not rule reporting is enabled, the Software does not send TrueVectors the Participant's code, prompts, conversations, transcripts, reflections, findings, the text of any realized class, project files, file names, or the contents of the dashboard. All capture, verification, realization, and compilation run locally on the Participant's machine, and the reflections themselves are written by the AI coding tool the Participant already uses, under the Participant's own account and at no additional charge from TrueVectors.

What the Software says to the Participant's agent. Through the editor's own hook interface, the Software hands the agent short instructions generated on the Participant's machine from the Participant's own store: a request to reflect after a set number of exchanges, the Participant's own compiled rules block, and a request to add the marker line to a reply. Every such text opens by naming its source ("GNOTH (your own hook, installed in this project by you, running locally)"). By default the Software never places a message in a chat: the standing instruction to reflect lives in the Software's MCP server description and in the rules file, and hooks use only the editor's context and stop channels (Claude Code, Copilot); in Cursor, whose stop hook can only reply with a chat message, hooks capture and stay silent. gnoth delivery full enables that Cursor message; gnoth delivery rules-only turns all sending off, leaving the rules file and the dashboard's manual reflect.

Inspection. The Participant can see the license state and whether a beacon address is set with gnoth license, the delivery mode with gnoth delivery, the reporting mode and the exact report with gnoth telemetry --show, and can inspect everything the Software stores in the store directory chosen at install time.

TrueVectors uses beacon data to know who is running the beta, which version, on what platform, and until when, and to plan support and the commercial release. TrueVectors will not sell beacon data or rule reports, and will delete beacon data within [90] days after the beta ends, except as required by law. Rule reports are retained in aggregate; because they carry no identifying content, they are not attributed to a Participant.

7. Confidentiality

The Participant will keep Confidential Information confidential, use it only for the evaluation, protect it with at least the care used for the Participant's own confidential information, and disclose it only to the Participant's own personnel who need it for the evaluation and are bound by obligations at least as protective as this section. The Participant will notify TrueVectors promptly of any unauthorised use or disclosure. This section survives for [three] years after the Term, and for trade secrets for as long as they remain trade secrets.

8. Feedback

The Participant grants TrueVectors a perpetual, irrevocable, worldwide, royalty-free license to use, reproduce, modify, and incorporate Feedback into its products and services without restriction or attribution. TrueVectors is not obliged to use any Feedback. Feedback that describes the Participant's own code or conversations remains the Participant's, and TrueVectors will not publish it in identifiable form without consent.

9. Beta nature, no warranty

The Software is pre-release. It may contain errors, may change or be withdrawn without notice, and may write to files in the Participant's projects (a marked block in rules files such as CLAUDE.md). The Participant is responsible for reviewing what the Software writes and for keeping backups.

THE SOFTWARE AND ANY OUTPUTS ARE PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. TrueVectors does not warrant that the Software will find every error an AI coding tool makes, that any finding is correct, or that any AI coding tool will behave differently as a result. The Software carries no measure or guarantee of reliability.

10. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, TRUEVECTORS WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR LOSS OF DATA, PROFITS, OR BUSINESS, ARISING OUT OF OR RELATING TO THIS AGREEMENT OR THE SOFTWARE, HOWEVER CAUSED. TRUEVECTORS' TOTAL LIABILITY UNDER THIS AGREEMENT WILL NOT EXCEED [ONE HUNDRED US DOLLARS (US$100)]. Nothing in this Agreement limits liability that cannot be limited by law.

11. Term and termination

This Agreement begins when the Participant accepts it and ends on the earliest of: the expiry date in the License Token; written notice of termination by either party; or TrueVectors' announcement that the beta has ended (the "Term"). TrueVectors may also terminate immediately if the Participant breaches sections 4 or 7.

On termination the license ends, the Software stops running when the License Token expires or is revoked, and the Participant will uninstall the Software, delete the release package and the License Token, and on request confirm in writing that it has done so. The Participant may keep the compiled rules block already written into the Participant's own project files. Sections 5 through 12 survive termination.

12. General

• Governing law and venue. This Agreement is governed by the laws of [jurisdiction], and the courts of [venue] have exclusive jurisdiction, without regard to conflict-of-law rules.
• Export and sanctions. The Participant will comply with applicable export control and sanctions laws.
• Assignment. The Participant may not assign this Agreement. TrueVectors may assign it to a successor of its business.
• Entire agreement. This Agreement is the entire agreement about the beta and replaces any earlier discussions. Changes must be in writing and signed by both parties, except that TrueVectors may update the Software and issue replacement tokens under these same terms.
• Severability and waiver. If a provision is unenforceable, the rest remains in effect. A failure to enforce is not a waiver.
• Notices. Notices to TrueVectors go to [notices email]. Notices to the Participant go to the email address the License Token was sent to.

13. What may be offered later

The Software is provided free of charge for the research preview, and the License Token carries the expiry date of that preview. TrueVectors makes no commitment, in this Agreement or elsewhere, about the price or availability of the Software after that date. Before the preview ends, TrueVectors will write to the address the Participant registered with, setting out what is offered next. That may include a continued free tier, or a separate paid service such as a control plane across several stores, or comparable features that do not run on the Participant's machine alone. Any such offer will be optional, and the Participant is never obliged to take it. Whatever is offered, the compiled rules block already written into the Participant's own project files remains the Participant's, as section 11 provides.

Acceptance

Accepted by installing the License Token, or by signature below.

	TrueVectors	Participant
Name
Title
Signature
Date