Proposal phases

Proposal Phases

To show the direction clearly, I shipped real components so you can feel the style and motion. This page outlines what is live, what I am proposing for Phase 0 and Phase 1, and how we evolve it together.

This is a live prototype. Text and numbers are placeholders and have not been verified. For best experience, view on desktop - mobile performance may vary and has not been tested on the main website.

Review next steps Sketch the plan

TLDR 01

Premium public energy

Make the public site feel premium, mysterious, and credible.

TLDR 02

Holder command hub

Give holders a single surface for ITF reports, tools, and signals.

TLDR 03

Simple stack, fast cadence

Keep the stack lean so we can iterate weekly without friction.

Mission snapshot

Lay the foundation, keep the cadence, amplify the order.

These cards capture the near-term mission: the outcomes we must hit, the principles that keep the work honest, and the surfaces already in motion.

Primary outcomes for MVP

  • Public homepage that tells the story in seconds and converts to Request a Cloak.
  • Lore section that showcases the art and identity of the order.
  • Gated ITF area with member logins, report views, and a basic update feed.
  • A light hub that surfaces what matters now across Discord and Telegram.

Guiding principles

  • Signal over noise. Every pixel supports credibility or conversion.
  • Motion with purpose. Subtle microinteractions, low CPU, high polish.
  • One home. Centralize the rituals we already run across X, Telegram, and Discord.
  • Low friction. Ship small, validate, then expand.

Home

  • Premium dark aesthetic with clean sections and CTAs that fit the brand.
  • Animated touches, more motion planned around the hooded figure.
  • ITF preview section with current stats and an animated dashboard visual.

Lore

  • Route that highlights Row’s artwork and the Cloak narrative.
  • Intended to grow into a living archive for every Cloak who creates.

ITF (demo)

  • Gated route concept with unique login per Cloak.
  • Supports cumulative cohort metrics and per-cloak detail views.
  • Concept for a persistent feed so reports and notices live in one place.

Timeline

Phase by phase, with the proof and protections baked in.

Hover or tap each phase to see the deliverables, acceptance guardrails, and the signals that tell us when to move forward.

Phase 0

Discovery & Alignment

Lock style, information architecture, and data boundaries so Phase 1 ships clean.

Focus

Design system + data rules

Output

Route contracts + copy frame

Tempo

Set up weekly iteration loop

Deliverables

Design system v1

  • Color tokens, gradients, glass surfaces, borders, radii, shadows.
  • Motion system: durations, easing, when to animate and when not to.
  • Icon set and animation library shortlist.

Site map and route contracts

  • Routes: /, /itf, /lore, /hub, /tools, /pillars, /network, /scarcity, /join, /brand, /legal.
  • For each route: purpose, audience, success metric, API needs.

ITF data rules

  • What is public, what is holders-only, what is per-holder private.
  • Access roles: council, cloak holder, guest.
  • Redaction policy for public views.

Content outline and copy frame

  • Headline and CTA copy for each section below.
  • Legal footers and risk language.

Build plan for Phase 1

  • Tasks, acceptance criteria, and a short burn chart.

Acceptance criteria

  • Alignment on data visibility, the route list, and starting copy.
  • Signed-off animation palette and performance budget.
  • No open questions that block MVP delivery.

Route details & copy frames

Every surface has a job. Here is the script for each.

/

Home

Hero

  • Heading: Cloak DAO.
  • Subheads: A limited order of one hundred. Data-built conviction. Measurable edge.
  • Primary CTA: Request a Cloak. Secondary CTA: Enter the ITF.

ITF preview

  • Heading: The ITF is Cloak DAO’s Inflection Point Indicator Trading Fund.
  • Subcopy: Outsiders glimpse the headlines. Insiders receive executed plays, on-chain proofs, and quarterly distributions.
  • Metrics: Capital at work, Payouts sent, Performance this year.
  • CTA: View full ITF report.

What we do

  • Copy: We engineer a full stack execution engine for Solana. Internal data surfaces trigger the moves, the collective trades together, and every playbook is documented for the mantle.
  • Feature cards: Cloak Capital, Council, Cloak College, Ambient signal loop.

Membership

  • Heading: Exclusive Membership.
  • Sub: No public mint. Seats rotate only when a Cloak exits so the desk stays disciplined and aligned with treasury expansion.
  • Meter: Seats remaining. CTA: Request a Cloak.

Partners

  • Heading: Strategic collaborators.
  • Blurbs for desks, treasury leads, governance alliances, builders, and educators.
  • CTA: See all partnerships.

