Page cover
For the complete documentation index, see llms.txt. This page is also available as Markdown.

FOUNDER DECISION BRIEF

Record clear strategic decisions, owners, conditions, and next actions.

Meeting: 5 August 2026 Purpose: Record clear strategic decisions, owners, conditions, and next actions Status: Pre-meeting decision sheet


Decision Principle

The founders are not being asked to approve token price, PC/SP conversion ratios, cash-out fees, public-token backing, reserve ratios, DEX/CEX listing, DeFi, or yield products.

They are being asked to decide the strategic direction, boundaries, ownership, and resources.


Decision 1 — Product-Led Strategic Transition

Does BGC × iBLOOMING approve a shift from reward-led acquisition toward measurable demand for physical products, digital products, content, education, profiling, and AI-enabled services?

Recommendation: Approve.

Conditions or notes:


Decision 2 — Web3 Login Implementation

Do the founders authorize Yuku and the engineering team to implement the approved WEB3LOGIN specification?

Recommendation: Approve.

Required before kickoff:

  • named engineering lead;

  • implementation timeline and budget;

  • actual authentication-topology verification;

  • canonical user-ID confirmation;

  • architecture checkpoint with Prof. NOTA;

  • security and acceptance plan.

Owner:

Target date:


Decision 3 — Existing-System Tokenization Closure

Do the founders agree that membership, PC, SP, LTS, rewards, pools, and payouts will not be tokenized under the archived Whitepaper and Tokenflow drafts?

Recommendation: Approve closure.


Decision 4 — Public Token Status

Select one:

Recommendation: Continue as separate research only.

Required boundary:

A future public token must not be funded by affiliate entry, distributed as recruitment compensation, used to pay existing obligations from new buyers, or marketed with yield, buyback, price-support, or appreciation promises.


Decision 5 — Product Pilot Selection

Select at least one physical and one digital pilot.

Physical

Digital

Recommendation: One product passport and one digital access pass.


Decision 6 — Product Metric Separation

Do the founders approve separate reporting for membership entry, direct product sale, non-affiliate customer, affiliate product purchase, PC redemption, repeat purchase, subscription retention, content completion, gross margin, refund, and fulfillment?

Recommendation: Approve.


Decision 7 — Resource Ownership

Do the founders agree that no workstream may proceed without an accountable owner and sufficient resources?

Area
Named Owner

Business decision

Product

Operations

Finance/accounting

Data

Engineering

Legal/tax

Document/change control

Recommendation: Approve.


Decision 8 — Financial-Product Boundary

Do the founders agree that this program will not create or distribute the following through the BGC affiliate network?

Recommendation: Approve boundary.


Decision 9 — Prof. NOTA’s Role

Proposed role:

Product and Web3 Transformation Consultant

Proposed scope:

  • product technology;

  • commerce and distribution systems;

  • blockchain-suitability analysis;

  • AI enablement;

  • product ownership;

  • access and credentials;

  • traceability;

  • architecture;

  • pilot design;

  • founder decision support.

Explicitly excluded without a new mandate and resources:


Decision 10 — Phase-2 Program

Do the founders authorize preparation of:

BGC × iBLOOMING Product-Led Systems Program 2026–2027 — Practical Blockchain and AI Integration for Product, Commerce, Access, Distribution, and Trust

Recommendation: Approve concept. Finalize only after the meeting record is accepted.


Draft Founder Resolution

The BGC × iBLOOMING Founders acknowledge the completion of the Phase-1 business-rules documentation, Web3 Login architecture, SIMALPHA working MVP, data preparation, and preliminary simulation reporting.

The founders acknowledge that current evidence does not support tokenization of existing membership, Purchase Credit, Sales Point, LTS, rewards, pools, or payouts.

The founders approve Web3 Login as a separate infrastructure implementation track and approve a strategic transition toward measurable product demand, commerce, access, distribution, ownership, and trust.

Any future public-token research will remain separate from the affiliate reward engine and will require separate economic, legal, tax, accounting, technical, and founder approval.

This program will not create or distribute a new deposit, yield, DeFi, DEX, CEX, or fundraising product through the BGC affiliate network.

Resolution status

Amendments:


P.S. Read this document freely for information and guidance. Do not redistribute or restate—no quotes, summaries, paraphrases, or derivatives—without prior written permission from Prof. NOTA. Sharing the link is allowed. So, share the link, not the text. Do not discuss or re-tell the contents in any form—written, spoken, or recorded—without prior written permission.


Last updated