Intellectual Property

There was a long stretch of history in which "who does this belong to?" had no good answer for anything you couldn't put in a warehouse. Land and machines settle the question by themselves, because when someone takes them the owner no longer has them. Names, drawings, writing and code behave differently. Someone can copy the whole thing and the original sits exactly where it was, which makes the claim of having been harmed hard to even phrase. Two years of work could be lifted in three days and there was no obvious ground to stand on.

The discomfort showed up in two directions. In one, something a company made walks out the door. A name that took years of advertising to plant in people's heads gets used by another company, and customers who came looking for one product land on another. In the other, something someone else made walks in. A chunk of code gets pasted in on a deadline, conditions were attached to it, and the fact surfaces the week before a contract closes.

The second direction causes more accidents than the first. Taking someone's work requires a person to decide to do it. Using someone's work without knowing requires nobody to mean any harm at all — a search result near the top of the page and a copy-paste on a busy afternoon will do it.

Pagedeck got caught on exactly this once. The enterprise plan had a name, a logo draft and a set of help articles before anyone checked whether the name was free, and it turned out an identical mark was already registered in the same category of goods. Grace ordered the search three weeks before launch, and renaming the plan cost another two. Run earlier, the same check would have taken an afternoon. Nothing about the search got harder in those three weeks; the only thing that changed was how much work was already sitting behind the name.

Intellectual property is the umbrella that organizes the institutional answer to all of this. Different kinds of creations get different regimes, and each regime states in advance what it protects, from what moment, and for how long. For a company the term resolves into two ongoing jobs: knowing which rights sit on the things you made, and checking which conditions sit on the things you borrowed. Both are cheap before you build and expensive once you are selling, which is why this field runs on scheduled checks near the front of a plan rather than on responses after the fact.

The terms under this heading fall into two groups. One covers the rights that attach to what your company makes. The other covers the conditions that come attached to what other people made. The first group is what you use to defend yourself; the second is what keeps you from causing an incident.

There are four rights. They divide by what they protect and by how the right comes into existence. That second question splits them cleanly in half. A trademark and a patent exist only after you file an application and it survives examination. A copyright and a trade secret have no application process at all. For the first pair, the whole job is timing — a right nobody filed for never appears. For the second pair, the right already exists, so the job is knowing who holds it and how carefully it has been handled.

1. Trademark — an exclusive right to a product or company name and its logo, inside a declared category of goods and services. It comes from filing with the patent office and passing examination; using a name for years without registering generally does not create one. Because registration is tied to a category, the same word often sits registered to different owners in unrelated industries. If you have named a software product, the question that matters is whether something similar is already registered in that category.
2. Copyright — the right that attaches to expression a person created: code, documents, design files, images, prose. It arises the moment the work is made, with no registration step, which is the sharpest contrast with trademarks. What it covers is narrower, though. Copying someone's code verbatim runs into it; looking at what a feature does and writing your own version does not. Inside a company the live question is rarely who made something but whether the right was transferred to the company. A logo produced by an outside contractor stays with the contractor unless the agreement says otherwise.
3. Patent — the right to exclude others from a technical invention for a fixed period. You file, you are examined, and in exchange for the exclusivity the invention is published for anyone to read. That trade is the thing to weigh first: a patent only makes sense for something you are willing to disclose. The process also costs far more time and money than the two rights above, and registration can take years.
4. Trade secret — information inside the company that has value precisely because it hasn't been disclosed. Customer lists, the internal rules behind pricing, an algorithm you never published. There is nothing to register, and in exchange you have to show evidence of having treated it as a secret: access controls on the files, confidentiality commitments signed at hire. Left in a folder anyone can open, even genuinely valuable information is hard to protect. The protection here is a byproduct of how the company behaves day to day rather than a certificate it can point at, which makes this the one right of the four that decays quietly when nobody is watching.

There are three license terms. This side deals with borrowed work, so it is about conditions rather than rights.

5. Open source license — the document stating what you must do to use publicly available software. Public does not mean unconditional; it means permitted as long as you meet the conditions. The common ones are mild, usually asking you to carry the author's name and the license text somewhere in the product, and a list tucked under a settings screen satisfies them. The difficulty is that these documents are not interchangeable. The same phrase covers licenses that want an acknowledgment and licenses that want your source code, so treating them as one category means eventually picking up a heavy one by accident.
6. Copyleft — the strictest family of those conditions. It requires that whatever you build from the code be released under the same terms. The intent is to keep what was given freely in circulation, but inside a commercial product it reads as a risk that your own code becomes publishable too. When code like this turns up in a feature you already sell, the realistic options narrow to ripping it out and rebuilding. The severity also depends on how the code is used: something a customer never receives sits differently from something shipped inside the product they install, and that distinction is the first thing an engineer checks once such a library is found.
7. License compliance — the work of listing every external component in your product and verifying that each one's conditions are being met. It needs both a gate for new arrivals and a sweep over what is already there. Enterprise customers sometimes ask for the list as a document during contract work, so a team that hasn't kept one ends up assembling it under deadline. A product of any size pulls in hundreds of external components, and most of them arrived because something else you chose depended on them, which is why counting by hand stops working early.

The two groups meet inside a single product. Your screens and code carry copyright, the name on those screens carries a trademark, and the code contains other people's open source. Neglect the first four and you have no footing when someone copies you. Neglect the last three and you have nothing to say except that you didn't know.

"Has anyone run a trademark search on this name? Worth checking before we commission the logo."

Check while the name can still be changed. After design files and help articles exist, reversing costs several times more.

"What's the license on that library? If it's copyleft we can't use it for this feature."

Pulling that code in could put our own code on the table, so let's find another option.

"I'd keep this as a trade secret rather than file for a patent. The method is easy to copy once it's published."

A patent publishes the method, and if publication alone makes it reproducible, the exclusivity is worth less than what you give up.

At Pagedeck the phrase surfaces most often in two places: the meeting where a new plan gets its name, and the week before an enterprise contract closes. In the naming meeting Ravi brings three candidates and Grace searches each one in the same category of goods. If one is already taken it comes off the list on the spot, before any design work has been paid for.

The pre-contract meeting runs the opposite direction. The customer's review questionnaire has a field for every external component in the product and its license. Theo goes through the libraries to fill it in, and when he finds something with heavy conditions, Sofia has to push the signing date to buy time to replace that code. A team that maintains the list fills the field in a day. A team that doesn't spends two weeks, and those are two weeks with the contract sitting still, which pushes the revenue back by the same amount.

The most common mistake is reading public code as free code that can be used however you like, with no distinction between one license and another. It downloads at no cost and installs with one command, so the reading is understandable. What it actually is, is permission granted in exchange for conditions rather than money, and those conditions range from crediting an author to publishing everything you built on top. Skip the check and the exposure accumulates quietly until the day an enterprise customer asks for the list, by which point several features sit on that code. Ten minutes to add, several people-weeks to remove.

The second one is assuming that registering a business, or buying the domain, makes the name yours. Both feel official, so it's easy to believe the name came with them. They are three separate systems and none substitutes for another. A domain is a slot you rent by getting there first, a business registration identifies a legal entity, and the right to stop others from using a name comes only from trademark registration. Teams that miss this find out after the brand is known, when changing the name also throws away the recognition that advertising paid for.