Back to Equivox v1.0

Proposals

Equivox's core differentiating feature is its proposal system: a structured way for an idea to evolve into a formal company proposal through community support.

Each step pairs a heading and description with a decorative 3D preview of the Equivox UI. Those previews are skipped in screen reader navigation and are not interactive for assistive technology—the text beside each preview is authoritative.

Support

The proposal flow starts in Support. Users can support a proposal once they verify they own shares in the target company. We gated this for credibility, adding real ownership weight behind momentum.

Verification can happen through brokerage connection or a dedicated Proof of Ownership upload page. To avoid aggressive early friction, users can postpone verification until Signatures, only completing it once a proposal has meaningful traction.

When the creator-defined support goal is reached, the proposal automatically advances to the next phase through async backend state transitions.

Drafting

Ends in10:42:19

Refine the proposal while it's gathering support. The highest-voted draft is selected at the deadline.

Top Rated

Drafting

The second phase is collaborative Drafting, where users co-author the proposal letter that will be sent to the company. An initial AI draft is generated from the proposal title/body and supporting web context.

Anyone can create a draft, and anyone can fork an existing draft. Draft titles act as concise summaries of what changed, so iterations can be compared quickly.

Draft cards include upvote/downvote controls. At the end of the Drafting timer, the top-voted draft is selected as the final letter. To improve momentum, drafting is also enabled during Support while backing builds.

Signatures & Submission

These phases were intentionally less sophisticated at the time because platform traction was low. If a proposal showed clear momentum, the plan was to harden these flows quickly.

Signatures were designed as symbolic, non-binding endorsements where supporters could draw or type their signature. The final letter would include named supporters to humanize demand and demonstrate backing.

Submission was designed as a response/status tracker for company communication. That tracking layer was scoped but not fully implemented in v1.