60 lines
8.0 KiB
Markdown
60 lines
8.0 KiB
Markdown
# Brand and intellectual property
|
|
|
|
Status: **Wristivo is a provisional working name, not legally cleared or registered.** Official references checked 2026-09-16. These engineering controls reduce avoidable risk; they cannot guarantee freedom from disputes or replace jurisdiction-specific clearance.
|
|
|
|
## Product identity
|
|
|
|
Owner-approved working brand (2026-09-16): **Wristivo**. Proposed descriptive subtitle: **Wrist-powered TV remote**. Use an original abstract motion/light identity, original typography treatment, and independently created app screens. This is a naming proposal; name availability, similar marks, app listings, domains, and visual identity still need clearance.
|
|
|
|
Use `Wristivo` as the protocol client display name where the supported TV pairing mechanism permits it. The user should recognize that name in the TV's access prompt and allowed-device list. Saving a trusted client on a TV is device authorization; it is not trademark registration, Samsung certification, a published Tizen TV application, or a guarantee that every TV retains the same displayed name. Verify actual behavior on each supported model.
|
|
|
|
Proposed compatibility copy, pending implementation evidence and release review:
|
|
|
|
> Wristivo is an independent remote-control app for compatible Samsung TVs running Tizen. It is not affiliated with or endorsed by Samsung or Apple. Supported models and setup requirements are listed in the compatibility guide.
|
|
|
|
Use third-party names only where they explain genuine compatibility. Do not use Samsung, SmartThings, Tizen, Apple, or competing remote-app names in the primary brand, bundle branding, original icon, or a claim of official status. Do not copy manufacturer logos or imply that a disclaimer alone grants usage rights. Samsung's developer-site terms do not grant rights to its marks. Apple provides conditions for referential compatibility statements and prohibits implied endorsement. Check applicable agreements and actual marketing before publication. [Samsung developer terms](https://developer.samsung.com/terms?location=us), [Apple trademark guidelines](https://www.apple.com/legal/intellectual-property/guidelinesfor3rdparties.html).
|
|
|
|
## Distinct risks require distinct checks
|
|
|
|
| Area | What the project must examine | Required evidence |
|
|
| --- | --- | --- |
|
|
| Copyright | Source code, icons, illustrations, fonts, audio, documentation, TV screenshots, and copied UI artwork | Original-work provenance or license/permission and preserved notices |
|
|
| Trademark | Wristivo and confusingly similar names, logos, pronunciations, or commercial impressions in target markets | Dated clearance search and decision for actual goods/services and territories |
|
|
| Patents | Relevant gesture recognition, wearable control, and TV-control inventions | Specialist freedom-to-operate review if warranted for commercial launch; original coding alone does not answer patent questions |
|
|
| Contract/platform terms | SDK licenses, sample-code terms, API/service terms, protocol implementation sources, and distribution agreements | Reviewed terms, permitted usage, and unresolved limitations recorded |
|
|
|
|
The basic distinction is that trademarks identify source, copyright protects original expressive works, and patents protect qualifying inventions. Rights can overlap. [USPTO overview](https://www.uspto.gov/trademarks/basics/trademark-patent-copyright).
|
|
|
|
## Name clearance release gate
|
|
|
|
1. Product owner chooses launch territories and intended publisher/legal entity. Do not infer the legal market from a developer's timezone or device locale.
|
|
2. Search exact `Wristivo`, spacing variants such as `Wrist Ivo`, phonetic/spelling neighbors, related marks, and similar visual identities. Search software, remote controls, wearables, and related goods/services, not just identical names.
|
|
3. Check WIPO and each relevant national/regional register, plus app stores, search engines, company names, domains, and relevant marketplace usage. WIPO notes that its coverage does not replace national/regional searches. USPTO describes federal, state, and common-law sources as part of comprehensive US clearance. [WIPO database](https://www.wipo.int/en/web/global-brand-database), [USPTO clearance guidance](https://www.uspto.gov/trademarks/search/comprehensive-clearance-search-similar-trademarks).
|
|
4. Save date, source, exact query, jurisdiction, relevant results, status, goods/services, and reviewer decision. A search-engine no-result page, available domain, or App Store name reservation is not legal clearance.
|
|
5. Have a qualified trademark professional assess material conflicts and filing strategy for the selected territories before major branding expenditure or launch. Do not use a registered-mark symbol unless valid rights justify it.
|
|
6. Only after clearance, finalize the visible name, publisher-controlled reverse-DNS identifiers, domain, icon, legal text, and store metadata. Keep the proposed name configurable until then.
|
|
|
|
Current clearance record: **not completed**. The integration engineer performed narrow quoted public-web searches for `"Wristivo"` and `"Wristivo" remote app trademark` on 2026-09-16 and reported no returned results. This is preliminary screening only; no trademark-register, phonetic-similarity, domain, or jurisdiction-specific clearance is established. An earlier working-name candidate was dropped after an existing retail-product use was found. No registered-name, domain-ownership, or non-infringement claim is made by this repository.
|
|
|
|
## Rules for parallel implementation agents
|
|
|
|
- Write original implementations from the project's interface contracts and independently justified design. Do not clone a commercial remote's screens, icon, copy, calibration tutorial, or proprietary code.
|
|
- Do not treat public GitHub/Gitea code, forum snippets, sample code, or downloaded assets as license-free. Before incorporating any source or dependency, record its origin, version, license, attribution, distribution obligations, and decision.
|
|
- Avoid dependencies with unresolved provenance or obligations incompatible with the intended commercial distribution. If unsure, isolate the issue and ask the integration engineer to decide before merge.
|
|
- Keep a dependency and asset register, including generated assets and fonts. Record author/tool, input/reference rights, modifications, and license. AI-generated work is not automatically free of infringement risk; review similarity and provenance.
|
|
- Use neutral original demo content on a TV or simulated TV. Exclude movie stills, channel logos, streaming-service artwork, personal accounts, and copyrighted broadcast footage unless rights are documented.
|
|
- Use Apple-provided symbols, platform assets, or device frames only within their applicable license/marketing conditions; availability in a tool is not unrestricted redistribution permission.
|
|
- Document protocol observations and authoritative references. Do not copy an entire third-party implementation, bypass TV consent, extract secrets from vendor software, or claim an unofficial endpoint is a supported vendor API.
|
|
- Keep source private on the owner's Gitea until publication/licensing is explicitly decided. A private repository still requires compliance with licenses for incorporated material.
|
|
- Do not apply a blanket open-source license or assign copyright ownership to an unverified legal entity. The owner must select the licensing and contributor-rights model before external contribution or publication.
|
|
|
|
## Required pre-release artifacts
|
|
|
|
- Completed name/mark clearance log and final name decision.
|
|
- Dependency and asset inventory, exact licenses, required attributions, and any written permissions.
|
|
- Original design/source provenance notes and review of protocol licensing/terms.
|
|
- Store copy, screenshots, icon, compatibility claims, and disclaimer reviewed together.
|
|
- Applicable rights and permission questions resolved for the intended launch territories.
|
|
|
|
App Store acceptance does not establish IP ownership or immunize the publisher from claims. Keep these artifacts with the release evidence and repeat relevant checks when the brand, dependencies, features, or launch markets change.
|