# Brand Architecture

Status: working decision.

## Decision

Use the domain already owned:

```text
voxonlabs.com/evercommons
```

Use the public naming stack:

```text
VoxonLabs
  Voxon Shield (working name for the reusable trust layer)
  EverCommons (application #1)
```

## Roles

- **VoxonLabs** is the parent lab, studio, or incubator identity.
- **Voxon Shield** is the working name for the reusable trust, identity, authentication, and safety layer.
- **EverCommons** is the first public application and movement built under VoxonLabs.
- **EverCommons Social** is the first product name until a separate consumer brand is justified.
- **EverCommons Foundation** is a future stewarding structure, not a current public claim.

## Why Not "The Open Source Foundation"

"The Open Source Foundation" is too generic for this project and creates avoidable confusion with existing open-source institutions and naming patterns. It also undersells the actual mission, which is broader than open-source code: privacy, creator economics, capacity-gated growth, transparent money, and public benefit.

EverCommons is more specific for the first application. VoxonLabs leaves room for Shield, social, identity, cloud, messaging, or other public-interest services later.

## Domain Guidance

For now, do not buy another domain. The zero-cost rule wins.

Recommended paths:

- `voxonlabs.com` for the parent homepage.
- `voxonlabs.com/evercommons` for the public campaign page.
- `docs/RFC-0002-VOXON-SHIELD.md` for the Shield architecture while the project remains zero-cost and pre-code.
- `github.com/<org>/evercommons` for the public repository.
- `github.com/VoxonLabs/evercommons` as the assumed repository URL in the current static site.
- `hello@voxonlabs.com` only after mail is configured.
- `security@voxonlabs.com` only after a private security mailbox exists.

## Inspiration References

EverCommons can publicly say it learns from or respects public-interest technology such as Signal, GitHub, VideoLAN, and other open-source communities.

Use language like:

```text
Inspired by public lessons from Signal, GitHub, VideoLAN, and open-source maintainers.
```

Avoid:

```text
Signal/GitHub/VideoLAN supports EverCommons.
```

These names are nominative references only. No endorsement, partnership, sponsorship, or compatibility claim exists unless there is explicit written permission.

## Legal Boundary

EverCommons is a working name pending formal clearance. Before broad public launch, complete trademark, company registry, domain, app-store, social-handle, and package-registry checks in target markets.

Do not claim that a foundation exists until the entity exists. Until then, use language like:

```text
EverCommons is a public-benefit project incubated by VoxonLabs.
```

Avoid:

```text
The EverCommons Foundation operates...
```
