feat: trademark terms on /brand, and name Makisuo, Inc. as the owning entity - #385
Merged
Conversation
JeremyFunk
force-pushed
the
feat/brand-trademark-terms
branch
from
August 10, 2026 13:56
9633531 to
d765241
Compare
… entity The brand page granted use of the artwork with no boundary on it: "take what you need, no permission required" and nothing about the name. On an FSL project that points the wrong way. The licence hands a forker all of the code and none of the marks, but the page most likely to be read by whoever is forking said only that the assets were free. FSL-1.1-ALv2 already withholds trademarks in its own Trademarks clause, and the Apache 2.0 it converts to withholds them again in section 6, so section 05 is a restatement for people who will never open LICENSE rather than a new grant. It also states the other half explicitly: describing what you built is protected nominative use, and a policy that pretended otherwise would be unenforceable. Scoped to what a rebranded fork actually turns on. Licence-is-not-a-trademark, no use in product names or domains or handles, no implied endorsement, and revocability. Deliberately not here: a merchandise ban and a standalone registration clause, both of which appear in well under half of the comparable policies (Rust, CNCF, Grafana, HashiCorp, Docker, Mozilla, PSF, PostgreSQL) and neither of which bears on the fork case. Mark modification is already covered four times over by section 04. The ownership record named five different parties. Terms and Privacy said "Makisuo LLC", the root LICENSE said "David Granzin", three package LICENSEs said "Maple Tech Labs", clickhouse-builder said "Maple", and the footer said "(c) 2026 Maple. All rights reserved." The company is incorporated, so the two documents that actually bind users named an entity that does not exist. Every one of them now reads "Makisuo, Inc.", which also makes the "we" in the FSL Trademarks clause resolve to the party the brand page names. Vendored copyright is untouched: lib/llm stays with opencode and lib/thinking-orbs with Jakub Antalik. The footer's "All rights reserved" is dropped rather than reworded. It is a Buenos Aires Convention formality that has conferred nothing since 2000, and it contradicted the FSL badge rendered 12px to its right. The string is now locale-neutral, so the ja and ko footers no longer carry untranslated English. Editing a copyright line asserts ownership rather than transferring it. This assumes the founder IP assignment to the company has actually been executed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
JeremyFunk
force-pushed
the
feat/brand-trademark-terms
branch
from
August 10, 2026 13:59
d765241 to
2080525
Compare
🍁 Maple PR previewNote Preview resources were removed when this pull request closed. Final commit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds section 05 — Terms to
/brand(and its/brand.mdtwin), and reconciles the legal entity name across the whole repo.Why the section
/brandgranted the artwork with no boundary: "take what you need — no permission required, and no need to ask first", and nothing at all about the name. On a source-available project that points the wrong way. The licence hands a forker every line of the code and none of the marks, but the page most likely to be read by whoever is forking said only that the assets were free.FSL-1.1-ALv2already withholds trademarks in its own Trademarks clause, and the Apache 2.0 it converts to withholds them again in §6. So this is a restatement for people who will never openLICENSE, not a new grant. It also states the other half out loud: describing what you built ("a fork of Maple", "built on Maple", "compatible with Maple") is protected nominative use, and a policy pretending otherwise would be unenforceable and would read as bluster.Scoped to what a rebranded fork actually turns on:
Deliberately not included: a merchandise ban and a standalone trademark-registration clause. Both appear in well under half of the comparable policies surveyed (Rust, CNCF/Linux Foundation, Kubernetes, Grafana, HashiCorp, Docker, Mozilla, PSF, PostgreSQL), and neither bears on the fork case. Mark modification is already covered four times over by section 04.
Register is closer to PostHog than to Docker, which is the right reference class for this page. Rust's 2023 trademark-policy backlash is the documented failure mode for over-lawyering a brand page.
The ownership record named five different parties
TermsContent.astro×3,PrivacyContent.astro×1LICENSE(FSL-1.1-ALv2)packages/{effect-sdk,browser,alchemy-maple}/LICENSElib/clickhouse-builder/LICENSEmessages/{en,ja,ko}.jsonbrand.astro,brand.md.tsalchemy-maple,clickhouse-builderpackage.jsonauthorThe company is incorporated, so Terms and Privacy — the two documents that actually bind users, including the limitation-of-liability clause — were naming an entity that does not exist. That is the most serious item here.
Updating the root
LICENSEalso matters structurally: the FSL defines Licensor generically as "The party offering the Software", so the Notice copyright line is what identifies them. The "we" in its Trademarks clause now resolves to the same entity the brand page names.Vendored copyright is untouched —
lib/llmstays with opencode,lib/thinking-orbswith Jakub Antalik.The footer
© 2026 Maple. All rights reserved.was two problems in one line: Maple is a product, not a legal person, and "all rights reserved" contradicts theFSL-1.1 → Apache 2.0badge rendered 12px to its right in the same flex row."All rights reserved" is dropped rather than reworded: a Buenos Aires Convention formality, obsolete since 2000, and the badge already does the licensing work accurately. Side benefit, the string is locale-neutral, so the
jaandkofooters no longer carry untranslated English.src/paraglide/messages/*.jsare regenerated. They are tracked despite paraglide writing its own.gitignore, so they have to stay in sync with the message JSONs.Reviewer note
Editing a copyright line asserts ownership; it does not transfer it. This change assumes the founder IP assignment to the company has actually been executed. If it hasn't, the paperwork is the real fix and these lines should follow it rather than lead it.
Still not addressed
Makisuo/maple(~60 references) and the real remoteMapleTechLabs/maple(twopackage.jsons, one workflow comment).getmaple.dev(legal@,privacy@) while the brand page useshello@maple.dev.Verification
bun run --filter=@maple/landing build→ 109 pages, exit 0Makisuo, Inc.renders correctly in the builtindex,terms,privacy, andbrandpages, and inbrand.mdMakisuo LLC,David Granzin, orMaple Tech Labsremaining in anyLICENSE,package.json,.astro, or.tsoutsidenode_modulesInc..anywhere; no surviving "All rights reserved"package.jsons and all three message JSONs still parse; the©escape style is preserved🤖 Generated with Claude Code