provenote

Brand And Domain Boundary

This page records the current repo-side brand and domain decision for Provenote.

In plain language: the product brand is still Provenote. A future .ai domain can help people find it, but it should not automatically force a repo, package, CLI, or MCP rename.

Current Brand Decision

product brand: Provenote
repo name: keep current repo naming
package / CLI / MCP script names: keep current technical names until a real brand decision is finalized

Why This Is The Current Call

The strongest public truth in this repository is not the top-level domain. It is the product shape:

auditable outputs
source-grounded drafts
research threads
verified outcomes
MCP compatibility through a first-party server

That means the safest current strategy is:

keep Provenote as the primary name
treat any future .ai domain as a landing, redirect, or campaign domain
avoid implying that domain choice alone changes the product’s maturity

What This Page Does Not Claim

This page does not claim:

that provenote.ai is currently owned or configured
that the repository should be renamed now
that package, CLI, or MCP script names should be rewritten before the brand decision is truly settled

Naming Guardrails

If a future domain is added, keep these boundaries:

domain choice is a distribution decision, not product proof
vendor or platform names stay descriptive, not co-branded
do not imply official partnerships through naming
do not rename technical surfaces just to mirror a marketing URL

External Window Boundary

Decision area	Current safe reading	What must happen outside the repo
GitHub homepage target	the current homepage can stay on the repo-owned docs index without changing the technical brand	owner decides later whether the canonical public front door should stay there, move to a docs site, or move to a custom domain
custom domain or redirect	no custom domain is claimed here	owner secures the domain and configures DNS or redirects
trademark / naming clearance	`Provenote` remains the current product name in repo truth	owner or counsel confirms whether a stronger external brand move is safe
marketplace / directory / partner naming	keep all current language in the compatibility-or-non-claim bucket	separate platform submission or formal agreement is required before changing public wording

This site is open source. Improve this page.