What is Intellectual Property?

Intellectual Property (IP) is a category of property that covers creations of the mind — inventions, designs, artistic works, names, symbols, and so on. Unlike physical property, it is intangible, but the law still treats it as something that can be owned, licensed, sold, or protected.

For a project like NanoJam, IP is relevant because the device combines several "things of the mind":

-The circuit design (custom PCB)
-The firmware (code running on the XIAO ESP32-S3)
-The 3D-printed enclosure design (CAD files)
-The user interface graphics on the OLED
-The name and visual identity of NanoJam itself

Each of these can, in principle, be protected by a different kind of IP right.

(prompt for Claude: differentiate the main IP's in accordance to NanoJam)

Patents

A patent gives the inventor the right to exclude others from making, using, selling, or importing the invention for a limited period (usually 20 years) in the country where the patent is filed.

Important things I learned:

- There is no such thing as a global patent. You have to file in each country/region where you want protection.
- The invention has to be novel, non-obvious, and useful.
- Patents are expensive to file and maintain, and only make sense when there is a real commercial reason.
- Filing also means publishing the invention , so the trade-off is: protection in exchange for disclosure.

- For NanoJam, which builds on a lot of existing prior art (MP3 players, rotary encoders, ESP32-based audio projects), filing a patent does not make sense. The novelty is mostly in how the pieces are combined, not in any one new technical idea.

Copyright

Copyright protects original works of authorship — writing, music, art, code, photographs, drawings. Unlike patents, copyright is automatic: the moment I write firmware or draw a CAD file, I already hold the copyright on it. I don't need to register anything.

For NanoJam, copyright covers:

the firmware source code
the KiCad schematic and PCB files
the CAD enclosure files
the documentation pages
photos and renders of the device

Copyright is the right that all the open-source licenses (MIT, GPL, Creative Commons) actually rest on. You can only license something to others if you hold copyright on it in the first place.

Trademarks

A trademark distinguishes the goods or services of one creator from another. It can be a word, logo, shape, color, or even a sound.

Quick symbols:



img

For NanoJam, the name and the small logo I am designing could in principle be trademarked, but I do not plan to register one. The project is non-commercial and the name is more of an identifier than a brand.

Trade Secrets

Trade secrets protect confidential information that has commercial value because it is secret — like a recipe or a manufacturing process. To qualify:

- The information must be commercially valuable because it is secret
- It must be known only to a limited group
- The owner must take reasonable steps to keep it secret (NDAs, access controls, etc.)

Since I want to share everything about NanoJam openly, trade secrets are the opposite of what I want. Mentioned here for completeness.

Licenses

Holding copyright on something does not automatically tell anyone else what they are allowed to do with it. A license is the document that says: "here is what you can and cannot do with my work." Without a license, the default is "all rights reserved" — meaning nobody can legally reuse it.

For open projects, there are a few well-known license families:

MIT License The MIT License is one of the most permissive open-source licenses. It basically says: do whatever you want with this software — use it, copy it, modify it, sell it — just keep the original copyright notice and don't sue me if it breaks.

It is the most popular software license on GitHub. Great for code that you want to be reused as widely as possible, including in commercial products.

GPL (GNU General Public License) The GPL is a copyleft license. It also lets you use, modify, and share the software — but with one big condition: anything you build on top of GPL code must also be released under the GPL. This keeps the software open forever, but it can be restrictive if you want to combine GPL code with proprietary code.

Creative Commons (CC) Creative Commons is a family of six licenses designed mainly for creative works (images, documentation, designs) rather than code, though they can be used for anything. CC licenses let you mix and match three conditions:

(prompt : generate table for CC symbols)

There are six different license types, listed from most to least permissive here: img

Choosing a License for NanoJam

After reading through the options, I decided to license NanoJam under CC BY-NC-SA 4.0.

My reasoning:

BY (Attribution) — I want to be credited if someone uses or remixes my work. This also helps anyone who finds a derivative version trace it back to the original documentation.
NC (NonCommercial) — NanoJam is a learning project and I don't want someone to take it as-is and sell it on Amazon. If a company wants to commercialize it, they should talk to me first.
SA (ShareAlike) — If someone builds on top of NanoJam, I want their version to also stay open so the community can keep learning from it. This feels like the right spirit for a Fab Academy project.

This license fits the openness Fab Academy encourages, while keeping the project from being silently absorbed into a commercial product.

Generating the license

I used the Creative Commons License Chooser to generate the license text.

Steps I followed:

- Opened the chooser and answered the questions about how I want my work to be used.
- The chooser confirmed my selection as CC BY-NC-SA 4.0.


- Filled in the attribution details — title, creator name, link to the work, link to my profile, year.


- Copied the generated HTML snippet to embed on my final project page.

The license badge for NanoJam looks like this: NANOJAM © 2026 by archita b k is licensed under CC BY-NC-SA 4.0

Dissemination Plan

Dissemination is about how I want the project to reach people once it is finished. For NanoJam, I want it to live as both a finished object that people can see and try, and as a set of files that other makers can build on.

Future plans

NanoJam started as a single object, but I would like it to grow:

Modular firmware — the current firmware is tightly tied to my exact hardware. I want to refactor it so people can swap out the OLED, the encoder, or the audio amp and still have the project work.

Open call for skins — the rotating disc interface lends itself well to custom artwork. I would love for the community to design and share their own disc graphics.

Wireless variant — adding Bluetooth audio output would make it possible to use NanoJam with wireless headphones, which fits the handheld, on-the-go nature of the device.

Workshop kit — at some point I would like to turn NanoJam into a workshop kit that beginners can assemble in a weekend, since the build touches on PCB assembly, 3D printing, and embedded firmware all in one project.



Why open? Honestly, almost everything I learned in Fab Academy came from people who documented their projects openly — instructor pages, past student documentation, forum posts, GitHub repos. NanoJam owes a real debt to that openness. Releasing the project under CC BY-NC-SA is the simplest way to pay that forward, while still keeping a say in how the work is used.


Please refer to the Project Development Page for the final project progress.

References

Creative Commons

WIPO — What is Intellectual Property?

Open Source Initiative — MIT License

GNU General Public License v3

Claude - used for generating the IP diagrams and tables, and for proofreading & improvising the text - (prompt : Go through the documentation and improvise where needed without loosing the essence and writing style of the contexts).