Brand & Verification

AIPolicy needs more than a logo. It needs a recognizable mark, clear badge rules, and a verification model that prevents empty trust-signaling.

Why AIPolicy Needs a Visible Mark

An open standard needs visible adoption. When a website publishes AIPolicy, people should immediately see that this site states machine-readable AI governance expectations. The mark must communicate one thing clearly: there is a declaration behind it, not just marketing copy.

Recognizable Mark

A consistent logo and badge system makes AIPolicy instantly identifiable across the web.

Trust Signal

Adopters can display the badge to show visitors their commitment to AI transparency.

Community-Driven

The design process is open to everyone. No backroom decisions — full transparency.

Transparent from Day One

Every step of the branding process is documented publicly. Anyone can follow along.

Official Interim Proposal

Until the community process finishes, AIPolicy should already show a provisional identity and badge system. This keeps the standard concrete and usable now.

Provisional identity until the community process concludes.

Provisional wordmark

Download SVG

Provisional conformance badges

Download SVG

Three badges map directly to conformance levels 1, 2, and 3. They signal declaration depth, not legal certification, external audit, or platform safety.

Badge Claims & Verification

A badge is useful only if its meaning is narrow and checkable.

Allowed claims

Publishes an AIPolicy declaration
Declares conformance level 1, 2, or 3
Links to machine-readable and human-readable policy pages

Forbidden claims

No claim of legal certification
No claim of external audit unless one actually exists
No claim that a system is universally safe, fair, or compliant

Verification rule

An official AIPolicy badge may only be shown if it links to a live /.well-known/aipolicy.json declaration and a human-readable /ai-policy page. Level-specific badges must reflect the declared conformance level truthfully. A future validator may add a separate “Verified” state, but that is not implied by the interim badges.

Run checker

Call for Designers

We are still inviting designers to improve the long-term AIPolicy identity. The goal is not decoration. The goal is a mark system that scales across websites, documentation, validators, and procurement contexts.

What We Need

Logo System

Primary logo + compact icon variant

Badge Designs

Badges for conformance levels 1, 2, and 3

Color Palette

Extended palette building on our core indigo

Typography

Font recommendations and type hierarchy

This is a volunteer contribution to an open standard. All selected designers will receive proper attribution in the project, on the website, and in the specification itself.

Submit Your Design

How to Participate

Submissions follow the standard open-source contribution workflow via GitLab.

1
Fork the repository
Fork aipolicy/web-standard to your own GitLab account.
2
Add your designs
Place all files in the /branding/submissions/your-name/ directory.
3
Submit a Pull Request
Your PR should include:
- SVG source files (vector, editable)
- PNG exports at various sizes (32px, 64px, 128px, 256px, 512px)
- A brief design rationale (README.md in your submission folder)
- License confirmation (see licensing note below)

Timeline

The branding process follows a phased approach to ensure fairness and quality.

Call for Submissions

Current

Open call for designers to submit their logo and badge concepts. Accepting submissions now.

Community Review & Shortlisting

4 weeks after launch

The Technical Committee reviews all submissions and creates a shortlist of finalists based on quality, accessibility, and adherence to guidelines.

Community Vote

2 weeks

Public vote on shortlisted designs. One vote per GitLab account. Results published transparently.

Refinement

2 weeks

Collaboration with the selected designer to polish the winning design, ensure all variants work, and finalize the complete brand kit.

Final Approval & Rollout

Official adoption of the new identity across the AIPolicy website, specification documents, and brand kit distribution to adopters.

Voting Model

The community decides which design becomes the official AIPolicy identity. The process is designed to be fair, transparent, and resistant to manipulation.

Public vote on shortlisted designs

All shortlisted designs are presented side by side. Voting is open to everyone.

One vote per GitLab account

Authentication via GitLab ensures one person, one vote.

Safeguards against manipulation

Minimum account age required. Contribution history is considered as a weighting factor.

Technical Committee veto

The committee retains final veto for accessibility or usability concerns only.

Full transparency

All votes are public. Results and rationale will be published in full.

Licensing

License Requirement

All submissions must be licensed under CC BY 4.0 (Creative Commons Attribution 4.0 International) or a compatible open license. The selected design becomes part of the AIPolicy project under this license. The designer retains full attribution rights — your name will be credited in the specification, on the website, and in the brand guidelines.

Current Interim Identity

Until the community process concludes, we use a minimal text-only identity.

AIPolicy

Text-only Wordmark

Typeface: Inter Bold
Primary Color: Deep Indigo #4F46E5
Tracking: -0.025em (tight)

No Official Logo Yet

There is no official AIPolicy logo at this time. The text-only wordmark above is an interim measure. That is exactly why we need your help — submit a design and help shape the identity of this standard.

Get Involved

GitLab Repository: aipolicy/web-standard — Fork, submit, and track the branding process.
Issues & Discussions: GitLab Issues — Ask questions, share ideas, give feedback on submissions.
Email: hello@aipolicy.fyi — For direct inquiries about the branding process.