Footer risk

  • Notice: High risk investment. Past performance does not guarantee future results. Only invest what you can afford to lose.

/lore

Lore

Hero

  • Heading: The Cloaks do not merely tell stories. They weaponize lore.
  • Sub: Every artwork preserves a victory. This is the archive and memory palace of the order.

Grid

  • Filters: Season, artist, tag, medium.
  • Card microcopy: Title, edition, short caption.
  • CTA: Explore Lore and Gallery.

Detail

  • Fields: Artwork, narrative excerpt, field report tie-in, artist, cloak id, on-chain link.
  • CTA: Submit art to the archive.

/itf

ITF (gated)

Auth

  • Wallet or email based login. Role set to holder by default after verification.

List

  • Table: Date, window, status, PnL summary, tags, link to report.

Report

  • Tabs: Cohort Summary and My Detail.
  • Attachments: CSV or JSON reports, screenshots, or visual of trade flow.
  • CTA: Subscribe to notices.

Privacy modes

  • Open cohort aggregate.
  • Per-cloak private.
  • Council elevated access when required.

/hub

Hub

Purpose

  • One dashboard for what matters now so a busy Cloak can catch up in 60 seconds.

Blocks

  • Today’s summary: top five items pulled from Discord and Telegram.
  • Pins: council or desk pins with expiry.
  • Signals: upcoming windows, recent IPI triggers, deadlines.
  • Digest: daily or weekly email or DM summary.

/tools

Tools

Purpose

  • Index of internal tools and community builds.

Blocks

  • Featured tools with short copy and access level.
  • Submit a tool link for builders.
  • Tag filters: data, charts, bots, research, automation.

/pillars

Pillars

Copy points

  • Autonomous Signal Mesh: chain native data, macro feeds, sentiment surfaces routed into trades.
  • Institutional Risk Spine: hedges, stop bands, multisig governance.
  • Synchronized Liquidity: windowed deposits and withdrawals so the cohort trades as one book.

/network

Network

Copy points

  • Directory of collaborators and desks.
  • Short bios and links.
  • Contact path for vetted partners.

/scarcity

Scarcity

Copy points

  • Seats overview and rotation rules.
  • How to request a cloak.
  • History of seat changes.

/join

Join

Copy points

  • Step 1 Request. Step 2 Verify. Step 3 Match. Step 4 Access.
  • FAQ accordions and legal footers.
  • CTAs: Request a Cloak, Full joining guide.

Delivery mechanics

Technical spine, metrics, and risk guardrails.

Everything below keeps the build predictable and defensible while the order weighs in.

Technical plan

Stack

  • SvelteKit 5 on Vercel.
  • Auth: Firebase or Supabase with role claims.
  • Data: Firestore or Postgres for reports, notices, and content.
  • Automation: n8n workflows for Discord and Telegram summary ingestion, daily digests, alert pings.
  • Storage: Vercel Blob or Firebase Storage for report files and media.
  • Analytics: Vercel Analytics or Plausible.
  • CI: Preview deploys on every PR.

Animation

  • Lazy load with IntersectionObserver.
  • Respect prefers reduced motion.
  • Performance budget: each animation under 300 KB, total per view under 800 KB.

Security & privacy

  • Strict CSP with no inline scripts; allow data: only for images if required.
  • Role-based access to ITF content.
  • Audit log for admin changes.

Risks & mitigations

  • Data sensitivity

    Mitigate with strict roles and redaction modes.

  • Scope creep

    Keep Phase 1 tight. Everything else rolls into Phase 2.

  • Motion overuse

    Ship with a motion checklist and a budget per view.

Next steps

  1. 1 Approve Phase 0 scope and decisions.
  2. 2 Approve Phase 1 deliverables and acceptance criteria.
  3. 3 Lock roles for ITF access and decide on privacy mode for per-cloak data.
  4. 4 Provide initial content: three to five ITF reports, ten artworks, partner list, council bios.
  5. 5 I start building the MVP branch and post previews for review.

Button copy library

Request a CloakEnter the ITFView full ITF reportExplore Lore and GalleryExplore the PillarsSee all partnershipsSubmit art to the archiveSubmit a toolSubscribe to notices

Optional Phase 2 ideas

  • Member directory with call signs and verified links.
  • Real-time signal widgets on the homepage.
  • Per-member notification settings and alert rules.
  • On-chain proof viewer tied to reports.
  • Public changelog and RSS.