Context
Came up during a licensing review (open source vs. closed source for the engine). Conclusion was to keep packages/core MIT — the commerce model already separates the paid surface (Packs, Pro/Team sync, distribution) from the engine, so code licensing isn't the actual moat.
The real gap: MIT grants no trademark rights. Nothing currently stops a fork from competing for the ContextCake name. A DCO now covers contribution provenance (#71); trademark registration is the other half — it protects the name and brand regardless of what happens to the code license, and is comparatively cheap.
Action
Not a code change — this is a business/legal task for @siracusa5 to pursue outside the repo (e.g. USPTO filing or equivalent for the relevant jurisdiction). Filing here as a tracked follow-up so it doesn't get lost, not something an AI contributor should attempt.
Context
Came up during a licensing review (open source vs. closed source for the engine). Conclusion was to keep
packages/coreMIT — the commerce model already separates the paid surface (Packs, Pro/Team sync, distribution) from the engine, so code licensing isn't the actual moat.The real gap: MIT grants no trademark rights. Nothing currently stops a fork from competing for the ContextCake name. A DCO now covers contribution provenance (#71); trademark registration is the other half — it protects the name and brand regardless of what happens to the code license, and is comparatively cheap.
Action
Not a code change — this is a business/legal task for @siracusa5 to pursue outside the repo (e.g. USPTO filing or equivalent for the relevant jurisdiction). Filing here as a tracked follow-up so it doesn't get lost, not something an AI contributor should attempt.