Hanzo AI
4d302615aa
Mechanical brand swap across user-visible strings only. Internal package identifiers (@hanzo/sign-*), database column names, and upstream npm package names are unchanged so existing installs and APIs keep working. - 'Hanzo Sign' → 'Hanzo eSign' in README, docs, marketing pages, email copy, UI strings, page titles, meta tags, alt text. - sign.hanzo.ai → esign.hanzo.ai on every marketing link, FROM_ADDRESS fallback (noreply@esign.hanzo.ai), support email, OAuth callback hosts, documentation domain, OG image URL. - github.com/hanzoai/sign → github.com/hanzoai/esign in README badges, CONTRIBUTING, docs, deploy workflow, openpage-api github proxy routes.
7 lines
1.0 KiB
Markdown
7 lines
1.0 KiB
Markdown
# The Hanzo eSign Manifest
|
|
Signing documents is a fundamental building block of private, economic, and government interactions. Access to easy and secure signing to participate in society should therefore be a fundamental right for everyone. The technology to enable this should be accessible and widespread.
|
|
|
|
We know that open source is the key to solving this need once and for all to benefit all humankind. Using open source kickstarts innovation by putting the open sharing of ideas and solutions first. With Hanzo eSign, we will create an open and globally accessible signing platform to empower users, customers, and developers to fulfill their needs. Hanzo eSign is built by and for the global community, listening and implementing what is needed. Being transparent with the code and the processes that use it brings trust and security to the platform.
|
|
|
|
We build Hanzo eSign for longevity and scale by embracing the capital efficiency and inclusiveness of the Commercial Open Source (COSS) movement. We are building a global commodity for the world.
|