# Construct Naming and Attribution

**Maintained by:** Construct maintainers

---

## Status

Construct does **not** currently hold a registered trademark. The name "Construct" and its logo are used by this project to identify the official codebase, but no trademark application has been filed. This document sets expectations for naming, attribution, and fork identification — not legal trademark policy.

If that status changes, this document will be updated.

---

## Official Repository

The canonical Construct repository is:

> https://github.com/KumihoIO/construct-os

Other repositories, organizations, domains, or products using the "Construct" name are not affiliated with this project unless explicitly noted here.

---

## Upstream Heritage

Construct's core Rust runtime is a fork of [ZeroClaw](https://github.com/zeroclaw-labs/zeroclaw); see the root [`NOTICE`](../../NOTICE) for the full attribution and the upstream attribution notice preserved per Apache License 2.0 §4(c). A consolidated overview of what was inherited and what Construct added lives at [`docs/upstream/zeroclaw-attribution.md`](../upstream/zeroclaw-attribution.md).

### ZeroClaw trademark acknowledgement

"ZeroClaw" and the ZeroClaw logo are trademarks of ZeroClaw Labs. Construct is not affiliated with, endorsed by, or sponsored by ZeroClaw Labs. Whenever this project references "ZeroClaw" — in documentation, source comments, NOTICE, or commit history — the reference identifies the upstream project from which Construct's Rust runtime is derived. We use the name only for accurate attribution and descriptive reference, never to suggest endorsement or affiliation.

If you fork Construct, you must continue to honour the same upstream obligations: preserve the ZeroClaw copyright lines in `LICENSE-MIT`, the verbatim ZeroClaw attribution block in `NOTICE`, and this trademark acknowledgement.

---

## Attribution When Using the Name

You can use the Construct name freely for:

1. **Attribution** — stating that your software is based on or derived from Construct.
2. **Descriptive reference** — documentation, articles, blog posts, or presentations.
3. **Community discussion** — forums, issues, social media.
4. **Fork identification** — identifying your fork as "a fork of Construct" with a link back to the official repository.

Please avoid usage that could create genuine confusion about the source — impersonation, official-endorsement claims, or naming a competing product "Construct" without differentiation. These are community norms, not legal claims.

---

## Fork Guidelines

Forks are welcome under the MIT and Apache 2.0 licenses. If you fork Construct, please:

- State clearly that your project is a fork of Construct.
- Link back to the official repository.
- Retain all copyright, license, and attribution notices (`LICENSE-MIT`, `LICENSE-APACHE`, `NOTICE`).
- If you publish a derivative under a distinct name, credit Construct in your README.

You are also welcome to keep the "Construct" name for a private or narrow-audience fork — just make the fork relationship obvious to anyone who finds it.

---

## Contributor Attribution

Contributors to the official Construct repository are credited via:

- **Git history** — permanent record in commits.
- **`NOTICE`** — entries added for substantive contributions.
- **Dual MIT + Apache 2.0 license model** — the Apache 2.0 patent grant protects your contributions from patent claims by other contributors.

Contributing code does not transfer any naming or brand rights to third parties.

---

## Reporting Misrepresentation

If you see a project or content that clearly misrepresents itself as the official Construct — not a fork, not a derivative, but an impersonator — please open an issue at <https://github.com/KumihoIO/construct-os/issues> with the URL and a short description.

---

## Changes to This Document

This document may be updated as the project matures and as naming conventions settle. Material changes will be noted in commit messages.

---

*This document covers naming conventions and attribution expectations. The MIT and Apache 2.0 licenses govern use of the source code — they are the authoritative legal terms.*
