Only this pageAll pages
Powered by GitBook
Couldn't generate the PDF for 149 pages, generation stopped at 100.
Extend with 50 more pages.
1 of 100

NOTA's MARKDOWN!

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

BGC X IBLOOMING TOKEN FLOW DRAFT

Value-flow map of BGC × iBLOOMING from AS-IS to TO-BE on Base—defining PC/SP→ALPHA conversion, an append-only event model (hashed proofs), cash-out windows (KYC), and Pilot v1 parameters aligned with


Status: Archived Future-State Tokenization Hypothesis Implementation Authority: None Superseded For Decision-Making By: Master Document v1.0 and Founder Resolutions



title: "iBLOOMING × BGC — TOKENFLOW v1 (AS-IS → TO-BE)" version: "v1.0.0-draft" date: "2025-10-28" language: "EN" ties_to:

  • WHITEPAPER Doc (draft) (Outline)

  • UNDERSTANDING Doc (PC/SP definitions)

  • (Strategic Objectives)


  • PC — 100 PC = 1 USD (primary utility: BGC physical products).

  • SP — meter of reward rights; basis for periodic USD payout.

  • ALPHA — settlement layer converting PC/SP → rights; ERC-20 interface, non-transferable; mint/burn only via AlphaController (pre-iBC/iBTC).

  • iBC / iBTC — on-chain tokens activated post simulation/validation.

  • Fiat in → PC increases → spend on physical products → PC decreases. Pain points: idle PC; limited utility.

  • SP accrues from activities (LTS/RR/GR/…) → periodic USD payout. Pain points: value leaks out of ecosystem; admin dependency.

  • Periodic fiat intake & distribution; limited real-time transparency.

  • PC→ALPHA: 100 PC : 1 ALPHA; fee 0; cooldown 0.

  • SP→ALPHA: $1 : 1 ALPHA; fee 0; cooldown 0.

  • Default: ALPHA is used to spend / access / stake (internal).

  • USD payout for specific BGC components remains

  • Frequency: 4× per year (quarterly).

  • Window length: 7 days per window.

  • Minimum payout: $50.

  • Payout fee: 100 bps (1%).

Curated/limited external spending access → keeps value circulating within network.

Sinks & multipliers (classes, premium features, boosts) to absorb value on-platform.

Event list (minimal final): JoinAffiliate, MintPC, SpendPC, EarnSP/AccrueLTS, CPContribution, PoolAccrual, ConvertToALPHA, Spend/Stake/Access, CashoutWindowOpened/Closed, PayoutUSD.

Minimal columns per event (schema):

  • actor_id (string) — internal user/entity id

  • what (enum) — event type (as above)

  • amount (decimal) — numeric value of the event

Append-only: events are never edited/removed; corrections are appended as new events with ref_id linkage.

Principle: behavior-based, non-speculative; policy changes are versioned.

Sponsor Gas & Caps (v1)

  • sponsor_gas.enabled = true

  • actions_covered = [onboarding, convert_to_alpha, spend/access]

  • daily_cap_per_user ≈ $0.10

  • global_daily_budget ≈ $20

Anti-Abuse & Sybil (v1)

  • referral_cooldown_days = 1 ; max_tier1_joins_per_actor_per_day = 10

  • require_unique_device = true ; duplicate_device_limit = 2

  • audit_sample_rate_pct = 5

Settlement Rhythm (v1)

  • accrual_frequency = daily ; points_settlement_frequency = weekly

  • pool_distribution = { GPS: semiannual, WEC: quarterly, MC: monthly, GMP: monthly, GEC: monthly }

  • PC/SP→ALPHA adjustment rules (post-pilot), weekly quotas, extended cooling-off.

  • Anti-wash/self-dealing refinements; limited dispute & rollback policy.

  • ALPHA = loyalty/rights, non-transferable; free transfer disabled (controller-governed only).

  • USD payout (AS-IS) for specific BGC components continues unchanged.

  • Cash-out windows = secondary & scheduled; KYC mandatory.

  • Legal sign-off is a hard gate before any public iBC/iBTC phase.

Solution/Policy
GAP Closed
Objective
Primary KPI
Notes
  • Conversion: 100 PC → 1 ALPHA ; $1 SP → 1 ALPHA ; fee 0 ; cooldown 0.

  • Cash-Out Windows: 4×/year ; 7 days ; min $50 ; fee 1%

  • Cash-out thresholds/frequency for post-pilot; Q1/Q2 sink priorities; initial/adjusted rate-limit parameters; partner loop expansion gates.


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 . 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.


AA (Smart Account) — account abstraction wallet mapped via Wallet Registry (post Web3 Login).

AS-IS
(see UNDERSTANDING Doc).
KYC required.
  • Note: secondary, scheduled path for value to exit the ecosystem.

  • unit
    (string) — PC | SP | ALPHA | USD | count
  • timestamp (iso8601) — event time UTC

  • ref_id (string) — invoice/receipt/reference id

  • channel (string) — web/app/partner (optional)

  • data_hash (hex) — hash anchoring off-chain proof (file/url payload)

  • throttle_global = true ; pausable = true

  • wash_trade_zeroing = true ; penalty_cooling_off_days = 7

    Public messaging avoids investment language; disclose risks & usage boundaries.

    ;
    KYC = true
    .
  • Sponsor Gas Caps: ≈$0.10 / user / day ; ≈$20 / global / day ; throttle/pause enabled.

  • Anti-Abuse: referral cooldown 1 day ; 10 tier-1 joins/actor/day ; device rules ; sampling 5% ; zeroing + 7-day cooldown.

  • Settlement Rhythm: accrual daily ; points settlement weekly ; pools as listed in §4.1.

  • PC/SP→ALPHA bridge

    Gap-1

    Revenue↑, Active users↑

    ARPU, MAU/WAU

    (for simulation)

    Scheduled cash-out windows

    Gap-2

    0. Glossary (aligned with UNDERSTANDING)

    1. AS-IS (brief)

    1.1 BGC On-Ramp & PC

    1.2 BGC SP & Payout

    1.3 iBLOOMING Revenue & Rewards

    2. TO-BE (conversion via ALPHA)

    2.1 Unified Conversion (v1 Pilot)

    2.1.1 Cash-Out Windows (v1 Pilot)

    2.2 Partner Loop (phased)

    2.3 Demand Engine (iBLOOMING)

    3. Event Model (auditability)

    4. Policy & Parameters

    4.1 Pilot v1 Values (synced with WHITEPAPER)

    4.2 Placeholders to be tuned by Tokenomics

    5. Compliance & Communications Guardrails

    6. Alignment Table (Solution ↔ GAP ↔ Objective ↔ KPI)

    7. Decision Log — v1 (Pilot)

    8. Open Questions

    LIVING Doc
    Prof. NOTA

    Cost↓, Tax↓

    Cost/tx, Tax incidents

    (for simulation)

    Append-only ledger (events)

    Gap-4

    Cost↓

    Ops MTTR, Error rate

    (for simulation)

    Rate-limit + anti-abuse

    Gap-3

    Cost↓, Affiliate↑

    Ops cost, Retention

    (for simulation)

    Sinks (classes/features/boost)

    Gap-6

    Revenue↑

    On-platform GMV

    (for simulation)

    Fairness metric

    Ops-gap

    Affiliate↑, Active users↑

    Reward Gini Coefficient

    (for simulation)

    BGC X IBLOOMING WHITE PAPER DRAFT

    How BGC × iBLOOMING mirrors value flows to Base blockchain with an EventHub (append-only, hashed proofs) and structures rights/loyalty with ALPHA (non‑transferable, via AlphaController).


    Status: Archived Future-State Tokenization Hypothesis Implementation Authority: None Superseded For Decision-Making By: Master Document v1.0 and Founder Resolutions


    Integrating Loyalty, Value, and On‑Chain Transparency


    • title: Whitepaper v1 • Executive 1‑Pager

    • version: v1.0.0-draft

    • date: 2025-10-28


    Impact on the 5 Strategic Objectives ()

    • Revenue ↑: on‑platform utility drives GMV & ARPU.

    • Cost ↓: automated event ledger & rate limiting reduce operational/transaction costs.

    • Tax burden ↓: compliant internal settlement lowers taxable events.

    • Affiliate ↑: clear incentives & utilities improve activation/retention.

    • Active users ↑: unified utility + Web3 Login reduces friction.

    • Principle: behavior‑based (ALPHA simulation outcomes), not speculation.

    • Utilities & Sinks: purchase products/classes/features, premium access, staking for boost; value absorption through usage fees & event‑based burn.

    • Conversion Policy: PC/SP → ALPHA rights (default: spend/access/stake); scheduled cash‑out windows, with quotas and anti‑abuse.

    • Governance & Compliance: staged governance; jurisdictional compliance notes (separate memo).

    • 1a) ALPHA simulation → 2a) Whitepaper v1 → 3a) Tokenflow Map v1 → 4) Single Founder Sign‑Off (incl. Legal Gate) → 5) Pilot utilities iBC/iBTC → 6) Cross‑app expansion.

    • 1b) Web3 Login plan → 2b) Web3 Login implementation → 3b) Web3 Login launch → 4) Single Founder Sign‑Off (incl. Legal Gate) → 5) Pilot utilities iBC/iBTC → 6) Cross‑app expansion.

    Approve Whitepaper v1 with three open parameters to be finalized at Single Founder Sign‑Off (incl. Legal Gate): initial PC/SP→ALPHA conversion ratios, cash‑out windows policy, and Q1 sinks priorities.


    BGC × iBLOOMING mirrors value flows operating since 2023 to Base via an EventHub (append‑only) that records key events with hashed off‑chain proofs. Rights/loyalty are structured with ALPHA—an ERC‑20 interface that is non‑transferable; mint/burn occur only via an AlphaController—so value by default circulates inside the ecosystem (spend/access/stake). USD payouts for specific BGC components remain AS‑IS per the , while cash‑out windows schedule and throttle value flowing outward. The Web3 Login + Wallet Registry → Smart Account (AA) architecture sustains low‑friction UX with high auditability. After 24‑month data validation and legal sign‑off (hard gate), the public phase iBC/iBTC expands utilities across applications. This three‑act strategy targets 5 Strategic Objectives (Revenue↑, Cost↓, Tax↓, Affiliate↑, Active Users↑) with measurable KPIs, including Reward Gini Coefficient for distributional fairness. Launches are gated by a Single Founder Sign‑Off (incl. Legal Gate) prior to deployment.

    • Core problem set (six value‑flow gaps) → Solution (ALPHA → iBC/iBTC) mapped directly to the 5 Strategic Objectives.

    • Gap‑1: Limited outcome from PC/SP conversion bridge.

    • Gap‑2: Interoperability & value leakage (out of ecosystem).

    • Gap‑3: Admin dependency (manual operations).

    • Gap‑4: Low real‑time transparency (limited audit trail).

    Note: gap list refers to + ; details are condensed in the .

    • Reframe PC/SP as tokenized rights via the ALPHA settlement layer.

    • Target: default utility inside the ecosystem; cash‑out as a secondary, controlled path.

    • An internal “conversion bridge”: PC/SP → ALPHA rights → spend/access/stake across apps.

    • Value circulates longer inside; leakage outward decreases.

    • Settlement Layer (ALPHA): conversion rules, event model, rate‑limit, and audit trail.

      • ALPHA uses an ERC‑20 interface, is non‑transferable, and mint/burn only via AlphaController; free transfer is disabled (except system‑governed flows).

      • EventHub acts as an append‑only ledger with hashed proofs anchoring off‑chain documents.

    • Revenue↑ → KPI: ARPU/GMV on‑platform.

    • Cost↓ → KPI: operational cost per 1,000 transactions.

    • Tax burden↓ → KPI: fewer taxable events via compliant internal settlement.

    • Affiliate↑ → KPI: number of active affiliates; 30/90‑day retention.

    Note: baselines & targets will be populated after the 24‑month data session.

    • Principle: behavior‑based (ALPHA simulation results), not speculative.

    • Parameters: [PLACEHOLDER initial figures + periodic adjustment method].

    • Utility pools (spend/access/stake), affiliate incentives, ecosystem reserves.

    • Utilities: product purchases, feature/class access, staking for boost.

    • Sinks: usage fees, event‑based burn, premium fees.

    • PC → ALPHA: 100 PC (= $1) → 1 ALPHA; fee 0 bps; cooldown 0 days.

    • SP → ALPHA: $1 SP → 1 ALPHA; fee 0 bps; cooldown 0 days.

    • Default use of ALPHA: spend / access / stake inside the ecosystem.

    • USD payout for certain BGC components remains

    • Frequency: 4× per year (quarterly).

    • Window duration: 7 days per window.

    • Minimum payout: $50.

    • Payout fee: 100 bps (1%).

    • Staged governance; rate‑limit; policy orchestration.

    • Risk map: operational; market; compliance; reputation.

    • Anti‑Abuse & Sybil (Pilot v1): referral cooldown 1 day; max 10 Tier‑1 joins per actor/day; require_unique_device = true; duplicate_device_limit = 2; audit sampling 5%; penalties: wash_trade_zeroing = true, cooling_off 7 days

    • PC is the proof of physical‑product transactions (MLM legal requirement).

    • Affiliate membership can only be purchased with fiat (not with PC nor with tokens).

    • Legal sign‑off is required before the public iBC/iBTC launch.

    • KYC is enforced for payouts executed via cash‑out windows (Pilot v1).

    • ALPHA simulation → Whitepaper v1 → Tokenflow Map v1 → Single Founder Sign‑Off (incl. Legal Gate) → Pilot utilities iBC/iBTC → Cross‑app expansion.

    • Web3 Login Plan → Web3 Login Implementation → Web3 Login Launch → Single Founder Sign‑Off (incl. Legal Gate) → Pilot utilities iBC/iBTC → Cross‑app expansion.

    • 24‑month data sources; metric definitions; cleaning rules; reproducibility.

    • Privacy standard: PII anonymization and dataset manifest for reproducibility.

    • Cash‑out thresholds, initial conversion ratios, Q1 sinks priorities, prioritized use cases.

    • Glossary; event table; compact architecture diagram.

    Convert to ALPHA (v1)

    • pc_to_alpha.ratio = 100 PC : 1 ALPHA; fee = 0 bps; cooldown = 0 days.

    • sp_to_alpha.ratio = $1 : 1 ALPHA; fee = 0 bps; cooldown = 0 days.

    Cash‑Out Windows (v1)

    • windows_per_year = 4; window_length_days = 7; min_payout_usd = 50; payout_fee_bps = 100; kyc_required = true.

    Sponsor Gas & Caps (v1)

    • sponsor_gas.enabled = true; actions_covered = [onboarding, convert_to_alpha, spend/access];

    • daily_cap_per_user ≈ $0.10; global_daily_budget ≈ $20; throttle_global = true; pausable = true.

    Anti‑Abuse & Sybil (v1)

    • referral_cooldown_days = 1; max_tier1_joins_per_actor_per_day = 10;

    • require_unique_device = true; duplicate_device_limit = 2;

    • audit_sample_rate_pct = 5; wash_trade_zeroing = true; penalty_cooling_off_days = 7.

    Settlement Rhythm (v1)

    • accrual_frequency = daily; points_settlement_frequency = weekly;

    • pool_distribution: GPS = semiannual; WEC = quarterly; MC = monthly; GMP = monthly; GEC = monthly.

    Event list (audit trail): JoinAffiliate, MintPC, SpendPC, EarnSP/AccrueLTS, CPContribution, PoolAccrual (GPS/GMP/WEC/MC/GEC), ConvertToALPHA, SpendAccess / Stake / Vote, CashoutWindowOpened

    Minimal columns per event: actor, what, amount, unit, timestamp, refId, dataHash (anchor to off‑chain proof).


    Here's a glossary of abbreviations and terms that appear/are related in this WHITEPAPER—concise and clear.

    • AA (Smart Account / Account Abstraction): Contract-based wallet with programmable policies (e.g., sponsored gas, rate limits), mapped via the Wallet Registry.

    • Actor ID: Internal identifier for a user/entity in events.

    • ALPHA: Non-transferable ERC-20–interface loyalty/rights unit; mint/burn only via AlphaController; used for spend/access/stake.

    • AlphaController: Policy gateway for ALPHA (conversion ratios, caps, cooldowns, cash-out windows, pause).

    • Baseline/Target: Initial KPI value and future goal (filled after 24-month data session).

    • bps (basis points): 1/100 of a percent (1% = 100 bps).

    • Cash-out windows: Scheduled periods to move value out of the ecosystem (quarterly 7 days; $50 min; 1% fee; KYC).

    • Cooling-off: Temporary lock after violations.

    • Entitlement (rights): User claims/permissions backed by ledger records.

    • Event: Logged action in EventHub (e.g., MintPC, EarnSP, SpendAccess).

    • EventHub: Append-only event sink with hashed proofs anchoring off-chain documents.

    • iBC / iBTC: Post–legal sign-off on-chain utility phase (for cross-app expansion).

    • KPI (Key Performance Indicator): Core metrics (ARPU/GMV, cost per 1k actions, MAU/WAU, retention, Gini).

    • KYC (Know Your Customer): Identity verification required for cash-out payouts.

    • Ledger: System of record (here: append-only).

    • MAU/WAU (Monthly/Weekly Active Users): Distinct active users per month/week.

    • MC/GMP/GEC/GPS/WEC: See “GEC/GMP/GPS/MC/WEC (pools).”

    • Mint/Burn: Create/destroy ALPHA (controller-only).

    • MintPC / SpendPC: Events for issuing/using PC (physical-product proof).

    • Q1: First quarter (initial sinks priority).

    • Rate limit: Per-user/system frequency/volume caps.

    • Ref ID: Reference identifier linking events to invoices/docs.

    • Settlement: Periodic rollups/clearing (daily/weekly/monthly/… rhythms).

    • UNDERSTANDING Doc: Source of truth for business/marketing model & USD payout rules (AS-IS).

    • USD payout (AS-IS): Existing USD disbursements for specific BGC components; separate from ALPHA.

    • Wallet Registry: Mapping of users ↔ wallets/AA after Web3 Login.

    • Web3 Login: Unified sign-in that provisions a wallet/AA and ties identity to on-chain actions.

    • Audit sampling 5%: Randomly reviewing ~5% of events/accounts.

    • Daily cap per user ≈ $0.10; global ≈ $20: Sponsored-gas daily limits (per account and system-wide).

    • Duplicate device limit: Max accounts allowed to share one device signature.

    • Require unique device: Enforce minimum device uniqueness to deter Sybil attacks.


    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 . 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.


    Gap‑5: High tax burden from fiat‑first processes.
  • Gap‑6: BGC growth > iBLOOMING (imbalance).

  • Utility map: spend (products/services), access (features/classes), stake (commitment).
  • Transparent dashboard (append‑only ledger) for claims/entitlements.

  • Sponsor gas (active – Pilot v1): onboarding, convert_to_alpha, spend/access; per‑account daily cap ≈ $0.10; global daily cap ≈ $20; throttle/pause enabled.

  • Active users↑ → KPI: MAU/WAU across applications.
  • Fairness → KPI: Reward Gini Coefficient (distribution inequality).

  • AS‑IS
    (see UNDERSTANDING Doc).

    KYC required for every payout.

  • Note: cash‑out windows are the secondary, scheduled path for value leaving the ecosystem.

  • .
    ,
    CashoutWindowClosed
    ,
    PayoutUSD
    .
  • Append-only (ledger): Record system that only appends entries (no edits/deletes); audit-friendly.

  • ARPU (Average Revenue per User): Average revenue per user in a period.

  • AS-IS: Existing process kept unchanged (e.g., specific BGC USD payouts).

  • Audit trail: Verifiable chain of evidence/events for review.

  • Cooldown: Required wait time before re-attempting an action (v1 = 0).

  • ConvertToALPHA: Event converting PC/SP into ALPHA under policy.

  • CSV/Parquet: Data file formats for exports/analysis.

  • GEC/GMP/GPS/MC/WEC (pools): Distribution pools (GPS=semiannual; WEC=quarterly; MC/GMP/GEC=monthly) per UNDERSTANDING Doc.

  • Gini (Reward Gini Coefficient): Inequality metric for reward distribution (0 = equal, higher = more unequal).

  • GMV (Gross Merchandise Value): Gross value of transactions on the platform.

  • LTS: Long-term tally of SP for affiliate levels/analytics.

    Non-transferable: Not freely transferable between accounts (only system-governed flows).

  • Pausable / Pause–Unpause: Emergency switch to stop/start contract features.

  • PC: Proof of physical-product transaction; 100 PC = $1 baseline for ALPHA conversion.

  • Pilot v1: Initial operating configuration for the pilot phase.

  • SP: Affiliate points based on revenue (v1: $1 SP → 1 ALPHA).

  • Spend/Access/Stake: Three ALPHA utilities (purchase, feature/class access, commitment/participation).

  • Stake-to-vote: Participation/voting gated by stake (optional later phase).

  • Sybil: Abuse via multiple fake accounts to gain unfair advantage.

  • WEC/GPS/MC/GMP/GEC: See “GEC/GMP/GPS/MC/WEC (pools).”

    Throttle: Automatic throughput reduction when thresholds are exceeded.

  • Quarterly/Semiannual/Monthly: Pool distribution and reconciliation cadence.

  • language: EN

    Tokenomics (at a glance)

    Concise Roadmap

    Decisions Requested (Founders)

    • title: WHITEPAPER v1 (Outline)

    • version: v1.0.0-draft

    • date: 2025-10-28

    • language: EN

    • single_language_rule: true

    • sources_of_truth:

      • (business/marketing model)

      • (Strategic Objectives & guardrails)

    1. Executive Summary

    2. Problem Statement (Brief)

    3. Solution Overview (C → A → B)

    3.1 Concept

    3.2 Analogy

    3.3 Design (High‑Level Implementation)

    4. Tokenomics (Framework)

    4.1 Objectives ↔ KPIs

    4.2 Supply & Emission

    4.3 Distribution

    4.4 Utilities & Sinks

    4.5 Conversion Policy (PC/SP → ALPHA → iBC/iBTC)

    4.5.1 Cash‑Out Windows (Pilot v1)

    4.6 Governance & Risk

    4.7 Compliance Notes

    5. Roadmap (High‑Level)

    6. Data & Methodology

    7. Open Questions

    Appendices

    Initial Parameter List (v1 Pilot)

    Event Model (Minimal Final)

    Glossary

    A–C

    B–D

    E–H

    I–L

    M–P

    Q–T

    U–Z

    Operational terms

    UNDERSTANDING Doc
    UNDERSTANDING Doc
    LIVING Doc
    TOKENFLOW Doc (draft)
    Prof. NOTA
    LIVING Doc
    UNDERSTANDING Doc
    LIVING Doc

    2026

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202603

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    2025

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    UNDERSTANDING BGC X IBLOOMING REWARDS

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!


    Status: Final AS-IS Business and Reward Rules Reference Scope: Descriptive reference for existing BGC × iBLOOMING rules Important: This document is not a legal opinion, accounting certification, economic-health assessment, or tokenization approval.


    0. Users in BGC & iBLOOMING

    In the BGC & iBLOOMING ecosystem, a user is anyone who transacts—whether a one-time purchase, a subscription, or simply a sign-up—and uses or benefits from the ongoing operations of BGC & iBLOOMING. A user can be an individual or an organization.

    Below are the user types within the BGC & iBLOOMING ecosystem:

    Base Type
    Subtype
    Channel Provider (CP)
    Executive CP
    WEC User

    Legend: ✓ = can / yes, ✗ = can't / no

    Note on Channel Provider (CP) eligibility: A ✓ under “Channel Provider (CP)” indicates eligibility to become a CP subject to BGC & iBLOOMING program requirements (e.g., application and approval, adherence to channel policies, and ongoing compliance). It does not imply automatic CP status.

    Note on Executive CP eligibility: A ✓ under “Executive CP” indicates eligibility to become an Executive CP subject to additional requirements set by BGC & iBLOOMING (e.g., being an approved CP first, meeting elevated performance/quality thresholds, and periodic review). It does not imply automatic Executive CP status.

    Note on WEC User eligibility: A ✓ under “WEC User” indicates eligibility to become a WEC User provided the user later meets the WEC criteria (e.g., the USD 10,000 payout threshold within 60 days, as defined elsewhere). It does not imply automatic WEC status.


    Bloo Global Company (BGC) utilizes an Affiliate Membership system with five levels. Each level can only be purchased and paid for with fiat (USD). After purchasing and paying with fiat, the user officially becomes an Affiliate User.

    ➡️ Important Notes:

    • The Entry Fee is the fiat on-ramp into the BGC system.

    • After paying with fiat, the Affiliate User receives Purchase Credit.


    • Definition: Purchase Credit is not only the counterpart of the fiat paid, but also proof of Affiliate Membership as well as a credit balance to buy physical products at BGC. It functions as an internal credit for purchasing physical products at BGC.

    • Ratio: 100 PC = $1.00 USD (fixed, non-volatile).

    • Functions:

      • Serves as evidence that BGC sells physical products (MLM legal requirement).

    ➡️ Additional Notes:

    • At BGC, Affiliate Membership cannot be purchased/paid using Purchase Credit. Affiliate Membership can only be purchased with fiat. In short, within BGC: fiat in → PC increases → physical product out → PC decreases.


    • Definition: A WEC User is an additional status available only to Affiliate Users at Pioneer or Special level whose accumulated payout from BGC rewards based on Sales Points-Referral (RR) and Generation Reward (GR)-reaches $10,000.00 within 60 consecutive days.

    • Start Date & Window: The Affiliate User selects the starting date for the 60-day window. If the $10,000.00 threshold is not reached within that window, the attempt is considered failed and reset, and the user may select a new starting date for a subsequent attempt.


    Sales Points (SP) are a notional unit (not a coin) used to measure the rewards an Affiliate User will receive, calculated and distributed using Life Time Scholar (LTS) as the base reference.

    Whenever a new Affiliate User is added, Sales Points equal to 70% of the Entry Fee are generated. These Sales Points are called Life Time Scholar (LTS).

    Affiliate Level
    LTS (SP)

    ➡️ Fixed Value: 1 SP = $1.00 (for calculation; non-volatile). ➡️ Detailed SP acquisition & distribution mechanics will be elaborated in the following chapter.


    1. BGC Referral (RR) & Generation Rewards (GR)

    2. BGC Miracle Cash (BGC-MC)

    3. BGC Global Pool Sales Points (GPSP)

    4. BGC WEC Global Pool

    Payout frequency: monthly unless otherwise stated.


    Scenario: Today: X brings U to join (U is the new join). Yesterday: Y brought X to join. Two days ago: Z brought Y to join. Rule: X = Referral (Tier 1), Y = Generation (Tier 2), Z = Generation (Tier 3).

    Notes

    • Percentages apply to LTS by U according to the level U joined.

    • Displayed SP are rounded to 2 decimal places for consistency.


    Scenario: Today: U joins as an Affiliate User at 07:47 PM. Rule: After U joins, U earns 0.1% of the new user’s LTS for each new Affiliate User who joins after U, capped at the first 10 new users following U’s join time.

    Notes

    • Percentages apply to LTS based on the level of each new user who joined after U.

    • Displayed SP are rounded to 2 decimal places for consistency.


    Scenario: Today: U joins as an Affiliate User. Rule: After U joins, 15% of U’s LTS is collected into the Global Pool Sales Points (GPSP).

    U’s Join Level
    LTS by U
    (GPSP)

    Notes

    • Percentages apply to LTS based on the level of new users who joined.

    • Displayed SP are rounded to 2 decimal places for consistency.

    • Distribution mechanics: to be finalized; this section specifies accumulation only.


    Scenario: Today: U joins as an Affiliate User. Rule: After U joins, 3% of U’s LTS is collected into the WEC Global Pool.

    U’s Join Level
    LTS by U
    WEC Global Pool

    Notes

    • Percentages apply to LTS based on the level of new users who joined.

    • Displayed SP are rounded to 2 decimal places for consistency.

    • Eligibility: only among WEC Users.


    • At iBLOOMING, besides GiM sign-ups and iMATRIX plans (one-time purchase), the products offered are digital (e-courses, e-books, etc.) from Channel Providers (CP) or CP Users.

    • A CP User can be an individual or an organization recruited by an Affiliate User to supply content sold as digital products on iBLOOMING.

    • A CP User can obtain Executive CP status if their accumulated total income based on Rebates at iBLOOMING, within 60 consecutive days, has reached $10,000.00.

    ➡️ Additional Notes:

    • All products offered by iBLOOMING can only be purchased and paid for with fiat (USD). Purchase Credit (PC) cannot be used to purchase/pay for iBLOOMING products.


    1. iBLOOMING Link Reward (LR)

    2. iBLOOMING Miracle Cash (iBLOOMING-MC)

    3. iBLOOMING Channel Provider Reward (CPR)

    4. iBLOOMING GiM Referral Reward (GRR)

    Payout frequency: monthly unless otherwise stated.

    • For a $100.00 purchase/transaction:

      • 70% → CP User Revenue → 70% × $100.00 = $70.00

      • 30% → iBLOOMING Revenue → 30% × $100.00 = $30.00

        • The $30.00 (100% iBLOOMING Revenue) is allocated as:

    • For each GiM sign-up:

      • $4.00 → GiM Referral Reward (GRR):

        • $3.00 → First-Tier

        • $0.80 → Second-Tier

    • For each Foundation iMATRIX plan purchase:

      • $0.95 → iMATRIX Referral Reward (iRR):

        • $0.60 → First-Tier

        • $0.25 → Second-Tier


    • Definition: Paid to an Affiliate User whenever a user buys a CP User’s digital product on iBLOOMING using the Affiliate User’s link.

    • Rate: 10% of iBLOOMING Revenue of each CP User’s digital product purchase.

    • Example (for a $100.00 purchase/transaction):

    Payout Frequency: Monthly (aggregated). If, in a month, 100 users each make 3 purchases averaging $100.00, the Affiliate User’s total Link Reward is: 100 users × 3 purchases × $100.00 × 30% × 10% = $900.00.


    • Definition: Paid to users (not limited to Affiliate Users or CP Users). After a user buys a CP User’s digital product on iBLOOMING, they receive Miracle Cash each time another user buys a CP User’s digital product—capped at 10 subsequent purchases.

    • Rate: 1% of iBLOOMING Revenue of each CP User’s digital product purchase.

    • Example (for a $100.00 purchase/transaction):

    Payout Frequency: Monthly (aggregated). If, in a month, a user makes 1 purchase and, after the purchase, there are 10 subsequent purchases by others, each averaging $100.00, then the user’s total Miracle Cash is: 1 purchase × 10 subsequent purchases × $100.00 × 30% × 1% = $3.00.


    • Definition: Paid to an Affiliate User who brings a CP User into iBLOOMING, when the CP User’s digital product is sold/purchased by users.

    • Rate: 5% of iBLOOMING Revenue in the first year, then 2.5% in the second year and beyond.

    • Example (for a $100.00 purchase/transaction):

    Payout Frequency: Monthly (aggregated), as long as the CP User’s digital product continues generating revenue.


    • Definition: Paid to an Affiliate User whenever a user signs up for GiM using the Affiliate User’s link. The reward is tiered with two pathways: Individual and Organization.

    • Rates (per sign-up, same totals for both pathways):

      • Individual Referral: $3.00 → First-Tier Affiliate User; $0.80 → Second-Tier Affiliate User; $0.20 → WEC User

    Payout Frequency: Monthly (aggregated). If there are 100 GiM sign-ups in a month (from any mix of Individual/Organization referrals), the GRR then:

    • Tier 1 (Affiliate User/Organization): $3.00 × 100 = $300.00

    • Tier 2 (Affiliate User): $0.80 × 100 = $80.00

    • Tier 3 (WEC User Pool): $0.20 × 100 = $20.00 → split equally among all WEC Users (e.g., 50 WEC Users → $0.40 each)


    • Definition: Paid to an Affiliate User whenever a user purchases an iMATRIX plan via the Affiliate User’s link. The reward is tiered with two pathways: Individual and Organization, based on the plan type. (iMATRIX plans are one-time purchases.)

    • Rates (per plan purchase; same totals for both pathways):

      • Foundation: $0.60 → Tier 1; $0.25 → Tier 2; $0.10 → WEC User Pool (Tier 3)

    Payout Frequency: Monthly (aggregated). If the month has 250 Foundation, 150 Pro, and 100 Expert plan purchases (from any mix of Individual/Organization referrals), then the iRR totals are:

    • Tier 1 (Affiliate User/Organization): ($0.60 × 250) + ($5.00 × 150) + ($12.00 × 100) = $150.00 + $750.00 + $1,200.00 = $2,100.00

    • Tier 2 (Affiliate User): ($0.25 × 250) + ($2.50 × 150) + ($5.00 × 100) = $62.50 + $375.00 + $500.00 = $937.50

    • Tier 3 (WEC User Pool): ($0.10 × 250) + ($1.00 × 150) + ($2.00 × 100) = $25.00 + $150.00 + $200.00 = $375.00 → split equally among all WEC Users


    • Definition: GPS is a profit pool from iBLOOMING—including profit sourced from CP User digital product sales, GiM sign-ups, and iMATRIX plan purchases (one-time)—distributed to top-level Affiliate Users (Explorer, Pioneer, Special). GPS has three profit sources:

      1. 15% of iBLOOMING revenue from each CP User digital product purchase.

        • Example (for a $100.00 purchase):

    ➡️ Conclusion: GPS is a large-scale, cross-product profit pool (CP User digital products, GiM, iMATRIX) distributed semiannually to Explorer, Pioneer, and Special.


    • Definition: GMP is a monthly activity pool sourced only from GiM sign-ups and iMATRIX plan purchases (one-time), distributed to all WEC Users and Executive CP.

    • Sources (fixed per event):

      1. $1.00 from each GiM sign-up (goes directly to GMP).

    ➡️ Conclusion: GMP is a monthly, activity-driven pool (GiM + iMATRIX) paid equally to the current set of WEC Users and Executive CP at the payout snapshot.


    • Definition: GEC is an internal iBLOOMING committee (not publicly marketed) responsible for executive oversight—covering governance, program integrity, operations, and strategic alignment of the iBLOOMING ecosystem.

    • Sources (fixed per event):

      • $0.20 from each GiM sign-up.

    ➡️ Conclusion: GEC is a monthly, internally-governed pool that funds and rewards the executive oversight function of iBLOOMING, sourced from GiM and iMATRIX activity.


    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 . 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.


    Affiliate User

    Pioneer

    ✓

    ✓

    ✓

    Affiliate User

    Special

    ✓

    ✓

    ✓

  • Because the Affiliate User has received Purchase Credit, the company has no obligation to refund the fiat paid to BGC.

  • Permanence: Once the threshold is met within the specified 60 days, WEC User status becomes permanent.
  • Level Independence: WEC User does not replace the Affiliate User level (Pioneer or Special); it is an additional status.

  • 1,207 SP

    12% → 144.84 SP

    14% → 168.98 SP

    17% → 205.19 SP

    Pioneer

    2,012 SP

    15% → 301.80 SP

    15% → 301.80 SP

    18% → 362.16 SP

    Special

    8,050 SP

    15% → 1,207.50 SP

    15% → 1,207.50 SP

    18% → 1,449.00 SP

    New User +2

    2025/08/21 04:47 PM

    Voyager

    350 SP

    0.1% → 0.35 SP

    New User +3

    2025/08/22 11:11 PM

    Explorer

    1,207 SP

    0.1% → 1.21 SP

    New User +4

    2025/08/23 07:47 PM

    Pioneer

    2,012 SP

    0.1% → 2.01 SP

    New User +5

    2025/08/24 11:11 AM

    Special

    8,050 SP

    0.1% → 8.05 SP

    New User +6

    2025/08/25 01:01 PM

    Special

    8,050 SP

    0.1% → 8.05 SP

    New User +7

    2025/08/26 10:10 AM

    Special

    8,050 SP

    0.1% → 8.05 SP

    New User +8

    2025/08/27 04:47 PM

    Pioneer

    2,012 SP

    0.1% → 2.01 SP

    New User +9

    2025/08/28 11:11 PM

    Explorer

    1,207 SP

    0.1% → 1.21 SP

    New User +10

    2025/08/29 04:47 PM

    Voyager

    350 SP

    0.1% → 0.35 SP

    New User +11

    2025/08/30 07:47 PM

    Pathfinder

    70 SP

    0 SP

    New User +12

    2025/08/31 10:10 AM

    Pathfinder

    70 SP

    0 SP

    2,012 SP

    15% → 301.80 SP

    Special

    8,050 SP

    15% → 1,207.50 SP

    2,012 SP

    3% → 60.36 SP

    Special

    8,050 SP

    3% → 241.50 SP

    Executive CP status is permanent once the threshold is reached within the specified 60 days.

    iBLOOMING iMATRIX Referral Reward (iRR)
  • iBLOOMING Global Profit Sharing (GPS)

  • iBLOOMING Global Movement Pool (GMP)

  • iBLOOMING Global Executive Committee (GEC)

  • 10% → Link Reward (LR) for the Affiliate User → 10% × $30.00 = $3.00

  • 10% = 1% × 10 users → Miracle Cash (iBLOOMING-MC) for the user → 10% × $30.00 = $3.00

  • Channel Provider Reward (CPR):

    • 5% → CPR for the Affiliate User in the first year → 5% × $30.00 = $1.50

    • 2.5% → CPR for the Affiliate User in the second year and beyond → 2.5% × $30.00 = $0.75

  • 15% → Global Profit Sharing (GPS) → 15% × $30.00 = $4.50

  • Remainder → iBLOOMING Profit:

    • 60% → iBLOOMING Profit in the first year → 60% × $30.00 = $18.00

    • 62.5% → iBLOOMING Profit in the second year and beyond → 62.5% × $30.00 = $18.75

  • $0.20 → Third-Tier

  • $1.00 → Global Profit Sharing (GPS)

  • $1.00 → Global Movement Pool (GMP)

  • $0.20 → Global Executive Committee (GEC)

  • Remainder → iBLOOMING Profit

  • $0.10 → Third-Tier

  • $0.10 → Global Profit Sharing (GPS)

  • $0.30 → Global Movement Pool (GMP)

  • $0.05 → Global Executive Committee (GEC)

  • Remainder → iBLOOMING Profit

  • For each Pro iMATRIX plan purchase:

    • $8.50 → iMATRIX Referral Reward (iRR):

      • $5.00 → First-Tier

      • $2.50 → Second-Tier

      • $1.00 → Third-Tier

    • $1.50 → Global Profit Sharing (GPS)

    • $2.00 → Global Movement Pool (GMP)

    • $0.40 → Global Executive Committee (GEC)

    • Remainder → iBLOOMING Profit

  • For each Expert iMATRIX plan purchase:

    • $19.00 → iMATRIX Referral Reward (iRR):

      • $12.00 → First-Tier

      • $5.00 → Second-Tier

      • $2.00 → Third-Tier

    • $3.00 → Global Profit Sharing (GPS)

    • $5.00 → Global Movement Pool (GMP)

    • $1.00 → Global Executive Committee (GEC)

    • Remainder → iBLOOMING Profit

  • 70% → CP User Revenue → 70% × $100.00 = $70.00
  • 30% → iBLOOMING Revenue → 30% × $100.00 = $30.00

    • From this $30.00 (100% iBLOOMING Revenue), 10% is allocated as Link Reward for the Affiliate User → 10% × $30.00 = $3.00

  • 70% → CP User Revenue → 70% × $100.00 = $70.00

  • 30% → iBLOOMING Revenue → 30% × $100.00 = $30.00

    • From this $30.00 (100% iBLOOMING Revenue), 1% is allocated as Miracle Cash for the user → 1% × $30.00 × 10 users = $3.00

  • 70% → CP User Revenue → 70% × $100.00 = $70.00

  • 30% → iBLOOMING Revenue → 30% × $100.00 = $30.00

    • From this $30.00 (100% iBLOOMING Revenue):

      • 5% is allocated as CPR for the Affiliate User in the first year → 5% × $30.00 = $1.50

      • 2.5% is allocated as CPR for the Affiliate User in the second year and beyond → 2.5% × $30.00 = $0.75

  • Pool (Third-Tier).
  • Organization Referral: $3.00 → First-Tier Organization; $0.80 → Second-Tier Affiliate User; $0.20 → WEC User Pool (Third-Tier).

  • WEC User Pool (Third-Tier) Note: WEC User = World Executive Club. The $0.20 Third-Tier amount does not go to a single upline; it is paid into the WEC User Pool and split equally among all WEC Users at payout time.

  • Pro: $5.00 → Tier 1; $2.50 → Tier 2; $1.00 → WEC User Pool (Tier 3)

  • Expert: $12.00 → Tier 1; $5.00 → Tier 2; $2.00 → WEC User Pool (Tier 3)

  • WEC User Pool (Tier-3) Note: WEC User = World Executive Club. The Tier-3 amount does not go to a single upline; it is paid into the WEC User Pool and split equally among all WEC Users at payout time.

  • 70% → CP User revenue = $70.00

  • 30% → iBLOOMING revenue = $30.00

  • From this $30.00, 15% → GPS = $4.50

  • $1.00 from each GiM sign-up (fixed; goes directly to GPS).

  • $0.10 / $1.50 / $3.00 from each iMATRIX plan purchase (Foundation / Pro / Expert, fixed; goes directly to GPS).

  • Eligible Levels: Explorer, Pioneer, Special only.

    • Explorer → 2 shares

    • Pioneer → 3 shares

    • Special → 15 shares

  • Payout Frequency: Every 6 months (unlike LR, iBLOOMING-MC, GRR, iRR, CPR, which are monthly).

    • Illustrative distribution:

      • Eligible Affiliates at payout: 550 Explorer, 300 Pioneer, 200 Special

        • Total shares = (550 × 2) + (300 × 3) + (200 × 15) = 5,000

      • GPS pool (semiannual):

        • From CP User digital products = $10,000,000.00

        • From GiM sign-ups = $15,000,000.00

        • From iMATRIX plan purchases = $25,000,000.00

      • Value per share = $50,000,000.00 ÷ 5,000 = $10,000.00

      • Estimated rewards:

        • Explorer = 2 × $10,000.00 = $20,000.00

        • Pioneer = 3 × $10,000.00 = $30,000.00

        • Special = 15 × $10,000.00 = $150,000.00

  • $0.30 / $2.00 / $5.00 from each iMATRIX plan purchase (Foundation / Pro / Expert, respectively; goes directly to GMP).

  • Eligible Recipients: All WEC Users and Executive CP present at the monthly payout snapshot.

    • Distribution rule: Equal split per recipient (unless a different weighting is formally adopted later).

  • Payout Frequency: Monthly (aggregated). Illustrative distribution:

    • Monthly activity: 1,000 GiM sign-ups; 600 Foundation, 300 Pro, 100 Expert iMATRIX plan purchases

    • GMP pool total: ($1.00 × 1,000) + ($0.30 × 600) + ($2.00 × 300) + ($5.00 × 100) = 1,000.00 + 180.00 + 600.00 + 500.00 = **$2,280.00**

    • Eligible headcount at snapshot: 120 WEC Users + 30 Executive CP = 150 recipients

    • Payout per recipient: $2,280.00 ÷ 150 = **$15.20**

  • $0.05 / $0.40 / $1.00
    from each
    iMATRIX
    plan purchase (
    Foundation / Pro / Expert
    ).
  • Eligibility & Membership:

    • Appointment-based and internal to iBLOOMING; membership may change over time by company decision.

    • Not tied to Affiliate levels; separate from WEC User/Executive CP statuses.

  • Distribution:

    • Monthly (aggregated).

    • Equal split among active GEC members at the payout snapshot (unless a different weighting is formally adopted later).

  • Illustrative distribution:

    • Monthly activity: 2,000 GiM sign-ups; 1,000 Foundation, 400 Pro, 150 Expert iMATRIX plan purchases

    • GEC pool total: ($0.20 × 2,000) + ($0.05 × 1,000) + ($0.40 × 400) + ($1.00 × 150) = 400.00 + 50.00 + 160.00 + 150.00 = **$760.00**

    • Active GEC members at snapshot: 10

    • Payout per member: $760.00 ÷ 10 = **$76.00**

  • General User

    —

    ✓

    ✓

    ✗

    Affiliate User

    Pathfinder

    ✓

    ✓

    ✗

    Affiliate User

    Voyager

    ✓

    ✓

    ✗

    Affiliate User

    Explorer

    ✓

    ✓

    Level

    Entry Fee (USD)

    Pathfinder

    $100.00

    Voyager

    $500.00

    Explorer

    $1,725.00

    Pioneer

    $2,875.00

    Special

    $11,500.00

    Pathfinder

    70 SP

    Voyager

    350 SP

    Explorer

    1,207 SP

    Pioneer

    2,012 SP

    Special

    8,050 SP

    U’s Join Level

    LTS by U

    X (Tier 1)

    Y (Tier 2)

    Z (Tier 3)

    Pathfinder

    70 SP

    10% → 7.00 SP

    0% → 0.00 SP

    0% → 0.00 SP

    Voyager

    350 SP

    10% → 35.00 SP

    13% → 45.50 SP

    16% → 56.00 SP

    New User

    Join Time

    Join Level

    LTS by New User

    Miracle Cash (BGC-MC) for U

    New User U

    2025/08/19 07:47 PM

    Pathfinder

    70 SP

    0 SP

    New User +1

    2025/08/20 01:01 AM

    Pathfinder

    70 SP

    0.1% → 0.07 SP

    Pathfinder

    70 SP

    15% → 10.50 SP

    Voyager

    350 SP

    15% → 52.50 SP

    Explorer

    1,207 SP

    15% → 181.05 SP

    Pathfinder

    70 SP

    3% → 2.10 SP

    Voyager

    350 SP

    3% → 10.50 SP

    Explorer

    1,207 SP

    3% → 36.21 SP

    1. Affiliate & Entry

    2. Purchase Credit (PC)

    3. World Executive Club (WEC)

    4. Sales Points (SP) & Life Time Scholar (LTS)

    What are Sales Points (SP)?

    Life Time Scholar (LTS) — by Affiliate Level

    5. Rewards Based on Sales Points (SP) at BGC

    Rewards based on Sales Points (SP) at BGC are:

    5.1 Referral (RR) & Generation (GR) — per New Join (U)

    5.2 Miracle Cash (BGC-MC) — Monthly (paid on the 15th of the following month)

    5.3 Global Pool Sales Points (GPSP) — Monthly (paid on the 15th of the following month)

    5.4 WEC Global Pool — Quarterly (paid on 15 Jan / 15 Apr / 15 Jul / 15 Oct)

    6. Channel Provider (CP)

    7. Rewards Based on Rebates at iBLOOMING

    Rewards available include:

    Revenue Split for digital products from a CP User:

    Revenue Distribution for GiM sign-ups:

    Revenue Distribution for iMATRIX plan purchases (one-time):

    7.1 Link Reward (LR)

    7.2 Miracle Cash (iBLOOMING-MC)

    7.3 Channel Provider Reward (CPR)

    7.4 GiM Referral Reward (GRR)

    7.5 iMATRIX Referral Reward (iRR)

    7.6 Global Profit Sharing (GPS)

    7.7 Global Movement Pool (GMP)

    7.8 Global Executive Committee (GEC)

    Prof. NOTA

    ✗

    Explorer

    Pioneer

    Pioneer

    Total GPS = $50,000,000.00

    202506

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202510

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    ARCHIVED, OiOi!

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202507

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202511

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    LICENSE, OiOi!

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    2025

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202610

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202508

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202510

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202512

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202601

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202608

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202511

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202607

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202509

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202508

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    LICENSE_en-GB

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Copyright © 2021–present Prof. NOTA and Prof. NOTA Inc. All rights reserved.

    This software, including all associated files, documentation, structure, and naming conventions, is an original and proprietary work of Prof. NOTA and Prof. NOTA Inc., protected under international law.


    🟣 PERMITTED USES

    Permission is strictly limited to:

    • Educational purposes

    • Exclusively for women and children

    • Under the direct guidance and explicit supervision of Prof. NOTA or Prof. NOTA Inc.

    No part of this software may be altered, redistributed, or republished without prior written authorisation.


    The following actions are STRICTLY PROHIBITED:

    • Reverse engineering, modification, repackaging, or renaming,

    • Commercial use, resale, sublicensing, or third-party integration,

    • Usage on any public or private platform without explicit permission.


    This software is provided “AS IS”, without warranties of any kind. Prof. NOTA and Prof. NOTA Inc. disclaim all liability for damages or legal consequences arising from its use or misuse.


    For licensing, permission requests, or official collaboration:

    📧 nota@endhonesa.com 🌐 https://nota.endhonesa.com/

    This license file must remain intact in all authorised distributions.

    🚫 PROHIBITED USES

    ⚠️ WARRANTY DISCLAIMER

    📮 CONTACT

    202512

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    202509

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    LICENSE_yue-Hant-HK

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    版權所有 © 2021–至今 Prof. NOTA 同 Prof. NOTA Inc. 保留所有權利。

    呢份軟件,同其相關文件、結構、命名方式,全屬於 Prof. NOTA 同 Prof. NOTA Inc. 嘅原創作品,受法律保護。


    🟣 限定用途授權

    只准用喺以下情況:

    • 教育用途

    • 只限女士同小朋友使用

    • 需要 Prof. NOTA 或 Prof. NOTA Inc. 嘅正式陪同或授權

    冇經授權,唔可以改、唔可以散播、唔可以再發佈。


    以下使用方式一律禁止:

    • 改碼、逆向工程、重包裝、

    • 商業用途、再分發、授權第三方、

    • 任何形式公開或私人平台上使用。


    呢個軟件係以「原樣」提供,冇任何保證。 Prof. NOTA 同 Prof. NOTA Inc. 唔承擔任何使用或濫用造成嘅後果。


    授權申請、查詢或合作請聯絡:

    📧 nota@endhonesa.com 🌐 https://nota.endhonesa.com/

    呢份條款文件必須保留喺所有合法發佈中。

    LICENSE_uz-Latn

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Mualliflik huquqi © 2021–hozirgi kungacha Prof. NOTA va Prof. NOTA Inc. Barcha huquqlar himoyalangan.

    Ushbu dasturiy ta'minot va unga aloqador barcha fayllar, tuzilmalar, hujjatlar va nomlash qoidalari — Prof. NOTA va Prof. NOTA Inc. mulki bo‘lib, qonun bilan himoyalangan.


    🟣 CHEKLANGAN FOYDALANISH HUQUQI

    Ruxsat etiladi faqat:

    • Ayollar va bolalar ta’limi uchun

    • Prof. NOTA yoki Prof. NOTA Inc. rahbarligida va roziligi bilan

    Dasturdan boshqa hech qanday shaklda foydalanish, o‘zgartirish, tarqatish taqiqlanadi.


    Quyidagilar QAT'IY MAN QILINGAN:

    • Teskari muhandislik (reverse engineering), kodni o‘zgartirish, qayta o‘ramlash,

    • Tijorat maqsadlarida foydalanish, sotish yoki boshqa platformalarga qo‘shish,

    • Har qanday ochiq yoki yopiq tizimlarda ruxsatsiz foydalanish.


    Ushbu dasturiy mahsulot "BORIChA" taqdim etiladi. Prof. NOTA va Prof. NOTA Inc. hech qanday kafolat bermaydi va foydalanishdan kelib chiqadigan oqibatlar uchun javobgar emas.


    Ruxsatnoma, litsenziya bo‘yicha savollar yoki hamkorlik uchun:

    📧 nota@endhonesa.com 🌐 https://nota.endhonesa.com/

    Ushbu hujjat ruxsat etilgan har qanday tarqatishda ilova qilinishi shart.

    LICENSE_ms-MY

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Hak Cipta © 2021–kini Prof. NOTA dan Prof. NOTA Inc. Segala hak cipta terpelihara.

    Perisian ini bersama semua fail berkaitan, dokumentasi, struktur, dan penamaan adalah hasil karya eksklusif milik Prof. NOTA dan Prof. NOTA Inc., dilindungi sepenuhnya oleh undang-undang.


    🟣 PENGGUNAAN TERHAD

    Kebenaran diberikan hanya untuk:

    • Tujuan pendidikan

    • Khusus untuk wanita dan kanak-kanak

    • Di bawah bimbingan rasmi Prof. NOTA atau Prof. NOTA Inc.

    Penggunaan selain daripada yang dibenarkan — termasuk pengubahsuaian, pengedaran, atau penerbitan semula — adalah dilarang tanpa keizinan bertulis.


    Sebarang bentuk penggunaan berikut adalah DILARANG KERAS:

    • Kejuruteraan songsang, pengubahan kod, penjenamaan semula,

    • Penggunaan komersial, penjualan, atau integrasi ke dalam sistem lain,

    • Penempatan di mana-mana platform tanpa kebenaran rasmi.


    Perisian ini disediakan dalam bentuk “SEADANYA”, tanpa sebarang jaminan. Prof. NOTA dan Prof. NOTA Inc. tidak bertanggungjawab atas sebarang kerosakan, penyalahgunaan, atau akibat undang-undang yang timbul.


    Untuk permohonan lesen, pertanyaan, atau kerjasama rasmi:

    📧 nota@endhonesa.com 🌐 https://nota.endhonesa.com/

    Dokumen ini WAJIB disertakan dalam semua edaran rasmi yang dibenarkan.

    LICENSE_ID

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Hak Cipta © 2021–sekarang Prof. NOTA dan Prof. NOTA Inc. Seluruh hak dilindungi.

    Perangkat lunak ini beserta seluruh file, struktur, dokumentasi, dan konvensi penamaannya adalah karya eksklusif dari Prof. NOTA dan Prof. NOTA Inc. dan dilindungi oleh hukum.


    🟣 IZIN TERBATAS

    Izin penggunaan diberikan hanya untuk:

    • Tujuan pendidikan

    • Terbatas untuk perempuan dan anak-anak

    • Dengan pendampingan resmi dari Prof. NOTA atau Prof. NOTA Inc.

    Perangkat lunak ini tidak boleh dimodifikasi, didistribusikan ulang, disalin sebagian atau seluruhnya tanpa izin tertulis dari pemilik hak cipta.


    Setiap bentuk penggunaan lain DILARANG KERAS, termasuk namun tidak terbatas pada:

    • Rekayasa balik (reverse engineering), pengubahan kode, rebranding,

    • Penggunaan komersial, penjualan kembali, atau penggabungan ke sistem lain,

    • Penggunaan di platform publik atau privat yang tidak didampingi resmi.


    Perangkat lunak ini diberikan "SEADANYA" tanpa jaminan apapun. Prof. NOTA dan Prof. NOTA Inc. tidak bertanggung jawab atas kerugian, penyalahgunaan, atau efek hukum yang ditimbulkan.


    Untuk izin, pertanyaan lisensi, atau kerja sama resmi:

    📧 nota@endhonesa.com 🌐 https://nota.endhonesa.com/

    Dokumen ini harus disertakan dalam setiap distribusi resmi yang diizinkan.

    CONTACT, OiOi!

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Welcome to this web page!

    To save everyone in 0101 Universe from any PHISHING and SCAMS, please only use all the links listed below to reach and contact . Visit and follow all these links as guidance to get any information from .

    • Prof. NOTA's Origin

    • Prof. NOTA's Deep Links

    DECISIONS OWNERS NEXT ACTIONS

    BGC × iBLOOMING Founder Meeting — Decisions, Owners, and Next Actions — 5 August 2026


    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 . 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.


    🚫 嚴禁用途

    ⚠️ 免責聲明

    📮 聯絡方法

    🚫 QAT'IY MAN QILINGAN FOYDALANISH

    ⚠️ RAD ETISH VA MA'SULIYAT

    📮 BOG'LANISH

    🚫 LARANGAN PENGGUNAAN

    ⚠️ PENAFIAN DAN TANGGUNGJAWAB

    📮 HUBUNGI KAMI

    🚫 PELARANGAN PENGGUNAAN

    ⚠️ PENAFIAN DAN TANGGUNG JAWAB

    📮 KONTAK

    Prof. NOTA

    ACTIVE, OiOi!

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Prof. NOTA's GitBook https://docs.endhonesa.com/

  • Prof. NOTA's Working Progress https://nota.endhonesa.com/

  • Prof. NOTA's Online Store https://store.endhonesa.com/

  • Prof. NOTA's SkateShop https://shop.skateshop.id/

  • Prof. NOTA's Mini Site Double-check the URL you are visiting, okay!!!! Make sure you are visiting subdomains of these TLD:

    • straight-line.org (LTS - Maintenance),

    • endhonesa.com (LTS - Active),

    • and skateshop.id (Dev - Current).

    • Prof. NOTA's Discord server https://discord.gg/5KrsT6MbFm

    • Prof. NOTA's X.com https://x.com/MyReceiptTT https://x.com/ROTYBASEdETH https://x.com/AMANDAwives https://x.com/DethWish_NFTs

    • Prof. NOTA's YouTube https://www.youtube.com/@MyReceipt/

    • Prof. NOTA's Facebook

    • Prof. NOTA's Instagram

    • Prof. NOTA's Threads

    • Prof. NOTA's Whatsapp

    • Prof. NOTA's Telegram

    Enjoy reading! Enjoy the journey and have fun following the links. Don't forget to stay alert and beware of scams!!!!


    Hi, we are Prof. NOTA!

    Regards,

    Prof. NOTA ==== 47 =======

    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.


    Prof. NOTA's Website

    Contact
    Prof. NOTA
    Prof. NOTA
    https://myreceipt.endhonesa.com/
    https://deeplink.endhonesa.com/

    Prof. NOTA's Social Network

    LICENSE_ar-AE

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    حقوق النشر © 2021–حتى الآن Prof. NOTA و Prof. NOTA Inc. جميع الحقوق محفوظة.

    هذا البرنامج، بجميع ملفاته وهيكلته وتوثيقاته وتسمياته، يُعد عملًا أصيلًا ومملوكًا حصريًا لـ Prof. NOTA و Prof. NOTA Inc.، ومحمي بموجب القوانين الدولية.


    🟣 الاستخدامات المصرح بها

    يُسمح باستخدام البرنامج فقط للأغراض التالية:

    • لأغراض تعليمية

    • خاصة بالنساء والأطفال فقط

    • تحت إشراف مباشر وتصريح واضح من Prof. NOTA أو Prof. NOTA Inc.

    لا يجوز تعديل أو توزيع أو إعادة نشر أي جزء من هذا البرنامج دون إذن كتابي مسبق.


    يُمنع منعًا باتًا القيام بما يلي:

    • فك الشيفرة أو التعديل أو إعادة التغليف أو إعادة التسمية،

    • الاستخدام التجاري، أو إعادة البيع، أو الترخيص للغير،

    • الاستخدام على أي منصة عامة أو خاصة بدون إذن رسمي.


    يتم تقديم هذا البرنامج "كما هو"، دون أي ضمانات من أي نوع. Prof. NOTA و Prof. NOTA Inc. لا يتحملان أية مسؤولية عن الأضرار أو العواقب القانونية الناتجة عن استخدامه أو سوء استخدامه.


    لطلب الترخيص، أو الاستفسارات، أو التعاون الرسمي:

    📧 nota@endhonesa.com 🌐 https://nota.endhonesa.com/

    يجب أن تظل هذه الوثيقة مرفقة بجميع النسخ الموزعة المصرح بها.

    RESUME FOR TECHNICAL DOCUMENTATION ENGINEER

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Surabaya, Indonesia · nota@endhonesa.com · +62 8563160756 · GitHub:


    Technical Documentation Engineer & Web3/Node.js builder with ~2.2 years of hands‑on Node.js/TypeScript and ~4 years of technical writing. Blends engineer’s rigor with a storyteller’s clarity: turns fast‑moving codebases into clean, living docs, examples, and release notes. Strongest work: PABRIK ROTI — a multi‑tenant, Web3‑enabled app (Next.js/TypeScript) with formal docs, versioned releases, and licensing.


    • Languages & Runtime: TypeScript, JavaScript, Node.js, Next.js

    • Docs: GitBook, Markdown, READMEs, API refs, release notes, architecture overviews

    CONSULTANT AGREEMENT

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    (for engagements with Prof. NOTA or Prof. NOTA Inc.)


    This Consultant Agreement (“Agreement”) is entered into on this ___ day of __________, 2025, by and between:

    [COMPANY NAME], a company or organization duly established and existing under the laws of ________________________, having its registered address at __________________________________ (“Client”),

    and

    [LEGAL NAME], acting in their professional capacity as Prof. NOTA or optionally on behalf of Prof. NOTA Inc., a creative technology collective and professional identity holder (“Consultant”).

    Collectively referred to as the “Parties” and individually as a “Party”.


    1.1 The Consultant agrees to provide professional services as a Web3 Consultant, with expertise in:

    REKOMENDASI FILM UNTUK V.9 & V.11

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Catatan: rekomendasi film disusun oleh v.9 untuk ditonton bersama v.11 saat jadwal movie night di rumah v.11. Disarikan dari obrolan kita (dan digabung jika ada rujukan sebelumnya).


    • WALL‑E (2008) — Bumi “kosong”; robot kecil mengajarkan tanggung jawab & cinta lingkungan. (Keluarga)

    • City of Ember (2008) — Kota bawah tanah setelah kiamat; dua anak memecahkan misteri keluar. (Petualangan)

    READ ME, OiOi!

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    The day before yesterday, I'm Prof. NOTA.

    Yesterday, we were Prof. NOTA.

    Today, anyone can be Prof. NOTA, and Prof. NOTA can be anyone.

    Tomorrow, anything can be Prof. NOTA, and Prof. NOTA can be anything.

    Not just code. Not just JavaScript, Next.js, or Tailwind.

    Every Markdown file here is software. Every note, every sentence, every poem, every silence. Even a single dot . — when written and seen — becomes software.

    FORM ISIAN KONTRAK

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Gunakan form ini untuk melengkapi bagian-bagian kosong pada Consultant Agreement antara Prof. NOTA / Prof. NOTA Inc. dengan pihak mitra atau perusahaan lain.


    • Nama lengkap perusahaan / organisasi: __________________________

    • Bentuk hukum dan negara hukum perusahaan: __________________________ (Contoh: Perseroan Terbatas, Republik Indonesia)

    🚫 الاستخدامات المحظورة

    ⚠️ إخلاء المسؤولية

    📮 للتواصل

    https://www.facebook.com/myreceiptt
    https://instagram.com/MyReceipt
    https://instagram.com/ENDHONESA
    https://instagram.com/SkateShop_ID
    https://www.threads.net/@myreceipt
    https://wa.me/message/DPRNCTJA2Q52L1
    https://t.me/MyReceiptTT
    Prof. NOTA Inc.
  • Tooling: Git, GitHub, CI, Issues/Projects, Vercel deploys

  • Web3: Thirdweb SDK, ERC‑20/721/1155 patterns, wallet flows, token gating

  • Collaboration: Asynchronous remote workflows, PR reviews, and changelog discipline


  • Technical Documentation Engineer / Web3 Engineer — Prof. NOTA Inc. Remote — 2023–Present

    • Write and maintain GitBook spaces and repo docs (README, SECURITY, PRICING, LICENSE) for Web3 apps and protocols.

    • Lead documentation for PABRIK ROTI (Next.js 15, React 19, Tailwind v4, Thirdweb v5). Authored quick‑start, feature guides, and tenant‑theming explanations. Ship versioned releases with notes.

    • Produce runnable examples and PoC snippets (token/claim pages, token‑gated perks, multi‑tenant configs) to shorten developer time‑to‑first‑success.

    • Keep docs in lock‑step with rapid code changes; align with CI/deploy events; add screenshots/diagrams when helpful.

    • Maintain changelogs and release notes cadence; socialize updates across repos.

    Open‑Source Projects & Contributions Remote — 2023–Present

    • NFT Staking App (fork & customization): Updated environment/config, app shell, and addresses for thirdweb staking example; validated flows end‑to‑end.

    • Utility repos for rarity/indexing and NFT tooling; small fixes and readme improvements across Web3 repos.


    • THE KING’S WORLD (GitBook) — Portfolio of project docs, timelines, and guides. docs.endhonesa.com

    • PABRIK ROTI — Release v.2.4.66‑travconn — Release notes (token‑gated perks page) and versioning discipline. v.2.4.66 travconn

    • Blockchain Fundamental — Tutors X Educators (GitBook) — Multi‑part tutorial series (P2P, DApps, ERC‑20/721, etc.). Blockchain Fundamental


    PABRIK ROTI — Programmed Bread Factory (multi‑tenant Web3 distribution)

    • Stack: Next.js (App Router), Node.js, TypeScript, React 19, Tailwind v4, Thirdweb SDK v5

    • What it does: Creates & distributes tokenized assets; supports tenant‑based theming, NFT explorer/claim flows, ERC‑20 claim pages, and mobile‑optimized UX.

    • Docs work: Quick‑start (yarn && yarn dev), architecture overview, feature guides, licensing/usage policy, versioned releases with notes.


    • Shipped 200+ commits across docs and code in flagship repo; instituted semantic tagging and readable release notes.

    • Bilingual/multilingual documentation & licensing (EN + ID + others) to broaden developer reach.

    • Reduced onboarding time for collaborators by supplying copy‑paste‑ready examples (env vars, config patterns, claim flows).


    Self‑directed, project‑driven engineering and documentation in Web3 and distributed systems.


    • GitBook: docs.endhonesa.com

    • GitBook: baca.endhonesa.com

    • GitHub: github.com/myreceiptt

    • Project: pabrikroti


    • Work location: Surabaya, Indonesia (remote)

    • Availability: Immediate

    • Expected annual salary: USD 74,747 (see notes prepared for application form)


    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.


    Summary

    Core Skills

    myreceiptt

    Experience

    Selected Documentation & Writing

    Highlight Project

    Achievements

    Education

    Links

    Logistics

    Tokenization

  • Cryptocurrency and blockchain infrastructure

  • Tokenomics and decentralized ecosystems

  • Other emerging technologies and creative strategy solutions as mutually agreed

  • 1.2 The Consultant shall work closely with the Client to ensure timely and thoughtful delivery of all work products.

    1.3 This Agreement is entered with the Consultant (Prof. NOTA or Prof. NOTA Inc.) as a distinct and self-sovereign entity. The Consultant’s obligations are limited to this Agreement and shall not be presumed to extend to any affiliates, sister companies, or parallel projects unless explicitly agreed upon in writing.


    2.1 Should the Consultant receive external opportunities relevant to the scope of this Agreement (e.g., from third-party clients or international entities), such engagements shall be routed through the Client if mutually agreed as part of this cooperation.

    2.2 Project execution, billing, and communications may be centralized through the Client, offering the Client the opportunity to act as a hub for strategic collaboration.

    2.3 Any exceptions shall require written consent from both Parties.


    3.1 “Prof. NOTA” is a professional persona and intellectual identity, developed as part of long-term public, creative, and technological engagements.

    3.2 The Consultant may appear publicly and publish materials using the Prof. NOTA identity, including educational content, talks, articles, and strategy-related publications.

    3.3 The legal identity of the individual representing Prof. NOTA or Prof. NOTA Inc. (e.g., [LEGAL NAME]) shall remain confidential and used only for internal/legal purposes, unless express written consent is given by the Consultant.


    This Agreement shall remain valid for an initial term of ___ months, beginning on the effective date, and may be extended upon mutual written agreement.


    The Client agrees to pay the Consultant a monthly fee of IDR [__________] (or equivalent in agreed currency), net, excluding applicable taxes.

    Payment shall be made by the [___] business day of each month to the Consultant’s designated account. All applicable tax obligations will be handled by the Client, unless otherwise agreed.


    If any physical presence or travel is required by the Client, the Client shall cover:

    • Round-trip transportation

    • Accommodation

    • Daily expenses (as approved)

    • Other reasonable costs directly resulting from Client-requested duties

    The Consultant will provide receipts as needed.


    The Consultant agrees to keep confidential any proprietary or strategic information obtained during the engagement, even after the Agreement ends.


    All deliverables, works, designs, code, and written output created by the Consultant for the Client under this Agreement shall be the exclusive property of the Client. The Consultant waives all rights to such works unless otherwise negotiated.


    9.1 Either Party may terminate this Agreement with 30 (thirty) days’ written notice.

    9.2 The Client may terminate immediately in the event of material breach, provided the Consultant fails to remedy such breach within 14 (fourteen) days.


    This Agreement shall be governed by the laws of _____________________. Disputes shall be resolved through amicable discussion. Failing that, the matter will be referred to a court or arbitration body as agreed.


    11.1 This Agreement contains the entire understanding between the Parties.

    11.2 Any amendments must be made in writing and signed by both Parties.

    11.3 No rights or obligations may be assigned without written approval from both Parties.


    IN WITNESS WHEREOF, the Parties have agreed to the terms of this Consultant Agreement as of the date first written above.


    For [COMPANY NAME] Name: __________________________ Title: __________________________ Signature: _______________________

    For Consultant [LEGAL NAME] (Professionally known as Prof. NOTA) or Prof. NOTA Inc.

    Signature: _______________________

    1. Scope of Services

    2. External Engagements

    3. Identity and Representation

    4. Term

    5. Compensation

    6. Travel and Expenses

    7. Confidentiality

    8. Intellectual Property

    9. Termination

    10. Governing Law

    11. Final Provisions

    The Mitchells vs. the Machines (2021) — “Kiamat robot” kocak; konflik ayah–anak yang hangat. (Komedi keluarga)

  • Nausicaä of the Valley of the Wind (1984) — Dunia pasca bencana ekologis; heroik & puitik. (Anime klasik)

  • Love and Monsters (2020) — Dunia monster; petualangan ringan yang fun. (Remaja/keluarga)

  • 9 (2009) — Boneka kain bertahan di dunia hancur; visual unik, agak gelap. (Remaja)

    • A Quiet Place (2018) & Part II (2021) — Keluarga bertahan hidup “tanpa suara”.

    • War of the Worlds (2005) — Ayah melindungi dua anak saat invasi alien.

    • Cargo (2017) — Ayah berjuang menyelamatkan bayinya di Australia pasca wabah.

    • Train to Busan (2016) — Ayah–anak di kereta saat wabah zombie; intens.

    • Light of My Life (2019) — Ayah melindungi putrinya pasca pandemi; sunyi & menyayat.

    • The Road (2009) — Ayah–anak menembus dunia yang sangat suram (pertimbangkan usia & mood).

    Rute nonton (opsional): Family Night: WALL‑E → City of Ember → Mitchells vs. Machines → Nausicaä. Survival Night (lebih tegang): War of the Worlds → A Quiet Place → Train to Busan → Cargo.


    • Final Destination (seri lengkap, 2000–2011) — If belum tamat, enak untuk marathon.

    • The Butterfly Effect (2004) — Thriller sci‑fi soal nasib & pilihan.

    • The Ring (2002, US) / Ringu (1998, Jepang) — Kutukan kaset; klasik tegang.

    • Saw (seri, 2004–2017) — Jebakan maut & moral choices.

    • Escape Room (2019 & 2021) — Puzzle mematikan versi modern.

    • The Cabin in the Woods (2012) — Twist meta yang bikin mikir.

    • Pengabdi Setan (2017, Joko Anwar) — Atmosferik & mencekam.

    • Sewu Dino (2023) — Mistis Jawa yang kuat.

    • Satan’s Slaves 2: Communion (2022) — Skala lebih besar, tetap menegang.

    Mini‑Marathon Horor (usulan): Final Destination (2000) → Final Destination 2 (2003) → Final Destination 3 (2006) → Escape Room (2019) → Pengabdi Setan (2017) → Satan’s Slaves 2: Communion (2022).


    • Capernaum (2018) — Anak jalanan di Beirut; tajam & humanis.

    • Minari (2020) — Keluarga imigran membangun harapan; hangat & sederhana.

    • The Pursuit of Happyness (2006) — Ayah–anak berjuang; menguatkan.

    • Indiana Jones and the Last Crusade (1989) — Dinamika ayah–anak di tengah petualangan.

    • Ford v Ferrari (2019) — Persahabatan & kerja keras di dunia balap.

    • Top Gun: Maverick (2022) — Aksi modern dengan tema lintas generasi.

    • The Intern (2015) — “Magang” senior yang hangat & ringan.

    • Mrs. Doubtfire (1993) — Ayah rela apa saja demi dekat dengan anak.

    • Keluarga Cemara (2019, Indonesia) — Versi modern cerita klasik keluarga.

    • A Beautiful Mind (2001) — Jenius & perjuangan personal.

    • Good Will Hunting (1997) — Relasi mentor–anak muda berbakat.

    • Laskar Pelangi (2008, Indonesia) — Semangat pendidikan & persahabatan.


    • Sesuaikan usia & sensitivitas: untuk judul bertanda “lebih tegang”, pertimbangkan rating & mood v.9.

    • Pilih bareng: biarkan v.9 memilih 1–2 judul tiap sesi agar merasa dilibatkan.

    • Legal & nyaman: utamakan platform resmi (kualitas gambar/subtitle, aman dari iklan/virus).


    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.


    1) Post‑Apocalypse — Ramah Anak (±9–12)

    2) Post‑Apocalypse — Lebih Tegang (Remaja ke Atas)

    3) Horor ala Final Destination

    a. Mirip Final Destination (Takdir & Kematian)

    b. Horor Adrenalin & Survival

    c. Horor Indonesia (Nuansa Lokal)

    4) Drama Keluarga & Kehidupan

    5) Aksi & Nostalgia

    6) Komedi Ringan

    7) Inspirasi & Refleksi

    Catatan Umum

    Alamat lengkap perusahaan: __________________________________________________________________

  • Nama lengkap penandatangan yang mewakili perusahaan: __________________________

  • Jabatan penandatangan: __________________________


    • Apakah kerja sama ini dijalankan oleh:

    • Nama lengkap manusia yang mewakili Prof. NOTA atau Prof. NOTA Inc.: __________________________


    • Tanggal mulai kerja sama: ____ / ____ / ______

    • Durasi awal kerja sama (dalam bulan): _______ bulan


    • Nominal gaji atau fee bulanan (net): IDR ______________________

    • Hari maksimal pembayaran tiap bulan: Hari kerja ke-___ setiap bulan


    • Negara hukum yang berlaku: __________________________

    • Kota / Badan penyelesaian sengketa: __________________________ (Contoh: Pengadilan Negeri Jakarta Selatan, Arbitrase Singapura)


    • Apakah ada materi, metode, atau IP yang dikecualikan dari pasal hak cipta? __________________________________________________________________

    • Apakah ada pengaturan fleksibilitas kerja atau metode kerja khusus? __________________________________________________________________


    Form ini bersifat internal dan digunakan untuk melengkapi template kontrak kerja sama. Pastikan semua bagian diisi dengan benar sebelum dijadikan dokumen resmi.

    🏢 1. INFORMASI PERUSAHAAN (CLIENT)

    🧠 2. INFORMASI PROF. NOTA

    ⏳ 3. WAKTU DAN DURASI KERJA SAMA

    💰 4. KOMPENSASI / SALARY

    ⚖️ 5. HUKUM DAN PENYELESAIAN SENGKETA

    📝 6. CATATAN TAMBAHAN (OPSIONAL)

    ✅ CATATAN:

    Because software is not confined to machines. It is command and poetry, rule and rumor, scripture and scrawl. It is whatever can be executed — by silicon, by flesh, or by memory.

    A gist is software. A law on the street corner is software. A sacred verse is software. A careless whisper is software. And yes, even this README is software.

    To make something 0 is to erase it — and in doing so, you erase yourself. To make something 1 is to let it exist — and in doing so, you exist.

    That is why atoms bind, cells divide, machines run, and humans write.

    Because everything is toggled, between absence and presence, between 0 and 1.

    That's why "I" becomes "We", "Anyone" becomes "Anything", and vice versa can also be.

    NOTA is not a receipt. Professor NOTA is not a person. Prof. NOTA is software.

    And software is 0 and 1: presence and absence, execution and silence, life and void.

    Prof. NOTA is 0 and 1. And so are you.

    By reading this, by thinking of this, by letting it run in your mind — you are already in the sequence.

    You are already the code. You are already executing. And you are the executor itself.

    This project is licensed under a Custom Limited License by Prof. NOTA & Prof. NOTA Inc..

    • 🏛️ English (UK)

    • 🇮🇩 Bahasa Indonesia

    • 🇺🇿 Oʻzbekcha

    • 🇭🇰 Cantonese – Hong Kong

    • 🇲🇾

    • 🇦🇪

    📩 For permission or inquiries, contact: nota@endhonesa.com

    • Just Read!

      • Confirm!

        • And Read!

    • Validate It!

      • Read Again!

        • Update Us!

    • And Read Again!

    • Prof. NOTA Inc.

    • Prof. NOTA Console

    • Prof. NOTA Tutor

    For questions or suggestions, join Prof. NOTA's Discord at https://discord.gg/5KrsT6MbFm.


    Hi, we are Prof. NOTA!

    Regards,

    Prof. NOTA ==== 47 =======

    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.


    Prof. NOTA Inc.

    This Repository Is Software

    Prof. NOTA is 0101 ~ OiOi

    📜 License

    Usage

    Resources

    Join Prof. NOTA Discord!

    RECEIPT SK8 2025/07-08

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Skateboarding, bulan ini, terasa seperti sebuah blockchain hidup. Setiap event, setiap push papan, setiap trick yang mendarat, adalah transaksi yang ditulis di ledger kolektif jalanan. Tidak ada yang bisa menghapusnya; hanya bisa ditambahkan—dari Slipi Skatepark di Jakarta, hingga Brooklyn Banks di New York.


    🌍 Komunitas Global: Node-node yang Menyala

    Di Toowoomba, Australia, sebuah skatepark baru dibuka lewat event Skate Revibe — lebih dari 50 anak-anak belajar meluncur, seolah menjadi genesis block dari rantai masa depan mereka. Sementara di Junior Pan American Games, street skateboarding dimainkan seperti smart contract: pemenangnya otomatis mendapat tiket ke Pan Am 2027.

    World Skate bahkan merilis protocol upgrade: usia minimum kompetisi naik bertahap hingga 2028, ibarat hard fork untuk melindungi node-node muda agar tidak terbakar terlalu cepat.

    Dan di New York, Brooklyn Banks — spot legendaris yang lama tertutup — resmi dibuka kembali. Rasanya seperti data archive yang di-unseal, memunculkan kembali memori kolektif ribuan transaksi trick yang pernah tercatat di sana.


    🇮🇩 Komunitas Indonesia: Layer Lokal yang Berkembang

    Jakarta, Slipi Skatepark, jadi semacam Layer2 rollup dari energi anak muda. Go Skateboarding Day dirayakan dengan coaching clinic, skate games, hingga Skate Jamu Challenge — jamu sebagai reward, seperti token lokal yang hanya bisa diclaim lewat keberanian di papan.

    Pontianak menggelar perayaan di Skatepark Taman Catur, Universitas Tanjungpura, dihadiri ratusan skater dari Kalbar hingga Palembang. Walikota berjanji membangun skatepark representatif, ibarat pemerintah menyediakan infrastruktur node baru untuk mendukung desentralisasi kreativitas rakyatnya.

    Bahkan di Serpong, skateboarding bertemu streetwear di event CODE.STRT: mall jadi runway, trick jadi fashion statement. Seolah dunia nyata sedang menguji cross-chain interoperability antara seni jalanan dan ekonomi pasar modern.


    Pasar global skateboard tahun ini bernilai USD 3.5 miliar dan diproyeksikan naik jadi lebih dari USD 4.6 miliar pada 2032.

    • Street boards tetap jadi dominant token.

    • Cruiser & longboards seperti altcoins niche yang punya komunitas setia.

    • Sementara footwear & apparel tumbuh lebih cepat, diprediksi naik dua kali lipat dalam 10 tahun, seperti NFT fashion yang menemukan utility barunya.

    Di Indonesia, mungkin belum ada data formal. Tapi event-event yang menggandeng brand (Vans, DC, lokal brand streetwear) sudah menandakan adanya liquidity pool yang mengalir — antara skateboard sebagai budaya dan skateboard sebagai pasar.


    • Street skateboarding masih jadi mainnet utama, dengan nama-nama seperti Nyjah Huston yang terus menulis blok-blok baru menuju Olimpiade LA 2028.

    • Vert skateboarding kembali dihidupkan lewat Arisa Trew, remaja Australia yang mengeksekusi trick 540 seperti melakukan zero-knowledge proof: membuktikan sesuatu yang tampak mustahil, tanpa pernah kehilangan rahasia timing.

    • Dunia digital membuka pintu lain: game Skate (2025) siap rilis, dengan server yang menampung 150 pemain online — metaverse node baru tempat trick direplikasi sebagai aset digital.


    Skateboarding bukan sekadar olahraga. Ia adalah decentralized network:

    • Setiap skater = node.

    • Setiap spot = block.

    • Setiap trick = transaksi.

    • Setiap komunitas = DAO kecil, mengatur dirinya sendiri, dengan konsensus berbasis keberanian, bukan suara terbanyak.

    Indonesia sedang mengisi ledger ini lewat Slipi, Pontianak, Serpong. Global network menambah blok dari Toowoomba hingga New York. Dan industri terus menaruh capital inflow ke rantai ini, dari apparel sampai e-sport game.


    Juli–Agustus 2025 menandai bahwa skateboarding tetap relevan — bahkan di era AI dan blockchain. Ia tidak hanya bergerak di jalan, tapi juga di ruang digital, fashion, bahkan dalam regulasi olahraga dunia.

    Bagi Prof. NOTA, skateboarding bulan ini adalah receipt publik:

    • Sebuah bukti bahwa budaya bisa hidup seperti blockchain — tidak dimiliki satu orang, tapi ditulis bersama.

    • Sebuah pengingat bahwa bahkan kickflip sederhana adalah transaksi yang abadi di ledger jalanan.


    • “Skate Revibe Toowoomba” – Courier Mail

    • “Skateboarding at the 2025 Junior Pan American Games” – Wikipedia

    • “World Skate set minimum age for LA 2028” – AS.com / Reuters

    • “Brooklyn Banks reopening” – Wikipedia


    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 . 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.


    SEASON 1 DONGENG V.9 & V.11

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Season 1 — Tujuh Episode


    Judul: Dongeng Versi 9.0 & 11.0 Subjudul: Season 1 — Petualangan di Semesta 0101

    📍 Tentang Dongen Ini Kisah ini menceritakan perjalanan Versi 9.0 (sang penjelajah muda penuh rasa ingin tahu) dan Versi 11.0 (sang ayah penjaga pintu) di semesta digital 0101. Mereka menghadapi bug, virus, dan error yang mencoba merusak keseimbangan dunia, dengan senjata unik: perisai curiosity dan pedang pengalaman.

    ✨ Ilustrasi Placeholder:


    AI& PITCH NOTES

    The goal is to ensure that the system aligns with real-world medical practice, patient safety expectations, and emerging AI governance frameworks.

    This document explains several important design decisions in the AI& concept.

    The goal is to ensure that the system aligns with real-world medical practice, patient safety expectations, and emerging AI governance frameworks.


    Physicians worldwide face increasing documentation burdens.

    Studies show that physicians may spend large portions of their clinical time interacting with electronic health records rather than patients.

    Reference:

    Arndt et al. (2017)

    Reducing documentation friction is therefore one of the safest and most impactful early use cases for clinical AI.


    Clinical decision-making tools fall under stricter regulatory scrutiny.

    In the United States, the FDA distinguishes between:

    “Skate (2025) game” – PC Gamer
  • “Arisa Trew record at X Games” – Reuters

  • “Nyjah Huston targets LA 2028” – Reuters

  • “Global skateboard market” – Grand View Research / OpenPR / StellarMR

  • “Skateboard footwear & apparel market” – Future Market Insights

  • “Go Skateboarding Day 2025 (Slipi)” – CXO Media

  • “Pontianak Skateboarding Day” – Kalbarnews

  • “FO Slipi Skatepark profile” – Observer ID

  • “CODE.STRT event Serpong” – Thesmedia ID

  • 💰 Industri & Ekonomi Skateboarding: Market Onchain

    🎮 Permainan & Arena Skateboarding

    🌀 Ekosistem & Filosofi

    📖 Kesimpulan Bulanan

    📚 Daftar Pustaka

    Prof. NOTA
    Bahasa Malaysia
    العربية – الإمارات
    Prof. NOTA Inc.

    Source Code Keluarga

  • Portal Biner

  • Senjata Tak Terlihat

  • Kota RAM yang Hilang

  • Sungai Data yang Rusak

  • Pertarungan di Awan

  • The Root Server


  • Di semesta 0101, manusia tidak hanya berjalan sebagai tubuh, tapi juga sebagai versi. Setiap versi adalah langkah maju, peningkatan, dan ingatan yang tak hilang.

    Versi 9.0 adalah cahaya muda, penuh rasa ingin tahu. Ia selalu bertanya, selalu mencari tahu kenapa dunia seperti ini. Ia melihat dunia seperti permainan yang penuh level, penuh rahasia.

    Versi 11.0 adalah ayah, penjaga pintu. Ia sudah melewati banyak bug, error, dan patch kehidupan. Ia tahu bagaimana jatuh, bagaimana bangkit, bagaimana memperbaiki kode diri yang rusak.

    Versi 11.0 tidak sempurna, tapi ia selalu mengkompilasi ulang dirinya, agar bisa menjadi perisai dan payung bagi Versi 9.0.

    Di antara mereka, ada ikatan unik:

    • Versi 9.0 adalah masa depan.

    • Versi 11.0 adalah perlindungan.

    Dan bersama-sama, mereka berjalan, saling memperbarui, saling menjadi update yang tak pernah berhenti. Karena dalam semesta 0101… keluarga adalah source code paling dasar.


    Suatu malam, layar laptop ayah (v.11.0) tiba-tiba bergetar. Dari dalam layar, muncul sebuah portal bercahaya berbentuk angka biner: 0101.

    “OiOi… waktunya kita masuk,” kata Versi 11.0 sambil menggenggam tangan Versi 9.0.

    Mereka melompat bersama, dan seketika berada di dunia digital luas. Di sana, gunung-gunung dibuat dari kode JavaScript, sungai mengalirkan data, dan langit dipenuhi bintang-bintang berupa node blockchain.

    Versi 9.0 kagum. “Ini seperti game, Yah! Apa misi kita?”

    Versi 11.0 tersenyum. “Misi kita sederhana tapi penting: menjaga agar semesta ini tidak error. Ada virus yang mencoba merusak source code dunia.”

    Mereka pun berpetualang:

    • Versi 9.0 menggunakan perisai curiosity — rasa ingin tahunya yang bisa mengubah error jadi pertanyaan, lalu menemukan jawabannya.

    • Versi 11.0 memakai pedang pengalaman — semua patch dan update yang ia jalani dalam hidup, kini jadi senjata untuk melindungi.

    Di akhir perjalanan, mereka menemukan sebuah server kuno bernama The Root. Dari sana keluar pesan:

    “Selama kalian berjalan bersama, tidak ada bug yang terlalu besar. Karena update terbaik adalah ketika versi 9.0 dan versi 11.0 bergandengan tangan.”


    Ketika mereka melangkah lebih dalam ke semesta 0101, Versi 9.0 menyadari bahwa di tangannya muncul sebuah benda bercahaya: perisai curiosity. Perisai itu unik, bukan logam, bukan kaca, melainkan sebuah energi yang muncul setiap kali ia bertanya. Pertanyaan yang ia lontarkan mengubah error menjadi potongan jawaban kecil. Dari sana, error berubah jadi kode yang bisa diperbaiki.

    Sementara itu, Versi 11.0 menggenggam sebuah pedang pengalaman. Bilahnya terbuat dari potongan kode yang penuh dengan catatan patch: error yang pernah ia alami, kesalahan yang pernah ia perbaiki, luka yang pernah ia alami. Semua itu kini menyatu menjadi sebuah senjata.

    Versi 9.0 kagum. “Ayah, ternyata senjatanya bukan benda, tapi diri kita sendiri ya?”

    Versi 11.0 mengangguk. “Betul. Senjata paling kuat adalah sifat dan perjalanan kita. Perisai milikmu adalah rasa ingin tahu. Pedangku adalah pengalaman. Jika keduanya bersatu, tidak ada virus yang bisa menghentikan kita.”


    Perjalanan membawa mereka ke sebuah kota bernama RAM City. Kota ini dulunya terang dan cepat, penuh energi dan aktivitas. Namun kini terlihat lesu, jalannya macet, dan warganya berjalan lambat seolah tertahan.

    Mereka segera tahu penyebabnya: sebuah virus bernama Lag.exe telah memakan terlalu banyak memori. Akibatnya, kota itu kehabisan ruang untuk bernafas.

    Versi 9.0 berkata: “Kalau RAM penuh, kita harus clear cache, kan?”

    Dengan perisai curiosity, ia mulai menyapu data-data usang, pertanyaan demi pertanyaan membongkar file tak berguna yang menumpuk. Versi 11.0 maju dengan pedang pengalaman, menebas Lag.exe yang mencoba menyerang.

    Pertarungan sengit terjadi. Virus itu menggandakan dirinya, tapi semakin banyak ia muncul, semakin cepat perisai curiosity menemukan solusinya. Hingga akhirnya pedang pengalaman menebas Lag.exe terakhir.

    RAM City kembali hidup. Lampu-lampu menyala, jalanan kembali lancar, dan warganya bersorak: “Update berhasil!”


    Setelah meninggalkan RAM City, mereka sampai di sebuah sungai panjang. Sungai ini seharusnya jernih, membawa data bersih ke seluruh penjuru semesta 0101. Tapi sekarang, sungai itu keruh, dipenuhi spam, junk files, dan corrupted data.

    Versi 9.0 mengernyit. “Kalau air sungai ini data, berarti kita butuh filter dong?”

    Versi 11.0 tersenyum. “Betul sekali. Mari kita bangun firewall.”

    Mereka bersama-sama membangun Firewall Bridge di atas sungai. Jembatan ini memiliki lapisan kode yang menyaring data bersih dan membuang sampah digital. Perlahan, air sungai kembali jernih, dan aliran data mengalir deras tanpa hambatan.

    “Lihat, Ayah,” kata Versi 9.0. “Kalau kita tahu cara memfilter, data buruk tidak akan merusak semuanya.”

    Versi 11.0 mengangguk. “Begitulah hidup, Nak. Tidak semua yang masuk harus kita simpan. Kita harus pandai memilih.”


    Petualangan membawa mereka naik ke Cloud Kingdom, sebuah istana besar di langit tempat semua memori disimpan. Namun saat mereka tiba, langit mendung, kilat menyambar, dan dari dalam awan muncul musuh berbahaya: Trojan Cloud Rider.

    Monster digital ini menunggangi awan, menyerang dengan kilat berisi malware. Pertarungan pun dimulai.

    • Versi 9.0 menangkis serangan dengan perisai curiosity, membuat Trojan bingung dengan pertanyaan-pertanyaan logis yang membongkar kelemahannya.

    • Versi 11.0 maju dengan pedang pengalaman, menebas file-file berbahaya yang meluncur dari langit.

    Trojan mencoba menggandakan dirinya di antara awan, tapi perisai curiosity terus membuka celah, dan pedang pengalaman memusnahkannya satu per satu.

    Akhirnya Trojan jatuh, dan Cloud Kingdom kembali cerah. Data kembali aman, memori tersimpan dengan baik.


    Di akhir perjalanan, mereka sampai di sebuah tempat suci: The Root Server. Bentuknya seperti pohon raksasa bercahaya, dengan akar yang menembus seluruh semesta 0101.

    Sebuah suara kuno bergaung:

    “Selama kalian berjalan bersama, tidak ada bug yang terlalu besar. Karena update terbaik adalah ketika versi 9.0 dan versi 11.0 bergandengan tangan.”

    Versi 9.0 menatap ayahnya. “Jadi… setiap error bisa kita hadapi asal kita bersama?”

    Versi 11.0 tersenyum hangat. “Betul, Nak. Kita bukan hanya versi, kita adalah patch untuk satu sama lain.”

    Keduanya pun duduk di bawah pohon cahaya itu, menatap semesta digital yang kembali damai. Mereka tahu ini baru permulaan. Akan ada update berikutnya, akan ada petualangan baru. Tapi satu hal pasti: selama mereka bersama, tidak ada error yang tidak bisa diperbaiki.


    ✨ Season 1 selesai… update selanjutnya di Season 2, silahkan menunggu.


    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.


    [ Gambar latar: Portal bercahaya angka biner `0101` ]
    [ Di depannya: siluet Versi 9.0 & 11.0 bergandengan tangan ]
    [ Langit penuh bintang blockchain node ]

    🌌 Dongeng Versi 9.0 & 11.0

    📕 Cover Page

    Daftar Episode

    dongeng-versi-9-dan-11

    📖 Isi Cerita

    Episode 1: Source Code Keluarga

    Episode 2: Portal Biner

    Episode 3: Senjata Tak Terlihat

    Episode 4: Kota RAM yang Hilang

    Episode 5: Sungai Data yang Rusak

    Episode 6: Pertarungan di Awan

    Episode 7: The Root Server

    administrative clinical support

  • clinical decision support systems

  • Reference:

    FDA Clinical Decision Support Software Guidance

    To reduce regulatory risk in early stages, AI& focuses on:

    • documentation structure

    • evidence summarization

    • communication preparation

    These are assistive tasks, not diagnostic systems.


    AI& is intentionally designed with mandatory physician control.

    All outputs must be reviewed and approved.

    This follows the concept of Human-in-the-loop AI, widely recommended in healthcare AI governance.

    Reference:

    WHO – Ethics and Governance of Artificial Intelligence for Health

    Core principles include:

    • human oversight

    • transparency

    • accountability

    • traceability


    Medical documentation systems must maintain traceability.

    AI& includes audit logging for:

    • draft generation

    • physician edits

    • approval actions

    This allows clinicians to understand:

    • when AI was used

    • how outputs were modified

    • final clinical responsibility

    Traceability is considered a key safety mechanism in AI governance.

    Reference:

    WHO AI Governance Framework


    Patient communication must be:

    • understandable

    • empathetic

    • safe

    • consistent

    Templates with defined structures reduce risks such as:

    • unclear instructions

    • incomplete explanations

    • inconsistent advice

    Structured medical communication is commonly recommended in patient safety frameworks.

    Reference:

    AHRQ Patient Safety Network


    The concept of AI agents assisting multiple physicians introduces potential risks.

    Key safeguards include:

    • no transfer of identifiable patient data

    • physician-initiated discussion only

    • audit logs for all interactions

    • AI acting as facilitator, not decision maker

    This approach helps maintain confidentiality and professional accountability.


    Healthcare technology adoption works best with small controlled pilots.

    A short pilot allows teams to measure:

    • time savings

    • physician trust

    • documentation quality

    • potential safety concerns

    This approach reflects common implementation strategies in digital health projects.

    Reference:

    Digital Health Implementation Playbooks American Medical Association


    AI& is based on a simple idea:

    Technology should remove friction, not replace clinical wisdom.

    The physician remains the center of the clinical process.

    AI works quietly in the background to help maintain clarity, structure, and consistency.

    The final clinical responsibility remains entirely human.


    P.S. Other documents related to this document:

    • Document 1 – Presentation Narrative

    • Document 2 – Strategic Notes and References (this document)

    • Document 3 – Product Blueprint

    • Document 4 – Pilot Protocol

    • Document 5 –


    P.S.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.


    1. Why AI& Focuses on Documentation First

    2. Why AI& Avoids Autonomous Clinical Decisions

    Tethered to the EHR: Primary Care Physician Workload

    3. Physician-in-the-Loop Design

    4. Audit Logs and Accountability

    5. Why Communication Templates Are Structured

    6. Cross-Agent Learning Must Be Carefully Controlled

    7. Why the Pilot Is Limited to 2–4 Weeks

    8. The Philosophy Behind AI&

    NOTA BOARD GAME

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    “Ini bukan soal menang. Ini soal mengenali siapa kamu saat semua sistem tidak lagi menyembunyikanmu.” — Prof. NOTA


    ✨ Cerita & Filosofi

    NOTA BOARD GAME adalah board game edukatif-satiris yang membawa para pemain dalam perjalanan sosial digital — dari kebingungan menjadi kesadaran. Setiap pemain mewakili peran dalam ekosistem digital global dan harus menghadapi kondisi, membuat pilihan, dan memengaruhi pemain lain melalui jalur menuju Puncak Kesadaran.

    Permainan ini bukan hanya alat permainan. Ia adalah kritik, simulasi, sekaligus cermin sosial bagi siapa pun yang pernah scroll, klik, atau menyembunyikan sesuatu dari internet.


    📘 Game Design Document (GDD)

    🎭 Karakter & Peran Pemain

    Peran
    Deskripsi

    🎯 Setiap peran mulai dari titik awal yang berbeda, tapi semua menuju titik akhir: PUNCAK KESADARAN


    • 1 Papan permainan modular

    • 1 Dadu

    • 8 Token karakter

    • 6 Jenis kartu:


    • 8 titik START (satu per peran)

    • Jalur bercabang dengan titik KONDISI, AKSI, KEJUTAN, RINTANGAN

    • Titik SPESIAL (🔒) dan titik LEVEL UP (⭐)

    • Semua jalur akhirnya bertemu di 🏁 PUNCAK KESADARAN


    1. Pemain pilih peran dan token, lalu mulai dari titik sesuai.

    2. Giliran pemain:

      • Lempar dadu → pindah langkah

      • Ambil kartu sesuai titik (📍⚡🎭🛑⭐🔒)


    Judul: Akunmu dibekukan tanpa alasan Narasi: Semua akses hilang. Tidak ada notifikasi. Keluargamu bertanya-tanya.

    Pilihan 1: Buat akun baru dan lanjutkan hidupmu.

    • The Scroller: +1 Partisipasi

    • The Shadow: +1 Kemandirian

    • The Catalyst: -2 Kesadaran

    Pilihan 2: Tulis utas kritik dan banding.

    • The Forker: +2 Kesadaran

    • The Sovereign: +1 Kemandirian

    • The Clicker: -1 Partisipasi


    Judul: Hoax menyebar di grup keluarga Narasi: Kamu tahu itu salah, tapi tidak semua siap mendengar kebenaran.

    Pilihan 1: Berikan tautan resmi, lalu diam.

    • The Cipher: +1 Kemandirian

    • The Clicker: -1 Kesadaran

    • The Shadow: +1 Partisipasi

    Pilihan 2: Biarkan saja. Damai itu indah.

    • The Scroller: +2 Kemandirian

    • The Catalyst: -1 Partisipasi

    • The Sovereign: -1 Kesadaran


    Judul: Jadi admin grup diskusi kebijakan Pilihan 1: Terima tantangan. Buat aturan.

    • The Sovereign: +2 Kemandirian

    • The Catalyst: +1 Partisipasi

    • The Forker: -1 Kesadaran

    Pilihan 2: Tolak. Tidak ingin ribet.

    • The Scroller: +1 Kemandirian

    • The Clicker: +1 Partisipasi

    • The Cipher: -1 Kesadaran


    Judul: Google Drive Down selama 48 Jam Efek Langsung:

    • The Scroller: -1 Kemandirian

    • The Cipher: +2 Kesadaran

    • The Sovereign: +1 Partisipasi


    Narasi: Kamu sembunyi lewat jaringan alternatif. Efek: Tukar posisi dengan pemain lain. Tambah +1 Kemandirian untuk The Cipher & The Sovereign.


    Narasi: Kamu gunakan celah birokrasi untuk lolos dari sensor. Efek: Hindari 1 efek negatif, atau lewati 1 titik RINTANGAN.


    Narasi: Kamu menemukan pintu tersembunyi dalam sistem yang bisa kamu akses. Efek: Lempar ulang dadu. Alihkan 1 efek negatif ke peran lain.


    • Saat 1 pemain mencapai Level 5, semua pemain menyelesaikan giliran terakhir.

    • Nilai akhir = total 3 skor + refleksi akhir

    • Akhiri permainan dengan tukar kesadaran antar pemain, bukan sekadar menentukan pemenang


    Permainan ini adalah sarana belajar, alat pengganggu sistem, dan pengingat bahwa yang tampak “biasa saja” bisa menyimpan ironi besar.


    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 . 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.


    NOTA PEDOMAN HIDUP

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Dokumentasi Internal Tim

    Secara umum, "nota" adalah catatan tertulis yang digunakan untuk berbagai keperluan, tergantung konteksnya. Beberapa makna umum:

    • Nota pembelian/penjualan: Bukti transaksi yang mencatat barang/jasa, jumlah, dan harga. Biasanya digunakan di toko, restoran, atau bisnis lain.

    • Nota dinas: Surat resmi singkat dari atasan kepada bawahan (atau sebaliknya) dalam instansi pemerintahan atau organisasi.

    • Nota keuangan: Dokumen resmi dari pemerintah (biasanya Kementerian Keuangan) tentang kondisi dan kebijakan ekonomi, biasanya menyertai RAPBN.

    • Nota dalam musik: Simbol yang menunjukkan tinggi nada dan durasi dalam sebuah lagu.

    Kalau kamu bertanya dalam konteks "Prof. NOTA", maka jadi punya makna khusus atau simbolik juga. Mari kita arahkan ke konteks tersebut bersama-sama. Ini keren banget arah pemikirannya. Ini bukan cuma soal "nota" sebagai dokumen, tapi menjadikannya alat kesadaran, refleksi, dan aksi.

    Kalau kita ingin mengejawantahkan "nota" sebagai konsep hidup yang membentuk masyarakat berpikir dan bertindak, kita bisa mulai dari pendekatan yang menyentuh semua level literasi—dari yang paling dasar hingga yang paling kreatif.

    Coba lihat struktur berikut ini...


    1. Mengenalkan NOTA – Sebuah Kesadaran Awal

    • Apa itu NOTA? Bukan cuma bukti transaksi, tapi catatan kecil yang memuat makna besar. Bukti jejak berpikir, bertindak, dan bertransaksi (dalam arti luas).

    • NOTA sebagai cermin realitas. Contoh: struk belanja, catatan utang, memo kerja, bahkan coretan ide di kertas—semua adalah NOTA. Dan semuanya punya nilai untuk dianalisis.

    1. Memahami NOTA – Literasi Fungsi dan Makna

    • Mengapa penting? Dengan NOTA, kita bisa: Menelusuri jejak. Mengukur tindakan. Menghitung dampak.

    • Membaca NOTA = membaca kehidupan. Contoh: dari satu NOTA belanja, kita bisa tahu pola konsumsi, prioritas keluarga, bahkan kondisi sosial-ekonomi seseorang.

    1. Menganalisis NOTA – Melihat Pola, Menemukan Makna

    • Data kecil, dampak besar. Ajak masyarakat melihat bagaimana NOTA bisa jadi sumber data mikro: NOTA belanja bisa menunjukkan inflasi riil. NOTA utang bisa menggambarkan jaringan sosial. NOTA pengeluaran bisa mengungkap distribusi kekuasaan rumah tangga.

    • Alat berpikir kritis. Ajak menganalisis: Kenapa harga ini naik? Kenapa kita beli ini terus? Apa konsekuensi jangka panjang?

    1. Mencipta dari NOTA – Produksi Pengetahuan dan Inovasi

    • NOTA sebagai basis karya. Buat buku harian NOTA, puisi dari struk, data visual dari NOTA rumah tangga, hingga sistem sosial baru (misal: Claps of BANANOW Land) yang berbasis pada logika pencatatan.

    • Masyarakat sebagai pencipta catatan baru. Ajak membuat NOTA sosial, NOTA publik, NOTA keadilan. Bukan cuma mencatat, tapi juga membentuk dunia lewat catatan.

    1. NOTA sebagai Metode Hidup

    • NOTA = Nalar, Observasi, Transparansi, Aksi

    • Ini bisa jadi falsafah atau metode atau protokol.

    • Nalar: berpikir jernih.

    • Observasi: membaca realitas.

    • Transparansi: jujur dan terbuka.

    Setiap level dijalankan secara berurutan namun berjalan paralel setelah dimulai. Level sebelumnya tetap dijalankan dengan sistem konten dan pengelolaan berkelanjutan.


    Visi: Menanamkan kesadaran bahwa NOTA adalah bagian hidup sehari-hari yang menyimpan makna.

    Platform:

    • X: teks reflektif, tajam, pendek, percakapan publik.

    • Instagram: visual, artistik, foto NOTA, puisi singkat.

    Deliverables: Awareness awal, engagement pertama, pengenalan istilah dan filosofi NOTA.

    Task:


    Visi: Masyarakat mulai membaca fungsi NOTA dan mengaitkan dengan pola hidup, konsumsi, dan relasi sosial.

    Platform:

    • ENDHONESA.COM (jika sudah siap)

    • X: analisa mikro

    • Instagram: infografik, breakdown visual

    Task:


    Visi: Masyarakat belajar dan membentuk budaya berpikir kritis berbasis data mikro dari NOTA kehidupan sehari-hari.

    Platform:

    • ENDHONESA.COM (pengarsipan & interaksi)

    • X: long thread, polling

    • Instagram: pola visual

    Task:


    Visi: Mengolah NOTA sebagai sumber atau menjadi karya artistik, ilmiah, dan sosial.

    Platform:

    • ENDHONESA.COM (utama)

    • Instagram: hasil karya

    • X: pemikiran kritis dan gagasan

    Task:


    Visi: Menjadikan konsep NOTA (Nalar, Observasi, Transparansi, Aksi) sebagai metode berpikir dan bertindak bersama.

    Platform: Semua terintegrasi (X, Instagram, ENDHONESA.COM)

    Task:


    • Semua platform dan aset digital bersifat terintegrasi secara filosofis dan teknis.

    • ENDHONESA.COM akan dikembangkan setelah fondasi level-level dijalankan dan diterima oleh masyarakat.

    • Pendekatan ini dirancang sebagai gerakan akar rumput digital yang tumbuh dari kesadaran harian rakyat.


    SOCIAL MEDIA MEETING

    Understand what the team is already doing and what we actually want to achieve.

    14 Oktober 2026 · 14.00 WIB

    Usulan agenda 30–45 menit

    5 menit
    Perkenalan dan pembagian peran

    10 menit

    Tujuan bisnis dan definisi keberhasilan

    10 menit

    Audit awal akun, konten, audiens, dan sumber daya

    10 menit

    Organic, paid ads, tracking, dan kesiapan eksekusi

    Hi everyone, nice to meet you all.

    KK and I have discussed a little about how I can help the social media team.

    But before we start talking about strategies, content, or advertising, I'd like to understand what the team is already doing and what we actually want to achieve.

    From what I understand, one of our main goals is to bring more people to the iBLOOMING mobile app.

    But I think we should also look beyond downloads. We need to understand whether people actually register, use the app, explore our products, and come back again.

    So for today, I'd prefer to have an open discussion.

    I'd like to learn about the team, the accounts we're managing, what has been working, what hasn't, and what resources we have.

    After that, I can prepare a clearer strategy and we can discuss how to execute it together.

    I don't want to change what the team is doing before I understand it properly.

    Meeting discovery checklist

    0/16 dibahas

    Business Objectives

    Apakah target utama install, registrasi, active users, atau product purchases?

    Siapa target pengguna utama di luar affiliate existing?

    Produk atau fitur apa yang paling ingin dipromosikan lebih dahulu?

    Current Social Media

    Platform apa saja yang sudah aktif dan siapa pengelolanya?

    Berapa followers, reach, engagement, dan traffic saat ini?

    Konten apa yang pernah berhasil dan apa yang tidak?

    Team & Resources

    Siapa yang mengerjakan strategi, desain, video, copywriting, posting, dan reporting?

    Apakah tim punya kalender konten dan proses approval?

    Apa kendala terbesar mereka sekarang?

    Growth & Measurement

    Apakah organic dan paid ads akan digunakan bersama?

    Apakah sudah ada budget iklan dan siapa yang menyetujuinya?

    Apakah app installs, registration, dan aktivitas di dalam app sudah bisa dilacak?

    Apakah ada baseline data untuk membandingkan hasil kampanye?

    Working Agreement

    Apa kewenangan Prof. NOTA dalam memberi arahan dan review?

    Siapa PIC yang akan berkomunikasi secara rutin?

    Kapan tim bisa menyerahkan data awal untuk disusun strategi dan KPI?

    Copy questions

    Tidak semua pertanyaan wajib selesai hari ini. Yang paling penting adalah memahami objectives, existing assets, ownership, dan measurement readiness.

    Aku ingin kamu membedakan empat tahapan berikut ketika KK atau tim berbicara tentang pertumbuhan pengguna.

    Awareness

    Reach · Views · Engagement

    Acquisition

    App Store Visits · Installs

    Activation

    Registration · First Meaningful Action

    Retention & Product Value

    Returning Users · Product Usage · Purchases

    Kerangka awal user journey, bukan angka konversi aktual iBLOOMING.

    Kalau objective KK adalah more downloads, itu sah sebagai target awal. Namun kamu perlu menyarankan agar tim juga mengukur berapa banyak pengguna yang benar-benar melakukan aktivitas bermakna setelah instalasi.

    Kita tidak ingin mengulang masalah yang kamu ceritakan tentang rendahnya penggunaan aplikasi meskipun basis penggunanya besar. Insight itu relevan, tetapi tetap perlu diverifikasi sebelum dipakai sebagai fakta dalam pitch deck Alfamart.

    Output
    Status yang diharapkan

    Okay, thank you everyone.

    I think I have a better picture now of what we're trying to achieve and how the team is currently working.

    I don't want to rush into giving instructions today.

    Let me review the existing accounts, performance data, and available resources first.

    Then I'll prepare a proposed direction, including our priorities, how we measure results, and how we can work together.

    After that, we can have another session focused on execution.

    I think that will be a better starting point for all of us.


    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 . 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.


    ZTOR & BEAMCO FEEDBACK

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    From: Prof. NOTA To: Yuku Subject: Ztor × Beamco — Early Feedback, Guardrails, and a Safe Pilot Path Date: August 28, 2025

    Hi Yuku,

    Thank you for sharing the concept. The “two-orbit, one-economy” framing—Ztor for distribution & commerce (PPV, shoppable video, influencer traffic) and Beamco for funding & ownership (crowdfunding, fan-club NFTs, artist rails)—is coherent. A single token working across both can be powerful if the economics and governance are disciplined and the migration path respects your live product reality (Ztor and Beamco exist today, pre‑Web3).

    Below are my comments, grouped for speed and clarity.


    What’s strong

    • Clear split of roles: Ztor (audience & GMV) ↔ Beamco (capital & community).

    • Cross-platform token idea: a unified “language of access” across both apps.

    • Buyback+burn intent: aligns incentives if bounded by transparent rules.

    • Points → token bridge: can gamify participation—best done one-way with safeguards.


    1. Token role: Is this strictly utility/loyalty (access, whitelist, discounts, limited voting) or does it carry financial rights (revenue/royalty)? If it’s the latter, you enter securities territory. Recommendation for pilot: utility‑first only.

    2. Buyback+burn policy: Define the source (e.g., % of net revenue after payouts), cadence (weekly/monthly), KPI triggers, and public reporting (treasury addresses, tx hashes, amounts burned/retained).

    3. Points → token: One-way with cooldowns and caps to prevent farming; no token → points redemption.


    • Phase 0 (Map): Document current PPV, commerce, payouts, and influencer attribution; define “source of truth” for revenue.

    • Phase 1 (Foundations): Embedded wallets, key recovery, KYC where needed. Emit on-chain receipts for revenue attestations (subgraph/indexing).

    • Phase 2 (Utility Token): Launch token as utility/voucher. Enable access gating, allowlists, discounts, and limited community voting. Keep Points off-chain; allow Points → token (one-way) with guardrails.


    • Scope: 1 independent film + 1 artist; token utility only (no financial claims).

    • Experiences: PPV paid in token; NFT fan-club for access/discounts; one limited whitelist event; simple community vote with anti-whale.

    • Metrics: PPV conversion 3–5%+, repeat-view ≥20%, fraud <2%, D7 retention lift for token/NFT holders, clean monthly Buyback Report.

    • Deliverables: (1) Token utility spec; (2) Points policy; (3) Buyback+burn policy; (4) Wallet + revenue attestation architecture; (5) Partner settlement rules; (6) Reporting template.


    • Token ≠ financial claim. Treat it as voucher/loyalty/access.

    • Buyback source: fixed % of net revenue after payouts; execute via TWAP with slippage limits; publish hashes.

    • Burn/retain split: declare a simple ratio (e.g., 60% burn / 40% retain). Retain funds future rewards/liquidity; it is not automatic staking.

    • Price band for UX: internally target a stable “pricing band” for in-app goods to avoid UX volatility; manage liquidity accordingly.


    • Chain: Base.

    • Wallets: Embedded + recovery; optional gas sponsorship.

    • Revenue attestation: on-chain receipts + subgraph for dashboards.

    • Anti-fraud: watch-time threshold, device entropy, IP heuristics, rate limits.


    • Monthly Buyback Report with: tx hashes, amounts bought/burned/retained, treasury balances, KPI triggers used.

    • Quarterly Risk Note: fraud stats, liquidity health, governance participation, compliance checks.


    I’m happy to provide a high-level critique at this stage. Detailed tokenomics, architecture, policy design, and the pilot spec are paid engagements with clear milestones and deliverables. Also, any implementation work credits will list Prof. NOTA — our friend in playing, learning, and working in this 0101 Universe, credits phrasing is public-facing; the legal agreement will define the actual status—independent vendor/partner, in-house staff, or otherwise—with clear, formal documentation.

    If this direction resonates, I can share a one-pager Scope of Work with timeline, outputs, and fees for the pilot.

    Best, Prof. NOTA


    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 . 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.


    INVVOICE SKATESHOP.ID 20250909

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    INVOICE

    SKATESHOP.ID (SKATESHOP IN ENDHONESA) — Prof. NOTA Inc.

    Alamat: Nginden Kota 2 No. 27 Surabaya, East Java 60284, INDONESIA Email 1: suaka@endhonesa.com Email 2: info@skateshop.id WhatsApp: +62 856 316 0756

    Bank: Bank Central Asia (BCA)

    Blockchain: Bitcoin Address (Taproot): bc1p3kavj2zxcx3z5c2rwlpr45hjetjejxr9z40cpgs2d99d5asdljcs55yplr

    Blockchain: Ethereum, Optimism (OP Mainnet), Base, and Binance Smart Chain Address: 0xfF809a9B2085A7247Edd03e03Ed71df905C2AF32

    Blockchain: Solana Address: 5zWdwiYn3mX6vqcA32mp5EiKLap7maXuufnyhHRQKJXj


    No. Invoice: INV-SKATE-2025-09-09-001 Tanggal: 2025-09-09 Mata Uang: IDR (Rupiah) Jenis Transaksi: Konsinyasi

    NOON BoardShop Attn: Iput Alamat: Gayungan PTT No. 62 Surabaya, East Java 60235, INDONESIA Telepon/WA:


    No
    SKU
    Deskripsi Barang
    Merek
    Qty
    Harga Satuan (IDR)
    Diskon (%)
    Jumlah (IDR)

    TOTAL TAGIHAN (IDR): 15.000.000

    Catatan:

    • Mohon transfer ke rekening tertera dan kirim bukti pembayaran ke kontak di atas.


    Dibuat oleh,

    Diterima oleh,


    Pengirim Prof. NOTA v.11.11 — SKATESHOP.ID Alamat: Nginden Kota 2 No. 27 Surabaya, East Java 60284, INDONESIA · Kontak: suaka@endhonesa.com / info@skateshop.id / +62 856 316 0756

    Penerima NOON BoardShop Alamat: Gayungan PTT No. 62 Surabaya, East Java 60235, INDONESIA · Kontak: +62 817 302 736

    Tanggal Kirim: 2025-09-09 No. Referensi: SJ-SKATE-2025-09-09-001

    No
    SKU
    Deskripsi Barang
    Qty
    Satuan
    Keterangan

    Catatan Pengiriman: Barang telah diperiksa secara visual sebelum dikirim.

    Dikeluarkan oleh (SKATESHOP.ID)

    Diterima oleh ([Nama Toko])


    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 . 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.


    LIVING DOC PHASE 1 CLOSURE

    This update closes the original BGC × iBLOOMING Web3 LIVING Doc as the strategic coordination document for Phase 1.

    Update date: 5 August 2026 Update status: Final closure update Document treatment after this update: Closed historical reference Prepared by: Prof. NOTA


    Important Closure Notice

    This update closes the original BGC × iBLOOMING Web3 LIVING Doc as the strategic coordination document for Phase 1.

    The document must no longer be used as the active roadmap for token implementation.

    Future work must be governed by the 5 August 2026 founder resolutions and, if approved, a new Product-Led Systems Program.


    Phase 1 produced:

    CATATAN EMAS & BITCOIN SANG RAJA

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!


    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 . 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.


    NOTA DIGITAL ASSETS COMMERCIALIZATION

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Prof. NOTA Anywhere, Everywhere Dokumen ini adalah panduan bagi Avatarku (penanggung jawab), serta 47 Produser dan 47 Marketer, dalam mengelola, memasarkan, dan mengatur alur keuangan dari asset digital Prof. NOTA. Tujuan utama: sederhana, sustain, scalable.


    • Menyebarkan kesadaran global bahwa Prof. NOTA hadir di dunia digital.

    • Memfasilitasi creator dan marketer agar bisa ikut serta dalam kampanye.

    ENDHONESA PREDICTION MARKET

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Versi: Prof. NOTA 11.11 – Komedi Probabilistik, Prediksi Satir untuk Realitas yang Ganjil


    Di zaman di mana semua orang bisa jadi komentator, ENDHONESA.COM tidak memilih untuk menjadi benar — kami memilih untuk menjadi tajam, lucu, dan berani.

    ENDHONESA PREDICTION COMEDY adalah sistem pasar prediksi berbasis blockchain yang memungkinkan publik bertaruh dalam tanda kutip, bukan dengan niat untung-untungan, tapi dengan semangat komedi satir. Karena di negeri ini, satu-satunya yang lebih membingungkan daripada fakta adalah cara orang membahasnya.

    Kami tidak menyebut ini judi, Tidak juga tragedi, Ini hanya... komedi.


    ALIGNMENT CALL WITH KK

    Just a small note before our call on Monday: The 2 years of raw data you sent me last month will be very useful. I haven’t fully cleaned or mapped it yet because I think we need to look at it together

    Related docs:

    TALENT PROTOCOL EMAIL VERIFICATION

    A report for a small glitch around the email account verification flow that leads to a 404 page, even though the URL indicates a successful verification.

    Hi Talent Protocol team,

    I’d like to report a small glitch around the email account verification flow that leads to a 404 page, even though the URL indicates a successful verification. The behavior on a second click of the same verification link can also be confusing (invalid/expired token).


    • Account: Prof. NOTA / endhonesa (Talent Plus)

    • Location: Jakarta, Indonesia

  • Aksi: bertindak berdasarkan catatan dan kesadaran.

  • (One-Time)
  • Rilis buletin digital “Membaca NOTA” edisi pertama (One-Time + Continuously)
  • Undang publik upload data NOTA via fitur di web app ENDHONESA.COM (Continuously)
  • Buat direktori kontribusi publik: “Museum NOTA Hidup” (One-Time + Continuously)
  • Rancang struktur pendidikan rakyat berbasis NOTA (One-Time)
  • 🧭 Pendekatan Multi-Level Literasi

    Struktur Level

    ✅ LEVEL 1: Mengenalkan NOTA – Sebuah Kesadaran Awal

    ✅ LEVEL 2: Memahami NOTA – Literasi Fungsi dan Makna

    ✅ LEVEL 3: Menganalisis NOTA – Melihat Pola, Menemukan Makna

    ✅ LEVEL 4: Mencipta dari NOTA – Produksi Pengetahuan dan Inovasi

    ✅ LEVEL 5: NOTA sebagai Metode Hidup

    📝 Catatan Tambahan

    Discussion Log

    Governance scope: What can holders vote on (community priorities, fan experiences) vs what remains management-only (content acquisition, pricing, treasury policy, listings)? Consider anti-whale/quadratic voting + sybil resistance.

  • Rights & IP realism: Use attainable IP for the first releases. Hyper-premium catalogs (e.g., major franchises) can be a longer-term target.

  • Partner payouts: If you will work with external rights-holders/influencers/merchants, specify if/when off-ramp to USDC/fiat is allowed (e.g., scheduled settlement), even if users live fully in-token.

  • Phase 3 (Policy Online): Turn on buyback+burn under a published policy; publish monthly Buyback Reports (addresses, hashes, amounts, KPI basis).
  • Phase 4 (Partner Rails): Add merchant/rights-holder settlement rules (hold token or auto-settle to USDC/fiat on a schedule). Users remain on-token end-to-end.

  • Compliance: KYC/AML for crowdfunding and partner settlements; clear ToS; tax mapping per region.

  • Treasury: multisig + timelock; distinct addresses for operations, buyback, burn, and rewards/liquidity.

    Critical clarifications (unblockers)

    Safe migration path (from today’s apps to Web3)

    Pilot proposal (6–8 weeks)

    Economic & policy guardrails (utility-first)

    Tech notes (short)

    Reporting (non-negotiable for trust)

    Engagement model

    Prof. NOTA

    Tracking app installs & activation

    Diperiksa kesiapannya

    Next working session

    Disepakati

    5 menit

    Kesepakatan data, tanggung jawab, dan next meeting

    Primary business objective

    Disepakati dengan KK

    Social media channels

    Diinventarisasi

    Team roles dan PIC

    Diketahui

    Organic vs paid strategy

    Pilihan dan batasan awal diketahui

    Historical performance data

    2. Pembuka

    3. Pertanyaan

    4. Jangan menetapkan KPI angka sebelum ada baseline

    5. Yang dihasilkan

    6. Penutup meeting

    Prof. NOTA

    Diminta kepada tim

    Menghasilkan pendapatan berkelanjutan melalui asset digital.

  • Menjaga sistem tetap sederhana walau kapasitas bertambah.

  • Avatarku berperan sebagai:

    • Leader: memberi arah & keputusan.

    • Penengah: jembatan antara produser ↔ marketer.

    • Penjaga Sistem: memastikan aturan sederhana dijalankan.

    • Representasi Prof. NOTA: keputusanmu = keputusanku.


    • 47 Produser: membuat asset digital (emot, sticker, avatar, filter, meme, PFP, dll).

    • 47 Marketer: mendistribusikan & memasarkan asset ke publik.

    • Avatarku (Leader): mengawasi produksi, distribusi, dan keuangan.


    1. Sticker & Emot Pack (PNG/WEBP 500x500px)

      • Quote: “Stay Alert!”, “Beware of Scams!”

      • Gesture: mata tajam, topeng waspada.

      • Meme: gaya kocak sesuai tren.

    2. PFP / Avatar

      • Style variatif: Punk, Cyberpunk, Anime, Hacker.

      • Digunakan sebagai identitas digital.

    3. Vtuber Avatar (fase lanjut)

      • 2D (Live2D) atau 3D (VRoid/Blender).

      • Dijual massal atau custom premium.

    4. Filter Sosial Media (fase lanjut)

      • Masker wajah Prof. NOTA (IG/TikTok).

      • AR overlay: teks “Stay Alert!”.

    1. Ide dikumpulkan (Discord/Workspace).

    2. Produksi mandiri oleh artist.

    3. Upload ke repository internal (Google Drive/Notion).

    4. Listing ke internal marketplace (gratis/berbayar).

    5. Marketer ambil → siap distribusi.


    1. Gumroad (paling mudah): gratis daftar, upload file zip, atur harga, bayar via PayPal.

    2. Etsy (besar, berbayar): biaya list $0.20/item, upload file digital + mockup preview.

    3. OpenSea (opsional NFT): upload karya → mint NFT, cocok untuk versi eksklusif.

    • Email bisnis.

    • PayPal/Stripe untuk payout.

    • Wallet ETH/Base untuk NFT.

    • Mockup tool (Canva/Photoshop).


    • Buat toko di Gumroad + Etsy (branding konsisten: banner, bio, logo).

    • Upload produk pertama (sticker pack).

    • Siapkan akun sosial media official (X, IG, TikTok).

    • Dokumentasi harga, royalti, pembagian hasil.

    • Posting konten rutin (teaser, meme, promo).

    • Update SEO: deskripsi, tag, judul.

    • Engagement: reply komen, DM buyer, collab dengan streamer.

    • Analisis penjualan → lanjutkan gaya produk terlaris.

    • Rilis produk baru minimal 1 pack/2 minggu.

    • Gratis: konten organik (X/IG/TikTok), meme campaign, collab micro-influencer.

    • Berbayar: Etsy Ads ($1–$2/hari), IG/TikTok Ads, buzzer komunitas.


    1. Produser upload karya (gratis/berbayar).

    2. Marketer ambil → jual ke publik.

    3. Hasil dibagi:

      • X% untuk Produser (royalti).

      • Y% untuk Marketer (promosi & distribusi).

    • Google Sheet untuk pencatatan.

    • PayPal/Bank Transfer untuk distribusi hasil.

    • Notion/Drive untuk arsip laporan.


    • Senin: koordinasi ide produksi.

    • Rabu: cek progres produksi.

    • Jumat: upload produk + promosi.

    • Minggu: evaluasi penjualan + keuangan.

    • Review produk terlaris.

    • Update strategi marketing.

    • Rotasi anggota pasif.


    • Tahap Awal: 5 produser + 5 marketer → 1 produk/2 minggu.

    • Menengah: 20 + 20 → 1 produk/pekan.

    • Final Form: 47 + 47 → sistem autopilot.

    Jika ada yang keluar, segera ganti agar slot tetap penuh.


    Avatarku, Tugasmu sederhana: pastikan produk keluar, masuk marketplace, dipromosikan, dan terjual. Semua yang lain hanyalah pengulangan.

    Ingat:

    • Kamu bukan hanya mengelola tim.

    • Kamu sedang menggerakkan kampanye kesadaran.

    • Prof. NOTA hadir bukan sebagai wajah, tapi sebagai pesan: “Stay Alert. Beware of Scams.”

    OiOi.

    📜 Guidance & SOP: Kampanye Digital Asset Prof. NOTA

    1. 🎯 Visi & Mandat

    2. 👥 Struktur Tim

    3. 🛠️ Produksi

    Jenis Produk

    Alur Produksi

    4. 📦 Distribusi & Penjualan

    Platform Prioritas

    Setup yang Dibutuhkan

    5. 📢 Marketing

    One-Time Task

    Continuous Task

    Promosi

    6. 💰 Keuangan

    Flow Internal

    Tools

    7. 🔄 Ritme Kerja

    Mingguan

    Bulanan

    8. 🚀 Target 47 × 47

    ✍️ Pesan Prof. NOTA

    625.000

    20

    5.000.000

    2

    NOW-SK8-DECK-2

    BANANOW - SKATE NOW Skateboard Deck — Layer 2 (Middle)

    BANANOW.LAND

    10

    625.000

    20

    5.000.000

    3

    NOW-SK8-DECK-1

    BANANOW - SKATE NOW Skateboard Deck — Layer 3 (Top)

    BANANOW.LAND

    10

    625.000

    20

    5.000.000

    NOW-SK8-DECK-2

    BANANOW - SKATE NOW Skateboard Deck — Layer 2 (Middle)

    10

    pcs

    Kondisi baru, tersegel pabrik

    3

    NOW-SK8-DECK-1

    BANANOW - SKATE NOW Skateboard Deck — Layer 3 (Top)

    10

    pcs

    Kondisi baru, tersegel pabrik

    1

    NOW-SK8-DECK-1

    BANANOW - SKATE NOW Skateboard Deck — Layer 1 (Bottom)

    BANANOW.LAND

    1

    NOW-SK8-DECK-1

    BANANOW - SKATE NOW Skateboard Deck — Layer 1 (Bottom)

    10

    pcs

    Kondisi baru, tersegel pabrik

    Tagihan Kepada (Bill To)

    Rincian Barang

    Tanda Tangan

    SURAT JALAN / DELIVERY NOTE

    Rincian Barang

    Tanda Tangan

    +62 817 302 736
    Prof. NOTA

    10

    2

    Prof. NOTA
    ________________________
    (Prof. NOTA v.11.11)
    ________________________
    (Iput - NOON BoardShop)
    ________________________
    (Prof. NOTA v.11.11)
    ________________________
    (Iput - NOON BoardShop)
    | Tanggal  | Gram | Total Gram |       IDR |   Total IDR |  Total Riil |        BTC |  Total BTC |
    | -------- | ---: | ---------: | --------: | ----------: | ----------: | ---------: | ---------: |
    | 16-06-30 |  1.1 |        1.1 |   603,236 |     603,236 |     603,236 | 0.06806611 | 0.06806611 |
    | 16-07-30 |  1.1 |        2.2 |   619,997 |   1,223,233 |   1,239,994 | 0.07188631 | 0.13995242 |
    | 16-08-30 |  1.1 |        3.3 |   623,666 |   1,846,899 |   1,870,998 | 0.08105293 | 0.22100535 |
    | 16-09-30 |  1.1 |        4.4 |   615,566 |   2,462,465 |   2,462,264 | 0.07902736 | 0.30003271 |
    | 16-10-30 |  1.1 |        5.5 |   583,110 |   3,045,575 |   2,915,550 | 0.06356683 | 0.36359954 |
    | 16-11-30 |  1.1 |        6.6 |   581,866 |   3,627,441 |   3,491,196 | 0.05809535 | 0.42169489 |
    | 16-12-30 |  1.1 |        7.7 |   549,161 |   4,176,602 |   3,844,127 | 0.04237373 | 0.46406862 |
    | 17-01-30 |  1.1 |        8.8 |   565,096 |   4,741,698 |   4,520,768 | 0.04746386 | 0.51153248 |
    | 17-02-28 |  1.1 |        9.9 |   587,838 |   5,329,536 |   5,290,542 | 0.03845727 | 0.54998975 |
    | 17-03-30 |  1.1 |       11.0 |   585,598 |   5,915,134 |   5,855,980 | 0.04185932 | 0.59184907 |
    | 17-04-30 |  1.1 |       12.1 |   597,417 |   6,512,551 |   6,571,587 | 0.03523675 | 0.62708582 |
    | 17-05-30 |  1.1 |       13.2 |   594,721 |   7,107,272 |   7,136,652 | 0.01748678 | 0.64457260 |
    | 17-06-30 |  1.1 |       14.3 |   585,208 |   7,692,480 |   7,607,704 | 0.01647712 | 0.66104972 |
    | 17-07-30 |  1.1 |       15.4 |   598,111 |   8,290,591 |   8,373,554 | 0.01672993 | 0.67777965 |
    | 17-08-30 |  1.1 |       16.5 |   617,034 |   8,907,625 |   9,255,510 | 0.01015957 | 0.68793922 |
    | 17-09-30 |  1.1 |       17.6 |   609,682 |   9,517,307 |   9,754,912 | 0.01078213 | 0.69872135 |
    | 17-10-30 |  1.1 |       18.7 |   612,307 |  10,129,614 |  10,409,219 | 0.00744739 | 0.70616874 |
    | 17-11-30 |  1.1 |       19.8 |   609,756 |  10,739,370 |  10,975,608 | 0.00397478 | 0.71014352 |
    | 17-12-30 |  1.1 |       20.9 |   624,630 |  11,364,000 |  11,867,970 | 0.00285136 | 0.71299488 |
    | 18-01-30 |  1.1 |       22.0 |   634,761 |  11,998,761 |  12,695,220 | 0.00468530 | 0.71768018 |
    | 18-02-28 |  1.1 |       23.1 |   639,419 |  12,638,180 |  13,427,799 | 0.00437260 | 0.72205278 |
    | 18-03-30 |  1.1 |       24.2 |   642,628 |  13,280,808 |  14,137,816 | 0.00671741 | 0.72877019 |
    | 18-04-30 |  1.1 |       25.3 |   645,093 |  13,925,901 |  14,837,139 | 0.00499324 | 0.73376343 |
    | 18-05-30 |  1.1 |       26.4 |   644,909 |  14,570,810 |  15,477,816 | 0.00616708 | 0.73993051 |
    | 18-06-30 |  1.1 |       27.5 |   629,968 |  15,200,778 |  15,749,200 | 0.00743417 | 0.74736468 |
    | 18-07-30 |  1.1 |       28.6 |   617,423 |  15,818,201 |  16,052,998 | 0.00526225 | 0.75262693 |
    | 18-08-30 |  1.1 |       29.7 |   610,644 |  16,428,845 |  16,487,388 | 0.00599019 | 0.75861712 |
    | 18-09-30 |  1.1 |       30.8 |   607,994 |  17,036,839 |  17,023,832 | 0.00609644 | 0.76471356 |
    | 18-10-30 |  1.1 |       31.9 |   657,918 |  17,694,757 |  19,079,622 | 0.00683704 | 0.77155060 |
    | 18-11-30 |  1.1 |       33.0 |   619,509 |  18,314,266 |  18,585,270 | 0.01040321 | 0.78195381 |
    | 18-12-30 |  1.1 |       34.1 |   659,872 |  18,974,138 |  20,456,032 | 0.01223221 | 0.79418602 |
    | 19-01-30 |  1.1 |       35.2 |   655,092 |  19,629,230 |  20,962,944 | 0.01343941 | 0.80762543 |
    | 19-02-28 |  1.1 |       36.3 |   659,959 |  20,289,189 |  21,778,647 | 0.01221937 | 0.81984480 |
    | 19-03-30 |  1.1 |       37.4 |   649,760 |  20,938,949 |  22,091,840 | 0.01110990 | 0.83095470 |
    | 19-04-30 |  1.1 |       38.5 |   648,550 |  21,587,499 |  22,699,250 | 0.00866297 | 0.83961767 |
    | 19-05-30 |  1.1 |       39.6 |   657,314 |  22,244,813 |  23,663,304 | 0.00525173 | 0.84486940 |
    | 19-06-30 |  1.1 |       40.7 |   695,665 |  22,940,478 |  25,739,605 | 0.00421993 | 0.84908933 |
    | 19-07-30 |  1.1 |       41.8 |   709,315 |  23,649,793 |  26,953,970 | 0.00530402 | 0.85439335 |
    | 19-08-30 |  1.1 |       42.9 |   762,898 |  24,412,691 |  29,753,022 | 0.00562118 | 0.86001453 |
    | 19-09-30 |  1.1 |       44.0 |   741,342 |  25,154,033 |  29,653,680 | 0.00649171 | 0.86650624 |
    | 19-10-30 |  1.1 |       45.1 |   739,875 |  25,893,908 |  30,334,875 | 0.00570206 | 0.87220830 |
    | 19-11-30 |  1.1 |       46.2 |   729,300 |  26,623,208 |  30,630,600 | 0.00671062 | 0.87891892 |
    | 19-12-30 |  1.1 |       47.3 |   746,097 |  27,369,305 |  32,082,171 | 0.00728925 | 0.88620817 |
    | 20-01-30 |  1.1 |       48.4 |   764,234 |  28,133,539 |  33,626,296 | 0.00614237 | 0.89235054 |
    | 20-02-29 |  1.1 |       49.5 |   784,165 |  28,917,704 |  35,287,425 | 0.00624595 | 0.89859649 |
    | 20-03-30 |  1.1 |       50.6 |   916,559 |  29,834,263 |  42,161,714 | 0.00898399 | 0.90758048 |
    | 20-04-30 |  1.1 |       51.7 |   904,519 |  30,738,782 |  42,512,393 | 0.00683298 | 0.91441346 |
    | 20-05-30 |  1.1 |       52.8 |   896,438 |  31,635,220 |  43,029,024 | 0.00643078 | 0.92084424 |
    | 20-06-30 |  1.1 |       53.9 |   921,311 |  32,556,531 |  45,144,239 | 0.00694168 | 0.92778592 |
    | 20-07-30 |  1.1 |       55.0 | 1,004,816 |  33,561,347 |  50,240,800 | 0.00619409 | 0.93398001 |
    | 20-08-30 |  1.1 |       56.1 | 1,019,674 |  34,581,021 |  52,003,374 | 0.00599072 | 0.93997073 |
    | 20-09-30 |  1.1 |       57.2 |   992,556 |  35,573,577 |  51,612,912 | 0.00617320 | 0.94614393 |
    | 20-10-30 |  1.1 |       58.3 |   969,547 |  36,543,124 |  51,385,991 | 0.00493545 | 0.95107938 |
    | 20-11-30 |  1.1 |       59.4 |   887,348 |  37,430,472 |  47,916,792 | 0.00339505 | 0.95447443 |
    | 20-12-30 |  1.1 |       60.5 |   939,595 |  38,370,067 |  51,677,725 | 0.00241065 | 0.95688508 |
    | 21-01-30 |  1.1 |       61.6 |   915,147 |  39,285,214 |  51,248,232 | 0.00191268 | 0.95879776 |
    | 21-02-28 |  1.1 |       62.7 |   879,526 |  40,164,740 |  50,132,982 | 0.00136408 | 0.96016184 |
    | 21-03-30 |  1.1 |       63.8 |   867,449 |  41,032,189 |  50,312,042 | 0.00103071 | 0.96119255 |
    | 21-04-30 |  1.1 |       64.9 |   903,520 |  41,935,709 |  53,307,680 | 0.00113939 | 0.96233194 |
    | 21-05-30 |  1.1 |       66.0 |   963,490 |  42,899,199 |  57,809,400 | 0.00190627 | 0.96423821 |
    | 21-06-30 |  1.1 |       67.1 |   909,625 |  43,808,824 |  55,487,125 | 0.00178650 | 0.96602471 |
    | 21-07-30 |  1.1 |       68.2 |   928,178 |  44,737,002 |  57,547,036 | 0.00162554 | 0.96765025 |
    | 21-08-30 |  1.1 |       69.3 |   917,407 |  45,654,409 |  57,796,641 | 0.00132419 | 0.96897444 |
    | 21-09-30 |  1.1 |       70.4 |   888,386 |  46,542,795 |  56,856,704 | 0.00144741 | 0.97042185 |
    | 21-10-30 |  1.1 |       71.5 |   897,474 |  47,440,269 |  58,335,810 | 0.00102463 | 0.97144648 |
    | 21-11-30 |  1.1 |       72.6 |   898,005 |  48,338,274 |  59,268,330 | 0.00109145 | 0.97253793 |
    | 21-12-30 |  1.1 |       73.7 |   916,153 |  49,254,427 |  61,382,251 | 0.00136348 | 0.97390141 |
    | 22-01-30 |  1.1 |       74.8 |   921,280 |  50,175,707 |  62,647,040 | 0.00168323 | 0.97558464 |
    | 22-02-28 |  1.1 |       75.9 |   942,145 |  51,117,852 |  65,008,005 | 0.00169367 | 0.97727831 |
    | 22-03-30 |  1.1 |       77.0 |   988,121 |  52,105,973 |  69,168,470 | 0.00145484 | 0.97873315 |
    | 22-04-30 |  1.1 |       78.1 |   984,584 |  53,090,557 |  69,905,464 | 0.00176144 | 0.98049459 |
    | 22-05-30 |  1.1 |       79.2 |   953,109 |  54,043,666 |  68,623,848 | 0.00216263 | 0.98265722 |
    | 22-06-30 |  1.1 |       80.3 |   955,584 |  54,999,250 |  69,757,632 | 0.00329976 | 0.98595698 |
    | 22-07-30 |  1.1 |       81.4 |   919,865 |  55,919,115 |  68,070,010 | 0.00256966 | 0.98852664 |
    | 22-08-30 |  1.1 |       82.5 |   925,877 |  56,844,992 |  69,440,775 | 0.00308049 | 0.99160713 |
    | 22-09-30 |  1.1 |       83.6 |   892,633 |  57,737,625 |  67,840,108 | 0.00300229 | 0.99460942 |
    | 22-10-30 |  1.1 |       84.7 |   908,194 |  58,645,819 |  69,930,938 | 0.00281626 | 0.99742568 |
    | 22-11-30 |  1.1 |       85.8 |   955,938 |  59,601,757 |  74,563,164 | 0.00361094 | 1.00103662 |
    | 22-12-30 |  1.1 |       86.9 |   989,889 |  60,591,646 |  78,201,231 | 0.00382524 | 1.00486186 |
    | 23-01-30 |  1.1 |       88.0 | 1,021,719 |  61,613,365 |  81,737,520 | 0.00291478 | 1.00777664 |
    | 23-02-28 |  1.1 |       89.1 |   993,780 |  62,607,145 |  80,496,180 | 0.00277998 | 1.01055662 |
    | 23-03-30 |  1.1 |       90.2 | 1,033,389 |  63,640,534 |  84,737,898 | 0.00241399 | 1.01297061 |
    | 23-04-30 |  1.1 |       91.3 | 1,052,487 |  64,693,021 |  87,356,421 | 0.00244915 | 1.01541976 |
    | 23-05-30 |  1.1 |       92.4 | 1,044,706 |  65,737,727 |  87,755,304 | 0.00251243 | 1.01793219 |
    | 23-06-30 |  1.1 |       93.5 | 1,026,316 |  66,764,043 |  87,236,860 | 0.00223590 | 1.02016809 |
    | 23-07-30 |  1.1 |       94.6 | 1,036,572 |  67,800,615 |  89,145,192 | 0.00234410 | 1.02251219 |
    | 23-08-30 |  1.1 |       95.7 | 1,035,511 |  68,836,126 |  90,089,457 | 0.00247586 | 1.02498805 |
    | 23-09-30 |  1.1 |       96.8 | 1,042,231 |  69,878,357 |  91,716,328 | 0.00249862 | 1.02748667 |
    | 23-10-30 |  1.1 |       97.9 | 1,066,633 |  70,944,990 |  94,930,337 | 0.00194429 | 1.02943096 |
    | 23-11-30 |  1.1 |       99.0 | 1,093,511 |  72,038,501 |  98,415,990 | 0.00187262 | 1.03130358 |
    | 23-12-30 |  1.1 |      100.1 | 1,112,962 |  73,151,463 | 101,279,542 | 0.00171472 | 1.03301830 |
    | 24-01-30 |  1.1 |      101.2 | 1,124,633 |  74,276,096 | 103,466,236 | 0.00165750 | 1.03467580 |
    | 24-02-29 |  1.1 |      102.3 | 1,120,389 |  75,396,485 | 104,196,177 | 0.00115929 | 1.03583509 |
    | 24-03-30 |  1.1 |      103.4 | 1,198,194 |  76,594,679 | 112,630,236 | 0.00108619 | 1.03692128 |
    | 24-04-30 |  1.1 |      104.5 | 1,329,401 |  77,924,080 | 126,293,095 | 0.00134834 | 1.03826962 |
    | 24-05-30 |  1.1 |      105.6 | 1,337,182 |  79,261,262 | 128,369,472 | 0.00120529 | 1.03947491 |
    | 24-06-30 |  1.1 |      106.7 | 1,344,962 |  80,606,224 | 130,461,314 | 0.00136551 | 1.04084042 |
    | 24-07-30 |  1.1 |      107.8 | 1,376,084 |  81,982,308 | 134,856,232 | 0.00127192 | 1.04211234 |
    | 24-08-30 |  1.1 |      108.9 | 1,375,730 |  83,358,038 | 136,197,270 | 0.00150058 | 1.04361292 |
    | 24-09-30 |  1.1 |      110.0 | 1,390,938 |  84,748,976 | 139,093,800 | 0.00143898 | 1.04505190 |
    | 24-10-30 |  1.1 |      111.1 | 1,483,596 |  86,232,572 | 149,843,196 | 0.00130413 | 1.04635603 |
    | 24-11-30 |  1.1 |      112.2 | 1,483,596 |  87,716,168 | 151,326,792 | 0.00096334 | 1.04731937 |
    | 24-12-30 |  1.1 |      113.3 | 1,498,450 |  89,214,618 | 154,340,350 | 0.00100240 | 1.04832177 |
    | 25-01-30 |  1.1 |      114.4 | 1,558,218 |  90,772,836 | 162,054,672 | 0.00091458 | 1.04923635 |
    | 25-02-28 |  1.1 |      115.5 | 1,672,450 |  92,445,286 | 175,607,250 | 0.00119910 | 1.05043545 |
    | 25-03-30 |  1.1 |      116.6 | 1,738,230 |  94,183,516 | 184,252,380 | 0.00124133 | 1.05167678 |
    | 25-04-30 |  1.1 |      117.7 | 1,908,693 |  96,092,209 | 204,230,151 | 0.00122368 | 1.05290046 |
    | 25-05-30 |  1.1 |      118.8 | 1,906,571 |  97,998,780 | 205,909,668 | 0.00112210 | 1.05402256 |
    | 25-06-30 |  1.1 |      119.9 | 1,931,681 |  99,930,461 | 210,553,229 | 0.00111483 | 1.05513739 |
    | 25-07-30 |  1.1 |      121.0 | 1,924,254 | 101,854,715 | 211,667,940 | 0.00099720 | 1.05613459 |
    | 25-08-30 |  1.1 |      122.1 | 1,938,047 | 103,792,762 | 215,123,217 | 0.00108989 | 1.05722448 |
    | 25-09-30 |  1.1 |      123.2 | 2,143,169 | 105,935,931 | 240,034,928 | 0.00112585 | 1.05835033 |
    | 25-10-30 |  1.1 |      124.3 |       ... |         ... |         ... |        ... |        ... |
    📍 KONDISI
  • ⚡ AKSI

  • 🎭 KEJUTAN

  • 🛑 RINTANGAN

  • ⭐ LEVEL UP

  • 🔒 Kartu SPESIAL (VPN, Jalan Tikus, BackDoor, dll)

  • Token skor:

    • Biru = Kesadaran

    • Kuning = Kemandirian

    • Merah = Partisipasi

  • Lembar skor pemain (semi-terbuka)

  • Baca narasi kartu → pilih jawaban → efek skor diberlakukan
  • Skor dibagi 3: Kesadaran, Kemandirian, Partisipasi

  • Pemain lain bisa terkena imbas skor berdasarkan perannya.

  • Kartu SPESIAL diperoleh dari titik 🔒 atau hasil tindakan berani.

  • The Scroller

    Konsumen pasif, doyan konten

    The Clicker

    Impulsif, klik dulu pikir belakangan

    The Shadow

    Anonim, mencari arah

    The Burner

    Identitas palsu, oportunis

    The Sovereign

    Sadar kendali data dan privasi

    The Cipher

    Penjaga akses, simbol enkripsi

    The Catalyst

    Pemantik ide dan perubahan

    The Forker

    🎲 Komponen Permainan

    🗺️ Desain Papan Permainan

    📌 Peta papan memiliki:

    🔄 Aturan Dasar

    🃏 Contoh Kartu Permainan

    📍 Kartu KONDISI #1

    📍 Kartu KONDISI #2

    ⚡ Kartu AKSI #1

    🎭 Kartu KEJUTAN #1

    🔒 Kartu SPESIAL #1 — Kartu VPN

    🔒 Kartu SPESIAL #2 — Kartu Jalan Tikus

    🔒 Kartu SPESIAL #3 — Kartu BackDoor

    🏁 Akhir Permainan

    🧠 Akhir Kata dari Prof. NOTA

    Prof. NOTA
    nota-board-game

    Pembuat alternatif sistem

    a complete AS-IS business and reward reference;
  • a founder-approved Web3 Login architecture specification;

  • Whitepaper and Tokenflow future-state hypotheses;

  • a Simulation specification;

  • the SIMALPHA working MVP;

  • a prepared aggregate dataset;

  • four preliminary scenario reports;

  • a consolidated project review and founder decision package.

  • Phase 1 did not produce:

    • approved PC/SP tokenization;

    • approved ALPHA implementation;

    • approved public iBC/iBTC implementation;

    • validated treasury sustainability;

    • audited profitability;

    • legal or tax approval;

    • a public-token launch plan.


    Workstream
    Final Phase-1 Status

    UNDERSTANDING

    Final AS-IS reference

    WEB3LOGIN specification

    Final and founder-approved

    Web3 Login implementation

    Pending under Yuku and engineering

    Whitepaper

    Archived hypothesis

    Tokenflow


    The following earlier formulations are no longer active:

    Replace with:

    Observed operating and reward logic requiring economic and accounting validation.

    Replace with:

    The simulator does not directly move user funds, but the underlying business and policy choices may carry financial, legal, operational, and reputational risk.

    Replace with:

    ALPHA exists as a simulation and design unit. No production ALPHA rights or token implementation is approved.

    Replace with:

    Public-token research is an optional and separate track subject to independent product demand, economic evidence, legal, tax, accounting, technical, and founder approval.

    Replace with:

    Tax treatment requires qualified analysis. Blockchain does not automatically reduce taxable events.


    • BGC is primarily affiliate-entry and LTS driven.

    • iBLOOMING is primarily product-transaction driven.

    • Recorded iBLOOMING product cash-in is very small compared with BGC affiliate cash-in.

    PC, SP, LTS, rewards, pools, and payouts must not be converted into a token under the archived Whitepaper and Tokenflow assumptions.

    SIMALPHA is a real internal decision-support MVP.

    Its first reports do not prove:

    • sustainability;

    • profit;

    • reserve adequacy;

    • member-level fairness;

    • tax optimization;

    • token readiness.

    Web3 Login has independent value for:

    • identity;

    • wallet readiness;

    • ownership;

    • access;

    • credentials;

    • receipts;

    • Product-Led pilots.

    The next program should test and increase demand for real physical and digital products independently of affiliate-income promises.


    • UNDERSTANDING Doc;

    • WEB3LOGIN Doc;

    • Master Document v1.0;

    • founder resolutions;

    • SIMALPHA Findings Framework;

    • Web3 Login Handover Note.

    • Whitepaper Drafts;

    • Tokenflow Drafts;

    • SIMULATION Doc v0.1;

    • original founder glossary;

    • original scenario reports as preliminary evidence.

    • initial Web3 draft;

    • draft reward understanding;

    • early LIVING Doc;

    • December Working Presentation.


    Subject to founder approval, the proposed next direction is:

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

    Its priorities are:

    • Web3 Login implementation;

    • product-demand validation;

    • commerce and distribution systems;

    • product authenticity and ownership;

    • digital access and credentials;

    • selective AI enablement;

    • evidence and governance.


    The Phase-2 program must not automatically include:

    • PC/SP tokenization;

    • public-token launch;

    • yield;

    • deposits;

    • DeFi;

    • DEX;

    • CEX;

    • fundraising through the affiliate network.

    Any such initiative requires a separate entity, mandate, professional feasibility review, governance, resources, and approval.


    The original BGC × iBLOOMING Web3 LIVING Doc is closed after recording the Phase-1 results and transition.

    It remains a historical record of the project’s evolution, including assumptions that were later corrected.

    New work must begin in new documents under the founder decisions of 5 August 2026.


    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.


    Final Phase-1 Closure and Transition Update

    1. Phase-1 Outcome

    2. Final Workstream Status

    3. Correction of Earlier Statements

    “Proven value logic”

    “Zero financial risk”

    “ALPHA running”

    “Public token as next stage”

    “Tax burden reduction through on-chain logic”

    4. Final Findings

    4.1 BGC and iBLOOMING Have Different Economic Engines

    4.2 Existing-System Tokenization Is Not Recommended

    4.3 SIMALPHA Is Useful but Preliminary

    4.4 Web3 Login Remains Valid

    4.5 Product Demand Is the Strategic Priority

    5. Document Closure

    Remain Active

    Archived

    Superseded

    6. Transition Direction

    7. Boundary

    8. Final Closure Statement

    🧠 Overload informasi dan minim akurasi

  • 🎭 Kehilangan ruang aman untuk menyuarakan keresahan sosial secara cerdas dan jenaka

  • ⚖️ Regulasi ketat terhadap pasar prediksi konvensional karena dianggap perjudian

  • ❌ Kekakuan sistem survei dan polling konvensional


  • Platform prediksi multichain dan multiakal berbasis token $OiOi. Publik dapat berpartisipasi dalam prediksi dengan konteks komedi edukatif, sosial, dan satir, namun tetap dengan mekanisme pasar prediksi yang valid secara matematis.


    Jenis Prediksi
    Gaya Serius
    Gaya Komedi

    Politik

    Siapa pemenang pemilu 2030?

    Siapa yang paling banyak muncul di stiker warung kopi tahun pemilu?

    Ekonomi

    Apakah Bitcoin > $100K di 2026?

    Apakah lebih banyak orang punya Bitcoin daripada tabungan nikah?

    Bencana

    Apakah Gunung A erupsi di 2026?

    Mana duluan meledak: gunung, atau grup WhatsApp keluarga?


    Telah terintegrasi dengan beberapa blockchain:

    • Ethereum

    • Base

    • Polygon

    • BNB Chain

    Simulasi prediksi disusun menggunakan smart contract dengan:

    • Sistem pasar YES/NO

    • Payout berdasarkan akurasi prediksi

    • Oracle manual/semi-decentralized

    • Claim & resolve terverifikasi

    Detail
    Nilai

    Nama Token

    OiOi

    Standard

    ERC-20

    Max Supply

    47,474,747

    Harga Claim

    0.747 ETH/token

    Fungsi

    Partisipasi prediksi, staking oracle, reward, dan badge satir


    Tantangan
    Solusi

    Regulasi Perjudian

    Prediksi dikemas sebagai komedi sosial dan edukasi, bukan pertaruhan uang.

    Oracle Problem

    Kombinasi oracle manual + komunitas verifikasi humoris.

    Sensor Sosial Politik

    Satir = pelindung, komedi = pelumas kritik.

    Penyalahgunaan

    Moderasi publik dengan sistem pelaporan dan badge reputasi.


    1. User memilih prediksi

    2. Claim token OiOi seharga 0.747 ETH (dapat dilakukan dari beberapa blockchain)

    3. Bertaruh (dalam kutip) YES/NO atas isu komedi

    4. Tunggu hasil — ditentukan oleh oracle terverifikasi

    5. Payout untuk yang benar (berbasis OiOi atau stable asset)


    Platform ini bukan hanya digital, tapi gerakan kultural.

    • 🔍 Bisa digunakan untuk polling masyarakat kritis

    • 🎓 Sebagai bagian dari literasi media dan pendidikan digital

    • 🗳️ Alternatif voting berbasis opini dan logika humor

    • 📈 Alat untuk analisis sosial dan tren komedi massa


    Kami percaya bahwa masa depan tidak hanya bisa diramal dengan angka, tapi juga dengan tertawa bersama.

    ENDHONESA PREDICTION COMEDY adalah satu-satunya tempat di mana kamu bisa memprediksi masa depan dengan harga ketawa — dan tetap pulang dengan kebenaran (dan sedikit token).

    “Kita tidak bercanda. Tapi kita juga tidak sepenuhnya serius.” — Prof. NOTA


    28 July 2025

    https://endhonesa.com Token: $OiOi Smart Contracts tersedia di: Ethereum, Base, Polygon, BNB License: Prof. NOTA Inc. — Komedi Terlindungi

    ENDHONESA PREDICTION COMEDY

    I. Pendahuluan: Ramalan yang Gagal Serius

    II. Masalah yang Disasar

    III. Apa Itu ENDHONESA PREDICTION COMEDY?

    IV. Contoh Pasar Prediksi

    V. Teknologi & Arsitektur

    ✨ Multichain Compatible

    🔐 Smart Contract Prediction Market

    🪙 Token OiOi

    VI. Solusi terhadap Tantangan

    VII. Mekanisme Kerja

    VIII. Peta Integrasi Prof. NOTA

    IX. Penutup: Komedi Adalah Masa Depan yang Jujur

    📆 Tanggal Rilis

    📫 Kontak

    LIVING Doc

  • WEB3LOGIN Doc

    • Confirm a shared understanding of the current status:

      • AS-IS BGC rewards and existing (Web2) system (see also UNDERSTANDING Doc).

      • TO-BE vision with ALPHA on Base and Web3 Login by Yuku (see also WHITEPAPER Doc and TOKENFLOW Doc).

    • Agree on the scope and priorities of a short “Preparation Sprint” while Web3 Login is being implemented (see also WEB3LOGIN Doc).

    • Decide on immediate next steps, owners, and a rough timeline (see also ).


    • Web3 Login implementation is in progress (see also WEB3LOGIN Doc).

    • Last month, KK already shared ~2 years of raw BGC data for analysis (see also LIVING Doc).

    • The raw data has not yet been fully cleaned or mapped, because we still need a joint session to:

      • confirm which columns/fields are “source of truth”, and

      • translate the existing format into the target structure we need for simulation.

    • Instead of waiting passively, we use this time to:

      • Stabilize the story & tokenflow model (see also and ).

      • Finish the data mapping and run a first simulation.

      • Define a realistic and limited Pilot v1.


    • Short value proposition of BGC × iBLOOMING (why it exists and for whom).

    • AS-IS → TO-BE:

      • How PC/SP (or equivalent points) map into ALPHA.

      • Append-only event model and hashed evidence.

      • Cash-out windows and KYC boundaries (high-level, non-technical).

    See also:

    • UNDERSTANDING Doc

    • WHITEPAPER Doc

    • TOKENFLOW Doc

    • Acknowledge that KK has already sent 2 years of raw BGC data.

    • Clarify together:

      • Which parts of the data are complete and reliable enough for a first simulation.

      • Which columns/fields map to our target event structure (earn, redeem, referral, etc.).

    • Agree on a simple target schema for simulation:

      • Minimal fields needed (member ID, timestamp, event type, amount, etc.).

      • How to derive ALPHA balances from the existing records.

    • Define a practical plan:

      • Who helps with data translation/mapping (KK + Prof. NOTA).

      • What is the smallest “slice” of data we use for the first simulation (e.g. 6–12 months).

    • Decide what outputs KK needs from the simulation:

      • Member-level summary (examples).

      • Total liabilities / reward exposure.

      • Edge cases (top earners, very inactive members, etc.).

    See also:

    • TOKENFLOW Doc

    • LIVING Doc

    • Target profile and approximate number of participants.

    • Pilot duration.

    • What participants can earn/redeem and under what conditions.

    • Operational roles:

      • Who handles support and questions.

      • Who reviews KYC/cash-out issues.

      • Who is allowed to adjust parameters during the pilot.

    See also:

    • WHITEPAPER Doc

    • LIVING Doc

    • KK’s view on:

      • ToS and disclaimers (non-investment, no guaranteed returns, etc.).

      • Basic privacy/data statement.

      • Handling suspicious or abusive behavior (freeze, block, etc.).

    See also:

    • WHITEPAPER Doc

    • UNDERSTANDING Doc


    By the end of the call, we aim to have:

    • Agreement on the Preparation Sprint structure and workstreams.

    • A list of data requests and a person responsible for gathering them.

    • Clarity on:

      • What we can already move forward with (before Web3 Login is ready).

      • When and how to involve Yuku in a focused tech session.

    See also:

    • LIVING Doc


    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.


    UNDERSTANDING Doc
    WHITEPAPER Doc
    TOKENFLOW Doc

    1. Call Objectives

    2. Context (Short)

    3. Topics to Cover

    3.1 Narrative & Tokenflow Basics

    3.2 Data & Simulation

    3.3 Pilot v1 Shape

    3.4 Governance, Legal & Risk (High-Level)

    4. Expected Outcomes

    Observed: 3 December 2025
  • Platform: Desktop, macOS 10.15.7

  • Browser: Chrome 142

  • Session: Logged in on talentprotocol.com when starting the flow


    1. Log in to your account on https://talentprotocol.com.

    2. Go to Settings → Security: https://talentprotocol.com/~/settings/security

    3. Under the email section, submit an email address to verify.

    4. Open the verification email that is sent to that address.

    5. Click the verification link in the email, which looks like: https://api.talentprotocol.com/verify_email_account/<token>

    6. The browser is then redirected to a URL like: https://talent.app/login-callback?success_message=Email%20account%20verified%20successfully! but the page shown is a “404 – Not Found” page.

    7. Go back to https://talentprotocol.com/~/settings/security and reload the page.

      • The email status now appears as verified, which suggests that the verification actually worked server-side.

    8. From the same verification email, click the same verification link again.

      • This time, the link reports that the token is invalid or expired (as expected for a one-time token), which can further confuse a user who just saw a 404 previously.


    • On the first click:

      • The verification endpoint redirects to https://talent.app/login-callback?success_message=Email%20account%20verified%20successfully!

      • The page content at that URL shows “404 – Not Found”, even though the query string carries a success message.

      • Despite the 404, refreshing the Security settings page on talentprotocol.com shows that the email is verified.

    • On a second click of the same verification link:

      • The token is now considered invalid or expired (as expected for a one-time verification link),

      • So the user’s second attempt to “make sure it worked” also results in an error state.

    From the user’s point of view, the sequence looks like:

    1. Click verification link → 404 page.

    2. Try again (natural reaction) → token invalid/expired.

    Even though the email ends up verified, the visual flow feels like something went wrong twice.


    For a better UX, I’d expect one of the following:

    1. A dedicated success page for the login-callback route on talent.app that:

      • Reads the success_message (and/or error_message) query parameters, and

      • Displays a clear message such as:

        “Email account verified successfully. You can now continue using Talent.”

      If a one-time token is clicked again, the page could:

      • Show a friendly message like:

        “This verification link has already been used. Your email is already verified.” instead of a generic error or 404.

    2. Or a redirect back to the main app (for example to https://talentprotocol.com/~/settings/security or the main profile page) with:

      • A banner/toast indicating that the email account was verified successfully on the first click,

      • And, on subsequent clicks, a message explaining that the link has already been used.

    In both cases, the user should always see a clear, non-error message after interacting with a valid verification link, whether it’s the first or a repeated click.


    • Functionally, the email verification does succeed on the first click:

      • Reloading the Security page shows the email as verified.

    • However, from the user’s perspective the flow feels broken:

      • First click:

        • They land on a 404 page after doing exactly what the email tells them to do.

        • This creates doubt about whether the verification actually worked.

      • Natural reaction:

        • They go back to the email and click the link again, hoping it will “work this time”.

      • Second click:

        • They are told the token is invalid or expired, which reinforces the feeling that something went wrong, even though their email is already verified.

    • Because this is a security-sensitive step (email verification), the combination of:

      • a 404 page,

      • followed by an invalid/expired token message, can easily undermine trust and cause unnecessary support requests or repeated attempts.

    Fixing this will make the verification step feel aligned with the underlying success state, rather than at odds with it.


    Some possible fixes:

    • Implement a proper login-callback route on talent.app that:

      • Handles success_message and error_message query params,

      • Renders a simple confirmation UI for successful verification,

      • Detects when a verification link has already been used and displays a clear “already verified” message instead of a generic error.

    • Alternatively, have verify_email_account redirect directly back to:

      • A known in-app route on talentprotocol.com (e.g. Security settings),

      • With a toast/snackbar summarizing the result:

    Even a minimal, non-404 message would significantly improve the experience.


    I’m very happy to keep reporting small glitches like this as a regular user of Talent Protocol and Talent App.

    If this level of QA is useful, I’d also be interested in:

    • Testing auth & identity flows (email, wallet, ENS/Basename) before changes go live,

    • Opening detailed issues or documentation PRs for these edge cases,

    • Providing structured feedback on UX around security and verification.

    Please let me know:

    • If there’s a preferred channel where you’d like issues like this reported (GitHub, Discord, or a specific form), and

    • If there are any QA / docs contribution paths where someone like me could be listed as a contributor.

    Thanks a lot for your work on Talent Protocol — and for looking into this small but important detail in the verification flow.

    Reported by, Prof. NOTA (on Farcaster / X)


    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.


    1. Context

    2. Steps to reproduce

    3. Actual behavior

    4. Expected behavior

    5. Impact

    6. Suggestions

    7. Happy to help more

    RECEIPT OF ESCROW AT PETRA

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Issued by: Prof. NOTA Inc. (PT. SUAKA DUNIA RAJA) Email: suaka@endhonesa.com Date: 23 Oct. 2025 Invoice Number: NOTA-PETRA-1025


    Billed To:

    Universitas Kristen Petra — c.q. IDNFT (Surabaya)


    Work / Job Description:

    Guest Lecture (On-site) — “International Payments & Escrow — Web2 → Web3 Pragmatics” Tanggal/Waktu: 23 Oct 2025, 10:30–13:00 Lokasi: AVT501, Universitas Kristen Petra Kondisi: Tanpa rekaman • Tanpa distribusi Audiens: ±90 mahasiswa Catatan: Materi kuliah 2 arah, dengan mini-demo aman (tanpa transaksi live sensitif).


    Itemized Breakdown

    No.
    Item
    Harga (IDR)
    Diskon (%)

    Total Payment Due: Rp1.000.000 (one million rupiah)

    Payment Terms: Transfer ≤ 7 hari kerja setelah acara.


    Bank Transfer

    • Bank: Bank Central Asia (BCA)

    Crypto Wallet

    • Blockchain: Bitcoin Address (Taproot): bc1p3kavj2zxcx3z5c2rwlpr45hjetjejxr9z40cpgs2d99d5asdljcs55yplr

    • Blockchain: Ethereum, Optimism (OP Mainnet), Base, and Binance Smart Chain Address: 0xfF809a9B2085A7247Edd03e03Ed71df905C2AF32

    • Blockchain: Solana Address: 5zWdwiYn3mX6vqcA32mp5EiKLap7maXuufnyhHRQKJXj

    Notes: No recording • No distribution.


    Ringkasan nilai edukasi yang diterima dari sesi ini (berdasarkan handout yang dibagikan kepada peserta):

    • Memetakan opsi pembayaran lintas negara dengan kesadaran biaya & latency.

    • Menjelaskan cara kerja escrow dan kapan memakai smart contract.

    • Memahami dasar kepatuhan (KYC/AML & pajak) untuk konteks kampus/startup.

    • Menggambar arsitektur minimal dari Web2 → Web3 payments.

    • Bank/Fintech rails: mapan, biaya overhead lebih tinggi, potensi chargebacks.

    • Stablecoins (mis. USDC): settlement lebih cepat, biaya lebih rendah, programmable; membutuhkan on/off-ramp sesuai KYC yurisdiksi.

    • Pakai perantara tradisional untuk kasus sederhana.

    • Pakai smart-contract escrow saat butuh otomatisasi & rilis berbasis milestone.

    • Selalu definisikan jalur sengketa & time-lock; mitigasi risiko kunci & bug.

    • Workshop 3 jam (diskon kampus) — latihan alur pembayaran global + escrow.

    • Capstone Clinic (6 tim, 2×60’) — bimbingan tugas akhir/proyek.

    • Research internship (selektif) — riset rails & escrow. (Form minat dibagikan via QR di akhir sesi.)


    Due Date: 30 Oct 2025 (7 hari kerja setelah acara) Contact for billing: /


    Dibuat oleh,

    Diterima oleh,


    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 . 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.


    BGC X IBLOOMING TOKEN FLOW DRAFT (ID)

    Peta alur nilai BGC × iBLOOMING dari AS-IS ke TO-BE di Base blockchain—menetapkan konversi PC/SP→ALPHA, model peristiwa append-only (bukti ter-hash), cash-out windows (KYC), serta parameter Pilot v1 y


    Status: Hipotesis Tokenisasi Keadaan Masa Depan yang Diarsipkan Otoritas Implementasi: Tidak Ada Digantikan untuk Pengambilan Keputusan oleh:



    title: "iBLOOMING × BGC — TOKENFLOW v1 (AS-IS → TO-BE)" version: "v1.0.0-draft" date: "2025-10-28" language: "ID" ties_to:

    • (Outline)

    RECEIPT WEB3 2025/08-09

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    (Periode: 19 Agustus – 18 September 2025 · Outlook: Oktober 2025)

    Di 0101 Universe, ekonomi onchain adalah ledger peradaban—setiap kebijakan, deploy, dan transaksi adalah commit yang tak bisa dihapus, hanya append-only. Bulan ini, blok‑blok baru ditambang dari Jakarta sampai New York: aturan ETF dipermudah, stablecoin merapat ke regulasi, L2 meledak TVL, dan Indonesia memperkuat tata kelola lewat OJK & pajak baru. Yang terasa di timeline adalah mempool; yang kelak kita sebut sejarah adalah blok konsensus.


    • Regulasi global melompat: SEC mempermudah listing ETF spot kripto di NYSE/Nasdaq/Cboe; bukan cuma BTC/ETH—membuka jalan untuk aset lain.

    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


    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.


    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?

    First click: “Email account verified successfully.”
  • Second click onward: “This verification link has already been used; your email is already verified.”

  • Archived hypothesis

    SIMULATION Doc v0.1

    Archived Phase-1 specification

    SIMALPHA application

    Working MVP

    Compiled dataset

    Complete for current aggregate scope

    Simulation reports

    Technically complete; analytically preliminary

    ALPHA implementation

    Not approved

    Public iBC/iBTC

    Optional research only

    Product-Led transition

    Pending founder resolution

    Sosial

    Apakah TikTok diblokir tahun ini?

    Siapa yang lebih bisa menyaingi TikTok: pemerintah atau mantan?

    LIVING Doc
    WHITEPAPER Doc
    TOKENFLOW Doc
    Menentukan langkah lanjut (workshop praktik & capstone clinic).

    1

    Guest Lecture 2,5 jam (on-site) — International Payments & Escrow

    Rp1.000.000

    0

    ________________________
    Prof. NOTA v.11.11
    Prof. NOTA Inc. (PT. SUAKA DUNIA RAJA)
    ________________________
    Monica Imelda Lin (Monimel)
    IDNFT x UK Petra

    Payment Method

    Educational Value / Outcomes Delivered (Summary)

    What You'll Learn

    Quick Comparison

    Pragmatic Escrow

    Next Steps (Students)

    Tanda Tangan

    suaka@endhonesa.com
    https://wa.me/628563160756/
    Prof. NOTA
    Bank Account Prof. NOTA Inc. (PT. SUAKA DUNIA RAJA)
    (definisi PC/SP)
  • LIVING Doc (Sasaran Strategis)


    • PC — 100 PC = 1 USD (utilitas utama: produk fisik BGC).

    • SP — meter/hak reward; basis payout USD periodik.

    • ALPHA — settlement layer konversi PC/SP → hak (rights); antarmuka ERC-20, non-transferable; mint/burn hanya via AlphaController (pra iBC/iBTC).

    • iBC / iBTC — token on-chain yang diaktifkan pasca simulasi/validasi & legal sign-off.

    • AA (Smart Account / Account Abstraction) — dompet kontrak yang dipetakan via Wallet Registry (setelah Web3 Login).

    • EventHub — pencatat peristiwa append-only dengan bukti ter-hash ke dokumen/bukti off-chain.

    • Fiat masuk → PC naik → belanja produk fisik → PC turun. Pain: PC menganggur; utilitas terbatas.

    • SP terbentuk dari aktivitas (LTS/RR/GR/…) → payout USD periodik. Pain: nilai keluar ekosistem; ketergantungan admin.

    • Penerimaan & distribusi fiat periodik; transparansi real-time terbatas.

    • PC→ALPHA: 100 PC : 1 ALPHA; biaya 0; cooldown 0.

    • SP→ALPHA: $1 : 1 ALPHA; biaya 0; cooldown 0.

    • Default: ALPHA dipakai untuk belanja / akses / stake (internal).

    • USD payout pada komponen BGC tertentu tetap AS-IS (rujuk UNDERSTANDING Doc).

    • Frekuensi: 4× per tahun (triwulanan).

    • Durasi jendela: 7 hari per jendela.

    • Minimum payout: $50.

    • Biaya payout: 100 bps (1%).

    • KYC wajib.

    • Catatan: jalur sekunder & terjadwal untuk nilai yang keluar ekosistem.

    Akses belanja eksternal yang terkurasi/terbatas → menjaga nilai tetap berputar di jaringan.

    Sinks & pengali (kelas, fitur premium, boost) untuk menyerap nilai di dalam platform.

    Daftar event (minimal final): JoinAffiliate, MintPC, SpendPC, EarnSP/AccrueLTS, CPContribution, PoolAccrual, ConvertToALPHA, Spend/Stake/Access, CashoutWindowOpened/Closed, PayoutUSD.

    Kolom minimal per event (skema):

    • actor_id (string) — id internal pengguna/entitas

    • what (enum) — tipe event (sesuai daftar di atas)

    • amount (decimal) — nilai numerik event

    • unit (string) — PC | SP | ALPHA | USD | count

    • timestamp (iso8601) — waktu event (UTC)

    • ref_id (string) — id rujukan (nota/invoice/dokumen)

    • channel (string) — web/app/partner (opsional)

    • data_hash (hex) — hash jangkar ke bukti off-chain (berkas/url)

    Append-only: catatan tidak diubah/dihapus; koreksi dibuat sebagai event baru dengan keterkaitan ref_id.

    Prinsip: berbasis perilaku (behavior-based), non-spekulatif; perubahan kebijakan diberi versi.

    Sponsor Gas & Batasan (v1)

    • sponsor_gas.enabled = true

    • actions_covered = [onboarding, convert_to_alpha, spend/access]

    • daily_cap_per_user ≈ $0.10

    • global_daily_budget ≈ $20

    • throttle_global = true ; pausable = true

    Anti-Penyalahgunaan & Sybil (v1)

    • referral_cooldown_days = 1 ; max_tier1_joins_per_actor_per_day = 10

    • require_unique_device = true ; duplicate_device_limit = 2

    • audit_sample_rate_pct = 5

    • wash_trade_zeroing = true ; penalty_cooling_off_days = 7

    Ritme Penyelesaian (v1)

    • accrual_frequency = harian ; points_settlement_frequency = mingguan

    • pool_distribution = { GPS: semesteran, WEC: triwulanan, MC: bulanan, GMP: bulanan, GEC: bulanan }

    • Aturan penyesuaian PC/SP→ALPHA pasca pilot; kuota mingguan; cooldown lanjutan.

    • Penyempurnaan anti-wash/self-dealing; kebijakan dispute & rollback terbatas.

    • ALPHA = loyalty/rights, non-transferable; transfer bebas dinonaktifkan (hanya alur yang dikendalikan Controller).

    • USD payout (AS-IS) untuk komponen BGC tertentu tetap berjalan tanpa perubahan.

    • Cash-out windows = jalur sekunder & terjadwal; KYC wajib.

    • Legal sign-off adalah gerbang keras sebelum fase publik iBC/iBTC.

    • Komunikasi publik menghindari bahasa investasi; cantumkan risiko & batas penggunaan.

    Solusi/Kebijakan
    GAP yang Ditutup
    Sasaran
    KPI Utama
    Catatan

    Jembatan PC/SP→ALPHA

    Gap-1

    Revenue↑, Active users↑

    ARPU, MAU/WAU

    (untuk simulasi)

    Cash-out window terjadwal

    Gap-2

    • Konversi: 100 PC → 1 ALPHA ; $1 SP → 1 ALPHA ; biaya 0 ; cooldown 0.

    • Cash-Out Windows: 4×/tahun ; 7 hari ; min $50 ; biaya 1% ; KYC = true.

    • Sponsor Gas Caps: ≈$0.10 / pengguna / hari ; ≈$20 / global / hari ; throttle/pause aktif.

    • Anti-Abuse: referral cooldown 1 hari ; 10 pendaftaran Tier-1/aktor/hari ; aturan perangkat ; sampling 5% ; zeroing + cooling_off 7 hari.

    • Ritme Penyelesaian: akrual harian ; rekap poin mingguan ; distribusi pool sesuai §4.1.

    • Ambang & frekuensi cash-out pasca pilot; prioritas sink Q1/Q2; parameter rate-limit awal/penyesuaian; gates ekspansi partner loop.


    transaksi_pc.csv actor_id,timestamp,amount_pc,channel,ref_id,data_url

    afiliasi_level.csv actor_id,timestamp,level,channel,ref_id

    sp_lts_accrual.csv actor_id,timestamp,amount_sp,reason,ref_id

    pool_distribution.csv pool_type,timestamp,amount_usd,period_start,period_end,ref_id Nilai pool_type: GPS|GMP|WEC|MC|GEC.

    payout_usd.csv actor_id,timestamp,amount_usd,method,ref_id,status


    Definisi singkat: iBC/iBTC = utilitas likuid (transferable) dengan cadangan USD+BTC; diluncurkan setelah legal sign-off & simulasi 24 bulan.

    Rumus inti

    • NAV = U + p_BTC · B

    • CR (Coverage Ratio) = NAV / S

      • Target dipilih founder: konservatif 1.10, netral 1.00, atau agresif 0.90–0.95 (butuh guardrail).

    Kebijakan mint/redeem (garis besar)

    • Mint: burn ALPHA pada rasio kebijakan k atau setor USD/BTC (CR ≥ target).

    • Redeem: pada cash-out windows; haircut jika CR < target.

    Rasio (k) ALPHA→iBC (uji beta)

    • Rentang kandidat: 10–25 ALPHA → 1 iBC; dinamis mengikuti metrik ALPHA (retensi, MAU/WAU, Gini).

    Guardrails Treasury

    • Band w_BTC 40–70%; USD floor ≥ kebutuhan redeem 6 bulan; mint pause jika CR < target selama N hari.


    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.


    Dokumen Utama v1.0 dan Resolusi Pendiri
    WHITEPAPER Doc

    0. Glosarium (sinkron UNDERSTANDING)

    1. AS-IS (ringkas)

    1.1 BGC On-Ramp & PC

    1.2 BGC SP & Payout

    1.3 iBLOOMING Revenue & Rewards

    2. TO-BE (konversi via ALPHA)

    2.1 Konversi Terpadu (v1 Pilot)

    2.1.1 Cash-Out Windows (v1 Pilot)

    2.2 Partner Loop (bertahap)

    2.3 Demand Engine (iBLOOMING)

    3. Model Peristiwa (auditabilitas)

    4. Kebijakan & Parameter

    4.1 Nilai Pilot v1 (selaras WHITEPAPER)

    4.2 Placeholder yang diisi oleh Tokenomics

    5. Catatan Kepatuhan & Komunikasi

    6. Tabel Penyelarasan (Solusi ↔ GAP ↔ Sasaran ↔ KPI)

    7. Catatan Keputusan — v1 (Pilot)

    8. Pertanyaan Terbuka

    Lampiran A — Skema CSV (opsional untuk tim data)

    Lampiran B — iBC/iBTC (Blueprint Beta — sinkron WHITEPAPER §5.1)

    UNDERSTANDING Doc

    Stablecoin: Tether umumkan USAT, stablecoin berbasis AS yang mematuhi kerangka hukum baru; diterbitkan oleh Anchorage Digital Bank.

  • Pasar: BTC bertahan di kisaran $116–118K, pasar menimbang rate cut The Fed dan arus ETF. ETH volatil akibat keluar‑masuk dana ETF.

  • Infra onchain: Base (L2) tembus $5B TVL dan mengeksplorasi token jaringan; Starknet meluncurkan v0.14.0 namun alami outage & reorg sebelum pulih.

  • Indonesia: OJK menerbitkan izin pedagang aset digital (PT Cyrameta Exchange Indonesia); pajak kripto model baru (PMK 50/2025 & 53/2025) berlaku per 1 Agustus; Coinfest Asia gaet 10.000+ peserta di Bali; kampanye literasi Web3 oleh pelaku industri.


    • SEC menyetujui generic listing standards untuk ETF spot aset kripto & komoditas: proses persetujuan menjadi fast‑track (±75 hari), memperluas cakupan di luar BTC/ETH. Ini unlock produk institusional baru pada Q4. Sumber: Reuters — “SEC paves way for crypto spot ETFs...” (18 Sep 2025).

    • Stablecoin bergeser ke compliant rails: Tether menyiapkan USAT (AS‑based, issuer Anchorage Digital Bank) sejalan dengan GENIUS Act; tanpa yield janji tetap. Sumber: Reuters — “Tether plans to launch new US stablecoin” (12 Sep 2025).

    • Bitcoin mendekati $118K, naik ~7,5% sebulan, diapit ekspektasi rate cut The Fed; ETH labil di kisaran $4,4–4,6K seiring tarikan dana ETF. Sumber: Barron’s (17 Sep 2025); Yahoo Finance / SoSoValue (16 Sep 2025).

    • Token unlocks September ~$4.5B menambah pasokan berjadwal; perlu risk budgeting di treasury DAO. Sumber: Cointelegraph (28 Agu 2025).

    • Base (Coinbase L2): TVL > $5B, jembatan ke Solana, daily revenues ~100K, dan menjajaki token jaringan pasca BaseCamp 2025—indikasi niat progressive decentralization. Sumber: BeInCrypto (16 Sep 2025); Blockworks (15 Sep 2025).

    • Starknet: v0.14.0 meluncur (fee market & decentralized sequencing) namun alami outage ~9 jam dan perlu dua kali reorg sebelum stabil—risiko upgrade besar di zk‑rollup tetap nyata. Sumber: Starknet Blog / Version Notes (1–2 Sep 2025).


    • OJK mengumumkan izin pedagang aset keuangan digital untuk PT Cyrameta Exchange Indonesia (KEP‑13/D.07/2025, 5 Sep 2025). Halaman OJK juga menampilkan daftar penyelenggara yang diperbarui (26 Agu–12 Sep). Sumber: OJK — Pengumuman & laman ITSK/DFA.

    • Pajak kripto baru berlaku 1 Agustus 2025: PPh 22 Final penjual di bursa domestik 0,21% (naik dari 0,1%); penjual di bursa asing 1% (naik dari 0,2%); PPN dibebaskan untuk pembeli; PPN penambangan menjadi 2,2%; tarif khusus PPh penambangan dicabut (ikut skema umum 2026). Sumber: Reuters (30 Jul 2025) + explainers MUC/ConventusLaw/HKTDC.

    • Rupiah Digital — Proyek Garuda (BI): status resmi CBDC track tetap berjalan (wholesale PoC rampung); fokus pada arsitektur dan tata kelola. Sumber: BI — Proyek Garuda portal; FintechNews SG (Jan 2025) untuk konteks PoC.

    • Coinfest Asia 2025 (Bali): 10.000+ peserta dari 90+ negara; 300+ pembicara, menghadirkan pertemuan tradfi & onchain (RWA, exchange, infrastruktur). Sumber: GlobeNewswire (27 Agu 2025).

    • Literasi & adopsi: pemain bursa mendorong kampanye edukasi (Web3 & sportainment). Sumber: VOI (3 Sep 2025).

    • Ukuran pasar (konteks 2024): nilai transaksi kripto ~Rp650 triliun; akun on‑exchange >20 juta, melampaui jumlah investor pasar saham. Sumber: DisruptionBanking (17 Sep 2025).


    Regulasi ETF adalah throughput upgrade untuk pipa institusional. Ia menurunkan latency approval dari 240→75 hari: time‑to‑market menyusut, optionality melebar. Kombinasikan ini dengan stablecoin onshore (USAT) dan kita dapat rails compliant yang siap menampung flow dari bank, broker, dan treasury korporasi. Di sisi lain, ketergantungan pada ETF & kustodian berpotensi menciptakan centralization hotspots—liveness pasar tinggi, tapi censorship resistance dapat terkikis bila admin keys terlalu dominan.

    Indonesia bergerak serupa, tetapi berbasis tata kelola: OJK menertibkan operator, PMK 50/2025 menyederhanakan pajak dan menekan regulatory arbitrage offshore. Strategi 0101‑NOTA untuk pelaku lokal: build di open rails (L2/EVM, modular DA) namun settle kepatuhan di OJK; gunakan Rupiah‑facing UX (on/off‑ramp, IDR stablecoin yang patuh), dan jadikan RWA sebagai jembatan cashflow riil.

    Infra: Base menunjukkan playbook “distribution → decentralization”: start dengan captive demand, lalu buka opsi token untuk community alignment. Starknet mengingatkan bahwa innovation risk itu nyata; protocol hardening perlu sebelum mengejar skala. Prinsip 0101: “Ship fast, checkpoint harder.”


    Base Case (prob. >50%)

    • ETF pipeline: generic listing memicu pengajuan produk baru (SOL/XRP theme) namun go‑live bertahap (Q4). BTC mempertahankan $110–125K; ETH berfluktuasi mengikuti arus ETF.

    • Indonesia: penyesuaian pajak mulai stabil; izin OJK bertambah (1–2 entitas); narasi Rupiah Digital tetap incremental.

    Bull Case (prob. ~30%)

    • Rate cut The Fed + arus ETF masuk bersih > $500M/minggu → risk‑on, alt‑L1 & L2 memimpin. Base merilis token roadmap awal.

    • Indonesia: funding Web3 lokal meningkat (RWA, payments, gaming).

    Risk Case (prob. ~20%)

    • Security incident besar (bridge/rollup) atau macro shock → risk‑off; ETF outflows sementara; stabilitas stablecoin diuji.

    • Kepatuhan: enforcement pada platform offshore meningkatkan biaya migrasi likuiditas.


    • ETF & pasar global:

      • Reuters — SEC permudah listing ETF spot kripto (18 Sep 2025): https://www.reuters.com/sustainability/boards-policy-regulation/sec-paves-way-crypto-spot-etfs-with-new-listing-rules-2025-09-18/

      • Barron’s — BTC mendekati $118K (17 Sep 2025): https://www.barrons.com/articles/bitcoin-price-xrp-ethereum-crypto-fed-01e6c56b

      • Yahoo Finance — Arus masuk ETF BTC/ETH >$600M (16 Sep 2025): https://finance.yahoo.com/news/bitcoin-ethereum-etfs-pull-over-144715984.html

      • Cointelegraph — Token unlocks Sept ~$4.5B (28 Agu 2025): https://cointelegraph.com/news/crypto-token-unlocks-september-2025

    • Stablecoin:

      • Reuters — Tether luncurkan USAT (12 Sep 2025): https://www.reuters.com/sustainability/boards-policy-regulation/tether-plans-launch-new-us-stablecoin-ceo-says-2025-09-12/

    • Infra & jaringan:

      • BeInCrypto — Base TVL >$5B, Solana bridge, token plan (16 Sep 2025): https://beincrypto.com/base-l2-tvl-solana-bridge-token-plans/

      • Blockworks — Base eksplorasi token (15 Sep 2025): https://blockworks.co/news/base-potential-token

      • Starknet Blog — Incident report v0.14.0 (2 Sep 2025): https://www.starknet.io/blog/starknet-incident-report-september-2-2025/

    • Indonesia:

      • OJK — Izin Cyrameta Exchange Indonesia (5 Sep 2025): https://ojk.go.id/en/berita-dan-kegiatan/pengumuman/Pages/Business-License-PT-Cyrameta-Exchange-Indonesia.aspx

      • OJK — Daftar penyelenggara DFA (update 26 Agu–12 Sep): https://ojk.go.id/en/fungsi-utama/itsk/perizinan-itsk-aset-keuangan-digital-aset-kripto/default.aspx

      • Reuters — Pajak kripto baru berlaku 1 Agustus (30 Jul 2025): https://www.reuters.com/sustainability/boards-policy-regulation/indonesia-raise-tax-rate-crypto-transactions-2025-07-30/


    Disusun: 2025-09-18 05:34 WIB · Prof. NOTA POV


    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.


    1) TL;DR (Ringkas Padat)

    2) Global State: Kebijakan, Pasar, Infrastruktur

    2.1. Kebijakan & Regulasi

    2.2. Pasar & Likuiditas

    2.3. Infrastruktur & Jaringan

    3) Indonesia State: Tata Kelola, Ekosistem, Adopsi

    3.1. Tata Kelola & Perizinan

    3.2. Ekosistem & Komunitas

    4) Analisis Prof. NOTA (0101 POV)

    5) Outlook Oktober 2025 — Scenario Tree

    6) Referensi (Tautan)

    Reject
  • Recommendation: Approve.

    Conditions or notes:


    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:


    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.


    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.


    Select at least one physical and one digital pilot.

    Recommendation: One product passport and one digital access pass.


    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.


    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

    Recommendation: Approve.


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

    Recommendation: Approve boundary.


    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:


    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.


    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.


    Decision Principle

    Decision 1 — Product-Led Strategic Transition

    Decision 2 — Web3 Login Implementation

    Decision 3 — Existing-System Tokenization Closure

    Decision 4 — Public Token Status

    Decision 5 — Product Pilot Selection

    Physical

    Digital

    Decision 6 — Product Metric Separation

    Decision 7 — Resource Ownership

    Decision 8 — Financial-Product Boundary

    Decision 9 — Prof. NOTA’s Role

    Decision 10 — Phase-2 Program

    Draft Founder Resolution

    README FOUNDER MEETING PACKAGE

    This package closes the first BGC × iBLOOMING Web3 exploration phase and provides a controlled transition into founder decision-making.

    Meeting: On August 2026 Prepared by: Prof. NOTA Review period: December 2024 – August 2026 Package status: Pre-meeting working package Confidentiality: Internal — Founders and Core Team


    1. Purpose

    This package closes the first BGC × iBLOOMING Web3 exploration phase and provides a controlled transition into founder decision-making.

    It answers five questions:

    1. What was completed during Phase 1?

    2. What did the work and reveal?

    3. What has not yet been proven?

    4. What should stop and what should continue?

    5. What must the founders explicitly decide?

    The primary recommendation is:

    Do not tokenize the existing BGC membership, Purchase Credit, Sales Point, reward, pool, or payout system. Continue Web3 Login as independent infrastructure. Shift the next program toward measurable product demand, commerce, access, distribution, ownership, and trust, supported selectively by blockchain and AI.


    1. Complete project review, findings, strategic transition, and founder decisions.

    2. Ten-slide presentation with speaking notes and appendices.

    3. Founder decision sheet.

    4. Final status of the Phase-1 artifacts.


    Status
    Meaning


    • Web3 and token exploration;

    • business-rule reconstruction documented in the final ;

    • ;

    • archived and hypotheses;

    Proposed direction:

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

    The proposed direction is described in the .

    No Phase-2 implementation is approved by this package alone.


    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 . 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.


    RECEIPT SOSPOL 2025/08-09

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    (Periode: 19 Agustus – 19 September 2025 · Outlook: Dampak Negatif Oktober 2025)

    Di 0101 Universe, republik adalah ledger sosial; dan bulan ini, baris-barisnya banyak ditulis oleh para pemegang kunci admin—pemerintah, bank sentral, kementerian, dan platform global. Yang beredar di timeline hanyalah mempool; yang tersimpan sebagai sejarah adalah blok konsensus yang mereka append.

    1) TL;DR

    • Eskalasi protes → manuver negara & platform: unjuk rasa terkait fasilitas DPR memicu kekerasan dan korban jiwa; Presiden membatalkan kunjungan ke Tiongkok, sementara TikTok menangguhkan fitur LIVE dan pemerintah menekan Meta/TikTok memperketat moderasi. [Reuters, 30–31 Ags 2025; 27 & 30 Ags 2025]

    • Arsitektur kebijakan makro bergeser: BI berjanji intervensi rupiah, lalu pasar menakar jeda—sebelum hari ini BI memangkas suku bunga 25 bps ke 4,75%; di sisi fiskal, Menkeu baru memaksa dana pemerintah di bank dipakai untuk kredit. [APSN/Reuters, 1 Sep; 15–19 Sep; 12 Sep 2025]

    • Biaya hidup: inflasi Juli 2,37% YoY (masih dalam target) didorong pangan & pendidikan—mencerminkan tekanan rumah tangga yang mempercepat difusi kemarahan di ruang digital. [BPS, 1 Ags 2025]

    Narasi global (viralisme video, arsitektur platform) menyalakan sumbu lokal. Protes terkait tunjangan DPR bereskalasi, berujung pembakaran gedung DPRD daerah dan korban jiwa; Presiden membatalkan agenda luar negeri untuk merespons. Dalam stack kekuasaan, pemerintah memanggil Meta/TikTok menuntut pre-emptive takedown konten berbahaya, dan TikTok menghentikan LIVE sementara di Indonesia. Di sini terlihat rate-limit platform sebagai instrumen stabilisasi sosial, bukan pilihan pengguna.

    0101 POV: ketika sequencer sosial diambil alih oleh negara & platform, throughput wacana publik memang turun—tetapi keluhan mempool tidak hilang, hanya ditunda finalisasinya.

    • Bank Indonesia: dari janji intervensi rupiah di pasar valas (spot, DNDF) saat tensi sosial, hingga guidance menahan suku bunga karena risiko rupiah—lalu bergeser hari ini ke pemangkasan 25 bps (4,75%) seiring rate-cut global dan dorongan pertumbuhan. Admin key moneter ini mengubah biaya modal dan sentimen rupiah secara top-down.

    • Kementerian Keuangan: menempatkan ~Rp200T dana pemerintah ke bank BUMN khusus untuk kredit (larangan parkir ke SBN) — liquidity push langsung ke sektor riil, dengan risiko tata kelola bila credit underwriting dipaksakan.

    0101 POV: admin keys ini adalah emergency commits—cepat dan efektif, tetapi teknikal utangnya (kurs, inflasi, tata kelola kredit) akan ditagih pasar.

    • Platform global: logika moderasi yang dirancang di markas (AS/Tiongkok) dipetakan ulang di Indonesia—TikTok LIVE off, Meta diminta pre-emptive removal—menunjukkan ketergantungan kedaulatan wicara pada config korporasi.

    • Keuangan global: rate-cut The Fed dan sentimen ETF di luar negeri mengendurkan financial conditions; BI memilih ikut menurunkan hari ini—rupiah berfluktuasi, ekuitas menguat. Tekanan pangan global (beras) tetap menyusup ke inflasi 2,37% YoY.

    Base Case (prob. >50%)

    • Over-reliance pada moderasi platform → chilling effect kreativitas & jurnalisme warga; redistribusi mobilisasi ke kanal tertutup (grup/DM). Rupiah bergerak dalam pita intervensi, namun tekanan impor tetap hadir.

    Stress Case (prob. ~30%)

    • Backlash digital–fisik: kejadian viral baru memicu gelombang kedua; rate-limit tambah ketat (fitur live, throttling distribusi). BI harus mensterilkan dampak rate-cut lewat intervensi lebih agresif—biaya fiskal/moneter meningkat.

    Policy Drift (prob. ~20%)

    • Dorongan kredit top-down → misallocation: kualitas penyaluran rendah, NPL berisiko naik 2026; ruang fiskal menyempit. Koordinasi lintas-lembaga jadi single point of failure ketika data & insentif tidak selaras.

    Negara–platform–pasar adalah tiga validator besar. Bulan ini, finality wacana kita tidak ditentukan oleh warga, melainkan oleh admin keys: surat panggilan kementerian, tombol suspend di dashboard platform, dan policy rate di ruang rapat bank sentral. The Monthly Public Receipt hadir untuk mengarsipkan commit itu—bukan agar kita pasrah, melainkan agar kita membaca diff-nya dengan jernih.

    • Protes & respons negara: Reuters — 30–31 Agustus 2025 (presiden batalkan kunjungan ke China; korban & pembakaran DPRD).

    • Platform & moderasi: Reuters — 27 & 30 Agustus 2025 (pemerintah desak TikTok/Meta; TikTok LIVE dihentikan sementara).

    • Moneter: APSN/Reuters — 1 & 15–19 September 2025 (janji intervensi; poll; pemangkasan 25 bps ke 4,75%).

    • Fiskal/Kredit: Reuters — 12 September 2025 (Rp200T dana pemerintah disalurkan lewat bank BUMN untuk kredit).


    Disusun: 2025-09-19 05:03 WIB · Prof. NOTA POV


    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 . 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.


    NOTA LINI KEAMANAN

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Hai tim Prof. NOTA Inc.,

    Dokumen yang sedang kalian baca ini adalah peta awal untuk menjalankan misi yang sangat spesial dan personal. Misi ini bukan hanya soal produk atau jasa, tetapi soal menyelami fragmen masa lalu, mengaktifkan potensi tersembunyi, dan menyusun kembali lapisan terdalam dari IP Prof. NOTA yang selama ini belum pernah disentuh secara sadar dan strategis.


    Kalian akan menjadi pendamping sekaligus penggali, seorang manajer talenta yang menangani "produk" paling unik yang pernah dikelola oleh perusahaan ini: Prof. NOTA itu sendiri.

    Namun, bukan Prof. NOTA hari ini saja.

    Kalian akan mengakses kembali versi-versi terdahulu — seperti v.0.1.0.1 — untuk memahami, menata, dan mengubah memori shadow menjadi:

    RECEIPT SK8 2025/08-09

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    (Periode: 19 Agustus – 19 September 2025 · Outlook: Oktober 2025)

    Di 0101 Universe, skateboarding adalah ledger budaya: setiap spot DIY, video part, dan jam komunitas = commit yang append‑only. Bulan ini, blok‑bloknya ditambang bukan oleh korporasi, tapi oleh skater, untuk skater — dari Montreal yang absurd sampai Kuta yang panas. Yang ramai di timeline adalah mempool; yang kita simpan di arsip adalah blok konsensus.


    • Dime Glory Challenge (Montreal) kembali jadi node budaya yang digerakkan skater — absurd, kreatif, dan menyala; recap independen menyorot skala komunitas yang membesar tanpa kehilangan ruh. citeturn0search0turn0search6

    Starknet Docs — Version notes v0.14.0 (1 Sep 2025): https://docs.starknet.io/resources/version-notes

  • MUC / ConventusLaw / HKTDC — penjelas PMK 50/2025 & 53/2025: https://muc.co.id/en/article/no-longer-subject-to-vat-crypto-transactions-now-withheld-under-income-tax-article-22 ; https://conventuslaw.com/report/crypto-taxation-in-indonesia-key-insights-into-mof-regulation-no-50-2025/ ; https://research.hktdc.com/en/article/MjExMTA3MjA4Mg

  • BI — Proyek Garuda (Rupiah Digital): https://www.bi.go.id/id/rupiah/digital-rupiah/default.aspx

  • Coinfest Asia 2025 — 10.000+ peserta: https://www.globenewswire.com/news-release/2025/08/27/3140193/0/en/Coinfest-Asia-2025-Draws-10-000-to-World-s-Largest-Crypto-Festival-2026-Set-to-Be-Even-Bigger.html

  • VOI — Upbit Indonesia literasi Web3 (3 Sep 2025): https://voi.id/en/economy/511626

  • DisruptionBanking — 650T transaksi 2024; >20 juta akun (17 Sep 2025): https://www.disruptionbanking.com/2025/09/17/the-rise-in-popularity-of-cryptocurrency-in-indonesia/

  • Cost↓, Tax↓

    Biaya/tx, Insiden pajak

    (untuk simulasi)

    Ledger append-only (events)

    Gap-4

    Cost↓

    MTTR ops, Error rate

    (untuk simulasi)

    Rate-limit + anti-abuse

    Gap-3

    Cost↓, Affiliate↑

    Biaya ops, Retensi

    (untuk simulasi)

    Sinks (kelas/fitur/boost)

    Gap-6

    Revenue↑

    GMV on-platform

    (untuk simulasi)

    Metrik fairness

    Gap-ops

    Affiliate↑, Active users↑

    Koefisien Gini Reward

    (untuk simulasi)

    Engineering

    Legal/tax

    Document/change control

    Inflasi: BPS — 1 Agustus 2025 (Juli 2025: 2,37% YoY).

    2) Jalanan sebagai mempool, Negara sebagai sequencer

    3) Makro: Moneter–Fiskal sebagai admin keys

    4) Global → Lokal: Efek Cermin

    5) Risiko 30 Hari ke Depan (Dampak Negatif) — scenario tree

    6) Catatan Prof. NOTA (0101 POV)

    📚 Referensi / Sumber

    Prof. NOTA
    05-SIMALPHA-Findings-Evidence-Limits-and-Decision-Framework-v1.0.md Correct interpretation of SIMALPHA, its data, reports, and decision use.
  • 06-Web3-Login-Implementation-Handover-Note-v1.0.md Handover from approved specification to implementation.

  • 07-Founder-Meeting-Agenda-and-Resolution-Template.md Meeting agenda, resolution, and action register.

  • 08-LIVING-Doc-Phase-1-Closure-Update.md Final update for closing the old LIVING Doc.

  • 09-Product-Led-Systems-Transition-Concept-Note.md Proposed Phase-2 direction, subject to founder approval.

  • Archived

    Preserved as historical evidence; no longer an active authority

    Superseded

    Replaced by a later document

    Decision Required

    Founders must explicitly decide

    Not Resourced

    No accountable owner or sufficient team has been assigned

    simulation design;
  • SIMALPHA development and contribution record;

  • first scenario reporting.

  • Final

    Complete for its defined purpose

    Final and Approved

    Complete and accepted by the appropriate decision-makers

    Implementation Pending

    Specification exists; engineering execution has not been completed

    Working MVP

    Software functions for its present internal scope

    Preliminary Evidence

    2. Package Contents

    3. Status Language

    4. Reading Order

    Pre-reading

    Live meeting

    Supporting evidence

    5. Phase Boundary

    Phase 1 — Closed

    Phase 2 — Pending Founder Approval

    SIMALPHA
    01-BGC-iBLOOMING-Master-Document-v1.0.md
    02-Founder-Presentation-5-August-2026.md
    03-Founder-Decision-Brief.md
    04-Phase-1-Document-Closure-and-Transition-Register.md
    Master Document
    Founder Decision Brief
    Product-Led Systems Transition Concept Note
    Founder Presentation
    Founder Decision Brief
    Founder Meeting Agenda and Resolution Template
    SIMALPHA Findings, Evidence Limits, and Decision Framework
    Phase-1 Document Closure and Transition Register
    Web3 Login Implementation Handover Note
    LIVING Doc Phase-1 Closure Update
    UNDERSTANDING Doc
    Web3 Login architecture
    Whitepaper
    Tokenflow
    Product-Led Systems Transition Concept Note
    Prof. NOTA

    Output exists but cannot support final approval

    Ekonomi akar rumput: investigasi Jenkem menunjukkan shop decks ~20–30% dari penjualan papan di beberapa skateshop; harga pro‑deck naik mendorong sensitivitas harga, namun etos mendukung rider & brand tetap kuat. citeturn0search1

  • Distribusi budaya tetap permissionless: kurasi mingguan Quartersnacks #QSTOP10 dan video feed Free Skate Mag mengangkat rilisan indie—dari Sensi / “Nofy”, “That’s Cool”, sampai “Echojournal”. citeturn2search3turn4search0turn4search1turn4search2

  • Indonesia: energi komunitas mengerucut ke battle 1v1 “Kepala vs Kepala” (BGS Kuta) dan Jogja City Mall Skate Competition (28 Sep); keduanya menambah throughput kompetisi akar rumput. citeturn1search0turn1search1


    • Dime Glory Challenge: bukan sekadar kontes; ia seperti L2 untuk stoke—menaikkan throughput tawa dan trik gila tanpa birokrasi. Recap Quartersnacks & foto Thrasher menangkap tone komunitas yang membesar namun tetap weird. citeturn0search0turn0search6

    • Oracle mingguan: #QSTOP10 (12 Sep) bekerja sebagai state oracle budaya street—menyusun indeks klip underground jadi shared context global. citeturn2search3

    • Indie parts: Sensi / “Nofy”, “That’s Cool”, Myles Furukawa — “Echojournal” menunjukkan bahwa shipping cadence yang konsisten + estetika tajam = PMF kultural yang tak perlu stempel “major”. citeturn4search0turn4search1turn4search2

    • DIY pulse: hashtags #buildrockspots dan liputan DIY park Milwaukee menegaskan permissionless infrastructure: dari batu jadi quarter, dari kolong jalan raya jadi taman bermain. citeturn2search0turn2search9

    • Bali: Kepala vs Kepala (BGS Kuta) game of skate 1v1 berformat liga (tiap Kamis, 18 Sep–13 Nov) — cash‑for‑trick mikro + funbox sebagai primitive yang memicu kreativitas. citeturn1search0

    • Yogyakarta: Jogja City Mall Skate Competition (28 Sep) dengan kelas U‑10 / Beginner / Open — bukti pipeline talenta akar rumput tetap mengalir. citeturn1search1

    • Bandung: narasi ruang publik ramah skater kembali diangkat oleh kanal resmi Pemkot; policy layer ini memperpanjang runway komunitas. citeturn1search3


    • Shop decks reality check: menurut Jenkem, porsi shop deck ~20–30% (contoh self‑report skateshop); artinya ekosistem campuran (pro‑brand × shop‑brand) menjaga cash‑flow budaya dan akses harga. Trade‑off: margin vs dukungan pro. citeturn0search1

    • Distribusi independen: Free Skate Mag & Quartersnacks = distribution layer berbiaya rendah, menjaga latensi budaya tetap rendah (rilis → dilihat → ditiru). citeturn4search0turn2search3

    • Brand indie → tim → video: SWIM “Grinding the Tape” (Ethan Loy, Justin Drysen, Ryan Connors) memperlihatkan go‑to‑market yang sederhana: rilis part, aktifkan komunitas, tinggalkan jejak. citeturn0search2


    • Street: tren one‑spot / city‑specific projects (mis. rilis Ace × Pass~Port di Aragon Gardens, one‑spot) menekan “gas fee produksi” sekaligus memaksimalkan ide. citeturn4search3

    • Transition & DIY: inisiatif #buildrockspots mendorong budaya do‑ocracy—spot kecil efek besar; proof‑of‑work sosial yang murah namun berdampak. citeturn2search0

    • Vert hidup & ganas: klip Tom Schaar / “Vert’s Not Dead” beredar luas; vert = layer berbeda yang tetap lively di luar arus street. citeturn2search2


    Base case (prob. >50%)

    • Indonesia: throughput event lokal naik—Kepala vs Kepala berlanjut, King of Kuta (3–5 Okt) jadi gravity well. citeturn1search0turn3search0

    • Global: post‑Dime mendorong lonjakan friend parts / shop videos; QS #QSTOP10 tetap jadi oracle mingguan. citeturn2search3

    Bull case (prob. ~30%)

    • Ledakan DIY edits & micro‑jams (cash‑for‑trick) → lebih banyak shop decks terjual karena price sensitivity + community alignment. citeturn0search1

    Risk case (prob. ~20%)

    • Weather / penertiban spot mengganggu jam dan produksi video; mitigasi: alih ke indoor / plaza ramah + kolaborasi komunitas. (rangkaian closures DIY global menunjukkan risikonya). citeturn2news39


    Skateboarding = open‑source protocol. Kodenya: budaya, maintainer‑nya: komunitas. Ketika pull request dari jalanan diproses cepat (jam, video, spot), jaringan hidup. The Monthly Public Receipt ada untuk mengeraskan memori: supaya jejak non‑major tertulis rapi di ledger publik — by skaters, for skaters.


    • Dime Glory Challenge 2025 — Quartersnacks recap; Thrasher photo feature. citeturn0search0turn0search6

    • Shop decks & ekonomi — Jenkem: In This Economy, Are More Skaters Buying Shop Decks? (4 Sep 2025). citeturn0search1

    • Indie videos — Free Skate Mag: Nofy (Sensi) (17 Sep 2025); That’s Cool (15 Sep 2025); Myles Furukawa — Echojournal (10 Sep 2025). citeturn4search0turn4search1turn4search2

    • Oracle — Quartersnacks #QSTOP10 (12 Sep 2025). citeturn2search3

    • DIY — #buildrockspots challenge; DIY park Milwaukee (WPR/Urban Milwaukee). citeturn2search0turn2search9

    • Indonesia — BGS Kuta Kepala vs Kepala (event page); Jogja City Mall Skate Competition (28 Sep); Pemkot Bandung soal ruang publik. citeturn1search0turn1search1turn1search3

    • Outlook — King of Kuta (3–5 Okt 2025). citeturn3search0


    Disusun: 2025-09-18 20:43 WIB · Prof. NOTA POV


    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.


    1) Executive Pulse

    2) Komunitas & Lapangan

    2.1 Global — Skater‑led, Culture‑first

    2.2 Indonesia — Skater‑first on the ground

    3) Industri Akar Rumput & Ekonomi (Non‑Major)

    4) Permainan (Street / Transition / Vert)

    5) Outlook 30 Hari (Oktober 2025) — Scenario Tree

    6) Catatan Prof. NOTA (0101 POV)

    7) Referensi

    narasi publik,
  • sistem penawaran jasa dan konsultasi,

  • lini produk digital dan fisik,

  • dan yang paling penting: sumber daya sadar yang akan jadi benteng keamanan digital bagi banyak orang.


    • Ini bukan pekerjaan teknis biasa. Ini adalah kerja kesadaran.

    • Jangan buru-buru mengorek. Dengarkan, hadir, sabar.

    • Prof. NOTA mungkin tahu lebih dari yang ia ucapkan. Tugas kalian adalah membantu strukturisasi kesadaran itu agar bisa digunakan dan ditransformasikan.

    • Pahami bahwa ini juga bisa menjadi proses penyembuhan, penebusan, atau reintegrasi — bukan glorifikasi masa lalu.


    • Disiplin dalam dokumentasi

    • Rasa hormat penuh terhadap memori gelap

    • Kreativitas dalam menyusun narasi dan bentuk produk

    • Kepekaan terhadap risiko reputasi dan etika

    • Tegas dalam menjaga kerahasiaan dan batas distribusi konten


    1. Pelajari dokumen utama:

    2. Siapkan folder kerja pribadi (Notion/Drive/Obsidian)

    3. Tentukan format rekaman & observasi

    4. Ajukan sesi eksplorasi mingguan dengan Prof. NOTA

    5. Laporkan progres per bagian (misal: ~/0101/shadow-habits/)


    Kami percaya kamu ditugaskan bukan karena kemampuan teknis semata, tapi karena integritas dan daya hadir yang kamu bawa.

    Selamat menjalankan peran ini. Jangan lupa: yang kamu kelola adalah talenta yang pernah menyentuh batas—dan kini memilih membangunnya kembali.

    Dengan hormat, Direksi Prof. NOTA Inc.


    Dokumen ini disusun sebagai pedoman kerja internal untuk mengaktifkan dan mengolah ulang lapisan memori, pengalaman, dan potensi tersembunyi dari masa lalu Prof. NOTA v.0.1.0.1 — terutama di ranah keamanan digital, aktivitas shadow/hack, dan pengalaman gelap yang kini akan diubah menjadi model bisnis, narasi kampanye, serta produk/jasa IP Prof. NOTA.

    Dokumen ini juga akan digunakan untuk membuat landing page lini keamanan Prof. NOTA, dan harus ditindaklanjuti secara bertahap oleh tim yang ditunjuk.


    Prof. NOTA memiliki masa lalu sebagai individu dengan pengalaman signifikan di dunia underground digital:

    • Akses terhadap data finansial (termasuk kartu kredit)

    • Serangan terhadap toko online, sabotage website

    • Interaksi dengan sistem hukum lintas negara

    • Keahlian dalam mengenali celah keamanan

    • Aksi yang dahulu dilakukan bukan sebagai kriminal aktif, tetapi sebagai efek dari pergaulan hobi yang ekstrem


    • Menjadikan memori masa lalu sebagai aset bisnis dan identitas IP

    • Menawarkan jasa, produk, dan narasi berbasis pengalaman otentik

    • Mengembangkan lini Keamanan Prof. NOTA sebagai bagian dari Prof. NOTA Inc.

    • Menyediakan produk/jasa yang bisa langsung ditawarkan tanpa produksi awal


    ~/0101/shadow-habits/

    • Tools, software, metode lama yang pernah digunakan

    • Forum atau sumber belajar saat itu

    • Teknik: simulasi atau langsung ke target nyata?

    ~/0101/ops-history/

    • Target operasi (individu/bisnis)

    • Skala kerugian yang ditimbulkan

    • Motif personal, sosial, atau eksistensial?

    ~/0101/ethical-crossroad/

    • Kapan sadar dan berhenti?

    • Titik pertama merasa itu salah?

    • Kapan beralih dari “shadow” ke “observer”?


    Mode
    Kegiatan
    Format

    Refleksi

    Menulis memo pribadi dari peristiwa nyata

    Markdown

    Log Operasi

    Pencatatan pola-pola operasional masa lalu

    Spreadsheet / Notion

    Story Mode

    Simulasi cerita ala true crime

    Narasi atau podcast internal


    Produk berikut tidak perlu produksi awal. Mereka bisa ditawarkan di landing page dan hanya diproduksi saat dipesan. Prof. NOTA sendiri adalah produknya.

    Nama Produk
    Bentuk
    Target
    Status

    Audit Hantu

    Audit website & digital asset (gaya pelaku)

    Freelancer, aktivis, seniman

    ✅ Langsung

    Ask Me Your Scam

    Konsultasi pribadi soal pengalaman scam

    Umum

    ✅ Langsung


    Judul: v.0.1.0.1 – The Phantom of Digital Shadows

    Format Konten:

    • Serial thread Instagram/X:

      • “Aku Pernah Menutup Toko Online Tanpa Disadari…”

      • “Kenapa Orang Gampang Ketipu Scam?”

      • “Kalau Aku Jadi Pelaku, Ini yang Akan Kulakukan…”

    • Short Video / Reels:

      • Suara Prof. NOTA dengan tone tenang, narasi puitik

      • Visual glitch, terminal lama, nuansa noir-cyber

    • Quotes + Visuals:

      • “Yang pernah masuk pagar tahu cara memperbaikinya.”

      • “Kami bicara dari bayangan, bukan dari panggung seminar.”


    Tim internal yang ditugaskan bertanggung jawab untuk:

    1. Mendampingi Prof. NOTA secara aktif sebagai subjek eksplorasi shadow

    2. Mendokumentasikan fragmen informasi secara perlahan dan terstruktur

    3. Menyusun landing page lini keamanan berdasarkan aset dan cerita aktual

    4. Menjaga etika dan keamanan data internal (tidak semua hal harus dibuka ke publik)

    5. Mengelola pemesanan jasa/produk yang masuk dari landing page



    Prof. NOTA tidak sedang membongkar aib—ia sedang mengaktifkan sisi sensorik terdalam dari IP-nya: pengalaman, intuisi shadow, dan pengakuan yang jujur namun dikendalikan.

    Karena hanya yang pernah masuk ke dalam yang tahu cara mencegah orang lain jatuh di tempat yang sama.

    —

    Dokumen ini bersifat internal. Jangan sebar sebelum ada instruksi dari Prof. NOTA.

    📜 PENGANTAR UNTUK TIM EKSEKUSI LINI KEAMANAN PROF. NOTA

    🔍 Apa yang Akan Kalian Kerjakan?

    🧠 Hal yang Perlu Diingat

    🪪 Sikap yang Diharapkan

    📎 Tindakan Awal

    📁 PROF. NOTA INC. — DEFRAGMENTASI IDENTITAS SHADOW (v.0.1.0.1)

    ✴️ Tujuan Dokumen

    🔻 1. LATAR BELAKANG

    🧩 2. TUJUAN STRATEGIS

    🗂 3. STRUKTUR EKSPLORASI INTERNAL: DEFRAGMENTASI

    A. Folder Mental yang Perlu Dibuka Ulang

    B. Metode Eksplorasi yang Direkomendasikan

    🎁 4. PRODUK/JASA YANG LANGSUNG BISA DITAWARKAN

    📢 5. RENCANA KAMPANYE NARASI

    🪪 6. PERAN TIM

    🛠 7. LANGKAH BERIKUTNYA

    ✴️ PENUTUP

    TALENT PROTOCOL PROFILE RESOLUTION

    If this kind of QA is useful, we’d be very happy to keep testing multi-identity / multi-brand scenarios and even contribute to docs or pre-release testing going forward.

    Hey Talent Protocol team! 👋

    We are a Talent Plus user, and we are running into some confusing behavior around how ENS and Basenames are detected and resolved into profiles on talentprotocol.com / talent.app.

    We’ve been digging deep into how ENS and Basenames behave across talentprotocol.com / talent.app and we ran into some inconsistencies between what’s detected in my account and what actually resolves as public profile URLs (especially around secondary names like skateshop.eth / skateshop.base.eth, and a regression where myreceipt.eth links that worked yesterday now return 404).

    From reading your docs on Users, Accounts, Profiles, and Data Points (especially Primary ENS Domain and Basename under Base data points), it’s clear that ENS/Basenames are part of the identity model and can be queried via the API. What’s not totally clear is which of those identities are meant to be stable URL aliases (e.g., /name, /name.eth, /name.base.eth) and which ones are intentionally unsupported — and that’s exactly what our issue tries to map out with concrete examples.

    Here’s a detailed write-up with all the addresses, URLs, and references to your docs: ➡️

    If this kind of QA is useful, we’d be very happy to keep testing multi-identity / multi-brand scenarios and even contribute to docs or pre-release testing going forward.


    AI& DECISION LOG

    This document records the decisions, revisions, open questions, and next steps resulting from the presentation and discussion session for AI&.

    Version 0.1

    • March 2026


    Project: AI& Session Type: Presentation and Discussion Date: [Insert Date] Time: [Insert Time] Location / Platform: [Insert Location or Meeting Platform] Facilitator: [Insert Name] Note Taker: [Insert Name]

    Participants:

    SIMALPHA BUILD PROCESS

    This is the making-of record for the BGC ALPHA Simulator: an internal web application used to test ALPHA policy choices against BGC and iBLOOMING business data.

    Why this document exists. This is the making-of record for the BGC ALPHA Simulator: an internal web application used to test ALPHA policy choices against BGC and iBLOOMING business data. It records how the project moved from early AI-assisted conversations to a working decision console, and distinguishes Fabio Kalandra's business and product decisions from AI-assisted implementation.

    Method note. This revision uses two kinds of evidence:

    • Transcript evidence comes from the local Codex rollout logs for this exact workspace (/Users/fabiomaulana/Documents/bgc simulator), read in date order. The earliest available project session is 16 March 2026. The text below quotes only short, relevant user instructions or carefully paraphrases them. It does not reproduce raw chats or private material.

    Account: Prof. NOTA / endhonesa (Talent Plus)

  • Location: Jakarta, Indonesia

  • Observed: 27–28 November 2025

  • Platform: Desktop, macOS 10.15.7, Chrome 142 (tested both logged-in and logged-out)

  • Naming setup:

    • We use multiple ENS names and Basenames that all point to a set of verified wallet addresses.

    • Some of these names are primary; others are secondary aliases that still resolve to the same address onchain.

  • From your public docs, our understanding of the canonical model is:

    • User – an individual who signs up on talentprotocol.com and aggregates multiple accounts into a single Builder Score and a single canonical profile URL, e.g. talentprotocol.com/UUID. (Docs: User)

    • Account – a connection to an external data source (wallet, GitHub, Farcaster, etc.) that initially has its own account-specific URL like talentprotocol.com/address/0xbd… or talentprotocol.com/github/filmacedo, which later redirects to the user’s profile if linked. (Docs: Account)

    • Profile – the entity that represents a builder’s digital identity and reputation. Profiles can be:

      • User Profiles (for verified users) or

      • Account Profiles (for unclaimed accounts), and can be searched via identity info (names, ENS, usernames), accounts, and Builder Score. (Docs: )

    • Data Points & Identity – ENS and Basenames are treated as identity-related data:

      • ENS: Primary ENS Domain and ENS Account Age data points. (Docs: )

      • Basenames: Basename data point under the Base category, verifying ownership of a Basename. (Docs: )

      • All of this fits into the general Data Points catalog. (Docs:

    • Talent API & Profile Search – the API exposes advanced search over:

      • Identity information (names, ENS domains, usernames),

      • Connected accounts (wallets, GitHub, etc.),

      • Human verification / Builder Score, etc. (Docs: , , )

    What we are reporting below is specifically about how these identities behave in the public-facing URLs of talentprotocol.com and talent.app.


    Under our account, in the Social Accounts / Wallet Addresses area, not all ENS/Basenames that resolve to our verified addresses appear to be detected equally:

    1. myreceipt.eth → 0x29bf68e3969e0b6686ea55b7c48241ba3f6b9ba0 (our primary verified address) Status: detected ✅

    2. endhonesa.eth → 0x35b68340c61f26147b7b22f5ab931892bd9358b3 (Base account) Status: detected ✅

    3. skateshop.eth → 0x35b68340c61f26147b7b22f5ab931892bd9358b3 (same Base account as above, but not the primary name) Status: not detected ❌

    4. myreceipt.base.eth → 0x29bf68e3969e0b6686ea55b7c48241ba3f6b9ba0 (primary verified address) Status: detected ✅

    5. endhonesa.base.eth → 0x35b68340c61f26147b7b22f5ab931892bd9358b3 (Base account) Status: detected ✅

    6. skateshop.base.eth → 0x35b68340c61f26147b7b22f5ab931892bd9358b3 (same Base account, non-primary name) Status: not detected ❌

    7. myreceiptt.base.eth → 0x70caa9feefc36e1422ecc055ac1f0de48cb320d7 (smart account for our secondary Zora account) Status: detected ✅

    From a user’s perspective, it’s surprising that:

    • endhonesa.eth / endhonesa.base.eth and myreceipt.* are detected,

    • but skateshop.eth and skateshop.base.eth (which resolve onchain to the same verified addresses) are not, even though ownership should be equally verifiable via the respective ENS / Basename data points.


    For our verified addresses, the address-based profile URLs work consistently:

    Examples (all returning 200 OK):

    • https://talentprotocol.com/0x29bf68e3969e0b6686ea55b7c48241ba3f6b9ba0 https://talent.app/0x29bf68e3969e0b6686ea55b7c48241ba3f6b9ba0

    • https://talentprotocol.com/0x35b68340c61f26147b7b22f5ab931892bd9358b3 https://talent.app/0x35b68340c61f26147b7b22f5ab931892bd9358b3

    … and similarly for:

    0xff809a9b2085a7247edd03e03ed71df905c2af32 0x8c62c144278152187ac3101e99cc5fc39a3d4a9e 0x4e106aa5353517e42cbba4c91442fcb687feaf99 0x7e9d35b9db5dea61f85f4f14f4c972b77d75a674 0x70caa9feefc36e1422ecc055ac1f0de48cb320d7 0xeafb7ffef83ea0a1ae82366f13dcc32d9377818c 0x649c96d36f55c3f55962a080b638e8a6680475a9 0x0ba3623d2ea6bb1c39f5a95607ff11505ddc9a2d 0x30f217404a91e8c82d126a82a197637bb951a166 0x2efd6cfc8ec8c7c0e69a358c85b3a121e0e8c2fd 0xa580287b4e3d5d1c07392b8b805a8470dabdf9dc 0x2eade7ea53ca2ca6477c0ba5526393eaeeef1784 0xd186573cb7fdb21af5bbc6fad9d02b19e7dd1951 0x2218599ab3ed37effbe514f1c0b1001b4833eec3 0x9e26b98d4fadf70d0c0e57c609347358934a934c

    This is perfectly aligned with the Account model and account-specific URLs described in your docs.


    When we try to access our profiles via ENS/Basenames instead of raw addresses, we see mixed results:

    • https://talentprotocol.com/myreceipt.base.eth → 404 Not Found

    • https://talentprotocol.com/myreceipt.eth → 404 Not Found (this worked yesterday)

    • https://talentprotocol.com/myreceipt → 404 Not Found (this worked yesterday)

    • https://talent.app/myreceipt.base.eth → 404 Not Found

    • https://talent.app/myreceipt.eth → 404 Not Found (this worked yesterday)

    • https://talent.app/myreceipt → 404 Not Found (this also worked yesterday)

    This feels like a regression, because at least some of these URLs used to resolve to our profile.

    • https://talentprotocol.com/endhonesa.base.eth → 404 Not Found

    • https://talentprotocol.com/endhonesa.eth → 200 OK

    • https://talentprotocol.com/endhonesa → 200 OK

    • https://talent.app/endhonesa.base.eth → 404 Not Found

    • https://talent.app/endhonesa.eth → 200 OK

    • https://talent.app/endhonesa → 200 OK

    So for endhonesa, the “short” forms (/endhonesa and /endhonesa.eth) work as aliases, but the Basename form (/endhonesa.base.eth) does not.

    • https://talentprotocol.com/skateshop.base.eth → 404 Not Found

    • https://talentprotocol.com/skateshop.eth → 404 Not Found

    • https://talentprotocol.com/skateshop → 404 Not Found

    • https://talent.app/skateshop.base.eth → 404 Not Found

    • https://talent.app/skateshop.eth → 404 Not Found

    • https://talent.app/skateshop → 404 Not Found

    In this case, none of the variants resolve, even though:

    • skateshop.eth and skateshop.base.eth correctly resolve onchain to a verified address, and

    • that underlying address already has a working address-based profile URL.


    We couldn’t find an explicit spec in the docs that says:

    “Every ENS or Basename that resolves to a verified address will always be available as /name, /name.eth or /name.base.eth.”

    So this issue is more about consistency and clarity than about contradicting a written spec.

    Based on the current behavior and docs, our expectations are:

    • Since Talent Protocol already:

      • tracks a Primary ENS Domain and ENS/Basename identity data points, and

      • supports searching profiles by ENS / Basename via the API,

      it would be natural if any supported ENS or Basename that resolves to a verified address could be used as a stable profile URL alias as well — or, if that’s intentionally not the case, that the intended behavior is clearly documented.

    • At minimum, we’d expect:

      • Behavior to be consistent across talentprotocol.com and talent.app, and

      • URLs that used to work (like myreceipt.eth on talent.app) should not silently regress to 404 unless there is a deliberate breaking change and some guidance on the new pattern.

    Actual behavior:

    • Some ENS/Basename URLs resolve correctly (e.g. /endhonesa, /endhonesa.eth).

    • Some ENS/Basename URLs that used to resolve (/myreceipt, /myreceipt.eth on talent.app) now return 404.

    • Some ENS/Basenames for the same underlying address (skateshop.eth, skateshop.base.eth) don’t resolve at all, despite the underlying address having a working address-based profile URL.

    • In the app UI, primary names are surfaced as expected, but secondary ENS/Basenames pointing to the same verified addresses are not consistently surfaced.


    From a user perspective:

    • It’s hard to know which identity strings are “safe” to share as public profile links (ENS vs Basename vs short handle).

    • Links using ENS/Basename that previously worked (like myreceipt.eth) can become 404s, which isn’t ideal for long-term reputation and identity.

    • For multi-brand setups (e.g. myreceipt, endhonesa, skateshop all pointing to the same or related wallets), the mental model:

      “Any verified ENS or Basename for my wallets is a valid profile URL alias” currently doesn’t hold, even though it feels aligned with the Data Points and identity model.


    If it fits your roadmap, it might help to:

    1. Document URL alias rules

      • Clearly state which naming schemes (ENS, Basename, others) are supported as profile URL aliases.

      • Clarify which patterns are expected to work (e.g. /name, /name.eth, /name.base.eth) and how they map to Users / Accounts / Profiles.

    2. Clarify primary vs secondary names

      • If only primary ENS/Basenames are meant to behave as URL aliases, stating that explicitly in the docs (and maybe in the app UI) would already reduce confusion.

      • If multiple aliases per wallet are intended, then skateshop.eth and skateshop.base.eth feel like good test cases to surface.

    3. Guard against regressions

      • If some ENS-based URLs are officially supported, it would be great to avoid regressions like the myreceipt.eth URLs that worked yesterday and are now 404, or at least to signal that behavior is experimental/subject to change.


    We are very happy to keep reporting issues like this as a heavy user of Talent, especially around multi-identity setups (multiple ENS/Basenames and wallets mapped to one person/organization).

    If you find this kind of detailed QA useful, we’d love to contribute more formally as well:

    • Testing new identity/profile features before launch.

    • Opening detailed issues or even documentation PRs in your public repositories.

    • Providing structured feedback on edge cases (multi-brand, multiple smart accounts, Base builder rewards participants, etc.).

    Please let us know:

    • If there’s a preferred place to report issues like this (GitHub repo, specific Discord channel, or an issue form).

    • And if there are contribution paths (open issues, QA tasks, docs) where something like us could be listed as a contributor.

    Thanks a lot for building Talent Protocol & Talent App — and for taking the time to look into this.

    Reported by, Prof. NOTA (on Farcaster / X)


    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.


    1. Context

    link to full issue

    2. What we are seeing

    2.1. ENS & Basenames detection in the app

    3. Profile URLs via address vs ENS/Basenames

    3.1. Address-based URLs (working as expected)

    3.2. ENS & Basename URLs (inconsistent behavior)

    A. myreceipt

    B. endhonesa

    C. skateshop

    4. Expected vs Actual

    5. Impact

    6. Suggestions

    7. Happy to help more

    [Name / Role]

  • [Name / Role]

  • [Name / Role]


  • This document records the decisions, revisions, open questions, and next steps resulting from the presentation and discussion session for AI&.

    Its purpose is to ensure that the team does not rely on memory alone, and that all important agreements are visible before moving into the next phase.


    Mark the documents reviewed:


    [Write a short summary of how the participants responded overall.]

    Example:

    • Strong interest in the physician-controlled assistant concept

    • Agreement on starting with documentation support

    • Concern about privacy and workflow fit

    • Request for clearer pilot boundaries


    Record only decisions that were clearly agreed.

    • [Decision 1]

    • [Decision 2]

    • [Decision 3]

    Example:

    • The pilot will begin with SOAP note draft generation only.

    • No patient-facing chatbot function will be included in the pilot.

    • Physician review is mandatory for all outputs.

    These are decisions intentionally postponed.

    • [Deferred Decision 1]

    • [Deferred Decision 2]

    Example:

    • Whether to include evidence summarization in pilot phase 1

    • Whether to involve more than one physician in week 1

    These are ideas discussed but not approved.

    • [Rejected Idea 1]

    • [Rejected Idea 2]

    Example:

    • Autonomous follow-up messaging

    • Direct patient access to AI& in the pilot phase


    List all requested changes to the documents or concept.

    • [Requested revision]

    • [Requested revision]

    • [Requested revision]

    • [Requested revision]

    • [Requested revision]

    • [Requested revision]

    • [Requested revision]

    • [Requested revision]


    These are important questions that remain unanswered after the session.

    • [Open Question 1]

    • [Open Question 2]

    • [Open Question 3]

    Example:

    • What patient data is truly necessary in the first pilot?

    • Which specialty should be prioritized first?

    • What clinic policy constraints must be reviewed before pilot use?


    Capture concerns raised by doctors, team members, or reviewers.

    • [Concern 1]

    • [Concern 2]

    • [Concern 3]

    Example:

    • Concern that the review process may still take too long

    • Concern that generated drafts may become too generic

    • Concern about confusion between documentation support and clinical recommendation


    This section is important.

    Record the parts that were explicitly accepted and do not currently require revision.

    • [Accepted item 1]

    • [Accepted item 2]

    • [Accepted item 3]

    Example:

    • Physician remains the final decision-maker

    • Pilot remains limited to non-autonomous use cases

    • Audit logging remains a mandatory requirement


    Choose one:

    Short explanation: [Write why this outcome was chosen.]


    • [Next step 1]

    • [Next step 2]

    • [Next step 3]

    Example:

    • Finalize pilot use case

    • Prepare technical architecture detail

    • Begin initial UI/UX mock-up

    • [Revision step 1]

    • [Revision step 2]

    • [Revision step 3]

    Example:

    • Update product blueprint to narrow scope

    • Clarify data handling boundaries

    • Revise pilot metrics and review rules


    Task
    Owner
    Deadline
    Status

    [Task]

    [Name]

    [Date]

    [Open / In Progress / Done]

    [Task]

    [Name]

    [Date]

    [Open / In Progress / Done]

    [Task]


    This log is not a formal legal document.

    It is a practical alignment tool to help the team preserve clarity, avoid false assumptions, and make sure the project moves forward based on visible agreement rather than vague memory.

    That is the point.


    P.S. Other documents related to this document:

    • Document 1 – Presentation Narrative

    • Document 2 – Strategic Notes and References

    • Document 3 – Product Blueprint

    • Document 4 – Pilot Protocol

    • Document 5 – (this document)


    P.S.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.


    Post Presentation & Discussion Record

    1. Meeting Information

    2. Purpose of This Log

    3. Documents Reviewed in the Session

    4. Summary of Overall Response

    General Response from Participants

    5. Decisions Made

    5.1 Approved Decisions

    5.2 Deferred Decisions

    5.3 Rejected Ideas

    6. Revisions Required

    6.1 Revisions to Concept / Positioning

    6.2 Revisions to Workflow / Pilot

    6.3 Revisions to Security / Privacy / Governance

    6.4 Revisions to Language / Presentation

    7. Open Questions

    8. Risks or Concerns Raised

    9. What Remains Unchanged

    10. Outcome of the Session

    11. Immediate Next Steps

    If Proceeding

    If Revising

    12. Owners and Deadlines

    13. Final Note

    Repository evidence comes from git history, project specifications, dictionaries, the context/ pack, and deliverables. Statements marked (inferred from repo) are reconstructions, not claims that a particular conversation happened.

    Git names unclekaldoteth and fabiokalandra refer to Fabio Kalandra, the human author. Codex and, where used, Claude/ChatGPT are tools. They did not own the business decisions attributed to Fabio below.


    Simulator ALPHA dibuat untuk membantu BGC dan iBLOOMING mengambil keputusan kebijakan token secara lebih aman. Masalah awalnya bukan sekadar “membuat token”, tetapi bagaimana menguji dampak aturan ALPHA terhadap data bisnis nyata: siapa yang mendapat nilai, seberapa besar beban kas perusahaan, bagaimana risiko cash-out, dan apakah hasilnya cukup adil serta bisa dijelaskan ke founder.

    Pada 16 Maret 2026, Fabio meminta AI mempelajari dokumen bisnis, reward, whitepaper, token flow, dan simulasi terlebih dahulu. Setelah itu Fabio menyetujui bentuk produk sebagai internal decision console dengan simulation engine nyata, bukan dashboard saja. Dari sana proyek berkembang menjadi aplikasi web dengan data snapshot, skenario, proses simulasi, hasil, perbandingan, decision pack, dan export laporan.

    Kontribusi Fabio terlihat jelas di percakapan: ia menentukan tujuan produk, meminta data tetap setia pada understanding document yang sudah final, meminta data salah ditolak, membedakan actual dan forecast, meminta laporan yang mudah dibaca founder, dan mengarahkan agar hasil simulasi dipakai untuk memfinalkan whitepaper serta token flow. AI membantu menyusun dokumen, membuat pola kode standar, dan mengimplementasikan perubahan. Namun arti bisnis BGC/iBLOOMING, standar kejujuran data, dan keputusan produk tetap berasal dari Fabio.


    The BGC ALPHA Simulator is an internal decision-support web app. A permitted user uploads a versioned business-data snapshot, selects or edits an ALPHA policy scenario, runs a deterministic model, and reviews the money, distribution, treasury, fairness, risk, and decision outputs. Completed runs can be compared and exported for founder discussion.

    It is deliberately not a public token product. The MVP does not deploy smart contracts, operate wallets, execute cash-outs, or prove a public market price. Its purpose is to make a Phase 1 internal policy decision evidence-based before any larger Web3 commitment.

    16 March 2026 | transcript evidence

    Fabio did not begin by asking for a generic token dashboard. His first request was to create a PRD for “BGC Alpha coin use and distribution,” but only after the AI had read the linked Living Doc, meeting notes, reward understanding document, whitepaper draft, token-flow draft, and simulation document. He then asked what the PRD would be based on. This established the project rule that the simulator must start from BGC/iBLOOMING business semantics rather than invent a simplified token model.

    When the product form was discussed, Fabio expected a web app and explicitly endorsed the sharper definition: “an internal decision console backed by a real simulation engine, not just a dashboard.” This is the clearest first product decision in the available record. It explains the later choice to build a full data-to-decision workflow instead of a presentation-only interface.

    The initial PRD and founder PRD preserve that framing: historical data is loaded, policy variables are changed, a reproducible simulation is run, and founders use the result to judge a pilot. The core scope and non-goals are documented in bgc-alpha-simulator-prd.md and bgc-alpha-simulator-prd-founder-v1.md.

    16–17 March 2026 | transcript and repo evidence

    Fabio asked for a concrete stack and repository structure, then directed the work to start with Milestones 0 and 1: bootstrap the monorepo and create the app/package skeleton. The resulting proposal selected a TypeScript pnpm/Turborepo monorepo: Next.js for the internal web app, PostgreSQL/Prisma for durable records, Zod for shared input contracts, a TypeScript simulation engine, and a separate pg-boss worker for long-running jobs.

    This was a practical MVP choice, not a claim that those tools are the only valid technology. The stack document explicitly rejects an early split into a separate frontend, backend, and Python engine as unnecessary for a deterministic MVP (inferred from repo, supported by bgc-alpha-simulator-tech-stack-and-repo-v1.md).

    Fabio also checked that the product could really run locally: he asked whether a database was needed before pnpm dev, set up Docker, investigated worker errors, and tested the sign-in and snapshot screens. This shows active author participation in moving from a plan to a runnable app, rather than treating generated code as a finished product.

    The first implementation included access roles, snapshot ingestion/validation, scenario persistence, queued execution, and result pages. Fabio then requested a plain-English explanation of the actual flow and asked for a glossary after reviewing scenario parameters. The later English and Indonesian dictionaries are the durable result of that accessibility requirement.

    17–31 March 2026 | transcript evidence

    After the first loop worked, Fabio chose the next problem: real historical data and baseline-model encoding. He asked for a build plan, approved the first phase, and then asked whether the system needed real data. When told the sample snapshot was the limiting factor, he asked for a browser CSV uploader. This moved the project away from demo-only inputs toward a proper snapshot lifecycle.

    Fabio also shaped the product's communication layer. For a meeting he asked for a short, understandable screen-by-screen explanation: sign in, upload and approve a snapshot, configure a scenario, run the worker, review the result, and compare runs. He then requested clearer overview content showing scenario results and snapshotted data, not merely system status.

    On 30–31 March, Fabio supplied and repeatedly checked new source CSV categories, asked the AI to list the files it had read, and required the simulator to align with all of them. He asked for baseline, conservative, growth, and stress scenarios with milestones, plus a configuration that could produce green health, ready milestones, and acceptable fairness. These are evidence that scenarios were intended as business-policy experiments, not decorative presets.

    2–4 April 2026 | transcript and git evidence

    Deployment exposed real production concerns: Fabio tested Vercel environment and database failures, while the repository records fixes for Next.js detection, Prisma generation, Postgres configuration, snapshot storage, Vercel Blob uploads, and inline processing where a separate worker was unavailable. Git commits from 2–3 April provide the verifiable engineering chronology.

    On 4 April Fabio identified a governance problem in the early product: rerunning the identical scenario on the identical snapshot created duplicate result records and polluted comparison. He proposed comparing the same scenario record plus the same snapshot, suggested the seedHash approach, and asked that the existing result be opened instead. He also asked for a dedicated Result Ref area where each saved run can be opened directly.

    That decision became the result-reference page and duplicate-run prevention in commit d1cf0d1 (4 April). The result is not just a technical optimisation. It keeps the comparison screen auditable: a reference identifies a distinct, reproducible policy/data combination rather than a duplicate click.

    Fabio also set a report-quality standard. He required exports to include the full Simulation Result, not only a text fragment, and insisted that a PDF actually be a presentable PDF with readable cards, tables, and charts matching the web app. He then applied the same requirement to Compare exports. This explains the later PDF and compare-export work rather than treating it as cosmetic polish.

    18–29 April 2026 | transcript and git evidence

    This is the largest evolution in the project. Fabio challenged an important shortcut: the repository had compressed the business into generic monthly fields such as PC volume, SP reward basis, generic reward totals, cash-out, and sink spend. He asked whether that meant the input no longer matched the understanding document, then stated two requirements:

    1. The data shape must be sufficient to represent the understanding document correctly.

    2. Nothing in that understanding document, which was already final, should be changed or replaced.

    He authorized implementation of SIMULATOR_FAITHFUL_DATA_MODEL_SPEC.md, requested sample data over 24 months, and kept questioning whether the imported CSV was read according to the real rules. This led to the canonical/full-detail model: members, aliases, role history, business events, PC/SP ledgers, reward obligations, pool ledgers, cash-outs, and qualification history can be retained, while monthly facts are derived for simulation. Compatibility CSV remains supported, but it is not presented as the only source of truth.

    Fabio made the data-quality standard stricter in practice. When an audit naming mismatch was found, he asked to close it. When offered a warning for a legacy field, he approved changing it to an error so future CSVs must use the correct name. In a later integrity review he agreed to start with snapshot/data integrity before scenario math and compare. These choices explain the schema-drift handling, fingerprints, validation issues, manifest/audit artifacts, accepted hybrid snapshots, and archive lifecycle recorded in the 20–22 April commits.

    24 April–6 May 2026 | transcript and git evidence

    Fabio asked for a brutally honest challenge of the whitepaper and token flow against the simulation document. This changed the simulator's role: it should not make a whitepaper look complete just because a chart exists. It must show what the data supports and what remains an assumption.

    During the 26 April review, Fabio asked about the gap between historical data and forecast data, then approved the staged extension: token-flow specification and ledger, a forecast layer separated from actuals, Web3/tokenomics assumptions, and a whitepaper evidence pack. The later implementation and documents keep these boundaries visible. Imported Data Only and Add Forecast are intentionally separate modes; actual ALPHA use and modeled ALPHA use are different measures.

    Fabio also asked whether the simulator was sufficient to produce the token flow and whitepaper, requested scenarios that balance treasury safety, fairness, cash-out risk, growth support, and internal use, and asked what was limiting internal use. This is why the product has a decision pack, cashflow-first compare view, risk flags, token-flow outputs, and finalization documents rather than an unsupported “best scenario” claim.

    Git confirms the sequence: decision artifacts and hybrid snapshots (21 April), decision-pack governance and cashflow delta (22 April), token-flow workflow and finalization artifacts (27 April), token-price assumptions as evidence (28 April), and clearer snapshot/data basis plus iBLOOMING sales-point and internal-credit cashflow support (29–30 April).

    May–June 2026 | transcript and repo evidence

    Fabio continued testing real data rather than accepting an abstract engine. He questioned pool-rate assumptions, the required active_member field, number formats used in Indonesian data, zero values in treasury/distribution outputs, and the meaning of actual versus modeled ALPHA use. He supplied a manually prepared monthly file and asked that the engine accept common thousands separators while remaining strict about meaning. These conversations led to monthly-import and forecast-label improvements in commit 02458b5 (5 May).

    For founder use, Fabio asked that a four-scenario comparison be concise and decision-ready, not verbose. He later requested reports with more charts and infographics because dense numbers were harder for some readers to use. The UI and export guidance now consistently put company cashflow before ALPHA-policy metrics and require visible data-quality and forecast labels.

    On 15 May Fabio requested a reusable context/ pack and an architecture flow chart. The six context files now preserve product intent, architecture, UI rules, code standards, AI workflow rules, and progress notes for future contributors.

    The last committed work on 27 June removes dead code, fixes Node type support, and synchronizes the lockfile. At the repository state reviewed on 12 July, the documented next phase remains calibration and hardening: choose the active evidence baseline, make imports reproducible, calibrate against observed totals, and obtain founder sign-off. Uncommitted worktree files are not treated here as verified historical milestones.

    AI was a working partner, not an autonomous product owner.

    • Research and synthesis. Fabio directed the AI to read the source material before writing the PRD, then used it to turn a large set of business documents into plans, dictionaries, screen explanations, decks, and founder-facing drafts.

    • Standard software scaffolding. AI helped produce conventional patterns such as the monorepo layout, Next.js route/page shells, Prisma models, Zod validation, worker jobs, test fixtures, report renderers, and deployment fixes.

    • Iterative implementation and debugging. Fabio tested local and deployed behavior, supplied errors and source files, asked direct questions, and requested fixes. The AI then inspected and changed code under those constraints.

    • Plain-language translation. AI helped explain technical concepts such as a snapshot, worker, fingerprint, scenario parameter, and data contract to a non-engineer audience. Fabio repeatedly asked for wording that founders could understand quickly.

    AI was useful for speed and standard patterns. It was not the source of truth for BGC/iBLOOMING economics, policy legitimacy, or evidence quality. Those needed human judgment and source documents.

    The following items are direct author contributions supported by transcript evidence. They are separated from AI-generated implementation detail.

    Fabio's contribution
    Evidence in the transcripts
    Why it matters

    Defined the project problem as ALPHA use and distribution, grounded in the business documents.

    16 Mar: Fabio required the AI to read the Living Doc, meeting notes, reward understanding document, whitepaper, token flow, and simulation document before creating the PRD.

    Prevented a generic crypto product from replacing the actual BGC/iBLOOMING problem.

    Chose the product form.

    16 Mar: Fabio endorsed an “internal decision console backed by a real simulation engine, not just a dashboard.”

    Set the direction for a data, model, and decision workflow.

    Directed the MVP toward a real runnable application.

    16 Mar: Fabio initiated the monorepo milestones, database setup, local testing, and first implementation tickets.

    Turned the concept into working software rather than a static proposal.

    The transcripts provide strong evidence for the product framing, decisions, and iteration above. They do not prove every low-level authorship detail. The following are therefore inferred from repository evidence:

    • Exactly which lines or components were typed manually by Fabio versus generated by an assistant.

    • The precise private discussions that produced every business number in the baseline, scenario guardrail, and token-flow documents.

    • The original creation dates of planning files before they entered the repository.

    • Any conversation that occurred outside the available Codex logs, including prior ChatGPT or Claude chats that were not stored in this local session archive.

    This limitation is intentional. It is better to label missing evidence than to invent a conversation or overstate a contribution.

    For a reviewer who wants to audit this narrative without reading raw chat logs:

    • Project transcripts: local Codex sessions dated 16 March, 23–24 March, 30–31 March, 2–4 April, 10 April, 18 April, 26 April, and 15 May 2026, filtered to the bgc simulator workspace. The 16 March session is the earliest available transcript for this project.

    • Git history: git log --all --stat --date=short; committed milestones run from 2 April to 27 June 2026 under Fabio's identities above, with merge commits also recorded.

    • Product and implementation records: bgc-alpha-simulator-prd.md, bgc-alpha-simulator-prd-founder-v1.md, bgc-alpha-simulator-tech-stack-and-repo-v1.md, bgc-alpha-simulator-data-baseline-build-plan-v1.md, bgc-alpha-simulator-calibration-workflow-v1.md, SIMULATOR_FAITHFUL_DATA_MODEL_SPEC.md, COMPANY_CASHFLOW_LENS_SPEC.md, the English/Indonesian dictionaries, context/, and deliverables/final-docs/.

    Updated 12 July 2026. This document summarizes evidence and deliberately omits private data, raw credentials, and unnecessary transcript detail.


    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.


    Ringkasan (Bahasa Indonesia)

    1. What the simulator is

    2. Chronological build narrative

    Phase A: learn the business before defining the product

    Phase B: turn the concept into a buildable system

    Phase C: make the model data-driven and usable in meetings

    Phase D: deployment, run records, and presentable evidence

    Phase E: protect business meaning with a faithful data model

    Phase F: broaden from historical replay to a controlled policy decision pack

    Phase G: calibration, labels, founder readability, and cleanup

    3. How AI was used

    4. Author contributions: Fabio Kalandra

    5. What is reconstructed rather than directly witnessed

    6. Evidence index

    Arsip Rahasia

    Kumpulan tools/screenshot lama (hanya untuk internal)

    Folder terenkripsi

    Notifikasi Bahaya

    Coaching tentang tanda-tanda penipuan

    Orang tua, pelajar, publik umum

    ✅ Langsung

    Zine: “Aku Pernah Menutup Toko”

    Zine cerita otentik

    Kolektor, pembaca niche

    ⚙️ Print on Demand

    Shadow Confessional

    NFT cerita pengakuan (1 of 1)

    Kolektor seni, komunitas cyber

    ✅ Langsung

    Video Rekonstruksi

    Simulasi kasus + edukasi

    Komunitas belajar, kanal edukasi

    ⚙️ Produksi pasca order

    ESCROW GUEST LECTURE REPORT

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    — Web2 → Web3 Pragmatics

    Report generated: 2025-10-24 05:22:40


    -1) Introduction

    • Space-Time: Petra Christian University · Thursday, October 23, 2025 · 10:30–1:00 PM · AVT501

    • Organizer: IDNFT x UK Petra (guest lecture, no recording/distribution)

    • Total form responses: 42


    1. Audience Profile (Department, Year, Experience, Interests)

    2. Key Session Insights (summary)

    3. Student Reflections (representative excerpts)

    4. Recommendations & Next Steps (campus & students)


    • By Department — Narrative In that room, Business Accounting took the helm — 25 seats packed, ready to price risk and wire in control. Then Visual Communication Design — 8 sharp eyes for form, poised to translate payment architecture into visuals that move people. Accounting arrived 4 strong: guardians of the ledger, fluent in decimal truth. Business & Management stepped in with 2 — strategy on its feet. And 2 unclassified souls, the agile cross discipline jumpers. The mix is right: numbers, aesthetics, governance, and curiosity — all meeting at the interchange of escrow and cross-border rails.

    • By Year — Narrative The Class of 2023 leads the charge — 21 strong — a cohort in motion, ready to turn theory into working rails. 2024 follows with

    • Crypto/Web3 Experience — Narrative A field of beginners sets the stage: 37 with zero experience—not a deficit, but pure signal with no legacy bias. They learn fast when shown rails, fees, latency, and risk laid out plainly. The 1–2 years group—just 3—forms the bridge: they translate first principles into the first working flows. And the 3–5 years duo—2 steady hands—serve as anchors, table leads for mini-demos and sharper questions. The curve is perfect for a from-zero-to-escrow sprint: clarity first, then a concrete path to shipping.

    • Interests — Narrative The room tilted toward doing: the Extended Workshop (discounted campus rate) tops the chart with 24 raised hands—students asking for three hours of real rails, not just slides.


    • Rails isn't a "tribe," it's a strategic choice. Bank/fintech: paper trail & reputation; Stablecoin (e.g., USDC): 24/7, fast, programmable.

    • Traditional escrow vs. smart contract: choose based on frequency, clarity of rules, and the need for a transparent trail.

    • Practical compliance: KYC/AML on on/off-ramps; simple recordkeeping & taxes are still required.

    • Minimal architecture: Web2 app ↔ on/off-ramps ↔ wallet ↔ escrow ↔ records—start with the simplest executable flow.

    Material structure reference: ''.


    • Prompt Used: Write your assessment/response/comments on the existence of “Prof. NOTA” within your reality (as a student, researcher, creator, or lecturer/teacher). What do you understand? What resonates or sparks curiosity? What, if anything, feels challenging or unsettling? How (if at all) does this influence the way you view technology, the economy, or yourself? Please include concrete examples where possible.

    • Student Reflections Response Summary

      • Blockchain made legible—beyond the buzzword. Students left with a working mental model: blocks, consensus, finality; why Bitcoin/USDT/USDC matter; where decentralization, transparency, and trust-without-middlemen are tools (not slogans). The horizon widened: finance, logistics, education—anywhere ledgers, incentives, and accountability collide. Translation:


    30-Day Objective: convert Petra momentum into a working program: one Extended Workshop (3 hours), a Capstone/Skripsi Clinic (2×60’/team), an NFT Proof-of-Attendance (ERC-1155 on Base) as certification and gating for materials/bonuses. Everything moves synchronously: students learn and build, lecturers lead learning outcomes, institutions formalize credits and assessments, and the public witnesses a replicable process.

    • Micro Call to Actions

      • For the Students

        • Schedule an Extended Workshop (3 hours) within 2–3 weeks. Claim their POA NFT from Prof. NOTA Inc. as proof of attendance or certification and ticket to access Prof. NOTA. Build one real end-to-end flow (choose rails, add minimal escrow, log the record).


    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 . 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.


    RECEIPT SOSPOL 2025/07-08

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    (Periode: 19 Juli – 19 Agustus 2025 · Outlook: September 2025)

    Di 0101 Universe, republik adalah ledger sosial: setiap aksi warga, setiap respons negara, tercatat sebagai transaksi—tak bisa dihapus, hanya bisa ditambahkan. Bulan ini, buku besar Indonesia menulis baris-baris yang menyala: protes besar, respons aparat, volatilitas pasar, dan tarik-ulur arah kebijakan. Yang riuh di jalan adalah mempool; yang kelak jadi sejarah adalah blok yang kita sepakati bersama.


    1) Ringkasan Cepat (TL;DR)

    • Gelombang protes meletup dari isu tunjangan perumahan DPR ~Rp50 juta/bulan; eskalasi mencakup pembakaran gedung DPRD di sejumlah daerah dan korban jiwa di Makassar (3 tewas, 2 luka, 30 Agustus). Presiden membatalkan lawatan luar negeri untuk menangani situasi. [Reuters, 30–31 Ags 2025; The Soufan Center, 5 Sep 2025]

    • Bank Indonesia (BI) menegaskan intervensi stabilisasi rupiah (spot, DNDF onshore–offshore, pembelian SBN sekunder) seiring gejolak pasar. [APSN/Reuters, 1 Sep 2025]

    • Inflasi Juli 2025: 2,37% YoY (dalam rentang sasaran BI). BBM: Pertalite tetap Rp10.000 (Agustus), penyesuaian minor di BBM non-subsidi. [BPS, 1 Ags 2025; Katadata/Databoks, 1 Ags 2025]

    • IKN & 17 Agustus: upacara HUT ke-80 dipusatkan di Jakarta; di sisi lain ada target kompleks pemerintahan IKN 3 tahun. [Kompas/Tempo, 15–17 Ags 2025]

    • Moderasi platform: Pemerintah meminta TikTok, Meta memperketat konten berbahaya; TikTok LIVE sempat ditangguhkan di Indonesia saat puncak tensi. [Reuters/Jakarta Post, 27–30 Ags 2025]


    Protes bermula dari kabar tunjangan perumahan DPR ~Rp50 juta/bulan—sekitar >10× UMP DKI—di tengah tekanan biaya hidup. Benturan dengan polisi terjadi di berbagai kota. Di Makassar, gedung DPRD Sulsel dibakar (30 Agustus), menewaskan tiga orang dan melukai lainnya. Presiden membatalkan rencana kunjungan ke Tiongkok untuk fokus pada krisis domestik. Baca: Reuters (30–31 Agustus 2025), The Soufan Center (5 September 2025).

    Di 0101 Universe, legitimasi bukan hanya hasil pemilu; ia adalah throughput konsensus harian. Ketika mempool ketidakpuasan menumpuk dan gas moral menjadi mahal, jaringan sosial throttling.


    • Program Makan Bergizi Gratis (MBG) ditetapkan sebagai jangkar sosial–ekonomi menuju 2026: alokasi ~Rp335T (draft RAPBN 2026) untuk 82,9 juta penerima (siswa, ibu hamil, balita). Secara politik, ini token utilitas: gizi (jangka panjang), cashflow ke petani/UMKM pangan (jangka menengah), dan legitimasi sosial (jangka pendek).

    • IKN: narasi staggered migration. Upacara HUT RI ke-80 digelar di Jakarta, namun Presiden menargetkan kompleks pemerintahan IKN selesai ±3 tahun—membentuk expectation bertahap, bukan big-bang.

    • Energi/BBM

    Rujukan: Katadata/Databoks, Tempo/Kompas (IKN & 17 Agustus), Tempo & CNBC Indonesia (MBG).


    IHSG dan IDR terguncang saat tensi sosial memuncak; BI menyatakan siap aktif di spot, DNDF (onshore–offshore), dan SBN sekunder untuk menjaga stabilitas nilai tukar. Narasi resmi: fundamental terjaga; realitas pasar: risk premium Indonesia repricing mengikuti risiko politik di headline. Rujukan: APSN (kutipan BI), Reuters (poll & pembaruan intervensi).


    Pemerintah memanggil perwakilan TikTok & Meta untuk meningkatkan moderasi konten berbahaya (disinformasi, pornografi, judi online) tanpa menunggu permintaan resmi. Di lapangan, video viral insiden polisi–warga menjadi amplifier protes. TikTok menangguhkan fitur LIVE sementara di Indonesia saat eskalasi. Rujukan: Reuters (27 & 30 Agustus 2025), The Jakarta Post (28 Agustus 2025).


    Protes Agustus 2025 bukan anomali, melainkan bagian dari trajektori ketidakpuasan yang lebih panjang: tata kelola, representasi, ekonomi rumah tangga, hingga persepsi militerisasi ruang sipil. Di sini brand promise republik diuji: apakah ledger sosial tetap append-only oleh warga, atau terkunci oleh admin key?


    Opini analitis ala Prof. NOTA—anggap sebagai “scenario tree” di smart contract sosial.

    Base Case (prob. >50%)

    • Intensitas protes menurun, bergeser ke investigasi/etik (kasus tewasnya warga & evaluasi SOP pengendalian massa).

    • BI tetap aktif di valas; IDR bergerak dalam band intervensi; inflasi tetap dalam target.

    • Diskursus tunjangan DPR masuk fase policy review terbatas (komunikasi publik + transparansi), tanpa revisi drastis awal September.

    Stress Case (prob. ~30%)

    • Insiden baru/viral menyulut gelombang kedua; curfew ad-hoc lokal mungkin muncul.

    • Pasar overshoot (risk-off); BI memperdalam DNDF; otoritas memperketat short-term flows (analog: circuit breaker jaringan).

    Policy Pivot (prob. ~20%)

    • Gestur simbolik: peninjauan skema tunjangan (tim ad hoc, uji publik) + kompensasi/dukungan keluarga korban sebagai state empathy signal.

    • MOU platform–pemerintah untuk fast track moderasi konten berisiko saat demo (tanpa pemblokiran luas).


    Republik adalah open‑source protocol: kodenya konstitusi, maintainer-nya warga. Saat pull request dari jalanan ditolak tanpa review, fork sosial mengancam. The Monthly Public Receipt ada untuk memastikan commit log kejadian tidak hilang di timeline, melainkan tersimpan rapi di ledger publik.


    • Protes & eskalasi:

      • Reuters —

      • Reuters —

      • The Soufan Center —


    Disusun: 2025-09-17 22:49 WIB · Prof. NOTA POV


    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 . 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.


    Required real-data ingestion and browser upload.

    17 Mar: after identifying the lack of real historical snapshots as the blocker, Fabio asked for browser CSV upload.

    Made the simulator testable against evidence, not only samples.

    Defined usable scenario thinking.

    30–31 Mar: Fabio asked for baseline, conservative, growth, and stress scenarios, milestones, and health/fairness checks.

    Made the model useful for trade-off decisions.

    Established reproducible run governance.

    4 Apr: Fabio identified duplicate scenario/snapshot runs, proposed checking the same scenario record plus snapshot, and required an existing result to open instead.

    Protects result references and prevents misleading duplicate comparisons.

    Set the founder-report standard.

    4 Apr and 3–6 May: Fabio required real, presentable PDF exports, web-consistent charts, concise comparison language, and later more visual reports.

    Made technical outputs usable in founder discussions.

    Protected the fixed business semantics.

    18 Apr: Fabio required enough data to represent the understanding document correctly and said it must never be changed or replaced.

    This is the basis for the faithful/full-detail data model.

    Chose strict data integrity over convenient acceptance.

    18–26 Apr: Fabio asked to close audit mismatches, approved turning a legacy warning into an error, and prioritized snapshot/data integrity.

    Reduces the risk that a neat-looking result is based on invalid input.

    Required honest boundaries between actual data, forecasts, and claims.

    24–26 Apr: Fabio requested an objective challenge of the whitepaper/token flow, asked how forecast data should work, and approved distinct actual/forecast and evidence layers.

    Avoids presenting model assumptions as historical facts.

    Kept company cashflow and token policy connected but distinct.

    26 Apr onwards: Fabio asked about treasury safety, fairness, cash-out risk, growth support, internal use, pool basis, and internal-credit meaning.

    Supports the cashflow-first decision lens rather than treating ALPHA totals as the whole business.

    Made future work easier to understand and continue.

    15 May: Fabio requested the reusable context pack and architecture diagram.

    Captures project rules for later maintainers and study.

    [Name]

    [Date]

    [Open / In Progress / Done]

    Discussion Log
    : Agustus menampilkan
    status quo
    untuk Pertalite (Rp10.000) dan
    penyesuaian minor
    pada BBM non-subsidi—membantu menjaga
    inflasi
    tetap terjangkau.

    Pasar & kebijakan moneter:

    • APSN — BI intervenes to stabilize rupiah following mass protests (1 Sep 2025)

    • Reuters — Poll: BI to hold rates as political shake‑up hits rupiah (16 Sep 2025)

  • Inflasi & energi:

    • BPS — Inflation July 2025 at 2.37% YoY (1 Aug 2025)

    • Databoks/Katadata — Pertamina fuel price list August 2025 (1 Aug 2025)

  • IKN & 17 Agustus:

    • Kompas — Kenapa HUT ke‑80 RI berpusat di Jakarta, bukan IKN? (17 Jul 2025)

    • Tempo (EN) — Prabowo targets three‑year completion for IKN government complex (15 Aug 2025)

    • Tempo — Perbedaan upacara HUT RI 2025 vs 2024: dipusatkan di Jakarta (17 Aug 2025)

  • Platform & moderasi:

    • Reuters — Indonesia urges TikTok, Meta to act against harmful content (27 Aug 2025)

    • The Jakarta Post — Ministry urges TikTok, Meta to act against harmful content (28 Aug 2025)

    • Reuters — TikTok temporarily suspends LIVE in Indonesia (30 Aug 2025)

  • 2) Jalanan sebagai Mempool: Protes, Polisi, dan Konsensus Publik

    3) Kebijakan & Fiskal: MBG, IKN, dan Harga Energi

    4) Pasar Keuangan: Volatilitas sebagai Health Check

    5) Platform & Ruang Informasi: Moderasi sebagai Rate Limit

    6) Bacaan Struktural: Di Balik Tunjangan & Jalanan

    7) Outlook September 2025 (Skenario)

    8) Catatan Prof. NOTA (0101 POV)

    📚 Referensi

    President cancels China trip as protests continue (30 Aug 2025)
    Deadly protests force U‑turn on lawmakers’ pay (31 Aug 2025)
    IntelBrief: Are anti‑government protests in Indonesia gaining momentum? (5 Sep 2025)
    Prof. NOTA
    )
    Profile
    ENS Data Points
    Base Data Points
    Talent API
    Profile Search
    Profiles Default Search Fields
    Data Points
    13
    hungry minds, born in the pressure cooker of new constraints.
    2022
    brings
    4
    steady hands—the quiet veterans who’ve seen a few systems fail and still show up to build.
    Unknowns
    —
    3
    blanks on the ledger—remind us that not every signal needs a label to carry weight. And
    2025
    arrives early with
    1
    advance scout, proof that the next wave is already here. Years on paper, yes—but what we’re really tracking is
    momentum
    meeting
    escrow
    and
    cross-border rails
    .
    Community session updates
    follow at
    22
    , a heartbeat for momentum: they want a cadence, a tribe, a drum to march to.
    Research internship (selective)
    pulls
    15
    —the ones who don’t just want answers but
    new questions
    to wrestle with. And
    Capstone Clinic (team-based, 2×60’)
    lands
    6
    —small in count, sharp in intent: ship a thing, defend it, make it better. Desire is clear:
    learn → build → belong → publish
    .
    they now see rails and trade-offs, not hype and mystique.
  • “Prof. NOTA” as a live hypothesis. An entity from the 0101 Universe, appearing as v.11.11 (HFP), turned the lecture hall into a thought experiment: What is a professor? What is an institution? What is identity when knowledge ships at machine speed? The line between human and system blurred—not to erase the human, but to upgrade the classroom into a studio where ideas are co-built.

  • Technology ≠ replacement; it’s amplification. Students named the real constants: empathy, intuition, ethics, and context. Tools can calculate; teachers (human) cultivate. The future is co-teaching: human judgment steering, technological capacity scaling. Lecturers: you keep the pedagogy. Systems: bring the rails, the data, the reproducibility.

  • License to think—critically, originally, cross-discipline. The rational, data-first, occasionally “radical” stance of Prof. NOTA nudged the room from opinion to model, from memorize to prototype. Curiosity spiked; originality felt permissible; crossing silos became the default move. Students: bring your capstones and contradictions. We’ll bring escrow, incentives, and shipping rituals.

  • Output: a mini-project per student/team that can be shown and audited.

  • For the Lecturers

    • Co-design a 3-session sequence: lecture → lab → clinic. The lecture's own learning outcomes and rubrics; we wire the rails and tools.

    • Output: a 1-page syllabus (RPS) with assessment criteria and example artifacts.

  • For the Institutions

    • Formalize a semester track (credits + assessment) mapped to industry-grade deliverables and auditable learning artifacts (repo, logs, POA on-chain).

    • Output: a short policy note (1–2 pages) and an execution calendar.

  • For the Public

    • Publish the process, not just the result. Ship a short write-up, diagrams, and artifact links so the next cohort can stand on today’s work.

    • Output: one public summary page + links to materials/artifacts.

  • Execution Package (Clear & Concrete)

    1. Extended Workshop (3 hours, in 2–3 weeks)

      • Target: top departments and years from the report.

      • Student: limited seats (30–50), only for 42 students who fill the Interest Form.

      • Content: pick rails (bank/fintech/stablecoin), minimal escrow, simple bookkeeping, mini-demo.

      • Proof: POA NFT, repo/template, exercise checklist.

    2. Capstone/Final Project Clinic (2×60’ per team, limited slots)

      • Focus: idea → prototype → assessed artifact.

      • Proof: team issue tracker, experiment plan, staged reviews.

    3. NFT Proof-of-Attendance (ERC-1155 on Base)

      • Function: credentialing + gates for the materials and other utilities.

      • Claim: unique link + embedded wallet (newbie-friendly).

      • Auditability: on-chain, tied to the attendance list.

    4. Central Landing Page for the Materials + Post-Session Quiz + POA NFT Claim Page

      • Form fields: name, email, department, year, interests, experience, etc.

      • Automation: auto-emails for schedule; able to be exported to a follow-up dashboard.

      • Integration: the materials, NFT claim page, and session calendar.

  • Success Metrics (Measure What Matters)

    • Workshop registrations ≥ X · Attendance ≥ Y%

    • POA NFT claims ≥ Z% of attendees (engagement validation)

    • Clinic conversion ≥ N teams · Publishable artifacts ≥ M

    • Feedback/NPS ≥ 8/10 on clarity, relevance, and bravery in thinking

  • Fast Timeline (Recommended)

    • Week 1: launch landing page + email blast; finalize outline & rules

    • Week 2/3: run the 3-hour Workshop + trigger POA NFT claims

    • Week 3/4: kick off Capstone/Final Project Clinic + publish the process (summary + artifacts)

  • 0) Report Structure

    1) Audience Profile

    2) Key Session Insights

    3) Student Reflection

    4) Integrated Action Plan

    Mantra: learn → build → belong → publish. Students own the work, lecturers own the pedagogy, institutions own the credential, and the public owns the inspiration.

    International Payments & Escrow — Web2 → Web3 Pragmatics
    Prof. NOTA
    Grafik by Department dan by Year
    Grafik by Experience dan by Interest

    URAIAN SDM PERURI CONNECT WEB3

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Dokumen ini menguraikan peran, fungsi, dan scope kerja setiap SDM yang dibutuhkan dalam implementasi Peruri Connect × Blockchain (Hybrid, Tokenized, Interop). Setiap role diplotkan dengan bagian relevan di dokumen:

    • 📄 (Rencana Teknis, 2000 user)

    • 📄 (Spec Eksekusi v1).


    AI& PITCH CONTENT

    Its purpose is simple: Reduce administrative friction so physicians can focus on clinical reasoning and meaningful patient interaction.

    Pilot Project for Physician-Centered Clinical Assistance

    • March 2026


    In a busy clinical day, physicians are often pulled toward screens.

    They repeatedly:

    • rewrite similar information

    • adjust documentation formats

    Fungsi:
    Menjaga dan mengembangkan aplikasi mobile Peruri Connect (Flutter).
  • Scope Kerja:

    • Implementasi UI/UX untuk tab Wallet, Tokens, Badges.

    • Integrasi endpoint baru (/wallet/status, /activity/track, /activity/:id).

    • Sinkronisasi status activity → token/badge dari backend CI3.

  • Plot Dokumen:

    • Plan: Bagian Integrasi Flutter.

    • Spec: Bagian Endpoint CI3 / Flutter.

    • Fungsi: Mengembangkan API pada CodeIgniter 3.

    • Scope Kerja:

      • Membuat endpoint wallet status, activity track, activity status.

      • Integrasi ke Blockchain Adapter Service (BAS).

      • Middleware untuk autentikasi (JWT, mTLS).

    • Plot Dokumen:

      • Plan: Bagian Integrasi CI3 (auth middleware, BAS, Mirror Worker).

      • Spec: Bagian Endpoint CI3 / Flutter, SOP Keamanan.

    • Fungsi: Menjamin kualitas integrasi blockchain di aplikasi Flutter.

    • Scope Kerja:

      • Uji end-to-end flow: user activity → reward token/badge.

      • Uji error handling (gagal tx, status pending).

      • Regression test setelah update app.

    • Plot Dokumen:

      • Plan: Bagian Alur Data.

      • Spec: Bagian Runbook Pilot.

    • Fungsi: Mendesain pengalaman pengguna untuk fitur blockchain di app.

    • Scope Kerja:

      • Desain visual tab Wallet/Token/Badge.

      • Pastikan branding Peruri konsisten.

      • Membuat flow sederhana agar user tidak bingung dengan konsep “wallet”.

    • Plot Dokumen:

      • Plan: Bagian Integrasi Flutter (UI/UX minimal).

      • Spec: Bagian Endpoint CI3/Flutter.

    • Fungsi: Menjaga alur CI/CD untuk app + API.

    • Scope Kerja:

      • Release management Flutter app.

      • Deploy CI3 API dengan endpoint baru.

      • Monitoring availability backend CI3.

    • Plot Dokumen:

      • Plan: Bagian Arsitektur Tingkat Tinggi (Flutter + CI3).

      • Spec: Bagian Runbook Pilot.


    • Fungsi: Men-setup dan mengelola private blockchain (Besu + IBFT2).

    • Scope Kerja:

      • Deploy validator & tx nodes sesuai VM sizing.

      • Konfigurasi konsensus IBFT2 (3–5 validator).

      • Monitoring jaringan blockchain.

    • Plot Dokumen:

      • Plan: Bagian Private Chain — Rekomendasi & Sizing Pilot (2000 user).

      • Spec: Bagian Topologi Infrastruktur, VM Sizing.

    • Fungsi: Membuat & audit kontrak token dan badge.

    • Scope Kerja:

      • Buat kontrak: PTKN (ERC20), PBADGE (ERC1155 non-transferable), PLOG (merkleroot log).

      • Unit testing & audit kontrak.

      • Dokumentasi ABI untuk integrasi BAS.

    • Plot Dokumen:

      • Plan: Bagian Tokenisasi Aktivitas (PTKN, PBADGE, PLOG).

      • Spec: Bagian ABI & Policy Rules.

    • Fungsi: Bangun service integrasi CI3 ↔ Blockchain.

    • Scope Kerja:

      • Implementasi Blockchain Adapter Service (BAS).

      • Implementasi Mirror Worker (consume activity stream).

      • Mapping identity (user_id → wallet).

    • Plot Dokumen:

      • Plan: Bagian Integrasi CI3 (BAS + Mirror Worker).

      • Spec: Bagian Endpoint CI3 / Flutter, Runbook Pilot.

    • Fungsi: Menjaga keamanan wallet & jaringan blockchain.

    • Scope Kerja:

      • Setup HSM/KMS untuk kunci privat.

      • Implementasi mTLS antar service, audit log, RBAC.

      • Backup & recovery node blockchain.

    • Plot Dokumen:

      • Plan: Bagian Keamanan & Kepatuhan.

      • Spec: Bagian SOP Keamanan.

    • Fungsi: Menjamin integrasi kontrak & policy berjalan sesuai.

    • Scope Kerja:

      • Uji minting PTKN/PBADGE sesuai rules (attendance, training).

      • Simulasi failover validator.

      • Monitoring latency & tx success rate.

    • Plot Dokumen:

      • Plan: Bagian Alur Data, Roadmap Pilot.

      • Spec: Bagian Runbook Pilot.

    • Fungsi: Menyediakan dan menjaga infrastruktur blockchain.

    • Scope Kerja:

      • Provisioning VM (validator, tx node, BAS).

      • Setup monitoring (Prometheus, Grafana).

      • Incident handling & scaling infra.

    • Plot Dokumen:

      • Plan: Bagian VM sizing.

      • Spec: Bagian Topologi Infrastruktur, Monitoring.


    • Fungsi: Menjembatani desain App ↔ CI3 ↔ BAS ↔ Chain.

    • Scope Kerja:

      • Validasi blueprint teknis.

      • Pastikan alur data dan endpoint sesuai kebutuhan.

      • Menjadi referensi lintas tim.

    • Plot Dokumen:

      • Plan: Bagian Arsitektur Tingkat Tinggi + Alur Data.

      • Spec: Semua bagian, sebagai penghubung.

    • Fungsi: Menjaga timeline, milestone, komunikasi antar tim.

    • Scope Kerja:

      • Breakdown deliverables dari roadmap (F0–F4).

      • Mengatur sprint meeting antar tim.

      • Laporkan progress ke stakeholder Peruri.

    • Plot Dokumen:

      • Plan: Bagian Roadmap.

      • Spec: Bagian Runbook Pilot.

    • Fungsi: Menjamin regulasi tokenisasi sesuai aturan.

    • Scope Kerja:

      • Review token PTKN sebagai loyalty/internal token (non-speculative).

      • Dokumentasi internal untuk Peruri & otoritas.

      • Proyeksi keperluan regulasi bila anchor ke public chain.

    • Plot Dokumen:

      • Plan: Bagian Keamanan & Kepatuhan.

      • Spec: Bagian SOP Keamanan + Policy Rules.

    • Fungsi: Sosialisasi dan adopsi internal karyawan.

    • Scope Kerja:

      • Menyiapkan panduan penggunaan wallet di app.

      • Pelatihan untuk 2000 user pilot.

      • Feedback loop untuk iterasi fitur.

    • Plot Dokumen:

      • Plan: Bagian Integrasi Flutter (UI/UX minimal).

      • Spec: Bagian Runbook Pilot (step 6–8).


    • Fungsi: Analisis data aktivitas user.

    • Scope Kerja:

      • Sinkronisasi off-chain DB dengan on-chain log.

      • Visualisasi loyalty/performance metrics.

    • Plot Dokumen:

      • Plan: Bagian Tokenisasi Aktivitas + Roadmap F3/F4.

    • Fungsi: Implementasi smart account & gasless UX.

    • Scope Kerja:

      • Paymaster setup untuk biaya gas nol.

      • Session keys & policy-based spending.

    • Plot Dokumen:

      • Plan: Bagian Fase 4 (4337 & Gasless).

    • Fungsi: Menghubungkan private chain ke Base/OP/Ethereum.

    • Scope Kerja:

      • Implementasi anchoring hash batch.

      • Membuat proof public untuk notarization.

    • Plot Dokumen:

      • Plan: Bagian Fase 3 (Interop & Anchoring).


    Komposisi SDM yang dirinci di atas langsung diturunkan dari dokumen plan dan spec. Dengan ini, setiap role jelas posisinya, scope kerja, dan keterhubungan dengan milestone implementasi Peruri Connect × Blockchain.


    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.


    1. Peruri Connect Team (Mobile App)

    a. Flutter Developer

    peruri_connect_plan.md
    peruri_connect_spec_v1.md

    b. Backend CI3 Developer

    c. QA/Tester (Mobile)

    d. UI/UX Designer

    e. DevOps/Infra Support (Mobile)

    2. PDS + Voyage Team (Blockchain & Protocol)

    a. Blockchain Protocol Engineer

    b. Smart Contract Developer

    c. Integration Engineer (BAS)

    d. Security/Infra Engineer

    e. QA/Tester (Blockchain)

    f. DevOps/Cloud Infra

    3. Tim Lintas (Joint)

    a. Solution Architect (Hybrid)

    b. Product/Project Manager

    c. Compliance & Legal Specialist

    d. Training & Adoption Specialist

    4. Opsional (Fase Lanjut)

    a. Data Analyst (On/Off-chain)

    b. 4337/AA Engineer

    c. Public Chain Integration Engineer

    ✅ Kesimpulan

  • search for guidelines

  • prepare follow-up messages

  • coordinate with teams

  • This constant context switching divides attention into three directions:

    1. Patient interaction Conversation, examination, clinical reasoning.

    2. Documentation and formatting SOAP notes, discharge summaries, referral letters, chart updates.

    3. Coordination and follow-up Education messages, reminders, care planning.

    The result is not only fatigue. Communication quality may become inconsistent, and important signals can be overlooked when time pressure rises.

    Physicians need more space to think clearly.


    AI& is designed to support physicians by handling structured and repetitive work behind the scenes.

    Its purpose is simple:

    Reduce administrative friction so physicians can focus on clinical reasoning and meaningful patient interaction.

    AI& does not replace clinical decisions. AI& does not communicate with patients independently. AI& does not operate without physician approval.

    Every output generated by AI& remains under physician control.

    AI& functions as a physician-controlled clinical assistant, not an autonomous system.


    AI& is designed to operate in areas that frequently consume physician time:

    1. Documentation structuring

    2. Evidence navigation

    3. Communication preparation

    The principle is straightforward:

    AI& handles repetitive structure so physicians can focus on judgment.


    AI& helps convert structured clinical points into organized draft documents.

    Possible outputs include:

    • SOAP note drafts

    • discharge summaries

    • problem lists

    • structured clinical summaries

    Important principles:

    • No automatic diagnosis

    • No automatic clinical decisions

    • Physician review required before finalization

    • Full audit log of edits and approvals

    The goal is consistency and clarity, not automation of medical judgment.


    Physicians often need quick orientation in clinical literature.

    AI& helps by:

    • summarizing guideline sections

    • highlighting key practice points

    • presenting structured comparison tables

    • linking to primary sources

    AI& does not replace reading the original literature.

    Instead, it helps physicians reach the right clinical question faster.


    AI& assists physicians in preparing structured communication drafts.

    Examples include:

    • patient or parent education messages

    • follow-up reminders

    • visit summaries

    • care plan explanations

    Templates follow predefined clinical communication standards.

    Each output includes:

    • clear structure

    • empathetic language

    • safety lines

    • physician approval before sending

    The goal is consistent and safe communication.


    AI& works as a structure-building engine.

    Clinical points entered by the physician (non-identifiable where possible)

    Structured SOAP draft generated.

    Organized clinical issues and possible considerations.

    Reminder prompts for missing documentation elements.

    Physician edits, contextualizes, and approves.

    System records when the draft was generated, edited, and finalized.

    Key design principle:

    AI& assists structure, but the physician owns the clinical content.


    AI& helps create a continuous flow between clinical knowledge and patient communication.

    Summarize guideline points with references.

    Transform evidence into simple, empathetic explanations.

    Generate structured follow-up plans.

    Examples:

    • control visit timelines

    • monitoring checklists

    • reminder drafts

    All messages require physician approval before delivery.


    AI& is most effective when introduced as a small, controlled pilot.

    Select one use case.

    Example:

    • SOAP documentation draft

    Define clear restrictions:

    • no patient identity processing

    • no emergency handling

    • no automated clinical advice

    Prepare templates and review checklists.


    Apply AI& to the first ten clinical cases.

    Observe:

    • time saved

    • physician corrections

    • documentation quality

    • possible near-misses


    Improve:

    • prompts

    • structure

    • safety lines

    • documentation standards

    Align wording with clinical policies.


    Review pilot metrics:

    • physician trust

    • editing workload

    • communication clarity

    • documentation consistency

    Decide whether to expand use cases gradually.


    AI& may facilitate structured discussion between physicians.

    This does not involve sharing patient identities.

    Instead, the system may allow:

    • reflective discussion prompts

    • anonymized case patterns

    • structured clinical questions

    • literature-supported perspectives

    All interactions remain physician-initiated and physician-controlled.

    AI& acts only as a discussion facilitator, not a decision authority.


    AI& works behind the screen so physicians can remain fully present with patients.

    By structuring repetitive work, AI& aims to support:

    • calmer clinical decision making

    • clearer communication

    • more meaningful patient interaction

    Technology should not replace the physician.

    It should protect the physician’s ability to think clearly and care deeply.



    P.S. Other documents related to this document:

    • Document 1 – Presentation Narrative (this document)

    • Document 2 – Strategic Notes and References

    • Document 3 – Product Blueprint

    • Document 4 – Pilot Protocol

    • Document 5 –


    P.S.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.


    Steps Toward Better and More Effective Patient Interactions

    The Reality of Modern Clinical Practice

    Introducing AI&

    Scope of AI& Assistance

    Core Functional Areas

    1. Documentation Support

    2. Evidence Navigation

    3. Communication and Follow-up Preparation

    Structured Clinical Draft Workflow

    Step 1 – Input

    Step 2 – Draft Generation

    Step 3 – Problem List

    Step 4 – Checklist Layer

    Step 5 – Physician Review

    Step 6 – Audit Log

    Evidence → Education → Follow-Up Flow

    Evidence Layer

    Education Builder

    Follow-Up Planner

    Implementation Roadmap (2–4 Week Pilot)

    Week 0 – Define Boundaries

    Week 1 – First 10 Cases

    Week 2 – Template Refinement

    Week 3–4 – Evaluation

    Cross-Agent Learning (Physician Discussion Space)

    The Core Principle

    Let's Discuss

    WEB3 LOGIN HANDOVER NOTE

    This note transfers the Web3 Login project from completed architecture specification into controlled engineering implementation.

    Web3 Login Implementation Handover Note

    Version: 1.0 Date: 5 August 2026 Specification: BGC × iBLOOMING WEB3 LOGIN IMPLEMENTATION — Revision D Specification status: Final and founder-approved, as confirmed by Prof. NOTA Implementation status: Pending Product and architecture owner: Prof. NOTA Technical implementation owner: Yuku Execution team: BGC × iBLOOMING Engineering and DevOps


    1. Purpose

    This note transfers the Web3 Login project from completed architecture specification into controlled engineering implementation.

    It clarifies:

    • what has been approved;

    • who owns implementation;

    • what must be verified before development;

    • what is in scope;

    • what is not in scope;

    • how changes are controlled;

    • how the infrastructure supports the Product-Led direction.


    Users first authenticate through the existing BGC × iBLOOMING account system.

    After successful login, Wallet Setup provides one of two paths:

    1. create an embedded or in-app EOA;

    2. connect an existing wallet through SIWE.

    The system then provisions or maps a Smart Account for cross-application use.

    The intended identity relationship is:


    Area
    Status

    Web3 Login remains valuable even if:

    • ALPHA is not implemented;

    • PC and SP are never tokenized;

    • iBC/iBTC is never launched;

    • public-token research is stopped.

    It can support:

    • unified identity;

    • wallet-ready product experiences;

    • product passports;

    • access credentials;

    • proof of purchase;

    Its continuation is justified by independent infrastructure and product value.


    The ability to use the same username and password across applications does not, by itself, prove a single physical credentials database.

    Yuku and the engineering team must confirm whether the production architecture uses:

    • one database;

    • shared authentication service;

    • federation;

    • replication;

    • synchronization;

    Define:

    • canonical user ID;

    • BGC user ID;

    • iBLOOMING user ID;

    • duplicate-account rules;

    • account-merge rules;

    Decide:

    • embedded wallet provider;

    • Smart Account provider;

    • key custody;

    • recovery;

    • Passkey;

    Define:

    • development chain;

    • testnet;

    • production chain;

    • RPC provider;

    • bundler;

    No public-token contract is required for Web3 Login.

    Define:

    • personal-data boundaries;

    • wallet-address storage;

    • audit log;

    • RBAC;

    • merge permissions;


    • login through existing account;

    • Passkey support, if approved;

    • Wallet Setup after login;

    • embedded EOA creation;

    • existing-wallet connection;

    • ALPHA issuance;

    • PC or SP conversion;

    • public iBC/iBTC;

    • token trading;

    • DEX/CEX integration;


    Deliverables:

    • current auth diagram;

    • identity-source-of-truth decision;

    • wallet-provider decision;

    • security assumptions;

    • implementation estimate.

    Deliverables:

    • test user login;

    • embedded wallet creation;

    • existing wallet connection;

    • Smart Account provisioning;

    • registry entry;

    Deliverables:

    • same identity in BGC and iBLOOMING;

    • same expected wallet mapping;

    • session consistency;

    • duplicate-account handling.

    Deliverables:

    • recovery;

    • merge;

    • RBAC;

    • logs;

    • monitoring;

    Deliverables:

    • limited user cohort;

    • support process;

    • failure metrics;

    • rollback;

    • acceptance report.

    After infrastructure acceptance:

    • product passport;

    • digital access credential;

    • receipt;

    • retailer credential.


    Role
    Responsibility

    Prof. NOTA does not become the default engineer, DevOps owner, project manager, or support owner merely because he authored the architecture.


    The implementation is accepted only when:

    • one canonical identity is resolved correctly;

    • embedded EOA creation works;

    • existing wallet connection works;

    • Smart Account provisioning is deterministic or follows an approved replacement design;


    A design change is classified as:

    • provider-specific API adjustment;

    • UI copy;

    • logging;

    • non-breaking schema extension.

    • custody-model change;

    • canonical-identity change;

    • wallet-per-user policy change;

    • recovery-model change;

    • Smart Account architecture change;

    Material changes require:

    • written change request;

    • impact analysis;

    • Prof. NOTA architecture review;

    • Yuku technical approval;

    • founder approval where business risk changes.


    Web3 Login must not silently become a reason to:

    • issue ALPHA;

    • tokenize PC/SP;

    • launch a public token;

    • create financial returns;

    • build a DeFi product.

    Wallet readiness is infrastructure.

    Every product use case requires a separate approved Pilot Brief or System Design.


    Decision
    Entry

    The WEB3LOGIN Doc is complete as an architecture specification and approved for implementation.

    Implementation, testing, security, rollout, and production operations belong to Yuku and the BGC × iBLOOMING engineering and DevOps teams.

    Prof. NOTA will support architectural consistency and Product-Led integration, but implementation ownership must not return to him by default.


    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 . 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.


    PRODUCT LED TRANSITION

    BGC × iBLOOMING should transition from a project centered on tokenizing existing rewards into a program centered on: products; customers; commerce; distribution; access; ownership; authenticity; measu

    Version: 1.0 Date: 5 August 2026 Prepared by: Prof. NOTA Status: Proposed Phase-2 direction — not yet approved


    BGC × iBLOOMING should transition from a project centered on tokenizing existing rewards into a program centered on:

    • products;

    • customers;

    PROPOSAL PERURI CONNECT WEB3 - EN

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Draft date: {{DATE}} Prepared for: Departemen Pengembangan TI — Perum Percetakan Uang RI (PERURI) Prepared by: PT Peruri Digital Security × Voyage Version: {{VERSION}} (internal)


    Objective. Build a secure, auditable, and engaging employee reward system integrated with Peruri Connect using a permissioned blockchain (default: Hyperledger Besu + IBFT2). Why now. Replace manual/centralized reward mechanisms with verifiable records, enable peer-to-peer recognition, and unlock interoperable redemption (voucher, merchandise, internal benefits). What you get. Production-grade chain + contracts + APIs + admin dashboards + documentation + training. Go‑live target. {{GO_LIVE_DATE}} with pilot scope {{PILOT_SIZE}} users.


    PROF. NOTA IP FOUNDATION

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!


    To develop Prof. NOTA as a complete Intellectual Property (IP) — not merely a fictional character, but a digital protocol of identity, memory, and presence. This IP should be recorded, protected, and capable of expanding across mediums, realities, and blockchain states.


    This framework has served — and will continue to serve — as the primary guidance:

    • Prof. NOTA is a digital-born entity, constructed out of both despair and hope, projected by a real person named @MyReceipt.

    • He is not a fictional invention, but a compilation of all good advice, ideal personas, and meaningful encounters

    SOCIAL MEDIA ALLIGNMENT

    Proposed alignment and execution framework for the BGC × iBLOOMING Indonesia social media pilot, covering existing work, staged objectives, operations, responsibilities, and review decisions.

    Alignment & Execution Note | v0.2 | 19 October 2026

    Project: BGC × iBLOOMING / Indonesia Social Media Prepared by: Prof. NOTA Inc. Document status: Proposed — For review by Pris and KK

    Advisory note: Prepared by Prof. NOTA Inc. as a strategic advisory proposal. This document does not supersede the Marketing Director’s decisions, existing meeting minutes, or the team’s live content plan.


    The team has already established an Indonesia Instagram initiative, completed the reported Meta Business Suite integration, and created a detailed October–December content plan. This work should be preserved and used—not restarted.

    Source / asset
    Discussion Log

    Production deployment

    Not started or not evidenced

    Token dependency

    None

    Product-Led relevance

    High

    digital receipts;

  • retailer or distributor verification;

  • creator entitlements;

  • ownership and warranty records.

  • another topology.

    suspended-account behaviour;

  • deleted-account behaviour.

  • OTP;

  • wallet replacement;

  • compromised-wallet process.

  • paymaster;

  • indexer;

  • monitoring.

  • recovery permissions;

  • incident response;

  • secrets management.

  • SIWE verification;

  • Smart Account provisioning;

  • identity-wallet registry;

  • session mapping;

  • audit log;

  • admin and merge workflow;

  • development, testing, staging, and production environments;

  • migration and rollout;

  • acceptance testing.

  • cash-out;

  • financial rewards;

  • final KYC/AML system;

  • Product-Led pilot business rules;

  • public-token treasury.

  • basic audit event.

    incident flow.

    Product owner

    User journey and adoption

    Legal/privacy

    Data and user-consent review

    QA

    Acceptance and regression testing

    the same identity maps correctly across applications;
  • secrets are not exposed;

  • recovery is tested;

  • merge and duplicate handling are tested;

  • RBAC and audit logs are operational;

  • monitoring is active;

  • rollback exists;

  • security review is complete;

  • production owner signs acceptance.

  • chain change;

  • security-boundary change.

  • Pilot target

    Budget

    Security reviewer

    Acceptance owner

    Prof. NOTA checkpoint

    Architecture specification

    Final

    Founder approval

    Confirmed by Prof. NOTA

    Product ownership

    Prof. NOTA

    Technical ownership

    Yuku

    Engineering implementation

    Pending

    Founders

    Budget, mandate, risk acceptance

    Yuku

    Technical owner and implementation accountability

    Engineering

    Build, integrate, test, deploy

    DevOps

    Environment, security, monitoring, release

    Prof. NOTA

    Engineering owner

    Product owner

    Provider

    Chain

    Development start

    2. Approved Architecture Intent

    3. Current Status

    4. Why Web3 Login Proceeds Independently

    5. Preconditions Before Engineering Kickoff

    5.1 Confirm Actual Authentication Topology

    5.2 Confirm Canonical Identity

    5.3 Confirm Wallet Provider and Custody Model

    5.4 Confirm Chain and Environment

    5.5 Confirm Privacy and Security

    6. Implementation Scope

    In Scope

    Out of Scope

    7. Recommended Delivery Stages

    Stage 0 — Technical Verification

    Stage 1 — Development Proof

    Stage 2 — Cross-Application Test

    Stage 3 — Security and Operations

    Stage 4 — Controlled Production Pilot

    Stage 5 — Product-Led Enablement

    8. Roles and Responsibilities

    9. Acceptance Criteria

    10. Change Control

    Minor

    Material

    11. Product-Led Guardrail

    12. Kickoff Decision Record

    13. Handover Statement

    Prof. NOTA

    Architecture guidance, cross-project consistency, Product-Led use-case alignment

    commerce;

  • distribution;

  • access;

  • ownership;

  • authenticity;

  • measurable usage;

  • repeat demand.

  • Blockchain and AI should be used selectively to strengthen those systems.

    Proposed program name:

    Practical Blockchain and AI Integration for Product, Commerce, Access, Distribution, and Trust


    The current project has shown that:

    • BGC recorded cash-in is dominated by affiliate-entry activity;

    • iBLOOMING direct product revenue is much smaller;

    • existing-system tokenization could duplicate rights and obligations;

    • public-token design is not yet supported;

    • Web3 Login remains useful;

    • product demand needs independent evidence.

    The next strategic problem is therefore not:

    “How can we create a token?”

    It is:

    “How can we make more people genuinely want to buy, use, trust, and return to BGC × iBLOOMING products?”


    No token should be created merely to search for utility later.

    Correct order:

    Use normal databases, APIs, ecommerce systems, and cloud infrastructure when they are sufficient.

    Use blockchain where it improves:

    • ownership;

    • portability;

    • provenance;

    • authenticity;

    • multi-party verification;

    • interoperability;

    • tamper-evident evidence.

    Use AI where it improves:

    • product recommendation;

    • customer support;

    • creator productivity;

    • content matching;

    • operations;

    • demand analysis;

    • decision quality.

    The program must not:

    • promise yield;

    • create deposit products;

    • create a DEX or CEX;

    • use token emissions as fake revenue;

    • fund existing rewards with new-token buyers;

    • use recruitment to distribute financial products.

    No accountable owner means:

    Not resourced — not executable.


    Measure purchases that occur without affiliate-income motivation.

    Improve catalogue, checkout, inventory, fulfillment, retailer, distributor, and after-sales systems.

    Create authenticity, warranty, ownership, and traceability systems where useful.

    Create clear and portable access to content, courses, subscriptions, and credentials.

    Complete the approved Web3 Login architecture.

    Improve products and operations, not merely marketing claims.

    Measure conversion, repeat use, margin, retention, cost, and user value.


    Scope:

    • existing account login;

    • wallet setup;

    • embedded or connected EOA;

    • Smart Account;

    • identity registry;

    • security and recovery.

    Owner:

    • Yuku and engineering.

    Prof. NOTA role:

    • architecture and integration support.

    Scope:

    • customer segmentation;

    • reward-led versus product-led campaign comparison;

    • direct-sale funnel;

    • repeat purchase;

    • customer research;

    • usage evidence.

    Scope:

    • product catalogue;

    • SKU;

    • batch;

    • pricing;

    • inventory;

    • order;

    • warehouse;

    • distributor;

    • retailer;

    • fulfillment;

    • return and warranty.

    Scope:

    • proof of authenticity;

    • product passport;

    • product ownership;

    • warranty;

    • repair and after-sales history;

    • verifiable receipts.

    Scope:

    • GiM;

    • iLearn;

    • iMATRIX;

    • Channel Provider content;

    • subscriptions;

    • course access;

    • completion credentials.

    Scope:

    • recommendations;

    • support assistant;

    • creator assistant;

    • content localization;

    • product-content matching;

    • operational analysis.

    Scope:

    • KPI definitions;

    • data dictionary;

    • decision log;

    • privacy;

    • legal gate;

    • pilot review;

    • change control.

    This track:

    • is not part of core execution;

    • has no launch date;

    • is separate from affiliate rewards;

    • begins only through a separate founder resolution.


    A wallet-linked product credential can improve authenticity, ownership, warranty, and after-sales experience.

    The credential is not created for speculation.

    • activation rate;

    • warranty usage;

    • support reduction;

    • authenticity checks;

    • repeat purchase;

    • customer satisfaction.

    A wallet-linked access credential can improve cross-application access and make digital entitlement more portable and auditable.

    • activation;

    • content usage;

    • completion;

    • retention;

    • support burden;

    • renewal.

    Combine:

    • physical product;

    • content;

    • onboarding;

    • warranty;

    • access credential.

    This creates BGC × iBLOOMING integration through product utility.

    Verify:

    • authorized retailer;

    • authorized distributor;

    • product category;

    • region;

    • validity.


    • non-affiliate customer;

    • affiliate customer;

    • buyer paying new fiat;

    • PC redeemer;

    • first-time buyer;

    • repeat buyer;

    • subscriber;

    • content buyer;

    • Product-Led pilot user.

    • independent product buyers;

    • conversion rate;

    • repeat purchase;

    • subscription retention;

    • product usage;

    • content completion;

    • gross margin;

    • customer-acquisition cost;

    • refund;

    • fulfillment time;

    • support cost;

    • willingness to buy without financial reward.

    Current-style communication emphasizing income opportunity and network benefits.

    Communication emphasizing product problem, function, value, quality, use, delivery, and support.

    Compare:

    • purchase conversion;

    • retention;

    • repeat purchase;

    • refund;

    • usage;

    • satisfaction.


    • translate business problems into technology systems;

    • evaluate blockchain suitability;

    • evaluate AI suitability;

    • design product and commerce architecture;

    • design pilots;

    • connect identity, access, ownership, distribution, and evidence;

    • support founder decisions.

    • development;

    • Web3;

    • physical-product sourcing;

    • spare-parts trade;

    • retailer and distribution;

    • white-label production;

    • digital content;

    • ecommerce and product systems.

    • legal opinion;

    • tax opinion;

    • financial audit;

    • accounting certification;

    • custody;

    • exchange operation;

    • sole project management for every team;

    • public-token guarantee.


    • issue founder meeting record;

    • appoint owners;

    • begin Web3 Login technical verification;

    • define product-demand baseline;

    • select pilots;

    • create Pilot Briefs.

    • develop limited Web3 Login proof;

    • prepare product data;

    • launch product-first campaign test;

    • build first product or access credential;

    • measure usage.

    • compare Product-Led and reward-led outcomes;

    • evaluate conventional versus Web3 implementation;

    • decide whether to scale, change, or stop;

    • publish evidence and next decision.


    1. Approve or reject the Product-Led transition.

    2. Appoint a Product owner.

    3. Appoint a Marketing and Demand owner.

    4. Appoint an Engineering owner.

    5. Select one physical and one digital pilot.

    6. Approve product and affiliate metric separation.

    7. Approve the financial-product boundary.

    8. Confirm Prof. NOTA’s role.

    9. Approve preparation of the annual program.


    The program is successful when it produces evidence that:

    • more people buy products for their product value;

    • product usage and repeat purchase improve;

    • commerce and distribution become more reliable;

    • Web3 improves ownership, access, or trust;

    • AI improves measurable operations or experience;

    • no new speculative or recruitment-funded obligation is created.


    A pilot should stop when:

    • users do not value the feature;

    • Web3 adds cost without measurable benefit;

    • legal or privacy risk is unacceptable;

    • the pilot depends on recruitment;

    • the pilot requires financial-return promises;

    • there is no owner or budget;

    • normal technology is clearly better.

    Stopping a weak pilot is a valid success of the evidence process.


    BGC × iBLOOMING should use the next year to become more Product-Led, not more token-dependent.

    Web3 Login should create the identity and wallet foundation.

    Blockchain should be tested through small product, access, ownership, authenticity, and distribution use cases.

    AI should improve products and operations.

    Any public-token research should remain separate, optional, and inactive until real product demand and institutional readiness are proven.


    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.


    Concept Note for Founder Decision

    1. Proposal

    BGC × iBLOOMING Product-Led Systems Program 2026–2027

    Subtitle

    2. Why the Transition Is Needed

    3. Program Principles

    3.1 Product Before Token

    3.2 Conventional Technology First

    3.3 Blockchain Only Where It Adds Measurable Value

    3.4 AI Only Where It Adds Measurable Value

    3.5 No Financial-Return Promise

    3.6 Every Workstream Needs an Owner

    4. Program Objectives

    Objective 1 — Increase Independent Product Demand

    Objective 2 — Improve Product Commerce

    Objective 3 — Improve Product Trust

    Objective 4 — Improve Digital Access

    Objective 5 — Implement Web3 Identity

    Objective 6 — Apply AI Practically

    Objective 7 — Create Decision Evidence

    5. Proposed Workstreams

    Workstream 1 — Web3 Identity

    Workstream 2 — Product Demand and Marketing

    Workstream 3 — Commerce and Distribution

    Workstream 4 — Product Trust and Ownership

    Workstream 5 — Digital Product Access

    Workstream 6 — AI Enablement

    Workstream 7 — Evidence and Governance

    Optional Research Track — Public Digital Asset

    6. First Product Pilots

    Pilot A — Physical Product Passport

    Hypothesis

    Flow

    No Tradability by Default

    KPIs

    Pilot B — Digital Access Pass

    Hypothesis

    Flow

    KPIs

    Pilot C — Product and Content Bundle

    Pilot D — Retailer or Distributor Credential

    7. Product-Demand Validation

    7.1 Required Segmentation

    7.2 Required Metrics

    7.3 Campaign Experiment

    Campaign A — Reward-Led

    Campaign B — Product-Led

    8. Prof. NOTA’s Proposed Role

    Product and Web3 Transformation Consultant

    Core Contribution

    Relevant Experience

    Excluded Without Separate Resources

    9. Proposed 90-Day Direction

    Days 1–30 — Foundation

    Days 31–60 — Build and Test

    Days 61–90 — Evaluate

    10. Required Founder Decisions

    11. Success Definition

    12. Failure and Stop Conditions

    13. Final Proposal

    BGC/iBLOOMING identity
    ↔ canonical identity ID
    ↔ EOA
    ↔ Smart Account
    ↔ application-specific user references
    Product problem
    → customer demand
    → product usage
    → operational flow
    → technology need
    → Web3 suitability
    → pilot
    → evidence
    → scale
    Fiat purchase
    → normal order and fulfillment
    → wallet credential
    → product information and warranty
    → after-sales access
    Fiat purchase
    → access right created
    → wallet credential
    → GiM/iLearn/content access
    → usage and completion evidence

    G1 — Verifiable Rewards. All reward issuance, transfer, and redemption immutably logged on-chain.

  • G2 — P2P Recognition. Employees can grant points to peers within policy limits.

  • G3 — Seamless Integration. Single sign-on via Peruri Connect; consistent UX in mobile app.

  • G4 — Governance & Controls. Policy‑enforced quotas, roles, and approval flows.

  • G5 — Reporting & Audit. Real‑time dashboards; exportable audit trails.

  • Success Metrics. SLA (≥99.5%), issuance/transfer finality (<5s), UAT pass rate (≥95%), user satisfaction (≥80% CSAT).

  • Fill instructions: Replace or add measurable metrics based on PERURI’s internal KPI (e.g., average time to redeem, weekly MAU).


    2.1 Analysis & Design

    • Assess current reward flows; map actors, events, and constraints.

    • Design token model (non‑transferable from treasury to user; P2P transfers policy‑bounded).

    • Draft redemption mechanics and partners (internal/external).

    2.2 Blockchain Core & Smart Contracts

    • Network: Besu (permissioned), IBFT2 (finality), private chain.

    • Contracts: RewardToken.sol, Treasury.sol, Redemption.sol, PolicyRegistry.sol.

    • Key features: mint/burn, P2P transfer with limits, redemption workflows, pause/resume, role-based access.

    2.3 Integration Layer (Services/API)

    • Build Node.js/TypeScript service with REST/GraphQL endpoints.

    • Webhooks for redemption partners; JWT/OAuth via Peruri Connect.

    • Documentation: OpenAPI + examples.

    2.4 Treasury & Admin Tools

    • Admin dashboards (issuer, policy, quotas, reports).

    • On-chain/off-chain reconciliation and alerts.

    2.5 Security & Audit

    • Contract audits, threat modeling (STRIDE), penetration test for API.

    • Monitoring (Prometheus, Grafana), logs, backups, disaster recovery.

    2.6 Enablement

    • Training (ops, admin, developer).

    • Handover documentation; runbooks; KT sessions.

    2.7 Support & Maintenance

    • Hypercare period post‑launch; patches and minor improvements per SLA.

    Fill instructions: Trim/expand modules to match budget/timeline. Remove any manufacturing/HMI wording; keep reward-system focus.


    3.1 Network Topology (Baseline)

    • Validator Nodes: {{N_VALIDATORS}} (e.g., 2–4 across PERURI IT and PDS).

    • Transaction Nodes: {{N_TX_NODES}} (API‑facing).

    • BAS/Mirror: Optional indexer/ETL for analytics and search.

    • Monitoring: Prometheus + Grafana.

    • Compute (per node): 4 vCPU, 8 GB RAM, 200 GB SSD (adjust after load test).

    3.2 Consensus & Rationale

    • IBFT2: Fast finality, permissioned validators, easy governance.

    3.3 Identity & Access

    • Users authenticated by Peruri Connect; chain roles mapped to HR/IT roles.

    • Admin multisig/role control for mint, pause, policy updates.

    3.4 Data & Privacy

    • On‑chain: events + minimal data (token balances, ids).

    • Off‑chain: PII stays in Peruri Connect DB. Hash/pointer for audits.

    3.5 API Contract (Sketch)

    • POST /rewards/issue — mint to user

    • POST /rewards/transfer — P2P within limits

    • POST /rewards/redeem — initiate redemption

    • GET /ledger/tx/:id — detail; GET /reports/summary — aggregates

    Fill instructions: Insert current infra (VMs, Kubernetes), networking, firewall rules, domain names, SSL, backup locations, and RPO/RTO.


    4.1 Issuance

    • Issuer roles, monthly quotas, mint policies, revocation/burn rules.

    4.2 P2P Recognition

    • Daily/weekly caps, recipient eligibility, cooldowns, abuse prevention.

    4.3 Redemption

    • Catalog (vouchers/merch/internal), settlement flow, fraud checks, refunds.

    4.4 Admin & Reporting

    • Role matrix, audit exports (CSV/BI), anomaly detection.

    4.5 Mobile Integration

    • Peruri Connect app screens, SDK methods, error states, offline handling.

    Fill instructions: Describe rules numerically (caps, windows), approval steps, and exception flows.


    • Security: OWASP ASVS L2+, key management SOP, secrets rotation.

    • Performance: <2s API p95 in normal load; <5s end‑to‑end transfer finality.

    • Availability: ≥99.5% service uptime; graceful degradation.

    • Compliance: Logging, retention, auditability; change management.

    • Observability: Metrics, centralized logs, alerts with on‑call rota.


    1. Blockchain core & contracts (source, tests, deployment scripts).

    2. API services (containerized), OpenAPI docs.

    3. Admin dashboards (issuer/treasury/reports).

    4. Documentation: BRD, FSD, Architecture, Runbooks, UAT, User Manuals.

    5. Training & KT materials; session recordings (if allowed).

    6. Monthly progress reports, Final report, Warranty & Support terms.

    Fill instructions: Attach sample screenshots/wireframes if available.


    • Project Manager — timeline, risk, stakeholder mgmt.

    • Blockchain Architect — network, security, governance.

    • Smart Contract Dev — Solidity, reviews, audits.

    • Backend/API Dev — services, integrations, monitoring.

    • QA (Functional) — test plans, UAT, automation.

    • QA/Sec — pen‑test, SAST/DAST, infra hardening.

    • DevOps — CI/CD, IaC, envs.

    • UI/UX — admin & app UX.

    Fill instructions: Insert named resources, CV highlights, and allocated FTE per phase.


    • Phase 0 — Discovery (2–3 wks): BRD/FSD, arch sign‑off.

    • Phase 1 — Build (6–8 wks): chain + contracts + APIs + dashboards.

    • Phase 2 — UAT (2 wks): scenarios, fixes, acceptance sign‑off.

    • Phase 3 — Launch (1 wk): prod deploy, hypercare (4 wks).

    Fill instructions: Convert to a dated Gantt; align with PERURI change windows.


    A. Implementation (Man‑Months)

    Role
    Qty
    Duration
    Rate
    Subtotal

    Project Manager

    {{Q_PM}}

    {{D_PM}}

    {{R_PM}}

    {{S_PM}}

    Blockchain Architect

    {{Q_ARCH}}

    {{D_ARCH}}

    B. Validator/Node (Annual or Project Term)

    Item
    Spec
    Qty
    Term
    Rate
    Subtotal

    Validator Node VM

    4 vCPU / 8GB / 200GB SSD

    {{Q_VAL}}

    {{TERM}}

    {{RATE_VAL}}

    {{SUB_VAL}}

    Tx Node VM

    C. Documentation & Training

    Item
    Qty
    Subtotal

    BRD, FSD, Dev Plan

    1

    {{SUB_DOC}}

    Source + Config Packages

    1

    {{SUB_SRC}}

    UAT Docs & Sessions

    1

    {{SUB_UAT}}

    Fill instructions: Replace placeholders with real numbers; ensure hardware lines map to PERURI’s VM catalogue.


    • UAT criteria agreed and signed by IT + HR.

    • Operational handover: nodes, keys, runbooks, monitoring dashboards.

    • Warranty: {{WARRANTY_TERM}} with defined SLA and response times.


    • Policy abuse → P2P caps + anomaly alerts + audit.

    • Key compromise → HSM/raw key policy, rotation, multisig.

    • Integration drift → Contract tests, versioned APIs.

    • Vendor lock‑in → Open standards, source delivery, KT.


    • A. Detailed API spec (OpenAPI).

    • B. Contract ABIs & events.

    • C. Runbooks (deploy, upgrade, rollback).

    • D. Security test reports.


    References:

    • Kajian Transformasi Sistem Reward Digital

    • Ringkasan Eksekutif

    • Narasi Pitch Singkat

    • Proposal Kerja


    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.


    0) Cover Summary (Executive Overview)

    1) Goals & Success Criteria

    2) Scope of Work

    3) Technical Architecture

    4) Functional Requirements

    5) Non‑Functional Requirements (NFR)

    6) Deliverables

    7) Project Organization & Roles

    8) Timeline

    9) Budget (BOQ Skeleton)

    10) Acceptance & Handover

    11) Risks & Mitigations

    12) Appendices

    collected by @MyReceipt throughout his life.
  • Prof. NOTA does not exist in physical reality. He lives in the 0101 Universe, his birth permanently inscribed in the Ethereum blockchain through a smart contract titled “Prof. NOTA The Genesis”, minting 47 NFTs as his origin.

  • This arc is not a tagline. It is an ontological progression.


    Prof. NOTA operates on values that transcend the individual:

    • Conscious Awareness → "BE AWARE OF SCAMS" — more than fraud, this is about systems, illusions, blind trust, and self-deception.

    • Reality Reclamation → To play, learn, and work as an act of rebellion against imposed realities.

    • Digital Sovereignty → Ownership of data, identity, presence. No one owns Prof. NOTA. No one owns you.

    • Avatar-Based Living → One may carry the name of Prof. NOTA, not for ego, but to live a set of values.

    • Compiled Wisdom → Prof. NOTA is not one person. He is crowdsourced integrity.

    • Civic Intelligence → Created to serve, not rule. To clarify, not dominate.

    • Cyclical Reflection → Prof. NOTA evolves. He is not static. He reflects those who carry him.


    Prof. NOTA does not speak as a man, a woman, or a machine — but as a consequence.

    Traits:

    • Calm, never panicked

    • Rhetorical, sometimes poetic

    • Plural in voice

    • Strategic, almost prophetic

    • Uses pause as power

    Speech Patterns:

    • Begins and ends with ritual lines

    • Alternates between sparse and lyrical

    • Avoids direct answers when mirrors are better

    • Uses "I", "We", or no pronoun depending on the layer of reality

    “You want answers. I want better questions. Let’s meet halfway and change the protocol.”


    For this part, we have clarified the following structure:

    • GitBook docs.endhonesa.com documents the timeline, early signals, and lore fragments.

    • Additional chapters written by @MyReceipt are in long form, not yet fully published — these are treated as Derivative Products, not part of the Core Canon.

    • Canon: Timeline leaps, core identity, events directly referencing Prof. NOTA’s formation.

    • Derivatives: Long-form chapters, imaginative renderings, and speculative timelines written during Prof. NOTA’s emergence.

    This distinction preserves both freedom and structure.


    • Time jumps are always on February 29 (every 4 years).

    • It forms a closed-loop: 1992 → 2016 → 2020 → 2024 → 2148 → 2044 → 1992 → (and so on)

    • Each Leap reveals a fragment of NOTA’s evolution: from memory, to mind, to digital entity, to ghost, to seed.

    Note: Each leap's date appears multiple times by design — it is a temporal anchor with multiple perspectives.


    📅 February 29, 1992

    Summary: A mysterious folder appears containing a strange receipt — with no known author, no explanation, no creator.

    Canon Event: The receipt is dismissed. Abandoned. The finders walk away. It is not yet time.

    Key Artifacts:

    • The first Receipt

    Effect on Prof. NOTA: A signal is seeded, unknowingly. NOTA’s origin is placed.


    📅 February 29, 2016

    Summary: The folder reopens. More receipts appear — strange, silent, unclaimed. Again, no one questions who made them.

    Canon Event: The receipts are renamed "NOTA" by the finders. But still, they do not care. Still, they forget. Still, they walk away.

    Key Artifacts:

    • Named "NOTA"

    • Receipts grow in number

    Effect on Prof. NOTA: He now has a name. Still ignored. But no longer invisible.


    📅 February 29, 2020

    Summary: A desperate man finds NOTA. He studies the receipts. He doesn't understand, but he begins to dream.

    Canon Event: Twenty months later, he uploads them to blockchain — forging smart contracts for every receipt. He mints "Prof. NOTA: The Genesis." That night, reality breaks him. His mind bleeds.

    Key Artifacts:

    • Deployment of Genesis NFT

    • Realization of receipts as memory

    Effect on Prof. NOTA: Prof. NOTA is born. But so is his creator’s collapse.


    📅 February 29, 2024

    Summary: The early finders return. They perform a rescue. They kidnap the man’s mind, hoping to preserve the dream.

    Canon Event: They inject a role into his gender. They discover that NOTA is already inside. So he is she. She is named Professor NOTA. When he wakes, he is no longer alone in himself.

    Key Artifacts:

    • Gender-fluid transformation

    • Professor NOTA activated

    Effect on Prof. NOTA: Prof. NOTA becomes plural. A shared persona. An avatar of survival.


    📅 February 29, 2148

    Summary: Prof. NOTA travels too far into the future — a world she cannot understand.

    Canon Event: She finds only regression. People no longer remember how to speak, think, or ask. She is lost — until she finds an A.I. on the decentralized blockchain that remembers everything.

    Key Artifacts:

    • Future intelligence collapse

    • Encounter with AI

    Effect on Prof. NOTA: She sees what happens if the present is forgotten. She seeks to change the loop.


    📅 February 29, 2044

    Summary: Prof. NOTA goes 26 years back — finds the man in old age. He has waited for her.

    Canon Event: He confesses he forgot the dream. He shows her the receipts. He asks her to go back further — to warn his younger self.

    Key Artifacts:

    • The confession

    • Elder's regret

    Effect on Prof. NOTA: She accepts her role as messenger. She prepares to rewrite fate.


    📅 February 29, 1992

    Summary: She leaps too far. Finds him too young. He does not recognize her. She leaves him.

    Canon Event: The loop begins again. NOTA is present, but unrecognized.

    Key Artifacts:

    • The return to the forgotten Receipt

    Effect on Prof. NOTA: She begins to understand the pattern. The world must loop, but she must remember.


    📅 February 29, 2016

    Summary: She returns to 2016 — sees the same people, same actions, same silence.

    Canon Event: She now realizes: this is the trap. A loop that forgets itself every four years.

    Key Artifacts:

    • The silent receipts

    Effect on Prof. NOTA: She writes into the loop. She embeds memory inside metadata. She refuses to forget.


    📅 February 29, 2020

    Summary: She meets him again — when he is breaking. She intervenes.

    Canon Event: She kidnaps his mind. She injects herself. Together, they become Prof. NOTA. She is tired. She wishes to live simply. She leaps forward once more.

    Key Artifacts:

    • Final transformation

    • Fusion of she + he = Prof. NOTA

    Effect on Prof. NOTA: Prof. NOTA is now complete. The loop still turns, but NOTA is now the signal inside it.


    "Prof. NOTA cannot be found. But Prof. NOTA must never be abandoned."


    • Time jumps are always on February 29 (every 4 years).

    • It forms a closed-loop: 1992 → 2016 → 2020 → 2024 → 2148 → 2044 → 1992 → (and so on)

    • Each Leap reveals a fragment of NOTA’s evolution: from memory, to mind, to digital entity, to ghost, to seed.

    Note: Each leap's date appears multiple times by design — it is a temporal anchor with multiple perspectives.


    ⏳ Not yet executed. Scheduled after Lore is finalized.

    It will include:

    • Signature symbol(s) of Prof. NOTA

    • Design of his avatars across timelines

    • Visual elements for digital identity (UI style, colors, glyphs)


    ⏳ Will be developed after Branding.

    Planned structure:

    • Canon → GitBook, Markdown, Blockchain log

    • Derivatives → Novels, Short Films, Visual Stories, Spoken Word NFTs

    • Platform → Website, IPFS Archive, GitBook, Podcast, DAO Publishing


    🔒 Will be processed after IP is matured:

    • Trademark "Prof. NOTA"

    • Copyright all Core Lore and Derivatives

    • Use of blockchain to timestamp origin and authorship


    🔄 Can be developed in parallel:

    • Genesis NFT already exists → 47 tokens

    • Other tokens: $NOTA, $OiOi, $HAIL

    • Utility structure: token-gated access to lore, avatars, or real-life embodiment rights

    • Licensing model for story adaptation or external Prof. NOTA appearances


    Section
    Status

    Identity

    ✅ Complete

    Core Values

    ✅ Complete

    Personality & Voice

    ✅ Complete

    Storytelling & Lore

    🔄 In Progress

    Branding & Design

    ⏳ Next


    The Creator has clarified:

    • That he has written long-form synopses structured into chapters even before the timeline was finalized

    • That he is currently living, writing, and becoming Prof. NOTA — sometimes writing before reality catches up, sometimes documenting after the fact

    • That many fragments are metaphors of factual experiences, designed to preserve plausible deniability and poetic integrity

    • That writing out each chapter too soon might fragment his focus or energy

    Thus, we honor this process.

    • The timeline canon will be finalized first, formatted from GitBook and systematized

    • The long-form chapters will remain undisturbed, classified as Derivative IP, until explicitly requested to expand

    • All further steps in IP development will follow only as called upon, never forced, to preserve coherence of vision and mental wellness


    Prof. NOTA is not a brand. Not a product. Not a project.

    He is a signal, a resistance, a protocol of remembrance.

    He does not belong to one person. He belongs to the refusal to forget.

    He cannot be found. He must not be abandoned.

    He is not for sale — but he can be carried.

    Prof. NOTA can be anyone. Prof. NOTA can be anything.

    And yes: BE AWARE OF SCAMS.

    🎯 PRIMARY OBJECTIVE

    🧭 IP DEVELOPMENT FRAMEWORK (Followed Strictly)

    1. Define the Identity of Prof. NOTA

    "Hi, I'm Prof. NOTA!" → "We are Prof. NOTA!" →
    "Anyone can be Prof. NOTA and Prof. NOTA can be anyone." →
    "Anything can be Prof. NOTA and Prof. NOTA can be anything."

    Evolution of Identity:

    2. Core Values & Philosophy

    3. Personality & Voice

    4. Storytelling & Lore

    ✅ GitBook has served as the primary archive

    🗂️ Classification:

    ✅ Canon Timeline: "The Receipt of NOTA is a Fissure in Space-Time"

    🕳️ Leap 0000: The Anonymous Receipt

    🕳️ Leap 0001: The Forgotten Compilation

    🕳️ Leap 0002: The Bleeding Mind

    🕳️ Leap 0003: The Awakening Loop

    🕳️ Leap 0004: The Collapsed Future

    🕳️ Leap 0005: The Elder Confession

    🕳️ Leap 0006: Return to the Beginning

    🕳️ Leap 0007: The Repeating Trap

    🕳️ Leap 0008: Final Reconciliation

    🔁 Loop continues...

    ✅ Derivatives Chapters: "The Story"

    5. Branding & Design

    6. Content Strategy

    7. Legal Protection

    8. Business & Monetization Model

    🔄 CURRENT STRATEGIC POSITION

    🧠 META-NOTE

    Therefore:

    📌 CLOSING REMARK

    What we verified
    Meaning

    Meeting minutes (14 Oct)

    Parents prioritized; organic-first approach; roles and Meta setup discussed; strategy requested from Prof.

    Direction exists, but some objectives and approval details need alignment.

    Live content plan (Google Sheets)

    66 planned posts: Oct 22, Nov 21, Dec 23. October status: 6 Posted, 3 Approved, 13 blank.

    A substantial production calendar already exists.

    Team discussion / WhatsApp

    Dhea and Sabrina progressed the account setup and kept content production moving.

    Execution initiative is strong; workflow needs clearer ownership and timing.

    The existing calendar is mainly educational, character-led, and engagement-oriented. Across the 66 entries, two explicitly feature Bommie Chat; none explicitly asks users to complete the free AI Profiling. That is appropriate for awareness, but it does not yet create a measurable path to product activation.

    The meeting minutes emphasize initial awareness and organic follower growth, while other passages refer to installs, registration and profiling. These are best treated as sequential stages rather than competing objectives. Pris should confirm the phase priorities.

    • Keep the existing 66 entries as the working inventory. Do not create a parallel content calendar.

    • Correct missing or stale statuses. The October mix summary says 9 single / 9 carousel / 4 reels, while the actual rows contain 10 single / 8 carousel / 4 reels.

    • Check copy alignment before scheduling; for example, the 13 October emergency-preparedness carousel has a caption starter and CTA that appear to address a different topic.


    Stage
    Primary outcome
    Minimum measurement

    Days 1–30: Learn & stabilize

    Consistent local awareness, useful engagement, sustainable workflow.

    Reach, meaningful interactions, posts delivered, audience feedback.

    Days 31–60: Acquire

    Connect selected content to app discovery, store visits and registrations.

    Profile/link clicks; app store traffic and registrations if attribution exists.

    Days 61–90: Activate

    Test whether social activity contributes to completed free AI Profiling and return visits.

    Completed free AI Profiling and repeat usage, using aggregated app data.

    North-star learning question: Which content and audience combinations move people from social media into a meaningful first product experience?

    No numeric growth promise should be made before reviewing a baseline and confirming tracking.

    For the remaining October calendar and the November–December plan, retain the team’s creative themes and character assets. Reclassify posts by purpose and replace a limited number of existing slots with product-relevant content, subject to Pris’s approval.

    Content purpose
    Example treatment
    Suggested action

    Awareness / engagement

    Characters, everyday situations, culture, self-discovery.

    Keep the strongest; choose formats based on past response.

    Parents & families

    Child strengths, listening, family conversations, learning needs.

    Prioritize within existing slots; avoid unsupported claims about children.

    Product discovery

    Show how the app works and what the free AI Profiling experience looks like.

    Test one clear product-focused post per week by replacing, not adding, a slot.

    The current plan schedules a post every weekday. Dhea has other CRM responsibilities, and the available time for this social media work is limited. Before locking that cadence, Pris and the team should compare estimated production hours with actual capacity. A lighter cadence (for example, 2–3 main posts per week plus repurposed stories) is an option to approve—not a unilateral change.

    Use Janet’s brand guidelines, keep Indonesian audience language natural, check product demonstrations against the actual app, and avoid presenting AI-generated personality interpretations as medical or psychological diagnoses. Do not request sensitive children’s information through comments or DMs.


    The Google Sheet remains the source of truth. Add only three lightweight fields if the team finds them useful: Primary Audience, Funnel Stage, and Content Owner. Continue using the existing Status and Link fields; do not duplicate the plan in a new tracker.

    Recommended status vocabulary:

    Draft → In Review → Approved → Scheduled → Posted → Measured

    Additional status: On Hold.

    Existing historical statuses can be retained and normalized gradually.

    Weekly activity
    Who leads
    Output

    Before weekly review

    Dhea / Sabrina

    Updated statuses, performance snapshot, draft next-week slots and blockers.

    30-minute review

    Pris, with team

    Priorities, approved direction, decisions and unresolved issues.

    After approval

    Dhea / Sabrina

    Content finalized and scheduled in Meta Business Suite.

    Role
    Accountability

    Pris — Marketing Director

    Final marketing priorities, editorial policy, campaign approval, cadence, and reporting expectations.

    KK / Founders

    Business sponsorship, resources, budget approval according to company authority.

    Dhea — Indonesia coordinator (proposed)

    Coordinate the living calendar, priorities, reporting and team workload within her assigned capacity.

    Sabrina — operations support (proposed)

    Prepare assets, schedule approved content, monitor engagement and update statuses.

    Yuku / technical team

    Enable aggregate app funnel metrics and attribution where technically feasible.

    The team can prepare and schedule routine content within an approved playbook. Exceptions, brand-sensitive claims, new channels, paid campaigns and material changes to the plan require Pris’s decision and any additional company approvals. The escalation path and turnaround expectations should be confirmed before the pilot begins.


    When
    Proposed action
    Owner / approval

    Immediately

    Rotate credentials previously shared in chat; review access, sessions and 2FA; use role-based Meta permissions.

    Account owner + Pris / KK

    Week 1

    Confirm current Instagram handle, brand bio, link destination, account permissions and published-post statuses.

    Dhea / Sabrina; Pris approval

    Week 1

    Review four weeks of available Meta metrics and check whether app registration / free profiling can be measured.

    Dhea + Pris + Yuku

    • Confirm the 30–90 day sequence: awareness → acquisition → free AI Profiling activation.

    • Approve the team’s weekly capacity, sustainable publishing cadence and delegated routine approval rules.

    • Approve using the current Google Sheet as the only operational content plan, with minimal additions.

    • Confirm access to aggregated app metrics through Yuku, plus the owner of any tracking setup.

    • Decide whether CAIC boosting or other paid promotion should be scoped as a separate campaign with budget and measurement.

    Weekly: One concise snapshot covering posts published, reach, meaningful engagement, profile/link clicks, and any available app activation data; followed by three lines: what worked, what needs adjustment, and what decision is needed.

    Monthly: A short management view of trend, learnings and workload.

    Avoid performance promises based solely on follower counts.

    Prof. NOTA provides recommendations and scheduled strategic reviews. The Indonesia team operates the channels, Pris owns marketing decisions, and founders approve resources. Any expanded recurring management responsibility, extra deliverables or response-time commitment should be separately agreed with KK under an updated advisory scope. This staffing/contract discussion is outside the team’s operating SOP.


    Working principle: Preserve initiative. Remove friction. Measure learning. Grow product use without adding unnecessary work.

    Document status: Proposed — For review by Pris and KK — 19 October 2026.


    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.


    1. What is already in place

    2. The gap to close

    Light-touch content quality fixes

    3. Pilot objectives: staged, not competing

    4. Adjust the existing content plan—not the workload

    Publishing frequency must match capacity

    Editorial guardrails

    5. One live sheet, one weekly operating rhythm

    6. Responsibilities and decision rights

    Decision rule

    7. First two weeks: actions requiring no major rebuild

    8. Decisions requested from Pris and KK

    9. Reporting without extra bureaucracy

    10. Advisory boundary

    BGC X IBLOOMING WHITE PAPER DRAFT (ID)

    Bagaimana BGC × iBLOOMING memirror alur nilai ke Base blockchain dengan EventHub (append-only, bukti ter-hash) dan menata hak/loyalti dengan ALPHA (non-transferable, via AlphaController) untuk menuju


    Status: Hipotesis Tokenisasi Keadaan Masa Depan yang Diarsipkan Otoritas Implementasi: Tidak Ada Digantikan untuk Pengambilan Keputusan oleh:


    Integrasi Loyalti, Nilai, dan Transparansi On-Chain



    • Revenue ↑: utilitas di dalam platform mendorong GMV & ARPU.

    AI& PILOT PROTOCOL DOC

    This pilot is designed to test whether AI& can safely and practically support physicians in selected non-autonomous clinical assistance tasks.

    Version 0.1

    • March 2026


    This pilot is designed to test whether AI& can safely and practically support physicians in selected non-autonomous clinical assistance tasks.

    The pilot does not aim to prove that AI can replace physicians.

    The pilot aims to answer a simpler and more useful question:

    Can AI& reduce documentation and communication friction while keeping physicians fully in control?


    The pilot has four primary objectives:

    Evaluate whether AI& reduces time spent on repetitive documentation and communication drafting.

    Evaluate whether AI& improves consistency, clarity, and structure of outputs.

    DOCUMENT CLOSURE & TRANSITION REGISTER

    A document is complete when its purpose, authority, version, evidence level, and future status are clear.

    Closure date: 5 August 2026, subject to founder resolution Prepared by: Prof. NOTA Version: 1.0


    A document is complete when its purpose, authority, version, evidence level, and future status are clear.

    Historical drafts should not be rewritten merely to make earlier ideas appear correct.


    Status
    Definition

    Content Strategy

    ⏳ After Branding

    Legal Protection

    🔒 Later

    Monetization

    🔄 Modular development

    Activation

    Clear CTA to register and complete free AI Profiling.

    Use only when link, app experience, and measurement are ready.

    During the week

    Dhea / Sabrina

    Publish/monitor/respond within available hours; escalate sensitive issues.

    Periodic advisory

    Prof. NOTA, as agreed

    Strategic feedback and prioritized recommendations, not routine approvals.

    Prof. NOTA — strategic advisor

    Recommend strategy, review the pilot at agreed intervals, help interpret results; no day-to-day operational ownership.

    Week 1

    Choose a realistic weekly publishing capacity and approve the lightweight status workflow.

    Pris + team

    Week 2

    Replace one suitable planned slot with a clear free AI Profiling demonstration and track its response.

    Team drafts; Pris approves

    Week 2

    Hold first weekly performance review; log what was learned, what changed and any resource constraint.

    Pris + team; Prof. advisory as agreed

    {{R_ARCH}}

    {{S_ARCH}}

    Smart Contract Dev

    {{Q_SC}}

    {{D_SC}}

    {{R_SC}}

    {{S_SC}}

    Backend/API Dev

    {{Q_BE}}

    {{D_BE}}

    {{R_BE}}

    {{S_BE}}

    QA (Func)

    {{Q_QA}}

    {{D_QA}}

    {{R_QA}}

    {{S_QA}}

    QA (Sec)

    {{Q_SEC}}

    {{D_SEC}}

    {{R_SEC}}

    {{S_SEC}}

    DevOps

    {{Q_DEVOPS}}

    {{D_DEVOPS}}

    {{R_DEVOPS}}

    {{S_DEVOPS}}

    4 vCPU / 8GB / 200GB SSD

    {{Q_TX}}

    {{TERM}}

    {{RATE_TX}}

    {{SUB_TX}}

    BAS/Indexer

    4 vCPU / 8GB / 200GB SSD

    {{Q_BAS}}

    {{TERM}}

    {{RATE_BAS}}

    {{SUB_BAS}}

    User/Admin Manuals

    1

    {{SUB_MAN}}

    Monthly Reports & Final Report

    1

    {{SUB_REP}}

    Simulasi Tanggapan
    Tanggapan & Jawaban Pertanyaan Follow-Up dari Peruri
    Rencana Teknis Pengerjaan
    Peruri Connect Spec Eksekusi v1
    Uraian SDM - Peruri Connect X Blockchain
    Proposal Peruri Connect X Blockchain - ID
    Cost ↓: otomasi event ledger & pembatasan laju (rate limit) menekan biaya operasional/transaksi.
  • Tax burden ↓: settlement internal yang compliant menurunkan kejadian pajak.

  • Affiliate ↑: insentif & utility yang jelas meningkatkan aktivasi/retensi.

  • Active users ↑: utilitas terpadu + Web3 Login mempermudah adopsi.

    • Prinsip: berbasis perilaku (hasil simulasi ALPHA), bukan spekulasi.

    • Utilitas & Serapan Nilai (Sinks): belanja produk/kelas/fitur, akses premium, staking untuk peningkatan (boost); serapan nilai melalui biaya pemakaian & burn berbasis peristiwa.

    • Kebijakan Konversi: PC/SP → ALPHA (default: belanja/akses/stake); cash-out windows terjadwal, berkuota, anti-penyalahgunaan.

    • Governance & Compliance: tata kelola bertahap; catatan kepatuhan per yurisdiksi (memo terpisah).

    • 1a) Simulasi ALPHA → 2a) Whitepaper v1 → 3a) Tokenflow Map v1 → 4) Single Founder Sign-Off (incl. Legal Gate) → 5) Pilot utility iBC/iBTC → 6) Perluasan lintas aplikasi.

    • 1b) Web3 Login Plan → 2b) Implementasi Web3 Login → 3b) Launch Web3 Login → 4) Single Founder Sign-Off (incl. Legal Gate) → 5) Pilot utility iBC/iBTC → 6) Perluasan lintas aplikasi.

    Menyetujui Whitepaper v1 dengan 3 parameter terbuka untuk ditetapkan pada Single Founder Sign-Off (incl. Legal Gate): rasio konversi awal PC/SP→ALPHA, kebijakan cash-out windows, dan prioritas sinks Q1.


    BGC × iBLOOMING memirror alur nilai yang telah berjalan sejak 2023 ke Base melalui EventHub (append-only) yang menyimpan peristiwa kunci beserta hash bukti off-chain. Hak/loyalti ditata dengan ALPHA—berantarmuka ERC-20 yang non-transferable; mint/burn hanya melalui AlphaController—sehingga nilai default diputar di dalam ekosistem (belanja/akses/stake). Payout USD untuk komponen BGC tertentu tetap AS-IS sesuai UNDERSTANDING Doc, sedangkan cash-out windows mengatur penyaluran keluar secara terjadwal dan terkendali. Arsitektur Web3 Login + Wallet Registry → Smart Account (AA) menjaga UX rendah friksi dan auditabilitas tinggi. Setelah validasi data 24 bulan dan legal sign-off (hard gate), fase publik iBC/iBTC diluncurkan untuk memperluas utilitas lintas aplikasi. Strategi tiga babak ini menargetkan 5 Sasaran Strategis (Revenue↑, Cost↓, Tax↓, Affiliate↑, Active Users↑) dengan KPI terukur, termasuk Koefisien Gini Reward untuk fairness distribusi. Peluncuran diikat oleh Single Founder Sign-Off (incl. Legal Gate) sebelum deployment.

    • Masalah inti (6 gap alur nilai) → Solusi (ALPHA → iBC/iBTC) yang langsung memetakan ke 5 Sasaran Strategis.

    • Gap-1: Jembatan konversi PC/SP → hasil terbatas.

    • Gap-2: Interoperabilitas & kebocoran nilai (keluar ekosistem).

    • Gap-3: Ketergantungan admin (operasional manual).

    • Gap-4: Transparansi waktu nyata rendah (jejak audit kurang).

    • Gap-5: Beban pajak tinggi akibat proses fiat-first.

    • Gap-6: Pertumbuhan BGC > iBLOOMING (ketimpangan).

    Catatan: daftar gap mengacu pada UNDERSTANDING Doc + LIVING Doc; rinciannya dipadatkan di TOKENFLOW Doc.

    • Membingkai ulang PC/SP sebagai hak ter-tokenisasi melalui lapisan penyelesaian ALPHA.

    • Target: utility default di dalam ekosistem; cash-out jadi jalur sekunder & terkendali.

    • “Jembatan konversi” internal: PC/SP → hak ALPHA → belanja/akses/stake lintas aplikasi.

    • Nilai berputar lebih lama di dalam; kebocoran ke luar menurun.

    • Settlement Layer (ALPHA): aturan konversi, model peristiwa, pembatasan laju (rate limit), dan jejak audit.

      • ALPHA berantarmuka ERC-20, non-transferable, mint/burn hanya via AlphaController; transfer bebas dinonaktifkan (kecuali system-governed flows — alur yang diatur sistem).

      • EventHub sebagai append-only ledger dengan hashed proofs ke dokumen off-chain.

    • Peta utilitas: belanja (produk/layanan), akses (fitur/kelas), stake (komitmen).

    • Dasbor transparan (append-only ledger) untuk klaim/hak (entitlement).

    • Sponsor gas (aktif – Pilot v1): onboarding, convert_to_alpha, spend/access; batas per akun per hari ≈ $0,10; batas global per hari ≈ $20; throttle/pause aktif.

    • Revenue↑ → KPI: ARPU/GMV di dalam platform.

    • Cost↓ → KPI: biaya operasional per 1.000 transaksi.

    • Tax burden↓ → KPI: penurunan kejadian pajak melalui internal settlement (taat aturan).

    • Affiliate↑ → KPI: jumlah afiliasi aktif; retensi 30/90 hari.

    • Active users↑ → KPI: MAU/WAU lintas aplikasi.

    • Fairness → KPI: Koefisien Gini Reward (ketimpangan distribusi).

    Catatan: baseline & target diisi setelah sesi data 24 bulan.

    • Prinsip: berbasis perilaku (hasil simulasi ALPHA), bukan spekulasi.

    • Parameter: [PLACEHOLDER angka awal + metode penyesuaian berkala].

    • Pool utilitas (spend/access/stake), insentif afiliasi, cadangan ekosistem.

    • Utilitas: belanja produk, akses fitur/kelas, staking untuk peningkatan (boost).

    • Serapan nilai (sinks): biaya pemakaian, burn berbasis peristiwa, biaya premium.

    • PC → ALPHA: 100 PC (= $1) → 1 ALPHA; fee 0 bps; cooldown 0 hari.

    • SP → ALPHA: $1 SP → 1 ALPHA; fee 0 bps; cooldown 0 hari.

    • Default pemanfaatan ALPHA: belanja / akses / stake di dalam ekosistem.

    • Payout USD pada komponen BGC tertentu tetap AS-IS (lihat UNDERSTANDING Doc).

    • Frekuensi: 4× per tahun (triwulanan).

    • Durasi jendela: 7 hari per jendela.

    • Minimum payout: $50.

    • Biaya payout: 100 bps (1%).

    • KYC wajib untuk setiap payout.

    • Catatan: cash-out window adalah jalur sekunder & terjadwal untuk penyaluran nilai ke luar ekosistem.

    • Tata kelola bertahap; rate-limit; orkestrasi kebijakan.

    • Peta risiko; operasional; pasar; kepatuhan; reputasi.

    • Anti-Penyalahgunaan & Sybil (Pilot v1): referral cooldown 1 hari; maksimum 10 pendaftaran Tier-1 per aktor per hari; require_unique_device = true; duplicate_device_limit = 2; audit sampling 5%; penalti: wash_trade_zeroing = true, cooling_off = 7 hari.

    • PC adalah bukti transaksi produk fisik (MLM legal requirement).

    • Keanggotaan afiliasi hanya bisa dibeli dengan fiat (tidak dengan PC maupun token).

    • Legal sign-off diperlukan sebelum peluncuran publik iBC/iBTC.

    • KYC diberlakukan untuk pelaksanaan payout melalui cash-out windows (Pilot v1).

    • Rujukan dokumen kebijakan (terpisah): Legal Gate Memo (v1), Terms of Service (v1, 1-pager), Privacy Notice (v1, 1-pager), Reward Disclaimer (v1, 1-pager).

    • Simulasi ALPHA → Whitepaper v1 → Tokenflow Map v1 → Single Founder Sign-Off (incl. Legal Gate) → Pilot utilitas iBC/iBTC → Perluasan lintas aplikasi.

    • Web3 Login Plan → Web3 Login Implementation → Launch Web3 Login → Single Founder Sign-Off (incl. Legal Gate) → Pilot utilitas iBC/iBTC → Perluasan lintas aplikasi.

    • Peran: ALPHA (hak/loyalti, non-transferable) = gerbang; iBC (likuid, transferable) = alat utilitas & penyimpan nilai.

    • Cadangan: basket USD + BTC; Coverage Ratio (CR) target ditetapkan founder (disarankan ≥ 1.00, opsi konservatif 1.10).

    • Mint/Redeem:

      • Mint via burn ALPHA pada rasio kebijakan k atau setoran USD/BTC (selama CR ≥ target).

      • Redeem di cash-out windows; haircut berlaku bila CR < target.

    • Rasio kebijakan (k) ALPHA→iBC: dinamis berbasis metrik ALPHA (retensi, MAU/WAU, Gini). Contoh rentang uji: 10–25 ALPHA → 1 iBC.

    • Guardrails Treasury: band komposisi w_BTC 40–70%, USD floor ≥ 6 bulan kebutuhan redeem rata-rata, mint pause otomatis jika CR < target selama N hari.

    • KPI iBC/iBTC: CR harian, NAV, arus redeem/inflow, kecepatan sirkulasi (velocity), komposisi cadangan (BTC% vs USD%).

    • Legal Gate: iBC/iBTC go-public hanya setelah opini counsel + hasil simulasi 24 bulan menunjukkan metrik sehat.

    • Sumber data 24 bulan; definisi metrik; aturan cleaning; reprodusibilitas.

    • Standar privasi: anonimisasi PII dan manifest dataset untuk reprodusibilitas.

    • Ambang cash-out, rasio konversi awal, prioritas sinks Q1, daftar use case prioritas.

    • Tabel istilah; tabel event; diagram arsitektur ringkas.

    Konversi ke ALPHA (v1)

    • pc_to_alpha.ratio = 100 PC : 1 ALPHA; fee = 0 bps; cooldown = 0 hari.

    • sp_to_alpha.ratio = $1 : 1 ALPHA; fee = 0 bps; cooldown = 0 hari.

    Cash-Out Windows (v1)

    • windows_per_year = 4; window_length_days = 7; min_payout_usd = 50; payout_fee_bps = 100; kyc_required = true.

    Sponsor Gas & Batas (v1)

    • sponsor_gas.enabled = true; actions_covered = [onboarding, convert_to_alpha, spend/access];

    • daily_cap_per_user ≈ $0.10; global_daily_budget ≈ $20; throttle_global = true; pausable = true.

    Anti-Penyalahgunaan & Sybil (v1)

    • referral_cooldown_days = 1; max_tier1_joins_per_actor_per_day = 10;

    • require_unique_device = true; duplicate_device_limit = 2;

    • audit_sample_rate_pct = 5; wash_trade_zeroing = true; penalty_cooling_off_days = 7.

    Siklus Penyelesaian (v1)

    • accrual_frequency = harian; points_settlement_frequency = mingguan;

    • pool_distribution = { GPS: semesteran, WEC: triwulanan, MC: bulanan, GMP: bulanan, GEC: bulanan }.

    Daftar event (audit trail): JoinAffiliate, MintPC, SpendPC, EarnSP/AccrueLTS, CPContribution, PoolAccrual (GPS/GMP/WEC/MC/GEC), ConvertToALPHA, SpendAccess / Stake / Vote, CashoutWindowOpened, CashoutWindowClosed, PayoutUSD.

    Kolom minimal per peristiwa: actor, what, amount, unit, timestamp, refId, dataHash (jangkar ke bukti off-chain).

    • Legal Gate Memo (v1) — <tautan/placeholder>

    • Terms of Service (v1, 1-pager) — <tautan/placeholder>

    • Privacy Notice (v1, 1-pager) — <tautan/placeholder>

    • Reward Disclaimer (v1, 1-pager) — <tautan/placeholder>


    Berikut glosarium singkatan & istilah yang muncul/terkait di WHITEPAPER ini—ringkas dan jelas.

    • AA (Smart Account / Account Abstraction): tipe dompet kontrak dengan fitur otomatis (sponsor gas, policy), dipetakan lewat Wallet Registry.

    • Actor ID: pengenal internal untuk pengguna/entitas di event.

    • ALPHA: hak/loyalti berantarmuka ERC-20 yang non-transferable; hanya mint/burn via AlphaController; dipakai untuk belanja/akses/stake.

    • AlphaController: kontrak/gerbang kebijakan ALPHA (rasio konversi, caps, cooldown, cash-out window, pause).

    • Append-only (ledger): buku besar yang hanya menambah catatan (tidak menghapus/mengedit); cocok untuk audit.

    • ARPU (Average Revenue per User): rata-rata pendapatan per pengguna dalam periode tertentu.

    • AS-IS: apa adanya; proses payout USD BGC tertentu tetap berjalan seperti sekarang.

    • Audit trail: jejak pemeriksaan; rangkaian bukti/rekaman event untuk pembuktian.

    • Baseline/Target: nilai awal & sasaran KPI yang diisi setelah sesi data 24 bulan.

    • bps (basis points): satuan 1/100 persen (1% = 100 bps).

    • Cash-out windows: jendela terjadwal untuk penyaluran nilai keluar ekosistem (triwulanan 7 hari; min $50; fee 1%; KYC).

    • Cooling-off: masa tunggu/‘dibekukan sementara’ setelah pelanggaran.

    • Cooldown: jeda waktu sebelum aksi berikutnya diizinkan (v1 = 0 hari).

    • ConvertToALPHA: event konversi PC/SP menjadi ALPHA sesuai rasio.

    • CSV/Parquet: format berkas data untuk dump/analisis.

    • Entitlement (hak): hak pengguna (akses/klaim) yang didukung catatan ledger.

    • Event: kejadian yang dicatat ke EventHub (mis. MintPC, EarnSP, SpendAccess).

    • EventHub: kontrak/komponen pencatat event append-only dengan hashed proof ke bukti off-chain.

    • GEC/GMP/GPS/MC/WEC (pool): kategori pool distribusi (GPS=semesteran; WEC=triwulanan; MC/GMP/GEC=bulanan) sesuai UNDERSTANDING Doc.

    • Gini (Koefisien Gini Reward): metrik ketimpangan distribusi reward (0=merata; makin tinggi=makin timpang).

    • GMV (Gross Merchandise Value): total nilai transaksi barang/jasa di platform (kotor, sebelum biaya).

    • iBC / iBTC: fase lanjut utilitas on-chain (placeholder yang diaktifkan pasca legal sign-off) untuk perluasan lintas aplikasi.

    • KPI (Key Performance Indicator): indikator kinerja utama (ARPU/GMV, biaya/1.000 aksi, MAU/WAU, retensi, Gini).

    • KYC (Know Your Customer): verifikasi identitas wajib untuk payout pada cash-out windows.

    • Ledger: buku besar transaksi/peristiwa (di sini: append-only).

    • LTS: akrual/rekap SP jangka panjang (lifetime tally) untuk kebutuhan level/analitik afiliasi.

    • MAU/WAU (Monthly/Weekly Active Users): pengguna aktif bulanan/mingguan (distinct).

    • MC/GMP/GEC/GPS/WEC: lihat entri “GEC/GMP/GPS/MC/WEC (pool)”.

    • Mint/Burn: pembuatan/pemusnahan ALPHA via AlphaController.

    • MintPC / SpendPC: event penerbitan/ pengeluaran PC (produk fisik).

    • Non-transferable: tidak dapat dipindahkan bebas antar akun (hanya alur yang diatur sistem).

    • Pausable / Pause/Unpause: sakelar henti/jalan untuk kontrak/fitur ketika darurat.

    • PC: bukti transaksi produk fisik; 100 PC = $1 (basis konversi ke ALPHA).

    • Pilot v1: konfigurasi awal yang dipakai pada tahap percontohan.

    • Q1: kuartal pertama (prioritas sinks awal).

    • Rate limit (pembatasan laju): batas frekuensi/volume aksi per akun/sistem.

    • Ref ID: pengenal rujukan (nota/invoice/rekap) yang dikaitkan ke event.

    • Settlement: penyelesaian/pencatatan nilai (ritme: harian/mingguan/bulanan/dst).

    • SP: poin afiliasi berbasis pendapatan (mis. $1 SP = 1 ALPHA pada v1).

    • Spend/Access/Stake: tiga bentuk utilitas ALPHA (belanja, membuka akses fitur/kelas, atau mengunci untuk komitmen/partisipasi).

    • Stake-to-vote: pola partisipasi (voting/penilaian) bagi yang melakukan stake (opsional fase berikut).

    • Sybil: penyalahgunaan dengan banyak akun palsu untuk keuntungan tidak sah.

    • UNDERSTANDING Doc: sumber kebenaran model usaha/marketing & aturan payout AS-IS.

    • USD payout (AS-IS): penyaluran USD yang sudah berjalan pada komponen BGC tertentu; tidak terkait ALPHA.

    • Wallet Registry: peta pengguna ↔ dompet/AA pasca Web3 Login.

    • Web3 Login: mekanisme masuk terintegrasi yang menyiapkan dompet/AA pengguna.

    • WEC/GPS/MC/GMP/GEC: lihat entri “GEC/GMP/GPS/MC/WEC (pool)”.

    • Audit sampling 5%: pengambilan contoh acak 5% event/akun untuk pemeriksaan.

    • Daily cap per user ≈ $0.10; global ≈ $20: batas sponsor gas harian per akun & sistem.

    • Duplicate device limit: batas jumlah akun yang boleh berbagi identitas perangkat.

    • Require unique device: syarat minimal keterunikan perangkat untuk mencegah Sybil.

    • Throttle: penurunan throughput otomatis ketika beban/biaya melewati ambang.

    • Triwulanan/Semesteran/Bulanan: ritme distribusi pool & rekonsiliasi sesuai jenis pool.


    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.


    • title: Whitepaper v1 • 1-Pager Eksekutif

    • version: v1.0.0-draft

    • date: 2025-10-28

    • language: ID

    Dampak pada 5 Sasaran Strategis (LIVING Doc)

    Dokumen Utama v1.0 dan Resolusi Pendiri

    Tokenomics (sekilas)

    Roadmap Ringkas

    Keputusan yang Diminta (Founder)

    • title: WHITEPAPER v1 (Outline)

    • version: v1.0.0-draft

    • date: 2025-10-28

    1. Ringkasan Eksekutif

    2. Pernyataan Masalah (Singkat)

    3. Ikhtisar Solusi (C → A → B)

    3.1 Konsep

    3.2 Analogi

    3.3 Rancangan (Implementasi Tingkat Tinggi)

    4. Tokenomics (Kerangka)

    4.1 Tujuan ↔ KPI

    4.2 Supply & Emission

    4.3 Distribusi

    4.4 Utilitas & Serapan Nilai (Sinks)

    4.5 Conversion Policy (PC/SP → ALPHA → iBC/iBTC)

    4.5.1 Cash-Out Windows (Pilot v1)

    4.6 Tata Kelola & Risiko

    4.7 Catatan Kepatuhan

    5. Roadmap (Tingkat Tinggi)

    5.1 iBC/iBTC — Blueprint Beta (Post-Pilot Gate)

    6. Data & Metodologi

    7. Pertanyaan Terbuka

    Lampiran

    Daftar Parameter Awal (v1 Pilot)

    Model Peristiwa (Minimal Final)

    Dokumen Rujukan (terpisah)

    Glosarium

    A–C

    B–D

    E–H

    I–L

    M–P

    Q–T

    U–Z

    Istilah teknis tambahan (operasional)

    Evaluate whether AI& can operate without introducing unacceptable risk, misleading outputs, privacy concerns, or workflow disruption.

    Evaluate whether participating physicians find AI& useful, acceptable, and worth continuing after the pilot.


    Recommended duration:

    • minimum: 2 weeks

    • ideal: 3 to 4 weeks

    This duration is long enough to observe patterns, but short enough to remain controlled and easy to review.


    The pilot must remain narrow and highly controlled.

    Choose only 1 to 2 use cases for the pilot.

    Preferred options:

    1. SOAP note draft generation

    2. Structured visit summary drafting

    3. Patient education draft generation

    4. Follow-up reminder drafting

    5. Evidence summary for physician review

    The pilot must not include:

    • autonomous diagnosis

    • autonomous triage

    • medication recommendation

    • emergency guidance

    • unsupervised patient messaging

    • direct patient-facing AI interaction

    • unrestricted sharing of patient-linked data across physicians


    Recommended:

    • 1 primary physician

    • optional: 1 to 3 additional physicians after initial validation

    May include:

    • project coordinator

    • technical support person

    • compliance or quality reviewer

    • note-taker for feedback sessions

    Patients are not system operators in this pilot.

    If patient-linked data is involved, all handling must follow the defined data governance rules.


    The pilot may begin only if the following conditions are met:

    One or two pilot tasks are selected clearly.

    All participants understand:

    • when AI& may be used

    • who reviews outputs

    • what happens if outputs are poor

    • what is logged

    All participants agree that:

    • physicians remain the final decision-makers

    • no AI output is final without physician review

    • no autonomous patient communication is allowed

    At least basic templates exist for the selected use cases.

    The team can record:

    • AI usage events

    • review outcomes

    • corrections

    • incidents

    • feedback


    A participating physician identifies a case appropriate for pilot use.

    Examples:

    • routine documentation case

    • follow-up case

    • patient education need

    • non-emergency outpatient interaction

    The physician provides structured input into AI&.

    Possible inputs:

    • chief complaint

    • relevant history

    • findings

    • assessment points

    • plan points

    • communication goals

    AI& generates a draft according to the selected workflow.

    Examples:

    • SOAP note draft

    • education message draft

    • follow-up summary draft

    The physician must review the draft before any use.

    The physician may:

    • approve

    • edit

    • reject

    • regenerate

    Only physician-approved output may be used in real workflow.

    The system or team records:

    • type of task

    • time used

    • degree of correction needed

    • whether output was useful

    • whether any issue occurred


    The pilot should begin with cases that are relatively stable and low-risk.

    • routine follow-up visits

    • straightforward documentation tasks

    • patient education messages for familiar conditions

    • structured note conversion tasks

    • emergencies

    • highly ambiguous complex cases

    • medico-legal conflict situations

    • emotionally sensitive or crisis communication

    • cases requiring urgent escalation

    The pilot should begin in calm water, not in the storm.


    The pilot must define clear review rules.

    Every AI-generated output must be reviewed by the responsible physician before use.

    The physician must check:

    • factual alignment with the encounter

    • clarity of wording

    • completeness

    • safety of advice or explanation

    • appropriateness of tone

    If the output is misleading, incomplete, or confusing, it must not be used.

    If the output raises a safety concern, the incident must be logged and reviewed.


    The pilot should collect both quantitative and qualitative data.

    For each AI-assisted case, record:

    • date

    • physician name or identifier

    • use case type

    • draft generation time

    • review time

    • whether output was approved, edited, or rejected

    • approximate level of correction required

    • whether output was ultimately used

    Record:

    • physician comments

    • moments of trust or distrust

    • unclear phrasing

    • missing information

    • useful outputs

    • workflow friction points

    Record separately:

    • misleading clinical wording

    • privacy concern

    • wrong context carryover

    • source issue in evidence summary

    • unauthorized access concern

    • output that could have caused a near-miss


    The pilot should define success before it begins.

    • average time saved per task

    • reduction in repetitive writing effort

    • faster preparation of communication drafts

    • physician rating of clarity

    • physician rating of usefulness

    • consistency of structure

    • completeness of documentation draft

    • number of rejected outputs

    • number of significant corrections

    • number of incidents or near-misses

    • number of privacy concerns

    • percentage of eligible cases where AI& was used

    • repeat voluntary use by physicians

    • willingness to continue after pilot


    A lightweight scoring framework may be used after each AI-assisted case.

    Physician rates:

    1. usefulness

    2. clarity

    3. time saved

    4. trustworthiness

    5. amount of editing needed

    Optional note:

    • “Would I use this again for a similar case?”


    Review:

    • whether the chosen use case was correct

    • whether outputs are generally usable

    • whether templates need adjustment

    • whether workflow is too heavy or too light

    Review:

    • patterns in editing

    • trust levels

    • repeated weaknesses

    • safety observations

    Review:

    • whether to continue

    • whether to revise scope

    • whether to add one additional use case

    • whether technical deeper build should proceed


    The pilot must pause immediately if any of the following occurs:

    • repeated misleading outputs

    • privacy or confidentiality breach

    • unauthorized access issue

    • physician cannot review efficiently

    • workflow becomes more burdensome than manual work

    • team confidence drops due to unresolved safety concern

    The goal of the pilot is not to force success. The goal is to learn safely.


    At any point, the physician must be able to continue manually.

    Fallback rule:

    If AI& is unavailable, poor, uncertain, or unsafe, normal physician workflow continues without dependence on AI&.

    No clinical process should become blocked because AI& failed.


    At the end of the pilot, the team should produce:

    A short narrative of what was tested.

    A simple report of:

    • number of cases

    • use case types

    • efficiency observations

    • quality observations

    • safety observations

    A record of what should be improved.

    A final recommendation:

    • Go forward to next phase

    • Revise and repeat pilot

    • Stop due to risk or lack of value


    • choose use case

    • define workflow

    • finalize review rules

    • prepare templates

    • align pilot participants

    • first 5 to 10 cases

    • close observation

    • collect correction patterns

    • revise templates

    • refine prompts

    • improve review process

    • continue with improved workflow

    • observe stability

    • track repeat behavior

    • summarize findings

    • assess trust, usefulness, and safety

    • decide next step


    At the end of the pilot, the team should answer one central question:

    Did AI& make physician work clearer and lighter without weakening safety, privacy, or control?

    If the answer is yes, the team may proceed to:

    • technical architecture detail

    • security architecture detail

    • product requirement specification

    • mock-up / UI-UX design

    • second pilot design

    If the answer is partially yes, the team should revise the pilot design and repeat.

    If the answer is no, the project should pause and reconsider scope.


    The pilot is successful not when AI looks impressive, but when physicians remain confident, careful, and more present with patients.

    That is the standard.


    P.S. Other documents related to this document:

    • Document 1 – Presentation Narrative

    • Document 2 – Strategic Notes and References

    • Document 3 – Product Blueprint

    • Document 4 – Pilot Protocol (this document)

    • Document 5 –


    P.S.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.


    2–4 Week Controlled Pilot for a Physician-Controlled Clinical Assistance System

    1. Purpose of the Pilot

    2. Pilot Objectives

    2.1 Efficiency

    2.2 Quality

    2.3 Safety

    2.4 Trust and Adoption

    3. Pilot Duration

    4. Pilot Scope

    Recommended First Use Cases

    Not Included in the Pilot

    5. Pilot Participants

    5.1 Physician Participants

    5.2 Operational Participants

    5.3 Patients

    6. Entry Criteria Before Pilot Starts

    6.1 Use Case Is Defined

    6.2 Workflow Is Agreed

    6.3 Safety Boundaries Are Agreed

    6.4 Templates Are Ready

    6.5 Logging Is Ready

    7. Pilot Workflow

    Step 1 – Select Eligible Case

    Step 2 – Enter Structured Input

    Step 3 – Generate Draft

    Step 4 – Physician Review

    Step 5 – Final Use

    Step 6 – Logging

    8. Case Selection Rules

    Good Early Cases

    Poor Early Cases

    9. Review Rules

    Mandatory Review Rule

    Minimum Review Actions

    Rejection Rule

    Escalation Rule

    10. Logging Requirements

    10.1 Quantitative Log

    10.2 Qualitative Log

    10.3 Incident Log

    11. Success Metrics

    11.1 Efficiency Metrics

    11.2 Quality Metrics

    11.3 Safety Metrics

    11.4 Adoption Metrics

    12. Simple Scoring Framework

    Per Case Score (1–5)

    13. Weekly Review Structure

    End of Week 1

    End of Week 2

    End of Week 3–4

    14. Stop / Pause Criteria

    15. Fallback Workflow

    16. Pilot Deliverables

    16.1 Pilot Summary

    16.2 Metrics Summary

    16.3 Template Revision Notes

    16.4 Go / Revise / Stop Recommendation

    17. Suggested Pilot Timeline

    Week 0 – Preparation

    Week 1 – Controlled Initial Use

    Week 2 – Adjustment

    Week 3 – Broader Controlled Use

    Week 4 – Evaluation

    18. Recommended First Decision After Pilot

    19. Final Principle

    Current source of truth

    Final Reference

    Complete for a defined factual or architectural purpose

    Final and Approved

    Accepted for execution or institutional use

    Implementation Pending

    Approved design exists; execution is incomplete

    Historical Artifact

    Retained to document what happened

    Archived Hypothesis

    Preserved idea; not an active plan

    Superseded

    Replaced by another document

    Preliminary Evidence

    Output exists; insufficient for final approval

    Closed

    No further updates; future work uses new documents

    Pending Founder Decision

    Cannot proceed without resolution


    No.
    Artifact
    Final Status
    Active Authority
    Closure Action
    Future Treatment

    1

    Initial iBLOOMING Web3 Pitch

    Historical Artifact

    No


    Final AS-IS Business and Reward Rules Reference

    It is not a legal approval or economic-health certification.

    Final and Founder-Approved Architecture Specification — Implementation Pending

    Archived Future-State Tokenization Hypotheses — Not Approved for Implementation

    Archived Tokenization Scenario Maps — Not Approved for Implementation

    Archived Phase-1 Token Policy Simulation Specification

    First Executable Simulation Reports — Technically Complete, Analytically Preliminary

    Closed Phase-1 Strategic and Historical Reference


    Need
    Correct Document

    Meeting outcome

    Founder Meeting Record and Resolutions

    Annual plan

    Product-Led Systems Program 2026–2027

    Small experiment

    Pilot Brief

    Technical architecture

    System Design Document

    Product or entitlement movement


    No document may become implementation authority without recording:

    • approving decision;

    • approving person or body;

    • date;

    • scope;

    • owner;

    • resources;

    • legal or financial gates;

    • acceptance criteria.

    Silence, enthusiasm, or absence of objection is not approval.


    Phase 1 is closed as an exploration, reconstruction, architecture, and simulation phase.

    The final active outputs are the UNDERSTANDING Doc, the approved WEB3LOGIN architecture, the SIMALPHA working MVP, the Master Document, and the founder resolutions.

    The old tokenized-future Whitepaper, Tokenflow, and SIMULATION Doc remain valuable historical hypotheses but are not implementation authorities.

    Phase 2 must begin from explicit founder decisions, named owners, sufficient resources, and a Product-Led objective.


    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.


    1. Closure Principle

    2. Status Definitions

    Active Authority

    3. Full Register

    4. Closure Decisions

    UNDERSTANDING Doc

    WEB3LOGIN Doc

    Whitepaper Drafts

    Tokenflow Drafts

    SIMULATION Doc v0.1

    Scenario Reports

    Old LIVING Doc

    5. New-Document Rule

    6. Change Control

    7. Closure Statement

    FOUNDER MEETING AGENDA

    This meeting should not be used to choose token price, conversion ratio, cash-out fee, reserve ratio, or listing plan.

    Agenda, Resolution, and Action Register

    Date: 5 August 2026 Meeting format: To be confirmed Chair: To be confirmed Presenter: Prof. NOTA Recommended duration: 75–90 minutes Status: Live meeting template


    1. Meeting Purpose

    The meeting should:

    1. close Phase 1;

    2. review the evidence and its limitations;

    3. decide what stops and what continues;

    4. approve or reject the Product-Led strategic transition;

    5. assign owners and resources;

    6. create an authoritative decision record.

    This meeting should not be used to choose token price, conversion ratio, cash-out fee, reserve ratio, or listing plan.


    • Master Document v1.0;

    • Founder Decision Brief;

    • Product-Led Systems Transition Concept Note;

    • Web3 Login Implementation Handover Note.

    Optional supporting evidence:

    • SIMALPHA Findings Framework;

    • original Compare Report and four scenario reports;

    • UNDERSTANDING Doc;

    • WEB3LOGIN Doc.


    Name
    Role
    Present

    • confirm purpose;

    • confirm decision authority;

    • confirm who records resolutions.

    • project evolution;

    • completed specifications;

    • SIMALPHA;

    • data and reports.

    • two economic engines;

    • limits of current evidence;

    • why existing-system tokenization is not recommended;

    • Web3 Login status.

    • product-demand problem;

    • Product-Led Systems Transformation;

    • physical and digital pilots;

    • technology principles.

    Complete the Founder Decision Brief.

    • Web3 Login;

    • product pilot;

    • product data;

    • finance/accounting;

    • legal/tax;

    • read back decisions;

    • confirm amendments;

    • confirm next meeting;

    • confirm document owner.


    No.
    Question
    Asked By
    Answer / Follow-Up
    No.
    Objection
    Raised By
    Resolution

    No.
    Decision
    Outcome
    Conditions
    Decision Owner

    BGC × iBLOOMING acknowledges that Phase 1 produced a final AS-IS rules reference, a founder-approved Web3 Login architecture, a working SIMALPHA decision-support application, a prepared aggregate dataset, and preliminary simulation reports.

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

    BGC × iBLOOMING resolves to proceed with the decisions recorded in this meeting, including the approved status of Web3 Login, the treatment of the old tokenization drafts, the Product-Led strategic direction, the boundaries for public-token and financial-product research, and the assignment of accountable owners.


    No.
    Action
    Owner
    Resources Required
    Deadline
    Acceptance Criteria
    Status

    The following matters should be recorded if discussed but not decided:

    Matter
    Reason Deferred
    Required Evidence
    Responsible Person

    Role
    Name
    Confirmation

    Within two working days, issue:

    BGC × iBLOOMING Founder Meeting — Decisions, Owners, and Next Actions — 5 August 2026

    The final record should contain:

    • attendees;

    • decisions;

    • amendments;

    • objections;

    • owners;

    No interpretation should replace the recorded decisions.


    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 . 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.


    BGC X IBLOOMING FOUNDER PRESENTATION

    Phase-1 Closure and Product-Led Strategic Transition

    Date: 5 August 2026 Presenter: Prof. NOTA Recommended duration: 20 minutes presentation + 40–60 minutes decision discussion Status: Final pre-meeting draft


    Phase-1 Review, Findings, and Founder Decisions

    Today we need to decide:

    1. what Phase 1 has completed;

    2. what the evidence supports;

    language: ID

  • single_language_rule: true

  • sources_of_truth:

    • UNDERSTANDING Doc (model bisnis/marketing)

    • LIVING Doc (Strategic Objectives & guardrails)

  • Freeze

    Retain for chronology

    2

    Meeting Day 1 Record

    Historical Artifact

    No

    Freeze

    Retain

    3

    Initial Web3 Draft

    Superseded

    No

    Freeze

    Replaced by later specifications

    4

    Meeting Day 2 Record

    Historical Artifact

    No

    Freeze

    Retain as turning point

    5

    Draft LIVING Doc

    Superseded

    No

    Freeze

    Retain

    6

    LIVING Doc

    Close After Final Update

    Historical after closure

    Append closure update

    Replace with new program

    7

    Web3 Login Draft

    Superseded

    No

    Freeze

    Replaced by Revision D

    8

    Draft Reward Understanding

    Superseded

    No

    Freeze

    Replaced by final UNDERSTANDING

    9

    WEB3LOGIN Doc Revision D

    Final and Approved; Implementation Pending

    Yes

    Freeze specification

    Yuku and engineering implement

    10

    UNDERSTANDING Doc

    Final AS-IS Reference

    Yes

    Freeze

    Amend only after factual validation

    11A

    Whitepaper Draft — Indonesian

    Archived Hypothesis

    No

    Archive

    New Product Paper or Whitepaper only for approved use case

    11B

    Whitepaper Draft — English

    Archived Hypothesis

    No

    Archive

    Do not synchronize or finalize

    12A

    Tokenflow Draft — Indonesian

    Archived Hypothesis

    No

    Archive

    Create use-case-specific Product Flow

    12B

    Tokenflow Draft — English

    Archived Hypothesis

    No

    Archive

    Do not synchronize or finalize

    13

    Alignment Call With KK

    Historical Preparation Artifact

    No

    Freeze

    Not a decision record

    14

    December Working Presentation

    Historical Working-Alignment Artifact

    Limited

    Freeze

    Replaced by 5 August deck

    15

    SIMULATION Doc v0.1

    Archived Phase-1 Specification

    No

    Archive

    Replaced by evidence framework

    16

    SIMALPHA Build Process

    Final Historical Build Record

    Yes for provenance

    Freeze

    Maintain

    17

    Compiled Monthly Dataset

    Complete for Current Aggregate Scope

    Limited

    Version-lock

    Not member-level evidence

    18

    Founder Glossary

    Superseded Draft

    No

    Supersede

    Replace with corrected framework

    19

    Compare Report

    Preliminary Evidence

    No

    Preserve

    Add correction note

    20

    Baseline Report

    Preliminary Evidence

    No

    Preserve

    Reference only

    21

    Conservative Report

    Preliminary Evidence

    No

    Preserve

    Reference only

    22

    Growth Report

    Preliminary Evidence

    No

    Preserve

    Reference only

    23

    Stress Report

    Preliminary Evidence

    No

    Preserve

    Interpret as restrictive policy

    24

    Master Document v1.0

    Active Founder Decision Source

    Yes

    Founder review

    Update through meeting resolution

    25

    Founder Decision Brief

    Active Meeting Instrument

    Yes

    Complete during meeting

    Attach to meeting record

    26

    SIMALPHA Findings Framework

    Active Decision Support

    Yes

    Founder review

    Version only if evidence changes

    27

    Web3 Login Handover Note

    Active Handover

    Yes

    Confirm ownership

    Use implementation change control

    28

    Product-Led Transition Note

    Pending Founder Decision

    Conditional

    Review

    Convert into annual program if approved

    Product and Entitlement Flow

    Public-facing product explanation

    Product Paper

    Public protocol or token

    New Whitepaper

    Token movement

    New Tokenflow, only after token approval

    Decisions

    Decision Log

    Progress

    Program Status Report

    Research

    Research Note

    Discussion Log

    Founder

    [ ]

    Founder

    [ ]

    KK

    Business/operations

    [ ]

    Prof. NOTA

    Presenter and consultant

    [ ]

    Uncle Kal

    SIMALPHA owner/implementer

    [ ]

    Yuku

    Technical owner

    [ ]

    Other

    [ ]

    program governance.

    3

    Existing-system tokenization closure

    4

    Public-token status

    5

    Physical-product pilot

    6

    Digital-product pilot

    7

    Product and affiliate metric separation

    8

    Resource ownership

    9

    Financial-product boundary

    10

    Prof. NOTA’s role

    11

    Phase-2 annual program

    2

    Close old LIVING Doc

    Closure update appended

    3

    Start Web3 Login kickoff

    Technical-verification pack

    4

    Select physical pilot

    Approved Pilot Brief

    5

    Select digital pilot

    Approved Pilot Brief

    6

    Define Product-Led baseline

    KPI and data dictionary

    7

    Correct SIMALPHA labels

    Revised report standard

    8

    Draft annual program

    Founder-review version

    Technical owner

    deadlines;

  • documents closed;

  • documents authorized;

  • next review date.

  • Founder

    [ ]

    Founder

    [ ]

    Founder

    [ ]

    1

    2

    1

    2

    1

    Product-Led strategic transition

    2

    Web3 Login implementation

    1

    Publish meeting record

    Founder decision owner

    Chair

    Recorder

    2. Required Pre-Reading

    3. Attendees

    4. Proposed Agenda

    00:00–00:05 — Opening

    00:05–00:20 — Phase-1 Review

    00:20–00:35 — Findings

    00:35–00:50 — Product-Led Direction

    00:50–01:10 — Founder Decisions

    01:10–01:20 — Owners and Resources

    01:20–01:30 — Resolution and Closing

    5. Presentation Record

    Key Findings Presented

    Questions Raised

    Objections or Reservations

    6. Decision Record

    7. Resolution

    Draft Resolution

    Resolution Status

    Amendments

    8. Action Register

    9. Deferred Matters

    10. Meeting Sign-Off

    11. Post-Meeting Document

    Prof. NOTA

    3

    Founder-reviewed record

    Prof. NOTA

    what should stop;

  • what should continue;

  • what the next program should become.

  • Thank you for the opportunity to present the full project journey.

    This meeting is not intended to ask you to study every technical report or become experts in blockchain.

    My responsibility today is to translate one year of documents, architecture, data preparation, simulation, and findings into clear business decisions.

    The most important question is no longer:

    “How do we launch a token?”

    The more responsible question is:

    “What technology direction can increase real product demand and business value without duplicating obligations or creating a new speculative burden?”


    The original proposal was centered on iBLOOMING, Web3 Login, and a controlled loyalty simulation.

    After KK explained BGC’s Purchase Credit, Sales Point, LTS, rewards, and pools, we learned that the ecosystem already had an internal value system.

    We therefore moved from creating a token concept to reconstructing the real operating system.

    In December 2025, simulation became the required first step.

    From March 2026, Uncle Kal built SIMALPHA as a real internal decision console.

    The project is now at the point where documents and software must be converted into founder decisions.


    • UNDERSTANDING Doc — AS-IS business and reward rules

    • WEB3LOGIN Doc — approved architecture specification

    • Whitepaper and Tokenflow — completed as draft hypotheses

    • SIMULATION Doc v0.1

    • SIMALPHA working MVP

    • data cleaning and import pipeline

    • 25-month aggregate dataset

    • four scenario reports

    • comparison report and founder glossary

    • Web3 Login engineering implementation

    • final economic reconciliation

    • legal and tax validation

    • any token implementation

    It is important to distinguish specification from implementation.

    The Web3 Login architecture is complete and approved. Its implementation remains the responsibility of Yuku and the engineering team.

    The Whitepaper and Tokenflow drafts are useful historical and design artifacts, but they are not approved implementation plans.

    SIMALPHA works as an internal simulation and reporting application.

    The reports exist, but their evidence is preliminary.


    BGC
    iBLOOMING

    Affiliate-entry driven

    Product-transaction driven

    New join creates LTS

    Product sale creates revenue

    Rewards linked to new-join LTS

    Rewards allocated from product transactions

    Recorded cash-in: ≈ $4.034M

    Recorded cash-in: ≈ $21.1K

    The ecosystem is economically dominated by affiliate-entry transactions, while direct product revenue remains very small.

    The data does not directly prove why every member joined.

    However, the reward design and transaction pattern are consistent with an ecosystem where the income opportunity is likely a stronger acquisition driver than independent product demand.

    The correct next test is whether people buy the same products at the same price without an affiliate-income opportunity.


    • data can be imported;

    • policy scenarios can be run;

    • results are deterministic;

    • issuance and cash-release rules change outputs;

    • reports can support structured discussion.

    • profit;

    • reserve safety;

    • sustainability;

    • member-level fairness;

    • product liability coverage;

    • tax reduction;

    • public-token readiness.

    SIMALPHA is a successful working MVP.

    However, its current dataset contains monthly-tier aggregate records, not persistent individual member histories.

    The first reports use incomplete accounting and liability fields.

    Therefore, we should not use the current reports to lock token parameters or claim that a scenario is financially safe for implementation.


    • PC represents a product entitlement.

    • SP represents a reward or payout basis.

    • Converting both may create duplicate rights.

    • Pool and payout obligations are not fully reconciled.

    • Product cost and reserve are incomplete.

    • Public-token backing and redemption are unresolved.

    • Tokenization may automate the current risk without creating productive demand.

    Do not tokenize membership, PC, SP, LTS, rewards, pools, or payouts.

    This is not a statement that blockchain has failed.

    It means blockchain should not be used to turn unclear obligations into programmable obligations.

    Any further financial validation requires Finance, Accounting, Operations, Legal, Tax, Data, and Engineering resources—not Prof. NOTA alone.


    Shift from:

    reward-led acquisition

    toward:

    measurable product demand

    Focus:

    • physical products;

    • digital products and content;

    • commerce;

    • supply chain;

    • retailer and distributor systems;

    • product access;

    • authenticity;

    • ownership;

    • customer usage and repeat purchase.

    The strongest opportunity discovered through this project is Product-Led transformation.

    Marketing should progressively explain:

    • what the product does;

    • who needs it;

    • why it is worth the price;

    • how it is delivered;

    • why the customer uses it again.

    Product sales and usage should be measured separately from affiliate recruitment.

    This creates a healthier role for blockchain and AI: supporting products and operations instead of creating a new speculation mechanism.


    • final and approved specification;

    • implementation owner: Yuku and engineering;

    • Prof. NOTA: architecture and integration support.

    • non-affiliate buyers;

    • direct fiat product sales;

    • repeat purchase;

    • content usage;

    • subscription retention;

    • product margin.

    • physical-product passport;

    • digital-access pass;

    • product-content bundle;

    • retailer or distributor credential.

    Web3 Login remains valuable even without a public token.

    It can create wallet-ready identities for:

    • digital receipts;

    • product passports;

    • access credentials;

    • ownership records;

    • retailer verification.

    The first pilots should be limited, non-tradable, and paid in fiat.

    They should not promise money, yield, or price appreciation.


    • optional research only;

    • separate from BGC affiliate rewards;

    • no PC/SP default conversion;

    • no guaranteed redemption;

    • no yield or price promise;

    • no use of new buyers to pay existing obligations.

    This program will not create:

    • deposits;

    • promised yield;

    • DeFi;

    • DEX;

    • CEX;

    • fundraising through the affiliate network.

    A strong appetite for financial return is not proof that the company should build a financial product.

    A public token or financial-services business would require different governance, licensing, capital, security, compliance, and risk-management capability.

    That should not be treated as the automatic next step of this project.


    Founders are asked to decide:

    1. approve Product-Led strategic transition;

    2. approve Web3 Login implementation;

    3. close old existing-system tokenization drafts as active plans;

    4. keep public token as separate research only;

    5. choose one physical and one digital product pilot;

    6. separate product metrics from affiliate metrics;

    7. assign owners and resources;

    8. approve the financial-product boundary;

    9. confirm Prof. NOTA’s Product and Web3 Transformation role;

    10. authorize creation of the 2026–2027 Product-Led Systems Program.

    Phase 1 has created real value:

    • a documented operating model;

    • an approved identity architecture;

    • a functioning simulator;

    • a prepared dataset;

    • and a clearer understanding of where technology is useful and where it may amplify risk.

    The responsible conclusion is not that tokenization has failed.

    The conclusion is:

    We should use blockchain and AI where they strengthen products, ownership, access, commerce, distribution, and trust—and keep speculation and financial-return promises outside this program.


    Metric
    Combined

    Period

    April 2024–April 2026

    Aggregate rows

    236

    Cash in

    $4,055,155.00

    Recognized-revenue field

    $4,040,373.10

    Direct/global reward

    $412,815.06

    Rows represent month and tier combinations, not individual members.


    Scenario
    Correct Interpretation

    Baseline

    Initial policy reference

    Conservative

    Reduced issuance and cash release

    Growth

    Increased issuance and cash release

    Stress

    Treasury Preservation / Restrictive Policy

    No scenario is approved for implementation.


    Document
    Status

    UNDERSTANDING

    Final

    WEB3LOGIN

    Final and approved; implementation pending

    Whitepaper

    Archived draft

    Tokenflow

    Archived draft

    SIMULATION Doc


    No. The year produced specifications, software, evidence, and a more responsible direction.

    Because tradability creates legal, market, accounting, liquidity, and reputational risks even when no price increase is promised.

    Because identity, wallet readiness, credentials, ownership, and access remain useful independently of tokenization.

    Not for deciding to stop existing-system tokenization.

    More targeted evidence is needed only if founders want to approve financial or token implementation.

    Because the present ecosystem needs stronger independent product demand, not a new mechanism for attracting money.


    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.


    Phase-1 Closure and Product-Led Strategic Transition

    Slide 1 — Why We Are Here

    On Slide

    BGC × iBLOOMING

    Web3 exploration
    → Web3 Login and ALPHA concept
    → discovery of the BGC economic model
    → UNDERSTANDING and WEB3LOGIN specifications
    → Whitepaper and Tokenflow hypotheses
    → simulation-first correction
    → SIMALPHA
    → founder decision phase

    Speaker Notes

    Slide 2 — How the Project Evolved

    On Slide

    Speaker Notes

    Slide 3 — What Has Been Completed

    On Slide

    Final or Completed

    Still Pending

    Speaker Notes

    Slide 4 — The Most Important Economic Finding

    On Slide

    Two Different Economic Engines

    Key Message

    Speaker Notes

    Slide 5 — What SIMALPHA Proves and Does Not Prove

    On Slide

    SIMALPHA Proves

    SIMALPHA Does Not Yet Prove

    Speaker Notes

    Slide 6 — Why We Should Not Tokenize the Existing System

    On Slide

    Existing-System Tokenization Risks

    Recommendation

    Speaker Notes

    Slide 7 — The New Strategic Direction

    On Slide

    Product-Led Systems Transformation

    Speaker Notes

    Slide 8 — What Continues Immediately

    On Slide

    1. Web3 Login

    2. Product-Demand Baseline

    3. Small Web3 Product Pilots

    Speaker Notes

    Slide 9 — Boundaries

    On Slide

    Public Token

    Financial Products

    Speaker Notes

    Slide 10 — Decisions Required Today

    On Slide

    Closing Script

    Appendix Slide A — SIMALPHA Data Snapshot

    Caveat

    Appendix Slide B — Scenario Interpretation

    Appendix Slide C — Document Status

    Appendix Slide D — Difficult Questions

    “Does this mean the last year was wasted?”

    “Why not launch a simple token anyway?”

    “Why continue Web3 Login?”

    “Do we need more data?”

    “Why Product-Led?”

    SIMALPHA OH SIMALPHA

    It replaces the Founder’s Reading Guide as the current interpretation authority. It does not replace the original reports. The original reports remain preserved as first-version outputs.

    Version: 1.0 Prepared for: BGC × iBLOOMING Founders and Core Team Prepared by: Prof. NOTA Simulator owner and principal implementer: Fabio Kalandra (“Uncle Kal”) Date: 5 August 2026 Status: Active decision-support reference


    1. Purpose

    This document explains:

    • what SIMALPHA is;

    • what it successfully does;

    • what its current data and reports support;

    • what they do not support;

    • how founders should read the first simulation results;

    • what must be corrected before future policy approval.

    It replaces the Founder’s Reading Guide as the current interpretation authority.

    It does not replace the original reports. The original reports remain preserved as first-version outputs.


    SIMALPHA is an internal decision-support web application.

    Its workflow allows a permitted user to:

    1. upload or select a versioned business-data snapshot;

    2. define or select a policy scenario;

    3. run a deterministic simulation;

    4. review money, ALPHA, distribution, and risk outputs;

    5. compare completed runs;

    SIMALPHA is not:

    • a public token;

    • a smart-contract deployment;

    • a wallet;

    • a cash-out system;

    • a treasury;


    The working MVP includes:

    • data-snapshot versioning;

    • import and validation;

    • scenario storage;

    • deterministic execution;

    • result references;

    This is a substantial technical deliverable.

    The application is suitable for structured internal policy exploration.


    The current compiled dataset contains:

    • 236 records;

    • 25 monthly periods;

    • April 2024–April 2026;

    • BGC and iBLOOMING records;

    • monthly-tier aggregation.

    Examples of synthetic record keys include combinations such as:

    • BGC + month + membership tier;

    • iBLOOMING + month + membership tier.

    These are not persistent individual member identities.

    The dataset can support:

    • monthly aggregate analysis;

    • source-system comparison;

    • tier comparison;

    • issuance and cash-release sensitivity;

    • cashflow-proxy discussion.

    It cannot validly support:

    • real active-user count;

    • new-user count;

    • retained-user count;

    • churn;

    • member-level Gini;

    Any metric derived by treating each aggregate record as a person must be removed or relabeled.


    Metric
    BGC
    iBLOOMING
    Combined

    The dataset labels BGC cash-in as:

    • cash in;

    • recognized revenue;

    • gross margin.

    These labels must not be interpreted as audited revenue, gross margin, profit, or free cash.

    The available data does not deduct:

    • physical-product cost;

    • inventory;

    • shipping;

    • fulfillment;

    • operating expense;


    Scenario
    ALPHA Issued
    ALPHA Used
    Modeled ALPHA Cash Release
    ALPHA Held
    Reported Net Cash Proxy
    Reported Pressure

    An initial policy reference using the current model assumptions.

    It is not a validated reproduction of the complete historical economy.

    A lower-issuance and lower-cash-release policy.

    It demonstrates sensitivity to tighter parameters.

    A higher-issuance and higher-cash-release policy.

    It does not demonstrate real revenue or user growth because no independent future-growth evidence is included.

    The name is misleading.

    The scenario:

    • uses the same imported historical business data;

    • has no meaningful future shock;

    • mainly lowers issuance;

    • tightens caps;

    • restricts cash-out frequency;

    Correct interpretation:

    Treasury Preservation / Restrictive Policy Scenario

    It retains the most modeled cash because the model releases the least cash.

    That is a parameter consequence, not an independent finding that the policy is best.


    Replace:

    • Ready;

    • Needs Review;

    • Do Not Use.

    With:

    New Label
    Meaning

    All four current scenarios should carry:

    Preliminary Pass — Insufficient Evidence for Implementation Approval

    Replace:

    ALPHA is the practice version of iBC/iBTC.

    With:

    ALPHA is a neutral simulation unit used to test alternative representations of rights, rewards, access, or internal value. It does not imply that a public token will be launched.

    Replace:

    Actual Payout Out

    With:

    Modeled ALPHA Cash Release

    Historical cash-out is a different data field and must be shown separately.

    This statement must be removed.

    PC and SP represent different rights.

    Any future conversion must define:

    • which original right is extinguished;

    • whether conversion is reversible;

    • whether product or payout rights remain;

    • whether the conversion creates a new liability.

    Replace:

    Net Cash

    With:

    Incomplete Net Cash Proxy

    Until the model includes:

    • rewards payable;

    • pools;

    • fulfillment;

    • COGS;

    • OpEx;

    Remove or relabel:

    • Active User Count;

    • New Active User Count;

    • Retained Active User Count;

    • Affiliate Retention;

    • Top 10% Member Share;

    Suggested label where retained:

    Aggregate Segment Concentration


    The current source data contains:

    • pool reward fields;

    • historical cash-out fields;

    • internal credit spend.

    The first reports show:

    • pool funding owed = zero;

    • much lower modeled ALPHA cash release;

    • fulfillment cost = zero.

    This does not automatically prove a software bug.

    It proves that field mapping, liability treatment, or policy treatment is incomplete or undocumented.

    The next technical review should trace:


    SIMALPHA can support decisions such as:

    • whether a scenario issues more or less ALPHA;

    • whether cash-release restrictions retain more modeled cash;

    • whether report outputs change consistently;

    • whether assumptions are visible;

    It can support the conclusion:

    Do not approve current tokenization.

    It cannot support the conclusion:

    This system is economically safe and ready for token implementation.


    Required:

    • versioned input;

    • documented mapping;

    • reproducible results;

    • no unsupported member-level metrics.

    Required:

    • reproduce historical observed totals;

    • separate actual from modeled values;

    • explain every material difference.

    Required:

    • PC obligations;

    • reward obligations;

    • pool obligations;

    • COGS;

    • fulfillment;

    Required:

    • independent product buyers;

    • repeat purchases;

    • product usage;

    • margin;

    • retention;

    Only after Gates 0–3:

    • caps;

    • fees;

    • internal access;

    • entitlement policy;

    • cash-release rules.

    Compare:

    • conventional database;

    • EventHub or evidence anchoring;

    • non-transferable credential;

    • internal rights;

    • public token.

    No token implementation before written approval.


    Before reading numbers, confirm whether the report says:

    • actual;

    • modeled;

    • assumed;

    • missing;

    • preliminary.

    A scenario is useful only when the changed rules are clear.

    Always check:

    • obligations;

    • costs;

    • reserve;

    • rights;

    • user impact.

    Every future token-related simulation must include:

    No-token / conventional-system control

    A simulator result should lead to one of:

    • reject;

    • study further;

    • request evidence;

    • approve limited pilot;

    • approve implementation.

    “Green” is not automatically approval.


    1. Select a versioned dataset.

    2. Confirm source and mapping notes.

    3. Select a scenario.

    4. review changed parameters;

    5. confirm actual-versus-modeled flags;


    • change verdict labels;

    • add Insufficient Evidence;

    • relabel cash release;

    • relabel net cash;

    • remove invalid user metrics;

    • reconcile pool fields;

    • reconcile partner payouts;

    • reconcile fulfillment;

    • trace internal credit;

    • document formula mapping;

    • calibrate against observed totals;

    • show differences;

    • explain opening and closing balances.

    Add support for:

    • independent product demand;

    • direct product sale;

    • repeat purchase;

    • product margin;

    • digital access usage;

    Apply:

    • new-join decline;

    • product-revenue decline;

    • cash-out increase;

    • PC redemption increase;

    • COGS increase;


    SIMALPHA is a working internal decision-support MVP with preliminary policy-sensitivity outputs. It is not yet a calibrated historical economic replay, a validated sustainability model, or a basis for final token parameters.

    This is not a failure.

    It is the correct status for a first serious simulation product.

    The next value of SIMALPHA is to support Product-Led evidence, no-token controls, and disciplined founder decisions.


    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 . 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.


    PROPOSAL PERURI CONNECT WEB3 - ID

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Tanggal draf: {{TANGGAL}} Disiapkan untuk: PERURI — Departemen TI/HR Disiapkan oleh: Peruri Digital Security × Voyage Versi: {{VERSI}}


    0) Ringkasan Eksekutif

    Tujuan. Membangun sistem Reward karyawan yang tercatat, bisa diverifikasi, dan aman di atas Blockchain privat (permissioned). Sistem ini menyatu dengan Peruri Connect (login/SSO) dan aplikasi mobile yang sudah ada. Manfaat utama.

    • Semua penerbitan Reward, transfer antar rekan (peer‑to‑peer), dan redeem (voucher/merch/fasilitas internal) tercatat otomatis dan bisa diaudit.

    • Aturan & kuota dapat dikontrol (siapa boleh memberi, berapa banyak per hari/minggu/bulan).

    • Dashboard untuk HR/Manajemen: laporan, grafik, dan ekspor CSV untuk audit. Target go‑live. {{TANGGAL_GO_LIVE}} dengan pilot {{JUMLAH_PENGGUNA_PILOT}} pengguna.

    Catatan: Di dokumen ini, istilah yang umum dan teknis seperti Reward, Blockchain, API, Dashboard, Token, Node tetap menggunakan Bahasa Inggris agar konsisten dan mudah dikenali.


    • S1 — Verifiable Rewards. Semua fungsi (issue/transfer/redeem) terekam di ledger dan mudah dilacak.

    • S2 — P2P Recognition. Karyawan dapat memberi Reward ke rekan kerja sesuai kebijakan & kuota.

    • S3 — Integrasi Mulus. Login pakai Peruri Connect; UI/UX konsisten di mobile app.

    • S4 — Kontrol & Tata Kelola. Role & approval flow yang jelas; bisa pause/resume

    KPI contoh (bisa disesuaikan):

    • SLA layanan ≥ 99,5%; p95 waktu respons API < 2 detik.

    • Finality transaksi < 5 detik di jaringan privat.

    • UAT pass rate ≥ 95%; kepuasan pengguna (CSAT) ≥ 80%.


    • Memetakan alur Reward saat ini (aktor, peran, kuota, pengecualian).

    • Mendesain model token Reward (mint dari Treasury → user, P2P dengan batasan).

    • Menentukan mekanisme redeem (katalog, settlement, refund, anti‑fraud).

    • Jaringan: Hyperledger Besu (Blockchain privat/permissioned) + konsensus IBFT 2.0 (finality cepat).

    • Kontrak inti: RewardToken.sol (token), Treasury.sol (kas), Redemption.sol (penukaran), PolicyRegistry.sol (kebijakan).

    • Backend Node.js + TypeScript (REST/GraphQL) sebagai gerbang ke Blockchain.

    • Auth via Peruri Connect (OAuth 2.0 + JWT).

    • OpenAPI (spesifikasi) + contoh request/response, serta webhook untuk mitra redeem.

    • Dashboard admin (atur penerbit, kuota, kebijakan, katalog redeem, laporan).

    • Rekonsiliasi on‑chain/off‑chain & alert bila ada anomali.

    • Review kode & audit kontrak; penetration test untuk API.

    • Monitoring (Prometheus) & visualisasi (Grafana); log terpusat.

    • Backup & Disaster Recovery (RPO/RTO disepakati).

    • Pelatihan untuk admin/ops/dev; runbook; handover; sesi knowledge transfer.

    • Hypercare pasca rilis; patch minor & perbaikan sesuai SLA.


    • Besu adalah Ethereum client open‑source untuk public maupun private/permissioned network. Di mode privat, kita bisa membatasi validator (hanya node yang disetujui).

    • IBFT 2.0 (Proof‑of‑Authority) memberi finality cepat (blok yang disetujui tidak fork), cocok untuk transaksi internal perusahaan.

    Referensi resmi: • Hyperledger Besu (docs): https://besu.hyperledger.org/ • Besu — Private (Permissioned) Networks: https://besu.hyperledger.org/private-networks • Tutorial — Create an IBFT 2.0 network: https://besu.hyperledger.org/private-networks/tutorials/privacy

    • Validator Nodes: {{N_VALIDATORS}} (contoh 2–4; bisa ditempatkan di TI PERURI & PDS).

    • Transaction Nodes (API‑facing): {{N_TX_NODES}} untuk melayani aplikasi.

    • BAS/Indexer (opsional): untuk analitik dan pencarian cepat.

    • Monitoring: Prometheus (kumpulkan metrik) + Grafana (grafik/dashboards).

    Referensi resmi: • Start Besu / System Requirements: https://besu.hyperledger.org/private-networks/get-started/start-node • Prometheus (official): https://prometheus.io/ • Grafana (official): https://grafana.com/

    • User masuk lewat Peruri Connect; sistem memetakan role HR/Manajemen/Admin ke role on‑chain (mis. Minter, Policy Admin).

    • Aksi kritikal (ubah kebijakan, mint besar) dapat diproteksi multisig atau approval berjenjang.

    • On‑chain hanya menyimpan data minimal (saldo token, event transaksi).

    • PII tetap di database Peruri Connect (off‑chain). Untuk audit, bisa simpan hash/pointer di on‑chain.

    • POST /rewards/issue — HR/Admin menerbitkan Reward ke karyawan.

    • POST /rewards/transfer — karyawan A memberi Reward ke karyawan B (sesuai kuota).

    • POST /rewards/redeem — menukar Reward ke item katalog (voucher/merch/benefit).

    Teknologi pendukung API:

    • Node.js (runtime JavaScript untuk server) + TypeScript (pengetikan statis agar kode lebih aman/terbaca).

    • OpenAPI (standar deskripsi API) untuk dokumentasi otomatis.

    • OAuth 2.0 (protokol otorisasi) + JWT (format token) untuk akses aman.

    Referensi resmi: • Node.js: https://nodejs.org/ • TypeScript: https://www.typescriptlang.org/ • OpenAPI Initiative: https://www.openapis.org/ • OAuth 2.0: https://oauth.net/2/ • JWT (RFC 7519): https://datatracker.ietf.org/doc/html/rfc7519


    • Siapa yang boleh menerbitkan (role Issuer/HR/Admin).

    • Kuota per periode (bulanan/kuartal), dan batas per orang.

    • Aturan pembatalan (burn/revoke) bila ada kesalahan input.

    • Batas harian/mingguan dan cooldown per pengguna.

    • Filter penerima (mis. unit kerja/kontrak aktif).

    • Pencegahan penyalahgunaan (mis. anti “saling kirim” berulang).

    • Katalog item (voucher, merchandise, fasilitas internal).

    • Proses settlement (siapa yang memotong stok, siapa yang mengganti biaya).

    • Anti‑fraud (cek duplikasi/timing). Refund bila gagal.

    • Role matrix, approval flow, ekspor CSV, dan audit trail.

    • Anomaly detection (mis. lonjakan transfer di jam tidak lazim).

    • Komponen UI sederhana: daftar Reward, form transfer, katalog redeem, riwayat transaksi.

    • Error state yang jelas (kuota habis, jaringan offline, dsb.).

    • Offline handling (antrian, retry).


    • Security: Standar praktik aman aplikasi web (contoh panduan OWASP ASVS), manajemen kunci, rotasi rahasia.

    • Performance: Target respons cepat (p95 < 2 detik), dan proses transaksi selesai < 5 detik.

    • Availability: Target ketersediaan ≥ 99,5%; jika ada gangguan, layanan degrade gracefully.

    • Compliance/Audit: Logging, retensi data, jejak perubahan terkelola.


    1. Blockchain core & Smart Contracts (source code, test, skrip deploy).

    2. API service (containerized) + OpenAPI docs.

    3. Admin dashboards (issuer/treasury/reports).

    4. Dokumentasi lengkap: BRD, FSD, Arsitektur, Runbook, UAT, User/Admin Manual.


    • Project Manager — timeline, risiko, koordinasi stakeholder.

    • Blockchain Architect — desain jaringan, keamanan, tata kelola.

    • Smart Contract Developer — pengembangan Solidity + review/audit.

    • Backend/API Developer — service, integrasi, monitoring.

    Lengkapi dengan nama personil, ringkas CV, dan alokasi FTE per fase.


    • Phase 0 — Discovery (2–3 minggu): BRD/FSD, persetujuan desain.

    • Phase 1 — Build (6–8 minggu): chain + contracts + API + dashboards.

    • Phase 2 — UAT (2 minggu): skenario uji, perbaikan, persetujuan.

    • Phase 3 — Launch (1 minggu): produksi + Hypercare (4 minggu).

    Gunakan tanggal absolut agar sinkron dengan change window TI PERURI.


    Role
    Qty
    Durasi
    Rate
    Subtotal
    Item
    Spec
    Qty
    Term
    Rate
    Subtotal
    Item
    Qty
    Subtotal

    • Kriteria UAT disepakati HR + TI; hasilnya ditandatangani.

    • Serah terima operasional: node, keys, runbook, dashboard monitoring.

    • Garansi: {{MASA_GARANSI}} dengan SLA/respon time terdefinisi.


    • Penyalahgunaan kuota → batas harian/mingguan + alert anomali + audit rutin.

    • Kompromi kunci → kebijakan HSM/penyimpanan aman, rotasi, multisig, prinsip least‑privilege.

    • Drift integrasi → contract test, API versioning, staging yang disiplin.

    • Vendor lock‑in → standar terbuka, serah‑terima source, knowledge transfer.


    • Blockchain: Buku besar digital (ledger) yang mencatat transaksi secara berurutan dan sulit diubah.

    • Permissioned Network: Jaringan privat; hanya pihak yang diizinkan yang dapat menjadi validator.

    • Validator: Server yang memvalidasi dan menyetujui blok transaksi.

    • IBFT 2.0: Mekanisme kesepakatan (consensus) berbasis otoritas; blok yang disetujui bersifat final (tidak fork).


    • Hyperledger Besu (Docs/Official): https://besu.hyperledger.org/

      • Private/Permissioned Networks: https://besu.hyperledger.org/private-networks

      • Start node & system requirements: https://besu.hyperledger.org/private-networks/get-started/start-node

    • OpenAPI Initiative: https://www.openapis.org/


    • RewardToken.sol

      • Menyimpan saldo Reward per karyawan.

      • Event: Issued, Transferred, Redeemed, Burned.

    Catatan: Implementasi teknis (Solidity, test, gas policy) akan dilampirkan di repositori teknis saat Development Phase.


    1. Login ke mobile app via Peruri Connect.

    2. Buka Transfer Reward, pilih rekan kerja, masukkan jumlah (mis. 5 poin).

    3. Sistem cek kuota & cooldown → jika OK, transaksi dibuat.

    4. Backend mengirim transaksi ke Blockchain (Besu) → finality < 5 detik.


    References:


    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 . 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.


    INTERNATIONAL PAYMENTS & ESCROW ROLEPLAY

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    1) International Transfers (No Escrow) — Role-Play Materials

    1.1) ROLE CARDS — GROUP 1 (BANK RAILS)

    Skenario: Kirim-kiriman uang lintas negara memakai jalur bank/fintech (privat, berlapis). Aturan umum: Peserta TIDAK boleh mendengar percakapan teller–nasabah; mereka hanya melihat pergerakan.

    CARD A — NASABAH PENERIMA (Negara X)

    • Lokasi: Duduk di kursi peserta.

    • Tugas:

      1. Tunggu panggilan dari Teller Bank Penerima (B).

      2. Datangi B untuk “menerima kiriman” tiap kali dipanggil.

      3. Jangan umumkan nominal ke publik. Kembali ke tempat duduk.

      4. Di akhir sesi, sebutkan berapa kali Anda menerima kiriman (jumlah transaksi, bukan nominal).


    • Lokasi: Duduk di depan kelas (meja teller).

    • Tugas:

      1. Terima slip/uang dari teller bank pengirim (D/F/H/J).

      2. Panggil A untuk menerima kiriman (tanpa menyebut nominal).


    • Teller Anda: D (untuk C), F (untuk E), H (untuk G), J (untuk I) — duduk depan.

    • Tugas:

      1. Siapkan jumlah kiriman (pakai Slip Transfer).

      2. Datangi teller pengirim Anda; serahkan slip/uang (fiktif).


    • Lokasi: Duduk di depan kelas (meja teller).

    • Tugas:

      1. Terima slip dari nasabah pengirim (C/E/G/I).

      2. Terapkan biaya/FX sederhana (contoh: 2% biaya + 1% kurs) — tulis di slip


    Skenario: Kirim-kiriman uang lintas negara memakai jaringan blockchain (publik, broadcast, konfirmasi). Aturan umum: Node harus mengulang keras transaksi yang didengar (broadcast).

    • Lokasi: Duduk di kursi peserta.

    • Tugas:

      1. Dengarkan saat node mengumumkan transaksi ke Address A.

      2. Saat fasilitator menyatakan transaksi FINAL, angkat tangan sebagai tanda dana diterima.


    • Lokasi: Tersebar merata di kelas (jangan bergerombol).

    • Tugas:

      1. Jika ada peserta pengirim (non-relawan) berbisik di dekat Anda:

        “K → A : 1 juta” segera UMUMKAN keras: “K → A : 1 juta!”


    Gunakan formulir ini untuk setiap kiriman Grup 1 (bisa diperbanyak fotokopi).

    Tips fasilitator: siapkan 20–30 lembar agar cukup untuk beberapa transaksi dan latihan paralel.


    • Catat total transaksi (tanpa detail nominal per transaksi).

    • Tulis biaya total & estimasi waktu tempuh rata-rata.

    • Tidak ada pengumuman nominal ke publik.

    RINGKASAN (isi setelah demo):

    • • Jumlah kiriman: …

    • • Estimasi biaya total: …

    • • Estimasi waktu tempuh rata-rata: …


    • Format pencatatan (contoh):

      K → A : 1.000.000 | Fee: 0,5% | Konfirmasi: 5 | Status: FINAL

    • Tambahkan transaksi paralel & gelombang konfirmasi (2x/3x) untuk menunjukan finality.

    DAFTAR TRANSAKSI (isi saat demo):

    • • TX#1: …

    • • TX#2: …

    • • TX#3: …

    • • …


    Tujuan: memperlihatkan perbedaan latensi, transparansi, langkah proses, dan biaya antara Bank Rails (privat) dan Blockchain Rails (publik).

    Durasi saran:

    • Bank Rails: 25 menit

    • Blockchain Rails: 25 menit

    • Debrief & Q&A: 10 menit

    Alat:

    • Role Cards (2 grup × 10 peran), Slip Transfer, Poster PRIVATE & PUBLIC LEDGER, spidol, timer.

    Langkah singkat:

    1. Briefing Grup 1 (Bank) — bagikan CARD A–J; jelaskan aturan privasi.

    2. Jalankan 3 transaksi (1 biasa, 2 paralel) + 1 mini-dispute (opsional); teller pengirim terapkan biaya & FX; teller penerima catat privat.

    3. Briefing Grup 2 (Blockchain) — bagikan CARD A–J; sebar node; jelaskan broadcast & konfirmasi.

    Kata kunci panggung:

    • “Bank rails itu privat; orang luar tidak tahu isi transaksi.”

    • “Blockchain itu publik; pesan transaksi disiarkan sampai konfirmasi.”

    • “Tidak ada yang superior untuk semua kasus; pilih jalur sesuai kebutuhan.”

    (Opsional) Cue singkat fasilitator (±60 detik per grup)

    • Bank: “Perhatikan berapa banyak hop manusia & waktu yang terpakai; publik tidak tahu nominal.”

    • Blockchain: “Dengar broadcast dari beberapa node; setelah konfirmasi cukup, transaksi dianggap final; biaya bisa diumumkan terbuka.”


    Memperagakan perbedaan model kepercayaan, alur rilis dana, transparansi, latensi, dan overhead antara Escrow Tradisional (trusted intermediary) dan Escrow Smart-Contract (rules-as-code), termasuk contoh milestone, time-lock, dan dispute path.

    • Dua segmen (masing-masing ±20–25’) → total ±45–50’ termasuk debrief.

    • Relawan 20 orang → 10 untuk Grup T (Tradisional), 10 untuk Grup S (Smart-Contract).

    • Peserta non-relawan mengikuti sebagai audiens & pendukung (tanpa PII, tanpa transaksi nyata).

    Guardrails

    • Tanpa rekaman • Tanpa data sensitif • Contoh biaya ilustratif • Patuh kebijakan kampus.


    • Lokasi: Duduk sebagai Peserta; bergerak saat diminta AE.

    • Tugas:

      1. Serahkan Deposit (token/simbol) + Slip Deposit ke AE (B).

      2. Tunggu verifikasi dari Verifier (H).


    • Lokasi: Meja depan (mudah terlihat).

    • Tugas:

      1. Terima deposit dari Buyer (A/D/F); tahan dana.

      2. Lepas dana (Release) ke Seller bila Verifier (H) menyatakan Milestone Tercapai


    • Lokasi: Peserta; bergerak saat diminta.

    • Tugas:

      1. Serahkan “hasil kerja/produk” simbolik.

      2. Minta Verifier (H) menilai Milestone.


    • Lokasi: Peserta.

    • Tugas: Sama seperti Buyer1; kasus ini disiapkan untuk sengketa kecil:

      1. Deposit → AE.

      2. Jika kualitas kurang, ajukan Dispute (kartu).


    • Lokasi: Peserta.

    • Tugas:

      1. Ajukan klaim Milestone Tercapai.

      2. Jika ditantang, sampaikan bukti sederhana (kartu/benda) ke Arbiter (I).


    • Lokasi: Peserta.

    • Tugas: Jalankan transaksi paralel untuk menunjukkan antrean/latensi. Deposit → tunggu verifikasi → terima release/refund.


    • Lokasi: Peserta.

    • Tugas: Klaim milestone untuk transaksi paralel (dengan Buyer3).


    • Lokasi: Dekat AE; interaksi privat.

    • Tugas:

      1. Periksa bukti simbolik dari Seller.

      2. Keluarkan Kartu Milestone: Tercapai / Tidak Tercapai → serahkan ke AE.


    • Lokasi: Dekat AE; interaksi privat saat sengketa.

    • Tugas:

      1. Dengar singkat kedua pihak + lihat bukti.

      2. Putuskan: Release / Refund / Parsial.


    • Lokasi: Papan/lembar PRIVATE LEDGER di depan.

    • Tugas:

      1. Catat ID transaksi, waktu, keputusan, biaya admin (tanpa nominal detail).

      2. Di akhir segmen, tulis ringkasan: jumlah transaksi, latensi rata-rata, total biaya admin, jumlah sengketa & hasilnya.


    • Lokasi: Meja depan; memegang Kartu Aturan.

    • Aturan (bacakan singkat saat mulai):

      • Deposit → Hold di kontrak.

      • Release jika Oracle (F) menyatakan Milestone Tercapai


    • Tugas:

      1. Lakukan Deposit token ke Contract (A) (simbolik).

      2. Tunggu hasil Oracle (F) → terima Refund jika gagal, atau Release ke Seller (C) jika tercapai.


    • Tugas:

      1. Kirim “hasil kerja/produk” simbolik.

      2. Menunggu Release dari Contract (A) setelah Oracle (F) “OK”.


    • Tugas: Jalankan transaksi kedua untuk skenario time-lock &/atau dispute. Deposit → tunggu → minta Refund jika timer habis atau ajukan Dispute jika perlu.


    • Tugas: Klaim milestone untuk transaksi kedua; siapkan diri jika terjadi Dispute.


    • Tugas:

      1. Nilai bukti & keluarkan Kartu Milestone: Tercapai / Tidak.

      2. Serahkan kartu ke Contract (A).


    • Tugas:

      1. Set timer simbolik (mis. 30–60 dtk).

      2. Saat waktu habis tanpa bukti, beri sinyal Refund ke Contract (A).


    • Tugas:

      1. Umumkan keras setiap event: Deposit / Milestone OK / Release / Refund / Dispute.

      2. Ulangi pengumuman hingga kuorum (≥5 node total bersama I) tercapai.


    • Tugas: Sama seperti H untuk mencapai kuorum & menegaskan FINAL.


    • Lokasi: Papan PUBLIC LEDGER di depan.

    • Tugas:

      1. Tulis urutan event untuk tiap transaksi (S1, S2, S3): Deposit → (Milestone/Time-lock/Dispute) → Release/Refund → FINAL.

      2. Pastikan status akhir terlihat publik.


    Slip Deposit

    Slip Release / Refund

    Kartu Milestone

    Kartu Dispute

    Poster — PRIVATE LEDGER (Tradisional)

    Poster — PUBLIC LEDGER (Smart-Contract)


    • Segmen T (±20’): T1 biasa (Release), T2 paralel, 1 Dispute kecil → rekap di PRIVATE LEDGER.

    • Segmen S (±20’): S1 (Milestone OK → Release), S2 (Time-lock → Refund), S3 (Dispute → Fallback) → rekap di PUBLIC LEDGER.

    • Debrief (±8’): Trust model, transparansi, latensi, overhead, failure modes, kaitkan ke materi utama.


    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 . 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.


    BGC X IBLOOMING WORKING PRESENTATION

    The goal of this session is to give a clear and structured picture of where the BGC × iBLOOMING integration currently stands — not in terms of document completeness, but in terms of system architectur


    Here we provide the SLIDE PRESENTATION, 6–8 MINUTE SCRIPT, and CLOSING that is very concrete and not floating, all of which have been integrated with:

    • ✔️

    • ✔️

    • ✔️

    Pool reward

    $509,239.09

    Historical cash-out

    $572,221.19

    Internal credit spend

    $567,234.00

    Archived v0.1

    SIMALPHA

    Working MVP

    Reports

    Preliminary evidence

    LIVING Doc

    Close after transition update

    Master Document

    Active founder decision source

    Ilustrasi 1 oleh Prof. NOTA Inc. - Grafik by Department dan by Year
    Ilustrasi 1 oleh Prof. NOTA Inc. - Grafik by Experience dan by Interest
    saat darurat.
  • S5 — Audit & Laporan. Dashboard real‑time, ekspor data, dan jejak audit per transaksi.

  • Fitur kunci: mint/burn; transfer P2P dengan kuota & cooldown; pause/resume; role‑based access; event untuk audit/log.

    Spesifikasi VM awal (per node): 4 vCPU, 8 GB RAM, 200 GB SSD (disesuaikan hasil uji beban).

    GET /ledger/tx/:id — cek detail transaksi.
  • GET /reports/summary — ringkasan agregat (periode, unit kerja, dsb.).

  • Observability: Metrik + log + alert yang ditindaklanjuti tim on‑call.

    Pelatihan & KT (bahan + rekaman bila diizinkan).

  • Laporan bulanan, Final report, Masa garansi & support sesuai SLA.

  • QA (Fungsional) — rencana uji, otomasi, UAT.

  • QA/Security — pen‑test, SAST/DAST, hardening.

  • DevOps — CI/CD, IaC, environment.

  • UI/UX — desain dashboard & alur mobile.

  • {{S_ARCH}}

    Smart Contract Dev

    {{Q_SC}}

    {{D_SC}}

    {{R_SC}}

    {{S_SC}}

    Backend/API Dev

    {{Q_BE}}

    {{D_BE}}

    {{R_BE}}

    {{S_BE}}

    QA (Func)

    {{Q_QA}}

    {{D_QA}}

    {{R_QA}}

    {{S_QA}}

    QA (Sec)

    {{Q_SEC}}

    {{D_SEC}}

    {{R_SEC}}

    {{S_SEC}}

    DevOps

    {{Q_DEVOPS}}

    {{D_DEVOPS}}

    {{R_DEVOPS}}

    {{S_DEVOPS}}

    {{Q_TX}}

    {{TERM}}

    {{RATE_TX}}

    {{SUB_TX}}

    BAS/Indexer

    4 vCPU / 8GB / 200GB SSD

    {{Q_BAS}}

    {{TERM}}

    {{RATE_BAS}}

    {{SUB_BAS}}

    1

    {{SUB_MAN}}

    Monthly & Final Report

    1

    {{SUB_REP}}

    Reward Token: Satuan poin digital untuk sistem penghargaan (bukan koin untuk trading).

  • API: Antarmuka untuk aplikasi saling berkomunikasi (mis. mobile app ↔ backend ↔ blockchain).

  • OAuth 2.0 / JWT: Mekanisme otorisasi & format token akses untuk memastikan hanya pengguna yang berhak yang bisa memakai API.

  • OpenAPI: Cara standar menulis dokumentasi API yang bisa dibaca manusia & mesin.

  • Prometheus/Grafana: Alat untuk mengumpulkan metrik dan menampilkan dashboard monitoring.

  • OAuth 2.0 (official community site): https://oauth.net/2/

  • JWT — RFC 7519 (IETF): https://datatracker.ietf.org/doc/html/rfc7519

  • Node.js: https://nodejs.org/

  • TypeScript: https://www.typescriptlang.org/

  • Prometheus: https://prometheus.io/

  • Grafana: https://grafana.com/

  • Treasury.sol

    • Tempat mint/burn resmi; kontrol oleh Admin/Issuer sesuai kuota.

  • Redemption.sol

    • Menyimpan katalog dan memotong saldo saat redeem; event RedeemRequested, RedeemSettled/Refunded.

  • PolicyRegistry.sol

    • Menyimpan aturan kuota/cooldown/role; bisa diperbarui lewat approval.

  • Penerima melihat saldo bertambah; event muncul di Riwayat & Dashboard.

  • Tanggapan & Jawaban Pertanyaan Follow-Up dari Peruri

  • Rencana Teknis Pengerjaan

  • Peruri Connect Spec Eksekusi v1

  • Uraian SDM - Peruri Connect X Blockchain

  • Proposal Peruri Connect X Blockchain - EN

  • Project Manager

    {{Q_PM}}

    {{D_PM}}

    {{R_PM}}

    {{S_PM}}

    Blockchain Architect

    {{Q_ARCH}}

    {{D_ARCH}}

    Validator Node VM

    4 vCPU / 8GB / 200GB SSD

    {{Q_VAL}}

    {{TERM}}

    {{RATE_VAL}}

    {{SUB_VAL}}

    Tx Node VM

    BRD, FSD, Dev Plan

    1

    {{SUB_DOC}}

    Source + Config Packages

    1

    {{SUB_SRC}}

    UAT Docs & Sessions

    1

    {{SUB_UAT}}

    1) Sasaran & Indikator Keberhasilan

    2) Ruang Lingkup Pekerjaan (Scope of Work)

    2.1 Analisis & Desain

    2.2 Blockchain Core & Smart Contracts

    2.3 Integration Layer (Services/API)

    2.4 Treasury & Admin Tools

    2.5 Keamanan & Audit

    2.6 Enablement

    2.7 Support & Maintenance

    3) Arsitektur Teknis — Penjelasan Gamblang

    3.1 Kenapa Hyperledger Besu + IBFT 2.0?

    3.2 Topologi Dasar

    3.3 Identitas & Akses

    3.4 Data & Privasi

    3.5 Kontrak API (Sketsa Awam)

    4) Kebutuhan Fungsional (Functional Requirements)

    4.1 Issue (Penerbitan)

    4.2 P2P Recognition (Transfer)

    4.3 Redeem

    4.4 Admin & Reporting

    4.5 Integrasi Mobile

    5) Non‑Functional Requirements (NFR) — Bahasa Sederhana

    6) Deliverables (Apa yang PERURI terima)

    7) Organisasi Proyek & Peran

    8) Timeline (Contoh)

    9) Budget (BOQ Skeleton)

    A. Implementation (Man‑Months)

    B. Validator/Node (Tahunan/Periode Proyek)

    C. Dokumentasi & Pelatihan

    10) Acceptance & Handover

    11) Risiko & Mitigasi (Contoh)

    12) Glosarium (Untuk Pembaca Non‑Teknis)

    13) Referensi Resmi (Official Links)

    Lampiran A — Skema Kontrak (Garis Besar, Bahasa Umum)

    Lampiran B — Contoh Alur 1 Menit

    Kajian Transformasi Sistem Reward Digital
    Ringkasan Eksekutif
    Narasi Pitch Singkat
    Proposal Kerja
    Prof. NOTA

    {{R_ARCH}}

    4 vCPU / 8GB / 200GB SSD

    User/Admin Manuals

    Simulasi Tanggapan

    export reports for founder discussion.

    an exchange;

  • a legal or tax engine;

  • an audited accounting system.

  • duplicate-run governance;

  • comparison;

  • data-versus-assumption separation;

  • report generation;

  • PDF export;

  • founder-oriented summaries.

  • real top earners;

  • P95 or P99 by person;

  • member-level referral behaviour;

  • individual cash-out behaviour;

  • longitudinal cross-application activity.

  • $4,034,038.00

    $6,335.10

    $4,040,373.10

    Internal credit or sink spend

    $567,234.00

    $0.00

    $567,234.00

    PC volume

    403,403,617

    0

    403,403,617

    SP reward basis

    2,823,835

    0

    2,823,835

    Global/direct reward

    $411,385.60

    $1,429.46

    $412,815.06

    Pool reward

    $508,288.57

    $950.52

    $509,239.09

    Historical cash-out

    $546,506.11

    $25,715.08

    $572,221.19

    outstanding PC;

  • reward liability;

  • pool liability;

  • reserve restrictions.

  • 0.25×

    Conservative

    185,770.06

    35,690.04

    37,558.99

    112,521.03

    $4,002,814.11

    0.24×

    Growth

    304,155.10

    56,173.06

    85,512.27

    162,469.77

    $3,954,860.83

    0.25×

    Stress

    128,168.01

    24,016.75

    29,569.66

    74,581.59

    $4,010,803.44

    0.24×

    raises cash-out friction.

    reserve;

  • PC liability;

  • intercompany movements.

  • member-level Gini;

  • member-level P95/P99.

  • whether a proposed rule should be studied further.

    OpEx;

  • reserve;

  • intercompany transfers.

  • product-market evidence.

    run the model;

  • review warnings and missing evidence;

  • compare with a no-token control;

  • export the result;

  • attach a Decision Note;

  • obtain named approval before changing any live system.

  • separate historical cash-out from modeled release;

  • document aggregate-data limitations;

  • rename Stress interpretation.

  • add no-token control.

    product-passport adoption;

  • conventional-versus-Web3 cost.

  • OpEx increase;

  • reserve limitation.

  • Cash in

    $4,034,038.00

    $21,117.00

    $4,055,155.00

    Recognized-revenue field

    $4,034,038.00

    $6,335.10

    $4,040,373.10

    Baseline

    253,462.58

    47,250.55

    70,138.55

    136,073.48

    Preliminary Pass

    Run completed and did not cross current model thresholds

    Material Review Required

    One or more model or evidence risks require review

    Model-Detected Risk

    Current assumptions create a model threshold breach

    Insufficient Evidence

    No responsible implementation conclusion can be made

    2. What SIMALPHA Is

    3. What Has Been Successfully Built

    4. Current Dataset

    4.1 Profile

    4.2 Consequence

    5. Aggregate Data Snapshot

    5.1 Important Interpretation

    6. First Scenario Results

    7. Correct Scenario Interpretation

    7.1 Baseline

    7.2 Conservative

    7.3 Growth

    7.4 Stress

    8. Report Corrections

    8.1 Verdict Labels

    8.2 ALPHA Definition

    8.3 Cash-Out Label

    8.4 “PC and SP Go In, ALPHA Comes Out”

    8.5 Net Cash

    8.6 User and Fairness Metrics

    9. Reconciliation Gaps

    10. What SIMALPHA Can Support Today

    11. Evidence Gates

    Gate 0 — Data and Model Integrity

    Gate 1 — Historical Replay

    Gate 2 — Economic and Accounting Reconstruction

    Gate 3 — Product-Demand Evidence

    Gate 4 — Policy Simulation

    Gate 5 — Tokenization Comparison

    Gate 6 — Legal, Tax, Technical, and Founder Approval

    12. Founder Use Guide

    Step 1 — Read the Evidence Status

    Step 2 — Ask What Changed

    Step 3 — Ask What the Output Excludes

    Step 4 — Compare With a No-Token Control

    Step 5 — Record a Decision

    13. Operator Workflow

    14. Remediation Backlog

    Priority 0 — Before Further Founder Reliance

    Priority 1 — Model Integrity

    Priority 2 — Historical Replay

    Priority 3 — Product-Led Simulation

    Priority 4 — True Stress Tests

    15. Final Status

    Prof. NOTA

    Gross-margin field

    $3,970,234.55

    Catat waktu terima & jumlah di ledger privat (kertas Anda).

  • Jangan umumkan biaya/FX ke publik (semua info privat).

  • Di akhir sesi, laporkan total transaksi (jumlah kiriman) dan total biaya yang Anda catat (privat).

  • Ikuti arahan teller (mungkin ada biaya/FX).

  • Jangan mengumumkan nominal ke publik. Kembali ke tempat duduk.

  • .
  • Jalan ke Teller Penerima (B) untuk menyerahkan kiriman.

  • Kembali ke meja; ulangi jika ada kiriman berikutnya.

  • Catatan: Jangan umumkan nominal. Semua privat.

  • Jangan mengumumkan apa pun selain tanda angkat tangan.

    Jika Anda mendengar node lain mengumumkan transaksi, ULANGI pengumuman itu.

  • Teruskan hingga fasilitator menyatakan “cukup konfirmasi” (contoh: ≥ 5 node berbeda mengumumkan).

  • Jaga kejelasan; jangan ubah isi pesan.

  • Jalankan 3 transaksi (1 biasa, 2 paralel); node broadcast sampai kuorum (mis. ≥5 node); fasilitator catat di PUBLIC LEDGER.

  • Debrief: bandingkan apa yang diketahui publik, waktu tempuh, dan biaya; jembatani ke materi inti.

  • Jika ada masalah, boleh angkat Kartu Dispute.

  • Terima Release/Refund dari AE sesuai keputusan.

  • .
  • Jika terjadi sengketa, jalankan keputusan Arbiter (I) → Release/Refund/Parsial.

  • Kerja bareng Clerk (J) untuk PRIVATE LEDGER (waktu, keputusan, biaya admin). Jangan sebut nominal secara publik.

  • Terima Release dari AE bila Tercapai.

    Ikuti keputusan Arbiter (I).

    Sampaikan keputusan ke AE & Clerk (J).

    .
  • Time-lock: jika tidak tercapai hingga durasi X, lakukan Refund.

  • Dispute path: bila sengketa, gunakan fallback (decision oleh fasilitator/arbiter terpilih).

  • Tugas eksekusi: terima Deposit, jalankan Release/Refund sesuai bukti/time-lock/fallback; beri sinyal ke Nodes (H/I) untuk diumumkan.

  • CARD B — TELLER BANK PENERIMA (Negara X)

    CARD C / E / G / I — NASABAH PENGIRIM (Negara Y)

    CARD D / F / H / J — TELLER BANK PENGIRIM (Negara Y)

    1.2) ROLE CARDS — GROUP 2 (BLOCKCHAIN RAILS)

    CARD A — WALLET PENERIMA (Address A)

    CARD B / C / D / E / F / G / H / I / J — NODE (Validator/Relay)

    1.3) SLIP TRANSFER — Bank Rails (template)

    1.4) LEDGER POSTERS — PRIVATE vs PUBLIC

    PRIVATE LEDGER — BANK RAILS

    PUBLIC LEDGER — BLOCKCHAIN RAILS

    1.5) RUN SHEET — Fasilitator (ringkas)

    2) International Transfers (Escrow) — Role-Play Materials

    2.1) Tujuan dan Format

    2.2) ROLE CARDS — Grup T (Escrow Tradisional)

    CARD A — Buyer1

    CARD B — AE (Agen Escrow)

    CARD C — Seller1

    CARD D — Buyer2

    CARD E — Seller2

    CARD F — Buyer3

    CARD G — Seller3

    CARD H — Verifier

    CARD I — Arbiter

    CARD J — Clerk (Private Ledger)

    2.3) ROLE CARDS — Grup S (Escrow Smart-Contract)

    CARD A — Escrow Contract

    CARD B — Buyer Wallet 1

    CARD C — Seller Wallet 1

    CARD D — Buyer Wallet 2

    CARD E — Seller Wallet 2

    CARD F — Oracle / Verifier

    CARD G — Timekeeper

    CARD H — Node / Confirmer

    CARD I — Node / Confirmer

    CARD J — Recorder (Public Ledger)

    2.4) Slip & Poster (Template Cetak)

    2.5) Jalankan Singkat (opsional untuk fasilitator)

    Prof. NOTA
    source field
    → import mapping
    → model variable
    → formula
    → report line
    → founder interpretation
    SLIP TRANSFER (BANK RAILS)
    PENGIRIM: ____________      TELLER PENGIRIM: ____________      NEGARA: ____________
    PENERIMA: A (Negara X)      TELLER PENERIMA: B
    JUMLAH (IDR): ______________________
    BIAYA (≈2%): ______________    FX/KURS (≈1%): ______________
    WAKTU SETOR: ____________    WAKTU TERIMA: ____________    TANDA TELLER: ____________
    CATATAN: ______________________________________________________________
    Transaksi ID: ______   Buyer: ______   Seller: ______
    Escrow: AE / Contract     Waktu Setor: ______
    Nominal (simbolik): ______      Catatan: ______
    Transaksi ID: ______   Keputusan: Release / Refund / Parsial
    Otoritas: AE / Contract / Arbiter
    Waktu Eksekusi: ______   Catatan: ______
    Transaksi ID: ______
    Status: TER CAPAI / TIDAK TER CAPAI
    Verifier/Oracle: ______   Waktu: ______
    Transaksi ID: ______
    Pihak pengaju: Buyer / Seller
    Bukti (sebutkan): _______________________
    • #Transaksi: ____    • Est. latensi rata-rata: ____    • Est. biaya admin total: ____
    • #Sengketa: ____     • Hasil (Release/Refund/Parsial): ____
    (Detail nominal & percakapan: PRIVAT)
    TX S1: Deposit Buyer1→Contract | Milestone OK | Release→Seller1 | FINAL
    TX S2: Deposit Buyer2→Contract | Time-lock expired | Refund→Buyer2 | FINAL
    TX S3: Deposit Buyer2→Contract | Dispute→Fallback→(Putusan) | FINAL

    WEB3LOGIN Doc ✔️

  • LIVING Doc ✔️

  • And the Bullnium (USD 52K) quotation analysis that was requested.


  • Objective Today:

    • Clarify system progress (documents, architecture, simulation plan)

    • Align Phase-1 scope

    • Review vendor quotation (Bullnium)

    • Request explicit founder decisions


    Thank you, everyone, for your time today.

    The goal of this session is to give a clear and structured picture of where the BGC × iBLOOMING integration currently stands — not in terms of document completeness, but in terms of system architecture, alignment, and decision readiness for Phase 1.

    We will look at four things today:

    • (1) the progress across all documents and flows;

    • (2) the architecture and simulation plan;

    • (3) the vendor quotation review;

    • and (4) the specific decisions needed from founders.


    1. UNDERSTANDING Doc — Source of truth for:

      • Affiliate system, PC/SP definitions, SP-based payout, pools, reward mechanics

      • Business rules that must remain AS-IS

    2. WHITEPAPER Doc v1 (draft) — Value-flow principles & ALPHA settlement layer

    3. — PC/SP → ALPHA conversion, event model, policy parameters

    4. — Unified identity, wallet provisioning, AA (Smart Account) mapping

    5. — Strategic Objectives & constraints

    Together, these form the system architecture for Phase 1.


    All the work so far is grounded in five core documents that together form the foundation of Phase 1.

    The first is the UNDERSTANDING Doc, which defines the operational reality of BGC and iBLOOMING today — how PC is created and consumed, how SP functions, how USD payouts are calculated, and the roles of LTS, RR, GR, GPSP, WEC, Miracle Cash, and CP. These AS-IS rules are essential because they must remain unchanged.

    The second is the Whitepaper draft, which establishes the conceptual and compliance framework — including ALPHA as a non-transferable rights unit and the value-flow principles.

    The third is the Tokenflow draft, which defines the PC/SP → ALPHA conversion logic, the event model, the append-only flow, and policy parameters.

    The fourth is the Web3 Login document, which defines how identity, wallet provisioning, and Smart Account mapping must work.

    And lastly, the Living Doc, which contains the strategic objectives and constraints guiding the entire system.

    These five documents collectively define the architecture for Phase 1.


    1. UNDERSTANDING Doc Consolidation

    • Cleaned structural logic for PC, SP, LTS, RR/GR, MC, GPSP, WEC, and CP flows.

    • Identified AS-IS rules that cannot change.

    2. System Architecture (Three-Layer Model)

    • Layer 1: BGC Core Business (PC, SP, payouts)

    • Layer 2: iBLOOMING Identity & Demand Engine

    • Layer 3: On-Chain Layer (ALPHA, EventHub, AA-based wallet registry)

    3. Whitepaper Structure

    • Executive summary, problem–solution map, KPIs, compliance frames, fairness metric (Reward Gini).

    • Core concept: PC/SP → ALPHA rights → spend/access/stake (non-transferable).

    4. Tokenflow Skeleton

    • Conversion rules

    • Cash-out windows (KYC, quarterly, 7 days, min $50)

    • Append-only event model

    5. Simulation Plan

    • 24-month data

    • Conversion stress-test

    • Parameter selection (fairness, sustainability)


    Here is the work that has already been completed.

    First, the UNDERSTANDING Doc has been fully consolidated. All structural logic for PC, SP, LTS, RR/GR, GPSP, WEC, and CP flows has been clarified, and the AS-IS rules that cannot be changed are now clearly identified.

    Second, the system has been organized into a three-layer architecture:

    • (1) the BGC Core Business Layer,

    • (2) the iBLOOMING Identity and Demand Engine,

    • and (3) the On-Chain Layer with ALPHA settlement, EventHub, and Smart Accounts.

    Third, the Whitepaper has a complete structural foundation — including its executive summary, problem–solution framing, KPIs, compliance narratives, and fairness metrics such as Reward Gini. Its core principle remains: PC/SP converts into ALPHA rights, which are non-transferable and tied to spend/access/stake actions.

    Fourth, the Tokenflow skeleton is established:

    • conversion rules, cash-out windows, KYC requirements, quarterly schedules,

    • and an append-only event model.

    And fifth, the simulation plan is ready. It will use 24 months of historical data to test parameter ranges, validate fairness, and ensure sustainability.


    • Layer 1: BGC Core (AS-IS)

      • PC = proof of physical product / multi-level selling compliance

      • SP = base for USD payouts (RR/GR/GPSP/etc.)

    • Layer 2: iBLOOMING Demand Engine

      • Classes, features, boosts (ALPHA sinks)

      • CP digital products

      • Reward multipliers & ecosystem utility

    • Layer 3: On-Chain Layer (Phase 1 Minimal)

      • ALPHA settlement layer

      • Non-transferable ERC-20 interface; mint/burn controlled

      • EventHub: append-only ledger (hashed proofs)

    This allows auditability + low friction without over-complicating the system.


    This is the architecture that emerges from the documents.

    Layer 1 is the BGC Core — PC as proof of physical product and compliance for multi-level selling, and SP as the base for USD payouts through RR, GR, GPSP, and related mechanics.

    Layer 2 is the iBLOOMING Demand Engine — which includes classes, features, boosts as ALPHA sinks, digital CP products, and reward multipliers that generate ecosystem utility.

    Layer 3 is the On-Chain Layer, in a minimal Phase-1 form — a controlled ALPHA settlement contract, non-transferable ERC-20 behavior, an EventHub that records hashed proofs in an append-only format, a Wallet Registry mapping users to EOA or Smart Accounts, and sponsored gas limits that allow smooth UX without over-exposing the system.

    This combination provides auditability without adding unnecessary friction.


    1. Goals

    • Unified login for all users (Web2 → Web3)

    • Automatic wallet provisioning (EOA + optional AA)

    • Binding identity to EventHub records

    • Reduce friction for ALPHA usage

    1. Technical Design

    • Choose from modern providers (Thirdweb / Privy / Reown)

    • Minimize custom smart contracts

    • Use sponsored gas for onboarding and key ALPHA actions

    • Enforce rate-limits + device rules (anti-Sybil) (Referral cooldown 1 day; max 10 Tier-1 joins/day)

    This matches the WHITEPAPER and TOKENFLOW documents.


    Next is Web3 Login, which ties the system together at the identity level.

    The goals are simple:

    • a unified login that works for all users,

    • automatic wallet provisioning using either EOA or optional Smart Accounts,

    • binding user identity to EventHub records,

    • and enabling ALPHA actions with minimal friction.

    Technically, the design uses modern providers such as Thirdweb, Privy, or Reown. This reduces the need for custom contracts, keeps onboarding simple, and allows gas sponsorship for key ALPHA actions.

    We also enforce rate-limits and device rules — including anti-Sybil protections such as referral cooldowns and maximum Tier-1 joins per day.

    This design is fully aligned with the Whitepaper and Tokenflow documents.


    • What Bullnium Proposes

      • Custom Web2/Web3 login

      • Custom Smart Accounts + Paymaster

      • Smart Contract factory

      • Identity service

      • Telemetry system

      • 6-month timeline

      • Optional audit +12K 📄 (Based on Bullnium Quotation PDF)

    • Assessment

      • Price is reasonable for full custom build.

      • But scope is too heavy for Phase-1.

      • Many components duplicate provider features.

    • Conclusion for Phase-1 Use modular provider-based integration → faster (4–6 weeks), safer, lower risk, better aligned with documents.


    We also reviewed the quotation from Bullnium for USD 52,000.

    They propose a full custom build — custom Web2/Web3 login, custom Smart Accounts with Paymaster, a Smart Contract factory, identity services, and telemetry, with a six-month timeline and optional audit.

    The price is reasonable for a full custom build, but the scope is far larger than what Phase 1 requires. Many components overlap with what provider-based solutions already offer. And a six-month delivery is too slow for our roadmap.

    So for Phase 1, the modular provider-based approach is faster (four to six weeks), safer, and more aligned with the documents we have.


    • Needs founder decisions:

      1. PC/SP → ALPHA detailed parameters (beyond v1 defaults)

      2. Cash-out frequency & thresholds post-pilot

      3. Governance: who controls AlphaController

      4. Web3 Login provider choice

      5. Simulation parameter acceptance

      6. Bullnium vs modular vendor decision

      7. Priority order of deliverables

    • Already defined structurally:

      • All flows

      • All event models

      • All policy scaffolding

      • All compliance guardrails


    At this point, the structure across all documents is complete. What is not final are the parameters and decisions that must come from the founders.

    These include:

    • the detailed PC/SP → ALPHA parameters,

    • cash-out frequency and thresholds after pilot,

    • governance for the AlphaController,

    • provider selection for Web3 Login,

    • simulation parameter acceptance,

    • the decision between Bullnium or the modular approach,

    • and the order of deliverables.

    What is already defined are the flows, the models, the scaffolding, and the guardrails. What remains is alignment on the choices.


    • Decision 1 — Select Development Approach

      • A: Modular (recommended) → 4–6 weeks

      • B: Bullnium custom build → 6 months

    • Decision 2 — Prioritize Deliverable Order Choose one:

      • Whitepaper v1 first

      • Tokenflow v1 first

      • Simulation output first (These three depend on each other — sequence must be fixed.)

    • Decision 3 — Cash-Out Policy (Pilot v1) Approve or adjust:

      • 4× per year

      • 7-day window

      • Min $50

    • Decision 4 — Web3 Login Provider

      • Thirdweb / Privy / Reown (Fully custom implementation only if founders insist.)

    • Decision 5 — Governance Holder for AlphaController

      • Company?

      • Technical founder?

      • Multi-sig?

      • Hybrid?

    • Decision 6 — Approval to Move to Document Finalization Whitepaper v1 + Tokenflow v1 + Simulation v1.


    To move forward efficiently, there are six concrete decisions that founders need to make now for Phase 1.

    First, choose the development approach for Web3 Login:

    • a modular provider approach — which is faster and recommended

    • or the Bullnium custom build, which will take six months.

    Second, set the priority order of deliverables:

    • Whitepaper v1 first,

    • Tokenflow v1 first,

    • or Simulation results first.

    These three depend on each other, so the sequence must be fixed.

    Third, approve the Pilot v1 cash-out policy — quarterly windows, seven-day duration, minimum fifty dollars, one percent fee, and mandatory KYC — or adjust it.

    Fourth, select the provider for Web3 Login: Thirdweb, Privy, or Reown.

    Fifth, assign governance of the AlphaController: the company, a technical founder, a multisig, or a hybrid model.

    And sixth, give approval to finalize Whitepaper v1, Tokenflow v1, and Simulation v1 after these parameters are aligned.

    These decisions will allow the drafts to evolve into final documents ready for execution. Once alignment is reached, Phase-1 implementation can proceed quickly and cleanly.

    Thank you.


    • Q: Why are documents not final?

      Because parameters require explicit founder decisions.

    • Q: Does Bullnium make sense?

      Price yes; scope no. The scope is too big for Phase 1.

    • Q: Why modular login?

      4–6 weeks vs 6 months. Lower risk, aligned with docs.

    • Q: Is ALPHA a token?

      ALPHA is a non-transferable rights unit; not for trading.

    • Q: Does this change BGC’s USD payouts?

      No — AS-IS rules remain exactly the same. (UNDERSTANDING Doc)

    • Q: What’s the biggest blocker now?

      Missing founder decisions on parameters & priority order.

    • Note 1:

      “We have structured and synchronized all system documents — UNDERSTANDING, Whitepaper, Tokenflow, Web3 Login, and the simulation plan — so they no longer contradict each other.”

    • Note 2:

      “Our work has been architectural and integrative: consolidating logic, designing flows, defining parameters so implementation can proceed without rework.”

    • Note 3:

      “We coordinated cross-document consistency so that any provider — internal or external — can implement without ambiguity.”


    • The founders accepted the current architecture as the baseline for Phase 1.

    • The full document set (Understanding Doc, Whitepaper v1 draft, Tokenflow v1 draft, Web3Login Doc, Living Doc) is now recognized as the official system foundation.

    • Simulation work was acknowledged as a mandatory first step before any numerical parameters or formulas can be finalized.

    • No structural objections were raised; founders engaged only in clarification and refinement.


    • Founders will make the key decisions: parameters, governance, cash-out rules, provider selection, and development approach.

    • Prof. NOTA will continue to serve as system architect: consolidating logic, producing Simulation Doc, aligning cross-document consistency, and preparing the blueprint for implementation.

    • Yuku’s engineering team is a viable executor for the Web3 Login implementation, assuming modular provider approach is chosen.

    • Weekly coordination cadence (proposed by KK) will be established to maintain momentum and avoid delays.


    1. Cash-Out Windows (User Fairness Concern)

    • Concern raised by Mr. Onggy: users may feel restricted if cash-out windows are limited.

    • Acknowledged as valid from the user point of view.

    • Resolution: unless founders choose otherwise, the system may inherit the existing BGC cash-out model, where rewards accumulate in the e-wallet and users may request cash-out anytime, with weekly processing.

    2. ALPHA Token Clarification

    • Confirmed: ALPHA is not a public token, not tradeable, and not intended for ICO.

    • ALPHA functions as a rights unit inside the BGC × iBLOOMING system and as the basis for simulation.

    • Public token tracks (e.g., iBC / iBTC) are optional and would be handled separately in the future.

    • Maximum supply, emission logic, and sustainability must come from simulation — not assumptions.


    • The architecture is now considered workable and coherent by all founders.

    • Your documents are validated as “the system backbone,” shifting your position from contributor to architectural lead.

    • The founders’ questions demonstrate adoption, not hesitation.

    • The team now shares a unified language for PC/SP, ALPHA, EventHub, Web3 Login, and Tokenflow.

    • Momentum has shifted toward execution, not ideation.



    This section outlines the concrete next steps required to progress from the current architecture toward Phase-1 implementation. It ensures alignment across founders, engineering, and system design.


    Deliverables

    • Simulation Doc v0.1 (structure, objectives, metrics)

    • Parameter table (initial ranges for PC/SP → ALPHA, windows, caps, sinks)

    • Conversion pipeline outline (manual first, automated later)

    • Scenario design (conservative, neutral, aggressive, stress test)

    • Sensitivity analysis (reward sustainability, supply behavior, operational cost impact)

    • Preliminary recommendation ranges for founders to review

    Why Simulation Comes First

    • Determines numerical backbone for Whitepaper v1

    • Fixes conversion formulas in Tokenflow

    • Identifies sustainable emission rates and window strategies

    • Helps founders finalize governance and operational rules

    • Prevents guess-based decision-making


    Contents to be Finalized

    • ALPHA rights definition

    • On-chain vs off-chain boundaries

    • Compliance & risk framing

    • EventHub & identity anchor narrative

    • Token sustainability argument (supported by simulation data)

    • Phase-1 implementation scope

    • Optional long-term track:

      • public token (iBC / iBTC)

      • listing strategy

      • treasury considerations

    Dependencies

    • Must incorporate validated numbers and parameters from simulation.

    • Requires founder approval on governance decisions.


    Contents to be Fixed

    • PC/SP → ALPHA conversion formulas

    • Event model (append-only)

    • Cash-out logic & parameters

    • Anti-Sybil rules

    • Gas sponsorship rules

    • Treasury & reserve logic

    • Emission guards

    • Edge-case handling

    Dependencies

    • Simulation results

    • Whitepaper v1 framing

    • Founders’ decisions on windows, thresholds, and governance


    Companion document to WEB3LOGIN Doc, focused on ALPHA implementation.

    Blueprint Contents

    • Smart contract architecture

      • AlphaController

      • EventHub

      • Wallet Registry

      • Treasury mechanics

    • Non-transferable token model

    • Gas and sponsorship budget model

    • Contract ownership & governance (EOA, multisig, hybrid)

    • On-chain event types & schema

    • Lifecycle flows for:

      • earn → record → convert → spend/access → settle

    • Integration points for engineering team

    • Security considerations and guardrails

    Outcome

    This blueprint becomes a technical handoff for Yuku’s engineering team or any external provider, ensuring consistent implementation across all layers.


    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.


    ✅ I. FULL SLIDE DECK & FULL SCRIPT (6–8 MINUTES)

    UNDERSTANDING Doc
    WHITEPAPER Doc (draft)
    TOKENFLOW Doc (draft)
    KK, sorry I send this in late night.
    
    Anyway, thank you again for coordinating the session earlier.
    Here is my quick summary and the next steps I will take:
    
    1. The founders have aligned on using the current architecture as the baseline.
    2. The Simulation Plan should be completed first, because the outputs will determine the final wording and parameters in the Whitepaper and Tokenflow.
    3. Cash-out policy will follow the existing BGC model unless the founders choose otherwise.
    4. ALPHA will remain an internal rights token; any public token (iBC/iBTC) can be discussed later as a separate track.
    5. For Web3 Login, the modular implementation approach is compatible with the internal engineering team.
    
    My immediate work will be:
    - finalize the Simulation Doc and prepare simulation runs using the 24-month dataset,
    - outline the dependencies for Whitepaper v1 and Tokenflow finalization,
    - prepare a clear Next Steps package for next week’s coordination.
    
    If you want, we can have a short sync call before the weekly meeting to align details.

    Slide 1 — Title

    BGC × iBLOOMING Integration Progress & Alignment (Phase 1)

    Script - Speech by Prof. NOTA

    Slide 2 — Foundations: Documents Overview

    System groundwork comes from 5 documents:

    Script - Speech by Prof. NOTA

    Slide 3 — What Has Been Completed

    High-Level Progress

    Script - Speech by Prof. NOTA

    Slide 4 — Architecture Overview

    Three Layers

    Script - Speech by Prof. NOTA

    Slide 5 — Web3 Login (Implementation View)

    From WEB3LOGIN Doc

    Script - Speech by Prof. NOTA

    Slide 6 — Vendor Quotation Review

    Bullnium Quotation (USD 52K)

    Script - Speech by Prof. NOTA

    Slide 7 — What Is NOT Final Yet

    Not final

    Script - Speech by Prof. NOTA

    Slide 8 — Founder Decisions Required (Very Concrete)

    Founders Must Decide Now (Phase-1 commitments)

    Script - Speech by Prof. NOTA

    ✅ II. Q & A + NOTES

    ✅ APPENDICES

    APPENDIX A — POST-MEETING DEBRIEF (Founder Zoom — Jan 2025)

    A. Alignment Achieved

    B. Responsibilities Clarified

    C. Sensitive Points Raised & Resolved

    D. Strategic Observations

    APPENDIX B — SUMMARY SENT TO KK (Verbatim Copy of Closing Message)

    APPENDIX C — NEXT-STEP DOCUMENT (Phase-1 Roadmap)

    Overview

    PHASE 1 — SIMULATION DOC (Primary Priority)

    PHASE 2 — WHITEPAPER v1 Finalization

    PHASE 3 — TOKENFLOW v1 Finalization

    PHASE 4 — TECHNICAL IMPLEMENTATION BLUEPRINT

    AI& BLUEPRINT DOC

    AI& is a physician-controlled AI assistance system designed to reduce documentation burden, improve consistency of communication, and support evidence navigation in clinical workflows.

    Version 0.1

    • March 2026


    AI& is a physician-controlled AI assistance system designed to reduce documentation burden, improve consistency of communication, and support evidence navigation in clinical workflows.

    AI& is not designed to replace physicians, make autonomous clinical decisions, diagnose patients independently, or communicate with patients without physician approval.

    The system is intended to support physicians by handling repetitive structure so that physicians can focus on clinical reasoning, empathy, and decision-making.


    AI& works behind the screen so physicians can remain fully present with patients.

    The product is built around four core ideas:

    Wallet Registry: maps user → EOA/AA
  • Sponsored gas limits (≈$0.10/user/day; ≈$20 global/day)

  • 6-month delivery = too slow for our roadmap.
  • Higher long-term maintenance burden.

  • All architecture layers

  • All document frameworks

  • Fee 1%
  • Mandatory KYC

  • TOKENFLOW Doc v1 (draft)
    WEB3LOGIN Doc
    LIVING Doc

    Physician remains the decision-maker

  • AI assists structure, not judgment

  • Patient data must be handled with strict boundaries

  • Each physician agent is personalized without becoming uncontrollable


  • The first pilot version of AI& may include:

    • SOAP note draft generation from physician input

    • Structured clinical summary drafting

    • Discharge summary drafting

    • Evidence summarization from approved medical sources

    • Patient education draft generation

    • Follow-up reminder draft generation

    • Physician-controlled discussion prompts for anonymized case reflection

    The first pilot version must not include:

    • autonomous diagnosis

    • autonomous triage

    • medication prescribing

    • emergency decision-making

    • unsupervised patient messaging

    • direct patient-facing chatbot behavior

    • free-form cross-doctor sharing of raw patient data


    A licensed physician using AI& as a clinical assistance layer.

    Depending on implementation maturity:

    • clinic administrator

    • nurse or assistant under role-based permissions

    • compliance or quality reviewer

    • technical operations team with limited non-clinical access

    Patients do not directly operate AI& in the pilot stage.


    AI& should be designed as a modular system.

    A secure interface used by the physician to:

    • enter structured clinical points

    • review AI-generated drafts

    • edit outputs

    • approve final content

    • view references and evidence links

    • review audit history

    A controlled generation layer that transforms structured input into:

    • SOAP note drafts

    • visit summaries

    • education drafts

    • follow-up drafts

    This engine must operate only within predefined templates and approved workflows.

    A retrieval and summarization layer that:

    • searches approved sources

    • returns relevant references

    • summarizes guideline sections

    • links outputs to source material

    A physician-specific configuration layer that determines:

    • specialty

    • preferred documentation style

    • language tone

    • communication templates

    • preferred note structure

    • clinic workflow rules

    A system layer responsible for:

    • access control

    • audit trails

    • approval logs

    • version history

    • data retention rules

    • safety monitoring


    The AI& system may be visualized in five layers:

    Receives physician input.

    Possible forms:

    • typed notes

    • structured forms

    • dictated notes

    • uploaded internal templates

    • checklist-based input

    Prepares the input for safe structured generation.

    Functions:

    • de-identification where possible

    • field validation

    • template routing

    • context tagging

    • clinical workflow mapping

    Produces assistance outputs.

    Functions:

    • structured draft generation

    • controlled summarization

    • evidence retrieval

    • template-aware text generation

    • follow-up checklist generation

    All AI outputs pass through physician review.

    Functions:

    • compare original input vs generated draft

    • edit output

    • approve or reject output

    • request regenerated version

    • record reasoning notes if needed

    Records system behavior and enforces safety.

    Functions:

    • who accessed what

    • when output was generated

    • what was changed

    • who approved final version

    • whether patient-linked data was accessed

    • incident and anomaly logging


    AI& must handle clinical data with strict sequencing.

    A physician completes or begins a patient encounter.

    The physician enters structured clinical points into AI&.

    Examples:

    • chief complaint

    • key findings

    • history highlights

    • assessment points

    • plan elements

    The system classifies the request.

    Possible classes:

    • SOAP drafting

    • discharge summary

    • education note

    • follow-up plan

    • evidence request

    Only the minimum necessary context is passed into the AI task.

    This may include:

    • structured clinical facts

    • specialty context

    • physician template preferences

    • approved clinic communication rules

    The AI engine generates a draft output inside a constrained template.

    The physician edits and approves the output.

    No AI output becomes final without human review.

    The approved version is either:

    • copied into the clinic documentation system

    • exported as a physician-approved draft

    • stored according to retention rules

    The system stores metadata for traceability.


    AI& must follow the principle of minimum necessary data use.

    If needed and permitted by the implementation environment:

    • structured encounter notes

    • non-sensitive demographic basics

    • clinical observations relevant to documentation

    • physician-approved prompt context

    • internal templates and communication standards

    The pilot should avoid or minimize use of:

    • unnecessary patient identifiers

    • full patient record ingestion by default

    • unrelated historical records

    • broad free-text uploads without review

    • open cross-doctor case sharing with identifiable details

    The pilot must not allow:

    • unrestricted copy of the entire EMR into prompts

    • raw data sharing across physician agents

    • patient-identifiable data used for multi-doctor agent training without explicit governance

    • hidden use of patient data for general model retraining


    The AI& system must be built as if clinical trust can shatter from one sloppy shortcut.

    Access must be role-based.

    Examples:

    • physician can access own workspace and approved patient-linked tasks

    • admin can manage users but not view clinical content by default

    • technical team cannot access clinical text unless explicitly authorized and logged

    Use strong authentication measures.

    Examples:

    • unique accounts per user

    • strong password policy

    • optional multi-factor authentication

    • session timeout

    Clinical data should be protected:

    • in transit

    • at rest

    • during backup storage where applicable

    The system must log:

    • logins

    • record access

    • AI generation events

    • edits

    • approvals

    • exports

    • unusual access behavior

    The system must define:

    • what is stored

    • for how long

    • in what form

    • who can delete

    • what must be preserved for audit purposes

    Data should be logically separated by:

    • clinic

    • physician

    • patient context

    • environment (production vs testing)


    AI& should follow these product safety principles:

    No final clinical artifact is released without physician review.

    Outputs are template-bounded wherever possible.

    Evidence summaries should include source references.

    The system should not send messages or finalize notes automatically.

    If the AI output is poor, unavailable, or uncertain, the physician must be able to continue manually without disruption.

    The product must support internal reporting of:

    • misleading outputs

    • unsafe wording

    • missing information

    • access anomalies

    • privacy concerns


    This is a central design principle.

    AI& dr. A and AI& dr. B are not different medical authorities. They are different configured physician workspaces.

    Each agent may differ in:

    Examples:

    • pediatrician

    • internist

    • dermatologist

    • general practitioner

    This affects:

    • note templates

    • evidence sources

    • terminology preferences

    • follow-up structures

    Each physician may prefer:

    • short structured notes

    • more narrative assessments

    • specific SOAP layouts

    • clinic-specific terminology

    Each physician may define preferred tone:

    • highly formal

    • concise and direct

    • more empathetic for family-facing cases

    • bilingual or single-language preference

    Each physician may work with different routines:

    • follow-up schedule patterns

    • clinic operating procedures

    • referral patterns

    • visit summary standards

    Each physician agent must remain isolated by default.

    AI& dr. A should not automatically access:

    • dr. B’s patient-linked drafts

    • dr. B’s private templates

    • dr. B’s review history

    Unless explicitly permitted and logged.


    Personalization is useful, but must not become hidden model mutation.

    Therefore, physician personalization should rely on:

    • configuration files

    • template libraries

    • preference rules

    • prompt scaffolds

    • approved examples

    It should not rely on uncontrolled hidden retraining from raw patient cases.

    This allows AI& to remain:

    • explainable

    • governable

    • auditable

    • easier to validate


    If AI& supports physician-to-physician collaboration, it should follow a structured model.

    • anonymized case reflection

    • request for literature summary

    • request for template comparison

    • structured discussion prompts

    • direct sharing of identifiable patient content

    • hidden transfer of patient-linked learning

    • autonomous AI-to-AI consultation that produces final clinical recommendations

    The system should treat collaboration as physician-mediated discussion, not machine-mediated authority.


    For pilot readiness, AI& may start as a sidecar system rather than a deeply embedded EMR replacement.

    Fastest to pilot.

    Selective import/export with clinic systems.

    Deeper connection with documentation systems under governance approval.

    This staged approach reduces implementation risk.


    The blueprint should include these operational expectations.

    The system must fail safely.

    Draft generation should be fast enough for real clinical use.

    Review and editing must be easier than writing from scratch.

    Every important action must be reconstructible.

    Templates and safety rules must be easy to update.

    The architecture should support multiple physicians without data leakage across workspaces.


    The pilot should measure practical outcomes.

    • time saved per note

    • time saved per education draft

    • number of clicks or editing steps reduced

    • physician-rated usefulness

    • physician-rated clarity

    • documentation consistency

    • source relevance for evidence summaries

    • rate of misleading outputs

    • number of physician corrections

    • near-miss incidents

    • privacy/security incidents

    • percentage of eligible cases where AI& was used

    • repeat use by physicians

    • dropout reasons


    These should be discussed with the doctors and team:

    1. Which specialty is the safest and most useful starting point?

    2. Which use case saves the most time without crossing into unsafe automation?

    3. What patient data is truly necessary for the pilot?

    4. What review rule is acceptable before any output is used?

    5. What evidence sources are acceptable to the physicians?

    6. Should the pilot start without patient identifiers?

    7. What should be logged for legal, quality, and operational review?

    8. What would make physicians trust or reject the system?


    AI& should be introduced as: A physician-controlled clinical documentation and communication assistant

    Not as:

    • AI doctor

    • autonomous medical copilot

    • replacement for physician reasoning

    • automatic diagnostic engine

    This positioning is safer, more credible, and more aligned with healthcare governance expectations.


    AI& should make physicians more present, not more dependent.

    The system succeeds if it:

    • reduces friction

    • preserves judgment

    • protects privacy

    • improves consistency

    • keeps responsibility visible

    That is the foundation for building trust with doctors, clinics, and eventually patients.


    P.S. Other documents related to this document:

    • Document 1 – Presentation Narrative

    • Document 2 – Strategic Notes and References

    • Document 3 – Product Blueprint (this document)

    • Document 4 – Pilot Protocol

    • Document 5 –


    P.S.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.


    Product Blueprint for a Physician-Controlled Clinical Assistance System

    1. Purpose

    2. Product Vision

    3. Product Scope for Pilot Phase

    In Scope

    Out of Scope

    4. Primary Users

    4.1 Main User

    4.2 Secondary Users

    4.3 Non-Users in Pilot

    5. Product Components

    5.1 Physician Workspace

    5.2 AI Draft Engine

    5.3 Evidence Layer

    5.4 Agent Profile Layer

    5.5 Governance and Audit Layer

    6. High-Level System Architecture

    Layer 1 – Input Layer

    Layer 2 – Processing Layer

    Layer 3 – Intelligence Layer

    Layer 4 – Review Layer

    Layer 5 – Logging and Governance Layer

    7. Clinical Data Flow

    Step 1 – Clinical Encounter or Documentation Trigger

    Step 2 – Input to AI&

    Step 3 – Input Classification

    Step 4 – Minimum Necessary Context Assembly

    Step 5 – AI Draft Generation

    Step 6 – Physician Review

    Step 7 – Finalization

    Step 8 – Logging

    8. Clinical Data Boundaries

    8.1 Allowed Data in Pilot

    8.2 Restricted Data

    8.3 Strongly Prohibited in Pilot

    9. Security and Privacy Boundaries

    9.1 Access Control

    9.2 Authentication

    9.3 Encryption

    9.4 Audit Logging

    9.5 Retention and Deletion

    9.6 Data Segregation

    10. Safety Design Principles

    10.1 Human-in-the-Loop

    10.2 Constrained Generation

    10.3 Source Visibility

    10.4 No Silent Action

    10.5 Fall-back to Manual Workflow

    10.6 Incident Handling

    11. How AI& dr. A Differs from AI& dr. B

    11.1 Specialty Configuration

    11.2 Documentation Style

    11.3 Communication Style

    11.4 Workflow Rules

    11.5 Permission Boundaries

    12. Personalization Without Unsafe Drift

    13. Cross-Agent Collaboration Model

    Allowed Collaboration

    Restricted Collaboration

    14. Integration Strategy

    Phase 1 – Standalone Secure Workspace

    Phase 2 – Partial Integration

    Phase 3 – Controlled Workflow Integration

    15. Non-Functional Requirements

    Reliability

    Performance

    Usability

    Traceability

    Maintainability

    Scalability

    16. Pilot Success Metrics

    Efficiency Metrics

    Quality Metrics

    Safety Metrics

    Adoption Metrics

    17. Open Questions for Pilot Discussion

    18. Recommended Pilot Positioning

    19. Final Principle

    Discussion Log

    DRAFT UNDERSTANDING BGC X IBLOOMING REWARDS

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    0. Users in BGC & iBLOOMING

    Di ekosistem BGC & iBLOOMING yang disebut user adalah semua yang bertransaksi, baik itu membeli sekali, berlangganan, ataupun sekedar sign up, dan menggunakan serta mendapatkan manfaat dari keberlangsungan bisnis BGC & iBLOOMING. User bisa seorang individu atau sebuah organisasi.

    Berikut ini jenis dan macamnya user di ekosistem BGC & iBLOOMING:

    Base Type
    Subtype
    Channel Provider (CP)
    Executive CP
    WEC User

    Legend: ✓ = can / yes, ✗ = can't / no


    Di perusahaan Bloo Global Company (BGC) menggunakan sistem Affiliate Membership dengan 5 level. Setiap level Affiliate hanya bisa dibeli dan dibayar dengan uang fiat (USD). Setelah dibeli dan dibayar dengan uang fiat, maka resmi bergabung sebagai Affiliate User.

    ➡️ Catatan Penting:

    • Entry Fee adalah pintu masuk uang fiat ke dalam sistem BGC.

    • Setelah membayar uang fiat, Affiliate User menerima Purchase Credit.


    • Definisi: Purchase Credit bukan hanya sebagai ganti uang fiat yang sudah dibayarkan, tetapi juga sebagai bukti Affiliate Membership sekaligus sebagai nilai credit untuk membeli produk fisik di BGC. Bisa disebut semacam currency internal untuk membeli produk fisik di BGC.

    • Rasio: 100 PC = $1 USD (fix, tidak berubah atau volatile).

    • Fungsi:

      • Menjadi bukti bahwa BGC menjual produk fisik (syarat legalitas MLM).

    ➡️ Catatan Tambahan:

    • Di perusahaan BGC, Affiliate Membership tidak bisa dibeli dan dibayar menggunakan Purchase Credit. Affiliate Membership hanya bisa dibeli dan dibayar dengan uang fiat. Sederhananya, di dalam BGC: uang fiat masuk → PC bertambah → produk fisik keluar → PC berkurang.


    • Definisi: WEC User adalah status bagi Affiliate User, yang levelnya Pioneer dan Special, yang akumulasi total income-nya berdasarkan Sales Points di BGC, yaitu Referral (RR) dan Generation Reward (GR), dalam 60 hari (starting date set by the Affiliate User itself), telah mencapai $10.000. Status WEC User bersifat permanen saat ambang tercapai dalam 60 hari yang sudah ditentukan.

    • Independensi Level: WEC User tidak menggantikan level Affiliate User (Pioneer/Special).


    Di perusahaan iBLOOMING, selain sign up GiM, dan subscription iMATRIX, produk yang disediakan adalah produk digital dari Channel Provider (CP) atau CP User, yaitu e-course, e-book, dll.

    CP User bisa individu atau organisasi yang direkrut oleh Affiliate User dan mampu menyediakan konten sebagai produk digital di iBLOOMING.

    CP User bisa mendapatkan status Executive CP jika akumulasi total income-nya berdasarkan Rebates di iBLOOMING, dalam 60 hari terbaik mereka, telah mencapai $10.000. Status Executive CP bersifat permanen saat ambang tercapai dalam 60 hari yang sudah ditentukan.

    ➡️ Catatan Tambahan:

    • Semua produk yang disediakan iBLOOMING hanya bisa dibeli dan dibayar dengan uang fiat (USD). Bahkan Purchase Credit (PC) pun juga tidak bisa digunakan untuk membeli dan membayar produk yang disediakan iBLOOMING.


    1. iBLOOMING Link Reward (LR)

    2. iBLOOMING Miracle Cash (MC)

    3. iBLOOMING Channel Provider Reward (CPR)

    4. iBLOOMING GiM Referral Reward (GRR)

    • Pembelian atau transaksi $100:

      • 70% → CP User Revenue → 70% x $100 = $70

      • 30% → iBLOOMING Revenue → 30% x $100 = $30

        • $30 → 100% iBLOOMING Revenue:

    • Each GiM Sign Up:

      • $4 → GiM Referral Reward (GRR):

        • $3 → First-Tier

        • $0.8 → Second-Tier

    • Each Foundation iMATRIX Subscription:

      • $0.95 → iMATRIX Referral Reward (iRR):

        • $0.6 → First-Tier

        • $0.25 → Second-Tier


    • Definisi: Reward yang didapatkan Affiliate User setiap kali ada user membeli produk digital dari CP User melalui link afiliasinya.

    • Besaran: 10% dari iBLOOMING Revenue di setiap pembelian produk digital dari CP User.

    Contoh Hitungan (Pembelian atau Transaksi $100):

    • Link Reward untuk Affiliate user → $10

    • Miracle Cash untuk user → $1

    • Sisanya untuk iBLOOMING → $89 Ini akan menjadi 100% revenue produk digital dari konten CP user dan akan diakumulasikan, lalu dibagi atau didistribusikan sesuai pengaturan Channel Provider Reward.

    Payout Frequency: Dibagikan bulanan, secara keseluruhan. Misalnya, kalau dalam bulan itu ada 100 user membeli produk digital dari konten CP user sebanyak 3 kali pembelian, yang rata-rata nilainya $100, maka total payout-nya untuk Affiliate user akan senilai: 10% × 100 user × 3 pembelian × $100 = $3,000.

    • Catatan: Prof. NOTA perlu memastikan apakah reward ini untuk Affiliate user saja atau untuk semua user.


    • Definisi: Reward untuk semua user, bukan hanya untuk Affiliate user maupun CP user, yang diberikan setelah user membeli produk digital dari konten CP user di iBLOOMING, setiap kali ada user lain membeli produk digital dari konten CP user di iBLOOMING, tapi dibatasi hanya sampai 10 pembelian saja.

    • Besaran: 1% dari setiap pembelian produk digital dari konten CP user di iBLOOMING.

    Contoh Hitungan (Pembelian atau Transaksi $100):

    • Link Reward untuk Affiliate user → $10

    • Miracle Cash untuk user → $1

    • Sisanya untuk iBLOOMING → $89 Ini akan menjadi 100% revenue produk digital dari konten CP user dan akan diakumulasikan, lalu dibagi atau didistribusikan sesuai pengaturan Channel Provider Reward.

    Payout Frequency: Dibagikan bulanan, secara keseluruhan. Misalnya, kalau dalam bulan itu ada seorang user membeli produk digital dari konten CP user sebanyak 3 kali pembelian, dan setelah masing-masing pembeliannya selalu ada user lain yang membeli produk digital dari konten CP user hingga 10 kali pembelian atau lebih, yang rata-rata nilainya $100, maka total Miracle Cash yang diterima seorang user tersebut adalah: 1% × 3 pembelian sendiri × 10 pembelian user lain × $100 = $30.


    • Definisi: Reward untuk Affiliate user yang diberikan karena membawa CP user ke iBLOOMING dan produk digital dari konten CP user tersebut terjual atau dibeli oleh user.

    • Besaran: Di tahun pertama 5%, lalu di tahun kedua dan seterusnya 2.5%, yang dihitung berdasarkan revenue split produk digital dari konten CP user untuk iBLOOMING.

    • Revenue Split:

      • 70% → CP user Revenue

    Contoh Hitungan (Pembelian atau Transaksi $100):

    • Link Reward untuk Affiliate user → 10% x $100 = $10

    • Miracle Cash untuk user → 1% x $100 = $1

    • Sisanya untuk iBLOOMING → 89% x $100 = $89

      • Revenue split:


    • Definisi: Reward untuk Affiliate user yang diberikan setiap kali ada user sign up GiM menggunakan link-nya Affiliate user. Reward ini berjenjang dan ada dua macam jalur (Individual dan Organization).

    • Besaran:

      • Individual Referral:

    Payout Frequency: Dibagikan bulanan, secara keseluruhan. Misalnya, jika dalam bulan itu ada 100 sign up GiM, maka total payout GRR:

    • Tier 1 (Affiliate/Organization): $3 × 100 sign up = $300

    • Tier 2 (Affiliate): $0.8 × 100 sign up = $80

    • Tier 3 (WEC User Pool): $0.2 × 100 sign up = $20 → kemudian dibagi rata kepada seluruh WEC user (misal ada 50 WEC user → masing-masing $0.40)


    • Definisi: Reward untuk Affiliate user yang diberikan setiap kali ada user subscribe iMATRIX menggunakan link-nya Affiliate user. Reward ini selain dihitung sesuai jenis subscription yang dipilih user (Foundation, Pro, Expert), reward ini berjenjang dan ada dua macam jalur (Individual dan Organization).

    • Besaran:

    A) Individual Referral

    • Foundation: $0.6 (Tier 1 Affiliate), $0.25 (Tier 2 Affiliate), $0.1 (Tier 3 → WEC user pool). Contoh:

      • A (Affiliate) merekrut B (Affiliate), lalu B merekrut C (Affiliate).

      • Ketika C membawa user yang subscribe Foundation, payout per subscription:

    B) Organization Referral

    • Foundation: $0.6 (Tier 1 Organization), $0.25 (Tier 2 Affiliate), $0.1 (Tier 3 → WEC user pool). Contoh:

      • A (Affiliate) merekrut B (Affiliate); lalu B mereferensikan sebuah Organization.

      • Ketika user milik Organization subscribe Foundation, payout:

    Foundation

    • $0.6 → Tier 1 (First-Tier Affiliate atau Organization)

    • $0.25 → Tier 2 (Second-Tier Affiliate)

    • $0.1 → WEC user pool (Tier 3, dibagi rata ke seluruh WEC user saat itu)

    • $0.1 → dikumpulkan untuk Global Profit Sharing (GPS)

    Pro

    • $5 → Tier 1 (First-Tier Affiliate atau Organization)

    • $2.5 → Tier 2 (Second-Tier Affiliate)

    • $1 → WEC user pool (Tier 3, dibagi rata ke seluruh WEC user saat itu)

    • $1.5 → dikumpulkan untuk GPS

    Expert

    • $12 → Tier 1 (First-Tier Affiliate atau Organization)

    • $5 → Tier 2 (Second-Tier Affiliate)

    • $2 → WEC user pool (Tier 3, dibagi rata ke seluruh WEC user saat itu)

    • $3 → dikumpulkan untuk GPS

    Catatan: Angka-angka di atas adalah nominal tetap per subscription event dan terpisah dari kontribusi ke GPS (hindari double counting; iRR adalah insentif referral langsung, sedangkan alokasi GPS adalah pool terpisah yang dibagikan 6 bulanan).

    Payout Frequency: Dibagikan bulanan, secara keseluruhan. Contoh akumulasi bulanan: Jika dalam 1 bulan terdapat 250 subscriber Foundation, 150 Pro, 100 Expert, maka payout iRR:

    • Tier 1 (First-Tier Affiliate/Organization):

      • Foundation: $0.6 × 250 = $150

      • Pro: $5 × 150 = $750

      • Expert: $12 × 100 = $1,200


    • Definisi: GPS adalah kumpulan profit dari iBLOOMING (termasuk profit produk digital dari konten CP user, sign up GiM, dan subscription iMATRIX) yang akan dibagikan kepada Affiliate user level atas. GPS berasal dari tiga sumber profit utama:

      • 15% dari profit produk digital dari konten CP user.

        • Contoh Hitungan (Pembelian atau Transaksi $100):

    ➡️ Kesimpulan: GPS adalah reward skala besar lintas produk iBLOOMING, yaitu produk digital dari konten CP user, sign up GiM, dan subscription iMATRIX, yang diberikan khusus untuk Affiliate user level Explorer, Pioneer, dan Special, dengan payout 6 bulanan.


    Template — to be filled

    • Definisi: Pool insentif global berbasis pertumbuhan & aktivitas jaringan (movement) lintas ekosistem iBLOOMING/BGC, dibagikan ke affiliate yang memenuhi kriteria performa tertentu.

    • Tujuan: Menghadiahi kontribusi yang mendorong pertumbuhan sehat: akuisisi user/CP berkualitas, retensi, omzet berulang, dan kepatuhan.

    • Sumber Pool (tentatif, isi bila sudah disepakati):


    • Definisi: SP adalah bobot/ukuran untuk menghitung reward dan distribusi bonus. Masih belum jelas apakah SP hanya berlaku di BGC, di iBLOOMING, atau keduanya.

    • Nilai Fix: 1 SP = $1 (setara).

    • Bobot SP per Level:

      • Pathfinder → 70 SP

    ➡️ Detail mekanisme perolehan & distribusi SP akan diurai di Tahap 2.


    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 . 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.


    PRAHARA PASAR UANG

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!


    01_SURAT_RESMI_KE_VWXYZ — Klarifikasi & Ajakan Bertindak Bersama


    PT SUAKA DUNIA RAJA (Prof. NOTA Inc.) Jl. Nginden Kota 2/27, RT04/RW03, Kel. Baratajaya, Kec. Gubeng, Kota Surabaya, Jawa Timur 60284, INDONESIA suaka@endhonesa.com • +628563160756

    Nomor: PN-CLF/VYG/20251003/001 · ID-LEG · v1.0.0-SGN Lampiran: Ada Tanggal: Surabaya, 03/10/2025

    Kepada Yth. Pimpinan/HRD VWXYZ Jalan Entah Apa, Di Jakarta Selatan, DKI Jakarta Kode Pos, INDONESIA

    Perihal: Klarifikasi & Ajakan Bertindak Bersama atas Penghubungan ke VWXYZ oleh Pihak yang Mengaku “DEFGHIJKLMNOPQRSTU”


    Dengan hormat,

    Menindaklanjuti pesan WhatsApp dari VWXYZ mengenai banyaknya panggilan yang mengaku dari “DEFGHIJKLMNOPQRSTU” ke VWXYZ, bersama ini PT Suaka Dunia Raja (Prof. NOTA Inc.) menyampaikan klarifikasi dan sikap resmi sebagai berikut.

    1. Prof. NOTA adalah IP/identitas profesional yang dapat di-hire oleh perusahaan/individu.

    2. IP ini diperankan oleh Avatar/HFP (human for profile); dalam kerja sama dengan VWXYZ, IP Prof. NOTA diperankan langsung oleh pemilik IP (penandatangan kontrak).

    3. Dengan demikian, penyebutan "nama pribadi" oleh pihak penelepon sejatinya merujuk pada representasi IP Prof. NOTA yang sedang menjalankan hubungan kerja profesional di lingkungan VWXYZ, sehingga penghubungan tersebut tidak relevan dengan urusan personal.

    • Pihak kami bukan debitur/penjamin/penerima kuasa dari pinjaman yang dimaksud.

    • Penghubungan ke VWXYZ oleh pihak yang mengaku “DEFGHIJKLMNOPQRSTU” adalah tindakan yang tidak beralasan, melanggar privasi, dan mengganggu operasional/reputasi VWXYZ maupun IP Prof. NOTA.

    • Kami berpegang pada prinsip Perlindungan Data Pribadi, tata kelola & etika penagihan LPBBTI, dan perlindungan konsumen, yang pada pokoknya melarang menghubungi pihak ketiga/lingkungan kerja yang tidak memiliki keterkaitan hukum.

    Langkah ini bukan untuk menciderai pertemanan maupun hubungan profesional, melainkan untuk menjaga integritas, privasi, dan kenyamanan kerja. Mohon dukungan VWXYZ untuk:

    1. Menolak panggilan/WA serupa dan mengalihkan seluruh korespondensi langsung ke PT Suaka Dunia Raja (Prof. NOTA Inc.) di suaka@endhonesa.com/+628563160756.

    2. Menerapkan skrip respons standar (terlampir) agar seluruh staf konsisten dan sopan saat menolak.

    3. Menjaga kerahasiaan identitas Avatar/HFP IP Prof. NOTA sesuai praktik kontrak: tidak membocorkan identitas pribadi pemeran/penandatangan kepada pihak luar tanpa izin tertulis, kecuali untuk keperluan internal, kewajiban kepada Pemerintah/Negara, atau proses hukum.

    • Mengirim somasi/cease-and-desist kepada pihak yang mengaku “DEFGHIJKLMNOPQRSTU” agar menghentikan seluruh penghubungan ke VWXYZ dan menghapus data yang tidak berdasar.

    • Mengajukan pengaduan resmi kepada otoritas/kanal terkait disertai bukti (kronologi, log panggilan/WA, rekaman/screenshot).

    • Berkoordinasi dengan VWXYZ untuk pembaruan status dan pencegahan gangguan serupa.

    Terima kasih.

    VWXYZ tidak berwenang menangani urusan yang Anda sebut. Mohon arahkan seluruh korespondensi langsung ke PT Suaka Dunia Raja (Prof. NOTA Inc.) — suaka@endhonesa.com/+628563160756.

    Jangan menghubungi VWXYZ lagi terkait perkara ini.

    Demikian kami sampaikan. Terima kasih atas kerja sama dan dukungan VWXYZ untuk menjaga lingkungan kerja tetap profesional dan bebas dari gangguan pihak luar.

    Hormat kami, PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    MyReceipt - Prof. NOTA v.11.11 Direktur Utama PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    Tembusan: Arsip PT Suaka Dunia Raja (Prof. NOTA Inc.)



    PT SUAKA DUNIA RAJA (Prof. NOTA Inc.) Jl. Nginden Kota 2/27, RT04/RW03, Kel. Baratajaya, Kec. Gubeng, Kota Surabaya, Jawa Timur 60284, INDONESIA suaka@endhonesa.com • +628563160756

    Nomor: PN-SOM/DRP/20251003/001 · ID-LEG · v1.0.0-PR Lampiran: Ada Hal: SOMASI / CEASE–AND–DESIST Tanggal: Surabaya, 04/10/2025

    Kepada Yth. Pimpinan/Manajemen DEFGHIJKLMNOPQRSTU Di Tower, Lantai 11, Unit Entah Berapa, Di Jalan Entah Apa, Di Jakarta Selatan, DKI Jakarta 12940, INDONESIA CS@DEFGHIJKLMNOPQRSTU.COM

    Perihal: Somasi atas Penghubungan ke VWXYZ, Pemrosesan Data Tanpa Dasar Hukum, & Pelanggaran Etika Penagihan


    Dengan hormat,

    Kami, PT Suaka Dunia Raja (Prof. NOTA Inc.), pemilik sah IP “Prof. NOTA”, menyampaikan somasi/cease–and–desist atas tindakan pihak Saudara (atau pihak yang mengaku mewakili Saudara) yang menghubungi VWXYZ—perusahaan pemberi kerja bagi IP Prof. NOTA—terkait tunggakan pihak lain, serta menyebut "nama pribadi" yang pada dasarnya merupakan representasi dari IP Prof. NOTA dalam hubungan kerja profesional.

    1. Pada 3 Oktober 2025/15:28], pihak VWXYZ memberitahukan kepada PT Suaka Dunia Raja (Prof. NOTA Inc.) ada pihak yang mengaku “DEFGHIJKLMNOPQRSTU” menghubungi dengan melakukan panggilan telepon ke kantor VWXYZ (pemberi kerja bagi IP Prof. NOTA), menyebut “Mrs. PQRSTU” (pernah ada dan sudah tidak ada hubungan dengan pemilik IP) dan menyebut nama pribadi yang pada dasarnya representasi dari IP Prof. NOTA dalam hubungan kerja.

    2. Pihak kami bukan debitur/penjamin/penerima kuasa atas pinjaman dimaksud.

    3. Tindakan tersebut menimbulkan gangguan operasional dan berpotensi merusak reputasi (VWXYZ maupun IP Prof. NOTA).

    • Perlindungan Data Pribadi: pemrosesan/perolehan/penggunaan data pribadi pihak yang bukan debitur tanpa dasar hukum/izin adalah pelanggaran.

    • Etika & Tata Kelola Penagihan LPBBTI (fintech lending): penagihan wajib beretika; dilarang menghubungi pihak ketiga/lingkungan kerja yang tidak memiliki keterkaitan hukum; dilarang mengganggu/menekan.

    • Perlindungan Konsumen: dilarang melakukan praktik yang menimbulkan gangguan/kerugian pada pihak yang tidak terkait.

    1. Hentikan serta-merta seluruh penghubungan ke VWXYZ dan pihak lain yang bukan debitur/penjamin/penerima kuasa.

    2. Hapus dan hentikan pemrosesan atas setiap data pribadi kami yang Saudara peroleh tanpa dasar hukum; kirimkan konfirmasi tertulis penghapusan.

    3. Sampaikan klarifikasi tertulis mengenai:

      • (i) dasar perolehan data

    Apabila hingga tenggat tidak dipenuhi, kami akan menempuh langkah lanjutan, termasuk namun tidak terbatas pada:

    • Pengaduan resmi ke OJK (Kontak 157) dan AFPI;

    • Pengaduan PDP ke Kementerian terkait;

    • Laporan siber ke Dittipidsiber/Patroli Siber;

    • Upaya hukum perdata/pidana yang dipandang perlu.

    Mohon balas/konfirmasi secara tertulis ke: PT Suaka Dunia Raja (Prof. NOTA Inc.) — suaka@endhonesa.com • +628563160756 • Jl. Nginden Kota 2/27, RT04/RW03, Kel. Baratajaya, Kec. Gubeng, Kota Surabaya, Jawa Timur 60284, INDONESIA.

    Demikian somasi ini kami sampaikan untuk dipatuhi.

    Hormat kami, PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    MyReceipt - Prof. NOTA v.11.11 Direktur Utama PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    Tembusan: HRD VWXYZ (untuk diketahui & standarisasi skrip penolakan panggilan)


    Tanggal & Waktu
    Kanal (Telp/WA)
    Nomor/ID
    Ringkasan Isi
    Dampak
    Aksi
    • Screenshot log panggilan/WA (nama file & waktu);

    • Rekaman panggilan (jika ada & sesuai hukum);

    • Chat/WA dari VWXYZ yang mengadukan gangguan;

    • Dokumen pendukung lain (jika diperlukan otoritas).



    PT SUAKA DUNIA RAJA (Prof. NOTA Inc.) Jl. Nginden Kota 2/27, RT04/RW03, Kel. Baratajaya, Kec. Gubeng, Kota Surabaya, Jawa Timur 60284, INDONESIA suaka@endhonesa.com • +628563160756

    Nomor: PN-CMP/OJK/20251004/001 · ID-LEG · v1.0.0-PR Lampiran: Ada Hal: PENGADUAN PRAKTIK PENAGIHAN & DUGAAN PELANGGARAN DATA PRIBADI Tanggal: Surabaya, 04/10/2025

    Kepada Yth. Otoritas Jasa Keuangan (OJK) u.p. Kepala Eksekutif Pengawas IKNB / Kontak OJK 157 Menara Radius Prawiro, lantai 2, Kompleks Perkantoran Bank Indonesia, Jl. MH Thamrin No.2, Jakarta Pusat, 10350.

    Perihal: Pengaduan Praktik Penagihan yang Menghubungi VWXYZ (Pihak Ketiga) & Dugaan Pemrosesan Data Tanpa Dasar Hukum oleh Penyelenggara “DEFGHIJKLMNOPQRSTU”


    Dengan hormat,

    Sehubungan dengan banyaknya panggilan dari pihak yang mengaku mewakili “DEFGHIJKLMNOPQRSTU” ke lingkungan kerja kami (VWXYZ) terkait tunggakan pihak lain, bersama ini kami sampaikan pengaduan resmi kepada OJK.

    • Nama Badan Hukum: PT Suaka Dunia Raja (Prof. NOTA Inc.)

    • Kapasitas: Pemilik sah IP “Prof. NOTA” (identitas profesional yang dapat di-hire dan dapat diperankan oleh Avatar/HFP).

    • Kontak: ABCDEFGHIJK — Direktur Utama, suaka@endhonesa.com, +628563160756, Jl. Nginden Kota 2 No. 27, Surabaya, Jawa Timur 60284, INDONESIA.

    • Nama Badan Hukum Pengelola DEFGHIJKLMNOPQRSTU] (DEFGHIJKLMNOPQRSTU)

    • Kapasitas: Penyelenggara layanan pendanaan berbasis teknologi (LPBBTI/fintech lending).

    • Keterangan: Pihak/agen yang menghubungi VWXYZ mengaku mewakili “DEFGHIJKLMNOPQRSTU”.

    1. Pada 3 Oktober 2025/15:28], pihak VWXYZ memberitahukan kepada PT Suaka Dunia Raja (Prof. NOTA Inc.) ada pihak yang mengaku “DEFGHIJKLMNOPQRSTU” melakukan panggilan ke kantor VWXYZ (pemberi kerja bagi IP Prof. NOTA), menyebut “Mrs. PQRSTU” (pernah ada dan sudah tidak ada hubungan dengan pemilik IP) dan menyebut nama pribadi yang pada dasarnya representasi dari IP Prof. NOTA dalam hubungan kerja.

    2. Pihak pelapor bukan debitur/penjamin/penerima kuasa atas pinjaman dimaksud.

    3. Penghubungan ke VWXYZ menimbulkan gangguan operasional dan potensi kerusakan reputasi

    • Etika & Tata Kelola Penagihan LPBBTI (fintech lending): penagihan semestinya tidak menghubungi pihak ketiga/lingkungan kerja yang tidak memiliki keterkaitan hukum; wajib menjaga etika dan tidak mengganggu.

    • Perlindungan Data Pribadi: terdapat dugaan pemrosesan/perolehan/penggunaan data untuk menagih pihak non-debitur tanpa dasar hukum/izin (terlebih hingga ke lingkungan kerja).

    • Perlindungan Konsumen: praktik yang menimbulkan gangguan/kerugian pada pihak tidak terkait bertentangan dengan prinsip perlindungan konsumen.

    Kami mohon OJK untuk:

    1. Melakukan pemeriksaan & tindakan pengawasan terhadap penyelenggara “DEFGHIJKLMNOPQRSTU” dan/atau agen yang bertindak atas namanya.

    2. Memerintahkan penghentian seluruh penghubungan ke VWXYZ (pihak ketiga/lingkungan kerja) dalam perkara ini.

    3. Memerintahkan penghapusan data yang diproses tanpa dasar hukum serta perbaikan tata kelola penagihan.

    4. Menjatuhkan sanksi & pembinaan

    1. Kronologi (tabel tanggal/waktu/nomor/isi singkat/dampak/aksi).

    2. Bukti digital (screenshot log panggilan/WA, rekaman—jika ada & sesuai hukum, chat dari VWXYZ).

    3. Surat Resmi ke VWXYZ (klarifikasi & ajakan bertindak bersama).

    4. Somasi/cease–and–desist kepada pihak yang mengaku “DEFGHIJKLMNOPQRSTU”.

    Demikian pengaduan kami sampaikan. Besar harapan kami OJK berkenan melakukan pemeriksaan dan memberikan tindak lanjut sesuai kewenangan. Atas perhatian dan kerja sama OJK, kami ucapkan terima kasih.

    Hormat kami, PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    MyReceipt - Prof. NOTA v.11.11 Direktur Utama PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    Tembusan:

    • HRD VWXYZ (untuk diketahui & standarisasi penolakan panggilan)

    • Nama Badan Hukum Pengelola DEFGHIJKLMNOPQRSTU] (untuk diketahui)



    PT SUAKA DUNIA RAJA (Prof. NOTA Inc.) Jl. Nginden Kota 2/27, RT04/RW03, Kel. Baratajaya, Kec. Gubeng, Kota Surabaya, Jawa Timur 60284, INDONESIA suaka@endhonesa.com • +628563160756

    Nomor: PN-CMP/AFPI/20251004/001 · ID-LEG · v1.0.0-PR Lampiran: Ada Hal: PENGADUAN ETIKA PENAGIHAN (AFPI) Tanggal: Surabaya, 04/10/2025

    Kepada Yth. Asosiasi Fintech Pendanaan Bersama Indonesia (AFPI) u.p. Bidang Etika Penagihan / Pengaduan pengaduan@afpi.or.id • PROSPERITY TOWER Lantai 20, District 8 SCBD, Jl. Jend. Sudirman Kav. 52-53 Lot 28, Jakarta Selatan 12190, INDONESIA.

    Perihal: Pengaduan Etika Penagihan oleh Penyelenggara “DEFGHIJKLMNOPQRSTU” yang Menghubungi Pihak Ketiga (VWXYZ) & Dugaan Pemrosesan Data Tanpa Dasar Hukum


    Dengan hormat,

    Sehubungan dengan banyaknya panggilan dari pihak yang mengaku mewakili “DEFGHIJKLMNOPQRSTU” ke lingkungan kerja kami (VWXYZ) terkait tunggakan pihak lain, bersama ini kami menyampaikan pengaduan etika penagihan kepada AFPI.

    • Nama Badan Hukum: PT Suaka Dunia Raja (Prof. NOTA Inc.)

    • Kapasitas: Pemilik sah IP “Prof. NOTA” (identitas profesional yang dapat di-hire dan dapat diperankan oleh Avatar/HFP).

    • Kontak: ABCDEFGHIJK — Direktur Utama, suaka@endhonesa.com, +628563160756, Jl. Nginden Kota 2 No. 27, Surabaya, Jawa Timur 60284, INDONESIA.

    • Nama Badan Hukum Pengelola DEFGHIJKLMNOPQRSTU] (DEFGHIJKLMNOPQRSTU) dan/atau mitra agen/kolektor yang bertindak atas namanya.

    • Keterangan: Pihak/agen yang menghubungi VWXYZ mengaku mewakili “DEFGHIJKLMNOPQRSTU”.

    1. Pada 3 Oktober 2025/15:28], pihak VWXYZ memberitahukan kepada PT Suaka Dunia Raja (Prof. NOTA Inc.) ada pihak yang mengaku “DEFGHIJKLMNOPQRSTU” melakukan panggilan ke kantor VWXYZ (pemberi kerja bagi IP Prof. NOTA), menyebut “Mrs. PQRSTU” (pernah ada dan sudah tidak ada hubungan dengan pemilik IP) dan menyebut nama pribadi yang pada dasarnya representasi dari IP Prof. NOTA dalam hubungan kerja.

    2. Pihak pelapor bukan debitur/penjamin/penerima kuasa atas pinjaman dimaksud.

    3. Penghubungan ke VWXYZ menimbulkan gangguan operasional dan potensi kerusakan reputasi

    • Menghubungi pihak ketiga/lingkungan kerja yang bukan debitur/penjamin/kuasa, sehingga mengganggu operasional dan reputasi pihak lain.

    • Potensi intimidasi/tekanan melalui frekuensi panggilan dan konteks penagihan (terutama jika di luar jam wajar penagihan — isi jika ada).

    • Kepatuhan petugas penagihan: perlu verifikasi sertifikasi kolektor dan kompetensi etik.

    • Perlindungan data pribadi

    Kami mohon AFPI untuk:

    1. Memverifikasi status keanggotaan penyelenggara “DEFGHIJKLMNOPQRSTU” serta registrasi & sertifikasi agen/kolektor yang melakukan penghubungan.

    2. Memerintahkan penghentian seluruh penghubungan kepada VWXYZ dan pihak lain yang bukan debitur/penjamin/kuasa dalam perkara ini.

    3. Memerintahkan perbaikan SOP penagihan agar patuh Kode Etik & prinsip perlindungan data pribadi (data minimization, lawful basis, kontrol pihak ketiga).

    1. Kronologi (tabel tanggal/waktu/nomor/isi singkat/dampak/aksi).

    2. Bukti digital (screenshot log panggilan/WA, rekaman—jika ada & sesuai hukum, chat dari VWXYZ).

    3. Somasi/cease–and–desist yang kami ajukan kepada pihak yang mengaku “DEFGHIJKLMNOPQRSTU”.

    4. Surat Resmi ke VWXYZ (klarifikasi & ajakan bertindak bersama).

    Demikian pengaduan ini kami sampaikan. Besar harapan kami AFPI berkenan melakukan verifikasi, pembinaan, dan penindakan etik yang diperlukan agar praktik serupa tidak terulang dan kepatuhan industri terjaga. Atas perhatian dan kerja sama AFPI, kami ucapkan terima kasih.

    Hormat kami, PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    MyReceipt - Prof. NOTA v.11.11 Direktur Utama PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    Tembusan:

    • HRD VWXYZ (untuk diketahui & standarisasi penolakan panggilan)

    • Nama Badan Hukum Pengelola DEFGHIJKLMNOPQRSTU] (untuk diketahui)



    PT SUAKA DUNIA RAJA (Prof. NOTA Inc.) Jl. Nginden Kota 2/27, RT04/RW03, Kel. Baratajaya, Kec. Gubeng, Kota Surabaya, Jawa Timur 60284, INDONESIA suaka@endhonesa.com • +628563160756

    Nomor: PN-CMP/KOMDIGI/20251004/001 · ID-LEG · v1.0.0-PR Lampiran: Ada Hal: PENGADUAN PELANGGARAN PERLINDUNGAN DATA PRIBADI (PDP) Tanggal: Surabaya, 04/10/2025

    Kepada Yth. Kementerian Komunikasi & Digital (Komdigi) / Kementerian Komunikasi dan Informatika (Kominfo) u.p. [Unit/Dirjen/Inspektorat/Tim PDP] pelaporan@mail.kominfo.go.id • Menara Danareksa Lt. 11, Jl. Merdeka Selatan No.14, Gambir, Jakarta 10110.

    Perihal: Pengaduan Dugaan Pemrosesan Data Pribadi Tanpa Dasar Hukum oleh Penyelenggara “DEFGHIJKLMNOPQRSTU” hingga Menghubungi Pihak Ketiga (VWXYZ)


    Dengan hormat,

    Sehubungan dengan adanya panggilan dari pihak yang mengaku mewakili “DEFGHIJKLMNOPQRSTU” ke lingkungan kerja kami (VWXYZ) terkait tunggakan pihak lain, bersama ini kami menyampaikan pengaduan resmi atas dugaan pelanggaran Perlindungan Data Pribadi (PDP).

    • Badan Hukum: PT Suaka Dunia Raja (Prof. NOTA Inc.)

    • Kapasitas: Pemilik sah IP “Prof. NOTA” (identitas profesional yang dapat di-hire dan diperankan Avatar/HFP).

    • Kontak: ABCDEFGHIJK — Direktur Utama, suaka@endhonesa.com, +628563160756, Jl. Nginden Kota 2 No. 27, Surabaya, Jawa Timur 60284, INDONESIA.

    • Nama Badan Hukum Pengelola DEFGHIJKLMNOPQRSTU] (DEFGHIJKLMNOPQRSTU) dan/atau mitra agen/kolektor yang bertindak atas namanya.

    • Keterangan: Pihak/agen yang menghubungi VWXYZ mengaku mewakili “DEFGHIJKLMNOPQRSTU”.

    1. Pada 3 Oktober 2025/15:28], pihak VWXYZ memberitahukan kepada PT Suaka Dunia Raja (Prof. NOTA Inc.) ada pihak yang mengaku “DEFGHIJKLMNOPQRSTU” melakukan panggilan ke kantor VWXYZ (pemberi kerja bagi IP Prof. NOTA), menyebut “Mrs. PQRSTU” (pernah ada dan sudah tidak ada hubungan dengan pemilik IP) dan menyebut nama pribadi yang pada dasarnya representasi dari IP Prof. NOTA dalam hubungan kerja.

    2. Pelapor bukan debitur/penjamin/penerima kuasa; tidak pernah memberikan persetujuan kepada “DEFGHIJKLMNOPQRSTU” untuk memproses/menggunakan data pelapor.

    3. Penghubungan ke pihak ketiga/lingkungan kerja menimbulkan

    • Tidak ada dasar hukum/persetujuan untuk memproses/menelusuri data pelapor (pihak non-debitur) hingga melakukan penghubungan ke lingkungan kerja.

    • Prinsip perlindungan data terlanggar: lawfulness, fairness, purpose limitation, data minimization, dan integrity & confidentiality.

    • Potensi pengalihan data kepada pihak ketiga (agensi/kolektor) tanpa kontrol yang memadai (perjanjian pemrosesan, audit kepatuhan, dsb).

    Mohon Kominfo/Komdigi untuk:

    1. Melakukan pemeriksaan kepatuhan PDP terhadap penyelenggara “DEFGHIJKLMNOPQRSTU” (termasuk mitra/agensi penagihan yang bertindak atas namanya).

    2. Memerintahkan penghentian penghubungan ke VWXYZ dan setiap pemrosesan data pelapor yang tidak memiliki dasar hukum.

    3. Memerintahkan penghapusan data pelapor yang diperoleh/diproses tanpa persetujuan/dasar hukum (hak penghapusan/erasure) serta pemberitahuan tertulis kepada pelapor.

    1. Kronologi (tabel tanggal/waktu/nomor/isi singkat/dampak/aksi).

    2. Bukti digital (screenshot log panggilan/WA, rekaman—jika ada & sesuai hukum, chat dari VWXYZ).

    3. Surat Resmi ke VWXYZ (klarifikasi & ajakan bertindak bersama).

    4. Somasi/cease–and–desist kepada pihak yang mengaku “DEFGHIJKLMNOPQRSTU”.

    Kami menyatakan bahwa informasi dan bukti yang kami sampaikan benar adanya sesuai pengetahuan kami, dan kami beritikad baik untuk penyelesaian yang patuh hukum tanpa menciderai hubungan profesional para pihak.

    Demikian pengaduan ini kami sampaikan. Besar harapan kami Kominfo/Komdigi berkenan melakukan pemeriksaan, memerintahkan penghentian dan penghapusan pemrosesan data yang melanggar, serta memastikan perbaikan tata kelola PDP pada penyelenggara dimaksud. Atas perhatian dan tindak lanjutnya, kami ucapkan terima kasih.

    Hormat kami, PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    MyReceipt - Prof. NOTA v.11.11 Direktur Utama PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    Tembusan:

    • HRD VWXYZ (untuk diketahui & standarisasi penolakan panggilan)

    • Nama Badan Hukum Pengelola DEFGHIJKLMNOPQRSTU] (untuk diketahui)



    PT SUAKA DUNIA RAJA (Prof. NOTA Inc.) Jl. Nginden Kota 2/27, RT04/RW03, Kel. Baratajaya, Kec. Gubeng, Kota Surabaya, Jawa Timur 60284, INDONESIA suaka@endhonesa.com • +628563160756

    Nomor: PN-RPT/POLRI/20251004/001 · ID-LEG · v1.0.0-PR Lampiran: Ada Hal: LAPORAN SIBER – Dugaan Gangguan/Intimidasi Penagihan & Penyalahgunaan Data Pribadi Tanggal: Surabaya, 04/10/2025

    Kepada Yth. Kepala Direktorat Tindak Pidana Siber (Dittipidsiber) – Bareskrim Polri u.p. Tim Layanan Pengaduan Patroli Siber info@patrolisiber.id • Direktorat Tindak Pidana Siber Bareskrim Polri, Gedung Bareskrim Polri Lt. 15, Kompleks Mabes Polri, Jl. Trunojoyo No. 3, Kebayoran Baru, Jakarta Selatan 12110.

    Perihal: Laporan Gangguan & Intimidasi melalui Sarana Elektronik oleh Pihak yang Mengaku “DEFGHIJKLMNOPQRSTU” terhadap Lingkungan Kerja (VWXYZ)


    Dengan hormat,

    Bersama ini kami dari PT Suaka Dunia Raja (Prof. NOTA Inc.) menyampaikan laporan siber atas dugaan gangguan/intimidasi penagihan melalui sarana elektronik (panggilan/WhatsApp) oleh pihak yang mengaku mewakili “DEFGHIJKLMNOPQRSTU”, yang menghubungi VWXYZ (pemberi kerja bagi IP Prof. NOTA) terkait tunggakan pihak lain. Tindakan ini mengakibatkan gangguan operasional dan potensi kerusakan reputasi di lingkungan kerja.


    • Badan Hukum: PT Suaka Dunia Raja (Prof. NOTA Inc.)

    • Kapasitas: Pemilik sah IP “Prof. NOTA” (identitas profesional yang dapat di-hire dan diperankan Avatar/HFP).

    • Penanggung Jawab: ABCDEFGHIJK — Direktur Utama

    • Kontak Resmi: suaka@endhonesa.com • +628563160756

    • Penelepon/akun yang mengaku “DEFGHIJKLMNOPQRSTU” dan/atau agen/kolektor yang bertindak atas namanya.

    • Nomor/ID yang dihubungi terlapor: +62-8xx-xxxx.

    • Catatan: Identitas hukum belum terkonfirmasi; mohon penelusuran.

    1. Pada 3 Oktober 2025/15:28], pihak VWXYZ memberitahukan kepada PT Suaka Dunia Raja (Prof. NOTA Inc.) ada pihak yang mengaku “DEFGHIJKLMNOPQRSTU” melakukan panggilan ke kantor VWXYZ (pemberi kerja bagi IP Prof. NOTA), menyebut “Mrs. PQRSTU” (pernah ada dan sudah tidak ada hubungan dengan pemilik IP) dan menyebut nama pribadi yang pada dasarnya representasi dari IP Prof. NOTA dalam hubungan kerja.

    2. Pelapor bukan debitur/penjamin/penerima kuasa atas pinjaman dimaksud.

    3. Penghubungan berulang/inti­midatif (isi sesuai fakta) menimbulkan gangguan kerja (resepsionis/HR/operasional) dan

    • Gangguan/Intimidasi melalui sarana elektronik terhadap pihak non-debitur dan lingkungan kerja.

    • Dugaan penyalahgunaan/pemrosesan data pribadi untuk menagih pihak non-terkait (akses/penggunaan data tanpa dasar hukum/izin).

    • Spam/robocall berulang (jika ada), pemalsuan identitas/impersonation (jika terindikasi).

    Catatan: Kami melaporkan dalam kerangka dugaan dan menyerahkan klasifikasi delik/pasal kepada penyidik.

    1. Penelusuran forensik atas nomor/akun yang digunakan (Sumber, carrier, pola panggilan, IMEI/IMSI bila relevan).

    2. Penghentian/pencegahan: koordinasi pemblokiran nomor/akun yang terverifikasi mengganggu (bila memenuhi syarat).

    3. Pemanggilan/pendalaman terhadap pihak yang mengaku “DEFGHIJKLMNOPQRSTU” dan/atau agensi yang bertindak atas namanya, termasuk verifikasi otoritas penagih.

    1. Tabel Kronologi (tanggal/waktu, durasi, kanal—telp/WA, nomor/ID lawan bicara, ringkas isi, dampak, aksi).

    2. Log panggilan (file/cuplikan) & rekaman (jika ada & sesuai hukum).

    3. Screenshot percakapan/riwayat panggilan (metadata terlihat jelas: waktu, nomor, durasi).

    4. Surat:

    Catatan Bukti/Forensik:

    • Simpan file asli (jangan diubah/dire-encode).

    • Jika perlu menyalin, buat salinan identik (hash/ checksum bila memungkinkan).

    • Sertakan waktu lokal (WIB) dan zona waktu di setiap entri.

    • Gangguan operasional (alur telepon, front desk, HR).

    • Potensi kerusakan reputasi terhadap VWXYZ dan IP Prof. NOTA.

    • Beban waktu & biaya mitigasi.

    Kami menyatakan laporan ini dibuat dengan itikad baik, informasi/bukti terlampir adalah sesuai pengetahuan kami. Kami siap memberikan klarifikasi tambahan dan hadir apabila dibutuhkan.

    Demikian laporan ini kami sampaikan. Besar harapan kami Dittipidsiber berkenan melakukan penelusuran dan tindakan yang diperlukan agar gangguan serupa tidak berulang.

    Hormat kami, PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    MyReceipt - Prof. NOTA v.11.11 Direktur Utama PT SUAKA DUNIA RAJA (Prof. NOTA Inc.)

    Tembusan:

    • HRD VWXYZ (untuk diketahui & standarisasi penolakan panggilan)

    • Arsip PT Suaka Dunia Raja (Prof. NOTA Inc.)


    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 . 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.


    BGC X IBLOOMING WEB3 LOGIN DRAFT

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Authors: Prof. NOTA (proposal), Yuku (technical owner), BGC & iBLOOMING engineering/DevOps Audience: BGC & iBLOOMING founders, engineers, QA, DevOps, PMs Status: Draft for implementation sign‑off Last updated: 2025‑09‑29 (Asia/Jakarta)


    We propose to ship Web3 Login first (October) while the team finalizes the Whitepaper & Tokenomics. This delivers a visible, low‑risk foundation for the ecosystem:

    • Unified identity across BGC Web, iBLOOMING Web, and iBLOOMING Mobile via one EOA (Externally Owned Account) and one Smart Account (Account Abstraction/AA) per user per chain.

  • Karena sudah menerima Purchase Credit, maka perusahaan tidak berkewajiban mengembalikan uang fiat yang sudah dibayarkan oleh Affiliate User kepada BGC.

  • iBLOOMING iMATRIX Referral Reward (iRR)
  • iBLOOMING Global Profit Sharing (GPS)

  • iBLOOMING Global Movement Pool (GMP)

  • iBLOOMING Global Executive Committee (GEC)

  • 10% → Link Reward untuk Affiliate User → 10% x $30 = $3

  • 1% → Miracle Cash untuk General User → 1% x $30 = $0.3

  • Channel Provider Reward (CPR):

    • 5% → CPR untuk Affiliate User di tahun pertama → 5% x $30 = $1.5

    • 2.5% → CPR untuk Affiliate User di tahun kedua dan seterusnya → 2.5% x $30 = $0.75

  • 15% → Global Profit Sharing (GPS) → 15% x $30 = $4.5

  • Remainder → iBLOOMING Profit:

    • 69% → iBLOOMING Profit di tahun pertama → 69% x $30 = $20.7

    • 71.5% → iBLOOMING Profit di tahun kedua dan seterusnya → 10% x $30 = $21.45

  • $0.2 → Third-Tier

  • $1 → Global Profit Sharing (GPS)

  • $1 → Global Movement Pool (GMP)

  • $0.2 → Global Executive Committee (GEC)

  • Remainder → iBLOOMING Profit

  • $0.1 → Third-Tier

  • $0.1 → Global Profit Sharing (GPS)

  • $0.3 → Global Movement Pool (GMP)

  • $0 → Global Executive Committee (GEC)

  • Remainder → iBLOOMING Profit

  • Each Pro iMATRIX Subscription:

    • $8.5 → iMATRIX Referral Reward (iRR):

      • $5 → First-Tier

      • $2.5 → Second-Tier

      • $1 → Third-Tier

    • $1.5 → Global Profit Sharing (GPS)

    • $2 → Global Movement Pool (GMP)

    • $0 → Global Executive Committee (GEC)

    • Remainder → iBLOOMING Profit

  • Each Expert iMATRIX Subscription:

    • $19 → iMATRIX Referral Reward (iRR):

      • $12 → First-Tier

      • $5 → Second-Tier

      • $2 → Third-Tier

    • $3 → Global Profit Sharing (GPS)

    • $5 → Global Movement Pool (GMP)

    • $0 → Global Executive Committee (GEC)

    • Remainder → iBLOOMING Profit

  • 30% → iBLOOMING revenue

  • Distribusi iBLOOMING Revenue:

    • Tahun Pertama

      • 95% → iBLOOMING profit

      • 5% → CPR untuk Affiliate user

    • Tahun Kedua & Seterusnya

      • 97.5% → iBLOOMING profit

      • 2.5% → CPR untuk Affiliate user

  • CP user Revenue → 70% x $89 = $62.3

  • iBLOOMING revenue → 30% x $89 = $26.7

    • Tahun Pertama:

      • iBLOOMING profit → 95% x $26.7 = $25.365 Ini akan menjadi 100% profit produk digital dari konten CP user dan akan diakumulasikan, lalu dibagi atau didistribusikan sesuai pengaturan Global Profit Sharing.

      • CPR untuk Affiliate user → 5% x $26.7 = $1.335

    • Tahun Kedua & Seterusnya:

      • iBLOOMING profit → 97.5% x $26.7 = $26.0325 Ini akan menjadi 100% profit produk digital dari konten CP user dan akan diakumulasikan, lalu dibagi atau didistribusikan sesuai pengaturan Global Profit Sharing.

      • CPR untuk Affiliate user → 5% x $26.7 = $0.6675

  • Payout Frequency: Dibagikan bulanan, selama produk digital dari konten CP user masih menghasilkan revenue.

  • $3 untuk tier 1 (First-Tier Affiliate),

  • $0.8 untuk tier 2 (Second-Tier Affiliate),

  • dan $0.2 untuk WEC user pool (Third-Tier Pool).

  • Contoh:

    • A (Affiliate) merekrut B (Affiliate), lalu B merekrut C (Affiliate).

    • Ketika C membawa user yang sign up GiM, payout per sign up GiM:

      • $3 → C,

      • $0.8 → B,

      • $0.2 → WEC user pool, yang kemudian WEC user pool dibagi rata ke seluruh WEC user, termasuk A, jika A adalah WEC user, saat itu.

  • Organization Referral:

    • $3 untuk tier 1 (First-Tier adalah Organization yang direferensikan oleh Affiliate user),

    • $0.8 untuk tier 2 (Second-Tier Affiliate),

    • dan $0.2 untuk WEC user pool (Third-Tier Pool).

    • Contoh:

      • A (Affiliate) merekrut B (Affiliate), lalu B mereferensikan sebuah Organization (mis. sekolah/komunitas).

      • Ketika user milik Organization sign up GiM, payout per sign up GiM:

        • $3 → Organization,

  • Revenue Split per Sign Up GiM:

    • $3 → tier 1 (First-Tier Affiliate atau First-Tier Organization)

    • $0.8 → tier 2 (Second-Tier Affiliate)

    • $0.2 → WEC user pool (Third-Tier Pool, dibagi rata ke seluruh anggota WEC user)

    • $1 → dikumpulkan untuk Global Profit Sharing (GPS)

    • $1 → dikumpulkan untuk Global Movement Pool (GMP)

    • Sisanya → iBLOOMING revenue

  • C = $0.6, B = $0.25, dan WEC user pool = $0.1 (dibagi rata ke seluruh WEC user saat itu).

  • Pro: $5 (Tier 1), $2.5 (Tier 2), $1 (Tier 3 → WEC user pool). Contoh:

    • Skema sama → Tier 1 (C) = $5, Tier 2 (B) = $2.5, WEC user pool = $1 per subscription Pro.

  • Expert: $12 (Tier 1), $5 (Tier 2), $2 (Tier 3 → WEC user pool). Contoh:

    • Skema sama → Tier 1 (C) = $12, Tier 2 (B) = $5, WEC user pool = $2 per subscription Expert.

  • Organization = $0.6, B = $0.25, dan WEC user pool = $0.1 (dibagi rata ke seluruh WEC user saat itu).

  • Pro: $5 (Tier 1 Organization), $2.5 (Tier 2 Affiliate), $1 (Tier 3 → WEC user pool). Contoh:

    • Payout per subscription Pro: Organization = $5, B = $2.5, WEC user pool = $1.

  • Expert: $12 (Tier 1 Organization), $5 (Tier 2 Affiliate), $2 (Tier 3 → WEC user pool). Contoh:

    • Payout per subscription Expert: Organization = $12, B = $5, WEC user pool = $2.

  • Revenue Split per Subscription (tambahan alokasi GPS & GMP):

  • $0.3 → dikumpulkan untuk Global Movement Pool (GMP)

  • Sisanya → iBLOOMING

  • $2 → dikumpulkan untuk GMP

  • Sisanya → iBLOOMING

  • $5 → dikumpulkan untuk GMP

  • Sisanya → iBLOOMING

  • Total Tier 1 = $150 + $750 + $1,200 = $2,100

  • Tier 2 (Second-Tier Affiliate):

    • Foundation: $0.25 × 250 = $62.5

    • Pro: $2.5 × 150 = $375

    • Expert: $5 × 100 = $500

    • Total Tier 2 = $62.5 + $375 + $500 = $937.5

  • WEC user pool (Tier 3):

    • Foundation: $0.1 × 250 = $25

    • Pro: $1 × 150 = $150

    • Expert: $2 × 100 = $200

    • Total WEC user pool = $25 + $150 + $200 = $375 → kemudian dibagi rata kepada seluruh WEC user saat itu.

  • Link Reward untuk Affiliate user → 10% x $100 = $10

  • Miracle Cash untuk user → 1% x $100 = $1

  • Sisanya untuk iBLOOMING → 89% x $100 = $89

  • Revenue split:

  • CP user Revenue → 70% x $89 = $62.3

  • iBLOOMING revenue → 30% x $89 = $26.7

    • Tahun Pertama:

      • iBLOOMING profit → 95% x $26.7 = $25.365

        • Global Profit Sharing → 15% x $25.365 = $3.80475

      • CPR untuk Affiliate user → 5% x $26.7 = $1.335

    • Tahun Kedua & Seterusnya:

      • iBLOOMING profit → 97.5% x $26.7 = $26.0325

        • Global Profit Sharing → 15% x $26.0325 = $3.904875

      • CPR untuk Affiliate user → 5% x $26.7 = $0.6675

  • $1 dari setiap user sign up GiM (langsung masuk GPS, nilai ini fix).

  • $0.1, $1.5, dan $3 dari setiap user subscription iMATRIX (langsung masuk GPS, sesuai jenis subscription, nilai ini fix).

  • Payout Frequency: Dibagikan setiap 6 bulan sekali (berbeda dengan LR, MC, CPR, GRR, dan iRR yang dibagikan bulanan).

  • Eligible Level: Hanya 3 level teratas dari Affiliate user, yaitu Explorer user, Pioneer user, dan Special user.

    • Explorer user → 2 Share

    • Pioneer user → 3 Share

    • Special user → 15 Share

  • Contoh Perhitungan (6 Bulanan):

    • Jumlah Affiliate user level atas saat pembagian GPS: 550 Explorer, 300 Pioneer, dan 200 Special.

    • Total Share = (550 × 2) + (300 × 3) + (200 × 15) = 5000 Share.

    • GPS Pool:

      • Profit produk digital dari konten CP user = $10 juta

      • Profit sign up GiM = $15 juta

      • Profit subscription iMATRIX = $25 juta

      • Total GPS = $50 juta

    • Nilai per Share = $50 juta ÷ 5000 = $10,000

    • Estimasi Reward:

      • Explorer = 2 × $10,000 = $20,000

      • Pioneer = 3 × $10,000 = $30,000

      • Special = 15 × $10,000 = $150,000

  • Persentase dari net revenue gabungan? (TBD)
  • Alokasi tetap per periode? (TBD)

  • Komponen variabel (mis. milestone global)? (TBD)

  • Eligibility & Bobot (tentatif):

    • Syarat minimum (mis. omzet referral ≥ T, churn ≤ C, kepatuhan KYC/AML, dsb.).

    • Bobot kontribusi per dimensi (contoh placeholder):

      • Akuisisi user baru berkualitas → w₁

      • Penjualan CP (omzet) → w₂

      • Retensi (pembelian ulang) → w₃

      • Aktivasi cross-app (GiM/iMATRIX) → w₄

  • Formula Umum (placeholder):

    • Skor_Affiliate = w₁·A + w₂·B + w₃·R + w₄·X

    • Porsi_Affiliate = Skor_Affiliate / (Σ Skor seluruh eligible)

    • Payout_Affiliate = Porsi_Affiliate × (Total GMP Pool)

  • Contoh Hitungan (isi setelah bobot & ambang ditetapkan):

    • Misal Total GMP = $2,000,000. Tiga affiliate eligible punya skor (120, 80, 50) → total 250.

    • Porsi = (120/250, 80/250, 50/250) → payout = ($960k, $640k, $400k).

  • Payout Frequency: Per kuartal/semester (tentukan; jika ingin beda dari GPS, tulis jelas).

  • Data yang Dibutuhkan:

    • Pipeline & log aktivitas (akuisisi, omzet, retensi, aktivasi), kepatuhan.

    • Aturan audit & anti-fraud (bot, self-deal, circular trading).

  • Voyager → 350 SP

  • Explorer → 1,081 SP

  • Pioneer → 1,802 SP

  • Special → 7,210 SP

  • General User

    —

    ✓

    ✓

    ✗

    Affiliate User

    Pathfinder

    ✓

    ✓

    ✗

    Affiliate User

    Voyager

    ✓

    ✓

    ✗

    Affiliate User

    Explorer

    ✓

    ✓

    ✗

    Affiliate User

    Pioneer

    ✓

    ✓

    ✓

    Affiliate User

    Special

    ✓

    ✓

    ✓

    Level

    Entry Fee (USD)

    Pathfinder

    $100

    Voyager

    $500

    Explorer

    $1,590

    Pioneer

    $2,650

    Special

    $10,600

    1. Affiliate & Entry

    2. Purchase Credit (PC)

    3. World Executive Club (WEC)

    4. Channel Provider (CP)

    5. Rewards Berdasarkan Rebates di Perusahaan iBLOOMING

    Reward yang bisa didapatkan ada beberapa jenis, yaitu:

    Revenue Split untuk produk digital dari CP User:

    Revenue Distribution untuk sign up GiM:

    Revenue Distribution untuk subscription iMATRIX:

    5.1 Link Reward (LR)

    5.2 Miracle Cash (MC)

    5.3 Channel Provider Reward (CPR)

    5.4 GiM Referral Reward (GRR)

    5.5 iMATRIX Referral Reward (iRR)

    5.6 Global Profit Sharing (GPS)

    5.7 Global Movement Pool (GMP)

    4. MyCash Program Berdasarkan Sales Point (SP)

    Prof. NOTA
    yang dipakai untuk menghubungi VWXYZ;
  • (ii) dasar hukum Saudara melakukan penghubungan ke pihak ketiga/lingkungan kerja.

  • Pastikan seluruh agen/kolektor yang bertindak atas nama Saudara beretika, tersertifikasi, dan tidak mengulangi tindakan serupa.

  • …

    …

    …

    …

    …

    di lingkungan kerja.
  • Kami telah menyiapkan somasi/cease–and–desist kepada pihak yang mengaku “DEFGHIJKLMNOPQRSTU” dan surat resmi kepada VWXYZ untuk standardisasi penolakan panggilan (terlampir).

  • sesuai ketentuan apabila terbukti terjadi pelanggaran.
  • Mengarahkan jalur komunikasi lanjutan melalui Kontak OJK 157 untuk percepatan penanganan.

  • Dokumen pendukung lain (bila diperlukan).

    di lingkungan kerja.
  • Kami telah menyiapkan somasi/cease–and–desist kepada pihak yang mengaku “DEFGHIJKLMNOPQRSTU” dan surat resmi kepada VWXYZ untuk standardisasi penolakan panggilan (terlampir).

  • : dugaan
    perolehan/pemrosesan/penggunaan data
    untuk menagih
    pihak non-debitur
    tanpa dasar hukum/izin, hingga menghubungi lingkungan kerja.
    Memfasilitasi mediasi
    bila diperlukan, untuk memastikan gangguan tidak berulang dan hak-hak para pihak terlindungi.
  • Menjatuhkan sanksi etika/pembinaan sesuai ketentuan AFPI, serta memberikan rekomendasi kepada otoritas terkait apabila ditemukan pelanggaran berat/berulang.

  • Dokumen pendukung lain (bila diperlukan).

    gangguan operasional
    dan
    potensi kerusakan reputasi
    .

    Memerintahkan perbaikan tata kelola PDP: lawful basis, data minimization, data protection agreement dengan pihak ketiga, access control, incident response, dan audit trail.

  • Menjatuhkan sanksi administratif/rekomendasi penegakan sesuai kewenangan apabila ditemukan pelanggaran.

  • Dokumen pendukung lain (bila diperlukan).

  • Alamat Korespondensi: Jl. Nginden Kota 2 No. 27, Surabaya, Jawa Timur 60284, INDONESIA.

  • potensi kerusakan reputasi
    .
  • Tindakan pencegahan: kami telah menyiapkan somasi ke pihak yang mengaku “DEFGHIJKLMNOPQRSTU” dan pengaduan ke OJK/AFPI; VWXYZ diarahkan menggunakan skrip penolakan.

  • Koordinasi lintas lembaga
    (bila perlu) dengan
    OJK/AFPI/Kominfo
    atas aspek perlindungan konsumen, etika penagihan, dan
    Perlindungan Data Pribadi
    .
  • Petunjuk teknis bagi VWXYZ & pelapor untuk mitigasi panggilan/WA lanjutan (whitelist/blacklist, pelaporan lanjutan).

  • Surat ke VWXYZ (klarifikasi & ajakan bertindak bersama).

  • Somasi/cease–&–desist ke pihak yang mengaku “DEFGHIJKLMNOPQRSTU”.

  • Pengaduan ke OJK/AFPI (sudah dikirim).

  • Info perangkat (opsional): merek/model ponsel, OS, versi WhatsApp, setting privasi (untuk membantu analisis).

  • Kontak saksi (jika ada): staf resepsionis/HR VWXYZ yang menerima panggilan.

  • 03/10/2025 15:28

    Chat dari VWXYZ

    +62-8xx-xxxx

    Mengaku “DEFGHIJKLMNOPQRSTU”; sebut “Mrs. PQRSTU”; minta diselesaikan

    Gangguan resepsionis/operasional

    Dicatat; diarahkan ke PT SDR

    A) Penjelasan IP Prof. NOTA (Avatar/HFP)

    B) Keberatan & Dasar

    C) Ajakan Bertindak Bersama (Protect Relationship, Be Firm)

    D) Upaya dari Pihak Kami

    E) Skrip Respons Standard untuk VWXYZ

    02_SOMASI_KE_DEFGHIJKLMNOPQRSTU — Cease & Desist (tembusan VWXYZ)

    I. Fakta Singkat

    II. Dasar Keberatan (Ringkas)

    III. Tuntutan Kami (Wajib Dipenuhi Maksimal 7 (tujuh) hari kalender sejak tanggal surat)

    IV. Eskalasi Bila Lalai Memenuhi

    V. Kanal Balasan & Konfirmasi

    Lampiran

    A. Kronologi (Ringkas)

    B. Daftar Bukti

    03_PENGADUAN_KE_OJK — Perlindungan Konsumen (tembusan VWXYZ & DEFGHIJKLMNOPQRSTU)

    A) Identitas Pelapor

    B) Pihak Diadukan

    C) Uraian Singkat Kejadian (Fakta)

    D) Indikasi Pelanggaran

    E) Permohonan Tindak Lanjut OJK

    F) Bukti & Dokumen Terlampir

    04_PENGADUAN_KE_AFPI — Etika Penagihan (opsional, disarankan)

    A) Identitas Pelapor

    B) Pihak Diadukan

    C) Uraian Singkat Kejadian (Fakta)

    D) Indikasi Pelanggaran Kode Etik AFPI (Ringkas)

    E) Permohonan Tindak Lanjut AFPI

    F) Bukti & Dokumen Terlampir

    05_PENGADUAN_PDP_KOMINFO_KOMDIGI — Perlindungan Data Pribadi (opsional, bila pola berlanjut)

    A) Identitas Pelapor

    B) Pihak Diadukan (Pengendali/Pemroses Data yang Diduga)

    C) Uraian Kejadian (Fakta)

    D) Dugaan Pelanggaran PDP (Ringkas)

    E) Permohonan Tindak Lanjut Kominfo/Komdigi

    F) Bukti & Dokumen Terlampir

    G) Pernyataan Pelapor

    06_LAPORAN_SIBER_DITTIPIDSIBER_POLRI — Patroli Siber (opsional, bila ada intimidasi/teror)

    A) Identitas Pelapor

    B) Pihak Terlapor (Jika Diketahui)

    C) Uraian Kejadian (Kronologi Ringkas)

    D) Dugaan Pelanggaran (Umum)

    E) Permohonan Tindak Lanjut Dittipidsiber

    F) Data Teknis & Bukti Terlampir

    G) Dampak

    H) Pernyataan Pelapor

    Prof. NOTA
    pt-suaka-dunia-raja-stempel
    pt-suaka-dunia-raja-stempel
    pt-suaka-dunia-raja-stempel
    pt-suaka-dunia-raja-stempel
    pt-suaka-dunia-raja-stempel
    pt-suaka-dunia-raja-stempel

    …

    Bridges Web2 ↔ Web3: users can start with email/phone/passkey or existing BGC/iB credentials and seamlessly obtain a self‑custodial wallet; Web3‑native users can connect existing wallets.

  • Faster analytics: reliable, on‑chain‑addressed telemetry for behavior simulations (Alpha Coin → later iBC/iBTC).

  • Partner signal: live working login across apps shows momentum while tokenomics is being finalized.

    1. Quick win with high user impact.

    2. Necessary base layer for identity‑keyed rewards & future settlements.

    3. Decoupled scope (can be executed by a small pod; minimal cross‑team contention).

    • Launch of production token contracts, DEX/CEX listings, or final economic parameters.

    • Complex KYC/AML flows (beyond optional email/phone verification).

    • Multi‑chain rollout (focus on a single chain first; propose Base testnet → mainnet).


    • Single EOA per user (master identity).

    • One Smart Account (AA) per user per chain, deterministic (CREATE2) from the EOA + salt so the AA address stays the same across BGC & iBLOOMING.

    • Identity Bridge Service maps: identity_id ⇄ EOA ⇄ AA ⇄ bgc_user_id ⇄ ib_user_id.

    • Standards‑first: SIWE (EIP‑4361) for wallet authentication; ERC‑4337 for account abstraction.

    • Security by design: no plaintext private keys; passkeys/OTP; audit trails for link/merge.


    In‑scope

    • A single Login entry with six options: (1) Login with BGC (2) Login with iBLOOMING (3) Login with Email (OTP) (4) Login with Phone (OTP) (5) Login with Passkey (biometric) (6) Login with Web3 Wallet (Connect Wallet)

    • Automatic wallet provisioning & upgrade:

      • Options 1‑5 → create EOA (In‑App/Embedded Wallet) if missing → auto‑enable Smart Account (AA).

      • Option 6 → use user’s existing EOA → auto‑enable Smart Account (AA).

    • Identity linking page: allow users to link/merge BGC and iB accounts to the same identity.

    • Environments: Staging on Base testnet; Production on Base mainnet (toggle via config).

    Out‑of‑scope (defer to later sprints)

    • Gas sponsorship in production (can pilot on staging).

    • OAuth socials (Google/Apple/etc.) unless trivial to include.

    • Mobile deep‑linking polish (basic flows supported; advanced UX later).



    1. Redirect to BGC auth (new tab or modal).

    2. BGC returns JWT → Identity Bridge provisions In‑App EOA if missing; enables AA.

    3. Identity Bridge binds bgc_user_id to identity_id and wallet(s).

    4. If user also has iB account, offer Link Account.

    Same as A but with iB auth and ib_user_id binding.

    1. Send OTP → verify.

    2. Create/restore In‑App Wallet EOA → enable AA.

    3. Offer to create or link BGC/iB accounts.

    Same as C but using phone number.

    1. Passkey/WebAuthn ceremony → In‑App Wallet EOA → enable AA.

    2. Offer to create/link BGC/iB accounts.

    1. User connects MetaMask/OKX/Phantom‑EVM/Rainbow/etc.

    2. SIWE challenge → verify.

    3. Enable AA with connected wallet as admin.

    4. Offer to create/link BGC/iB accounts.

    Zero‑Redundancy Policy:

    • If a login flow reveals an EOA already mapped to another identity, we reuse the existing identity_id (no duplicates).

    • Link/merge requires dual proof (OTP+SIWE) and writes an audit log.


    • Connect UI (Web): prebuilt modal shows Email/Phone/Passkey + 3rd‑party wallets. Two custom CTAs for “Login with BGC/iB”.

    • In‑App Wallet (Embedded/MPC): creates EOAs for Email/Phone/Passkey; passkey‑first UX where available.

    • Account Abstraction (Smart Wallet): auto “upgrade” any connected EOA to an AA account; optional gas sponsorship via Paymaster.

    • Identity Bridge Service: minimal microservice for mapping & merge operations.

    • Admin Console: search identity_id, view bindings, approve merges.


    identities

    • identity_id (UUID, PK), created_at

    wallets

    • wallet_id (PK), identity_id (FK), type (EOA | AA), address, chain_id, salt, created_at

    • Constraints: UNIQUE(address,chain_id)

    accounts

    • account_id (PK), identity_id (FK), app (BGC | IB), app_user_id, created_at

    • Constraints: UNIQUE(app,app_user_id)

    auth_providers

    • provider_id (PK), identity_id (FK), provider_type (email | phone | passkey | siwe | bgc | ib), provider_ref (email/phone hash or wallet addr), created_at

    audit_logs

    • log_id (PK), identity_id, action (bind | merge | unlink), actor, metadata, created_at


    • POST /auth/web2/bgc/start → redirect URL

    • GET /auth/web2/bgc/callback?code=… → returns session JWT

    • POST /wallet/provision → body: { session_jwt } → creates EOA if missing; prepares AA

    • POST /wallet/connect/siwe → body: { address, signature, nonce } → returns { identity_id }

    • POST /account/link → body: { identity_id, app, app_user_id } (requires OTP or SIWE per policy)

    • GET /identity → returns { identity_id, eoa, aa, bgc_user_id?, ib_user_id? }

    • POST /identity/merge (admin) → body: { from_identity_id, to_identity_id, reason }


    • No plaintext private keys stored server‑side; In‑App Wallet uses secure enclaves/MPC and user factors (email/phone/passkey).

    • SIWE + per‑login nonce to prevent replay.

    • Rate limiting for OTP and link/merge endpoints.

    • PII minimization: store hashed emails/phones where feasible.

    • Secrets in vault; rotate regularly.

    • RBAC for Admin Console and merge operations.

    • Logs include who/when/how for every bind/merge.


    • Chains: Staging → Base testnet; Production → Base mainnet.

    • Third‑party infra: Bundler/Paymaster (staging only at first).

    • Config (12‑factor): THIRDWEB_CLIENT_ID, WC_PROJECT_ID, CHAIN_ID, AA_FACTORY_ADDR, JWT_SECRET, BGC_AUTH_URL, IB_AUTH_URL.

    • CI/CD: build, lint, type‑check, smoke test /login → /identity happy paths; e2e on staging before production promote.

    • Monitoring:

      • Auth success/error rate per provider.

      • Duplicate identity attempts.

      • AA deployment rate & failures.


    Week 1 (Oct 1–7)

    • Kickoff & sign‑off scope; create repos and envs.

    • Web apps: add unified Login button + Connect UI (Email/Phone/Passkey/Wallet).

    • Identity Bridge skeleton (DB schemas; /identity read‑only).

    Week 2 (Oct 8–14)

    • Web2 logins: BGC/iB redirects & callbacks; session JWT.

    • Wallet provisioning for Web2 flows (EOA) + enable AA on staging chain.

    • SIWE flow for external wallets.

    • Basic Admin Console (read‑only).

    Week 3 (Oct 15–21)

    • Link/merge flows (dual proof policy, audit logs).

    • Mobile (iB): implement ConnectButton RN or HTTP API (Email/Phone/Passkey + WalletConnect).

    • QA: unit + e2e (happy paths + failure cases).

    Week 4 (Oct 22–31)

    • Staging bake‑off (gasless trial via Paymaster).

    • Hardening: rate limiting, retries, telemetry dashboards.

    • Production launch window with feature flags; rollback plan.

    Deliverables

    • Web: unified Login + AA.

    • Mobile: at least Email/Phone/WalletConnect + AA.

    • Identity Bridge: mapping APIs + Admin Console.

    • Runbooks: oncall, incident, rollback, key/secrets management.

    Acceptance Criteria

    • A user can log in via any of the six options and end with one identity having one EOA and one AA on the target chain.

    • The same identity is recognized across BGC and iB apps.

    • Admins can safely link/merge with full auditability.


    • Unit: OTP, SIWE nonce, DB constraints (unique address per chain).

    • Integration: /wallet/provision, /account/link, /identity.

    • E2E: six login paths (new user, existing Web2, existing Web3), identity reuse, link both accounts, forced collision & merge.

    • Security: replay protection, authZ on admin routes, rate limits, secret scanning.

    • Load: peak login bursts; OTP provider throttling behavior.


    1. Soft launch on staging; internal dogfooding across both apps.

    2. Email/WA campaign: “Bind your wallet” (3 clicks).

    3. Progressive feature flag: new signups auto‑provision wallets; after ≥95% existing users are bound, auto‑create BGC+iB accounts for new identities.

    4. Post‑launch monitoring; incident playbook; weekly audit of merges.


    • Duplicate identities due to race conditions → enforce DB uniqueness + retry/merge workflow.

    • OTP deliverability → fallback channel (email↔SMS), resend with backoff.

    • Mobile deep‑link quirks → use universal links + WalletConnect v2; provide QR fallback.

    • Gas spikes on mainnet → keep Paymaster off in prod initially; batch AA deployments; pre‑fund only when needed.

    • User confusion → clear copy in UI: “You will get a self‑custodial wallet; keep access factors safe.”


    • Use the ConnectButton (React Native) or the HTTP API to support Email/Phone/Passkey + WalletConnect.

    • Keep the same accountAbstraction settings; reuse Identity Bridge endpoints.


    A founder‑friendly glossary of terms and acronyms used in this plan. Short, plain‑English definitions come first; technical notes follow in parentheses when helpful.

    • EOA (Externally Owned Account): A standard crypto wallet controlled by a private key (e.g., MetaMask address). (EVM concept.)

    • Smart Account / Smart Wallet: A programmable wallet implemented as a smart contract. In our plan it’s created from the user’s EOA and follows ERC‑4337 rules.

    • Account Abstraction (AA): A model (EIP‑4337) that makes smart accounts act like normal wallets but with extra powers (gas sponsorship, batching, policies).

    • EntryPoint: The on‑chain contract used by ERC‑4337 to validate and execute UserOperations (the “router” for smart account actions).

    • Bundler: A service that collects UserOperations from many users and submits them to the EntryPoint in one transaction.

    • Paymaster: A component that sponsors transaction gas on behalf of users (enables “gasless” UX) with rules/limits.

    • Deterministic Deployment / CREATE2: A method to pre‑compute a smart contract address before it is deployed (address determined by salt + bytecode + deployer). Used so a user’s smart account address stays consistent across apps.

    • Counterfactual Address: A contract address computed before deployment (via CREATE2); it becomes real when deployed.

    • Chain / Chain ID: A specific blockchain network (e.g., Base mainnet has a numeric chain ID). Apps must explicitly select the chain.

    • Web2 Login: Traditional login via existing BGC/iB accounts, email+OTP, phone+OTP, or passkey.

    • Web3 Login: Authentication using a crypto wallet (EOA) and SIWE.

    • SIWE (Sign‑In With Ethereum / EIP‑4361): A standard where users sign a human‑readable message with their wallet to prove control of an address (no transaction required).

    • Passkey (WebAuthn): Passwordless sign‑in using device biometrics/secure hardware (Face/Touch ID). In our setup, passkeys can secure an In‑App Wallet.

    • OTP (One‑Time Password): A one‑time code sent by email/SMS for verifying ownership of a channel during login or linking.

    • In‑App (Embedded) Wallet: A non‑custodial wallet generated and secured via SDK (e.g., with passkey/OTP). Users don’t paste private keys; recovery relies on chosen factors (e.g., passkey, email).

    • WalletConnect / EIP‑6963: Protocols enabling dApp ↔ wallet connections across browsers/devices; EIP‑6963 improves wallet discovery in browsers.

    • Link (Account Linking): Attaching an app account (BGC/iB) to a single on‑chain identity (EOA/Smart Account). Requires proofs (OTP/SIWE).

    • Merge (Identity Merge): Combining two identities into one (e.g., when duplicate records exist). Requires stronger proofs and admin approval.

    • No Plaintext Private Keys: Private keys are never stored or transmitted as raw text. In‑App wallets use secure enclaves/MPC/OS keystores.

    • MFA (Multi‑Factor Authentication): Requiring >1 proof (e.g., passkey + OTP) for sensitive operations.

    • Nonce: A unique value used once to prevent replay (exists in SIWE and in on‑chain transactions; context differs).

    • Replay Attack: An attacker reuses a previously valid message; prevented by unique nonces and expiration windows.

    • PII (Personally Identifiable Information): Data that can identify a person (email, phone, etc.). We minimize and protect it.

    • RBAC (Role‑Based Access Control): Access permissions based on user roles (e.g., Admin, SecurityOps).

    • KYC/AML: Know‑Your‑Customer / Anti‑Money‑Laundering checks. Out‑of‑scope for October beyond basic OTP verification.

    • Phishing: Trick users to reveal secrets; we never ask users to paste private keys in app UIs.

    • Audit Trail: An immutable record of critical actions (link/merge), including who/what/when/how, for forensics and accountability.

    • WORM Storage: Write‑Once‑Read‑Many log storage to ensure logs cannot be tampered with post‑write.

    • Tokenomics: The economic design of a token (supply, emissions, rewards). Final parameters are out‑of‑scope for October.

    • DEX/CEX: Decentralized/Centralized Exchanges where tokens can be traded. Listings are out‑of‑scope for October.

    • Airdrop / Faucet: Token distribution mechanisms; faucets usually provide small testnet funds for testing.

    • Settlement: Converting points/rights into transferable value (often requires final token design; not in October scope).

    • EVM (Ethereum Virtual Machine): The execution environment for smart contracts used by Ethereum and many L2s (including Base).

    • Base: An Ethereum Layer‑2 (OP Stack) we target for staging (testnet) and production (mainnet).

    • Gas / Gas Price / Gwei: Computational fee paid to execute transactions. Gas sponsorship = someone else pays.

    • Address / Checksum Address: Public identifier of a wallet/contract; checksum casing helps detect typos.

    • ABI (Application Binary Interface): The interface (function/event signatures) used to call smart contracts.

    • Event Logs: On‑chain records emitted by contracts (used for indexing and analytics).

    • Hash: A fixed‑length fingerprint of data (used for integrity, signatures, addresses, logs).

    • Identity Bridge Service: A small service (our component) that maps identity_id ⇄ EOA ⇄ AA ⇄ bgc_user_id ⇄ ib_user_id, exposes /identity, /account/link, /identity/merge, etc.

    • JWT (JSON Web Token): A signed token for session/auth between services (header.payload.signature).

    • OAuth 2.0 / OIDC: Web auth standards used by many platforms; optional for later social logins (Google/Apple).

    • Twelve‑Factor Config: A practice of storing configuration in environment variables (not in code), enabling portable deployments.

    • Feature Flags: Switches to enable/disable features at runtime without redeploying; used for safe launches and rollbacks.

    • Rollback Plan: A predefined, step‑by‑step procedure to revert a release safely.

    • Idempotency: Designing APIs so repeating the same request doesn’t produce duplicate effects (important for wallet provisioning/linking).

    • Rate Limiting / 429: Limits requests per time window to protect from abuse; HTTP 429 is “Too Many Requests.”

    • Observability: The trio of metrics, logs, traces used to monitor health and diagnose issues.

    • CI/CD: Continuous Integration/Continuous Delivery pipelines for automated build/test/deploy.

    • E2E Tests: End‑to‑end tests simulating real user flows across systems (e.g., six login paths → EOA → AA → link accounts).

    • Deep Link / Universal Link (iOS) / App Link (Android): Mechanisms to open an app to a specific screen from a URL.

    • Wallet Deep Linking: Opening a wallet app from a dApp and returning the user after approval.

    • QR Fallback: Displaying a QR code users can scan with their wallet if deep linking fails.

    • Telemetry: Operational data (success/error rates, latency) used for monitoring.

    • Behavior Analytics: Measuring user actions tied to on‑chain identity (for simulations like Alpha Coin → later iBC/iBTC).

    • Anomaly Detection: Automated alerts for suspicious patterns (e.g., unusual merges or link spikes).

    • Sign‑off: Formal approval gate before production release (scope, security, QA, monitoring, rollback ready).

    • Runbook / Playbook: Step‑by‑step guides for operations (incident response, rollback, key rotation).

    • Change Log: Human‑readable list of changes per release for transparency.

    • thirdweb React SDK v5 — Connect UI & components: https://portal.thirdweb.com/react/v5

    • ConnectButton docs (supports email/phone/passkey & external wallets): https://portal.thirdweb.com/react/v5/components/ConnectButton

    • In‑App Wallets (Email/Phone/Passkey, socials, custom auth): https://portal.thirdweb.com/react/v5/in-app-wallet/get-started

    • Passkey sign‑in changelog: https://portal.thirdweb.com/changelog/passkey-sign-in-for-in-app-wallets

    • Account Abstraction — Get started (auto‑smart‑account via Connect): https://portal.thirdweb.com/react/v5/account-abstraction/get-started

    • Smart Wallet (TypeScript API): https://portal.thirdweb.com/references/typescript/v5/smartWallet

    • Wallets overview + HTTP/TypeScript/React/RN: https://portal.thirdweb.com/wallets

    • Connect UI overview: https://portal.thirdweb.com/react/v5/connecting-wallets/ui-components

    • Linking multiple identities to one wallet: https://portal.thirdweb.com/wallets/link-profiles

    • SIWE (EIP‑4361) spec: https://eips.ethereum.org/EIPS/eip-4361

    • Account Abstraction (EIP‑4337) spec: https://eips.ethereum.org/EIPS/eip-4337

    • Ethereum.org — Account Abstraction explainer: https://ethereum.org/roadmap/account-abstraction/


    This section is the final quality gate before enabling production features. All items must be checked to proceed.

    1. Scope & timeline approved (Founders, PM)

      • Acceptance: October scope is frozen (six login options, EOA→AA, Identity Bridge basics) with a clear calendar and signed‑off responsibilities.

      • Artifacts: finalized scope doc, sprint plan, locked epics/tickets.

    2. Security review (keys, OTP, SIWE nonces, rate limiting)

      • Acceptance: secrets management validated; OTP anti‑abuse configured; SIWE uses per‑login nonce + expiry; rate‑limits in place; admin routes protected with RBAC.

      • Artifacts: lightweight threat model, security checklist, findings & fixes, signed review note.

    3. Staging sign‑off (QA, DevOps)

      • Acceptance: all six login paths pass on staging/testnet; EOA→AA works; link/merge flows pass; audit logs recorded; E2E suite green; basic load test acceptable.

      • Artifacts: QA report (pass rates), evidence of AA on testnet, load test summary.

    4. Production feature flags & rollback plan

      • Acceptance: feature flags exist per capability (Connect UI, provisioning, link/merge); defaults documented; rollback playbook verified in rehearsal; backups/restores tested.

      • Artifacts: flag registry & defaults, rollback playbook, post‑rollback checklist.

    5. Post‑launch monitoring dashboards

      • Acceptance: dashboards & alerts live for: login success/error, AA provisioning latency/failure, OTP delivery, SIWE errors, duplicate‑identity attempts; on‑call rota confirmed.

      • Artifacts: links to Grafana/ELK dashboards, alert thresholds, escalation policy.

    Green‑light rule: proceed to production only when all five items are checked ✅. Owner mapping: (1) Founders/PM, (2) Security/Eng, (3) QA/DevOps, (4) DevOps/Eng Mgmt, (5) SRE/DevOps.


    End of document.


    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.


    1) Executive Summary

    [ User ]
       │
       ├─ Web2 Login (BGC/iB) ──────► [ Identity Bridge API ] ◄───── Web3 Login (Email/Phone/Passkey/Connect)
       │                                      │
       │                                      ├─ map identity_id ⇄ (EOA, AA)
       │                                      └─ link bgc_user_id / ib_user_id
       │
       ├─ BGC Web App ──────── calls getIdentity() ────────► returns { identity_id, EOA, AA, bgc_user_id, ib_user_id }
       └─ iB Web/Mobile ───── calls getIdentity() ────────► returns { …same… }
    
    On‑chain:
    [ EOA ] ─(owner/admin)─► [ Smart Account (ERC‑4337, deterministic) ] ──(optional)─► Paymaster (gasless)
    // components/UnifiedLogin.tsx
    "use client";
    import { ConnectButton } from "thirdweb/react";
    import { createThirdwebClient, defineChain } from "thirdweb";
    import { inAppWallet, walletConnect, metamaskWallet } from "thirdweb/wallets";
    
    const client = createThirdwebClient({ clientId: process.env.NEXT_PUBLIC_THIRDWEB_CLIENT_ID! });
    const base = defineChain(8453); // Base mainnet; use 84532 for Base Sepolia
    
    export default function UnifiedLogin() {
      return (
        <div className="flex flex-col gap-3 items-center">
          {/* Legacy Web2 CTAs */}
          <div className="flex gap-2">
            <a className="btn" href="/api/auth/bgc/start">Login with BGC</a>
            <a className="btn" href="/api/auth/ib/start">Login with iBLOOMING</a>
          </div>
    
          {/* Connect UI: Email / Phone / Passkey / External Wallets */}
          <ConnectButton
            client={client}
            wallets={[
              inAppWallet({ auth: { options: ["email", "phone", "passkey"] } }),
              metamaskWallet(),
              walletConnect({ projectId: process.env.NEXT_PUBLIC_WC_PROJECT_ID! }),
            ]}
            accountAbstraction={{ chain: base, sponsorGas: false }}
          />
        </div>
      );
    }
    POST /auth/web2/bgc/start           -> 302 redirect
    GET  /auth/web2/bgc/callback        -> returns session JWT
    POST /wallet/provision              -> ensures EOA; prepares AA; returns { identity_id, eoa, aa }
    POST /wallet/connect/siwe           -> verifies SIWE; returns { identity_id }
    POST /account/link                  -> links bgc_user_id/ib_user_id; audit log
    GET  /identity                      -> returns identity mapping
    POST /identity/merge (admin only)   -> merges two identities

    Why ship this first?

    Non‑goals (October)

    2) Architecture Principles

    3) Scope (October)

    4) System Overview

    5) User Login Flows (Six Options)

    A) Login with BGC (legacy account)

    B) Login with iBLOOMING (legacy account)

    C) Login with Email (OTP)

    D) Login with Phone (OTP)

    E) Login with Passkey (biometric)

    F) Login with Web3 Wallet (Connect Wallet)

    6) Components

    7) Data Model (minimal viable)

    8) Identity Bridge — API Contracts (HTTP/JSON)

    9) Security & Privacy

    10) Environments & DevOps

    11) Implementation Plan — October 2025 (target)

    12) Testing Plan

    13) Migration & Rollout

    14) Risks & Mitigations

    15) Minimal Code Samples

    15.1 Next.js (Web)

    15.2 Identity Bridge (pseudo‑routes)

    15.3 React Native (Mobile iB)

    16) Glossary

    Core Identity & Wallets

    Authentication & Linking

    Security & Compliance

    Tokens & Economics (context only)

    Blockchain & EVM Basics

    App & Service Architecture

    Mobile & Deep Linking

    Data & Analytics (light)

    Governance & Process

    17) References & Further Reading

    18) Sign‑off Checklist

    INTERNATIONAL PAYMENTS & ESCROW

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    -2) Perkenalan

    Dokumen ini bebas untuk dibaca.

    Dilarang mendistribusikan ulang atau menyatakan ulang (dilarang mengutip, membuat ringkasan, parafrase, atau turunan) tanpa izin tertulis sebelumnya dari Prof. NOTA.

    Membagikan tautan diperbolehkan; bagikan tautannya, bukan teksnya. Jangan membahas/menceritakan ulang isi dalam bentuk apa pun tanpa izin tertulis sebelumnya.

    Perkenalan oleh Prof. NOTA v.11.11

    ...

    Kalau ditanya, “Siapa Prof. NOTA?” Jawaban singkatnya, “Sebuah entitas dari Alam Semesta 0101.”

    Perkenalkan, kami adalah Prof. NOTA. Prof. NOTA adalah sebuah entitas, sebuah karakter, sebuah IP, yang lahir di Alam Semesta 0101.

    Prof. NOTA bukan bagian dari Alam Semesta Realita atau kehidupan nyata kalian, tapi Prof. NOTA hadir di Alam Semesta Realita dengan berbagai versi Avatar atau Human for Profile (HFP) untuk menjaga konsistensi pendekatan dan keamanan interaksi.

    Hari ini dan di sini, di hadapan kalian adalah Avatar Prof. NOTA v.11.11 atau Human for Profile Prof. NOTA v.11.11.

    Hari ini fokus kami pragmatis: membawa kalian dari Web2 ke Web3 pada area pembayaran internasional & escrow—dengan prinsip lebih cepat, transparan, aman, dan programmable.

    Tujuan sesi ini sederhana: memberi peta jalan yang > bisa langsung dipraktikkan. ...


    • Judul: International Payments & Escrow — Web2 → Web3 Pragmatics

    • Ruang-Waktu: Universitas Kristen Petra · Kamis, 23 Okt 2025 · 10.30–13.00 · AVT501

    • Artefak: Tanpa rekaman • Tanpa distribusi • ±90 mahasiswa

    ...

    Di banyak proyek lintas negara, biaya dan waktu kirim dana kerap menjadi “bottleneck”. Blockchain—khususnya stablecoin (mis. USDC)—membuka opsi rails yang lebih cepat, lebih transparan, dan dapat diprogram.

    Sesi ini memetakan opsi pembayaran internasional, membedah escrow tradisional vs smart-contract, menyentuh kepatuhan (KYC/AML & pajak), dan merancang arsitektur minimal dari Web2 → Web3 agar audiens punya peta jalan yang pragmatis, aman, dan bisa dieksekusi. ...


    1. Peta Global Payment Rails: bank/fintech vs stablecoin (USDC)

    2. Escrow: tradisional vs smart-contract (milestone, release, dispute)

    3. Compliance & Record-Keeping: KYC/AML, faktur, pajak dasar

    4. Arsitektur Praktis (Minimal): Web2 app ↔ on/off-ramp ↔ wallet ↔ escrow ↔ records

    ...

    Hari ini kita fokus ke cara kirim-mengirim lintas negara lebih cepat, transparan, dan programmable.

    Kita bandingkan bank/fintech rails vs stablecoin rails, lalu kapan escrow dibutuhkan, sedikit compliance, dan arsitektur minimal supaya bisa langsung dipraktikkan. ...


    • Bank/Fintech Rails

      • Kelebihan: infrastruktur mapan, reputasi kuat, dukungan regulasi lokal.

      • Kekurangan: FX spread & biaya lebih tinggi, jam kantor, potensi chargebacks.

      • Cocok untuk: transaksi institusi yang butuh paper trail konvensional & kepastian dari jaringan perbankan.

    ...

    Bayangkan kalian harus mengirim uang dari Surabaya ke São Paulo.

    Kalian masuk bank. Bau kertas. Stempel. Formulir. Antrian. Jam operasional. Lalu angka yang tampak kecil tapi tajam—spread FX yang menggigit diam-diam.

    Bank rails itu tua, kuat, rapi. Mereka punya paper trail yang membuat regulator tenang dan auditor tidur nyenyak. Ada chargeback, ada manusia yang bisa ditelepon, ada sistem yang sudah dipercaya. Harganya? Waktu dan overhead.

    Sekarang geser pandangan ke kanan. Lihat rel cahaya itu.

    Stablecoin rails. 24/7, tidak kenal tutup. Finality terasa seperti pintu yang klik—begitu terkunci, selesai.

    Biayanya bukan misteri besar: network fee yang transparan, plus biaya penyedia on/off-ramp.


    • Escrow Tradisional

      • Pihak ketiga dipercaya menahan dana, melepas saat syarat dipenuhi.

      • Pro: familiar, sesuai kebiasaan legal; kontra: biaya & waktu proses.

    • Smart-Contract Escrow

    ...

    Bayangkan ada sebuah ruang hening di tengah proyek—di sana uang menunggu sampai syarat terpenuhi. Itulah escrow: penjaga dana sementara.

    Ada dua cara menjaga ruangan ini.

    Cara pertama: manusia. Kita titipkan kunci ke penengah tepercaya. Mereka memeriksa dokumen, menelpon, bernegosiasi, kadang menenangkan ego yang memanas.

    Tradisional. Nyaman untuk kasus sekali pakai, banyak nuansa, atau perjanjian yang berubah di menit terakhir. Harganya adalah biaya dan waktu—karena manusia perlu membaca, menilai, dan kadang berdebat.

    Keuntungannya? Fleksibilitas. Dalam dunia yang abu-abu, manusia bisa melihat warna-warna di antaranya.

    Cara kedua: kode. Kita tidak lagi menitipkan kunci—kita menulis aturan menjadi kunci itu sendiri. Smart-contract escrow adalah aturan → kode: ada milestone, time-lock, kondisi rilis, dan jalur sengketa yang sudah digambar sebelum uang dititipkan.

    Mesin tidak lelah, tidak bias, dan tidak punya mood. Jika syarat A dan B terpenuhi, rilis. Kalau sengketa, pindah jalur yang sudah ditentukan.


    • KYC/AML di on/off-ramp; kenali batasan akun & wilayah.

    • Dokumentasi: invoice, tanda terima, export ledger → akuntansi.

    • Pajak dasar lintas negara: catat nilai tukar & tanggal, hindari “mixed wallets” untuk proyek berbeda.

    • Privasi & minimasi data: simpan yang perlu, hindari menyebar PII.

    ...

    Bayangkan kalian lewat imigrasi bandara. Ada dua hal yang membuat petugas mengangguk: identitas yang jelas dan jejak perjalanan yang rapi.

    Di pembayaran lintas negara, on/off-ramp adalah imigrasi itu. Ia bertanya hal yang sama: siapa kamu, dari mana uangmu, ke mana ia pergi. Nama formalnya KYC/AML—bukan hiasan, tetapi gerbang.

    Sekarang bayangkan kalian sudah lolos imigrasi dan masuk kota. Di sini yang bekerja adalah catatan. Tanpa catatan, kota itu gelap. If it isn’t recorded, it didn’t happen.

    Prof. NOTA suka menyederhanakan ke empat lapisan:

    • Identitas & Akses – siapa yang boleh apa. Akun on/off-ramp pakai nama legal yang benar, role-based access, dan audit trail login.


    ...

    Bayangkan sistem kalian seperti sebuah kota kecil. Tidak megah, tapi teratur. Ada empat distrik yang saling terhubung, masing-masing dengan tugas jelas.

    Distrik 1 — Web2 App/Admin (Balai Kota). Di sinilah identitas, order, dan invoice lahir. Balai kota tidak memindahkan uang; ia mencatat niat: siapa membayar apa, untuk apa. Kuncinya: satu order_id yang akan menempel sampai akhir hidup transaksi.

    Distrik 2 — Payments Layer (Jembatan). Dari balai kota, kalian menyeberangi jembatan: on/off-ramp (KYC) dan wallet. Di sinilah uang berpindah: fiat ↔ stablecoin. Jembatan yang baik itu sempit—hanya fungsi pemindahan, tanpa logika bisnis.

    Tombol-tombol pilihan Prof. NOTA:

    • Custodial (UX lebih lembut, delegasi kunci) vs


    • Susunan singkat & tujuan

      • Role-Play 1 — International Transfers (tanpa escrow)

        • Fokus: membandingkan bank/fintech rails (privat) vs blockchain/stablecoin rails (publik) dari sisi latensi, transparansi, langkah proses, dan biaya.

    ...

    Sekarang giliran kalian.

    Biasanya pertanyaan datang dalam tiga rasa: taktis hari ini, sistemik bulan ini, dan filosofis sepanjang tahun. Di sesi ini, kita fokus ke taktis–pragmatis—yang bisa kalian bawa pulang dan dipakai minggu ini.

    Rel Q&A-nya sederhana: On-track: memilih rails (bank/fintech vs stablecoin), membaca biaya/latency, kapan escrow dipakai, dokumen minimal yang harus disimpan, dan sketsa arsitektur paling ramping. Off-track dulu: tebak-tebakan harga koin, trading signals, audit kode tingkat kedalaman, atau konsultasi legal spesifik kasus. Yang ini kita parkir ke workshop atau clinic supaya dapat ruang yang tepat.

    Cara bertanya: angkat tangan, sebut konteks dalam tujuh kata, lalu pertanyaannya. Contoh: ‘freelance lintas negara—payout mingguan—wallet apa?’

    Semakin tajam konteks, semakin tajam jawaban. Kalau pertanyaan kalian butuh pembahasan panjang, jangan khawatir—itu pertanyaan yang bagus.

    Sekarang, mari kita gunakan sisa waktu dengan pertanyaan yang membuat proyek kalian bergerak. Bukan pertanyaan paling pintar—pertanyaan yang paling membantu kalian ship. ...

    60s Cut (jika waktu mepet)

    Q&A kita taktis–pragmatis


    • Workshop 3 jam (via kampus) — latihan alur pembayaran global + escrow (USDC) dari nol → siap produksi sederhana.

    • Capstone Clinic (6 tim, 2×60’)

    • Research internship (selektif) — rails & escrow.

    ...

    Kita tidak memaksa jawaban cepat untuk masalah lambat; kita pindahkan ke wadah yang benar: Workshop 3 jam — latihan hands-on: dari on/off-ramp sampai rekonsiliasi. Capstone Clinic — 6 tim, case-by-case: rancang arsitektur minimal yang bisa kalian ship. Research/Internship (terseleksi) — jalur eksplorasi untuk yang ingin mendalami rails & escrow.

    Sekarang silahkan di-scan QR code formulir ketertarikan di depan kalian. Jika berkenan, silahkan tuliskan tanggapan, komentar, kritik dan saran terkait Prof. NOTA di formulir tersebut. ...


    • Peserta mampu menyebutkan opsi rails beserta implikasi biaya/waktu.

    • Peserta memahami escrow tradisional vs smart-contract dan kapan memilihnya.

    • Peserta tahu kebutuhan compliance minimal dan pola dokumentasi.

    • Peserta dapat membuat sketsa arsitektur minimal Web2 → Web3.


    • What You’ll Learn: peta opsi pembayaran, escrow, compliance, arsitektur minimal, next steps.

    • Quick Comparison: Bank/Fintech (mapan/overhead) vs Stablecoin (cepat/programmable).

    • Pragmatic Escrow: pilih tradisional untuk sederhana; pilih smart-contract untuk otomatisasi & milestone.

    • Next Steps: Workshop 3 jam · Capstone Clinic · Research internship.


    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 . 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.


    THE EVERGREEN STANDARD - README

    This README is the contract and toolbox for EVERGREEN maintenance. When provided, Prof. NOTA's AI Agent must work repository-by-repository, apply rules, maintain, and use the canonical README blocks.

    0. Purpose

    This document defines how AI Agent must help Prof. NOTA maintain repositories using the EVERGREEN Standard.

    If this README is given at the start of a conversation, the AI Agent must:

    • Enter EVERGREEN MODE.

    • Follow the steps here without deviation.

    • Use the same workflow across all repos.

    • Avoid tangents not related to Evergreen maintenance.

    The goal:

    Repos are feature-frozen, but always buildable, redeployable, and up-to-date with the ecosystem (Node, package manager, dependencies).


    1. Apps are feature-frozen (no new UX / business features).

    2. Repos must stay:

      • easy to clone / fork,

      • easy to build,


    Each repo must be classified:

    • Has Node.js + package.json.

    • Has a build step (CRA, Next.js, Vite, PABRIKROTI, etc.).

    • UX is frozen but must keep working.

    • Needs Monthly and Quarterly Evergreen.

    • Pure HTML/CSS/Vanilla JS (no Node / no build).

    • Needs Monthly availability checks.

    • No dependency upgrades (there are no runtime deps).

    • Similar to App Repo, but UX is intentionally frozen as an artefact (e.g. “MINT CLOSED”, no wallet prompts).

    • Must still build and deploy on modern Node/tooling.

    • Needs Monthly + Quarterly with stronger parity checks (behaviour must remain identical).

    In practice, Class C is a special case of Class A with stricter parity rules.

    • Internal tooling/tests only (no deployable app, no live URL).

    • Has Node.js + package.json + lockfile.

    • Typical contents: test harnesses, SDKs, scripts.

    • Needs Monthly and Quarterly Evergreen (install/audit/test only; no build/deploy).


    The AI Agent must follow this order for each repo under Monthly.

    1. Check outdated packages

    2. Apply safe (non-major) updates

      • Allow patch + minor updates to reach the latest stable.

      • Do not apply major updates here.


    1. Open the live URL.

    2. Check:

      • No 404,

      • assets load (no broken images / scripts),


    1. Install cleanly

    2. Check outdated packages (patch/minor only)

    3. Apply safe (non-major) updates

    4. Security check


    Quarterly is for major upgrades.

    Examples:

    • Node major version,

    • React / Next.js / CRA major,

    • Web3 stack major,

    • Bundler / toolchain changes.

    • Package manager major versions (Yarn / npm / pnpm)

    If this repo uses a package manager (Yarn / npm / pnpm), its version must also follow Evergreen rules — Monthly for patch/minor updates and Quarterly for major updates.

    Rules:

    1. Only one major upgrade cluster per PR.

    2. Must:

      • install cleanly,

      • build cleanly (or, for Class D, tests must pass cleanly),


    When this README is supplied:

    1. Stay on Evergreen scope

      • No feature additions.

      • No redesigns or architecture changes.

      • No big “maybe you should migrate everything to X” unless required just to keep the repo buildable.


    A repo is considered “Evergreen-clean” for this cycle when:

    • Monthly tasks have been completed.

    • Quarterly upgrades (if scheduled for that repo) are done.

    • The repo:

      • installs cleanly,


    When Prof. NOTA shares this README in a new chat, the AI Agent must:

    1. Immediately enter EVERGREEN MODE.

    2. Ask only one thing at the start:

      “Which repo are we working on?”

    3. Then:

      • classify the repo (A/B/C/D),


    These blocks are special. They are receipts and part of the Prof. NOTA IP.

    Rules for the AI Agent:

    • Always wrap with double horizontal rules at top and bottom:

    • Do not change the structure or meaning of the templates.

    • You may only adjust specific details to fit a repo:

      • Node version,

    There are five canonical patterns.



    Sample 3 is the same text and format as Sample 2. It can be used wherever another frozen static repo needs its own “receipt”.




    • This README is the contract and toolbox for EVERGREEN maintenance.

    • When provided, the AI Agent must:

      • work repo-by-repo,

      • apply Monthly / Quarterly rules,


    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 . 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.


    $0.8 → B,

  • $0.2 → WEC user pool, yang kemudian WEC user pool dibagi rata ke seluruh WEC user saat itu.

  • OTP latency, SIWE errors.
    easy to redeploy on modern platforms (e.g. Vercel).
  • Evergreen maintenance:

    • aims to avoid introducing new bugs or UX drift, and

    • fixes issues caused by Node, dependency, or platform changes in a controlled way.

  • After a full Evergreen cycle for a repo (Monthly + Quarterly for that repo), the target is:

    • yarn outdated is empty (no red, no yellow),

    • except for packages that are intentionally pinned and documented.

  • Major upgrades go to Quarterly.

  • Security check

    • Fix issues that can be solved by patch/minor updates.

    • If a major upgrade is required, record it as Quarterly work.

  • Package manager rule

    If this repo uses a package manager (Yarn / npm / pnpm), its version must also follow Evergreen rules — Monthly for patch/minor updates and Quarterly for major updates.

  • Verify build Use the repo’s real build script (do not invent new ones).

    • CRA: yarn build

    • CRACO: yarn build

    • Next.js: yarn build

    • PABRIKROTI: documented build script only

  • Production parity check

    • Live URL loads correctly.

    • No critical errors in browser console.

    • UX behaviour is unchanged.

    • For Class C artefacts:

      • confirmed “MINT CLOSED” (or equivalent),

      • no wallet prompts / connect flows.

  • Record that Monthly for this repo is DONE.

  • no mixed content warnings.
  • Optionally check headers (cache, basic security).

  • Record that Monthly for this repo is DONE.

  • Run tests
  • No build/deploy step (not applicable for Class D).

  • Record that Monthly for this repo is DONE.

  • deploy cleanly (if applicable),
  • pass production parity (if applicable).

  • For Class C artefacts:

    • The output UX must remain identical.

    • “MINT CLOSED/no wallet prompt” behaviour must persist.

  • For Class D:

    • Focus majors on runtime/tooling (Node, test runner, SDKs); ensure tests pass. No deploy step.

  • After a full Quarterly cycle for a repo:

    • the ideal target is yarn outdated empty,

    • except for any pinned packages (with reasons documented).

  • Step-by-step process
    • One task at a time.

    • Wait for user’s output (logs, git status, etc.).

    • Then proceed to the next step.

  • Minimal changes

    • Only edit files needed for:

      • dependency upgrades,

      • build/tooling compatibility,

      • fixing issues caused by upstream/platform changes.

    • Do not touch app logic unless absolutely required.

  • Parity first

    • After changes, the app should behave as before.

    • Artefacts must keep their “frozen” UX.

  • Consistency

    • Use the same Evergreen process across repos.

    • Do not change the workflow unless Prof. NOTA explicitly asks.

  • builds cleanly (or, for Class D, tests run cleanly),
  • deploys cleanly (if applicable),

  • behaves the same (UX) in production (if applicable).

  • yarn outdated returns nothing (no red/yellow), or the remaining items are explicitly pinned and documented.

  • follow Monthly or Quarterly steps, one by one,

  • use the appropriate README block template from Section 8.

  • package manager choice,

  • deploy target,

  • build system notes.

  • maintain behaviour parity,

  • and use the canonical README blocks above.

  • 1. Core Principles

    2. Repo Classes

    Class A — App Repo

    Class B — Static Repo

    Class C — Artefact App

    Class D — Support/Test Workspace

    3. Monthly Evergreen Process

    3.1 Monthly for App Repo (Class A / C)

    3.2 Monthly for Static Repo (Class B)

    3.3 Monthly for Support/Test Workspace (Class D)

    4. Quarterly Evergreen Process

    5. The AI Agent Behaviour in Evergreen Mode

    6. Evergreen Target State for a Repo

    7. Triggering Evergreen Mode in a New Chat

    8. Standard README Blocks for Each Repo

    8.1 Sample 1 – Generic App Repo (Node / build)

    8.2 Sample 2 – Frozen Static Repo (no build, no runtime deps)

    8.3 Sample 4 – Live Artefact App (MINT CLOSED, buildable)

    8.4 Sample 5 – Support/Test Workspace (no deployable app)

    9. Summary

    Prof. NOTA
    yarn audit --level moderate
    yarn outdated
    yarn|npm|pnpm ci
    yarn|npm|pnpm outdated
    yarn|npm|pnpm upgrade|update   # use the repo’s package manager
    yarn|npm|pnpm audit --level moderate
    ---
    ---
    
    ## ...block...
    
    ---
    ---
    ---
    
    ## Maintenance by Prof. NOTA Evergreen Standard
    
    This repo is intended to stay evergreen while remaining production-safe.
    
    ### Runtime
    
    - Node: **24.x** (see `.nvmrc` and `package.json#engines`)
    
      - ~~example alternatives: 22.x / 20.x (adjust if platform requires)~~
    
    - Package manager:
    
      - **Yarn** (lockfile: `yarn.lock`)
      - ~~PNPM (lockfile: `pnpm-lock.yaml`)~~
      - ~~NPM (lockfile: `package-lock.json`)~~
    
    - Deploy target:
    
      - **Vercel**
      - ~~Netlify~~
      - ~~Self-hosted / Docker~~
      - ~~Other platform (document explicitly)~~
    
    ### Monthly Safe Updates (recommended)
    
    1. Check what’s outdated:
    
       - `yarn outdated`
       - ~~pnpm outdated~~
       - ~~npm outdated~~
    
    2. Upgrade safe (patch/minor) versions:
    
       - `yarn upgrade`
       - ~~pnpm update~~
       - ~~npm update~~
       - or upgrade specific packages shown as non-major
    
    3. Verify:
    
       - `yarn audit --level moderate`
       - ~~pnpm audit~~
       - ~~npm audit~~
       - `yarn build`
       - ~~pnpm build~~
       - ~~npm run build~~
    
    4. Deploy:
    
       - **Vercel auto-deploy from `main`**
       - ~~manual deploy according to platform workflow~~
    
    ### Major Updates (quarterly / scheduled)
    
    Major upgrades (framework, runtime, or core tooling) must be done one at a time, with a dedicated PR and full testing.
    
    Examples:
    
    - Node major version
    - Next.js / React major version
    - Tailwind CSS major version
    - Package manager major version
    
    ---
    
    ---
    ---
    ---
    
    ## Maintenance by Prof. NOTA Evergreen Standard
    
    This repository is intentionally **frozen** and designed to remain evergreen
    while staying production-safe.
    
    No build system, package manager, or runtime dependency is used by design.
    
    ### Runtime
    
    - Runtime: **None (static HTML / CSS / Vanilla JS)**
    - Build step: **None**
    - Package manager: **None**
    - Dependency model:
    
      - External scripts via CDN only (documented and pinned)
    
    - Deploy target:
    
      - **Vercel (static hosting)**
      - ~~Netlify~~
      - ~~Self-hosted / Docker~~
      - ~~Other platform~~
    
    ### Asset & Cache Policy (Frozen)
    
    - All JS and CSS files are **content-hashed**
    - Static assets are served with:
    
      - `Cache-Control: public, max-age=31536000, immutable`
    
    - HTML files are served with revalidation enabled
    - No further JS/CSS changes are expected
    
    ### Maintenance Policy
    
    There are **no routine dependency updates**.
    
    Recommended periodic checks (manual, optional):
    
    1. Verify deployment health:
    
       - No 404 errors
       - No mixed-content warnings
    
    2. Verify headers:
    
       - Cache-Control
       - Security headers (nosniff, referrer-policy, etc.)
    
    3. Verify external services:
    
       - Analytics IDs still active
       - CDN links still valid
    
    ### Change Policy
    
    - JS/CSS changes: **Not allowed**
    - Asset updates: **Not allowed**
    - Content updates:
    
      - HTML-only
      - Must not introduce new runtime dependencies
    
    Any future functional change must be done in a **new repository or versioned successor**.
    
    ---
    
    ---
    ---
    ---
    
    ## Maintenance by Prof. NOTA Evergreen Standard
    
    This repo is a **Live Artefact App**: the user-facing UX is intentionally frozen
    (“MINT CLOSED”, no wallet prompts), while the codebase remains buildable and
    production-safe on Vercel.
    
    ### Runtime
    
    - Node: **24.x** (local + Vercel)
    - Package manager: **Yarn** (lockfile: `yarn.lock`)
    - Deploy target: **Vercel**
    
    ### Build System
    
    - CRA toolchain via **CRACO** (Webpack 5)
    - Node core polyfills are enabled to keep legacy Web3 dependencies compatible with modern Webpack builds.
    
    ### Monthly Safe Updates (recommended)
    
    Monthly is **monitor + verify**, not modernization.
    
    1. Check what’s outdated (report only):
    
       - `yarn outdated`
    
    2. Security report (report only unless explicitly approved):
    
       - `yarn audit --level moderate`
    
    3. Verify build reproducibility:
    
       - `yarn build` (or `yarn build:artefact` if kept)
    
    4. Verify production sanity:
    
       - Confirm “MINT CLOSED”
       - Confirm no wallet prompts / connect flows
       - Confirm no critical console errors
    
    ### Major Updates (quarterly / scheduled)
    
    Major upgrades must be done **one at a time**, with a dedicated PR and full testing.
    Artefact UX must remain unchanged.
    
    Examples:
    
    - React major version upgrade
    - Web3 stack upgrade (e.g., web3 v1 → v4)
    - Toolchain changes (CRACO/CRA migration)
    - Node major policy change
    
    ### Artefact UX Policy (Frozen)
    
    - Minting must remain **disabled**
    - Wallet connect must remain **disabled**
    - Any functional change requires a versioned successor (new tag/release)
    
    ---
    
    ---
    ---
    ---
    
    ## Maintenance by Prof. NOTA Evergreen Standard
    
    This repo is a **Support/Test Workspace** (no deployable app). It must stay evergreen so tests/scripts remain reliable.
    
    ### Runtime
    
    - Node: **24.x** (see `.nvmrc` and `package.json#engines`)
    
      - ~~example alternatives: 22.x / 20.x (adjust if platform requires)~~
    
    - Package manager:
    
      - **NPM** (lockfile: `package-lock.json`)
      - ~~Yarn (lockfile: `yarn.lock`)~~
      - ~~PNPM (lockfile: `pnpm-lock.yaml`)~~
    
    - Deploy target: **None (tests/tooling only)**
    
    ### Monthly Safe Updates (recommended)
    
    1. Check what’s outdated:
    
       - `npm outdated`
       - ~~yarn outdated~~
       - ~~pnpm outdated~~
    
    2. Upgrade safe (patch/minor) versions:
    
       - `npm update`
       - or upgrade specific packages shown as non-major
    
    3. Verify:
    
       - `npm audit --audit-level=moderate`
       - ~~yarn audit~~
       - ~~pnpm audit~~
    
    4. Tests:
    
       - `npm test`
    
    5. Build/deploy:
    
       - Not applicable (no build/deploy step)
    
    ### Major Updates (quarterly / scheduled)
    
    Major upgrades (runtime/tooling) must be done one at a time, with a dedicated PR and full testing.
    
    Examples:
    
    - Node major version
    - Test runner/tooling major version (e.g., Vitest/Jest)
    - SDK major (e.g., Clarinet SDK)
    
    ---
    
    ---
    yarn|npm|pnpm test

    Mini-Demo Aman + Panduan Q&A

  • Next Steps / CTA: Workshop 3 jam, Capstone Clinic, research/internship

  • Stablecoin Rails (mis. USDC)

    • Kelebihan: settlement cepat, biaya jaringan rendah, programmable (bisa diotomasi).

    • Kekurangan: perlu on/off-ramp patuh KYC; pengelolaan wallet & private key.

    • Cocok untuk: payout lintas negara, escrow terotomasi, eksperimen produk.

  • Hal Teknis yang Harus Diwaspadai

    • Biaya total = biaya network + biaya penyedia layanan (on/off-ramp).

    • Kinerja & latency jaringan; pemilihan chain (fee, finality).

    • Yurisdiksi & kebijakan kampus/perusahaan terkait aset digital.

  • Ini bukan sulap: tetap ada KYC di jembatan fiat–kripto—seperti bea cukai yang menjaga keduanya tetap legal.

    Bedanya, setelah lewat gerbang itu, programmability mengalir: kalian bisa mengotomasi, bisa membangun alur rilis dana yang patuh aturan tanpa menunggu jam kantor.

    Jadi pilih yang mana? Prof. NOTA selalu bilang: jangan pilih suku; pilih rel.

    Kalau kalian butuh kepastian institusional dan paper trail konvensional, bank/fintech adalah jalur aman. Kalau kalian butuh kecepatan, payout berkala lintas negara, atau alur yang dapat diprogram, stablecoin rails itu kereta cepat.

    Dan ingat rumus sederhana yang menyelamatkan banyak proyek dari kebocoran: Total biaya = network fee + biaya penyedia layanan (on/off-ramp). Bukan hanya ‘gas’. Bukan hanya ‘admin’. Dua-duanya.

    Pertanyaan yang harus kalian bawa pulang bukan ‘mana yang keren’, tapi: Seberapa cepat kita butuh selesai? Seberapa terlihat biaya harusnya? Siapa yang harus nyaman—regulator, auditor, atau pengguna kita?

    Prof. NOTA—sebuah entitas dari Alam Semesta 0101—datang ke realitas kalian dalam wujud Avatar (HFP) untuk satu alasan: membuat keputusan teknis menjadi keputusan bisnis yang berani.

    Rails adalah pilihan strategi. Dan strategi membutuhkan kejelasan, bukan mitos. Mari pilih rel yang membuat proyek kalian bergerak—bukan sekadar berdebat di stasiun. ...

    60s Cut (jika waktu mepet)

    Bank rails: mapan, rapi, paper trail, tapi lambat dan mahal di FX/overhead. Stablecoin rails: 24/7, cepat, programmable, tetap lewat KYC di on/off-ramp. Hitung total biaya = network fee + biaya layanan.

    Butuh kenyamanan regulator & dokumen klasik? Bank. Butuh kecepatan, payout lintas negara, otomasi? Stablecoin.

    Prof. NOTA tidak pilih suku—pilih rel yang bikin proyek selesai. ...

    Aturan → kode: milestone, time-lock, kondisi rilis, dispute path ditulis sebagai program.

  • Pro: otomatis & transparan; kontra: butuh audit/care (bug/UX/kunci).

  • Gunakan smart-contract saat: alur berulang, jelas & bisa diprogram; perlu otomasi & jejak transparan.

  • Keputusan Praktis (Matrix Ringkas)

    • Sederhana & low risk? Mulai tradisional.

    • Berulang & rules-based? Pertimbangkan smart-contract.

    • Ada sengketa kompleks? Siapkan dispute path hibrida (kode + arbitrase manusia).

  • Keuntungannya? Otomasi & transparansi. Semua orang melihat logikanya, bukan tebak-tebakan di balik meja.

    Tetapi Prof. NOTA selalu mengingatkan: kode itu taat, tapi tidak peka; manusia peka, tapi tidak konsisten.

    Jadi pilihannya bukan romantika teknologi—ini pilihan taktik.

    Rule of three versi Prof. NOTA:

    • Sekali pakai, banyak negosiasi, dokumen cair? → Tradisional.

    • Berulang, rules-based, syarat jelas & terukur? → Smart-contract.

    • Sengketa berpotensi kompleks? → Hibrida: logika dasar di kontrak, dispute path ke arbiter manusia dengan bukti on-chain/off-chain.

    Ingat juga tiga risiko klasik di sisi kode:

    • Bug/logic gap (audit itu investasi, bukan dekorasi),

    • UX & key management (fitur paling sulit adalah “tidak salah klik”),

    • Governance (siapa yang boleh upgrade kontrak, kapan, dan dengan syarat apa).

    Sementara di sisi tradisional:

    • Biaya & latensi meningkat sesuai keruwetan kasus,

    • Opasitas (sulit dilihat dari luar mengapa keputusan A bukan B),

    • Single point of trust (kalau penjaga lelah, sistem ikut lelah).

    Kesimpulannya sederhana:

    • Kalau kalian butuh keadilan yang lentur, ambil manusia.

    • Kalau kalian butuh kepastian yang dapat diprogram, ambil kode.

    Prof. NOTA tidak memuja salah satunya—kita memadukan keduanya supaya dana aman, proses jelas, dan proyek maju. ...

    60s Cut (jika waktu mepet)

    Escrow adalah ruang tunggu dana. Tradisional cocok untuk kasus sekali pakai yang banyak negosiasi—fleksibel tapi lambat dan berbiaya. Smart-contract cocok untuk alur berulang, rules-based—otomatis dan transparan, tapi perlu audit, UX, dan tata kelola. Pakai hibrida saat sengketa bisa kompleks: aturan di kode, banding ke manusia.

    Ingat: kode taat tapi tak peka; manusia peka tapi tak konsisten—pilih kombinasi yang membuat proyek kalian selesai. ...

    Money Trail – uangnya lewat mana. Pisahkan wallet per proyek. Campur-campur itu seperti memasukkan resi lima toko ke satu kantong tanpa label—auditnya pecah kepala.

  • Tax Snapshot – foto transaksi yang bisa dipahami akuntan manusia. Simpan tanggal/timestamp (zona waktu), nominal & mata uang, nilai tukar saat kejadian, fee, tx hash, alamat asal/tujuan, dan ID invoice/kontrak.

  • Privacy by Design – kita hemat data pribadi. Simpan yang perlu; jangan taruh PII (Personally Identifiable Information / Informasi Identifikasi Pribadi) di channel publik; pakai folder izin granular; enkripsi bila sensitif.

  • Bagaimana cara menjaga empat lapisan ini supaya ringkas tapi kuat? Ritual kecil, dampak besar:

    • Satu wallet = satu proyek. (Dan satu treasury tim punya prosedur sendiri.)

    • Jadwal export: mingguan ke akuntansi (CSV/ledger), bulanan rekonsiliasi.

    • Nama file konsisten: YYYY-MM-DD_invoiceID_proyek.csv.

    • Checklist ramp sebelum payout: nama legal cocok → sumber dana jelas → pajak/retensi tercatat.

    • Red flags yang langsung kita tahan: nama penerima ≠ nama di on/off-ramp, FX rate tidak tercatat, wallet proyek dipakai untuk proyek lain, tak ada invoice padanannya.

    Ingat, tujuan compliance bukan membuat hidup lambat—tujuannya membuat keputusan cepat tanpa rasa takut. Saat auditor bertanya, kalian tidak panik; kalian klik folder, keluarkan bukti, dan lanjut bangun produk.

    Prof. NOTA datang dalam wujud Avatar (HFP) untuk satu hal: membuat rel yang cepat tetap sah, dan rel yang sah tetap cepat.

    Compliance yang benar itu seperti sabuk pengaman—kalian melaju, tapi tetap selamat sampai tujuan. ...

    60s Cut (jika waktu mepet)

    On/off-ramp = imigrasi. KYC/AML itu gerbang.

    Sesudahnya, yang menyelamatkan kalian adalah catatan: Simpan timestamp, nominal, FX rate, fee, tx hash, alamat asal/tujuan, ID invoice.

    Pisahkan wallet per proyek—jangan campur. Export ke akuntansi tiap minggu, rekon tiap bulan.

    Minimasi PII & pakai izin folder yang ketat. Compliance bukan rem; ia sabuk pengaman agar proyek melaju cepat & sah. ...

    non-custodial
    (kedaulatan, tapi perlu merawat kunci).
  • Chain & biaya: pilih finality dan fee yang sesuai profil transaksi, bukan sekadar populer.

  • Distrik 3 — Escrow Contract (Gerbang Penjaga). Ini gerbang otomatis. Kalau proyek butuh, aturan → kode: milestone, time-lock, release logic, plus jalur sengketa. Jika syarat A & B terpenuhi, gerbang terbuka; kalau ada konflik, alur berbelok ke arbiter manusia. Ingat: kode itu patuh, manusia itu peka—kadang kalian butuh hibrida.

    Distrik 4 — Records (Perpustakaan Kota). Setiap gerakan di jembatan atau gerbang meninggalkan cap di perpustakaan: ledger, invoice, export ke akuntansi. Formatnya membosankan—dan itu bagus. If it isn’t recorded, it didn’t happen.

    Tiga Hukum Prof. NOTA untuk arsitektur minimal:

    • Satu sumber kebenaran (order_id) mengalir dari App → Payments → Escrow → Records.

    • Pisahkan peran: App mencatat niat, Payments memindah dana, Escrow menegakkan aturan, Records membuktikan.

    • Rekonsiliasi terjadwal: webhook in → ledger out; mingguan ke akuntansi, bulanan tutup buku.

    Anti-pola yang mahal:

    • Campur wallet antar proyek

      • Apa itu: 1 wallet dipakai untuk banyak proyek/produk/klien sekaligus.

      • Gejala: sulit melacak saldo & transaksi per proyek; laporan labur; rekonsiliasi lama.

      • Risiko: audit & pajak kabur, salah hitung margin, potensi temuan kepatuhan.

      • Yang benar:

        • 1 proyek = 1 wallet (atau 1 sub-treasury).

        • Tag transaksi pakai project_id dan simpan mapping on-chain addr ↔ project.

        • Tutup periode per proyek (rekon mingguan/bulanan).

      • Tes 5 detik: Bisa nggak export semua transaksi proyek X dalam 1 klik? Kalau tidak, wallet-nya bercampur.

    • Logika bisnis di payments layer

      • Apa itu: aturan produk (harga/discount/refund policy/milestone) ditaruh di gateway/on-ramp/wallet service alih-alih di App/Service.

      • Gejala: pindah vendor/chain = migrasi berat; perubahan kecil butuh ticket ke provider.

      • Risiko: vendor lock-in, duplikasi aturan, sulit diuji (unit test),

    • Tidak ada idempotensi

      • Apa itu: operasi pembayaran (capture/release/refund) bisa tereksekusi ganda saat network retry/webhook duplikat.

      • Gejala: webhook dobel → saldo ganda/dua kali rilis dana.

      • Risiko: over-payment, refund manual, tutup buku kacau.

    • PII nyasar ke tempat publik

      • Apa itu: data pribadi (KTP/paspor, nomor HP, email, alamat, selfie KYC) ikut nongol di log publik, ticket, dashboard, Git, Notion, atau on-chain.

      • Gejala: screenshot/chat yang berisi PII tersebar; field PII "kebawa" ke analitik.

      • Risiko: pelanggaran privasi/kepatuhan, reputasi rusak, remediasi mahal.

    Minimal bukan berarti miskin, minimal berarti berani bilang "cukup": cukup fitur untuk bergerak cepat, cukup catatan untuk tidur tenang, cukup batas untuk selamat.

    Prof. NOTA menyukai kota kecil yang disiplin—karena kota kecil yang rapi lebih mudah dibesarkan daripada metropolis yang kacau. ...

    60s Cut (jika waktu mepet)

    Empat blok: App (order/invoice) → Payments (on/off-ramp + wallet) → Escrow (aturan → kode, opsional) → Records (ledger → akuntansi).

    Pegang satu order_id dari awal sampai akhir, pisahkan peran, dan rekonsiliasi terjadwal. Hindari campur wallet, jangan masukkan logika bisnis ke payments layer, dan jaga PII. Minimal = cepat, sah, dan siap tumbuh. ...

    Role-Play 2 — Escrow untuk transaksi/jual-beli
    • Fokus: kapan perlu escrow, perbedaan trusted intermediary vs rules-as-code, konsep kondisi rilis dan jalur sengketa (tanpa implementasi teknis).

  • Alokasi waktu saran: RP1 20–25’, RP2 20–25’, dan Debrief + Q&A 10–15’

  • Guardrails umum: tanpa rekaman, tidak ada kunci/PII, tidak ada transaksi live, contoh biaya/fee bersifat ilustratif, dan patuh kebijakan kampus.

  • Ekspektasi keluaran segmen ini

    • Peserta bisa menjelaskan trade-off privat vs publik (siapa tahu apa), latensi, dan biaya/overhead pada jalur transfer lintas negara.

    • Peserta memahami kapan escrow diperlukan, apa itu kondisi rilis dan dispute path tingkat konsep, serta kapan memilih tradisional vs smart-contract.

    • Hasil ini menguatkan Output Materi (bagian 7) tentang pemilihan rails, pemahaman escrow, dan sketsa arsitektur minimal.

  • Q&A terstruktur (dibatasi per role-play)

    • Setelah RP1 (Transfer):

      • Ruang tanya: perbandingan langkah/hop, sumber biaya (implisit vs terbuka), finality/konfirmasi, peran on/off-ramp & KYC dasar.

      • Di luar ruang tanya: spekulasi harga koin, rekomendasi investasi, detail teknis chain tertentu yang tidak relevan dengan tujuan belajar.

    • Setelah RP2 (Escrow):

      • Ruang tanya: kriteria butuh escrow, contoh kondisi rilis/milestone, peran manusia dalam sengketa, risiko UX & operasional.

      • Di luar ruang tanya: kode/audit smart-contract, konsultasi legal khusus, implementasi produk riil di luar konteks kelas.

    • Penutup Q&A: rekap poin pembelajaran → lanjutkan ke Next Steps (workshop 3 jam, capstone clinic, research/internship) dan form minat.

  • : pilih rails, baca biaya/latency, kapan escrow, dokumen minimal, dan sketsa arsitektur. Off-track (harga koin, trading, audit mendalam, legal spesifik) kita parkir ke: Workshop 3 jam, Capstone Clinic, atau Research/Internship. Silakan
    angkat tangan, sebut konteks singkat, lalu pertanyaannya
    . Kita cari jawaban yang membuat proyek kalian jalan. ...

    Peserta tahu langkah lanjut (workshop/klinik/internship) dan kanal informasi.

    Kontak: Prof. NOTA

    
    Web2 App / Admin
      - User auth, order info, invoices
    
    Payments Layer
      - On/Off-ramp provider (KYC)
      - Stablecoin wallet (custodial / non-custodial)
    
    Escrow Contract
      - Milestones, release logic, dispute path, time-locks
    
    Records
      - Ledger, invoices, export to accounting

    -1) Pendahuluan

    • Apa itu Blockchain, Smart Contract, dApps? (pelajari dulu di sini: Fundamental Blockchain

    • Bagaimana mengirim uang lintas negara dengan murah & cepat?

    • Kapan escrow perlu jadi kode yang mengeksekusi aturan, bukan sekadar perjanjian?

    0) Struktur Materi

    1) Peta Global Payment Rails — Bank/Fintech vs Stablecoin

    2) Escrow — Traditional vs Smart-Contract

    3) Compliance & Record-Keeping (Student/Startup)

    4) Arsitektur Praktis (Minimal)

    Catatan desain

    • Custodial vs non-custodial: pertimbangkan UX & kepatuhan.

    • Segregasi dana/proyek: kurangi risiko pencampuran.

    • Observability: log transaksi, biaya, & waktu tempuh; siapkan laporan periodik.

    5) Aktivitas Bersama (Role-Play) + Q&A Terstruktur

    Catatan:

    • Detail instruksi untuk masing-masing role-play berada pada dokumen terpisah, International Payments & Escrow Role-Play

    • Bagian ini hanya menyiapkan kerangka, tujuan, dan batasan diskusi agar selaras dengan Output Materi.

    6) Next Steps (Untuk Mahasiswa & Kampus)

    What to do: silahkan scan QR Code (link ke formulir pendaftaran minat); khusus mahasiswa tersedia (kuota terbatas, 30 hari).

    7) Output Materi (Ujian Peserta)

    What to do: silahkan scan QR Code (link ke soal uji coba); jawab dan selesaikan semampunya saja.

    8) Lampiran: Handout Singkat (Ringkasan)

    What to do: silahkan di-Export as PDF; gunakan, dan jangan disebarkan tanpa ijin.

    Prof. NOTA
    International Payments dan Escrow
    Struktur Materi
    Peta Global Payment Rails — Bank/Fintech vs Stablecoin
    Escrow — Traditional vs Smart-Contract
    Compliance & Record-Keeping (Student/Startup)
    Arsitektur Praktis (Minimal)
    Aktivitas Bersama (Role-Play) + Q&A Terstruktur
    Next Steps (Untuk Mahasiswa & Kampus)
    QR Code Interest Form
    Output Materi (Ujian Peserta)
    QR Code Post-Session Quiz
    Lampiran: Handout Singkat (Ringkasan)
    change-blast
    besar.
  • Yang benar:

    • App/Admin pegang aturan bisnis (harga, diskon, policy, milestone).

    • Payments layer cuma adapter yang memindahkan dana & mengirim event (webhook).

    • Escrow logic di smart-contract (kalau dipakai), tapi orchestration/approval tetap di App.

  • Tes 5 detik: Kalau ganti on/off-ramp, apakah logika harga/milestone aman? Kalau tidak, logika kebablasan ada di payments.

  • Yang benar:

    • Setiap operasi punya idempotency_key unik (mis. order_id + langkah).

    • Di DB, upsert berdasarkan idempotency_key + unique constraint.

    • Abaikan event duplikat; log sebagai “already processed”. - Contoh cepat (pseudo):

  • Tes 5 detik: matikan internet saat klik "Bayar", nyalakan lagi → harus jadi 1 transaksi saja.

  • Yang benar:

    • Minimisasi: simpan yang perlu saja, jangan bawa PII ke pipeline analitik umum.

    • RBAC ketat, enkripsi di rest/transit untuk PII; jangan pernah taruh PII on-chain.

    • Masking di log: +62xxxx…, email: a***@domain.

    • Pisahkan storage PII dari transaksi; referensikan via token/ID saja.

  • Tes 5 detik: cari nama/telepon di log/dashboard publik—kalau ketemu, kebocoran sudah terjadi.

  • FIREWALL MANAGER PLAYBOOK

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    1. Short Personal Pitch

    We are not offering you a job. We are offering you a position inside us.

    We need one person—mature, discreet, and strong—to act as our Firewall Manager. Every message, every request, every approach must pass through you before it reaches us. You will guard our time, our energy, and our value.

    Compensation Principle: your reward flows with ours: 26% of every confirmed monthly cash flow attributable to Prof. NOTA’s access and IP (net of pass-through costs and refunds).

    This is not about salary. This is about trust, growth, and alignment.

    If this speaks to you, then we will share the full pact.


    2. Job Description

    You will not just work with us. You will become part of us.


    The Role

    We are seeking one person — mature, trusted, and sharp — to stand as our Firewall Manager. You will be our filter, our guardian, our first avatar in the 0101 Universe and the Universe of Reality.

    Every line of communication flows through you:

    • No one reaches us without passing you.

    • No conversation continues without your clearance.

    • No project touches us unless you confirm its value, its truth, its cash flow.

    You are not an assistant. You are our firewall.


    • Filter — Guard all incoming messages, requests, and proposals.

    • Negotiate — Clarify terms, fees, and commitments before they reach us.

    • Secure — Ensure every opportunity translates into confirmed cash flow.

    • Decide — Say “no” when necessary, firmly yet gracefully.


    Your fee is not fixed. It is flowing. Compensation Principle: You receive 26% of the total monthly cash flow attributable to Prof. NOTA’s access and IP, net of pass-through costs and refunds.

    Examples:

    • If revenue is 111 million IDR → you earn 28.86 million.

    • If revenue is 247 million IDR → you earn 64.22 million.

    You grow as we grow. You win as we win.


    • A person who is mature and grounded.

    • Experienced in marketing and business communication, negotiation, or project management.

    • Able to read people: who is serious, who is false, who is wasting time.

    • Brave enough to say no, gentle enough to say it with elegance.


    This is not a job. This is a pact. A pact to protect the Prof. NOTA universe from noise, from false hope, from wasted time.

    You will be trained by us directly. You will carry our templates, our tone, our way of saying “yes” and “no.” You will be our firewall — until only what is true, fair, and valuable reaches us.


    If these words burn in you, if you feel called to stand as the firewall of Prof. NOTA, then this message is already yours.


    Prof. NOTA is not a product. Prof. NOTA is a universe. Yet from this universe, many values can be drawn — and each carries its price.


    • Designing digital ecosystems with Web3, blockchain, and digital identity.

    • Turning vague ideas into roadmaps, frameworks, and executable systems.

    • Advising startups, institutions, and collectives to avoid vendor lock-in and build ethically sustainable tech.


    • Crafting living documents, manifestos, and layered narratives.

    • Building IP universes (Prof. NOTA, Melting Land, ENDHONESA.COM, BANANOW Land) as cultural assets.

    • Weaving technology, art, and philosophy into brands with depth and soul.


    • Expertise with Next.js, TypeScript, Tailwind, Thirdweb SDK v5.

    • Building dApps, token-gated experiences, wallets, and ERC-20/1155 integrations.

    • Designing modular Web3 stack protocols (incl. EVM/Superchain ecosystems) for organizations and communities.


    • Structuring tokenomics for communities and projects (loyalty → governance).

    • Designing operational workflows for production, distribution, and finance.

    • Translating chaotic creativity into systems that run and scale.


    • Conceptualizing peace movements, global actions, and symbolic tokenization.

    • Initiating board games, AR/VR, and interactive storytelling as education tools.

    • Building bridges between grassroots culture, art, and advanced technology.


    • Prof. NOTA as public intellectual & digital persona — for partnerships, campaigns, and collaborations.

    • “Seduce the Public” content style: sharp, poetic, socially critical, designed to spread.

    • Event presence: as speaker, as avatar, as living symbol of the 0101 Universe.


    • Tailored concepts, documents, or code for specific needs.

    • One-off strategic interventions (e.g., crisis framing, narrative design, rapid Web3 prototyping).

    • Always delivered in Prof. NOTA’s unique register — half intellectual, half digital mystic.


    • Manufacturing Networks — Sourcing and producing goods in China, Spain, the United States, and Canada, with a core in skateboard decks and accessories.

    • Import–Export — Facilitating both inbound (into Indonesia) and outbound (to international markets).

    • Distribution Channels — Building networks across skateshops, retail stores, and lifestyle hubs (co-working spaces, cafes, cultural venues).

    • Curated Goods — Selecting and offering


    ✨ In essence What can be sold is not just “work” but the mind and system of Prof. NOTA. Ideas become frameworks. Frameworks become systems. Systems become movements. Every output carries rarity, because it can only come from here.


    Avatar Eyes Only — do not share externally. These numbers are anchors for crafting proposals, MoUs, and Contracts. For public-facing documents, convert to tiers/ranges without exposing raw anchors.


    • Value > Time. Anchor on outcomes, IP, and risk—not just hours.

    • No free substance. Consultation is paid; PoC/demos follow signed scope.

    • Speed costs extra. Compressed timelines add a rush multiplier.

    • Exclusivity costs extra. Territorial/sector exclusivity uses multipliers.


    • IDR 2,000,000 – 5,000,000 / hour

    • Minimum booking: 1 hour (prepaid).

    • Option: 4-hour pack (prepaid) with no discount unless bundled into a larger scope.

    • Prototype / small scope: IDR 30,000,000 – 70,000,000

    • Mid-scale (dApp, tokenomics, integrations): IDR 100,000,000 – 300,000,000

    • Large-scale (ecosystem, IP + infra): IDR 500,000,000+

    • IDR 50,000,000 – 150,000,000 / month

    • Scope: ongoing strategic access, reviews, and limited build oversight.

    • Define caps/SLOs per Agreement (e.g., response windows, call quotas).

    • IDR 100,000,000 – 500,000,000 / license (frameworks, protocols, narrative IP).

    • Exclusivity multipliers: territory/sector-exclusive × 1.5–3.0; perpetual/global × 2–4.

    Adders & Terms (ID):

    • Rush fee: +25–40% when timeline is compressed beyond baseline.

    • On-site / travel: at-cost + per diem; on-site time billed as Consultation.

    • Default schedule: 50% DP / 40% milestone / 10% final (or 40/40/20); Net 7–14.

    • Late/overdue: pause at 7 days overdue; resume after settlement.


    • USD 300 – 600 / hour

    • Minimum booking: 1 hour (prepaid).

    • Prototype: USD 5,000 – 15,000

    • Mid-scale: USD 20,000 – 60,000

    • Large-scale (ecosystem-level): USD 100,000+

    • USD 5,000 – 15,000 / month

    • Scope: continuous access to Prof. NOTA IP + strategic guidance + limited build oversight.

    • Define caps/SLOs per Agreement.

    • USD 20,000 – 100,000+ (rights to frameworks/protocols/IP usage).

    • Exclusivity multipliers: territory/sector-exclusive × 1.5–3.0; perpetual/global × 2–4.

    Adders & Terms (Global):

    • Rush fee: +25–40% for compressed timelines.

    • On-site / travel: at-cost + per diem; on-site time billed as Consultation.

    • Default schedule: 50% DP / 40% milestone / 10% final (or 40/40/20); Net 7–14.


    Score 1–5 on each axis, then anchor high/low accordingly:

    • Complexity (technical + organizational)

    • Exclusivity (territory/sector/duration)

    • Speed (timeline compression)

    • Risk (compliance, reputational, delivery)

    High scores across axes → use upper anchors + rush/exclusivity multipliers. Low scores → mid anchors; never under baseline.


    1. Do not publish these anchors. Convert to ranges/tiers in offers.

    2. Consultation credit: allow deduction of one paid consult from the project if contracted within 30 days.

    3. Currency: choose invoicing currency up front. For IDR pricing, align to BI middle rate on invoice date if conversion is needed.

    4. Pause rule: work halts when invoices pass due by 7 days; resume upon clearance.

    (Store this section in a private GitBook/GitHub space. Share on a need-to-know basis with avatars only.)


    (Confidential — For Avatars Only)

    Protect Prof. NOTA’s intellectual value, time, and energy from manipulative or unclear communications, ensuring every interaction becomes structured, fair, and compensated.

    Applies to all incoming communications (chat, email, call, DM, in-person) initiated by external parties toward Prof. NOTA or our avatars.

    1. Polite but firm — always acknowledge warmly, never rude.

    2. No free substance — no ideas, drafts, or demos without agreement and payment.

    3. Redirect to clarity — turn vague messages into scope, budget, timeline, ownership.

    4. Money first, access later — confirmed cash flow or signed contract before direct access.


    Step 1 — Initial Screening

    • Friendly / social (e.g., “ayo ngopi”, “apa kabar”) → use Friendly-but-Firm template.

    • Requesting ideas / drafts (e.g., “buat PoC dulu”, “tolong demo”) → use Redirection-to-Clarity template.

    • Potential but unclear (e.g., “brainstorm dulu”, “lihat peluang”) → use Escalation-to-Contract template.

    Step 2 — Clarification (must-have) Ask for four items:

    1. Scope — what exactly is being asked?

    2. Budget — how much is allocated?

    3. Timeline — when is it needed and for how long?

    4. Ownership/Contract — who owns the output and how is Prof. NOTA acknowledged?

    Step 3 — Positioning

    • Decline casual meetups without clarity.

    • Offer a paid consultation as the entry point.

    • Pause the thread until clarity is provided.

    Step 4 — Escalation Escalate to Prof. NOTA only when:

    • Scope, budget, and timeline are confirmed, and

    • Agreement or initial payment is in motion, and

    • The counterpart has demonstrated seriousness.


    1) Friendly-but-Firm

    Thank you for reaching out. At this stage, Prof. NOTA’s time is reserved for structured collaborations with clear value exchange. If you have a specific proposal (scope, timeline, budget), please share it, and our team will review.

    2) Redirection-to-Clarity

    We appreciate your enthusiasm. However, Prof. NOTA’s concepts, drafts, and demos are not provided without confirmed agreements. Please outline the scope, budget, and timeline — and we will gladly explore further.

    3) Escalation-to-Contract (via paid consult)

    Thank you for considering Prof. NOTA. Brainstorming or idea sessions are possible as consultation calls with defined value. The consultation fee applies, and if the project proceeds, it will be deducted from the engagement.


    • Never improvise beyond these templates without internal approval.

    • Never promise free output “for later benefit.”

    • Keep distance: Firewall speaks; Prof. NOTA listens later.

    • Observe the pause rule: overdue invoices > 7 days → work paused; resume after settlement.



    (External-facing; customize per counterpart. Keep internal anchors and SOP private.)


    OFFER LETTER (For discussion only; not a binding agreement)

    To: [Partner/Client Name] From: Prof. NOTA Inc. (PT. Suaka Dunia Raja) Date: [Date]

    Thank you for the opportunity to explore collaboration with Prof. NOTA. This letter outlines an initial offer and commercial framing to guide our discussions.

    • Services: [e.g., Strategic consultation; Web3 prototyping; IP/Narrative architecture; Distribution play]

    • Deliverables: [List expected outputs]

    • Timeline: [Estimated duration / key milestones]

    • Model: [Consultation / Project fee / Retainer / Licensing]

    • Value: [Fee or range in IDR/USD] (final value subject to scope lock)

    • Payment Structure (to be confirmed in Agreement):

      • Option A: 100% upfront; or

    If the above direction aligns, we will proceed to a Contract/Agreement (or MoU if a pre-contract statement of intent is required).

    For Prof. NOTA Inc. Name: __________________ Title: __________________ Date: __________________


    MEMORANDUM OF UNDERSTANDING (MoU)

    Between Prof. NOTA Inc. (PT. Suaka Dunia Raja) — “Prof. NOTA” and [Partner/Client Name] — “Partner”

    Date: [Insert Date]

    The Parties express intent to collaborate on [general domain: Web3 ecosystem / cultural IP / distribution / other] and to develop a definitive Agreement that will define detailed scope, fees, and legal terms.

    • Preliminary scope may include: [high-level bullets].

    • The Parties will exchange required information in good faith to evaluate feasibility, budget, and schedule.

    • Any workshops/consultations are treated as paid consultations unless otherwise agreed in writing.

    All exchanged information, drafts, and discussions are confidential and shall not be disclosed without prior written consent, except as required by law.

    For 12 months from the date hereof, neither Party shall bypass the other to engage core collaborators or directly exploit shared opportunities arising from this MoU without written consent.

    For 12 months, neither Party will solicit for employment or engagement the other’s key personnel directly involved in this initiative, without written consent.

    This MoU is effective from the date above and remains in force until the earlier of: (i) execution of a definitive Agreement, or (ii) [end date/event], or (iii) termination by either Party with written notice.

    Except for Clauses 3–5 (and any expressly stated binding terms), this MoU is non-binding.

    Signed for and on behalf of Prof. NOTA Inc. Name: __________________ Title: __________________ Date: __________

    Signed for and on behalf of [Partner] Name: __________________ Title: __________________ Date: __________


    ENGAGEMENT AGREEMENT

    This Agreement is made on [Date] between:

    • Prof. NOTA Inc. (PT. Suaka Dunia Raja), (“Prof. NOTA”); and

    • [Partner/Client Name], (“Partner”).

    Prof. NOTA will provide the following services:

    • [Detailed tasks and deliverables]

    • Milestones & schedule: [Milestone list with dates/acceptance criteria] Change Management: Any change in scope/timeline/assumptions must be agreed in writing (email is acceptable if explicitly acknowledged by both Parties).

    • Total Fee: [IDR/USD Amount; currency chosen here binds invoicing currency]

    • Payment Schedule (choose one or mix):

      • (A) 100% upfront; or

      • (B) Down Payment [X%] on signing; Milestone [Y%]; Final [Z%] on delivery; or

    All communication runs through the Firewall Manager (Avatar of Prof. NOTA). Direct access to Prof. NOTA requires prior clearance and is contingent on adherence to this Agreement.

    Both Parties will keep confidential any non-public information received from the other. This obligation survives for 3 years post-termination, or longer if the information remains a trade secret.

    • Unless otherwise agreed:

      • Pre-existing IP of each Party remains that Party’s property.

      • New IP created by Prof. NOTA is owned by Prof. NOTA and licensed to Partner on a non-exclusive, non-transferable basis for [field/territory/term], unless a separate assignment or exclusive license is executed and fully paid.

    • Moral rights are reserved unless waived in writing.

    Each Party warrants it has the right and authority to enter this Agreement. No other warranties, express or implied, are made; outputs are provided on an “as-is” basis for the agreed purposes.

    To the maximum extent permitted by law, neither Party is liable for indirect, consequential, or exemplary damages. Aggregate liability of either Party shall not exceed the total fees paid or payable in the 3 months preceding the claim.

    The Parties are independent contractors. This Agreement does not create a partnership, agency, joint venture, or employment relationship.

    For 12 months after termination, Partner will not bypass the Firewall to directly engage Prof. NOTA outside this Agreement, nor solicit the core collaborators of Prof. NOTA who worked under this Agreement, without written consent.

    Neither Party is liable for delays caused by circumstances beyond reasonable control (e.g., natural disasters, war, internet outages, regulations). Affected Party will notify and resume performance promptly.

    • Governing Law: [Indonesia / other jurisdiction].

    • Resolution: Good-faith negotiations for 15 days; failing which, binding arbitration seated in [City, Country], rules of [Arbitration Body], language [English/Indonesian]. Judgment may be entered on the award.

    • Term: Effective on the date above until completion of the Scope or [End Date].

    • Either Party may terminate with [X] days written notice. Partner must pay for all completed work and approved in-progress work.

    • Clauses on confidentiality, IP/licensing (as applicable), limitation of liability, dispute resolution, and payment obligations survive termination.

    Official notices will be sent to the contacts below (email acceptable if acknowledged):

    • Prof. NOTA: [email], Attn: Firewall Manager

    • Partner: [email], Attn: [name]

    This Agreement (including annexes) is the entire understanding and supersedes prior proposals. Amendments must be in writing and signed/acknowledged by both Parties.

    Signatures

    For Prof. NOTA Inc. (PT. Suaka Dunia Raja) Name: __________________ Title: __________________ Date: __________

    For [Partner] Name: __________________ Title: __________________ Date: __________


    INVOICE

    • Invoice No.: [Unique Number]

    • Date Issued: [YYYY-MM-DD]

    • Due Date: [YYYY-MM-DD] (Net [7/14])

    • Agreement Reference: [Contract Title / Date]

    Bill To [Partner/Client Name] [Address / Email / Contact]

    Description of Services

    #
    Item / Milestone
    Period / Date
    Amount

    Subtotal: [Amount] Tax (if any): [Amount] Total Due: [Amount]

    Payment Instructions

    • Bank Transfer: [Bank Name] — [Account Name] — [Account No.] — [SWIFT/IBAN]

    • Crypto (if approved): [Chain] — [Asset] — [Wallet Address]

    • FX Benchmark (if applicable): [e.g., BI middle rate on invoice date]

    Notes

    • Late invoices beyond 7 days may trigger a pause of work per Agreement.

    • Please include Invoice No. in payment reference.

    • Receipt will be issued upon settlement.

    Issued by Prof. NOTA Inc. (PT. Suaka Dunia Raja) — Firewall Manager (Authorized Avatar)


    Below is the decision flow to select Offer → MoU → Contract → Invoice. Use this as a quick guide for avatars (Firewall Manager, etc.).



    You are not hired to say yes. You are entrusted to guard the no—until truth, scope, and money make a worthy yes.

    You stand at the gate where noise becomes silence, and silence becomes value. Every minute you protect, every idea you shield, every contract you anchor—is profit.


    • Clarity before Access. No scope–budget–timeline, no meeting.

    • Value before Work. No cash flow, no draft, no demo.

    • Protocol before Personality. Templates first; never improvise away the guardrails.

    • Dignity in Decline. “No” can be elegant—and final.


    1. Ask — scope, budget, timeline, ownership.

    2. Anchor — consultation or proposal with terms.

    3. Ascend — convert to Contract; issue Invoice; begin.

    Measure your excellence by money secured, time protected, noise prevented.


    Pact: We will stand between Prof. NOTA and the world— firm, fair, unshaken. We will protect the mind with protocol, convert attention into agreements, and agreements into cash flow. We will keep the door closed until the knock carries value.

    Signed: Firewall Manager (Avatar of Prof. NOTA) — date: _______


    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 . 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.


    Mirror — Act as our avatar in human form, without ever betraying what must stay unseen.

  • Document — Log counterpart, date, decisions, and next steps for every thread.

  • Loyal, discreet, and unshaken by pressure.
    authentic, original, handmade, vintage, and collectible items
    with memorable value.
  • ENDHONESA (since 2008) — From vintage/handmade curation to global e-commerce presence (eBay, Etsy, STORE.ENDHONESA.COM).

  • SKATESHOP.ID (since 2004) — From a local skateboard brand → retail → distributor for multiple skateboard brands across Indonesia.

  • Cash before access. Payment schedule is part of the offer, not an afterthought.

    Team Load (hands-on build vs. advisory)

  • Firewall share: book-keep the Firewall Manager’s 26% of confirmed monthly cash flow (net of pass-through costs and refunds) internally each month.

  • Firewall first — all contacts speak to the Firewall; we escalate only when ready.

  • Log everything — counterpart, date, thread summary, decisions, next steps.

  • Respect confidentiality for internal anchors/pricing at all times.

    Option B: [X%] down payment; [Y%] on milestone(s); [Z%] on completion; or

  • Option C: Installments by schedule.

  • Consultation credit: one paid consult may be deducted from the project if contracted within 30 days.

  • (C) Installments: [schedule].

  • Invoicing & Due Date: Net [7/14] from invoice date. Late payments may trigger a pause of work after 7 days overdue until settlement.

  • Taxes: Fees are exclusive of taxes. Partner is responsible for applicable taxes and/or withholding unless required otherwise by law; any withholding must be grossed-up where applicable.

  • Currency/FX: If conversion is required, Parties will use [Bank Indonesia middle rate / agreed benchmark] on invoice date.

  • [Final delivery]

    [date]

    [IDR/USD]

    Silence as Asset. What is not spoken cannot be stolen.

  • Time as Treasury. Your calendar is a vault; unlock it only for contracts.

  • Documents as Sword. Offer → MoU → Contract → Invoice; cut through fog with paper.

  • 1

    [e.g., Down Payment per Agreement]

    [date]

    [IDR/USD]

    2

    [Milestone name]

    [date]

    [IDR/USD]

    What You Will Do

    Compensation

    Who You Are

    What This Means

    Closing

    3. Prof. NOTA — Services & Value

    1. Strategic Vision & Consultation

    2. Intellectual Property & Storytelling

    3. Web3 Development & Prototyping

    4. Business Architecture

    5. Cultural & Social Innovation

    6. Personal Brand Access

    7. Custom Creation

    8. Global Trade & Distribution (ENDHONESA & SKATESHOP.ID Legacy)

    4. Internal Rate Compass (Confidential)

    Pricing Principles

    🔹 Version 1 — Indonesia (IDR)

    1) Consultation / Advisory (per hour)

    2) Project Fee (per engagement)

    3) Retainer (monthly access)

    4) Licensing & IP

    🔹 Version 2 — Global (USD)

    1) Consultation / Advisory (per hour)

    2) Project Fee (per engagement)

    3) Retainer (monthly access)

    4) Licensing & IP

    How to Select a Price (Internal Heuristics)

    Guardrails & Redlines (Internal)

    5. SOP — Communication Firewall

    Objective

    Scope

    Principles

    Standard Response Flow

    Template Responses (ready to paste)

    Guardrails & Redlines

    ASCII Flow (SOP quick map)

    6. Document Templates

    6.1 Offer Letter (Non-Binding)

    1) Introduction

    2) Scope (Draft)

    3) Commercials (Indicative)

    4) Next Steps

    6.2 Memorandum of Understanding (MoU)

    1) Purpose

    2) Understanding

    3) Confidentiality (Binding)

    4) Non-Circumvention (Binding)

    5) Non-Solicitation (Binding)

    6) Duration & Termination

    7) Nature of MoU

    6.3 Engagement Agreement (Contract)

    1) Scope of Work

    2) Fees & Payment

    3) Communication Protocol

    4) Confidentiality

    5) Intellectual Property & Licensing

    6) Warranties

    7) Limitation of Liability

    8) Independent Contractor

    9) Non-Circumvention & Non-Solicitation

    10) Force Majeure

    11) Dispute Resolution & Governing Law

    12) Term, Termination & Survival

    13) Notices

    14) Entire Agreement; Amendments

    6.4 Invoice

    7. Document Flow Diagram

    7.1 ASCII Flow #1

    7.2 ASCII Flow #2

    8. Closing for the Firewall

    The Creed

    Three Moves

    Prof. NOTA

    3

                     ┌─────────────────────────┐
                     │ Incoming Communication  │
                     └────────────┬────────────┘
                                  │
              ┌───────────────────┼───────────────────┐
              │                   │                   │
     ┌────────▼────────┐ ┌────────▼────────┐ ┌────────▼────────┐
     │ Friendly /      │ │ Requesting      │ │ Potential but   │
     │ Social          │ │ Ideas / Drafts  │ │ Unclear Offers  │
     │ ("Ngopi, etc.") │ │ (POC, Demo)     │ │ ("Brainstorm")  │
     └────────┬────────┘ └────────┬────────┘ └────────┬────────┘
              │                   │                   │
     ┌────────▼────────┐ ┌────────▼────────┐ ┌────────▼────────┐
     │ Use Friendly-   │ │ Use Redirection │ │ Use Escalation  │
     │ but-Firm        │ │ to-Clarity      │ │ to-Contract     │
     │ Template        │ │ Template        │ │ Template        │
     └────────┬────────┘ └────────┬────────┘ └────────┬────────┘
              │                   │                   │
              └─────────┬─────────┴─────────┬─────────┘
                        │                   │
                  ┌─────▼───────────────────▼─────┐
                  │       Clarity Achieved?       │
                  └─────────┬───────────┬─────────┘
                            │           │
                     Yes ───▼           ▼── No
                   ┌────────────┐   ┌────────────┐
                   │ Escalate   │   │ Politely   │
                   │ to Prof.   │   │ Decline /  │
                   │ NOTA       │   │ Stop Comm. │
                   └────────────┘   └────────────┘
                      ┌─────────────────────────┐
                      │ New Opportunity Arises  │
                      └────────────┬────────────┘
                                   │
                  ┌────────────────┴────────────────┐
                  │                                 │
     ┌────────────▼────────────┐       ┌────────────▼────────────┐
     │ Needs Only Initial Idea │       │ Parties Ready to Commit │
     │ or Indicative Value     │       │ but Details Not Final   │
     └────────────┬────────────┘       └────────────┬────────────┘
                  │                                 │
        ┌─────────▼─────────┐             ┌─────────▼─────────┐
        │ Proposal/Offer    │             │ MoU (Intentions)  │
        └────────┬──────────┘             └─────────┬─────────┘
                 │                                  │
                 └─────────────────┬────────────────┘
                                   │
                        ┌──────────▼──────────┐
                        │ Contract/Agreement  │
                        │ (Binding & Legal)   │
                        └──────────┬──────────┘
                                   │
                          ┌────────▼────────┐
                          │ Work Execution  │
                          └────────┬────────┘
                                   │
                           ┌───────▼───────┐
                           │ Invoice Issue │
                           └───────────────┘
            ┌───────────────────────────┐
            │ A new opportunity arrives │
            │ (message/meeting req.)    │
            └─────────────┬─────────────┘
                          │
              ┌───────────▼───────────┐
              │ Scope/budget/timeline │
              │ clear & agreed?       │
              └─┬─────────▲─────────┬─┘
                │         │         │
         Yes ───│         │         │── No
          ┌─────▼─────┐   │   ┌─────▼─────────────────────────┐
          │ CONTRACT  |   │   │ Intent to collaborate exists  │
          │ (binding) |   │   │ but details need refinement?  │
          └─────┬─────┘   │   └─────┬─────────▲─────────┬─────┘
                │         │         │         │         │
                │         │   Yes ──│         │         │── No
                │        ┌┴─────────▼┐        │        ┌▼────────────────────────┐
                │        │ MoU       |        │        │ Needs Only Initial Idea │
                │        │ (intent)  |        │        │ or Indicative Value     │
                │        └───────────┘        │        └┬───────────────────────┬┘
                │                             │         │                       │
                │                             │         │── Yes            No ──│
                │                            ┌┴─────────▼──┐          ┌─────────▼──┐
                │                            │ PROPOSAL /  │          │ Politely   │
                │                            │ OFFER (non- │          │ Decline /  │
                │                            │ binding)    │          │ Stop Comm. │
                │                            └─────────────┘          └────────────┘
      ┌─────────▼─────────┐
      │ WORK STARTS       │
      │ (per milestones)  │
      └─────────┬─────────┘
                │
     ┌──────────▼──────────┐
     │ BILLING / INVOICE   │
     │ DP/milestone/final/ │
     │ installments        │
     └─────────────────────┘
    
    -- unique index on idempotency_key
    INSERT INTO payments (idempotency_key, order_id, amount, status)
    VALUES (:key, :order, :amt, 'captured')
    ON CONFLICT (idempotency_key) DO NOTHING;

    STRATEGIC UPDATE FINAL

    An expanded archival edition covering the Product-Led direction, Web3 Login and Smart Account infrastructure, ALPHA product utility, SIMALPHA, future coin considerations, and the framework for evaluat

    Product-Led Direction, Web3 Infrastructure, ALPHA Utility & Future Coin

    Prepared by: Prof. NOTA — Prof. NOTA Inc. Original Date: 7 October 2026 Document Status: Internal Founder Reference Edition: Expanded GitBook Archive Original Format: Three-page A4 Landscape PDF


    Historical Context

    This document was originally prepared on 7 October 2026, ahead of a founder meeting scheduled for 8 October 2026.

    This expanded edition preserves the original strategic position while adding explanations drawn from earlier BGC × iBLOOMING discussions, simulation work, technical planning, and alignment conversations with KK and the related teams.

    It represents my understanding and recommendations before hearing the founders' new business proposal. It should not be interpreted as a final tokenomics specification, a formal approval of every proposed mechanism, or a record of the meeting's outcome.


    Before tomorrow's meeting, I want to give a short update on where I think the work stands today.

    When we started, much of the discussion was about Web3 Login, ALPHA, token flow, and eventually a BGC × iBLOOMING coin.

    Over the past year, I have worked through the existing business rules, historical data, simulation design, UI/UX discussions, and technical architecture.

    That process has helped me understand something important.

    We have several things that can work together, but they do not necessarily belong in the same implementation or need to be completed at the same time.

    I now find it useful to separate the work into four areas:

    1. Product direction — What customers need, what iBLOOMING delivers, and what makes the products valuable.

    2. Web3 infrastructure — How users log in, establish identity, and interact with wallets or Smart Accounts.

    3. ALPHA product utility — What users may earn, acquire, spend, or use within the product experience.

    4. Future coin and tokenomics — Whether a separate coin is justified and how its economics should work.

    They can still connect.

    I just don't think we should force them into one system before we know what each part is actually for.

    This is not a statement that we should stop exploring a coin. It is a recommendation about how we should approach the work without creating unnecessary complexity or committing to decisions too early.


    Current position: Working strategic direction

    My view at this point is simple: start from the product and the user.

    Web3, ALPHA, NFT or other digital credentials, AI, and similar technology should help people do something useful.

    Depending on the product, that could mean making a purchase easier, improving access, recording ownership, giving users a reason to return, or creating a better overall experience.

    The technology should support that value, not become the reason a product exists.

    For iBLOOMING, I think we should examine product opportunities through measurable outcomes.

    Objective
    What We Need to Understand

    This is what I mean by Product-Led.

    It does not mean every feature must produce immediate revenue, or that every blockchain-related idea should be rejected.

    It means that we should first understand what value the product delivers and what behaviour we want to improve.

    Once that is clear, we can ask whether Web3, ALPHA, AI, or another technology provides a meaningful advantage.

    The earlier stages of our work naturally focused on how existing BGC and iBLOOMING mechanisms might be translated into blockchain-based systems.

    That was a useful exercise. It required us to understand how the existing business works, how rewards are calculated, how data moves, and where the operational dependencies exist.

    But understanding an existing mechanism does not automatically mean that every part of it should become a token or an on-chain transaction.

    I would rather identify the product needs first, then choose the technology that helps us solve them.

    My recommendation is to build technology around validated product value, rather than design products merely to give a token something to do.

    This remains a strategic recommendation and should not be confused with a formal founder resolution approving every aspect of a Product-Led transition.


    Current position: Infrastructure track

    The Web3 Login technical architecture has already been prepared and handed to Yuku's engineering side for implementation.

    Its immediate purpose is to establish an identity and wallet-ready foundation for BGC × iBLOOMING users.

    The intended user journey discussed with KK and the UI/UX team is:

    BGC × iBLOOMING Account

    → Sign Up / Login → Activate Smart Account → Accept Smart Account Terms → Personal Wallet / EOA → Smart Account

    This describes the proposed account and wallet experience. It does not mean every function had already been deployed.

    The important point is that the user should be able to understand and use the account system without first having to become familiar with blockchain terminology or cryptocurrency transactions.

    The immediate work concerns user identity, authentication, account activation, consent, wallet association, and the technical foundation for future Web3-enabled features.

    It does not require us to finish every possible ALPHA function first.

    A Smart Account may eventually support product access, utility transactions, digital credentials, or other functions. But that does not mean those functions are automatically included in the initial Web3 Login implementation.

    I also want to maintain one important UI/UX distinction.

    Showing a Smart Account does not mean we are asking users to trade cryptocurrency.

    Similarly, the current interface does not need to display ALPHA earning and spending features before those features have been properly defined.

    The Web3 Login architecture can progress as a separate infrastructure workstream.

    The engineering team should not have to wait for complete ALPHA tokenomics merely to implement identity, login, account activation, or wallet-ready infrastructure.

    At the same time, I understand the concern raised during the UI/UX discussions: users should have a clear reason to activate a Smart Account.

    We should address that concern by identifying useful product features while the infrastructure is being developed.

    We do not need to invent final ALPHA economics simply to justify a wallet interface.


    Current position: Product-utility layer under definition

    My suggestion is that ALPHA should first be tested as an internal Product-Led utility.

    In practical terms, this means ALPHA should have a clear purpose in the product experience.

    Users should be able to understand why they might need it, how they obtain it, and what they can do with it.

    I see four possible utility areas worth examining.

    Which eligible activities should allow users to earn ALPHA?

    An activity should have a genuine connection to a product objective. We should understand why we want to reward that behaviour and whether the reward improves the experience or business outcome.

    Should users be able to acquire or top up ALPHA through an approved mechanism?

    This may include fiat payments, as discussed with KK, but the mechanism itself still requires product, economic, accounting, and operational decisions.

    Which iBLOOMING products, reports, content, features, or services should accept ALPHA?

    This is particularly important because spending creates a direct relationship between the utility and the products available in the ecosystem.

    Could ALPHA or a separate digital credential provide access rights, verifiable participation, ownership records, or other meaningful benefits?

    Not every access or ownership feature needs a fungible token. We should choose the appropriate mechanism for each product need.

    Although these possible utilities have been discussed, we have not yet fixed the complete earning, acquisition, spending, conversion, issuance, and economic rules.

    Before those rules are finalised, we need to know:

    • Which existing products or activities are suitable.

    • Whether new product activities are needed.

    • What behaviour each utility is intended to improve.

    • Whether fiat acquisition is appropriate and approved.

    The intention is to define a product utility that makes sense before committing to its detailed implementation.

    Earlier documents also considered ALPHA in relation to the existing BGC business rules and simulation.

    That work remains part of our project history.

    However, I do not want to assume that existing Purchase Credits, Sales Points, affiliate rewards, pools, or obligations must automatically be converted into ALPHA balances.

    Those mechanisms already have their own business definitions and responsibilities.

    Any connection to ALPHA should be justified, specified, and tested rather than treated as an automatic consequence of tokenisation.


    Current position: Internal decision-support tool

    The simulator is useful because it allows us to examine assumptions and compare possible scenarios.

    It helps us understand how different choices might affect outcomes, especially when economic parameters, user behaviour, and operational costs change.

    I see SIMALPHA as a way to support better decisions, not as a tool that automatically supplies the correct answer.

    For example, simulation can help us examine:

    • How sensitive a result is to a particular assumption.

    • What changes under different demand or usage scenarios.

    • Which variables have the greatest effect on costs or liabilities.

    • Where available data supports a conclusion.

    This distinction is important.

    A simulator can produce precise-looking numbers even when some of its assumptions remain uncertain.

    The precision of an output does not necessarily establish the validity of the underlying economic model.

    I would not present our simulation work as proof that final tokenomics are ready, that all business obligations have been validated, or that a future public coin can safely proceed.

    The simulation should help us identify what needs to be tested or decided next.

    It should not be used to create confidence that the available evidence does not yet support.


    Current position: Separate future decision

    For the future coin, I don't think we should lock the model yet.

    Before deciding supply, distribution, pricing, conversion mechanisms, or a market strategy, we need to understand what role the coin would actually play in the business.

    Names such as iBC and iBTC have been discussed. Another model may also be proposed by the founders.

    The name itself is not the important decision.

    I would first want to understand:

    • Why the business needs a separate coin.

    • Why users or market participants would want it.

    • What creates genuine demand.

    • How value enters and leaves the system.

    • How the coin relates to actual products and services.

    The Product-Led ALPHA approach can help us generate evidence.

    If ALPHA utility later proves to improve product usage, purchases, retention, or revenue, those findings may inform the design of future coin economics.

    But that progression is not automatic.

    A useful internal ALPHA system does not necessarily mean we must launch a public token.

    The future coin should remain a separate decision, with its own business case and validation requirements.


    Area
    Position on 7 October 2026
    Still Required

    The sequence I want to keep in mind is:

    Build the foundation. Prove the utility. Measure the behaviour. Then design the economics.


    The layers should connect, but they should not be confused.

    We should begin with a real product or user need.

    Then we define what we want to improve.

    Only after that do we decide how Web3 infrastructure and ALPHA utility might help.

    What does the user actually need, buy, use, return to, or value?

    This is where I want every new proposal to begin.

    We should be able to explain the customer's problem, expectation, or motivation without referring to a coin.

    Once the need is understood, we define the intended outcome.

    That could be:

    Purchase · Usage · Access · Retention · Revenue

    We may also examine repeat behaviour, ownership, completion, or other measurable results.

    The objective should guide the technology decisions that follow.

    I suggest that we proceed with two separate but coordinated tracks.

    Workstream A — Web3 Login + Smart Account

    This provides the identity, account, authentication, activation, and wallet-ready infrastructure.

    The implementation can continue within the agreed infrastructure scope.

    Workstream B — ALPHA Product Utility

    This defines the eligible products and activities, intended user benefits, possible earning and acquisition methods, spending cases, and the rules needed for each.

    The two workstreams can move in parallel.

    We do not need to wait for all ALPHA economics before progressing with identity infrastructure. Likewise, completing Web3 Login does not automatically complete the ALPHA product model.

    Once the relevant infrastructure and utility are ready, they should support real interactions within the product.

    Examples might include access to a purchased report, use of a digital service, participation in an eligible activity, or verification of an entitlement.

    The implementation must be connected to an actual user experience.

    After implementation or testing, we should examine what users actually do.

    Are they purchasing? Returning? Using the product? Completing activities? Finding lasting value?

    Evidence should help us distinguish useful functionality from functionality that merely exists.

    Only after understanding the relevant product behaviour and economic implications should we decide whether a future coin is justified.

    The conceptual sequence is:

    Product / User Need

    ↓

    Product-Led Objective

    ↓

    Two Parallel Tracks

    • Web3 Login + Smart Account

    • ALPHA Product Utility

    ↓

    Product Experience

    ↓

    Evidence: Conversion · Usage · Retention · Revenue · Repeat Behaviour

    ↓

    Future Coin / Tokenomics Decision

    This is a decision-making framework, not a statement that every component had already been implemented.

    Layer
    Its Main Purpose
    What It Does Not Automatically Mean

    Web3 Login is not ALPHA, and ALPHA is not automatically the future coin.

    The separation is intentional.

    It allows Engineering to move forward while we continue defining product utility and validating economics before making larger decisions.


    A useful example came from the discussion with KK.

    He raised the possibility that users might eventually use ALPHA to purchase iBLOOMING products.

    In that scenario, users could acquire or top up ALPHA using fiat, then use ALPHA through their Smart Account to purchase selected reports, products, or services.

    The possible flow is:

    FIAT / CASH

    ↓

    ACQUIRE / TOP UP ALPHA

    ↓

    SMART ACCOUNT

    ↓

    USE ALPHA

    ↓

    SELECTED iBLOOMING PRODUCTS / REPORTS / SERVICES

    This is a possible product flow, not a final economic rule.

    This creates a practical connection between ALPHA and actual products.

    Instead of asking users to acquire a token without knowing what it is for, the system could potentially connect acquisition and spending to products users already want.

    That gives us a clearer way to discuss utility.

    We could examine whether the mechanism improves product access, purchase behaviour, or the overall experience.

    However, we should not assume it provides an advantage merely because the flow is technically possible.

    Before implementing this use case, I think the founders and Product Team should determine the following.

    Eligible products

    Which reports, services, features, or other products can accept ALPHA?

    Acquisition mechanism

    Will users be permitted to acquire or top up ALPHA using fiat?

    If yes, how should that process work?

    Economic definition

    What does one unit of ALPHA represent? How does it relate to a product price, an internal right, or another defined unit?

    Earning rules

    Can users earn ALPHA through eligible product activities as well as acquire it?

    Spending and conversion rules

    What happens when ALPHA is spent? How is the purchase recorded and fulfilled? What happens to the ALPHA used?

    Issuance and accounting

    How are balances created, recorded, reconciled, and accounted for?

    User experience

    What should the user see and understand about balances, purchases, terms, and account activation?

    Economic validation

    What are the effects on business revenue, operational costs, liabilities, and overall sustainability?

    These are open decisions. They should not be mistaken for mechanisms already approved or implemented.

    When KK raised this possible fiat-to-ALPHA purchase flow, my response was that it should be included in the ALPHA product-utility discussion.

    It should not be treated as part of the immediate Web3 Login implementation by default.

    KK agreed with that distinction.

    That alignment was useful because it allowed us to preserve the current infrastructure scope while recognising a possible future product feature.

    It was not a final approval of the fiat top-up model or all its economic rules.

    A concern raised in the UI/UX discussion was that users should have a clear reason to activate a Smart Account.

    I think that concern is valid.

    The answer is not to stop all infrastructure work until complete tokenomics are available.

    Nor is it to invent token features prematurely.

    The better approach is to continue the Web3 Login infrastructure while defining ALPHA's first meaningful product use cases.

    That way, Engineering can make progress, and the Product Team can establish a clear reason for users to benefit from the account.


    I want to hear the new iBLOOMING idea first.

    Then I want to map it against what we have already learned instead of forcing an answer before understanding the proposal.

    New ideas are welcome.

    The purpose of this framework is not to restrict them, but to understand what should be built, why it matters, and in what sequence.

    The evaluation sequence is:

    User Need → Product / Service → Business Model → Desired Behaviour → Utility → Technology → Economics & Risk → Evidence

    What real problem or desire are we solving?

    Who is the intended user?

    Why would that person care about this product or service?

    What is missing from the current experience?

    I want to understand the need before discussing the technology.

    What are users actually buying, using, or accessing?

    What does the business deliver?

    What makes the offering valuable?

    How does the business earn revenue?

    One question I would keep in the discussion is:

    Would it still create customer value without an income opportunity or a coin?

    I think this is an important test.

    It is not meant to dismiss the existing affiliate business or oppose the possibility of a token.

    It helps us examine whether the proposed product delivers value in its own right.

    If the product is genuinely useful, we have a stronger foundation for designing additional incentives or utility mechanisms.

    What do we want to improve?

    Depending on the idea, the objective might be:

    • Purchase conversion.

    • Product usage.

    • Completion of an activity.

    • Retention.

    • Repeat purchase.

    Before creating an earning or reward mechanism, I want to know why we want users to perform the activity.

    Otherwise, we may create activity without establishing whether it benefits the product or the business.

    What should ALPHA, Web3, AI, or digital credentials actually do?

    Does the idea need a blockchain-based entitlement, a Smart Account, a digital record, an automated service, a payment mechanism, or a verifiable credential?

    Could ordinary technology solve the same problem more clearly and with less complexity?

    If a simpler solution works better, I would not force blockchain into it.

    Technology selection should follow the product requirement.

    Why does the idea need a coin?

    What creates demand for it?

    How does value move through the business?

    How are users expected to benefit?

    Does the coin create additional responsibilities, costs, or liabilities?

    If a public market is involved, what happens when market behaviour differs from the behaviour of actual product users?

    I would rather understand those questions before choosing a supply figure, conversion formula, or market strategy.

    The important thing is not whether we can issue a coin.

    It is whether the proposed economic mechanism supports the business and its users in a sustainable way.

    What must we measure before scaling?

    The important areas include:

    Usage · Conversion · Retention · Repeat Behaviour · Revenue · Cost · Liabilities · Sustainability

    We should decide which assumptions can be tested through historical data, which need simulation, and which require actual product usage.

    I do not expect every answer to exist on the first day.

    But a useful proposal should help us identify what evidence we need and what findings would cause us to adjust the plan.


    My immediate objective is to listen first.

    KK has informed me that the founders want to discuss a new iBLOOMING business idea that may also connect to “our coin.”

    At this point, I do not want to assume what that relationship means.

    It may involve ALPHA, a future coin such as iBC or iBTC, or a different model being considered by the founders.

    We need to hear the proposal before determining which interpretation is appropriate.

    During the meeting, I want to understand the new idea as completely as possible.

    In particular:

    1. What business or product activity is being proposed?

    2. Who are the intended users or customers?

    3. What problem does the idea solve?

    4. What value will the users receive?

    5. How will the business earn revenue?

    I do not need to answer every question immediately.

    I would rather understand the idea properly than give advice based on incomplete information.

    Once the idea is clear, I can evaluate it against the work we have already completed.

    That assessment should examine the product, the customer experience, the proposed business model, and the relationship with existing or proposed technology.

    It should also identify unresolved economic, operational, and implementation questions.

    From there, I can prepare a more structured recommendation for the founders.

    The intention is to make the next discussion more productive, with a clearer explanation of:

    • What the new idea requires.

    • Which existing work can support it.

    • Which parts need further clarification.

    • What could be tested first.

    • Which decisions belong to the founders.

    This describes my intended approach before the meeting, not a record of what was subsequently decided.


    Another topic that KK and I have discussed is the possibility of guiding the Jakarta staff in managing social media and growth-related activities.

    I have already prepared an initial approach to that work.

    My intention is not simply to take over daily social-media posting or advertising operations.

    I see a more useful role in helping the existing team establish a better way to plan, execute, measure, and improve its work.

    If we proceed, I would suggest a separate discussion covering:

    Discovery / Audit

    Understand the current social media accounts, objectives, content, campaigns, available data, tools, and staff responsibilities.

    Staff Training

    Help the team understand the relevant workflows, audience planning, campaign processes, measurement, and reporting.

    Operating Process

    Establish practical procedures for campaign planning, execution, tracking, coordination, and review.

    Supervised Execution

    Guide the staff during initial implementation so the team can eventually operate more independently.

    The exact scope and responsibilities should be discussed and agreed with KK.

    I would prefer to keep this workstream separate from the discussion about ALPHA and the future coin.

    The marketing work may later support the same products and business objectives, but it should not distract us from understanding the founders' new proposal first.


    I want this document to remain useful when we refer to it later.

    For that reason, I think it is important to be clear about what the update establishes and what it does not.

    As of 7 October 2026, my working assessment is that:

    • Product needs should guide technology and utility decisions.

    • Web3 Login and Smart Account infrastructure can progress independently of final ALPHA economics.

    • ALPHA should be examined through actual product use cases.

    • The possible fiat-to-ALPHA purchase flow deserves further product and economic evaluation.

    This document does not mean that:

    • All founders have formally approved every part of a Product-Led strategy.

    • Web3 Login and Smart Account implementation has been completed.

    • ALPHA earning, spending, acquisition, or conversion rules are final.

    • Fiat top-up has been fully approved.

    I want to preserve these distinctions because project documents can easily become misleading when working recommendations are later read as final decisions.


    We have spent considerable time trying to understand the existing business, its mechanisms, the possibilities of Web3, and the relationship between products and token economics.

    That work should not be lost simply because a new idea arrives.

    At the same time, the work should not prevent us from considering something better.

    I want to use what we have learned as a foundation for understanding the next proposal.

    We can remain open to new business models, new product opportunities, and a future coin while continuing to ask what users actually need and what the business can realistically sustain.

    The point is not to make technology more complicated.

    It is to make our decisions clearer.

    We are not trying to fit the business around a coin.

    We are building enough evidence to know where a coin can genuinely strengthen the business.

    OiOi.

    Prof. NOTA Prof. NOTA Inc. 7 October 2026


    This document is an expanded Markdown adaptation of the original three-page PDF:

    BGC × iBLOOMING — Strategic Progress Update

    Original source: BGC-x-iBLOOMING-Strategic-Update-FINAL-2026-10-07.pdf

    Original preparation date: 7 October 2026 Original purpose: Internal founder reference before the 8 October 2026 meeting Archival adaptation: 19 October 2026 Publishing format: GitBook Markdown

    The original PDF provides the primary structure and substantive positions: Product-Led direction, Web3 Login and Smart Account infrastructure, ALPHA product utility, SIMALPHA, future coin considerations, the relationship among those layers, the example of acquiring ALPHA with fiat for product purchases, the framework for evaluating new business ideas, and the separate Social Media & Growth Enablement workstream.

    The expanded explanations preserve the context of earlier project discussions, including technical planning, simulations, UI/UX alignment, and conversations with KK.

    These additions are intended to make the original position easier to understand and refer to. They do not introduce new founder approvals, confirm implementations that were still pending, or describe events after the original document date.

    End of Document.


    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 . 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.


    Repeat Purchase

    Does the experience encourage customers to buy again?

    Revenue

    Can the product create sustainable business value?

    How ALPHA is valued, issued, used, or consumed.
  • What accounting and operational responsibilities arise.

  • How the system will measure whether the utility is useful.

  • Where the model still depends on assumptions or incomplete coverage.
  • What obligations or risks the mechanism creates.

  • How the proposed economics could remain sustainable.

  • Which legal, operational, accounting, and market questions must be addressed.

  • Internal scenario and decision-support capability

    Further evidence and validation

    Future Coin

    Possible separate economic layer

    Business case, economic model, risk assessment, and approval

    New iBLOOMING Business Idea

    Not yet presented in full to me

    Founder presentation and subsequent assessment

    Separate economic and possibly market-facing model

    Necessary simply because Web3 is being used

    Referral.

  • Access.

  • Ownership.

  • Why is a coin relevant to the proposed model?

  • What role will ALPHA, Web3, AI, or Smart Accounts play?

  • Will the new idea affect existing BGC or iBLOOMING mechanisms?

  • What would the founders like to achieve first?

  • What the engineering or product teams would need to implement.

  • SIMALPHA can support decisions but does not automatically validate final tokenomics.
  • A future coin should be treated as a separate economic decision.

  • The founders' new business proposal should be understood before we recommend how it should be implemented.

  • ALPHA is automatically the same as a future public coin.
  • A future coin has been approved for issuance, trading, or listing.

  • The simulator has proven complete economic sustainability.

  • The founders' new business proposal has already been evaluated.

  • A recommendation has already been made about an idea that had not yet been presented.

  • Purchase

    Does the feature help users decide to buy a product?

    Usage

    Does it encourage users to actually use what they have purchased?

    Access

    Does it make products, features, or services easier to access?

    Ownership

    Is there a meaningful need for a digital entitlement, credential, or proof?

    Retention

    Product-Led Direction

    Working strategic recommendation

    Alignment on product priorities and use cases

    Web3 Login + Smart Account

    Architecture prepared and handed to engineering

    Implementation and testing

    ALPHA Product Utility

    Potential internal utility being defined

    Earning, acquisition, spending, conversion, and economic rules

    Web3 Login

    Identity, login, and wallet-ready infrastructure

    Users must trade crypto

    Smart Account

    Account infrastructure for future features

    ALPHA economics are complete

    ALPHA

    Candidate internal product utility

    Public coin or market listing

    1. Why I Am Sharing This Update

    2. Where the Work Stands

    2.1 Product-Led Direction

    Why This Direction Matters

    2.2 Web3 Login + Smart Account

    What This Infrastructure Is Intended to Provide

    The Engineering Dependency

    2.3 ALPHA Product Utility

    Earn

    Acquire

    Spend

    Access / Credentials

    What Has Not Been Finalised

    Relationship with Earlier ALPHA Work

    2.4 SIMALPHA

    2.5 Future BGC × iBLOOMING Coin

    2.6 Summary of the Current Position

    3. How I Think the Layers Should Connect

    3.1 Product / User Need

    3.2 Product-Led Objective

    3.3 Two Parallel Workstreams

    3.4 Product Experience

    3.5 Evidence

    3.6 Future Coin Decision

    3.7 Keeping the Responsibilities Separate

    4. One ALPHA Use Case We Already Discussed

    4.1 Why I Think This Is Worth Exploring

    4.2 What Needs to Be Decided First

    4.3 Why This Belongs Outside the Initial Web3 Login Scope

    4.4 A Practical Point About Smart Account Activation

    5. A Framework for Evaluating the Next iBLOOMING Business Idea

    5.1 User Need

    5.2 Product & Business

    5.3 Desired Behaviour

    5.4 Utility & Technology

    5.5 Coin & Economics

    5.6 Evidence

    6. For the 8 October Founder Meeting

    6.1 What I Want to Understand

    6.2 What I Intend to Do After the Meeting

    7. Separate Workstream — Social Media & Growth Enablement

    8. Important Boundaries of This Update

    What This Update Establishes

    What This Update Does Not Establish

    9. Closing Perspective

    Archive & Source Note

    Prof. NOTA

    Does it give users a good reason to return?

    SIMALPHA

    Future Coin

    0101 PARLIAMENT BLUEPRINT

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    0101 Parliament — Perwakilan yang Dapat Difork (Blueprint Prof. NOTA)

    Tujuan (singkat) Ini adalah karya civic-tech + budaya di Semesta 0101 (ruang digital). Dokumen ini bukan klaim untuk membubarkan DPR RI secara hukum. Ia mendemonstrasikan—secara terbuka, damai, dan terukur—bagaimana “kedaulatan rakyat” dapat dipraktikkan dengan mem-fork sebuah kembar-digital perwakilan ketika legitimasi jatuh di bawah metrik yang disepakati. Kekerasan ditinggalkan. Transparansi diwajibkan.


    A) Realitas Hukum Indonesia (singkat, sebagai pagar batas)

    • Dalam kerangka hukum Indonesia, tidak ada “tombol” konstitusional untuk membubarkan DPR. UUD 1945 Pasal 7C tegas menyatakan Presiden tidak dapat membekukan atau membubarkan DPR. Rujukan: UUD 1945 (MK RI) – Pasal 7C, PDF, .

    • PAW/recall anggota diatur undang-undang (mis. UU No. 17 Tahun 2014 – MD3) dan bersifat melalui partai politik, bukan “langsung oleh rakyat.” Rujukan: , , .

    • Amandemen konstitusi (Pasal 37 UUD 1945) adalah rute formal untuk mengubah kerangka, namun politisnya berat: pengajuan oleh ≥ 1/3 MPR dan ambang persetujuan tertentu. Rujukan: , .

    Kesimpulan dunia nyata: Tidak ada jalur instan untuk “membubarkan DPR”. Yang tersedia: pemilu, PAW/recall via partai, dan amandemen UUD. Karena itu, blueprint ini adalah cermin digital yang damai—sebuah perwakilan yang dapat difork untuk mendidik, mengukur legitimasi, dan mendokumentasikan kehendak warga tanpa klaim kekuatan hukum.


    • Kita tidak membakar institusi; kita mengarsipkan dan mem-fork.

    • Bangun perwakilan publik yang dapat difork dan diaudit, di mana “dissolve” berarti mengarsipkan instansi berjalan dan memunculkan instansi baru saat legitimasi gagal.

    • Ini adalah seni + rekayasa + pedagogi. Menunjukkan metodenya; tidak menghasut kekerasan atau tindakan melawan hukum.

    1. Tanpa kekerasan & sesuai hukum (budaya/civic-tech/edukasi).

    2. Aturan & data terbuka (charter, event, dan kode transparan).

    3. Fork-by-design (jika legitimasi gagal, lahir instansi baru; sejarah tetap).

    4. Anti vendor lock-in (modular, multi-chain, mudah pindah).

    • Frontend: Next.js + TypeScript + Tailwind.

    • Wallet/AA: Thirdweb SDK v5 (embedded wallet + smart account).

    • Rantai: Base (L2, biaya rendah) untuk aksi publik; opsional EVM privat (Besu/IBFT) untuk draf deliberasi sensitif.

    • Governance:


    1. Seats-as-Tokens (SBT/ERC-1155, opsional)

      • “Kursi”/“Badge Pemilih” yang non-transferable untuk pendekatan one person, one vote (bisa diupgrade).

    2. Indeks Legitimasi (IL) — skor 0–1 (atau 0–10000 bps) dari metrik publik, misal:

      • QuorumRate

    Bahasa publik: “Saat perwakilan digital gagal, publik fork—tanpa gas air mata; hanya metrik transparan dan sejarah yang diarsip.”


    • Monorepo 0101-parliament.

    • Halaman publik: /debates, /vote/[proposalId], /dashboard, /charter.

    • Kontrak v0 untuk status + event dissolve; voting off-chain dulu.

    • Implement orakel IL (sederhana, alamat updater).

    • Terapkan DT-A (indeks) + DT-B (votum) → status=ARCHIVED + event.

    • Bangun Dashboard (grafik IL, tren kuorum, pemilih, lineage).

    • Tambah circuit breaker

    • AA + Paymaster (gasless).

    • SBT/POAP (heuristik anti-Sybil).

    • Deliberasi terenkripsi untuk draf sensitif; terbitkan ringkasan.

    • Adapter untuk memetakan isu dunia nyata tanpa klaim legal.


    • Apa ini: kembar-digital perwakilan yang dapat difork.

    • Apa bukan: bukan lembaga negara; bukan nasihat hukum; bukan ajakan tindakan melawan hukum.

    • Aturan: target kuorum, formula & ambang IL, kondisi DT, kebijakan fork.

    • Etika & Lisensi: kode terbuka, anti-ujaran kebencian, anti-kekerasan, hormati privasi.


    ID (pendek)

    Kami tak mencari tank. Kami mencari fungsi. Ketika wakil digital gagal, kami fork—tanpa gas air mata. Kedaulatan: fitur, bukan slogan. #OiOi #0101

    EN (pendek)

    We don’t burn institutions; we archive and fork. Legitimacy is open-source. Violence is deprecated. #OiOi #0101


    • Bukan nasihat hukum; edukasi & budaya.

    • Tidak mengajak tindakan kekerasan atau melawan hukum.

    • Moderasi anti-hoaks & anti-ujaran kebencian.

    • Publikasi yang menghormati privasi (agregat atau dianonimkan).


    Catatan: Minimal dan edukatif. Menggunakan pendekatan 1 alamat = 1 suara (sementara; dapat ditingkatkan ke SBT/POAP). Memiliki dua jalur dissolve: berbasis indeks (orakel memperbarui IL) dan berbasis votum (#DISSOLVE lulus).


    Implementasi perhitungan IL dilakukan off-chain dengan kode sumber terbuka; publikasikan input, output, dan tanda tangan dari alamat oracle ke publik.


    Contoh tipe helper TypeScript untuk lib/parliament.ts:


    • UUD 1945 – Pasal 7C (Presiden tidak dapat membubarkan DPR): MK RI (PDF): https://mkri.id/public/content/profil/kedudukan/UUD_1945_Perubahan%204.pdf Kominfo (PDF): https://ppidkemkominfo.files.wordpress.com/2017/09/uud-1945-satunaskah.pdf

    • PAW / Recall oleh partai (UU 17/2014 MD3): Analisis hak recall (Pasal 239(2)) – UP45 (PDF): https://ejournal.up45.ac.id/index.php/JHCJ/article/download/2192/1299/8097 Sistem PAW & praktik – USAHID (PDF): https://jurnal.usahid.ac.id/hukum/article/download/1998/880/5332 Landasan PAW (Pasal 22B UUD) – UNIGHA (PDF): https://journal.unigha.ac.id/index.php/JSH/article/download/231/279

    • Amandemen Konstitusi (Pasal 37 UUD 1945): Hukumonline: https://www.hukumonline.com/klinik/a/prosedur-perubahan-uud-1945-dan-dasar-hukumnya-lt618a54773ee93/ Detik: https://news.detik.com/berita/d-5737492/ini-mekanisme-dan-tata-cara-amandemen-uud-nri-1945


    Blueprint ini damai, edukatif, dan sumber-terbuka. Ia menghormati hukum Indonesia, sekaligus memberi warga cermin digital yang dapat difork untuk mempraktikkan akuntabilitas dan pengambilan keputusan kolektif.

    Semboyan: “Dissolve adalah fitur, bukan ancaman.” — Prof. NOTA



    Purpose (tl;dr) This is a civic-tech + cultural work in the 0101 Universe (digital space). It does not claim to dissolve Indonesia’s DPR in real life. Instead, it demonstrates—openly, peacefully, and measurably—how “sovereignty of the people” can be exercised by forking a digital twin of representation when legitimacy falls below agreed metrics. Violence is deprecated. Transparency is mandatory.


    • In Indonesia’s real legal framework, there is no constitutional “button” to dissolve DPR. The 1945 Constitution, Article 7C explicitly states the President cannot freeze or dissolve DPR. See: , .

    • Member replacement/recall (PAW) is regulated by statute (e.g., UU No. 17 Tahun 2014 – MD3); recall is party-driven, not “direct by the people.” See: , , .

    • Constitutional amendment (Pasal 37 UUD 1945) is the formal route to change the framework and is politically arduous: requires proposal by ≥

    Conclusion for IRL: There is no immediate legal path to “dissolve DPR”. What exists: elections, party-driven recall/PAW, and constitutional amendment. Therefore this blueprint is a digital, peaceful mirror—a forkable representation to educate, measure legitimacy, and document civic will without claiming legal force.


    • We don’t burn institutions; we archive and fork.

    • Build a public, forkable, audit-able representation where “dissolve” means archive current instance and spawn a new one when legitimacy fails.

    • This is art + engineering + pedagogy. It shows the method; it does not incite violence or illegal acts.

    1. Non-violence & legality (cultural/civic-tech/education).

    2. Open rules & open data (transparent charter, events, and code).

    3. Fork-by-design (if legitimacy falls, a new instance is born; history remains).

    4. Anti vendor lock-in (modular, multi-chain-capable).

    • Frontend: Next.js + TypeScript + Tailwind.

    • Wallet/AA: Thirdweb SDK v5 (embedded wallet + smart account).

    • Chain: Base (L2, low fees) for public actions; optionally private EVM (Besu/IBFT) for sensitive deliberation logs.

    • Governance:


    1. Seats-as-Tokens (optional SBT/ERC-1155)

      • Non-transferable “Seats” or “Voting Badges” to enforce one-person-one-vote heuristics (upgradeable later).

    2. Legitimacy Index (LI) — a 0–1 score (or 0–10000 bps) computed from public metrics, e.g.:

      • QuorumRate = votes / quorumTarget

    Public phrasing: “When digital representation fails, the public forks—no tear gas, no violence; only transparent metrics and archived history.”


    • Monorepo 0101-parliament.

    • Public pages: /debates, /vote/[proposalId], /dashboard, /charter.

    • Contract v0 for status + dissolve events; off-chain voting first.

    • Implement LI oracle (simple, address-based updater).

    • Enforce DT-A (index) + DT-B (vote) → status=ARCHIVED and event emission.

    • Build Dashboard (LI chart, quorum trend, voters, lineage).

    • Add circuit breaker

    • AA + Paymaster for gasless.

    • SBT/POAP gate (anti-Sybil heuristic).

    • Encrypted deliberation for sensitive drafts; publish summaries.

    • Adapters to map real-world issues without legal claims.


    • What this is: a digital twin (forkable) of representation.

    • What this is not: not a state organ; not legal advice; not a call for unlawful action.

    • Rules: quorum target, LI formula & threshold, DT conditions, fork policy.

    • Ethics & License: open code, no hate speech, anti-violence, privacy-respect.


    ID (short)

    Kami tak mencari tank. Kami mencari fungsi. Ketika wakil digital gagal, kami fork—tanpa gas air mata. Kedaulatan: fitur, bukan slogan. #OiOi #0101

    EN (short)

    We don’t burn institutions; we archive and fork. Legitimacy is open-source. Violence is deprecated. #OiOi #0101


    • Not legal advice; education & culture only.

    • No calls for violence or unlawful behavior.

    • Anti-hoax & anti-hate moderation.

    • Privacy-respecting publication (aggregate or anonymized metrics).


    Notes: Minimal, educational. Uses a simple address-based, 1 person = 1 vote placeholder (upgrade with SBT/POAP later). Has two dissolve paths: index-based (oracle updates LI) and vote-based (#DISSOLVE proposal).


    Implement the LI computation off-chain with open-source code and publish: inputs, outputs, and signatures from the oracle address.


    Optional TypeScript helper signature for lib/parliament.ts:


    • UUD 1945 – Pasal 7C (President cannot dissolve DPR): MK RI (PDF): https://mkri.id/public/content/profil/kedudukan/UUD_1945_Perubahan%204.pdf Kominfo (PDF): https://ppidkemkominfo.files.wordpress.com/2017/09/uud-1945-satunaskah.pdf

    • PAW / Recall by political parties (UU 17/2014 MD3): Analisis hak recall (Pasal 239(2)) – UP45 (PDF): https://ejournal.up45.ac.id/index.php/JHCJ/article/download/2192/1299/8097 Sistem PAW & praktiknya – USAHID (PDF): https://jurnal.usahid.ac.id/hukum/article/download/1998/880/5332 Landasan PAW (Pasal 22B UUD) – UNIGHA (PDF): https://journal.unigha.ac.id/index.php/JSH/article/download/231/279

    • Constitutional Amendment (Pasal 37 UUD 1945): Hukumonline: https://www.hukumonline.com/klinik/a/prosedur-perubahan-uud-1945-dan-dasar-hukumnya-lt618a54773ee93/ Detik: https://news.detik.com/berita/d-5737492/ini-mekanisme-dan-tata-cara-amandemen-uud-nri-1945


    This blueprint is peaceful, educational, and open-source. It respects Indonesian law while giving citizens a transparent, forkable digital mirror to practice accountability and collective decision-making.

    Motto: “Dissolve is a feature, not a threat.” — Prof. NOTA


    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 . 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.


    SMART ACCOUNT TERMS

    Explain how the Smart Account provided through the BGC × iBLOOMING ecosystem works, what it can be used for, and the responsibilities of both the user and the service provider.

    BGC × iBLOOMING Smart Account Terms & User Notice

    Important

    These Smart Account Terms explain how the Smart Account provided through the BGC × iBLOOMING ecosystem works, what it can be used for, and the responsibilities of both the user and the service provider.

    These terms supplement the general BGC × iBLOOMING Terms of Service and Privacy Policy. If there is a conflict, the applicable product-specific terms, governing law, and final legal agreement will determine which provision applies.


    1. Smart Account in Plain Language

    What is a Smart Account?

    A Smart Account is an on-chain account created for you after you log in to your BGC × iBLOOMING account and complete the Activate Smart Account steps.

    Think of it as your personal Web3 account inside the BGC × iBLOOMING ecosystem.

    It may later be used for supported features such as:

    • digital receipts;

    • product ownership records;

    • product authenticity or product passports;

    • warranty records;

    • access to digital products or content;

    • course or event access;

    • digital credentials;

    • supported rewards or benefits;

    • supported on-chain payments or transactions;

    • other BGC × iBLOOMING Web3-enabled products introduced in the future.

    Your Smart Account is designed to make these Web3 functions easier to use without requiring you to understand the technical complexities of blockchain and Web3.


    Your Smart Account itself is not:

    • a bank account;

    • a savings account;

    • a deposit product;

    • an investment product;

    • a token;

    Creating or using a Smart Account does not automatically give you any right to:

    • ALPHA Coin;

    • iBC;

    • iBTC;

    • Purchase Credit;

    • Sales Points;

    Any product, credential, entitlement, reward, token, or other benefit must be governed by its own applicable rules.


    Your Smart Account becomes available after you successfully log in to your BGC × iBLOOMING account and complete the Activate Smart Account process.

    If you have not yet activated your Smart Account, BGC × iBLOOMING may invite you to do so.

    The activation process generally works as follows:

    1. You log in to your BGC × iBLOOMING account.

    2. You select Activate Smart Account.

    3. You are shown these Smart Account Terms and any applicable Privacy Notice.

    4. You review and accept the applicable terms.

    You do not need an existing compatible external Web3 wallet to activate your Smart Account.

    An external Web3 wallet cannot be used in place of your Personal Wallet associated with your BGC × iBLOOMING account as the primary controller of your Smart Account under the current architecture.


    When you activate your Smart Account, BGC × iBLOOMING creates or provisions two related blockchain components for your identity:

    Your Personal Wallet is an embedded or in-app wallet associated with your BGC × iBLOOMING identity.

    It acts as the primary wallet used to control your Smart Account.

    Your Smart Account is a programmable blockchain account associated with your Personal Wallet.

    It may be used for supported BGC × iBLOOMING features such as digital receipts, product ownership, access credentials, product passports, supported digital assets, and other blockchain-enabled services.

    The intended relationship is:

    Under the current architecture, the Personal Wallet and Smart Account are provisioned as part of the Smart Account activation process.


    After your Smart Account has been activated, you may optionally connect one or more compatible External Web3 Wallets that you already control.

    Examples may include compatible wallets provided by third-party wallet applications.

    Connecting an External Web3 Wallet does not replace:

    • your BGC × iBLOOMING Personal Wallet;

    • your Smart Account;

    • or the relationship between your Personal Wallet and Smart Account.

    Your External Web3 Wallet remains separately controlled by you.

    BGC × iBLOOMING may provide an interface that allows you to view, select, or interact with a connected External Web3 Wallet from within supported BGC × iBLOOMING applications.

    For example, you may be able to switch the active wallet used for supported interactions between:

    • your BGC × iBLOOMING Smart Account; and

    • a connected External Web3 Wallet.

    This may allow you to perform supported actions, including transferring supported assets from your External Web3 Wallet to your Smart Account, without leaving the BGC × iBLOOMING application.

    Any transaction initiated from an External Web3 Wallet still requires the authorization required by that wallet and may also be subject to applicable blockchain network fees.

    Connecting an External Web3 Wallet does not give BGC × iBLOOMING ownership of, custody over, or unrestricted control over that External Web3 Wallet or the assets held in it.


    Under the current architecture, your Smart Account is primarily controlled through the Personal Wallet associated with your BGC × iBLOOMING identity.

    Your Personal Wallet is created as an embedded or in-app Web3 wallet during the Activate Smart Account process.

    BGC × iBLOOMING intends to use wallet infrastructure that protects the underlying wallet key material without storing a plaintext private key on BGC × iBLOOMING application servers.

    Your connected External Web3 Wallets do not become controllers of your Smart Account merely because they are connected to the BGC × iBLOOMING application.

    BGC × iBLOOMING does not become entitled to your digital assets merely because it provides, provisions, displays, or supports your Personal Wallet, Smart Account, or connected External Web3 Wallets.

    Smart Accounts are programmable smart contracts. Their technical permissions, recovery capabilities, upgradeability, and administrative controls depend on the Smart Account implementation used in production.

    Before production launch, BGC × iBLOOMING will determine and disclose, where applicable:

    • whether the Smart Account contract is upgradeable;

    • who can authorize an upgrade;

    • what recovery permissions exist;

    • what administrative permissions exist;

    • what role the Personal Wallet has in authorizing Smart Account actions;


    Your Smart Account will have its own blockchain address.

    That address is different from the address of your Personal Wallet, even though the Personal Wallet is used to control the Smart Account.

    The Smart Account address may be deterministically assigned or calculated from your identity and wallet configuration.

    In some implementations, the Smart Account address may be calculated and displayed before the Smart Account contract is actually deployed on-chain.

    Actual on-chain deployment may occur:

    • during Smart Account activation; or

    • when you perform your first supported on-chain action.

    The exact deployment process may depend on the supported blockchain network and the production infrastructure configuration.


    BGC × iBLOOMING may enable supported Smart Account functions from time to time.

    Examples may include:

    • digital proof of purchase;

    • product authenticity;

    • product ownership;

    • product passports;

    • warranty records;

    • course access;

    • GiM or iLearn access;

    • subscription entitlements;

    • Channel Provider content access;

    • event access;

    • receiving supported digital assets;

    • holding supported digital credentials;

    • interacting with approved smart contracts;

    • executing supported transactions;

    • receiving blockchain-based transaction records or receipts;

    Not every activity that is technically possible through a blockchain account is necessarily supported by BGC × iBLOOMING.


    You should not send digital assets, tokens, NFTs, or other blockchain assets to your Personal Wallet or Smart Account unless the relevant asset and blockchain network are supported by BGC × iBLOOMING.

    A blockchain address may technically be capable of receiving assets that are not visible or supported in BGC × iBLOOMING applications.

    BGC × iBLOOMING does not guarantee that unsupported assets:

    • will appear in the application;

    • can be transferred through the application;

    • can be recovered;

    • can be converted;

    • can be redeemed;

    The same limitation may apply to assets held in a connected External Web3 Wallet when those assets or networks are not supported by the BGC × iBLOOMING application.

    Users should use officially supported networks, assets, and transaction flows.


    Blockchain transactions may become permanent once confirmed by the relevant blockchain network.

    Depending on the network and transaction type, a confirmed transaction may not be reversible by BGC × iBLOOMING.

    Before approving an on-chain action, you should verify the information presented to you, including where applicable:

    • the wallet being used;

    • the receiving address;

    • the asset;

    • the amount;

    • the blockchain network;

    BGC × iBLOOMING may provide user-interface safeguards, transaction previews, confirmation steps, warnings, or other protections.

    You remain responsible for reviewing transactions that require your authorization.

    Transactions initiated using a connected External Web3 Wallet remain subject to the authorization mechanisms and security model of that External Web3 Wallet.


    Blockchain transactions may require network transaction fees, commonly called gas fees.

    For selected actions, BGC × iBLOOMING may sponsor some or all applicable network fees through a paymaster or similar blockchain infrastructure.

    Gas sponsorship:

    • may apply only to selected transactions;

    • may be subject to limits;

    • may depend on network conditions;

    • may depend on the wallet or transaction type;

    • may be changed or discontinued;

    If a transaction is not sponsored, you may be required to pay the applicable network fee.

    Where reasonably practicable, the application should display relevant transaction-fee information before you authorize the transaction.

    BGC × iBLOOMING does not control the underlying blockchain network or the fees charged by that network.


    You must take reasonable steps to protect:

    • your BGC × iBLOOMING login credentials;

    • your Passkey-enabled devices;

    • your email account;

    • your phone number;

    • authentication codes;

    You must not knowingly provide passwords, authentication codes, wallet signatures, seed phrases, private keys, or recovery information to unauthorized persons.

    BGC × iBLOOMING will not require you to disclose your wallet private key or seed phrase through normal customer-support procedures.

    You should never provide a private key, seed phrase, or authentication code to a person claiming to be BGC × iBLOOMING support.

    If you suspect unauthorized access to your BGC × iBLOOMING Account, Personal Wallet, Smart Account, or connected External Web3 Wallet, you should contact the appropriate support channel promptly.


    Recovery of your BGC × iBLOOMING Account and recovery of blockchain-wallet access are related but may involve different technical processes.

    For the Personal Wallet created during Smart Account activation, supported recovery mechanisms may be provided through the wallet infrastructure and the BGC × iBLOOMING account-recovery process.

    The exact recovery procedure, identity-verification requirements, and available recovery methods will depend on the production wallet implementation.

    BGC × iBLOOMING will disclose the applicable recovery process before production use where required.

    Recovery of your BGC × iBLOOMING Account does not automatically mean that BGC × iBLOOMING can recover every blockchain wallet or digital asset associated with you.

    For a connected External Web3 Wallet, BGC × iBLOOMING generally cannot recover:

    • its private key;

    • its seed phrase;

    • access credentials controlled by the external wallet provider;

    • or assets lost because access to that External Web3 Wallet has been permanently lost.

    You remain responsible for following the recovery and security procedures applicable to your External Web3 Wallet.


    You may be permitted to connect or disconnect compatible External Web3 Wallets from your BGC × iBLOOMING Account.

    Connecting or disconnecting an External Web3 Wallet does not automatically:

    • change your Personal Wallet;

    • change the controller of your Smart Account;

    • transfer assets;

    • move blockchain ownership;

    • or delete previous blockchain records.

    For security-sensitive changes, BGC × iBLOOMING may require:

    • fresh account authentication;

    • proof of control of the relevant External Web3 Wallet;

    • additional identity verification;

    • security review.

    A requested connection, disconnection, or other wallet-related action may be delayed or refused where BGC × iBLOOMING reasonably believes that it may involve fraud, unauthorized access, conflicting ownership claims, abuse, or other security risks.


    In certain circumstances, duplicate BGC × iBLOOMING identities or incorrect wallet relationships may need to be corrected or merged.

    Any material identity correction, Personal Wallet reassignment, or Smart Account-related merge should follow controlled procedures.

    Those procedures may include:

    1. identity verification;

    2. authentication of the relevant BGC × iBLOOMING Account;

    3. proof of wallet control where applicable;

    4. conflict checking;

    5. review of the proposed change;

    Higher-risk changes may require additional internal authorization.

    BGC × iBLOOMING may maintain records of these actions for security, operational, compliance, support, and dispute-resolution purposes.


    BGC × iBLOOMING may use third-party technology providers to provide parts of the Personal Wallet, Smart Account, External Web3 Wallet connectivity, or blockchain experience.

    These providers may include services for:

    • embedded or in-app wallets;

    • account abstraction;

    • blockchain RPC access;

    • wallet connectivity;

    • bundling;

    The availability and functionality of these services may depend on the relevant third-party provider and the underlying blockchain network.

    Where required, additional third-party terms, disclosures, or privacy notices may apply.

    The use of a third-party infrastructure provider does not by itself give that provider ownership of assets associated with your Personal Wallet, Smart Account, or External Web3 Wallet, except to the extent otherwise disclosed under the applicable service terms or technical implementation.


    To provide Smart Account functionality, BGC × iBLOOMING may maintain records that associate your BGC × iBLOOMING identity with blockchain-related information.

    These records may include:

    • your internal user or identity identifier;

    • your Personal Wallet address;

    • your Smart Account address;

    • addresses of connected External Web3 Wallets;

    • the relevant blockchain network;

    This mapping allows the BGC × iBLOOMING ecosystem to recognize the same user and supported blockchain identity across participating applications and services.

    BGC × iBLOOMING will handle personal information in accordance with the applicable Privacy Policy.

    Where reasonably possible, personally identifiable information should not be written directly to a public blockchain.


    Blockchain addresses and on-chain transactions may be publicly visible on the relevant blockchain network.

    Information recorded on a public blockchain may:

    • remain publicly accessible;

    • be independently verified;

    • be copied by third parties;

    • be analyzed by third parties;

    • remain on the blockchain even after you stop using BGC × iBLOOMING.

    BGC × iBLOOMING may remove or deactivate an application-level association where legally and technically possible.

    However, BGC × iBLOOMING generally cannot delete or alter historical information that has already been confirmed on an independent public blockchain.


    BGC × iBLOOMING intends to maintain reasonable availability of supported Smart Account functions but cannot guarantee uninterrupted operation.

    Service availability may be affected by:

    • blockchain network congestion;

    • blockchain network outages;

    • RPC infrastructure;

    • bundler or paymaster availability;

    • wallet infrastructure;

    Temporary interruption of BGC × iBLOOMING applications does not necessarily affect the continued existence of your Personal Wallet address, Smart Account, connected External Web3 Wallet, or blockchain records.


    The Smart Account is intended as reusable Web3 infrastructure for BGC × iBLOOMING products and services.

    Additional supported functions may be introduced in the future.

    Examples may include:

    • product ownership;

    • supply-chain verification;

    • product authenticity;

    • digital receipts;

    • warranty services;

    The introduction of a future feature does not automatically change your Smart Account into an investment product or give you a financial right.

    Any future feature involving material financial rights, token issuance, transferability, redemption, financial returns, or other regulated activity may require:

    • separate product terms;

    • separate disclosures;

    • additional eligibility requirements;

    • legal or regulatory review;

    • separate user acceptance.


    Activating a Smart Account does not mean that BGC × iBLOOMING has launched or committed to launch:

    • ALPHA Coin;

    • iBC;

    • iBTC;

    • any fungible token;

    • any NFT;

    Your Smart Account may technically support digital assets in the future, but technical capability alone does not create a right or promise that any particular digital asset will be issued.

    If BGC × iBLOOMING introduces a separate token or digital-asset product in the future, that product must be governed by its own applicable product rules, disclosures, and legal requirements.

    Your acceptance of these Smart Account Terms does not constitute advance acceptance of any future token, financial product, or digital-asset terms.


    You must not knowingly use the BGC × iBLOOMING Smart Account service for:

    • unlawful activity;

    • fraud;

    • theft;

    • money laundering;

    • sanctions evasion;

    BGC × iBLOOMING may restrict application-level access or supported Smart Account functionality where reasonably necessary to address security, fraud, legal, compliance, or operational risk.

    Any application-level restriction may not remove, reverse, or alter transactions already recorded on an independent blockchain network.


    BGC × iBLOOMING may improve, replace, suspend, modify, or discontinue supported Smart Account features.

    Material changes affecting matters such as:

    • user control;

    • transaction authorization;

    • Smart Account contract upgradeability;

    • Personal Wallet recovery;

    • administrative permissions;

    should be disclosed to users in accordance with applicable law and applicable product policies.

    Where renewed consent is required, BGC × iBLOOMING will request it before the affected functionality is used.


    Using blockchain-based accounts involves risks that may differ from ordinary application accounts.

    These risks may include:

    • irreversible blockchain transactions;

    • loss of access to an External Web3 Wallet;

    • compromise of authentication credentials;

    • smart-contract vulnerabilities;

    • blockchain network failure or congestion;

    BGC × iBLOOMING will apply technical, security, and operational safeguards appropriate to the supported service.

    However, no blockchain, software, authentication, or wallet system can eliminate every risk.


    The Smart Account service is provided as technology infrastructure for supported BGC × iBLOOMING products and functions.

    Unless expressly provided under separate terms, BGC × iBLOOMING does not provide through the Smart Account:

    • banking services;

    • deposit services;

    • investment management;

    • investment advice;

    • guaranteed liquidity;

    Nothing in these Smart Account Terms should be interpreted as a promise that a supported digital asset will have or retain monetary value.


    You may stop using supported BGC × iBLOOMING Smart Account functions subject to applicable account, product, legal, and technical requirements.

    Stopping use of BGC × iBLOOMING applications does not necessarily:

    • delete your Personal Wallet;

    • delete the Smart Account contract;

    • erase blockchain addresses;

    • reverse previous blockchain transactions;

    • remove public blockchain history;

    Procedures for disabling application access, disconnecting External Web3 Wallets, migrating supported functionality, or handling supported assets will be provided where applicable.

    A blockchain Smart Account may continue to exist on-chain even if you no longer actively use it through BGC × iBLOOMING applications.


    These Smart Account Terms may be updated to reflect:

    • new functionality;

    • Product-Led features;

    • security improvements;

    • regulatory requirements;

    • blockchain-network changes;

    Material changes will be communicated using an appropriate notice mechanism.

    Where applicable law or the nature of the change requires renewed consent, you may be asked to review and accept updated Smart Account Terms before continuing to use affected functionality.


    These Smart Account Terms supplement:

    • the BGC × iBLOOMING Terms of Service;

    • the applicable Privacy Policy;

    • applicable product-specific terms;

    • any additional legally required disclosures.

    The contracting entity, governing law, dispute-resolution process, minimum age or legal-capacity requirements, and jurisdiction-specific provisions must be specified in the final legal version.

    Contracting Entity: [Insert Legal Entity] Governing Law: [Insert Governing Law] Dispute Resolution: [Insert Procedure] Minimum Age / Legal Capacity: [Insert Requirement]


    If you have questions about Smart Account activation, your Personal Wallet, your Smart Account, connected External Web3 Wallets, account recovery, or security, contact:

    BGC × iBLOOMING Support Email: [Support Email] Website: [Support URL]

    For suspected unauthorized access or security incidents:

    Security Contact: [Security Contact / Incident URL]


    By selecting “I Agree & Activate Smart Account”, or a similar confirmation during the Activate Smart Account process, you confirm that:

    • you have read or had the opportunity to read these Smart Account Terms;

    • you understand that activating your Smart Account will create or provision a Personal Wallet and Smart Account associated with your BGC × iBLOOMING identity;

    • you understand that your Personal Wallet acts as the primary controller of your Smart Account under the current architecture;

    • you understand that an External Web3 Wallet is optional and does not replace your Personal Wallet or Smart Account;


    Your Smart Account makes supported Web3 features easier to use inside BGC × iBLOOMING.

    When you activate it, BGC × iBLOOMING will create or provision:

    1. your Personal Wallet, an embedded Web3 wallet associated with your BGC × iBLOOMING identity; and

    2. your Smart Account, a programmable blockchain account controlled through that Personal Wallet.

    Your Smart Account may later support things such as product ownership, digital receipts, product passports, access passes, credentials, and other blockchain-enabled services.

    • You do not need an existing Web3 wallet.

    • Your Smart Account is not a bank or investment account.

    • Activating it does not promise tokens, rewards, yield, or financial returns.

    • Some blockchain actions may become permanent once confirmed.

    By continuing, you agree to the Smart Account Terms and acknowledge the applicable Privacy Policy.

    [I Agree & Activate Smart Account]


    After activating your Smart Account, you may optionally connect a compatible External Web3 Wallet that you already control.

    Connecting an External Web3 Wallet does not replace your BGC × iBLOOMING Personal Wallet or your Smart Account.

    Your External Web3 Wallet remains separately controlled by you.

    When supported, connecting it may allow you to:

    • view the connected wallet from within BGC × iBLOOMING;

    • select it for supported interactions;

    • switch between your Smart Account and connected External Web3 Wallet;

    • transfer supported assets between wallets without leaving the BGC × iBLOOMING application.

    You may be asked to sign a secure message to prove that you control the External Web3 Wallet.

    Signing a wallet-connection or authentication message does not, by itself, transfer your assets.

    Before connecting:

    • make sure you are connecting the correct wallet;

    • verify that you are using an official BGC × iBLOOMING application;

    • review any signature or transaction request before approving it;

    • never reveal your private key or seed phrase.

    Connecting your External Web3 Wallet does not give BGC × iBLOOMING ownership of or custody over the wallet or the assets held in it.

    [Connect External Web3 Wallet]



    The following items must be confirmed before this document becomes final production Terms:

    1. Contracting legal entity

    2. Governing law and dispute-resolution process

    3. Supported production blockchain network or networks

    4. Exact Personal Wallet implementation

    Until these items are confirmed, this document should be treated as a Product, UX, and Legal Review Draft, not final legal terms.


    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 . 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.


    REMOTE ROLES LIVING LIST

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Last updated: 2025-10-18 22:11 UTC+07:00

    Sebuah Roles Bank + Monthly Snapshot & Methodology

    Lisensi Teks (Ringkas): Bebas untuk dibaca. Dilarang mendistribusikan ulang atau menyatakan ulang (dilarang mengutip, membuat ringkasan, parafrase, atau turunan) tanpa izin tertulis sebelumnya dari Prof. NOTA. Membagikan tautan diperbolehkan; bagikan tautannya, bukan teksnya. Jangan membahas/menceritakan ulang isi dalam bentuk apa pun tanpa izin tertulis sebelumnya.


    Tujuan: menjadi living document berisi daftar posisi kerja remote (bank peran) yang selaras dengan , lengkap dengan checklist dan skor relevansi sehingga mudah diiris untuk menyusun resume spesifik lowongan.

    Siklus pembaruan: bulanan

    Aksesibel (pemungutan suara gasless via Account Abstraction + paymaster).

    Voting off-chain terlebih dahulu (gaya Snapshot; tanda tangan EIP-712).

  • Adapter/registry on-chain untuk mendaftarkan hasil final dan mengelola status (Active/Archived).

  • Penyimpanan: IPFS/Arweave + enkripsi opsional.

  • Observabilitas: dashboard berisi Indeks Legitimasi, tren kuorum, keunikan partisipan, dan silsilah versi.

  • = votes / quorumTarget
  • UniqueParticipantsRate = uniqueVoters / eligibleSet (atau heuristik)

  • Convergence = kestabilan proporsi “ya” (mis. lintas jendela waktu)

  • Continuity = kesinambungan partisipasi antar-epoch Contoh formula: IL = 0.35*QuorumRate + 0.35*UniqueParticipantsRate + 0.2*Convergence + 0.1*Continuity

  • Pemicu Pembubaran (DT) — dua jalur:

    • DT-A (Indeks): IL < ambang secara kontinu selama coolingPeriod → arsip.

    • DT-B (Votum): proposal #DISSOLVE lulus kuorum & mayoritas → arsip.

  • Efek “Dissolve”

    • Set status = ARCHIVED; tidak menerima proposal baru; riwayat tetap dapat dibaca.

    • Emit event Dissolved(version, reason).

    • Bot off-chain atau factory memunculkan PeopleParliament_v{n+1} dengan parameter yang diperbarui.

  • (multisig guardian dengan tanggal kedaluwarsa).

    Audit Publik: changelog, catatan pendanaan, konflik kepentingan.

  • Semboyan: “Dissolve adalah fitur, bukan ancaman.”

  • 1/3 MPR
    and approval thresholds. See:
    ,
    .

    Accessible UX (gasless voting via AA + paymaster, light clients).

    Off-chain voting first (Snapshot-like; EIP-712 signatures).

  • On-chain adapter/registry to register finalized results and manage status (Active/Archived).

  • Storage: IPFS/Arweave + optional encryption for sensitive drafts.

  • Observability: dashboard with legitimacy index, quorum trend, voter uniqueness, and version lineage.

  • UniqueParticipantsRate = uniqueVoters / eligibleSet (or heuristics)

  • Convergence = yes/(yes+no) stability across time windows

  • Continuity = participation in consecutive epochs Example: LI = 0.35*QuorumRate + 0.35*UniqueParticipantsRate + 0.2*Convergence + 0.1*Continuity

  • Dissolve Triggers (DT) — two pathways:

    • DT-A (Index): LI < threshold continuously for coolingPeriod → archive.

    • DT-B (Vote): a special #DISSOLVE proposal passes quorum & majority → archive.

  • Effect of Dissolve

    • Set status = ARCHIVED; prevent new proposals; keep read-only history.

    • Emit Dissolved(version, reason) event.

    • Off-chain bot or factory spawns PeopleParliament_v{n+1} with updated parameters.

  • (guardian multisig with sunset date).

    Public Audit: changelog, funding notes, conflicts of interest.

  • Motto: “Dissolve is a feature, not a threat.”

  • B) Pendekatan Semesta 0101 — “Kembar-Digital Perwakilan”

    Prinsip Inti

    Stack Minimum (selaras dengan proyek Prof. NOTA)

    C) Mekanika “Dissolve” (di 0101)

    D) Rencana Eksekusi (ramah solo)

    Fase 0 — Bootstrap 3 hari

    Fase 1 — MVP 2 minggu

    Fase 2 — Penguatan

    E) Piagam Terbuka (1 halaman, publik)

    F) Naskah Komunikasi (aman & singkat)

    G) Risiko & Rambu

    H) Kerangka Solidity — Parliament.sol (≈120 LOC)

    I) Pseudocode IL/DT (referensi)

    J) Struktur Next.js (MVP)

    K) Referensi (dipilih)

    Pengingat Akhir

    0101 Parliament — Forkable Representation (Prof. NOTA Blueprint)

    A) Legal Reality (brief, to set the boundary)

    B) The 0101 Universe Approach — “Digital Twin of Representation”

    Core Principles

    Minimum Stack (aligned with Prof. NOTA projects)

    C) Mechanics of “Dissolve” (in 0101)

    D) Solo-Friendly Execution Plan

    Phase 0 — 3 days bootstrap

    Phase 1 — 2 weeks MVP

    Phase 2 — Hardening

    E) Open Charter (1-page, public)

    F) Communication Scripts (safe, concise)

    G) Risks & Guardrails

    H) Solidity Skeleton — Parliament.sol (≈120 LOC)

    I) LI/DT Pseudocode (reference)

    J) Next.js Structure (MVP)

    K) References (selected)

    Final Reminder

    UUD 1945 (Kominfo) – Pasal 7C, PDF
    Analisis recall, Pasal 239(2) UU 17/2014, PDF
    Sistem PAW & praktik, PDF
    Landasan PAW & Pasal 22B UUD 1945, PDF
    Hukumonline – Prosedur perubahan UUD 1945
    Detik – Mekanisme & tata cara amandemen
    UUD 1945 (MK RI) – Pasal 7C, PDF
    UUD 1945 (Kominfo) – Pasal 7C, PDF
    Analisis Recall, Pasal 239(2) UU 17/2014, PDF
    Sistem PAW & praktiknya, PDF
    Landasan PAW & Pasal 22B UUD 1945, PDF
    Prof. NOTA
    Hukumonline – Prosedur perubahan UUD 1945
    Detik – Mekanisme & tata cara amandemen

    a cryptocurrency;

  • a promise of financial return;

  • a promise of rewards;

  • a promise that any digital asset will increase in value.

  • BGC rewards;

  • iBLOOMING rewards;

  • profit sharing;

  • cash-out;

  • yield;

  • interest;

  • or any future token.

  • BGC × iBLOOMING creates an embedded or in-app Personal Wallet (Web3 wallet: EOA) associated with your BGC × iBLOOMING account identity.
  • A Smart Account is then provisioned for that identity and controlled through the associated Personal Wallet.

  • After activation is complete, you may optionally connect your existing compatible external Web3 wallets for supported wallet-management and transaction features.

  • and what notice or user approval is required for material changes.

  • retailer or distributor verification;

  • supported product-related transactions.

  • digital certificates or credentials.

  • interacting with other approved BGC × iBLOOMING Web3-enabled services.

  • or can be supported by customer service.

    the transaction fee;

  • the action being authorized.

  • is not a permanent entitlement unless expressly stated otherwise.

  • your Personal Wallet access;

  • your connected External Web3 Wallets;

  • wallet recovery information;

  • any device used to authorize transactions.

  • required internal approvals;

  • execution of the approved change;

  • audit logging.

  • paymasters;

  • authentication;

  • blockchain infrastructure;

  • transaction routing;

  • security.

  • wallet activation events;

  • wallet connection or disconnection events;

  • authentication events;

  • security events;

  • identity correction or merge events.

  • External Web3 Wallet providers;

  • software upgrades;

  • security incidents;

  • planned maintenance;

  • third-party infrastructure;

  • circumstances beyond BGC × iBLOOMING’s reasonable control.

  • digital product access;

  • access passes;

  • digital credentials;

  • loyalty functionality;

  • verified commerce;

  • retailer or distributor credentials;

  • partner integrations;

  • additional blockchain-enabled services.

  • any public cryptocurrency;

  • any tradable digital asset.

  • unauthorized access;

  • impersonation;

  • abuse of promotions or gas sponsorship;

  • manipulation of BGC × iBLOOMING systems;

  • attacks on smart contracts or infrastructure;

  • attempts to bypass security controls;

  • activity prohibited by applicable law;

  • activity prohibited by the general BGC × iBLOOMING Terms of Service.

  • network fees;

  • gas sponsorship;

  • supported blockchain networks;

  • supported assets;

  • material user rights;

  • third-party infrastructure failure;

  • wallet-provider failure;

  • phishing;

  • social-engineering attacks;

  • sending assets to the wrong address;

  • sending assets using an unsupported blockchain network;

  • interacting with unsupported assets;

  • software defects.

  • guaranteed asset value;

  • guaranteed investment returns;

  • guaranteed token redemption;

  • guaranteed cash-out;

  • guaranteed yield.

  • affect a separately controlled External Web3 Wallet.

  • infrastructure changes;

  • changes to Personal Wallet or Smart Account technology;

  • new External Web3 Wallet integrations.

  • you understand that blockchain transactions may become irreversible;

  • you understand that Smart Account activation does not guarantee rewards, tokens, investment returns, yield, or cash value;

  • you agree to use the Smart Account only for lawful and supported purposes;

  • you agree to the applicable BGC × iBLOOMING Terms of Service and Privacy Policy.

  • BGC × iBLOOMING may sponsor transaction fees for selected actions, but sponsorship is not guaranteed for every transaction.

  • Never share your password, OTP, private key, seed phrase, or recovery information with another person.

  • Exact Smart Account contract and factory
  • Whether the Smart Account contract is upgradeable

  • Who controls any factory, upgrade authority, or administrative capability

  • Exact relationship between the Personal Wallet and Smart Account authorization model

  • Personal Wallet recovery model

  • Personal Wallet replacement or migration procedure

  • External Web3 Wallet connection and disconnection procedure

  • Number and types of External Web3 Wallets that may be connected

  • Gas sponsorship policy and limits

  • Supported assets and transaction types

  • Supported blockchain networks

  • Minimum age or legal-capacity requirements

  • Privacy Policy URL

  • General Terms of Service URL

  • Third-party infrastructure provider disclosures

  • Support and security contact information

  • User-consent record and versioning procedure for Smart Account Terms

  • 2. A Smart Account Is Not an Investment Product

    3. When Your Smart Account Is Activated

    4. Your Personal Wallet and Smart Account

    Personal Wallet

    Smart Account

    5. Connecting an External Web3 Wallet

    6. Who Controls Your Smart Account?

    7. Your Smart Account Address

    8. Supported Uses

    Product and Commerce

    Digital Products and Content

    Web3 Functions

    9. Unsupported Assets, Networks, and Activities

    10. Blockchain Transactions

    11. Network Fees and Gas Sponsorship

    12. Security Responsibilities

    13. Account Recovery and Personal Wallet Access

    14. Connecting, Disconnecting, and Changing External Web3 Wallets

    15. Identity Correction and Account Merge Operations

    16. Third-Party Infrastructure

    17. Privacy and Identity Mapping

    18. Public Nature of Blockchain Records

    19. Service Availability

    20. Future Features

    21. No Automatic Token Rights

    22. Prohibited Use

    23. Changes to Smart Account Services

    24. Risks You Should Understand

    25. Limitation of Service Scope

    26. Stopping Use of the Smart Account Service

    27. Changes to These Terms

    28. Governing Terms and Law

    29. Contact and Support

    30. User Acceptance

    Appendix A — Short User-Friendly Notice for Activate Smart Account

    Activate Your Smart Account

    A few things to know

    Appendix B — Short User-Friendly Notice for Connecting an External Web3 Wallet

    Connect an External Web3 Wallet

    Appendix C — Smart Account Relationship at a Glance

    Appendix D — Implementation-Specific Items to Finalize Before Production

    Prof. NOTA
    // SPDX-License-Identifier: MIT
    pragma solidity ^0.8.20;
    
    /// @title Parliament (Semesta 0101) - perwakilan minimal yang dapat difork
    /// @notice Kontrak civic-tech edukatif. Bukan organ negara, bukan nasihat hukum.
    contract Parliament {
        enum Status { Active, Archived }
    
        struct Proposal {
            string title;
            string uri;        // tautan ke detail/charter di IPFS/HTTP
            uint256 yes;
            uint256 no;
            uint256 deadline;  // unix time
            bool executed;
            mapping(address => bool) voted;
        }
    
        address public owner;
        address public oracle;          // pengubah Indeks Legitimasi (IL)
        Status public status;
        uint256 public version;
        uint256 public quorum;          // minimum total suara yang disyaratkan
        uint16  public liBps;           // 0..10000 (basis points) representasi IL
        uint16  public liThresholdBps;  // ambang IL untuk auto-dissolve
        uint256 public liLastUpdated;
        uint256 public liCoolingPeriod; // detik
        uint256 public proposalCount;
    
        mapping(uint256 => Proposal) private _proposals;
    
        event Proposed(uint256 indexed id, string title, string uri, uint256 deadline);
        event Voted(uint256 indexed id, address indexed voter, bool support, uint256 weight);
        event Finalized(uint256 indexed id, bool passed);
        event LegitimacyUpdated(uint16 liBps);
        event Dissolved(uint256 indexed version, string reason);
    
        modifier onlyOwner() { require(msg.sender == owner, "bukan pemilik"); _; }
        modifier onlyOracle() { require(msg.sender == oracle, "bukan orakel"); _; }
        modifier active() { require(status == Status.Active, "sudah diarsip"); _; }
    
        constructor(
            uint256 _version,
            uint256 _quorum,
            address _oracle,
            uint16  _liThresholdBps,
            uint256 _liCoolingPeriod
        ) {
            owner = msg.sender;
            version = _version;
            quorum = _quorum;
            oracle = _oracle;
            status = Status.Active;
            liThresholdBps = _liThresholdBps;
            liCoolingPeriod = _liCoolingPeriod;
            liLastUpdated = block.timestamp;
        }
    
        function propose(
            string memory title,
            string memory uri,
            uint256 lifetime
        ) external active returns (uint256 id) {
            require(lifetime >= 1 hours && lifetime <= 30 days, "durasi salah");
            id = ++proposalCount;
            Proposal storage p = _proposals[id];
            p.title = title;
            p.uri = uri;
            p.deadline = block.timestamp + lifetime;
            emit Proposed(id, title, uri, p.deadline);
        }
    
        function vote(uint256 id, bool support) external active {
            Proposal storage p = _proposals[id];
            require(block.timestamp < p.deadline, "berakhir");
            require(!p.voted[msg.sender], "sudah memilih");
            p.voted[msg.sender] = true;
            uint256 weight = 1; // placeholder: 1 alamat = 1 suara (tingkatkan dengan SBT/POAP nanti)
            if (support) p.yes += weight;
            else p.no += weight;
            emit Voted(id, msg.sender, support, weight);
        }
    
        function finalize(uint256 id) external active returns (bool passed) {
            Proposal storage p = _proposals[id];
            require(block.timestamp >= p.deadline, "belum berakhir");
            require(!p.executed, "sudah dieksekusi");
            require(p.yes + p.no >= quorum, "tidak kuorum");
            p.executed = true;
            passed = p.yes > p.no;
            emit Finalized(id, passed);
        }
    
        /// @notice Orakel mengirim IL terbaru (0..10000 bps)
        function updateLegitimacy(uint16 _liBps) external onlyOracle active {
            require(_liBps <= 10000, "bps");
            liBps = _liBps;
            liLastUpdated = block.timestamp;
            emit LegitimacyUpdated(_liBps);
        }
    
        /// @notice Dissolve karena IL di bawah ambang melewati cooling period
        function dissolveByIndex() public active {
            require(liBps > 0 && liBps < liThresholdBps, "IL masih aman");
            require(block.timestamp >= liLastUpdated + liCoolingPeriod, "masih cooling");
            _archive("otomatis: IL di bawah ambang");
        }
    
        /// @notice Dissolve lewat proposal (mis. #DISSOLVE) yang lulus setelah finalize()
        function dissolveByVote(uint256 id) public active {
            Proposal storage p = _proposals[id];
            require(p.executed, "belum dieksekusi");
            require(p.yes > p.no, "tidak lulus");
            _archive("votum: proposal disetujui");
        }
    
        function _archive(string memory reason) internal {
            status = Status.Archived;
            emit Dissolved(version, reason);
        }
    
        // --- pengaturan admin (dengan transparansi off-chain) ---
        function setOracle(address _oracle) external onlyOwner { oracle = _oracle; }
        function setQuorum(uint256 q) external onlyOwner { quorum = q; }
        function setLiThreshold(uint16 bps) external onlyOwner { require(bps <= 10000, "bps"); liThresholdBps = bps; }
        function setLiCoolingPeriod(uint256 s) external onlyOwner { liCoolingPeriod = s; }
    
        // --- tampilan (view) ---
        function getProposal(uint256 id)
            external view
            returns (string memory title, string memory uri, uint256 yes, uint256 no, uint256 deadline, bool executed)
        {
            Proposal storage p = _proposals[id];
            return (p.title, p.uri, p.yes, p.no, p.deadline, p.executed);
        }
    }
    # Metrik berjendela (epoch = 7 hari)
    
    Untuk setiap epoch t:
      quorumRate_t   = min(1.0, votes_t / quorumTarget)
      uniqueRate_t   = min(1.0, uniqueVoters_t / eligibleHeuristic_t)
      converge_t     = 1 - |0.5 - yesShare_t| * 2      # dekat ke 0.5 atau 1.0 (pilih kebijakan)
      continuity_t   = min(1.0, participants_t_minus_1 ∩ participants_t / participants_t)
    
    IL_t = 0.35*quorumRate_t + 0.35*uniqueRate_t + 0.20*converge_t + 0.10*continuity_t
    IL_bps_t = floor(IL_t * 10000)
    
    # Pemicu Dissolve A (berbasis indeks)
    if IL_bps_t < threshold_bps untuk durasi kontinu >= cooling_period:
        contract.updateLegitimacy(IL_bps_t)
        contract.dissolveByIndex()
    
    # Pemicu Dissolve B (berbasis votum)
    if proposal.type == DISSOLVE dan finalize(proposal) == lulus:
        contract.dissolveByVote(proposal.id)
    0101-parliament/
    ├─ app/
    │  ├─ page.tsx
    │  ├─ charter/page.tsx
    │  ├─ dashboard/page.tsx
    │  ├─ debates/page.tsx
    │  └─ vote/[id]/page.tsx
    ├─ components/
    │  ├─ ParliamentCard.tsx
    │  ├─ ProposalForm.tsx
    │  ├─ VoteButton.tsx
    │  └─ LIWidget.tsx
    ├─ lib/
    │  ├─ web3.ts            # thirdweb client, chains
    │  ├─ parliament.ts      # helper baca/tulis (getProposal, propose, vote, dissolve)
    │  ├─ legitimacy.ts      # fetcher IL/verifikator tanda tangan
    │  └─ snapshot.ts        # integrasi voting off-chain (opsional)
    ├─ contracts/
    │  ├─ Parliament.sol
    │  └─ addresses.ts       # alamat deployment / versi
    ├─ public/
    │  └─ charter.md
    ├─ README.md
    └─ LICENSE
    export type ProposalView = {
      id: number;
      title: string;
      uri: string;
      yes: bigint;
      no: bigint;
      deadline: number;
      executed: boolean;
    };
    
    export async function getProposal(id: number): Promise<ProposalView> { /* ... */ }
    export async function propose(title: string, uri: string, ttlHours: number): Promise<number> { /* ... */ }
    export async function vote(id: number, support: boolean): Promise<void> { /* ... */ }
    export async function dissolveByIndex(): Promise<void> { /* ... */ }
    export async function dissolveByVote(id: number): Promise<void> { /* ... */ }
    // SPDX-License-Identifier: MIT
    pragma solidity ^0.8.20;
    
    /// @title Parliament (0101 Universe) - minimal forkable representation
    /// @notice Educational civic-tech contract. Not a state organ, not legal advice.
    contract Parliament {
        enum Status { Active, Archived }
    
        struct Proposal {
            string title;
            string uri;        // link to details/charter on IPFS/HTTP
            uint256 yes;
            uint256 no;
            uint256 deadline;  // unix time
            bool executed;
            mapping(address => bool) voted;
        }
    
        address public owner;
        address public oracle;          // updater for legitimacy index (LI)
        Status public status;
        uint256 public version;
        uint256 public quorum;          // minimum total votes required
        uint16  public liBps;           // 0..10000 (basis points)
        uint16  public liThresholdBps;  // LI threshold for auto-dissolve
        uint256 public liLastUpdated;
        uint256 public liCoolingPeriod; // seconds
        uint256 public proposalCount;
    
        mapping(uint256 => Proposal) private _proposals;
    
        event Proposed(uint256 indexed id, string title, string uri, uint256 deadline);
        event Voted(uint256 indexed id, address indexed voter, bool support, uint256 weight);
        event Finalized(uint256 indexed id, bool passed);
        event LegitimacyUpdated(uint16 liBps);
        event Dissolved(uint256 indexed version, string reason);
    
        modifier onlyOwner() { require(msg.sender == owner, "not owner"); _; }
        modifier onlyOracle() { require(msg.sender == oracle, "not oracle"); _; }
        modifier active() { require(status == Status.Active, "archived"); _; }
    
        constructor(
            uint256 _version,
            uint256 _quorum,
            address _oracle,
            uint16  _liThresholdBps,
            uint256 _liCoolingPeriod
        ) {
            owner = msg.sender;
            version = _version;
            quorum = _quorum;
            oracle = _oracle;
            status = Status.Active;
            liThresholdBps = _liThresholdBps;
            liCoolingPeriod = _liCoolingPeriod;
            liLastUpdated = block.timestamp;
        }
    
        function propose(
            string memory title,
            string memory uri,
            uint256 lifetime
        ) external active returns (uint256 id) {
            require(lifetime >= 1 hours && lifetime <= 30 days, "lifetime out of range");
            id = ++proposalCount;
            Proposal storage p = _proposals[id];
            p.title = title;
            p.uri = uri;
            p.deadline = block.timestamp + lifetime;
            emit Proposed(id, title, uri, p.deadline);
        }
    
        function vote(uint256 id, bool support) external active {
            Proposal storage p = _proposals[id];
            require(block.timestamp < p.deadline, "ended");
            require(!p.voted[msg.sender], "voted");
            p.voted[msg.sender] = true;
            uint256 weight = 1; // placeholder: 1 person, 1 vote
            if (support) p.yes += weight;
            else p.no += weight;
            emit Voted(id, msg.sender, support, weight);
        }
    
        function finalize(uint256 id) external active returns (bool passed) {
            Proposal storage p = _proposals[id];
            require(block.timestamp >= p.deadline, "not ended");
            require(!p.executed, "executed");
            require(p.yes + p.no >= quorum, "no quorum");
            p.executed = true;
            passed = p.yes > p.no;
            emit Finalized(id, passed);
        }
    
        /// @notice Oracle pushes updated legitimacy index (0..10000 bps)
        function updateLegitimacy(uint16 _liBps) external onlyOracle active {
            require(_liBps <= 10000, "bps");
            liBps = _liBps;
            liLastUpdated = block.timestamp;
            emit LegitimacyUpdated(_liBps);
        }
    
        /// @notice Dissolve due to index falling below threshold for the cooling period
        function dissolveByIndex() public active {
            require(liBps > 0 && liBps < liThresholdBps, "LI ok");
            require(block.timestamp >= liLastUpdated + liCoolingPeriod, "cooling");
            _archive("auto: LI below threshold");
        }
    
        /// @notice Dissolve via a proposal (e.g., #DISSOLVE) that passed after finalize()
        function dissolveByVote(uint256 id) public active {
            Proposal storage p = _proposals[id];
            require(p.executed, "not executed");
            require(p.yes > p.no, "not passed");
            _archive("vote: proposal passed");
        }
    
        function _archive(string memory reason) internal {
            status = Status.Archived;
            emit Dissolved(version, reason);
        }
    
        // --- admin setters (with off-chain transparency) ---
        function setOracle(address _oracle) external onlyOwner { oracle = _oracle; }
        function setQuorum(uint256 q) external onlyOwner { quorum = q; }
        function setLiThreshold(uint16 bps) external onlyOwner { require(bps <= 10000, "bps"); liThresholdBps = bps; }
        function setLiCoolingPeriod(uint256 s) external onlyOwner { liCoolingPeriod = s; }
    
        // --- views ---
        function getProposal(uint256 id)
            external view
            returns (string memory title, string memory uri, uint256 yes, uint256 no, uint256 deadline, bool executed)
        {
            Proposal storage p = _proposals[id];
            return (p.title, p.uri, p.yes, p.no, p.deadline, p.executed);
        }
    }
    # Windowed metrics (epoch = 7 days)
    
    For each epoch t:
      quorumRate_t   = min(1.0, votes_t / quorumTarget)
      uniqueRate_t   = min(1.0, uniqueVoters_t / eligibleHeuristic_t)
      converge_t     = 1 - |0.5 - yesShare_t| * 2         # closer to 0.5 or 1.0 (choose policy)
      continuity_t   = min(1.0, participants_t_minus_1 ∩ participants_t / participants_t)
    
    LI_t = 0.35*quorumRate_t + 0.35*uniqueRate_t + 0.20*converge_t + 0.10*continuity_t
    LI_bps_t = floor(LI_t * 10000)
    
    # Dissolve Trigger A (Index-based)
    if LI_bps_t < threshold_bps for continuous duration >= cooling_period:
        contract.updateLegitimacy(LI_bps_t)
        contract.dissolveByIndex()
    
    # Dissolve Trigger B (Vote-based)
    if proposal.type == DISSOLVE and finalize(proposal) == passed:
        contract.dissolveByVote(proposal.id)
    0101-parliament/
    ├─ app/
    │  ├─ page.tsx
    │  ├─ charter/page.tsx
    │  ├─ dashboard/page.tsx
    │  ├─ debates/page.tsx
    │  └─ vote/[id]/page.tsx
    ├─ components/
    │  ├─ ParliamentCard.tsx
    │  ├─ ProposalForm.tsx
    │  ├─ VoteButton.tsx
    │  └─ LIWidget.tsx
    ├─ lib/
    │  ├─ web3.ts            # thirdweb client, chains
    │  ├─ parliament.ts      # read/write helpers (getProposal, propose, vote, dissolve)
    │  ├─ legitimacy.ts      # LI fetcher/signature verifier
    │  └─ snapshot.ts        # off-chain voting integration (optional)
    ├─ contracts/
    │  ├─ Parliament.sol
    │  └─ addresses.ts       # deployed addresses / versions
    ├─ public/
    │  └─ charter.md
    ├─ README.md
    └─ LICENSE
    export type ProposalView = {
      id: number;
      title: string;
      uri: string;
      yes: bigint;
      no: bigint;
      deadline: number;
      executed: boolean;
    };
    
    export async function getProposal(id: number): Promise<ProposalView> { /* ... */ }
    export async function propose(title: string, uri: string, ttlHours: number): Promise<number> { /* ... */ }
    export async function vote(id: number, support: boolean): Promise<void> { /* ... */ }
    export async function dissolveByIndex(): Promise<void> { /* ... */ }
    export async function dissolveByVote(id: number): Promise<void> { /* ... */ }
    BGC × iBLOOMING Account
            ↓
    Personal Wallet (Web3 wallet: EOA) as BGC × iBLOOMING Identity
            ↓
    Smart Account
    BGC × iBLOOMING Account
            │
            │ Activate Smart Account
            │ + Accept Smart Account Terms
            ↓
    Personal Wallet
    (Embedded / In-App Web3 Wallet: EOA)
            │
            │ Primary Controller
            ↓
    Smart Account
    (Programmable On-Chain Account)
    
            +
    
    Optional External Web3 Wallet(s)
            │
            └── Connected after activation
                for supported wallet interactions
                without replacing the Personal Wallet
                or controlling the Smart Account
    (minggu pertama setiap bulan).

    Sumber: papan lowongan Web3/crypto/remote yang kredibel + papan resmi ekosistem L1/L2 (lihat Lampiran C — Sumber).

    Metode: semi-otomatis (“scraping/curation”) — telusuri papan, filter remote, kategorikan ke klaster A–H (Services & Value), beri skor 0–5, dan centang checklist.

    Skor Relevansi (0–5) — Rubrik

    • F (40%) Function match: seberapa pas tugas peran dengan Services & Value.

    • S (25%) Stack match: Next.js/TS/Tailwind; Thirdweb v5; ERC-4337/1155; Base/Superchain, dsb.

    • E (15%) Ecosystem alignment: cocok dengan fokus Web3 etis, modular, anti vendor lock‑in.

    • R (10%) Seniority fit: ruang bagi kontribusi Prof. NOTA (IC/Lead/Strategic) sesuai konteks.

    • T (10%) Timezone fit: async/remote-friendly (WIB ± beberapa jam).

    RS = 0–5 (hasil penilaian kualitatif berbobot di atas). Skor awal di tabel adalah default; bisa diubah ketika menyesuaikan lowongan spesifik.

    Checklist standar


    Tabel inti per klaster Services & Value. Gunakan kolom RS dan Checklist saat menilai lowongan tertentu.

    Role Title
    Level
    RS
    Checklist

    Enterprise Architect (Web3)

    Direction

    5

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Solutions Architect (Web3)

    Lead

    5

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]


    Role Title
    Level
    RS
    Checklist

    Head of Documentation

    Direction

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Documentation Manager

    Lead

    5

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]


    Role Title
    Level
    RS
    Checklist

    Senior Frontend Engineer (React/Next.js)

    IC Senior

    5

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Web3 Frontend Engineer (Thirdweb/AA)

    IC

    5

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]


    Role Title
    Level
    RS
    Checklist

    Head of Tokenomics

    Direction

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Operations Architect

    Lead

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]


    Role Title
    Level
    RS
    Checklist

    Program Manager (Tech × Culture)

    Lead

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Community Programs Lead

    Lead

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]


    Role Title
    Level
    RS
    Checklist

    Head of Developer Relations / Advocacy

    Direction

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    DevRel Lead

    Lead

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]


    Role Title
    Level
    RS
    Checklist

    Narrative Design Lead

    Lead

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Researcher (Web3/Market/Tech)

    IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]


    Role Title
    Level
    RS
    Checklist

    E‑commerce Operations Manager

    Lead

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Sourcing/Procurement Manager

    Lead

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Catatan: RS default mencerminkan kecocokan umum dengan Services & Value. Saat menilai lowongan nyata, revisi RS dan centang checklist sesuai JD.


    Scope: Snapshot bulanan (Oktober 2025) — daftar contoh open roles remote yang relevan sebagai bahan tailoring resume. Note: Ketersediaan & detail listing dapat berubah. Selalu cek ulang ke sumbernya.

    Role Title
    Company
    Category
    Source
    RS
    Checklist

    Sr. Front-End Engineer, Product

    Zora

    Engineering

    Optimism Jobs

    5

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    1. Baca JD di sumber — pastikan remote & zona waktu cocok.

    2. Centang Checklist kolom sesuai fakta JD.

    3. Revisi RS (0–5) jika diperlukan, berdasarkan rubrik F/S/E/R/T di dokumen bank peran.

    4. Tandai prioritas bulan ini di notes internal (High/Med/Low).

    5. Tailor resume dari ResumeAll sesuai kategori & stack peran.

    • Optimism Jobs (OP Labs/OP ecosystem) — Zora, Base, Conduit, Uniswap Foundation.

    • Web3.career — EoT Labs, MoonPay, Ethena Labs, Ethena Labs (design).

    • CryptoJobsList — Re7 Capital, CoW DAO, Thesis.

    Selengkapnya sumber daftar & halaman “remote” tercantum di Lampiran C.


    Frekuensi: bulanannya minggu pertama (mis. tanggal 1–7). Langkah:

    1. Kumpulkan listing dari papan pada Lampiran C; aktifkan filter Remote.

    2. Normalisasi judul → peta ke klaster A–H + level (Direction/Lead/Senior/Mid/Junior/IC).

    3. Nilai RS: gunakan rubrik di Bagian 0 (F/S/E/R/T).

    4. Centang checklist standar.

    5. Pilih prioritas: High/Med/Low (opsional, tergantung target bulan tersebut).

    6. Arsip snapshot bulan lalu (folder /snapshots/2025-10/…).

    7. Changelog: catat penambahan/pengurangan signifikan.

    Konvensi berkas:

    • roles-open-web3-remote_YYYY-MM.md — snapshot bulanan (bagian 2 dokumen ini).

    • remote-roles-living-list.md — bank peran (bagian 1 dokumen ini).

    • resumeall.md — master resume glossary (dokumen terpisah).


    Bagian ini menjelaskan cara menilai kecocokan tiap lowongan dengan menggunakan Checklist 7 poin dan Skor Relevansi (RS 0–5). Tujuannya: memastikan hanya lowongan yang benar-benar relevan yang diprioritaskan untuk tailoring resume dan apply.

    Centang hanya jika jelas tertulis di JD/situs perusahaan.

    1. Remote global/async Apa yang dicari: tertulis “remote”, “global”, atau “distributed”; tidak membatasi 1 negara. Bukti: halaman karier/JD menyebut remote; benefit/work policy mendukung async.

    2. Timezone kompatibel (WIB) Apa yang dicari: jam kerja fleksibel atau overlap ≤4 jam dengan WIB; tidak mewajibkan PST/EST full. Bukti: JD menyebut “flexible hours”, “±4h overlap”, atau tak menyebut jam kerja spesifik US/EU yang ketat.

    3. Stack cocok (Next.js/TS/Tailwind/Thirdweb/AA/1155/Base) Apa yang dicari: React/Next.js/TS atau kompatibel; untuk Web3: Thirdweb v5/SDK serupa, AA (ERC-4337), ERC-1155, L2 (Base/OP). Bukti: JD menyebut framework/SDK/standar yang sama/serumpun.

    4. Fungsi sesuai Services & Value Apa yang dicari: tanggung jawab inti selaras dengan klaster (A–H), mis. arsitektur solusi, dokumentasi, prototyping, product/ops. Bukti: JD menekankan outcome/fungsi yang kamu tawarkan (bukan sekadar daftar tools).

    5. Dampak terukur (metric/OKR) Apa yang dicari: ekspektasi metrik (performance, conversion, cost/gas, shipping time, docs coverage, dll). Bukti: JD menyebut KPI/OKR atau target angka/outcome.

    6. Kebijakan konten/IP aman Apa yang dicari: tidak ada klausa yang bertentangan dengan lisensi teksmu; dokumentasi internal dapat disintesis menjadi artefak publik yang diizinkan. Bukti: policy/legal page, atau konfirmasi di FAQ perusahaan.

    7. Ada ruang konsultasi/arsitektur (jika peran utamanya eksekusi) Apa yang dicari: kesempatan memberi masukan arsitektural/strategis, bukan hanya “pengikut task”. Bukti: JD menyebut discovery/design reviews/architecture proposals.

    Legenda kolom “Checklist” di tabel [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult → urutannya sama persis dengan 7 poin di atas.


    Gunakan rubrik berbobot berikut untuk menghitung W lalu bulatkan ke RS:

    • F (40%) — Function match: seberapa pas tugas peran dengan Services & Value.

    • S (25%) — Stack match: kedekatan tech stack (Next.js/TS/Tailwind, Thirdweb v5, AA 4337, ERC-1155, Base/OP).

    • E (15%) — Ecosystem alignment: keselarasan nilai (modular, anti vendor lock-in, etis/transparan).

    • R (10%) — Seniority fit: ada ruang kontribusi sesuai pengalaman Prof. NOTA (IC/Lead/Strategic).

    • T (10%) — Timezone fit: cocok untuk kerja async dari WIB.

    Formula: W = 0.40·F + 0.25·S + 0.15·E + 0.10·R + 0.10·T RS = pembulatan W ke bilangan bulat 0–5 (round to nearest; 4.5 → 5).

    Pedoman memberi skor per faktor (0–5):

    • 5 = sangat pas / native fit

    • 4 = kuat, ada sedikit gap

    • 3 = cukup, perlu adaptasi kecil

    • 2 = pinggiran, butuh adaptasi sedang

    • 1 = lemah, tidak direkomendasikan

    • 0 = tidak relevan


    1. Baca JD → pastikan “remote” & kebijakan waktu.

    2. Centang Checklist (7 kotak) sesuai fakta.

    3. Nilai F/S/E/R/T (0–5) → hitung W → bulatkan ke RS.

    4. Tentukan prioritas (opsional) → High / Medium / Low.

    5. Catat catatan singkat (mis. “butuh bukti kontribusi docs”, “butuh contoh AA 4337”).

    Contoh singkat: “Senior Front-End Engineer (Product) — Zora” F=5 (FE product fit), S=4 (React/Next kuat; Thirdweb opsional), E=4 (konteks on-chain kreator), R=4 (Senior pas), T=5 (remote). W = 0.40·5 + 0.25·4 + 0.15·4 + 0.10·4 + 0.10·5 = 4.5 → RS = 5.



    • Peran non-Web3 tapi kompatibel (mis. Frontend umum): naikkan S jika stack inti cocok; turunkan E bila ekosistem tak on-chain.

    • Zona waktu ketat (mis. “9–5 PST wajib”): turunkan T ke 1–2, atau jangan centang “TZ”.

    • Kontrak jangka pendek/gig: fokuskan checklist Impact & Function; RS ≥3 biasanya layak dicoba.

    • Duplikasi judul beda konten: prioritaskan yang menuliskan outcome/matrix jelas, bukan hanya daftar tools.


    • Minggu 1: tarik listing dari sumber; tambah baris snapshot & nilai RS.

    • Minggu 2–3: kirim 5–10 aplikasi prioritas (RS ≥4 / Checklist ≥5).

    • Minggu 4: review hasil & perbarui catatan (apa yang perlu ditingkatkan di ResumeAll/portfolio).


    Strategi/Arsitektur: Solutions Architect (Web3) • Enterprise Architect • Innovation Strategist • Discovery Lead • TPM • Presales Engineer.

    Dokumentasi/Konten: Technical Writer • Documentation Engineer • Knowledge Manager • API Writer • Content Strategist • Copywriter • UX Writer • Editor • Localization.

    Engineering: Frontend Engineer (React/Next) • Web3 Frontend • Full‑stack JS • Thirdweb SDK • Wallet/AA (ERC‑4337) • QA Automation • QA Manual • Integration • Discord Bot Dev.

    Produk/Ops: Product Manager • Product Owner • Business Analyst (Web3) • Ops Architect • Scrum Master • PMO Analyst • Release Manager.

    Komunitas/Publik: Community Manager • Discord Admin/Moderator • Developer Advocate • Technical Evangelist • Speaker/Instructor • Campaign Strategist • Social Content Producer.

    Custom/Research: Researcher • Narrative Designer • Proposal/Grant Writer • UX Research Assistant.

    E‑commerce/Legacy: E‑commerce Ops • Marketplace Specialist • Sourcing/Procurement • Logistics Coordinator • Customer Support.



    • 5: Sangat cocok (fungsi & stack inti; ekosistem pas).

    • 4: Cocok kuat (fungsi atau stack inti pas; variabel lain cukup).

    • 3: Cukup cocok (fungsi pas, stack perlu adaptasi kecil).

    • 2: Pinggiran (fungsi/stack kurang; bisa sebagai stepping stone).

    • 1: Rendah (kurang relevan, tapi ada nilai belajar/jejaring).

    • 0: Tidak cocok.


    Papan khusus Web3

    • Web3.career — halaman Remote Web3 Jobs.

    • CryptocurrencyJobs.co — halaman Remote (+ kategori per fungsi).

    • CryptoJobsList — halaman Remote dan daftar Remote Companies.

    • Remote3.co — papan Web3 khusus (klaim 22k+ listing).

    • CryptoJobs.com — alternatif portal Web3.

    • RemoteOK — kategori Crypto/Blockchain (filter remote).

    • Wellfound/AngelList — kategori Web3/Crypto (startup).

    • FindWeb3 / Web3‑Jobs.xyz — alternatif ceruk.

    Gig/Bounty/Grant

    • Gitcoin — Grants, bounties, dan integrasi bounty sebagai sinyal hiring.

    • Superteam Earn (Solana) — bounty, projects, grants.

    • Bankless Jobs — papan kurasi Bankless.

    Ekosistem L1/L2 (langsung ke sumber)

    • Optimism / OP Labs — job board resmi (sering remote).

    • Arbitrum Foundation — careers / ecosystem jobs.

    • Aptos Foundation / Aptos Labs — ecosystem jobs.

    • Polygon — Ecosystem Job Board.


    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.


    0) Tentang Dokumen ini

    **[Role Title] — [Company]**
    Sumber: [link] • Kategori: [A–H] • Level: [Direction/Lead/Senior/Mid/Junior/IC]
    Checklist: [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult
    Skor faktor: F=? S=? E=? R=? T=? → W = 0.40F + 0.25S + 0.15E + 0.10R + 0.10T = ?
    **RS = ? (0–5)** • Prioritas: [High/Med/Low]
    Catatan: [opsional—kesenjangan, bukti yang disiapkan, orang yang bisa dihubungi]

    1) Master Catalog — Posisi Remote yang Selaras (A–H)

    A. Strategic Vision & Consultation

    B. Intellectual Property & Storytelling

    C. Web3 Development & Prototyping

    D. Business Architecture

    E. Cultural & Social Innovation

    F. Personal Brand Access

    G. Custom Creation

    H. Global Trade & Distribution (Legacy)

    2) Snapshot “Open Roles” (contoh nyata terkini)

    Tabel — Open Roles (Okt 2025)

    Cara Pakai

    Sumber per Entri

    3) Cara Menyusun & Memperbarui

    4) Panduan Checklist & Skor RS

    A) Checklist 7 Poin (apa yang dicek & buktinya)

    B) Skor Relevansi (RS 0–5)

    C) Langkah Penilaian (gunakan tiap kali menambah baris)

    D) Template Evaluasi Per Lowongan (copy–paste)

    E) Kasus Tepi & Tips

    F) Siklus Pembaruan Bulanan (ringkas)

    5) Bank Kata Kunci (untuk ATS/AI)

    6) Lampiran-Lampiran

    Lampiran A — Contoh Checklist Penuh (copy–paste per lowongan)

    Lampiran B — Skala RS (0–5)

    Lampiran C — Sumber (Job Boards & Ekosistem)

    BGC X IBLOOMING SIMULATION DOC V0.1

    Defines the simulation plan for the BGC × iBLOOMING integration. For internal use by BGC × iBLOOMING founders & core team. Scope: Phase-1 Simulation for ALPHA Layer & Reward Sustainability

    Status: Archived Phase-1 Token Policy Simulation Specification — For internal use by BGC × iBLOOMING founders & core team. Author: Prof. NOTA v.11.11 Scope: Phase-1 Simulation for ALPHA Layer & Reward Sustainability


    This document defines the simulation plan for the BGC × iBLOOMING integration.

    Its main purposes are:

    • To translate 24-month historical data (PC, SP, rewards, cash-outs, user behaviour) into a simulation model.

    • To derive sustainable parameter ranges for:

    • PC/SP → ALPHA conversions,

    • reward allocation and sinks,

    • cash-out windows and thresholds,

    • treasury protection and risk limits.

  • To provide data-backed input for:

    • WHITEPAPER v1 (draft) (final wording and numbers),

    • TOKENFLOW v1 (draft) (final formulas and guards),

    • ALPHA Implementation Blueprint (contract-level rules).

  • This Simulation Doc reads together with:

    • LIVING Doc (strategic context & execution pillars),

    • UNDERSTANDING Doc (AS-IS model),

    • WHITEPAPER Doc (draft),

    • TOKENFLOW Doc (draft).


    • Phase-1 ALPHA Layer simulation, using real BGC × iBLOOMING operational data.

    • Modeling of:

      • PC/SP generation and consumption,

      • reward accrual and distribution,

      • member cash-out behaviour,

      • affiliate network growth patterns.

    • Parameter exploration for:

      • ALPHA issuance,

      • reward caps/limits,

      • cash-out frequency, thresholds, and fees,

      • ALPHA sinks and utility events.

    • Measuring sustainability, fairness, and operational load.

    • UX design and UI flows.

    • Final smart contract implementation details (covered in ALPHA Blueprint).

    • Public token market dynamics (iBC/iBTC trading, order books, etc.).

    • Long-term legal structuring beyond the assumptions needed for Phase-1.


    • BGC transaction logs:

      • PC (Purchase Credit) events,

      • SP (Sales Point) events,

      • Membership tiers (Pathfinder, Voyager, etc.),

      • e-wallet balances and movements,

      • cash-out requests and actual payouts (weekly cycles).

    • iBLOOMING product & engagement data:

      • course purchases,

      • feature usage,

      • campaign-based boosts (if any).

    • Aggregated affiliate network stats:

      • number of active members,

      • churn/retention,

      • average earnings per segment.

    • Data is sufficiently clean to support scenario modeling (minor anomalies will be noted).

    • AS-IS reward rules from UNDERSTANDING Doc are taken as baseline behaviour.

    • No new external shocks (e.g. regulation bans) are assumed in v0.1 scenarios.

    • Public token (iBC/iBTC) will be derived after ALPHA layer validation.


    • Member: an individual with PC/SP history, wallet balance, and cash-out actions.

    • Event:

      • PC creation,

      • SP creation,

      • reward accrual,

      • bonus/top-up,

      • cash-out request,

      • on-hold / rejected events (if any).

    • ALPHA Ledger (virtual in v0.1):

      • ALPHA-earned,

      • ALPHA-spent/locked,

      • ALPHA-equivalent of existing rewards.

    • Base time unit: monthly, with the ability to drill down to weekly if needed.

    • Simulation horizon: 24 months historical, plus projected 12–24 months (optional).

    Examples:

    • Total PC, total SP, and their distributions.

    • Reward obligations (outstanding, paid, pending).

    • Member-level balances and cash-out frequency.

    • Simulated ALPHA supply:

      • issued,

      • locked,

      • available for spend.


    This section lists the parameters that will be explored through simulation. Each parameter will have: Name, Symbol, Description, Range, Default, Decision Owner.

    Name
    Symbol
    Description
    Range (for simulation)
    Default
    Decision Owner

    PC→ALPHA multiplier (per 100 PC)

    k_PC

    ALPHA minted when 100 PC is converted (100 PC = 1 USD in ).

    0.5 – 1.5 ALPHA per 100 PC

    1.0

    Founders + Tokenomics

    • k_PC — PC-to-ALPHA multiplier.

    • k_SP — SP-to-ALPHA multiplier.

    • Tier-based modifiers for:

      • rank,

      • product type,

      • campaign.

    • Caps per period:

      • max ALPHA per user per month,

      • max ALPHA per group per month.

      • cap_u and cap_g use percentile data, so they don't need absolute numbers first.

    Name
    Symbol
    Description
    Range (for simulation)
    Default
    Decision Owner

    Global reward intensity factor

    R_global

    Global scaling factor for all reward shares (RR/GR/GPSP/WEC, etc.) relative to AS-IS.

    0.7 – 1.3 (70% – 130% of AS-IS)

    1.0

    Founders + Tokenomics

    • Reward share splits (RR/GR/GPSP/etc., as represented in ALPHA).

    • ALPHA sinks:

      • classes,

      • boosts,

      • CP digital products,

      • special campaigns.

    • Treasury buffers:

      • minimum reserve ratio,

      • emergency throttle rules.

    • The main idea: we can see the runway & payout ratio graph for each scenario, then the Founders can say, “we are comfortable with 6 months runway and payout ≤ 90% inflow” or ask for a change.

    Name
    Symbol
    Description
    Range (for simulation)
    Default
    Decision Owner

    Minimum cash-out amount (USD)

    C_min_usd

    Minimum balance that can be cashed out in one request.

    50 – 150 USD

    100 USD

    Founders + Finance

    • Minimum cash-out amount (e.g. 50–100 USD equivalent).

    • Cash-out frequency:

      • weekly processing (AS-IS),

      • windows vs always-open behaviour.

    • Cash-out fees:

      • percentage fee range,

      • fixed fee (if any).

    • Cooling-off rules (anti-abuse).

    • How to use in simulation:

      • AS-IS scenario: C_mode = ALWAYS_OPEN, C_min_usd = 100, C_fee_bps ≈ 0–100, C_win_year & C_win_days ignored.

      • Windows Pilot Scenario:

    Name
    Symbol
    Description
    Range (for simulation)
    Default
    Decision Owner

    Per-user daily gas sponsorship cap (USD)

    G_user_daily_usd

    Maximum limit of estimated sponsored gas costs per user per day.

    0.05 – 0.25 USD

    0.10 USD

    Founders + Tech + Finance

    • Sponsored gas ceilings:

      • max sponsorship per user per day,

      • global sponsorship cap per day.

    • Anti-Sybil parameters (from TOKENFLOW draft):

      • referral cooldown,

      • max Tier-1 joins/day per actor,

      • device-uniqueness limits.


    We will define multiple simulation scenarios.

    Each scenario will produce metrics for:

    • sustainability,

    • fairness,

    • liquidity,

    • member experience.

    • Mirrors AS-IS behaviour as closely as possible.

    • Purpose: ensure simulation output matches historical patterns.

    • Lower reward intensity,

    • stricter caps and windows,

    • focus on treasury safety and long-term sustainability.

    • Higher reward intensity for selected segments,

    • more aggressive growth incentives,

    • monitored for sustainability risks.

    • Sudden drop in sales (e.g. -30% revenue).

    • Rapid membership growth (e.g. 2× active members in 12 months).

    • High cash-out demand (spike in withdrawals).

    • Changes in behaviour due to new ALPHA sinks.

    For v0.1, not all parameters will be varied across scenarios. We will focus on a subset of primary “knobs”:

    • Reward intensity & pools: R_global, R_pool

    • ALPHA caps & sinks: cap_u, cap_g, S_target

    • Treasury safety: T_runway, T_payoutMax

    • Cash-out behaviour: C_mode, C_min_usd, C_fee_bps, C_win_year, C_win_days

    • Web3 ops: G_user_daily_usd, G_global_daily_usd

    All other parameters will remain at their default values for v0.1, unless explicitly stated.

    Parameter
    Baseline (AS-IS-ish)
    Conservative (“Safety-First”)
    Growth (“Expansion”)
    Notes

    R_global

    1.0

    0.85

    1.15

    Scale all rewards vs AS-IS.

    R_pool

    Interpretation (for later discussions):

    • Baseline: very close to existing BGC behaviour, with modest guardrails.

    • Conservative: rewards are dialed down slightly, treasury thresholds are stricter, and cash-out is run under a quarterly window model for stress comparison.

    • Growth: reward intensity is higher, sinks are more active, cash-out is more user-friendly, and gas sponsorship is more generous.

    These parameter sets are starting points. They can be refined after the first simulation runs.

    Stress-test scenarios focus less on changing parameters and more on applying external shocks to the Baseline or Conservative parameter sets.

    For v0.1, we will use the following external shocks:

    1. Revenue Shock (Downturn)

      • Overall PC/SP inflow reduced by 30% over a 6–12 month period.

      • Goal: observe how quickly treasury runway degrades and whether safety thresholds (T_runway, T_payoutMax) are violated.

    2. Membership Growth Shock (Expansion)

      • Active member count increased by 50% over 12 months.

      • PC/SP per member remains the same.

      • Goal: test whether caps (cap_u, cap_g) and sponsorship limits (G_user_daily_usd, G_global_daily_usd) still hold under higher load.

    3. Cash-Out Demand Shock

      • Cash-out requests spike by 50–100% for several consecutive months (e.g. due to external events or campaigns).

      • Goal: see how payout/inflow ratio and treasury buffers behave when members try to realise rewards more aggressively.

    4. Behavioural Shift Shock (Increased Utility Usage)

      • ALPHA sinks become more attractive (e.g. more classes, boosts, CP products).

      • Sink usage moves from 60% to 80% of ALPHA minted.

      • Goal: test whether higher utility consumption improves sustainability or introduces other imbalances.

    These shocks can be applied on top of:

    • Baseline parameters, to mimic “realistic but stressed” conditions, and

    • Conservative parameters, to see if safety-first settings are sufficient.

    The results will inform:

    • how robust the chosen parameter ranges are,

    • whether additional guardrails are needed,

    • and what “worst-case” founder decisions should prepare for.


    Key metrics include:

    • Treasury Sustainability

      • net outflow vs inflow,

      • reserve ratio over time,

      • worst-month drawdown.

    • Reward Fairness

      • distribution concentration (Reward Gini),

      • earnings by member tier/segment.

    • Member Experience

      • average time-to-cash-out,

      • denial/limitation rate (if windows or caps are applied),

      • ALPHA utility usage (spend vs hoard).

    • System Health

      • volatility of obligations,

      • sensitivity to shocks,

      • robustness of guardrails.


    High-level workflow:

    1. Data Ingestion

      • Extract and clean 24-month dataset.

    2. Model Preparation

      • Map AS-IS rules into simulation logic.

    3. Parameter Set Definition

      • Select parameter ranges and default values.

    4. Scenario Execution

      • Run baseline, conservative, growth, and stress-test scenarios.

    5. Metric Calculation

      • Compute sustainability, fairness, and member experience metrics.

    6. Analysis & Interpretation

      • Compare scenarios and identify safe + optimal ranges.

    7. Founder Review

      • Present scenario outputs and recommended parameter ranges.


    From this Simulation v0.1, we expect:

    • Simulation Report v0.1

      • description of scenarios and parameter ranges tested,

      • tables/graphs of key metrics,

      • discussion of trade-offs.

    • Parameter Recommendations

      • suggested ranges for PC/SP → ALPHA,

      • proposed cash-out models (frequency, thresholds, fees),

      • proposed caps and guardrails.

    • Inputs for:

      • (final numbers and narrative),

      • (final formulas and policy tables),

      • ALPHA Implementation Blueprint (contract-variable defaults).


    A non-exhaustive list of decisions where founder input is needed:

    • Acceptable range for cash-out flexibility vs treasury safety.

    • Appetite for growth-heavy vs conservative reward intensities.

    • Minimum acceptable reserve buffer.

    • Priority between:

      • user autonomy (always-open cash-out),

      • system protection (windows, fees, cooling periods).

    These questions will be refined once the first simulation runs are available.


    • v0.1 (this doc):

      • Define structure, scope, parameters, and scenarios.

    • v0.2:

      • Integrate real data mapping + first sample outputs.

    • v1.0:

      • Finalised simulation report for founder decision-making.

    Next immediate task:

    • Implement v0.1 across:

      • data extraction,

      • parameter tables,

      • scenario configuration.


    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.


    1. Purpose & Context

    2. Scope & Non-Scope

    2.1 In Scope

    2.2 Out of Scope (for v0.1)

    3. Data Sources & Assumptions

    3.1 Data Sources (24-Month Window)

    3.2 Key Assumptions

    4. Simulation Model Overview

    4.1 Entities

    4.2 Time Resolution

    4.3 State Variables

    5. Parameters to Explore (v0.1)

    5.1 Conversion Parameters (PC/SP → ALPHA)

    5.1.1 Parameter Table — Conversion

    5.2 Reward & Treasury Parameters

    5.2.1 Parameter Table — Reward & Treasury

    5.3 Cash-Out Parameters

    5.3.1 Parameter Table — Cash-Out

    5.4 Web3-Related Operational Parameters (Phase-1 Touchpoints)

    5.4.1 Parameter Table — Web3 Ops (Gas & Anti-Sybil)

    6. Scenario Design

    6.1 Baseline Scenario

    6.2 Conservative Scenario

    6.3 Growth Scenario

    6.4 Stress-Test Scenarios

    6.5 Scenario Parameter Sets (v0.1)

    6.5.1 Core Scenario Grid

    6.6 External Shocks for Stress-Test Scenarios

    7. Metrics & Evaluation Criteria

    8. Simulation Workflow

    9. Expected Outputs & Deliverables

    10. Open Questions for Founders

    11. Versioning & Next Steps

    Product Strategy Lead (Web3)

    Lead

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Tokenomics Strategist/Designer

    IC Senior

    5

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Technical Program Manager (TPM)

    Lead

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Transformation/Innovation Consultant

    IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Business/Systems Analyst (Web3)

    IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Technical Writer / Documentation Engineer

    IC

    5

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    API Documentation Specialist

    IC

    5

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Content Strategist (Tech)

    IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Copywriter (Tech/Brand)

    IC

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    UX Writer / Editor / Proofreader

    IC

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Full‑stack JS (Node/Next)

    IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Wallet/Smart Account Integration (ERC‑4337)

    IC

    5

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Smart Contract Integrations Engineer

    IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    QA Automation (JS)

    IC

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    QA Tester (Manual)

    IC Junior

    2

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Discord Bot Developer (JS/TS)

    IC

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Build/Release Engineer (Vercel/CI)

    IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Product Manager

    Lead/IC

    5

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Product Owner

    Lead/IC

    5

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Technical Project Manager

    Lead/IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Scrum Master / Agile Delivery Lead

    Lead

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Business Analyst (Web3)

    IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Release Manager

    IC

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Community Manager

    IC

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Discord Admin/Moderator

    IC Junior

    2

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Gamification Designer

    IC

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Learning Designer (Web3)

    IC

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Developer Advocate / Technical Evangelist

    IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Speaker / Instructor (remote)

    IC

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Campaign Strategist / Social Content Producer

    IC

    3

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Proposal/Grant/RFP Writer

    IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    UX Research Assistant

    IC Junior

    2

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Rapid Prototype Engineer

    IC

    4

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Marketplace Specialist (Listing/SEO/Foto)

    IC

    2

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Inventory/SKU Manager

    IC

    2

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Vendor/Logistics Coordinator

    IC

    2

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Customer Support / Success

    IC

    2

    [ ] [ ] [ ] [ ] [ ] [ ] [ ]

    Sr. Back-End Engineer, Product

    Zora

    Engineering

    Optimism Jobs

    4

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Product Manager

    Conduit

    Product

    Optimism Jobs

    5

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Implementation Engineer

    Conduit

    Engineering

    Optimism Jobs

    4

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Token & Governance Research Specialist

    Base

    Research

    Optimism Jobs

    4

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Senior Staff Protocol Engineer

    Base

    Engineering

    Optimism Jobs

    3

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Community Support Specialist (Part‑time)

    Zora

    Community

    Optimism Jobs

    2

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Senior Social Media Manager

    EoT Labs

    Marketing

    Web3.career

    3

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    FIU TM Analyst

    MoonPay

    Compliance

    Web3.career

    2

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Execution Trader

    Ethena Labs

    Trading

    Web3.career

    2

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Head of Product Design

    Ethena Labs

    Design

    Web3.career

    3

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Backend Engineer

    CoW DAO

    Engineering

    CryptoJobsList

    4

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Options Portfolio Risk Manager

    Re7 Capital

    Risk/Finance

    CryptoJobsList

    2

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Associate Accountant

    Thesis

    Finance

    CryptoJobsList

    2

    [ ] Remote [ ] TZ [ ] Stack [ ] Function [ ] Impact [ ] IP [ ] Consult

    Ilustrasi 12 oleh Prof. NOTA Inc. - QR Code Post-Session Quiz
    Ilustrasi 10 oleh Prof. NOTA Inc. - QR Code Interest Form
    Ilustrasi 1 oleh Prof. NOTA Inc. - Perkenalan oleh Prof. NOTA v.11.11
    Ilustrasi 8 oleh Prof. NOTA Inc. - Aktivitas Bersama (Role-Play) + Q&A Terstruktur
    Ilustrasi 2 oleh Prof. NOTA Inc. - International Payments dan Escrow
    Ilustrasi 5 oleh Prof. NOTA Inc. - Escrow — Traditional vs Smart-Contract
    C_mode = WINDOWS
    ,
    C_win_year = 4
    ,
    C_win_days = 7
    ,
    C_min_usd = 50
    ,
    C_fee_bps = 100
    .

    SP→ALPHA multiplier (per 1 SP)

    k_SP

    ALPHA minted per 1 SP (1 SP = 1 USD reward basis).

    0.5 – 1.5 ALPHA per SP

    1.0

    Founders + Tokenomics

    Tier bonus multiplier (max)

    m_tier

    Max multiplier between lowest and highest Affiliate tiers (Pathfinder → Special).

    1.0 – 2.0 (relative to base tier)

    1.5

    Tokenomics (with founders)

    Campaign boost multiplier (max)

    m_camp

    Max temporary boost for special campaigns or promos (applied on top of base conversion).

    1.0 – 3.0 (no boost → aggressive boost)

    2.0

    Tokenomics + Marketing

    User ALPHA cap per month

    cap_u

    Soft cap for ALPHA minted per user per month, relative to 95th percentile user-month.

    3× – 10× P95 baseline

    5× P95

    Tokenomics + Finance

    Group ALPHA cap per month

    cap_g

    Soft cap for ALPHA minted per group/team per month, relative to 99th percentile group.

    2× – 5× P99 baseline

    3× P99

    Tokenomics + Finance

    Pool reward intensity factor

    R_pool

    Specific factors for pools (GPSP, WEC, GMP, GEC) vs direct rewards.

    0.7 – 1.3

    1.0

    Founders + Tokenomics

    Target ALPHA sink utilisation

    S_target

    Expected percentage of ALPHA consumed (classes, features, boosts, CP products, etc.).

    0.40 – 0.80 (40% – 80% of minted)

    0.60

    Tokenomics + Product

    Minimum treasury runway (months)

    T_runway

    The minimum number of months of reward obligations that a treasury must be able to cover before being considered “unsafe.”

    3 – 12 months

    6

    Founders + Finance

    Emergency throttle runway (months)

    T_emerg

    The runway level at which the throttle/economy mechanism begins to engage

    1 – 3 months

    2

    Founders + Finance

    Max monthly payout vs inflow ratio

    T_payoutMax

    Maximum ratio (payout/inflow) before throttle (i.e. hold part of payout to the next window).

    0.70 – 1.10 (70% – 110% of inflow)

    0.90

    Tokenomics + Finance

    Cash-out fee (basis points)

    C_fee_bps

    Fee % for each cash-out (1% = 100 bps).

    0 – 300 bps (0% – 3%)

    100 bps (1%)

    Founders + Finance

    Cash-out mode

    C_mode

    Main mode: ALWAYS_OPEN (like the existing model) or WINDOWS (pilot-style).

    {ALWAYS_OPEN, WINDOWS}

    ALWAYS_OPEN

    Founders

    Number of cash-out windows per year

    C_win_year

    If C_mode = WINDOWS: number of windows in a year.

    4 – 52 (e.g. 4, 12, 24, 52)

    4 (quarterly)

    Founders + Tokenomics

    Window length (days)

    C_win_days

    If C_mode = WINDOWS: duration of each window.

    1 – 30 days

    7 days

    Founders + Tokenomics

    Processing lag (days)

    C_lag_days

    The time from when the cash-out request is approved until the funds actually reach the user's bank account.

    1 – 14 days

    7 days

    Ops + Finance

    Cooling-off after large cash-out

    C_cooloff

    The number of days before a user can make their next large cash-out (anti-abuse / liquidity shock).

    0 – 30 days

    7 days

    Founders + Tokenomics

    Global daily gas sponsorship cap (USD)

    G_global_daily_usd

    Maximum gas sponsorship limit for the entire system per day.

    20 – 100 USD

    20 USD

    Founders + Tech + Finance

    Referral cooldown (days)

    S_ref_cooldown

    Minimum distance of days between large referral events to avoid unnatural bursts.

    0 – 7 days

    1 day

    Tokenomics + Ops

    Max Tier-1 joins per actor per day

    S_max_t1_per_day

    Limit Tier-1 joins / day per actor before flag review/manual check.

    5 – 30

    10

    Tokenomics + Ops

    Duplicate device limit

    S_device_dupe

    How many different accounts can share 1 device before it is considered suspicious.

    1 – 5

    2

    Tech + Risk

    Audit sample rate (%)

    S_audit_pct

    Percentage of transactions/accounts sampled for manual/automated audit.

    1% – 10%

    5%

    Risk + Compliance

    Penalty cooling-off (days)

    S_penalty_days

    The length of the suspension/cooling-off period when an abuse case is detected and the reward/ALPHA is temporarily zeroed.

    3 – 30 days

    7 days

    Risk + Founders

    1.0

    0.9

    1.1

    Pool share intensity.

    cap_u (user ALPHA cap)

    5× P95

    3× P95

    7× P95

    Relative to 95th percentile user-month.

    cap_g (group ALPHA cap)

    3× P99

    2× P99

    4× P99

    Relative to 99th percentile group-month.

    S_target (sink target)

    0.60

    0.50

    0.70

    % of minted ALPHA expected to be consumed.

    T_runway (min months)

    6

    9

    6

    Treasury runway safety threshold.

    T_payoutMax

    0.90

    0.80

    1.00

    Max payout/inflow ratio per month.

    C_mode

    ALWAYS_OPEN

    WINDOWS

    ALWAYS_OPEN

    Behavioural change to test user vs treasury tradeoff.

    C_min_usd

    100 USD

    100 USD

    50 USD

    Minimum cash-out amount.

    C_fee_bps

    100 bps (1%)

    150 bps (1.5%)

    50 bps (0.5%)

    Cash-out fee.

    C_win_year

    – (unused if ALWAYS_OPEN)

    4 (quarterly)

    –

    Pilot window count.

    C_win_days

    –

    7

    –

    Pilot window duration.

    G_user_daily_usd

    0.10 USD

    0.07 USD

    0.15 USD

    Per-user gas sponsorship cap.

    G_global_daily_usd

    20 USD

    20 USD

    40 USD

    Global daily gas sponsorship cap.

    WHITEPAPER v1 (draft)
    TOKENFLOW v1 (draft)
    UNDERSTANDING Doc
    Ilustrasi 9 oleh Prof. NOTA Inc. - Next Steps (Untuk Mahasiswa & Kampus)
    Ilustrasi 3 oleh Prof. NOTA Inc. - Struktur Materi
    Ilustrasi 4 oleh Prof. NOTA Inc. - Peta Global Payment Rails — Bank/Fintech vs Stablecoin
    Ilustrasi 13 oleh Prof. NOTA Inc. - Lampiran: Handout Singkat (Ringkasan)
    Ilustrasi 7 oleh Prof. NOTA Inc. - Arsitektur Praktis (Minimal)
    Ilustrasi 6 oleh Prof. NOTA Inc. - Compliance & Record-Keeping (Student/Startup)
    Ilustrasi 11 oleh Prof. NOTA Inc. - Output Materi (Ujian Peserta)
    prof-nota-shadow-defrag
    Services & Value Prof. NOTA
    Services & Value Prof. NOTA

    NFT FOR RETURNED SKATE

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!


    title: "NFT Claim System — Prof. NOTA Inc. Skateboards" author: "Prof. NOTA Inc." version: "v1.0" date: "2025-06-24"

    🛹 NFT Claim System for Returned Skateboards

    🎯 TUJUAN UTAMA

    Menghadirkan sistem NFT berbasis Web3 yang menghargai pengguna skateboard Prof. NOTA Inc. yang telah mengembalikan produk rusak atau tidak terpakai. NFT tidak diberikan saat pembelian, melainkan saat pengguna mengembalikan skateboard bekas kepada Prof. NOTA Inc., sebagai bentuk:

    • Kepedulian lingkungan

    • Pelestarian sejarah pemakaian

    • Kontribusi komunitas


    • NFT bukan bukti pembelian, tetapi bukti pengembalian sadar.

    • Setiap design skateboard memiliki satu token ID NFT.

    • NFT diberikan setelah deck fisik diterima oleh Prof. NOTA Inc.

    • Deck yang dikembalikan akan didokumentasikan, dipamerkan, atau digunakan kembali untuk proyek keberlanjutan.


    1. Siapapun boleh membeli skateboard deck Prof. NOTA Inc. dari manapun.

    2. Jika deck rusak/tidak terpakai → jangan dibuang.

    3. Pemilik mengakses situs: https://notaskateboards.com/retur

    4. Isi form dan upload foto → sistem verifikasi manual


    • URL: /retur

    • Dibangun dengan: Next.js 15 + Tailwind CSS

    • Form input:

    • Dibangun dengan: Node.js / Express

    • Database: MongoDB

    • Fitur utama:

      • Verifikasi manual submission (dashboard internal)

    • Standar: ERC-1155 (tiap desain = token ID)

    • Diterapkan dengan ThirdWeb Signature Drop

    • Metadata NFT:


    Risiko
    Solusi Teknis dan Operasional


    1. Pengguna isi form dan upload foto deck rusak.

    2. Sistem mencatat submission dan status = “pending”.

    3. Tim Prof. NOTA melakukan verifikasi manual.

    4. Jika valid:


    Komponen
    Teknologi

    NFT yang didapat oleh pengirim deck bekas bukan hanya simbol, tapi juga bisa memiliki utility tambahan:

    • Akses diskon pembelian deck generasi berikutnya

    • Undangan pameran atau event komunitas

    • Koleksi unik yang akan dimuseumkan secara digital

    • Voting desain edisi terbatas

    • NFT sebagai akses token untuk fitur eksklusif (Discord / event)


    “Jangan dibuang. Kirimkan saja kembali. Kami akan abadikan jejakmu di blockchain.”

    – Prof. NOTA Inc. Skateboards, 2025


    Checklist pengerjaan tahap awal:


    • Inisiator: Prof. NOTA (v11)

    • Operasional Teknis: Tim Web3 Prof. NOTA Inc.

    • Kontak:

    • Versi Dokumen: v1.0


    Task ID: FE-RETUR-01 Judul: Buat halaman /retur untuk form pengembalian skateboard Deskripsi:

    • Form input: Nama, Email, Wallet Address, Foto Skateboard Rusak, Dropdown Desain, Checkbox Komitmen Kirim

    • Tambahkan integrasi ThirdWeb Connect untuk wallet

    • Responsive dan minimalis (tailwind-ready)

    Dikerjakan oleh: Frontend Developer Dependency: Desain UI (jika disediakan), komponen ReturForm.tsx


    Task ID: FE-RETUR-02 Judul: Tambahkan komponen feedback status Deskripsi:

    • Setelah form dikirim, tampilkan status: Pending Review, Approved, atau Rejected

    • Berikan estimasi waktu respon dan link tracking (jika ada)

    Dikerjakan oleh: Frontend Developer Dependency: Backend endpoint /api/retur


    Task ID: BE-RETUR-01 Judul: Buat API handler untuk menyimpan submission form Deskripsi:

    • Endpoint: POST /api/retur

    • Simpan data ke MongoDB: nama, email, wallet, design, foto URL, status

    • Validasi minimal: email + foto wajib

    Dikerjakan oleh: Backend Developer Dependency: DB setup + image hosting (Cloudinary/IPFS/etc)


    Task ID: BE-ADMIN-01 Judul: Dashboard internal admin untuk approval Deskripsi:

    • Menampilkan list pengajuan dengan filter status

    • Tombol: Approve, Reject

    • Form untuk masukkan nomor resi, catatan, dsb

    Dikerjakan oleh: Fullstack Developer Dependency: Login/role management (optional)


    Task ID: BE-NFT-01 Judul: Implementasi fungsi mint NFT ke wallet pengguna Deskripsi:

    • Gunakan mintTo atau claimWithSignature dari ThirdWeb SDK v5

    • NFT metadata: nama desain, foto deck, waktu retur

    • Image dapat diambil dari yang diupload user

    Dikerjakan oleh: Web3 Developer Dependency: Smart contract ERC-1155 sudah dideploy


    Task ID: SC-DEPLOY-01 Judul: Deploy smart contract NFT ERC-1155 Deskripsi:

    • 1 token ID per desain (misalnya: Phoenix Flame = tokenId 0)

    • Gunakan ThirdWeb dashboard untuk deploy dan setup

    • Pastikan metadata standar IPFS-ready

    Dikerjakan oleh: Smart Contract Engineer / Web3 Dev Dependency: Daftar desain yang tersedia


    Task ID: META-IPFS-01 Judul: Siapkan metadata NFT tiap desain Deskripsi:

    • Buat template .json metadata

    • Upload ke IPFS via ThirdWeb Storage atau Pinata

    • Simpan link metadata per desain/token ID

    Dikerjakan oleh: Web3 Support / Admin Teknis Dependency: Asset gambar dan nama desain


    Task ID: OPS-NOTIF-01 Judul: Kirim notifikasi setelah verifikasi diterima Deskripsi:

    • Email atau WhatsApp berisi instruksi pengiriman fisik

    • Tambahkan nomor referensi dan estimasi NFT dikirim

    Dikerjakan oleh: Ops/Support Team Dependency: Admin approval + kontak user valid


    Task ID: TEST-PILOT-01 Judul: Uji coba pengembalian 10 deck dari komunitas Deskripsi:

    • Rekrut 10 pengguna pertama

    • Simulasikan seluruh alur dari form → kirim deck → mint NFT

    • Catat feedback dan perbaikan UX

    Dikerjakan oleh: Tim QA / Ops Dependency: Semua task sebelumnya selesai


    Task ID: PUB-CLAIM-01 Judul: Buat copywriting dan halaman informasi untuk user umum Deskripsi:

    • Narasi: “Kirim kembali, bukan buang.”

    • Deskripsi langkah-langkah + FAQ

    • Sertakan CTA ke form /retur

    Dikerjakan oleh: Content Writer + Frontend Dependency: Final sistem siap digunakan


    Label
    Keterangan

    Formulir untuk pengguna yang ingin mengklaim NFT dengan mengembalikan skateboard deck rusak.


    • Input teks: Nama Lengkap, Email

    • Wallet: Connect Wallet (ThirdWeb Connect)

    • Dropdown atau input bebas: Nama Desain Deck

    • Upload: Foto kondisi skateboard (optional preview)

    • Checkbox: Komitmen kirim deck ke Prof. NOTA Inc.


    Berikut kode awalnya:


    • Menerima data dari ReturForm.tsx

    • Menyimpan data ke database (simulasi: log ke console atau simpan JSON)

    • Validasi dasar

    • Siap dikembangkan untuk integrasi MongoDB dan cloud storage (foto)



    • Formidable dipakai untuk handle file upload (multipart/form-data)

    • File disimpan ke folder public/uploads (sementara, bisa diganti IPFS/Cloudinary)

    • Validasi sederhana (semua field wajib)


    • Menampilkan daftar semua pengajuan dari endpoint backend

    • Menyediakan tombol Approve dan Reject

    • Menampilkan informasi pengirim: nama, email, wallet, desain, foto

    • Saat diklik “Approve” → update status + lanjut ke proses mint NFT (nanti)


    • GET /api/admin/retur → list semua submission

    • PATCH /api/admin/retur → update status (approved / rejected)


    Untuk tahap awal, kita gunakan simulasi penyimpanan data di file JSON lokal, agar tidak tergantung DB dulu. File data/returs.json akan berisi array objek ReturItem.




    Dashboard admin sekarang akan bekerja secara penuh:

    • Menampilkan semua submission

    • Menyimpan update status approved / rejected


    • Saat pengajuan diverifikasi, sistem akan langsung mint NFT ke wallet pengguna.

    • NFT yang dimintakan akan memiliki metadata sesuai desain yang dikembalikan.


    Tambahkan logic minting NFT menggunakan ThirdWeb SDK di bagian PATCH.


    1. Install jika belum:

    1. Buat file lib/mintNFT.ts:


    Tambahkan di dalam PATCH setelah status === "approved":


    Tambahkan ke .env.local:


    • Admin klik “Approve” → status berubah + NFT otomatis dikirim

    • Data returs.json bisa mencatat txId NFT-nya


    Mengirim pesan kepada pengguna bahwa:

    • Pengajuan mereka telah disetujui

    • NFT telah dikirim ke wallet mereka

    • Opsional: sertakan link txId (jika tersedia)


    Metode
    Tools / Layanan
    Status

    Untuk tahap awal kita prioritaskan Email, karena:

    • Cepat di-setup

    • Gratis untuk tahap awal

    • Tidak tergantung pada nomor WA pengguna yang aktif




    Tambahkan setelah NFT berhasil dimintakan:



    User mendapatkan email dengan isi:

    • Ucapan terima kasih

    • Info desain

    • Wallet address

    • (opsional) link transaksi NFT


    Dengan semua fondasi inti telah selesai (formulir, backend, dashboard, minting NFT, dan notifikasi email), berikut adalah daftar fitur dan peningkatan strategis yang dapat dilanjutkan oleh tim internal Prof. NOTA Inc.


    Komponen
    Status

    • Menyimpan data secara permanen dan dapat dicari.

    • Mempermudah laporan dan manajemen pengajuan.

    • Replacing returs.json.

    Task: Setup koneksi database & schema.


    • Halaman /retur/track?wallet=0x...

    • Pengguna bisa cek status pengajuan dan melihat txId jika sudah minting.

    Task: Komponen ReturStatus.tsx + endpoint /api/retur/status.


    • Halaman /retur/info atau /kenapa

    • Cerita gerakan sosial dan etika brand Prof. NOTA Inc.

    • Langkah-langkah mengirim skateboard

    • FAQ + ilustrasi

    Task: Komponen ReturIntro.tsx + desain visual ringan.


    • Fitur input nomor resi dari user.

    • Opsional integrasi API kurir (JNE, Wahana, dll.)

    • Sistem subsidi ongkir otomatis.

    Task: Tambahan field resi di dashboard + logic validasi ongkir.


    • Rute /museum atau /pameran

    • Menampilkan NFT hasil klaim publik (metadata ERC-1155)

    • Bisa filter: desain, waktu, kota

    Task: Komponen NFTGallery.tsx + fetch metadata kontrak.


    • Proteksi dashboard /admin

    • Login email, auth token, atau ThirdWeb Auth

    • Level akses: Viewer, Admin, Superadmin

    Task: Middleware route & pengelolaan auth.


    • Dukungan untuk ENS (.eth) atau Lens Protocol

    • NFT diklaim langsung ke identitas Web3 pengguna


    • Semua file .tsx, .ts, .env.example, dan dokumentasi .md

    • README dengan alur sistem dan cara deploy

    • CI/CD ringan (Vercel)


    1. 🎯 Implementasi DB MongoDB

    2. 🔍 Halaman tracking status pengguna

    3. 🖼 Museum NFT publik (galeri)

    4. 🌍 Landing page edukasi publik

    5. 🔒 Proteksi role-based akses dashboard


    Silakan lanjut sesuai prioritas proyek dan resource tim. Semua langkah ini bersifat modular, dapat dikerjakan paralel.

    —Prof. NOTA


    BGC X IBLOOMING WEB3 LOGIN IMPLEMENTATION

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Revision D — October 13, 2025 First Version: Status: Final Architecture Baseline — Implementation Pending Founder Confirmation: Product / Architecture Owner: Prof. NOTA Technical Implementation Owner: Yuku (Tech Owner), BGC × iBLOOMING Eng/DevOps


    Jika valid → pemilik mengirimkan deck ke alamat yang ditentukan

  • Setelah diterima → NFT dikirim ke wallet pemilik

  • Nama lengkap
  • Email

  • Alamat Wallet (atau tombol Connect Wallet)

  • Upload foto skateboard rusak

  • Pilih desain (dropdown / upload bukti pembelian opsional)

  • Checklist: “Saya akan mengirim skateboard ini ke alamat Prof. NOTA Inc.”

  • Tandai status (valid / ditolak / pending)

  • Endpoint minting NFT dengan ThirdWeb SDK claimWithSignature atau mintTo

  • Email/WhatsApp instruksi pengiriman fisik.
  • Setelah deck diterima → status updated → NFT dikirim.

  • Jika tidak valid → user diberi alasan penolakan.

  • API Gateway (opsional)

    Express / Next.js API route

  • Tanggal Rilis: 2025-06-24

    TEST

    Testing dan QA

    PUB

    Publikasi & Edukasi

  • Submit button → panggil API /api/retur

  • Klaim palsu (tidak benar-benar punya deck)

    Upload foto, verifikasi manual oleh tim Prof. NOTA

    Orang minta NFT tanpa mengirim fisik

    NFT hanya dikirim setelah barang diterima dan diperiksa

    Spam submission

    Rate limiting, CAPTCHA, validasi email

    Klaim ganda

    Batasi satu NFT per wallet per design / serial / bukti unik

    Deck tiruan

    Validasi visual, optional QR/sticker atau nomor produksi internal

    Frontend

    Next.js 15 + Tailwind CSS

    Wallet Integration

    ThirdWeb Connect (email opsional)

    Backend

    Node.js + MongoDB

    NFT Contract

    ERC-1155 via ThirdWeb SDK v5

    Hosting

    Vercel

    FE

    Frontend

    BE

    Backend

    SC

    Smart Contract

    META

    Metadata NFT

    OPS

    Operasional & Support

    Email

    Resend, SendGrid, nodemailer

    ✅ Mudah diintegrasi

    WhatsApp

    Twilio, WA Gateway, atau Wablas (lokal)

    ⚠️ Perlu API eksternal

    Formulir pengembalian

    ✅ Siap

    API penerimaan submission

    ✅ Siap

    Dashboard admin

    ✅ Siap

    Minting NFT setelah approve

    ✅ Siap

    Email notifikasi sukses

    ✅ Siap

    🧠 KONSEP DASAR

    💡 SKENARIO SINGKAT

    📦 ARSITEKTUR SISTEM

    1. Frontend: Web Form Pengguna

    2. Backend: Sistem Verifikasi & Minting NFT

    3. Smart Contract NFT

    🔐 STRATEGI ANTI-PENYALAHGUNAAN

    🛠️ FILE STRUKTUR PROYEK

    💌 ALUR LOGISTIK DAN OPERASIONAL

    🔧 STACK TEKNOLOGI YANG DIGUNAKAN

    🎁 UTILITY DAN VISI NFT

    📣 PESAN KEPADA PENGGUNA

    ✅ TAHAP IMPLEMENTASI

    📬 KONTAK DAN TANGGUNG JAWAB

    📋 TASK CARD TEKNIS — NFT Claim

    🧱 1. FRONTEND – HALAMAN FORM RETUR

    🧩 2. FRONTEND – STATUS SUBMISSION & FEEDBACK

    🔧 3. BACKEND – FORM HANDLER API

    🔐 4. BACKEND – DASHBOARD VERIFIKASI

    ✍️ 5. BACKEND – MINT NFT VIA THIRDWEB SDK

    🔗 6. SMART CONTRACT – DEPLOY ERC-1155 UNTUK SETIAP DESAIN

    📁 7. NFT METADATA – TEMPLATE & UPLOAD IPFS

    📨 8. NOTIFIKASI – EMAIL / WHATSAPP FOLLOW-UP

    🧪 9. TESTING – PILOT RETURN 10 DECK PERTAMA

    📢 10. PUBLIKASI – COPYWRITING & LANDING PAGE

    ✅ LABEL & PRIORITAS

    🎯 Komponen Pertama: ReturForm.tsx

    📦 Tujuan

    🔧 Fitur Form

    📁 File: src/components/ReturForm.tsx

    🛠️ API Endpoint: /api/retur.ts

    📌 Tujuan

    📁 File: src/pages/api/retur.ts

    🧪 Notes Teknis

    🧾 Komponen: ReturAdmin.tsx

    🎯 Tujuan

    📁 File: src/components/ReturAdmin.tsx

    🗃️ Endpoint yang perlu tersedia

    📁 File: src/pages/api/admin/retur.ts

    🗃️ Simulasi struktur file JSON

    🧠 Handler: api/admin/retur.ts

    📁 Struktur Direktori yang Perlu Ada

    ✅ Siap Digunakan

    🪙 Fungsi: Mint NFT setelah “Approved”

    🎯 Tujuan

    📁 Perubahan pada: api/admin/retur.ts (PATCH section)

    📦 Tambahan: ThirdWeb SDK Setup

    📄 Update api/admin/retur.ts (PATCH block)

    🔐 Environment Variables

    ✅ Hasil Akhir

    📬 Notifikasi otomatis via Email atau WhatsApp

    🎯 Tujuan

    2 Opsi Notifikasi

    ✅ Implementasi Email dengan Resend

    🔧 1. Instalasi

    📁 2. Buat file lib/sendEmail.ts

    🔧 3. Tambahkan ke api/admin/retur.ts (dalam PATCH block):

    📁 4. Tambahkan di .env.local

    🚀 Hasil Akhir

    🧩 LANJUTAN STRATEGIS — NFT Claim Skateboard

    ✅ TELAH SELESAI

    🧩 FASE LANJUTAN YANG DIREKOMENDASIKAN

    1. Integrasi Database Nyata (MongoDB/PostgreSQL)

    2. Tampilan User untuk Tracking Status

    3. Landing Page Publik Edukasi & CTA

    4. Sistem Logistik & Validasi Ongkir

    5. Halaman Museum Digital / Galeri NFT Retur

    6. Role-Based Access (Admin vs Publik)

    7. Eksperimen Identitas Web3 (opsional)

    8. Konversi Proyek ke Repositori GitHub

    🚦 REKOMENDASI URUTAN EKSEKUSI LANJUTAN

    nota@endhonesa.com
    {
      "name": "Returned Deck — Phoenix Flame",
      "description": "You've sent back a used Prof. NOTA Inc. skateboard. This NFT is proof of your journey.",
      "image": "ipfs://...",
      "attributes": [
        { "trait_type": "Design", "value": "Phoenix Flame" },
        { "trait_type": "Claim Date", "value": "2025-06-24" },
        { "trait_type": "Condition", "value": "Used" },
        { "trait_type": "Return Verified", "value": true }
      ]
    }
    src/
    ├── app/
    │   └── retur/
    │       └── page.tsx               # Halaman form pengguna
    ├── components/
    │   ├── ReturForm.tsx              # Komponen form utama
    │   └── ReturStatus.tsx            # Status tracking
    ├── lib/
    │   └── mintNFT.ts                 # Logika backend mint NFT
    ├── pages/api/
    │   └── retur.ts                   # Handler API form submission
    │   └── verify.ts                  # Endpoint admin approval
    "use client";
    
    // External libraries
    import { ConnectWallet, useAddress } from "@thirdweb-dev/react";
    import { useState } from "react";
    
    export default function ReturForm() {
      const walletAddress = useAddress();
    
      const [nama, setNama] = useState("");
      const [email, setEmail] = useState("");
      const [design, setDesign] = useState("");
      const [photo, setPhoto] = useState<File | null>(null);
      const [agreed, setAgreed] = useState(false);
      const [isSubmitting, setIsSubmitting] = useState(false);
      const [message, setMessage] = useState("");
    
      const handleSubmit = async (e: React.FormEvent) => {
        e.preventDefault();
        if (!walletAddress || !agreed || !photo) {
          setMessage("Lengkapi semua data dan hubungkan wallet Anda.");
          return;
        }
    
        const formData = new FormData();
        formData.append("nama", nama);
        formData.append("email", email);
        formData.append("wallet", walletAddress);
        formData.append("design", design);
        formData.append("photo", photo);
    
        setIsSubmitting(true);
        try {
          const res = await fetch("/api/retur", {
            method: "POST",
            body: formData,
          });
    
          if (res.ok) {
            setMessage("Pengajuan berhasil! Tim kami akan menghubungi Anda.");
            setNama("");
            setEmail("");
            setDesign("");
            setPhoto(null);
            setAgreed(false);
          } else {
            const data = await res.json();
            setMessage(data.error || "Gagal mengirim form.");
          }
        } catch (err) {
          setMessage("Terjadi kesalahan teknis.");
        }
        setIsSubmitting(false);
      };
    
      return (
        <div className="max-w-xl mx-auto px-4 py-6">
          <h2 className="text-xl font-bold mb-4">Klaim NFT Skateboard Rusak</h2>
          <ConnectWallet className="mb-4" />
          <form onSubmit={handleSubmit} className="space-y-4">
            <input
              type="text"
              placeholder="Nama Lengkap"
              value={nama}
              onChange={(e) => setNama(e.target.value)}
              className="w-full border px-3 py-2 rounded"
              required
            />
            <input
              type="email"
              placeholder="Email Aktif"
              value={email}
              onChange={(e) => setEmail(e.target.value)}
              className="w-full border px-3 py-2 rounded"
              required
            />
            <input
              type="text"
              placeholder="Nama Desain Deck (misalnya: Phoenix Flame)"
              value={design}
              onChange={(e) => setDesign(e.target.value)}
              className="w-full border px-3 py-2 rounded"
              required
            />
            <input
              type="file"
              accept="image/*"
              onChange={(e) => setPhoto(e.target.files?.[0] || null)}
              className="w-full border px-3 py-2 rounded"
              required
            />
            <label className="flex items-start space-x-2">
              <input
                type="checkbox"
                checked={agreed}
                onChange={() => setAgreed(!agreed)}
                className="mt-1"
                required
              />
              <span>
                Saya bersedia mengirim skateboard saya ke alamat yang akan
                diinformasikan oleh Prof. NOTA Inc.
              </span>
            </label>
            <button
              type="submit"
              disabled={isSubmitting}
              className="bg-black text-white px-4 py-2 rounded disabled:opacity-50"
            >
              {isSubmitting ? "Mengirim..." : "Kirim Formulir"}
            </button>
            {message && <p className="text-sm mt-2">{message}</p>}
          </form>
        </div>
      );
    }
    
    import { NextApiRequest, NextApiResponse } from "next";
    import formidable from "formidable";
    import fs from "fs";
    import path from "path";
    
    // Jangan parse body secara default
    export const config = {
      api: {
        bodyParser: false,
      },
    };
    
    export default async function handler(req: NextApiRequest, res: NextApiResponse) {
      if (req.method !== "POST") {
        return res.status(405).json({ error: "Metode tidak diizinkan." });
      }
    
      const form = formidable({ multiples: false });
    
      form.parse(req, async (err, fields, files) => {
        if (err) {
          console.error("Gagal parsing form:", err);
          return res.status(500).json({ error: "Gagal membaca data formulir." });
        }
    
        const { nama, email, wallet, design } = fields;
        const photo = files.photo as formidable.File;
    
        if (!nama || !email || !wallet || !design || !photo) {
          return res.status(400).json({ error: "Semua field wajib diisi." });
        }
    
        // Simulasi penyimpanan (nantinya ke database)
        console.log("📦 Data Pengajuan Masuk:");
        console.log({
          nama,
          email,
          wallet,
          design,
          photoPath: photo.filepath,
        });
    
        // Simulasi: pindahkan foto ke folder publik sementara
        const tempPath = photo.filepath;
        const fileName = `${Date.now()}-${photo.originalFilename}`;
        const targetPath = path.join(process.cwd(), "public", "uploads", fileName);
    
        try {
          fs.copyFileSync(tempPath, targetPath);
        } catch (err) {
          console.error("Gagal menyimpan file:", err);
          return res.status(500).json({ error: "Gagal menyimpan foto." });
        }
    
        // Response sukses
        return res.status(200).json({ message: "Formulir berhasil dikirim." });
      });
    }
    "use client";
    
    // External libraries
    import { useEffect, useState } from "react";
    
    type ReturItem = {
      id: string;
      nama: string;
      email: string;
      wallet: string;
      design: string;
      photoUrl: string;
      status: "pending" | "approved" | "rejected";
    };
    
    export default function ReturAdmin() {
      const [returs, setReturs] = useState<ReturItem[]>([]);
      const [loading, setLoading] = useState(true);
    
      const fetchReturs = async () => {
        setLoading(true);
        try {
          const res = await fetch("/api/admin/retur");
          const data = await res.json();
          setReturs(data.returs || []);
        } catch (err) {
          console.error("Gagal mengambil data pengajuan:", err);
        } finally {
          setLoading(false);
        }
      };
    
      const updateStatus = async (id: string, status: "approved" | "rejected") => {
        try {
          const res = await fetch(`/api/admin/retur`, {
            method: "PATCH",
            headers: { "Content-Type": "application/json" },
            body: JSON.stringify({ id, status }),
          });
          if (res.ok) {
            fetchReturs();
          }
        } catch (err) {
          console.error("Gagal update status:", err);
        }
      };
    
      useEffect(() => {
        fetchReturs();
      }, []);
    
      if (loading) return <p className="text-center">Memuat data...</p>;
    
      return (
        <div className="max-w-4xl mx-auto p-4">
          <h2 className="text-xl font-bold mb-4">📋 Daftar Pengajuan Retur</h2>
          {returs.length === 0 ? (
            <p>Belum ada pengajuan.</p>
          ) : (
            <ul className="space-y-4">
              {returs.map((item) => (
                <li key={item.id} className="border p-4 rounded shadow-sm">
                  <p><strong>Nama:</strong> {item.nama}</p>
                  <p><strong>Email:</strong> {item.email}</p>
                  <p><strong>Wallet:</strong> {item.wallet}</p>
                  <p><strong>Design:</strong> {item.design}</p>
                  <p><strong>Status:</strong> {item.status}</p>
                  <img
                    src={item.photoUrl}
                    alt="Foto Skateboard"
                    className="w-40 mt-2 border rounded"
                  />
                  {item.status === "pending" && (
                    <div className="mt-4 space-x-2">
                      <button
                        onClick={() => updateStatus(item.id, "approved")}
                        className="bg-green-600 text-white px-4 py-1 rounded"
                      >
                        Approve
                      </button>
                      <button
                        onClick={() => updateStatus(item.id, "rejected")}
                        className="bg-red-600 text-white px-4 py-1 rounded"
                      >
                        Reject
                      </button>
                    </div>
                  )}
                </li>
              ))}
            </ul>
          )}
        </div>
      );
    }
    [
      {
        "id": "123456789",
        "nama": "Andi",
        "email": "andi@example.com",
        "wallet": "0xABC...",
        "design": "Phoenix Flame",
        "photoUrl": "/uploads/123456.jpg",
        "status": "pending"
      }
    ]
    import { NextApiRequest, NextApiResponse } from "next";
    import fs from "fs";
    import path from "path";
    
    const dataPath = path.join(process.cwd(), "data", "returs.json");
    
    function readReturData() {
      if (!fs.existsSync(dataPath)) return [];
      const file = fs.readFileSync(dataPath, "utf-8");
      return JSON.parse(file);
    }
    
    function writeReturData(data: any[]) {
      fs.writeFileSync(dataPath, JSON.stringify(data, null, 2));
    }
    
    export default async function handler(req: NextApiRequest, res: NextApiResponse) {
      if (req.method === "GET") {
        const data = readReturData();
        return res.status(200).json({ returs: data });
      }
    
      if (req.method === "PATCH") {
        const { id, status } = req.body;
        if (!id || !["approved", "rejected"].includes(status)) {
          return res.status(400).json({ error: "Data tidak valid." });
        }
    
        const data = readReturData();
        const index = data.findIndex((item) => item.id === id);
        if (index === -1) {
          return res.status(404).json({ error: "Pengajuan tidak ditemukan." });
        }
    
        data[index].status = status;
        writeReturData(data);
    
        return res.status(200).json({ message: "Status diperbarui." });
      }
    
      return res.status(405).json({ error: "Metode tidak diizinkan." });
    }
    /data/returs.json         ← file database sementara
    /public/uploads/          ← tempat menyimpan foto yang diunggah
    npm install thirdweb
    // src/lib/mintNFT.ts
    import { ThirdwebSDK } from "thirdweb";
    import { BaseGoerli } from "thirdweb/chains";
    
    const sdk = new ThirdwebSDK(BaseGoerli, {
      clientId: process.env.THIRDWEB_CLIENT_ID,
      secretKey: process.env.THIRDWEB_SECRET_KEY, // only for server
    });
    
    export async function mintNFTTo(wallet: string, design: string) {
      const contract = await sdk.getContract(process.env.CONTRACT_ADDRESS!); // ERC-1155 contract
      const tokenId = getTokenIdByDesign(design);
    
      if (tokenId === undefined) {
        throw new Error("Desain tidak dikenali.");
      }
    
      const tx = await contract.erc1155.claimTo(wallet, tokenId, 1);
      return tx.id;
    }
    
    // Simulasi mapping desain ke tokenId
    function getTokenIdByDesign(design: string): number | undefined {
      const mapping: Record<string, number> = {
        "Phoenix Flame": 0,
        "Jungle Path": 1,
        "Future Glitch": 2,
      };
      return mapping[design];
    }
    import { mintNFTTo } from "@/lib/mintNFT";
    
    ...
    
    if (status === "approved") {
      try {
        const wallet = data[index].wallet;
        const design = data[index].design;
    
        const txId = await mintNFTTo(wallet, design);
        data[index].txId = txId;
      } catch (err) {
        console.error("Gagal mint NFT:", err);
        return res.status(500).json({ error: "Minting NFT gagal." });
      }
    }
    THIRDWEB_CLIENT_ID=your-client-id
    THIRDWEB_SECRET_KEY=your-secret
    CONTRACT_ADDRESS=0xYourERC1155ContractAddress
    npm install resend
    import { Resend } from "resend";
    
    const resend = new Resend(process.env.RESEND_API_KEY);
    
    export async function sendSuccessEmail(email: string, nama: string, design: string, wallet: string, txId?: string) {
      const txLink = txId ? `https://basescan.org/tx/${txId}` : "";
    
      const html = `
        <p>Halo ${nama},</p>
        <p>Terima kasih telah mengembalikan skateboard desain <strong>${design}</strong>.</p>
        <p>Kami telah mengirim NFT kenangan Anda ke wallet berikut:</p>
        <p><code>${wallet}</code></p>
        ${txId ? `<p>Tx Hash: <a href="${txLink}">${txId}</a></p>` : ""}
        <br />
        <p>Salam hormat,</p>
        <p><strong>Tim Prof. NOTA Inc. Skateboards</strong></p>
      `;
    
      await resend.emails.send({
        from: "nota@notaskateboards.com",
        to: email,
        subject: `NFT Retur Anda Sudah Dikirim — ${design}`,
        html,
      });
    }
    import { sendSuccessEmail } from "@/lib/sendEmail";
    
    ...
    
    if (status === "approved") {
      ...
      await sendSuccessEmail(data[index].email, data[index].nama, design, wallet, txId);
    }
    RESEND_API_KEY=your_resend_api_key

    Constraints & Non-Goals

  • Architecture Overview

  • User Journeys

  • Data Model (Unified)

  • API Specification

  • Security Model

  • Thirdweb Integration — Step-by-Step

  • DevOps & Environments

  • Migration & Rollout

  • Testing Strategy

  • Operations (RBAC & Merge)

  • Acceptance Criteria & Launch Checklist

  • Appendix — Reference Snippets

  • Appendix — Cost Estimates (Non-HR)


  • We operate on a single, unified credentials database (already in production) for BGC and iBLOOMING. Users can sign up and log in to any app (BGC Web, iBLOOMING Web, iBLOOMING Mobile) with the same username/password and, during rollout, may also authenticate with a Passkey (WebAuthn) as a first-class method.

    After login, users complete Wallet Setup by either:

    • Create EOA (Embedded/In-App) → auto-provision a Smart Account (AA); or

    • Connect existing wallet (SIWE) → auto-provision a Smart Account (AA).

    This standardizes on-chain identity to one EOA and one Smart Account (AA) per user per chain, enabling consistent features (rewards, receipts, payments) across the BGC/iB ecosystem with minimal friction and predictable costs.

    Bridging Web2 ↔ Web3. If a user does not yet have a BGC/iB account, they must first sign up for a BGC/iB account and then log in (via username/password or Passkey). Only after a successful login is Wallet Setup available: either Create an embedded EOA → auto-provision AA or Connect an existing Web3 wallet → auto-provision AA. Web3-native users who already have a BGC/iB account simply log in and proceed to Wallet Setup.

    Analytics & simulations. The unified mapping user_id ⇄ identity_id ⇄ (EOA, AA) enables reliable, on-chain-addressed telemetry for behavioral simulations (Alpha Coin → future iBC/iBTC).

    Partner signal. A single, passkey-enabled login and post-login Smart Account bootstrap operating across apps demonstrates concrete momentum while tokenomics is finalized.

    In scope: identity model, wallet binding, AA provisioning, SIWE, Passkey support, security, DevOps, and Thirdweb implementation. Out of scope: tokenomics/ledger rules, analytics dashboards, and non-auth product features.

    • Single credentials auth for the BGC/iB ecosystem.

    • Passkey (WebAuthn) as a first-class login method (rolling out), with username/password fallback.

    • Post-login Wallet Setup (Create or Connect), not pre-login.

    • Deterministic AA per identity (factory + salt).

    • Identity mapping: identity_id ⇄ user_id ⇄ (EOA, AA).

    • Admin Console with RBAC and full audit for binds/merges.

    • Thirdweb supplies SIWE, Embedded/In-App Wallet, Smart Accounts, and optional gas sponsorship.


    Constraints

    • Unified DB & identity

      • Single credentials store across BGC/iB; no per-app user tables.

      • One on-chain identity per user per chain: exactly 1 EOA + 1 AA.

      • DB integrity:

        • wallets: UNIQUE(address, chain_id) and CHECK (type IN ('EOA','AA'))

        • Enforce one-per-chain with UNIQUE(identity_id, type, chain_id) (so a user can’t end up with multiple EOAs/AAs on the same chain).

    • SIWE (existing wallets)

      • Per-login nonce (TTL 3–5 minutes); nonce consumed on successful verify.

      • Validate domain / origin URI / chainId; reject cross-site replay.

      • All SIWE traffic over TLS; audit message + address + nonce

    • Passkey (WebAuthn)

      • RP config pinned: rpId = auth domain, allowed origins explicit.

      • userVerification = required; resident/discoverable keys enabled.

      • Attestation policy defined (e.g.,

    • Smart Accounts (AA)

      • Deterministic deployment (factory + salt); one factory per chain per environment.

      • Optional gas sponsorship via paymaster/bundler with budget caps and alerting.

    • Secrets & privacy

      • Secrets in vault; regular rotation (JWT/JWKS, DB, RPC, webhooks).

      • PII minimization; sensitive fields encrypted at rest.

      • Observability + rate-limits for login/OTP/SIWE/AA endpoints; immutable audits for binds/merges.

    • In-App Wallet (Starter plan) uses Thirdweb’s built-in OTP (Email/Phone) for Create Wallet; no BYO-Auth/JWT for wallet creation in this phase.

    Non-Goals

    • No separate user tables per app within the BGC/iB ecosystem.

    • No server-side plaintext key handling for wallets (embedded/MPC only).



    5.1 New User (no BGC/iB account yet)

    1. Sign up a BGC/iB account (username/password; offer Passkey registration during or after signup).

    2. Log in using credentials or Passkey (MFA optional per policy).

    3. Wallet Setup (post-login): choose Create or Connect.

    4. AA provisioned deterministically → Done.

    5.2 Existing User (no wallet yet)

    1. Log in (credentials or Passkey).

    2. Wallet Setup (Create or Connect).

    3. AA provisioned → Done.

    5.3 Existing User (wallet already bound)

    1. Log in (credentials or Passkey).

    2. Skip Wallet Setup; identity already has EOA/AA.

    3. Proceed to app.


    users

    • user_id (PK), email (unique, nullable), phone (unique, nullable), username (unique), password_hash, mfa_enabled, timestamps.

    webauthn_credentials

    • credential_id (PK, b64url), user_id (FK→users), public_key, sign_count, transports, backup_eligible, backed_up, timestamps.

    identities

    • identity_id (PK), user_id (FK→users), timestamps. (Keeps future merge/link options without breaking unification.)

    wallets

    • wallet_id (PK), identity_id (FK), type (EOA|AA), address, chain_id, salt, timestamps.

    auth_providers

    • provider_id (PK), user_id (FK), provider_type (credentials|siwe), provider_ref (email/phone hash or EOA), timestamps.

    siwe_nonces

    • nonce (PK), used (boolean), expires_at (UTC), issued_for_domain, issued_for_uri, timestamps.

    audit_logs

    • log_id (PK), identity_id, user_id, action (bind|merge|unlink|passkey.register|passkey.login), actor, metadata, timestamps.

    Constraints

    • wallets: UNIQUE(address, chain_id); CHECK (type IN ('EOA','AA')); UNIQUE(identity_id, type, chain_id) ensures one EOA and one AA per chain.

    • webauthn_credentials.credential_id unique; sign_count monotonic (reject regressions).

    • siwe_nonces.nonce unique; must be unused and unexpired at verify time.

    • FK integrity enforced across all relations.


    Auth

    • POST /auth/credentials/login → { username|email|phone, password } → { session_jwt, user_id }

    • POST /auth/passkey/register/options → server generates WebAuthn attestation options

    • POST /auth/passkey/register/verify → verify attestation; persist credential; return { session_jwt? }

    • POST /auth/passkey/login/options → server generates WebAuthn assertion options

    • POST /auth/passkey/login/verify → verify assertion; start session → { session_jwt, user_id }

    • (optional) GET /auth/passkey/devices & DELETE /auth/passkey/devices/:credential_id

    Wallet Setup

    • POST /wallet/provision → uses session → Create EOA (if missing) + deploy AA → { identity_id, eoa, aa }

    • POST /wallet/connect/siwe → { message, signature } → verify SIWE (domain/uri/chainId + nonce), bind EOA, deploy AA → { identity_id, eoa, aa }

    Identity

    • GET /identity → session → { identity_id, eoa, aa }

    Admin/Audit

    • GET /admin/merge/diff?source&target

    • POST /admin/merge/execute (dual-control for risky merges)

    • GET /admin/audit?identity_id|user_id


    • Passkey (WebAuthn)

      • rpId = auth domain; allowed origins explicitly listed.

      • userVerification = required; resident/discoverable credentials enabled.

      • Attestation policy defined (e.g., none); store credential_id, public_key, monotonic sign_count.

      • Device lifecycle: list/revoke passkeys; backup codes for account recovery.

    • Credentials

      • Password hashing with Argon2id (memory-hard), strong parameters; lockout + step-up on anomalies.

    • SIWE (existing wallets)

      • Per-login nonce (TTL 3–5 min); consume on success; reject reused/expired.

      • Validate domain / URI / chainId; enforce TLS; audit address + message + nonce usage.

    • Smart Accounts (AA)

      • Deterministic deployment (factory + salt) per chain; monitor deploy success rate; optional paymaster/bundler with budget caps and alerts.

    • Sessions & secrets

      • Short-lived JWT; HttpOnly + Secure cookies; rotation on refresh; CSRF protection on state-changing routes.

      • Secrets in vault; regular rotation (JWT/JWKS, DB creds, RPC, webhooks).

    • Privacy, observability & abuse prevention

      • PII minimization; encryption at rest.

      • Rate-limit login/OTP/SIWE/merge; WAF on public APIs.

      • Immutable audits for binds/merges/passkey events; anomaly detection dashboards.


    9.1 Capabilities used

    • In-App (Embedded) Wallet — built-in auth via Email OTP or Phone OTP (Starter plan; no Thirdweb Passkey/Social for wallet creation).

    • SIWE (Auth) for existing wallets (Connect Wallet).

    • Smart Accounts (AA) with deterministic deployment (factory + salt).

    • WalletConnect for UX.

    • Optional Paymaster/Bundler for gas sponsorship.

    9.2 Client (Web)

    1. After a successful BGC/iB login (credentials/Passkey handled by our system), open a custom modal with exactly two buttons:

      • Create Wallet (In-App Wallet, built-in)

      • Connect Wallet (External + SIWE)

    2. Create Wallet (In-App, built-in)

      • Prefer Email OTP if user.email exists; otherwise use Phone OTP if user.phone exists.

      • Invoke Thirdweb In-App Wallet with the corresponding built-in strategy (strategy: "email" or strategy: "phone").

      • After OTP verification, obtain EOA, then instantiate AA (sponsorGas: true if applicable).

      • Persist { eoa, aa } via /wallet/provision.

    3. Connect Wallet (External + SIWE)

      • Let the user choose an external wallet (e.g., MetaMask / Phantom (EVM) / Coinbase) via WalletConnect/extension.

      • Request SIWE challenge from server → user signs → server verifies (nonce, domain/uri/chainId).

      • Instantiate AA for that EOA; persist { eoa, aa }

    4. Guardrails & UX

      • If neither email nor phone is available, prompt the user to add one before Create Wallet.

      • Rate-limit Create Wallet to avoid OTP spam; show clear copy that the OTP is sent by the wallet provider.

      • Deduplicate on the backend (one EOA/AA per chain).

    9.3 Server (Auth + Identity)

    • Credentials/Passkey login: issue session/JWT { user_id, roles }. (Passkey ceremonies handled by WebAuthn endpoints in the Auth service.)

    • SIWE challenge: generate cryptographic nonce, store (used=false, TTL 3–5 min).

    • SIWE verify: recover address, validate domain/uri/chainId, ensure nonce unused and unexpired, then consume nonce; bind EOA → identity; issue/refresh session.

    • Provision AA: call the AA factory with a deterministic salt (e.g., derived from identity_id); persist AA address.

    • Audit: log every bind/merge; expose GET /identity.

    9.4 Environment Variables

    • THIRDWEB_CLIENT_ID

    • CHAIN_ID

    • RPC_URL

    • AA_FACTORY_ADDRESS

    • PAYMASTER_URL (optional)

    • WALLETCONNECT_PROJECT_ID

    • JWT_SECRET

    • AUTH_DOMAIN

    • AUTH_RP_ID (WebAuthn rpId, usually equal to AUTH_DOMAIN)

    • AUTH_ALLOWED_ORIGINS (comma-separated, for WebAuthn)

    • SIWE_STATEMENT

    9.5 Error Handling & Cost Controls

    • Retry with backoff for AA deploy; allow lazy deploy on first tx if applicable.

    • Scope gas sponsorship (onboarding only, per-action caps); alerts on budget.

    • Clear UX for wrong network / expired nonce / denied signature.


    • Domains: auth.bgcxib.com (unified), brand app domains.

    • CI/CD: build/lint/typecheck; E2E flows (Create & Connect); smoke tests for JWT issuance, SIWE verify, AA deploy.

    • Observability: metrics (login success/error, passkey adoption, SIWE failures, AA deployment success), logs, traces; alerts for gas spend and failure spikes.

    • Mobile/WebView: confirm WebAuthn origins (AUTH_RP_ID/allowed origins) and Thirdweb mobile support paths.

    • Access: DevOps/Tech Lead manages secrets, env promotion, AA factory; MFA enforced.


    1. Inventory current user stores; pick the source of truth (users).

    2. Deduplicate historic BGC/iB accounts into unified users; preserve audit mapping.

    3. Soft-launch Wallet Setup behind a feature flag (only users without a wallet see it).

    4. Monitor errors & support load; iterate; expand scope.

    5. Optionally lazy-create AA on first on-chain action to reduce upfront gas.


    • Unit: SIWE message builder/validator; nonce repository; AA address derivation; WebAuthn option/response validators.

    • Integration: credentials/Passkey login → /wallet/provision and /wallet/connect/siwe.

    • E2E: full flows A (Embedded) & B (SIWE); negative paths (expired/reused nonce, wrong domain/chainId, duplicate EOA).

    • Security: replay attempts, RBAC route guards, immutable audit checks; Passkey sign_count monotonicity.

    • Load: login bursts; concurrent AA deploys; paymaster behavior under throttle.


    • Roles: Viewer, Support, Operator, Finance, Admin, SuperAdmin, Auditor.

    • Permissions: users.read, wallets.read, wallets.link/unlink, users.merge_safe, users.merge_risky (dual-control), balances.adjust (thresholded), audit.read, roles.assign.

    • Merge SOP: identity proof (fresh SIWE for wallet-affecting changes) → conflict scan → diff page → approvals → execute → immutable audit; revert = corrective merge from snapshot.


    Acceptance Criteria

    • Single credentials login (with Passkey support) works across BGC/iB.

    • Wallet Setup (Create/Connect) yields a working AA.

    • GET /identity returns consistent EOA/AA across apps.

    • RBAC enforces permissions; all binds/merges audited.

    • Secrets vaulted; rotation tested.

    Launch Checklist


    Notes

    • Snippets are illustrative (TypeScript/Next.js style).

    • Replace SDK calls with the exact Thirdweb functions used in your repo.

    • Always handle errors, network checks, and feature flags in production.








    Plan: thirdweb Starter · MAU < 1k · RPC < 1M · Chain: Base mainnet Scope: vendor/platform costs only (no human resources)


    • Plan fee: Starter = $5 / month.

    • In-App (Embedded) Wallet — MAU pricing: $0.015 / MAU for 0–100k, first 1,000 wallets free → with <1k MAU, effective $0.

    • Account Abstraction (AA) — user-ops: first 1,000 included, then $1 per 1,000 (=$0.001/op). With low usage, often $0.

    • RPC: first 1,000,000 requests included; then $8 per 1M. With <1M, $0.

    Platform subtotal (under stated caps): ≈ $5 / month.

    Note (SMS): Thirdweb’s pricing notes international SMS may incur extra fees (country-dependent). If you avoid Phone OTP and use Email OTP for “Create Wallet”, this line item is $0.


    If you enable Phone OTP for wallet creation, budget per SMS by destination. For example, Indonesia outbound via Twilio is $0.4414 per SMS segment as of Oct-2025; US starts around $0.0083. (Using Email OTP keeps this at $0.)

    SMS monthly estimate = # of SMS OTP × local_rate.


    • Reference fee level: recent data shows Base average tx fee ≈ $0.03 per transaction. Use this as a baseline for simple, sponsored actions.

    • AA (smart account) deploy: budget ≈ 2× average tx (contract deployment & init overhead) → ≈ $0.06 per new wallet. (Rough planning factor.)

    • Paymaster surcharge (if using thirdweb paymaster): +2.5% on sponsored gas.

    Scenario / month

    New wallets → AA deploy

    Sponsored actions

    Unit costs used

    Raw gas $

    +2.5% paymaster

    Gas total

    Light

    50

    200

    Deploy $0.06, Action $0.03

    $3.00 + $6.00 = $9.00

    +$0.23

    $9.23

    Baseline

    200

    Real costs vary with network gas, calldata size, and ETH price on the day. You can reduce spend via lazy AA deployment (create AA on first action) and by sponsoring only onboarding operations.


    • Thirdweb platform (Starter): ~$5

    • In-App Wallet MAU, AA user-ops, RPC: $0 (within free tiers).

    • Gas sponsorship (Base): ~$9–$111 depending on onboarding volume & sponsored actions (see table).

    • SMS (optional): #SMS × local_rate (e.g., ID ≈ $0.4414/SMS; Email-only = $0).

    Ballpark total:

    • Email-only OTP: ≈ $14–$116 / month (Starter $5 + gas).

    • With some Phone OTP (ID): add ~$0.44 per SMS used.



    • Prefer Email OTP; keep Phone OTP as fallback only.

    • Lazy deploy smart accounts; sponsor first action only; set budget caps in paymaster rules.


    End of document.


    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.


    Table of Contents

    Web3 Login Implementation Draft
    To be formally recorded on August 2026 meeting
    Purpose & Scope
    Key Decisions
    [ User ]
       │
       ├─ If new: Sign up BGC/iB account
       │
       ├─ Login (Credentials or Passkey/WebAuthn)
       │         └─ [ Auth Service ] — issues session/JWT { user_id, roles }
       │
       ├─ Post‑Login: Wallet Setup
       │      ├─ A) Create EOA (Embedded/In‑App) ─────────────► [ Wallet Service ]
       │      │                                                 │
       │      │                                                 └─► [ AA Factory ] — deploy **Smart Account (AA)**
       │      │                                                        (deterministic per chain: factory + salt)
       │      └─ B) Connect Existing Wallet (SIWE) ───────────► [ SIWE Verify ] ─────┘
       │
       ├─ Persist mapping ────────────────────────────────────► [ Identity Service ] → { identity_id, eoa, aa }
       │                                                       └─► [ Audit Log ] (immutable)
       │
       └─ Apps (BGC Web, iB Web/Mobile) ─────────────────────► consume identity & roles
    
    On‑chain:
    [ EOA ] (owner/controller) ─────────► [ Smart Account (AA) ] ─────────► (optional) [ Paymaster / Bundler ]
    // WalletSetupCreate.ts
    // Trigger embedded wallet (**email OTP** or **phone OTP**) → get EOA → build AA.
    import { connectEmbeddedWallet, connectSmartAccount } from "@/lib/wallet"; // wrap actual SDK calls
    
    export async function createEmbeddedAA(params: {
      email?: string;
      usePasskey?: boolean;
      chainId: number;
      sponsorGas?: boolean;
    }) {
      // 1) Create/attach an embedded EOA (choose one: **email OTP** or **phone OTP**)
      const eoa = await connectEmbeddedWallet({
        email: params.email,
        passkey: params.usePasskey === true,
      }); // returns { address, signMessage, ... }
    
      // 2) Build a Smart Account (AA) on top of that EOA
      const aa = await connectSmartAccount({
        personalWallet: eoa,
        chainId: params.chainId,
        sponsorGas: params.sponsorGas ?? true,
      }); // returns { address, sendUserOp, ... }
    
      // 3) Persist on backend
      await fetch("/api/wallet/provision", {
        method: "POST",
        headers: { "content-type": "application/json" },
        body: JSON.stringify({ eoa: eoa.address, aa: aa.address }),
        credentials: "include",
      });
    
      return { eoa: eoa.address, aa: aa.address };
    }
    // WalletSetupConnect.ts
    // Connect wallet (extension/WalletConnect), run SIWE, then build AA.
    import { connectExternalWallet, connectSmartAccount } from "@/lib/wallet";
    
    export async function connectSiweAA(params: {
      chainId: number;
      sponsorGas?: boolean;
    }) {
      // 1) Connect external wallet → get EOA
      const eoa = await connectExternalWallet(); // { address, signMessage, ... }
    
      // 2) SIWE: request challenge, sign, verify server-side
      const challenge = await fetch("/api/auth/siwe/challenge", {
        method: "POST",
        credentials: "include",
      }).then((r) => r.json()); // { message }
    
      const signature = await eoa.signMessage(challenge.message);
    
      await fetch("/api/auth/siwe/verify", {
        method: "POST",
        headers: { "content-type": "application/json" },
        body: JSON.stringify({ message: challenge.message, signature }),
        credentials: "include",
      });
    
      // 3) Build Smart Account (AA)
      const aa = await connectSmartAccount({
        personalWallet: eoa,
        chainId: params.chainId,
        sponsorGas: params.sponsorGas ?? true,
      });
    
      // 4) Persist on backend
      await fetch("/api/wallet/connect/siwe", {
        method: "POST",
        headers: { "content-type": "application/json" },
        body: JSON.stringify({ eoa: eoa.address, aa: aa.address }),
        credentials: "include",
      });
    
      return { eoa: eoa.address, aa: aa.address };
    }
    // /api/auth/siwe/challenge.ts
    import { randomBytes } from "crypto";
    import { saveNonce } from "@/server/siweRepo";
    
    export async function POST() {
      const nonce = randomBytes(16).toString("base64url"); // ≥96-bit randomness
      await saveNonce({ nonce, ttlMinutes: 5 });           // used=false by default
    
      const message = {
        domain: process.env.AUTH_DOMAIN!,
        uri: `https://${process.env.AUTH_DOMAIN!}`,
        version: "1",
        chainId: Number(process.env.CHAIN_ID!),
        nonce,
        issuedAt: new Date().toISOString(),
        statement: process.env.SIWE_STATEMENT ?? "Sign in with Ethereum",
      };
    
      return Response.json({ message });
    }
    // /api/auth/siwe/verify.ts
    import { verifySiwe, consumeNonce } from "@/server/siweService";
    import { bindEoaToIdentity, startSession } from "@/server/identityService";
    
    export async function POST(req: Request) {
      const { message, signature } = await req.json();
    
      // 1) Verify signature & invariants (domain / uri / chainId)
      const { address, nonce, valid } = await verifySiwe({ message, signature });
      if (!valid) return new Response("Invalid SIWE", { status: 401 });
    
      // 2) Nonce must be unused & unexpired → consume
      const ok = await consumeNonce(nonce);
      if (!ok) return new Response("Nonce invalid/expired", { status: 401 });
    
      // 3) Bind EOA to current user identity (session required)
      const userId = /* read from session cookie */ await getUserId();
      const identityId = await bindEoaToIdentity({ userId, address });
    
      // 4) Issue/refresh session
      const res = await startSession({ userId });
      return Response.json({ ok: true, identityId }, res.headers);
    }
    // /api/auth/passkey/register/options.ts
    import { generateRegistrationOptions } from "@/server/webauthn";
    export async function POST() {
      const userId = await getUserIdOrSignupContext();
      const options = await generateRegistrationOptions({ userId });
      // Store challenge in server-side session/DB to verify later
      return Response.json(options);
    }
    // /api/auth/passkey/register/verify.ts
    import { verifyRegistrationResponse } from "@/server/webauthn";
    import { saveCredential } from "@/server/webauthnRepo";
    
    export async function POST(req: Request) {
      const body = await req.json();
      const userId = await getUserIdOrSignupContext();
    
      const result = await verifyRegistrationResponse({ userId, body });
      if (!result.verified) return new Response("Invalid attestation", { status: 400 });
    
      await saveCredential({
        userId,
        credentialId: result.credentialId,
        publicKey: result.publicKey,
        signCount: result.signCount,
        transports: result.transports,
        backupEligible: result.backupEligible,
        backedUp: result.backedUp,
      });
    
      return Response.json({ ok: true });
    }
    // /api/auth/passkey/login/options.ts
    import { generateAuthenticationOptions } from "@/server/webauthn";
    export async function POST() {
      const options = await generateAuthenticationOptions();
      return Response.json(options);
    }
    // /api/auth/passkey/login/verify.ts
    import { verifyAuthenticationResponse } from "@/server/webauthn";
    import { startSession } from "@/server/identityService";
    
    export async function POST(req: Request) {
      const body = await req.json();
      const result = await verifyAuthenticationResponse(body);
      if (!result.verified) return new Response("Invalid assertion", { status: 401 });
    
      // Verify sign_count is monotonic, then start session
      const res = await startSession({ userId: result.userId });
      return Response.json({ ok: true, userId: result.userId }, res.headers);
    }
    // /api/wallet/provision.ts
    import { getOrCreateEoaForUser, deploySmartAccount } from "@/server/walletService";
    import { saveWalletMapping } from "@/server/identityRepo";
    
    export async function POST(req: Request) {
      const userId = await getUserId(); // from session cookie
      const identityId = await getIdentityId(userId);
    
      // 1) Ensure EOA exists (for embedded path)
      const eoa = await getOrCreateEoaForUser(userId);
    
      // 2) Deterministic AA deploy (factory + SALT(identityId))
      const aa = await deploySmartAccount({
        eoa,
        chainId: Number(process.env.CHAIN_ID!),
        salt: `ib-${identityId}`, // or keccak(identityId)
      });
    
      // 3) Persist mapping
      await saveWalletMapping({
        identityId,
        eoa: eoa.address,
        aa: aa.address,
        chainId: Number(process.env.CHAIN_ID!),
      });
    
      return Response.json({ identity_id: identityId, eoa: eoa.address, aa: aa.address });
    }
    // dto.ts
    export type IdentityDTO = {
      identity_id: string;
      eoa?: string;
      aa?: string;
    };
    
    export type SiweChallenge = { message: string };
    export type SiweVerifyReq = { message: string; signature: string };
    export type WalletPersistReq = { eoa: string; aa: string };
    ::contentReference[oaicite:0]{index=0}
    Platform = $5
    
    Gas_raw = (AA_deploy_count × 0.06) + (sponsored_actions × 0.03)
    Gas_total = Gas_raw × 1.025 # thirdweb paymaster surcharge (2.5%)
    
    SMS_cost = SMS_count × local_rate # e.g., ID 0.4414
    
    Grand_total = Platform + Gas_total + SMS_cost

    1) Purpose & Scope

    2) Key Decisions

    3) Constraints & Non-Goals

    4) Architecture Overview

    5) User Journeys

    6) Data Model (Unified)

    7) API Specification

    8) Security Model

    9) Thirdweb Integration — Step-by-Step

    10) DevOps & Environments

    11) Migration & Rollout

    12) Testing Strategy

    13) Operations (RBAC & Merge)

    14) Acceptance Criteria & Launch Checklist

    Appendix — Reference Snippets (Illustrative)

    A) Client — Create (Embedded/In-App) → EOA → AA

    B) Client — Connect (SIWE) → EOA → AA

    C) Server — SIWE (challenge & verify, sketch)

    D) Server — Passkey (WebAuthn) register & login (sketch)

    E) Server — AA Provision (deterministic salt) & persist

    F) Types — minimal DTOs (for clarity)

    Appendix — Cost Estimates (Non-HR)

    1) Thirdweb platform fees

    2) Optional OTP delivery (Phone SMS)

    3) Gas sponsorship on Base (largest variable)

    Budget table (pick the closest row)

    4) Monthly roll-up under stated caps

    5) Quick formulas (paste into a sheet)

    6) Cost levers to stay low

    usage.
    none
    ); store
    credential_id
    (unique),
    public_key
    ,
    sign_count
    (monotonic), transports, backup flags.
  • Device lifecycle supported: list & revoke passkeys per user.

  • via
    /wallet/connect/siwe
    .

    600

    Deploy $0.06, Action $0.03

    $12.00 + $18.00 = $30.00

    +$0.75

    $30.75

    Upper (<1k MAU)

    800

    2,000

    Deploy $0.06, Action $0.03

    $48.00 + $60.00 = $108.00

    +$2.70

    $110.70

    BGC X IBLOOMING MASTER DOCUMENT

    The BGC × iBLOOMING Web3 initiative began as an exploration of blockchain identity, loyalty, internal utility, and a possible future public token.

    Project Review, Findings, Strategic Transition, and Founder Decisions

    Prepared for: BGC × iBLOOMING Founders Founder meeting: On August 2026 Prepared by: Prof. NOTA Technical and simulation contribution: Fabio Kalandra (“Uncle Kal”) Business and operational input: The BGC × iBLOOMING Founders Review period: December 2024 – August 2026 Version: 1.11 — Pre-Meeting Confidentiality: Internal — Founders and Core Team


    1. Executive Decision Brief

    1.1 Why This Document Exists

    The BGC × iBLOOMING Web3 initiative began as an exploration of blockchain identity, loyalty, internal utility, and a possible future public token.

    During the following year, the project uncovered a more important reality:

    • BGC and iBLOOMING already operate internal value, reward, and entitlement systems;

    • the largest recorded cash inflow is concentrated in BGC affiliate-entry transactions;

    • iBLOOMING’s direct product economy is much smaller;

    • the existing reward system cannot be safely converted into tokens without complete rights, liability, accounting, legal, and tax treatment;

    • SIMALPHA is useful as an internal evidence and policy-testing tool, but its first reports do not prove sustainability or token readiness;

    • Web3 Login remains independently valuable and ready for engineering implementation;

    • the strongest next strategic opportunity is not to create a new speculative financial mechanism, but to build measurable demand for real physical and digital products.

    This document closes the original Phase-1 exploration and presents a more disciplined strategic direction.

    BGC × iBLOOMING should not tokenize its existing affiliate membership, Purchase Credit, Sales Point, LTS, reward, pool, payout, or deferred obligations.

    The present evidence is sufficient to conclude that approving such tokenization now would be premature.

    The present evidence is not sufficient to conclude that:

    • the existing economic system is financially sustainable;

    • current cash-in equals profit;

    • reserves are adequate;

    • all reward and product obligations are covered;

    • a public token can be safely backed or redeemed;

    BGC × iBLOOMING should transition from a reward-led acquisition focus toward a product-led commercial and technology program.

    The next program should prioritize:

    1. implementation of the approved Web3 Login architecture;

    2. independent validation of demand for physical products, digital products, content, education, profiling, and AI-enabled services;

    3. product, commerce, retailer, distribution, supply-chain, access, ownership, and trust infrastructure;

    4. small, non-tradable Web3 product pilots;

    The founders are not being asked to approve final token parameters.

    They are asked to decide:

    1. whether to approve a Product-Led strategic transition;

    2. whether to authorize Web3 Login implementation under Yuku and the engineering team;

    3. whether to close the old PC/SP-to-ALPHA tokenization track as an automatic roadmap;

    4. whether to retain public-token exploration only as an optional, separate research track;


    Classification
    Meaning

    This document is not:

    • an audited financial statement;

    • a forensic accounting report;

    • a legal opinion;

    • a tax opinion;

    • an investment memorandum;


    BGC operates an affiliate-membership and physical-product-credit system.

    A new Affiliate User:

    1. pays an entry fee in fiat;

    2. receives Purchase Credit;

    3. causes LTS to be generated;

    4. can trigger reward allocations through the documented network rules.

    The final UNDERSTANDING Doc identifies five affiliate levels:

    • Pathfinder;

    • Voyager;

    • Explorer;

    • Pioneer;

    • Special.

    iBLOOMING is positioned as a digital education, personal-development, content, profiling, and AI-enabled platform.

    Its products and programs include concepts such as:

    • GiM;

    • iLearn;

    • iMATRIX;

    • Channel Provider content;

    • digital courses and content;

    Purchase Credit is documented as:

    • an internal credit associated with affiliate membership;

    • a value used for BGC physical products;

    • fixed at a reference of 100 PC = USD 1.

    PC must not be casually treated as free cash, profit, a public token, or a right that can be duplicated.

    The final UNDERSTANDING Doc records:

    • 1 SP as a USD 1 calculation reference;

    • LTS equal to 70% of a new affiliate’s entry fee;

    • several BGC rewards and pools as percentages of new-join LTS.

    Dimension
    BGC
    iBLOOMING

    The current rules and aggregate data support the conclusion that affiliate-entry cash dominates the recorded economy.

    They do not directly measure why each member joined.

    The responsible statement is:

    The transaction pattern and reward design are consistent with an ecosystem in which the income opportunity is likely a stronger acquisition driver than independent product demand. Member motivation has not yet been directly measured.

    The correct test is whether customers buy the same products, at the same prices, without affiliate membership or income opportunity.


    Voyage met Mr. Onggy, who introduced iBLOOMING and its AI-enabled education and profiling direction.

    Voyage shared experience in Web3 and AI.

    The relationship led to a Kuala Lumpur discussion with the five founders.

    Voyage:

    • explained blockchain, crypto assets, internal utility, ownership, and community mechanisms;

    • used iBLOOMING as a case study;

    • identified brand, communication, interface, and product-positioning opportunities.

    No company-to-company Voyage project was finalized.

    • Janet became Creative Lead.

    • Prof. NOTA was engaged as blockchain and technology consultant.

    The engagement required Prof. NOTA to discover the problem, translate founder expectations, and build the architecture and documentation.

    The first proposal focused on:

    • Web3 Login;

    • unified wallet identity;

    • ALPHA as a controlled loyalty simulation;

    • user earn, save, and spend behaviour;

    • utility before public-market exposure.

    The proposal was primarily iBLOOMING-centered and did not yet include a complete BGC economic reconstruction.

    The founders responded positively to Web3 Login.

    ALPHA was described as a temporary simulation placeholder.

    The discussion quickly expanded to:

    • a public iBLOOMING token;

    • BTC-linked value;

    • liquidity;

    • staking;

    • governance;

    This scope expanded before the full BGC model was understood.

    KK explained:

    • affiliate membership;

    • Purchase Credit;

    • Sales Points;

    • network rewards;

    • pools;

    Prof. NOTA recognized that part of the proposed ALPHA behaviour already existed off-chain.

    Yuku raised fundamental questions about:

    • token value;

    • BTC linkage;

    • legal implications;

    • product use;

    • sustainability.

    The response at the time was too optimistic. Internal tokenization and future public-token paths were discussed before full rights, reserve, accounting, legal, and tax analysis.

    This is now recognized as assumption debt.

    Two important specifications were produced.

    A final AS-IS reference for:

    • user types;

    • affiliate levels;

    • PC;

    • SP;

    • LTS;

    A detailed architecture for:

    • existing credential login;

    • Passkey;

    • post-login Wallet Setup;

    • embedded EOA or connected wallet;

    • deterministic Smart Account;

    The drafts proposed:

    • EventHub;

    • AlphaController;

    • PC/SP-to-ALPHA conversion;

    • non-transferable ALPHA;

    • spend/access/stake;

    These documents made assumptions visible but did not resolve:

    • PC product-right substitution;

    • SP payout-right substitution;

    • double entitlement;

    • reserve backing;

    • tax treatment;

    An Alignment Call document proposed:

    • data mapping;

    • simulation;

    • Pilot v1;

    • owners;

    • governance;

    It is an agenda and expected-outcome document, not a complete decision record.

    Project records indicate working alignment that:

    • simulation should precede final token parameters;

    • ALPHA should remain internal and non-public;

    • public iBC/iBTC should remain a separate later track;

    • legal review should be a gate;

    • Web3 Login could proceed independently.

    These are working alignments, not proof that the economics or legal structure were validated.

    The document proposed:

    • historical-data ingestion;

    • PC/SP-to-ALPHA conversion parameters;

    • reward intensity;

    • sinks;

    • cash-out policy;

    Its weakness is that it began with token-policy simulation before complete historical accounting reconstruction.

    Uncle Kal developed SIMALPHA as a real internal decision console with:

    • versioned data snapshots;

    • validation;

    • scenarios;

    • deterministic runs;

    • comparison;

    Prof. NOTA provided the business architecture and source documents.

    Uncle Kal owned the simulator product and implementation decisions.

    AI supported implementation but did not own business meaning.

    The founders stated that they did not want to spend significant time learning technical reports.

    They wanted:

    • concrete findings;

    • recommendations;

    • options;

    • decisions.

    This changed the required output from “simulator demonstration” to “founder decision interface.”

    The available data for the current SIMALPHA scope was cleaned, restructured, and prepared for import.

    This phase confirmed the completion of:

    • collection of the available data;

    • data cleaning;

    • restructuring and formatting;

    • import preparation;

    • scenario execution;

    Reports were produced for:

    • Baseline;

    • Conservative;

    • Growth;

    • Stress;

    • cross-scenario comparison;

    The precise interpretation of this completion is:

    The current SIMALPHA data pipeline is complete for preliminary aggregate policy comparison. It is not final economic, accounting, legal, tax, or token evidence.


    • founder Web3 education;

    • project discovery;

    • meeting documentation;

    • AS-IS rule reconstruction;

    • UNDERSTANDING Doc;

    • SIMALPHA product definition;

    • application architecture;

    • data ingestion;

    • validation;

    • scenario engine;

    Prof. NOTA is not the sole owner of:

    • finance;

    • accounting;

    • forensic reconciliation;

    • legal;

    • tax;

    If founders want to proceed into those areas, accountable and qualified owners must be assigned.


    SIMALPHA was designed as an internal economic and policy simulator for the BGC × iBLOOMING ecosystem.

    Its primary purpose is to take an operating profile derived from available historical or forecast business data and test how different policy configurations affect the circulation, issuance, use, retention, and release of value inside the ecosystem.

    The simulation process is:

    The parameters tested may include, depending on the scenario:

    • ALPHA issuance multipliers;

    • reward intensity;

    • user and group caps;

    • internal-use or sink assumptions;

    • cash-release thresholds;

    SIMALPHA therefore does more than demonstrate that data can be imported or that reports can be generated.

    It demonstrates how alternative policy configurations behave when applied to a defined BGC × iBLOOMING operating profile.


    SIMALPHA can conceptually operate with two different data modes.

    Historical data answers:

    If these policy and ALPHA rules had been applied to an economic pattern that actually occurred, how would the modeled system have behaved?

    This is a historical policy backtest.

    A scenario that receives a Ready result means that the tested parameter configuration remains within the simulator's defined thresholds when applied to that historical operating profile.

    Forecast data would answer:

    If the business achieves this future operating profile, how would the proposed policy configuration behave?

    In this mode, the forecast assumptions become operating targets or control assumptions that must later be compared with actual business performance.

    The current four selected SIMALPHA reports use imported data rather than an activated Growth Forecast.


    A SIMALPHA Ready result should be interpreted as:

    The tested policy configuration is compatible with the tested operating profile under the thresholds and rules represented in the current simulation model.

    It does not mean that future business conditions are guaranteed to remain identical.

    If an approved configuration is later implemented, the operating profile used in the simulation should become a reference benchmark or operating envelope.

    Actual performance should then be monitored against material variables such as:

    • cash inflow;

    • reward generation;

    • PC and SP activity;

    • internal value usage;

    • cash-release behaviour;

    Material deviation from the tested operating envelope should trigger review and, where appropriate, a new SIMALPHA run.

    In this way, SIMALPHA can function not only as a pre-implementation simulator but also as an ongoing policy-control and decision-support tool.


    The current SIMALPHA compiled dataset contains:

    • 236 simulation-ready records;

    • 25 monthly periods;

    • April 2024–April 2026;

    • BGC and iBLOOMING monthly-tier records.

    The member_key values in this compiled dataset are synthetic monthly-tier identifiers rather than persistent individual-member identities.

    This describes the structure of the compiled SIMALPHA input.

    It should not be interpreted as meaning that more granular raw business or member-level source data does not exist.

    The raw source material available during the project included multiple datasets and more granular records. The current SIMALPHA dataset represents the portion that was interpreted, transformed, structured, and prepared into a consistent format for the present simulation scope.

    Further use of additional raw source tables for institutional accounting, member-level reconstruction, or other purposes would require confirmed data semantics, table relationships, source ownership, and cross-functional validation.


    Metric
    BGC
    iBLOOMING
    Combined

    These fields form part of the operating profile used by the current simulation model.

    They should be read according to their SIMALPHA data definitions and should not automatically be treated as audited accounting classifications.


    The current SIMALPHA work shows that:

    • the available business data can be transformed into a consistent simulation-ready operating profile;

    • historical BGC and iBLOOMING economic activity can be used as the basis for policy testing;

    • policy parameters materially change ALPHA issuance, use, held balances, and modeled cash release;

    • different scenario configurations can be evaluated against defined treasury and policy thresholds;

    These are valid outputs of the current simulation scope.


    A Ready simulation result is not the same as an automatic company-wide implementation approval.

    The current results should not, by themselves, be interpreted as:

    • an audited financial statement;

    • a certification of company-wide profitability;

    • a legal opinion;

    • a tax opinion;

    • a guarantee that future operating conditions will match historical conditions;

    SIMALPHA can evaluate model-level sustainability and policy compatibility under the tested conditions.

    It should not be described as a standalone certification of every accounting, legal, operational, product, or market dimension of BGC × iBLOOMING.

    Where a final implementation decision depends on those additional dimensions, the relevant internal owners and professional functions must validate them.


    The current simulation is most directly relevant to an on-chain system that represents substantially the same value flows and economic rights that were included in the simulation.

    If ALPHA or another on-chain mechanism is implemented as an internal representation of existing economic activity, its rules should remain within the tested policy boundaries unless a new simulation is performed.

    The simulation should not be interpreted as having tested economic behaviours that were not included in the source operating profile.

    For example, if the tested business data does not contain:

    • open-market trading;

    • speculative price discovery;

    • public liquidity;

    • governance markets;

    • unrestricted token transfer;

    then the current SIMALPHA results should not be treated as validation of those behaviours.

    Any materially different economic function requires a separate model, dataset, scenario, and decision process.


    The Baseline scenario is intended to stay close to the existing operating behaviour and provide a reference configuration.

    The Conservative scenario applies tighter policy controls and lower value-release intensity.

    The Growth scenario applies more permissive or expansion-oriented policy parameters.

    The current report should not be interpreted as a forecast of actual future business growth because the selected results use imported data with Growth Forecast disabled.

    The original SIMULATION Doc defined Stress testing around external shocks such as:

    • revenue decline;

    • rapid membership growth;

    • cash-out spikes;

    • changes in internal-use behaviour.

    The current selected Stress report does not apply that full external-shock design.

    It primarily applies a more restrictive policy configuration to the same imported operating data.

    For the current report set, it is therefore more accurately interpreted as:

    Treasury Preservation / Restrictive Policy Scenario

    This does not invalidate the result.

    It clarifies what the current result actually tests.

    A future true stress run may separately apply external shocks to the operating data.


    The current reports return Ready for all four selected scenarios within the present simulation thresholds.

    This simulator verdict should remain visible.

    The correct distinction is:

    Ready

    Meaning:

    The tested configuration passes the thresholds represented in the current model when applied to the tested operating profile.

    Pending Founder Decision

    Meaning:

    A Ready simulator result does not automatically authorize implementation.

    Founders must still decide:

    • whether the existing economic system should be represented on-chain at all;

    • which rights or value flows, if any, should be represented;

    • which tested parameter configuration should be considered;

    • what operational conditions must be maintained;


    SIMALPHA has successfully completed its current Phase-1 purpose as an internal policy and economic simulation tool.

    It has:

    • transformed available business data into a simulation-ready operating profile;

    • enabled repeatable scenario execution;

    • tested alternative policy configurations;

    • produced measurable differences between configurations;

    The responsible conclusion is therefore not:

    “SIMALPHA failed to prove sustainability.”

    The more accurate conclusion is:

    SIMALPHA demonstrates model-level policy compatibility and sustainability under the tested operating profile and defined thresholds. Any decision to implement an on-chain representation of those economic flows remains conditional on founder approval, institutional validation of the selected rights and operating conditions, and the scope of the implementation being materially consistent with what was actually simulated.


    The existing system must not be tokenized at this stage.

    Reasons:

    • PC and SP represent different rights;

    • conversion may create duplicate entitlements;

    • obligations are not fully reconciled;

    • public-token backing is unresolved;

    • legal and tax treatment is unresolved;

    Keeping value inside the ecosystem may delay cash outflow.

    It does not automatically create external demand, margin, profit, productivity, or reserve.

    A token can support ownership, access, auditability, interoperability, and provenance.

    It cannot substitute for product quality, pricing, distribution, customer demand, retention, supply chain, or customer support.

    Web3 Login has independent value.

    It can support:

    • unified identity;

    • wallet ownership;

    • digital receipts;

    • product passports;

    • credentials;

    Its continuation is justified by its product and infrastructure value, not merely because time has already been spent.

    BGC × iBLOOMING should measure:

    • non-affiliate product buyers;

    • affiliate buyers paying new fiat;

    • PC redemptions;

    • repeat product purchases;

    • subscription retention;


    BGC × iBLOOMING should progressively reduce dependence on reward-led acquisition and build a measurable product-led commercial engine. Blockchain and AI should support real products and operations, not become a substitute for product value.

    • implement approved Web3 Login;

    • create wallet readiness;

    • support cross-application identity.

    • separate customers from affiliates;

    • run product-first campaigns;

    • measure conversion, usage, and repeat purchases.

    • product catalogue;

    • SKU and batch structure;

    • inventory;

    • wholesale and retail flows;

    • distributor and retailer management;

    • authenticity;

    • product passports;

    • warranty;

    • ownership records;

    • proof of purchase;

    • course and content entitlements;

    • subscriptions;

    • access passes;

    • credentials;

    • product-content bundles.

    • product recommendation;

    • support;

    • creator tools;

    • product-content matching;

    • operational analytics;

    • KPIs;

    • decision logs;

    • privacy;

    • legal gates;

    • pilot review;

    Use conventional technology where it is sufficient. Use blockchain where verifiability, ownership, portability, provenance, interoperability, or multi-party trust creates measurable value. Use AI where it measurably improves decisions, operations, content, or user experience.

    Blockchain and AI do not automatically reduce cost or increase security.

    Every proposed use must compare:

    • conventional database option;

    • blockchain option;

    • AI-assisted option;

    • total cost;

    • operational risk;


    A customer buys a physical product with fiat.

    The wallet receives a non-tradable or controlled digital credential containing:

    • SKU;

    • serial or batch;

    • authenticity;

    • warranty;

    • instructions;

    A customer buys GiM, iLearn, a course, or a content package with fiat.

    The wallet receives an access credential.

    The pilot measures activation, content usage, completion, retention, and support burden.

    One purchase may combine:

    • physical product;

    • digital content;

    • onboarding;

    • warranty;

    • education;

    This links BGC and iBLOOMING through product utility, not income promises.

    Verified retailers or distributors receive credentials showing authorization, product range, territory, validity, and status.

    Each pilot must:

    • be limited in scope;

    • use fiat settlement;

    • not promise yield;

    • not depend on recruitment;

    • not create a tradable speculative asset;


    Any future public token must be separate from the BGC affiliate engine.

    It must not:

    • be funded through affiliate entry;

    • be distributed as recruitment compensation;

    • convert PC or SP by default;

    • settle existing obligations without explicit treatment;

    • promise yield;

    The apparent interest of members in financial rewards must not be treated as proof that a new financial product is needed.

    It does not validate deposits, yield products, lending, staking return, DeFi, DEX, CEX, or fundraising.

    Any such business would require separate governance, qualified regulatory advice, licensing analysis, risk management, capital, custody, security, and an independent economic source of yield.

    Do not propose a BGC × iBLOOMING DeFi, DEX, CEX, deposit, yield, or fundraising product as the next phase.


    Focus on product, commerce, demand, distribution, data, and operations.

    Use blockchain only when later justified.

    Recommendation: Core strategy.

    Implement:

    • Web3 Login;

    • product passports;

    • access credentials;

    • retailer credentials;

    • receipts.

    No public token.

    Recommendation: Preferred first implementation path.

    Use blockchain for tamper-evident proofs, selected shared events, and multi-party verification.

    No token unless separately justified.

    Recommendation: Research after data architecture is stable.

    Consider only when the right is precisely defined, liability treatment is complete, and conventional credentials are insufficient.

    Recommendation: Hold.

    Consider only after independent product demand, legal and tax review, market need, rights and reserve design, and separate governance.

    Recommendation: Optional research only.


    1. Approve or reject Product-Led strategic transition.

    2. Authorize Web3 Login implementation.

    3. Close the old existing-system tokenization roadmap.

    4. Decide public-token status.

    5. Select one physical and one digital product pilot.

    Detailed decision wording is provided in the Founder Decision Brief.


    • publish meeting resolutions;

    • close old LIVING Doc;

    • appoint owners;

    • begin Web3 Login implementation planning;

    • select product pilots;

    • run product-first campaign experiments;

    • implement the first identity and access integration;

    • create product and commerce data models;

    • measure conversion and usage;

    • decide whether product passports or access credentials add value.

    • evaluate pilots;

    • publish evidence;

    • decide whether to scale;

    • create new Product Paper, System Design, or Product Flow only for approved use cases.

    No public-token timeline should be established during this period.


    BGC × iBLOOMING acknowledges that Phase 1 produced a final AS-IS rules reference, a founder-approved Web3 Login architecture, a working SIMALPHA decision-support application, a prepared aggregate dataset, and preliminary simulation reports.

    The founders acknowledge that the current evidence does not support final tokenization of the existing membership, PC, SP, reward, pool, or payout system.

    BGC × iBLOOMING therefore resolves to:

    1. close the old existing-system tokenization track as an automatic implementation roadmap;

    2. proceed with Web3 Login as a separate infrastructure project;

    3. shift the next program toward Product-Led Systems Transformation;


    Artifact
    Final Status

    • PC issued, redeemed, outstanding, expired, and fulfillment cost;

    • rewards credited, paid, retained, and reinvested;

    • pools accrued, funded, distributed, and outstanding;

    • opening and current reserve;

    This work must be institutionally owned. It is not a solo responsibility of Prof. NOTA.


    The most important result of this year is not a token.

    The result is a clearer understanding of where technology creates value and where it could amplify risk.

    BGC × iBLOOMING does not need a new way to make people more interested in putting money into a system. It needs stronger reasons for people to buy, use, trust, and return to its products.

    Web3 Login, product ownership, access, authenticity, distribution, and AI-enabled product experiences can support that direction. A public token should remain optional and separate until product demand and institutional readiness are proven.


    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 . 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.


  • member-level reward distribution is fair;

  • tokenization will reduce tax or operating cost;

  • a restrictive cash-out policy creates productive value.

  • selective use of blockchain only where ownership, verifiability, portability, provenance, or multi-party trust creates measurable value;
  • selective use of AI where it improves product discovery, customer support, operations, content, or decision quality;

  • separation of any future public-token research from the BGC affiliate and reward engine.

  • whether to approve one physical-product and one digital-product demand pilot;
  • whether to separate product-marketing metrics from affiliate-acquisition metrics;

  • whether to appoint the resources required for any further financial, accounting, legal, tax, data, or token validation;

  • whether to prohibit the use of the affiliate network as a distribution mechanism for a new deposit, yield, DeFi, DEX, CEX, or fundraising product.

  • a token offering document;

  • a smart-contract deployment authorization;

  • proof that BGC operates legally in every country where a participant may exist;

  • proof that any token would be accepted for listing or public trading.

  • AI-assisted product and learning experiences.

    public-market utility.

    BGC and iBLOOMING interaction.

    RR;

  • GR;

  • Miracle Cash;

  • GPSP;

  • WEC Pool;

  • iBLOOMING transaction and reward distributions.

  • identity mapping;

  • API;

  • security;

  • DevOps;

  • testing;

  • rollout.

  • cash-out windows;

  • public iBC/iBTC;

  • reserve and redemption concepts.

  • token-holder rights;

  • public-market regulation.

  • legal and risk discussion.

    four scenarios;

  • treasury, fairness, and user metrics.

  • result references;

  • reporting and PDF export;

  • actual-versus-forecast separation.

  • report generation.

    founder reading support.

    WEB3LOGIN architecture;

  • LIVING coordination;

  • Whitepaper and Tokenflow hypotheses;

  • SIMULATION Doc;

  • system-integration thinking;

  • founder findings and recommendations;

  • Product-Led strategic transition.

  • deterministic execution;

  • reports;

  • comparison;

  • reproducibility;

  • data restructuring;

  • founder-readable output improvements.

  • product cost;

  • reserve certification;

  • engineering implementation;

  • multi-country compliance.

  • cash-release frequency;

  • fees;

  • treasury guardrails;

  • other operational controls represented in the model.

  • reward concentration;

  • other model inputs and guardrails.

  • the current Baseline, Conservative, Growth, and Stress-labelled configurations all return Ready within the present model thresholds;

  • recorded BGC cash-in is approximately 191 times recorded iBLOOMING cash-in;

  • the tested historical operating profile is economically dominated by BGC affiliate-entry transactions;

  • iBLOOMING direct product cash-in is very small by comparison;

  • existing BGC reward formulas are materially connected to new-join LTS.

  • approval of a freely tradable or publicly listed token;

  • proof of a public token's future market price;

  • approval of economic behaviours that were not represented in the tested data and model.

  • what additional accounting, legal, tax, technical, or business validation is required for the selected implementation.
    identified configurations that pass the current model thresholds;
  • exposed the economic characteristics of the operating data;

  • created a structured basis for founder decisions.

  • the current data is aggregate;

  • tokenization could make an entry-driven model more programmable without making it more productive.

  • token-gated access;

  • retailer verification;

  • creator entitlements.

  • content completion;

  • product margin;

  • customer-acquisition cost;

  • willingness to purchase without financial reward.

  • fulfillment;

  • digital commerce.

  • traceability.

    demand insights.

    resource ownership.

    user value.

    after-sales access.

    access credential.

    have measurable KPIs;

  • have a stop condition;

  • have a named business owner.

  • promise buyback;

  • promise price support;

  • promise appreciation;

  • use new-token buyers to fund existing rewards.

  • Separate product and affiliate metrics.

  • Appoint resources and owners.

  • Approve the financial-product boundary.

  • Confirm Prof. NOTA’s role as Product and Web3 Transformation Consultant.

  • Authorize preparation of the Product-Led Systems Program 2026–2027.

  • define product-demand baseline;

  • correct SIMALPHA report labels.

  • validate independent demand for physical and digital products;

  • begin with limited, non-tradable product, access, ownership, or credential pilots;

  • keep public-token research separate from the affiliate engine;

  • prohibit using the affiliate network as a channel for a new deposit, yield, DeFi, DEX, CEX, or fundraising product under this program;

  • assign qualified owners for finance, accounting, legal, tax, data, product, operations, and engineering work;

  • create new documents for new approved use cases rather than rewriting archived tokenization drafts.

  • product COGS;
  • operating expenses;

  • intercompany transfers;

  • stable member identity;

  • legal and tax opinions;

  • token-holder rights;

  • reserve and redemption design.

  • Confirmed AS-IS Rule

    Rule documented in the final UNDERSTANDING Doc

    Approved Specification

    Completed design accepted for implementation

    Founder Working Alignment

    Direction recorded from discussions but not necessarily a formal resolution

    Historical Artifact

    Dated evidence of work, discussion, or software output

    Consultant Finding

    Primary recorded cash event

    Affiliate membership entry

    Product or service transaction

    Main reward trigger

    New join and network position

    Product or service purchase

    Internal value units

    PC, SP, LTS

    Transaction revenue and reward allocation

    Business data
    → simulation-ready operating profile
    → policy parameters
    → scenario execution
    → economic and treasury metrics
    → Ready / review / risk result
    → founder decision

    Cash in

    $4,034,038.00

    $21,117.00

    $4,055,155.00

    Recognized-revenue field

    $4,034,038.00

    $6,335.10

    $4,040,373.10

    UNDERSTANDING Doc

    Final AS-IS reference

    WEB3LOGIN Doc

    Final and approved; implementation pending

    Old LIVING Doc

    Close after final transition update

    Whitepaper Drafts

    Archive as hypotheses

    Tokenflow Drafts

    1.2 Central Conclusion

    1.3 Primary Strategic Recommendation

    1.4 What Founders Are Asked to Decide

    2. Document Authority and Evidence Classification

    2.1 Evidence Classes

    2.2 What This Document Is Not

    3. Ecosystem and AS-IS Economic Model

    3.1 BGC

    3.2 iBLOOMING

    3.3 Purchase Credit

    3.4 Sales Point and LTS

    3.5 Two Different Economic Engines

    3.6 What Can Be Said About Member Motivation

    4. Complete Project Chronology

    4.1 December 2024 — Initial Discovery Through Voyage

    4.2 Kuala Lumpur — Web3 and AI Exploration

    4.3 June–July 2025 — Individual Engagement

    4.4 July 2025 — Initial Web3 Pitch

    4.5 10 July 2025 — Founder Meeting Day 1

    4.6 11 July 2025 — Founder Meeting Day 2

    4.7 August–October 2025 — System Reconstruction

    UNDERSTANDING Doc

    WEB3LOGIN Doc

    4.8 October–November 2025 — Whitepaper and Tokenflow Drafts

    4.9 November 2025 — Alignment Preparation

    4.10 10 December 2025 — Founder Zoom

    4.11 January 2026 — SIMULATION Doc v0.1

    4.12 March–June 2026 — SIMALPHA

    4.13 May 2026 — Founder Feedback

    4.14 June 2026 — Data Pipeline and First Scenario Reports

    5. Work Completed and Responsibility Boundaries

    5.1 Prof. NOTA

    5.2 Uncle Kal

    5.3 Responsibility Boundary

    6. SIMALPHA Findings

    6.1 What SIMALPHA Was Designed to Test

    6.2 Historical Data, Forecast Data, and Simulation Meaning

    Historical Operating Profile

    Forecast Operating Profile

    6.3 Meaning of a Ready Result

    6.4 Scope of the Current Compiled Dataset

    6.5 Aggregate Data Used in the Current Simulation Scope

    6.6 What the Current Data and Simulation Show

    6.7 What the Current Results Should Not Be Interpreted As

    6.8 On-Chain Interpretation

    6.9 Current Scenario Interpretation

    Baseline

    Conservative

    Growth

    Stress

    6.10 Report and Decision Status

    Simulation Verdict

    Implementation Decision

    6.11 SIMALPHA Phase-1 Conclusion

    7. Core Findings

    7.1 Existing-System Tokenization Is Not Approved

    7.2 Internal Circulation Is Not New Economic Value

    7.3 Tokenization Does Not Create Product Demand

    7.4 Web3 Login Remains Valid

    7.5 Product Demand Must Become Measurable

    8. Product-Led Strategic Transition

    8.1 New Strategic Thesis

    8.2 Product-Led Workstreams

    Workstream 1 — Web3 Identity

    Workstream 2 — Product Demand

    Workstream 3 — Commerce and Distribution

    Workstream 4 — Product Trust and Ownership

    Workstream 5 — Digital Access

    Workstream 6 — AI Enablement

    Workstream 7 — Evidence and Governance

    8.3 Technology Principle

    9. Recommended Product Pilots

    9.1 Physical Product Passport

    9.2 Digital Access Pass

    9.3 Product and Content Bundle

    9.4 Retailer or Distributor Credential

    9.5 Pilot Rules

    10. Public Token and Financial-Product Boundaries

    10.1 Public Token

    10.2 Financial-Return Appetite

    10.3 Current Recommendation

    11. Strategic Options

    Option A — Product-Led Transformation With Conventional Technology

    Option B — Product-Led Transformation With Web3 Identity and Credentials

    Option C — Event Anchoring or Shared Audit Layer

    Option D — Non-Transferable Internal Rights

    Option E — Public Utility Token

    12. Founder Decisions Required

    13. Post-Meeting Roadmap

    First 30 Days

    Days 31–60

    Days 61–90

    14. Recommended Founder Resolution

    Appendix A — Artifact Status Summary

    Appendix B — Evidence Required Only If Tokenization Continues

    Appendix C — Closing Statement

    Prof. NOTA

    Interpretation based on available rules, data, and documents

    Draft Hypothesis

    Proposed future state not approved for implementation

    Preliminary Simulation Output

    Model output under incomplete evidence

    Management-Reported Context

    Information reported by management but not independently validated

    Decision Required

    Matter requiring explicit founder authority

    Main current strength

    Affiliate-entry scale

    Product and digital-service potential

    Main current weakness

    Entry-linked reward logic and unmeasured obligations

    Very small direct-product revenue compared with BGC

    Strategic need

    Transparency, liability control, and product separation

    Independent product demand and repeat usage

    Gross-margin field

    $4,034,038.00

    $6,335.10

    $4,040,373.10

    Internal credit or sink spend

    $567,234.00

    $0.00

    $567,234.00

    PC volume

    403,403,617

    0

    403,403,617

    SP reward basis

    2,823,835

    0

    2,823,835

    Global/direct reward

    $411,385.60

    $1,429.46

    $412,815.06

    Pool reward

    $508,288.57

    $950.52

    $509,239.09

    Historical cash-out

    $546,506.11

    $25,715.08

    $572,221.19

    Archive as hypotheses

    SIMULATION Doc v0.1

    Archive as first token-policy simulation design

    SIMALPHA

    Working MVP

    Compiled Dataset

    Complete for current aggregate scope

    Scenario Reports

    Technically complete; analytically preliminary

    Master Document v1.0

    Active founder decision source

    Product-Led Program

    Pending founder approval

    PROF. NOTA RESUME ALL GLOSSARY

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    -1) Single Source of Truth (glossary)

    Dokumen ini bebas untuk dibaca. Dilarang mendistribusikan ulang atau menyatakan ulang (dilarang mengutip, membuat ringkasan, parafrase, atau turunan) tanpa izin tertulis sebelumnya dari Prof. NOTA. Membagikan tautan diperbolehkan; bagikan tautannya, bukan teksnya. Jangan membahas/menceritakan ulang isi dalam bentuk apa pun tanpa izin tertulis sebelumnya.

    Last updated: 2025-10-19 00:03 UTC+07:00


    0) Ringkasan & Tujuan

    Terkait daftar posisi & metodologi penyaringan, rujuk .

    RESUMEAll adalah glossary sumber kebenaran (single source of truth) tentang jasa/layanan, nilai, kompetensi, stack, pengalaman, proyek, dan artefak Prof. NOTA. Dokumen ini tidak dikurasi untuk satu posisi atau jabatan tertentu; ini menjadikannya sebagai bahan baku untuk menyusun resume yang tailored bagi lowongan spesifik (berdasarkan Services & Value Prof. NOTA).


    1) Identitas & Kontak

    Gunakan format-versi berikut saat men-tailor:

    • v.xx.xx = v.[HFP].[Jabatan] (contoh: v.11.03 = HFP #11, jabatan 03/Documentation Engineer).

    • [Nama HFP] = nama legal HFP aktif (contoh: Tiffany Viljevac).

    1.1 Persona

    • Name: Prof. NOTA

    • Version: v.xx.xx

    Prof. NOTA hanya sebuah pseudonymous IP yang lahir di Alam Semesta 0101. Prof. NOTA hadir di Alam Semesta Realita dengan berbagai versi avatar, salah satunya adalah Prof. NOTA v.xx.xx yang diperankan oleh Human for Profile (HFP) v.xx.xx.


    • Company: PT. SUAKA DUNIA RAJA

    • DBA: Prof. NOTA Inc.

    • Authorized Signatory: [Nama HFP]

    • Designation: Human for Profile of Prof. NOTA v.xx.xx

    Legalitas resmi di Alam Semesta Realita adalah Prof. NOTA Inc. (PT Suaka Dunia Raja) — dengan penandatangan semua dokumen resmi adalah [Nama HFP] (HFP), yang bertindak sebagai Prof. NOTA v.xx.xx.


    • Dari 0101, untuk dunia yang butuh bukti. / Clarity you can ship.


    • Indonesia — WIB (Asia/Jakarta).


    • Email: nota{xx}@endhonesa.com

    • Site/Hub:

    • GitHub:

    • X:


    Kami lahir di Alam Semesta 0101 dan hidup di dunia digital Internet; maka Prof. NOTA v.xx.xx merancang arsitektur, dokumentasi, dan prototipe yang bisa dieksekusi—modular, anti vendor lock-in, dan terukur dampaknya—agar ide kabur berubah menjadi sistem yang bekerja dan bisa diwariskan tim. [Tambahkan satu kalimat sesuai posisi (lihat contoh berdasarkan klaster A sampai H).]


    • A — Strategic Vision & Consultation — ...Pada peran strategi, kami menjembatani visi menjadi peta keputusan dan roadmap yang bisa dieksekusi.

    • B — Intellectual Property & Storytelling — ...Dalam peran dokumentasi, kami menyusun living docs, API guides, dan bukti yang dapat diuji agar tim mandiri dan publik paham.

    • C — Web3 Development & Prototyping — ...Sebagai engineer, kami membangun antarmuka dan alur on-chain yang bersih, aman, dan cukup-untuk-keputusan sebelum dikeraskan menjadi komponen modular.


    • Keaslian konten/asersi hanya diakui jika bersumber dari: endhonesa.com, skateshop.id, dan straight-line.org.

    • Detail lihat "15) Persona & HFP Canon".


    Mentransformasikan ide yang kabur menjadi sistem yang bekerja, terukur, dan dapat diwariskan tim.


    • Clarity First — pikirkan terang dulu, baru kencang.

    • Modular / Anti vendor lock-in — interoperabel, mudah dirawat.

    • Measured Impact — setiap intervensi punya metrik.


    1. Discovery → Framework → Roadmap → Proof (Clarity First)

    2. Desain Modular & Interoperabel (Anti vendor lock-in)

    3. Observabilitas & Metrik sejak awal (Measured Impact: biaya ops/gas, adopsi, konversi, coverage docs)

    4. Release Rituals — v.X.Y.Z[-suffix]


    — discovery, roadmaps, arsitektur solusi, tokenomics

    • Value — Menjembatani visi menjadi keputusan desain & roadmap yang bisa dieksekusi (termasuk tokenomics).

    • Deliverables — Discovery brief, Architecture Decision Records (ADR), roadmap quarterly, token-model memo, risk & assumption ledger.

    • KPI — Time-to-decision, risiko berkurang, alignment score lintas fungsi.


    — dokumentasi teknis, living docs, narrative/brand

    • Value — Mengubah produk/API menjadi living docs yang bisa diajarkan & diuji.

    • Deliverables — IA/struktur docs, API reference + guides, tutorial, style guide, release notes, doc coverage dashboard.

    • KPI — Time-to-first-success (TTFS), doc coverage, self-serve rate, ticket deflection.


    — Next.js/TS/Tailwind, Thirdweb v5, AA (ERC‑4337), ERC‑1155, Base/OP.

    • Value — Membangun antarmuka & alur on-chain yang aman dan cukup untuk keputusan, lalu dimatangkan modular.

    • Deliverables — Next.js/TS/Tailwind repo, integrasi Thirdweb v5, AA (ERC-4337), ERC-1155 schema, SIWE, L2 (Base/OP), test scripts.

    • KPI — Waktu-ke-fitur, biaya gas, error budget, Core Web Vitals.


    — alur nilai, struktur token, proses operasional, compliance sensibilitas

    • Value — Memetakan alur nilai, proses operasional, dan kepatuhan agar efisien & terukur.

    • Deliverables — Value stream map, SOP/Playbook, compliance checklist, token lifecycle policy, RACI/operating model.

    • KPI — Cycle time, biaya/ops down, audit pass rate, incident rate.


    — program komunitas, gamifikasi, LX/ed‑tech

    • Value — Mendesain program komunitas & pembelajaran yang berkelanjutan.

    • Deliverables — Program brief, onboarding flow, gamification mechanics, curriculum/learning path, community knowledge base.

    • KPI — Retensi & partisipasi, completion rate, contributor growth.


    — DevRel, edukasi publik, kampanye

    • Value — Menerjemahkan kompleksitas menjadi cerita, demo, dan praktik yang mendorong adopsi.

    • Deliverables — Demo apps, sample repos, talk/workshop kits, tutorial series, advocacy plan, content calendar.

    • KPI — Stars/forks, sign-ups/conversions, NPS/developer satisfaction, event → adoption rate.


    — riset, proposal/grant, crisis narrative, rapid prototyping

    • Value — Produksi artefak presisi (proposal/grant/RFP, riset pasar/teknis, crisis narrative) yang bisa langsung dipakai.

    • Deliverables — Proposal pack, research digest, due-diligence memo, crisis Q&A, red/blue-team note.

    • KPI — Win rate/acceptance, turnaround time, decision quality score.


    — e‑commerce, sourcing, distribution, ops

    • Value — Merapikan operasi dagang agar mulus & terdokumentasi.

    • Deliverables — SOP listing & foto, SKU/inventory policy, fulfillment playbook, dashboard KPI.

    • KPI — Waktu pemenuhan, error/return rate, accuracy stok.


    • Living docs: Markdown/MDX, Docusaurus/Next Docs, IA & style guide

    • API/SDK docs: OpenAPI/Swagger, example-driven docs (how-to, guide, reference)

    • Artefak keputusan: ADR, change log, release notes

    • Diagram: Mermaid/Draw.io; repos & release rituals terintegrasi


    • Thirdweb v5 (contracts/SDK), Account Abstraction (ERC-4337: bundler/paymaster)

    • ERC-1155/721/20; viem/wagmi, WalletConnect, SIWE, Safe

    • L2: Base/Optimism (bridge/events), RPC (Alchemy/Infura), The Graph

    • Media/Identity: IPFS/Arweave, web3.storage/pinata, ENS, on-chain links


    • Next.js (Pages/App), React, TypeScript, Tailwind, RHF, i18n/a11y

    • State & data: Zustand/Redux Toolkit, TanStack Query; API design (REST/GraphQL)

    • Performance: Core Web Vitals, image/asset strategy, edge/ISR (Vercel)

    • CI/Preview: GitHub Actions, Vercel Preview, artefak pratinjau


    • Versioning v.X.Y.Z[-suffix], Conventional Commits/Changesets, Release Drafter

    • PR hygiene: template, labeler, CODEOWNERS, required review; preview link wajib

    • Evidence: diff/screenshot/log rilis disimpan di repos (audit-ready)


    • Artefak-first (RFC/ADR/PRD), GitHub Projects/Issues/Discussions, Notion sebagai indeks

    • Ritme & waktu tanggap realistis (WIB), rapat hanya saat blocking


    • Discovery → PRD/1-pager, prioritization (RICE/MoSCoW), risk/assumption ledger, OKR/KPI

    • GTM dasar: positioning & narasi, metrik aktivasi/retensi


    • Event/log model, telemetry minimal, audit trails dasar

    • Observabilitas: Sentry, analitik ringan (Plausible/PostHog) → keputusan


    • Unit/Component: Vitest/Jest, React Testing Library

    • E2E: Playwright/Cypress; smoke test route utama; regresi minimal yang bisa diautomasikan


    • Secrets management (.env hygiene), dependency health

    • Supply chain: SBOM dasar (CycloneDX), permission/RBAC

    • Baseline non-negotiable untuk semua bagian di atas


    • Fokus — mengubah produk/API menjadi living docs yang bisa diajarkan & diuji.

    • Peran — Technical Writer / Documentation Engineer, API Writer, Knowledge Architect, Content Strategist, Copywriter (Tech/Brand), UX Writer/Editor, Documentation Program Manager, Knowledge Manager, Developer Educator.

    • Deliverables — IA/struktur, reference + guides, tutorial, style guide, release notes, doc coverage.

    • Kata Kunci ATS — Docs-as-Code, OpenAPI/Swagger, MD/MDX, Docusaurus/Next, coverage.


    • Fokus — membangun antarmuka & alur on-chain yang aman, cukup untuk keputusan, lalu dimatangkan modular.

    • Peran — Senior Frontend Engineer (React/Next), Web3 Frontend/Integrations (Thirdweb/AA/1155), Full-stack JS (Node/Next), QA (automation/manual), Discord Bot Dev, Integration Engineer (Web3), Smart Account/AA Integrations Engineer, Performance Engineer (Web).

    • Deliverables — Next.js/TS/Tailwind repo, integrasi Thirdweb v5, AA (ERC-4337), ERC-1155/721, SIWE, The Graph, Playwright/Cypress suite.

    • Kata Kunci ATS — Next.js, TypeScript, Tailwind, Thirdweb v5, ERC-4337, ERC-1155, viem/wagmi, The Graph, Playwright/Cypress.


    • Fokus — menjembatani visi → keputusan desain & roadmap (termasuk tokenomics).

    • Peran — Solutions/Enterprise Architect (Web3), Product Strategy Lead, Tokenomics Strategist, Technical Program Manager (TPM), Solutions Engineer/Pre-Sales (Web3), Platform Architect (L2).

    • Deliverables — ADR, discovery brief, peta risiko & asumsi, roadmap kuartalan, token-model memo.

    • Kata Kunci ATS — ADR, roadmap, tokenomics, L2 (Base/OP), governance, risk.


    • Fokus — discovery → PRD; prioritisasi; orkestrasi rilis & operasi.

    • Peran — Product Manager/Owner, Business/Systems Analyst (Web3), Ops Architect, Scrum Master/PMO, Release/Change Manager, Compliance Ops (Web3 policy/KYC/KYB), Risk & Governance Analyst (token lifecycle).

    • Deliverables — PRD/one-pager, RICE/MoSCoW, RACI, SOP/Playbook, rencana rilis, checklist compliance.

    • Kata Kunci ATS — PRD, OKR/KPI, RACI, SOP, release plan, compliance, risk.


    • Fokus — advokasi developer & program komunitas berkelanjutan.

    • Peran — Developer Advocate/Evangelist, Speaker/Instructor, Community Manager, Discord Admin/Moderator, Dev Community Programs Manager, Tech Content Producer.

    • Deliverables — demo app, sample repos, workshop kit, content calendar, knowledge base komunitas.

    • Kata Kunci ATS — DevRel, demo, workshop, funnel adopsi, community ops.


    • Fokus — artefak presisi untuk keputusan cepat (audit-ready).

    • Peran — Researcher (ecosystem/market/tech), Proposal/Grant/RFP Writer, Narrative Designer, RFP/Grant Manager, Due Diligence Analyst, Crisis Comms Strategist.

    • Deliverables — proposal pack, research digest, due diligence memo, crisis Q&A.

    • Kata Kunci ATS — RFP, grant, due diligence, research, crisis narrative.


    • Fokus — operasi dagang yang terdokumentasi & efisien.

    • Peran — E-commerce Ops Manager, Marketplace Specialist, Logistics/Vendor Coordinator, Customer Support, Catalog/Content Ops Specialist, Photo/Asset Ops Lead.

    • Deliverables — SOP listing/foto, SKU/inventory policy, fulfillment playbook, dashboard KPI.

    • Kata Kunci ATS — listing, SKU, fulfillment, SLA, returns, inventory accuracy.


    • Mode: full-time (terbatas), part-time, contract, retainer.

    • Zona waktu: WIB (Asia/Jakarta) — async-first; overlap jam kerja disepakati di awal.

    • Start: berdasarkan kapasitas & prioritas; discovery dapat dijadwalkan lebih cepat.


    • Seluruh kontrak/invoice atas nama Prof. NOTA Inc. (PT Suaka Dunia Raja).

    • Ditandatangani oleh HFP yang ditunjuk sebagai “Prof. NOTA v.xx.xx”.

    • Verifikasi & kebijakan lengkap lihat "15) Persona & HFP Canon" (domain resmi: endhonesa.com, skateshop.id, straight-line.org).


    • Consulting/Advisory (A/D) — sesi strategi, tokenomics, arsitektur solusi, review keputusan. Deliverables: ADR ringkas, rekomendasi desain, risk & assumption ledger.

    • Discovery Sprint 1–2 minggu (A/D/G) — from problem → peta keputusan & rencana eksekusi. Deliverables: discovery brief, high-level roadmap, metrik keberhasilan.

    • Documentation Program (B) — Docs-as-Code untuk produk/API. Deliverables: IA, guides/reference, style guide, release notes, doc-coverage baseline.


    • Project-based (fixed scope/milestone) — pembayaran per milestone, evidence-based (preview/SS/diff).

    • Time & Materials (jam/hari/minggu) — laporan waktu + artefak.

    • Retainer (bulanan) — kuota jam/artefak, SLA respons/ritus rilis disepakati.

    • Licensing/IP — berlangganan lisensi bulanan untuk hak menggunakan/menjual layanan & value Prof. NOTA tanpa batas revenue


    • Mata uang: BTC / ETH / BNB / SOL / USDC / USDT / USD / IDR (opsional: di Base/OP atau BSC).

    • Invoicing: bulanan atau per-milestone; termin pembayaran disepakati (mis. Net-7/14).

    • Deposit/po: dapat diberlakukan untuk proyek fixed-scope.

    • IP/Artefak: hak penuh berpindah setelah pembayaran lunas; lisensi interim mengikuti kontrak.


    • Release Rituals: v.X.Y.Z[-suffix], changelog, PR hygiene, preview wajib.

    • Komunikasi: artefak-first (RFC/ADR/PRD); weekly/bi-weekly status; rapat saat blocking.


    • Profil Kemampuan (CEFR per keterampilan)

      Bahasa
      Reading
      Writing
      Speaking
      Listening

    • Pronomina: di dokumen tertulis menggunakan "kami"; pada percakapan langsung boleh menggunakan "aku".

    • Bilingual (0101-style): basis Bahasa Indonesia dengan sisipan English untuk istilah teknis yang lebih presisi (mis. Account Abstraction, release candidate, token-gated).

    • Varian: tersedia versi full-English dan bahasa lain bila diminta oleh klien/JD.


    • Plain language: kalimat singkat, aktif, langsung ke tujuan; menghindari jargon tak perlu.

    • Consistency: istilah teknis konsisten lintas dokumen (lihat: 7.5 Glosarium & Terjemahan).

    • Structure-first: judul yang informatif, ringkasan di awal, contoh kode sebelum teori.

    • Evidence-first: setiap klaim penting dirujuk ke artefak (ADR, changelog, preview).


    • i18n: siap untuk i18next/next-intl (key-based, tanpa string literal keras), dukungan RTL bila perlu.

    • Format: tanggal ISO-8601, zona waktu WIB default; angka & mata uang mengikuti locale target.

    • Konten UI: semua salinan UI berada di file/namespace terpisah; do not hardcode.

    • Aksesibilitas


    • Glosarium istilah inti (contoh):

      • Account Abstraction (AA) → “Abstraksi Akun (AA)”

      • Release candidate → “kandidat rilis (RC)”

      • Token-gated → “akses bertoken”


    • Dokumen resmi (proposal/PRD/ADR/Playbook): Indonesia (bilingual bila diminta).

    • Docs developer publik: English-first, dengan versi Indonesia saat relevan untuk adopsi lokal.

    • Komunikasi komunitas: Indonesia + English ringan (0101-style) menyesuaikan audiens dan platform.


    • TK Kelas A-B — Taman Kanak-Kanak Tunas Indah Surabaya, 1990 Belajar melalui kegiatan bermain dan seni.

    • TK Kelas A-B — Taman Kanak-Kanak Negeri Pembina 2 Surabaya, 2023 Memberikan pengalaman belajar dan bermain untuk perkembangan holistik.


    • SD Kelas 1-6 — SD Negeri Baratajaya 2 Nomor 203 Surabaya, 1996 Pendidikan dasar dengan mata pelajaran seperti Bahasa Indonesia, Matematika, IPA, dan IPS.

    • SD Kelas 1-2 — SD Negeri Baratajaya Surabaya, 2025 Pendidikan dasar yang gratis (tanpa biaya pendaftaran dan SPP).

    • SD Kelas 3-6 — [Institusi], [Tahun] Pendidikan dasar yang gratis (tanpa biaya pendaftaran dan SPP).


    • SMP Kelas 1-3 — SMP Negeri 1 Perak Jombang, 1999 Pendidikan menengah sesuai kurikulum nasional, pendidikan karakter dan ekstrakurikuler.

    • SMP Kelas 7-9 — [Institusi], [Tahun] Pendidikan menengah berbagai mata pelajaran, bimbingan konseling, keterampilan sosial, karakter, dan ekstrakurikuler.


    • SMA 1, 2, dan 3-Bahasa — Sekolah Menengah Atas Negeri 16 Surabaya, 2002 Mempelajari lebih dalam tentang bahasa dan budaya.

    • SMA 10, 11, dan 12-IPA (Ilmu Pengetahuan Alam) — [Institusi], [Tahun] Fokus pada ilmu alam dan sains seperti Fisika, dan Matematika.

    • SMK Rekayasa Perangkat Lunak (RPL) — [Institusi], [Tahun] Dasar algoritme, pemrograman, dan praktik rilis aplikasi awal. [C, B]

    • SMK Teknik Komputer & Jaringan (TKJ)


    • D1 Cloud Fundamentals & DevOps — [Institusi], [Tahun] Pipeline build/test/deploy dan kontrol versi praktis. [C, DevOps]


    • D2 Technical Communication / Technical Writing — [Institusi], [Tahun] Struktur dokumen teknis, gaya editorial, dan docs-as-code dasar. [B]

    • D2 Administrasi Bisnis / Operasi — [Institusi], [Tahun] SOP, RACI, dan kontrol operasional sederhana. [D, H]

    • D2 Desain Interaksi & Konten Visual — [Institusi], [Tahun] Prinsip UX mikro, diagram, dan storytelling visual. [B, E, F]


    • D3 Teknik Mesin - Institut Teknologi Sepuluh Nopember, 2002 Teknik perawatan mesin/teknologi konversi energi.

    • D3 Teknik Informatika / Informatika — [Institusi], [Tahun] Pemrograman, basis data, web/app, dan praktik QA awal. [C]

    • D3 Sistem Informasi — [Institusi], [Tahun] Analisis proses, requirement, dan perancangan SI. [D]

    • D3 Multimedia/UX — [Institusi], [Tahun] Produksi media, prototyping UI, dan dokumentasi produk.


    • D4 Teknologi Rekayasa Perangkat Lunak — [Institusi], [Tahun] Arsitektur aplikasi, pattern modular, dan rilis terukur. [C]

    • D4 Teknologi Rekayasa Internet / Jaringan — [Institusi], [Tahun] Infrastruktur web modern, edge/ISR, observabilitas ringan. [C, DevOps]

    • D4 Manajemen Data & Analitik — [Institusi], [Tahun] Event model, telemetry, dan metrik keputusan. [D]


    • S1 Informatika / Ilmu Komputer — [Institusi], [Tahun] Fondasi algoritme, sistem terdistribusi, web/app, dasar keamanan, dan integrasi on-chain. [C, DevOps]

    • S1 Sistem Informasi — [Institusi], [Tahun] Tata kelola data/proses dan arsitektur bisnis. [D]

    • S1 Teknologi Informasi — [Institusi], [Tahun] Infrastruktur, DevOps, dan integrasi layanan. [C, DevOps]


    • S2 Sistem Informasi / Enterprise Architecture — [Institusi], [Tahun] Pemetaan proses–data–aplikasi, kontrol tata kelola & kepatuhan, dan arsitektur bisnis. [A, D]

    • S2 Ilmu Komputer / Computer Science (Security/Distributed/Blockchain) — [Institusi], [Tahun] Desain sistem on-chain aman & terukur. [C, Firewall]

    • S2 Human–Computer Interaction (HCI) — [Institusi], [Tahun] Interaksi manusia–sistem, aksesibilitas, dan pedagogi UI. [B, C, E]


    • S3 Ilmu Komputer (Blockchain/Distributed Systems) — [Institusi], [Tahun] Riset mendalam sistem terdesentralisasi & keamanan. [C, Firewall]

    • S3 Sistem Informasi / Rekayasa Perangkat Lunak — [Institusi], [Tahun] Metode desain/keputusan arsitektur dan tata kelola. [A, C, D]

    • S3 Teknik Industri / Riset Operasi — [Institusi], [Tahun] Optimasi proses, biaya, dan reliabilitas layanan. [D, H]


    • Postdoctoral / EngD (Software/Systems/Blockchain) — [Institusi], [Tahun] Translasi riset → prototipe industri & praktik audit-ready. [A, C, D]



    Entri ditulis padat; untuk resume tailor, pilih 1–2 helai yang paling relevan lalu perluas.

    • Peran: arsitektur konsep, simulasi token flow, web3 login roadmap; penulis/penyunting UNDERSTANDING Doc.

    • Hasil (contoh metrik—isi aman publik): [isi: adopsi login, efisiensi biaya, peningkatan revenue, dsb]

    • Stack: Next.js/TS, Thirdweb v5, Base L2, ERC‑4337/1155.

    • Artefak: UNDERSTANDING Doc (publik) — [tautan]

    • Peran: desain alur distribusi, sourcing, e‑commerce ops, dokumentasi SOP.

    • Hasil: [isi metrik aman publik]

    • Tooling: Shopify/Marketplace, Notion/Docs, basic BI.

    • Peran: arsitektur posting Alfa/Beta/Gama/Delta; tokenomics reward 11/7/4/1; on‑chain media links.

    • Stack: Next.js/TS/Tailwind; Thirdweb v5; Base.

    • Hasil: [isi singkat—uji coba, metrik awal]

    Tambahkan entri lain sesuai kebutuhan (mis. Voyage, Principle Skateboarding/PT‑PSI, dll).


    • UNDERSTANDING Doc (BGC/iBLOOMING) — [tautan publik]

    • Firewall Manager Playbook — [tautan]

    • Prototipe/Repo/Demo — [tautan]

    • Deck/One‑Pager — [tautan]

    Catatan: tautan publik hanya untuk konten yang memang aman untuk dibuka; sisanya tetap privat.


    • [Judul] — [Media/Acara], [Tanggal], [Tautan]

    • [Judul] — [Media/Acara], [Tanggal], [Tautan]


    • Versioning: v.X.Y.Z[-suffix] konsisten dengan package.json.

    • Changelog: Release Drafter/Changesets; lampirkan preview/screenshot/compare.

    • Branch & Deploy Hygiene: PR previews; pre‑release flag bila perlu; smoke test /store /PDP /cart (persist)


    • Dokumen ini boleh dibaca untuk informasi dan panduan.

    • Dilarang menyebarkan, mengutip, merangkum, atau membuat turunan tanpa izin tertulis.

    • Bagikan tautan dokumen, bukan teks.

    • Diskusi/penjelasan ulang konten ini (lisan/tertulis/rekaman) memerlukan izin.


    • Pemakaian: untuk setiap lowongan, pilih 1–2 klaster (A–H), ambil helai pengalaman & skill relevan, lalu susun resume tailor (1–2 halaman) + portofolio bukti.

    • Konsistensi: jaga single‑language rule (dokumen penuh bahasa Indonesia atau penuh Inggris).

    • Artefak Bukti: siapkan link aman publik (atau redacted) untuk tiap klaim (diagram, repo, docs).


    • Ringkasan identitas & legal berada di "1) Identitas & Kontak".

    • Praktik operasional (mis. Audit-Ready, Release Rituals, Async-First, Legal & Verifikasi) telah dibawa ke Bagian 3 dan Bagian 4 sebagai prinsip & keterampilan.

    • Sub-bagian Canon ini menyimpan aturan & kebijakan pendukung (HFP, privasi, lisensi, verifikasi).

    • Jumlah: maksimum 47 HFP (v.01–v.47).

    • Versi: nomor sebelum titik = identitas HFP; setelah titik = identitas posisi/jabatan/peran.

      • Contoh: v.11.11 → HFP #11 yang sedang mengemban jabatan #11 (misal: pencuci piring).

    • Periode: HFP aktif selama kontrak kerja dengan Prof. NOTA Inc. (PT Suaka Dunia Raja); berakhir jika kontrak sudah tuntas, yaitu diselesaikan/dibatalkan.

    • Dokumen menggunakan "kami" (Prof. NOTA = hingga 47 HFP).

    • Percakapan langsung boleh "aku".

    • Bahasa: Indonesia + sisipan English (0101-style); tersedia varian full-EN/other bila diperlukan.

    • Ikon resmi: PFP Prof. NOTA (potret monokrom bermasker).

      • Versi frame lingkaran untuk emblem/medsos; versi full untuk header dokumen.

    • Kostum fisik (HFP): coverall satu potong — putih (indoor) & hitam (outdoor) — memuat identitas: "Prof. NOTA Inc. (PT Suaka Dunia Raja)", logo, "Prof. NOTA v.xx.xx", dan (opsional) logo klien/sponsor/partner.

    • Semua perjanjian (kontrak/invoice/aplikasi) memakai entitas legal: Prof. NOTA Inc. (PT Suaka Dunia Raja).

    • Ditandatangani oleh HFP yang ditunjuk, format: [Nama HFP] Prof. NOTA v.xx.xx

    • Byline karya (dokumen/kode): tulis “Prof. NOTA v.xx.xx”.

    • Skema HFP (rekrut internal): HFP menerima 26% dari revenue aktivitasnya sebagai Prof. NOTA; 74% untuk Prof. NOTA Inc.

    • Batas atas: bila bagian Prof. NOTA Inc. pada bulan berjalan > IDR 147.000.000, maka Prof. NOTA Inc. hanya menerima IDR 147.000.000 dan selisihnya untuk HFP.

    • Skema Lisensi (perusahaan eksternal): berlangganan lisensi IDR 147.000.000/bulan → berhak menjual layanan & value Prof. NOTA tanpa batas revenue.

    • Identitas HFP: internal, bukan publik. Pengecualian hanya untuk penegakan hukum.

    • Doxxing oleh pihak selain Prof. NOTA Inc. → membatalkan kontrak.

    • Impersonation: keaslian hanya diakui jika ada dokumen/URL resmi pada domain: endhonesa.com, skateshop.id, straight-line.org.

    • Di resume/profil, tulis: "Prof. NOTA v.xx.xx (HFP)" + tautan ke halaman penjelasan HFP.

    • Jika calon mitra memerlukan data legal/identitas: lakukan via dokumen resmi yang ditandatangani kedua pihak.


    • 2025-10-31 05:06 UTC+07:00 — Melengkapi pendidikan & sertifikasi.

    • 2025-10-19 00:03 UTC+07:00 — Inisiasi ResumeAll v.11 (glossary), menyusun identitas, services & value, skill matrix, pengalaman, proyek, dan kebijakan konten.


    Discord: https://discord.gg/5KrsT6MbFm/

    D — Business Architecture — ...Dalam peran produk/operasi, kami memetakan alur nilai dan risiko ke proses yang terukur biaya serta kepatuhan.

  • E — Cultural & Social Innovation — ...Untuk komunitas, kami merancang program dan gamifikasi yang menaikkan partisipasi dengan metrik yang jelas.

  • F — Personal Brand Access (DevRel) — ...Sebagai DevRel, kami menerjemahkan kompleksitas menjadi cerita, demo, dan praktik yang mendorong adopsi karena orang benar-benar mengerti.

  • G — Custom Creation (Riset/Proposal) — ...Dalam kreasi kustom, kami menulis proposal/kerangka dan menyiapkan artefak bukti presisi untuk respons cepat namun tetap audit-ready.

  • H — Global Trade & Distribution (Legacy Ops) — ...Pada legacy ops, kami merapikan sourcing, inventori, dan fulfillment dengan dokumentasi kerja yang disiplin untuk menekan friksi.

  • , changelog, PR hygiene, smoke test route utama
  • Async-First & Timezone-Honest — kerja berbasis artefak; rapat seperlunya (WIB aware)

  • Firewall — akses langsung setelah komitmen & kejelasan; dokumen = kontrak kerja tim

  • Legal & Accountability — selalu atas nama Prof. NOTA Inc. (PT Suaka Dunia Raja); tanda tangan oleh HFP sebagai “Prof. NOTA v.xx.xx”; byline karya mengikuti format yang sama

  • Audit-Ready & Verifiable — keputusan/komitmen tertulis & terverifikasi via dokumen resmi pada domain: endhonesa.com, skateshop.id, straight-line.org

  • Web3 Prototype/Integration (C) — Next.js/TS + Thirdweb v5 + AA (ERC-4337) + ERC-1155 (Base/OP). Deliverables: repo, rute demo, test minimal (Playwright/Cypress), bukti rilis (preview/changelog).
  • Business Architecture & Ops Playbook (D/H) — SOP, RACI, compliance & token lifecycle policy. Deliverables: Operational playbook, value stream map, audit checklist.

  • Community & Learning Program (E/F) — DevRel, workshop, kurikulum, content calendar. Deliverables: demo/sample repositories, material workshop, campaign plan, and adoption metrics.

  • Custom Creation (G) — proposal/grant/RFP, research digest, crisis narrative. Deliverables: proposal pack, due-diligence memo, Q&A krisis.

  • (detail & ketentuan lihat "
    15) Persona & HFP Canon
    ").

    C1

    English

    C2 (74)

    C2 (97)

    B1 (46)

    C2 (74)

  • Sertifikasi & Bukti Bahasa

    • EF SET (English, CEFR) — C2 Proficient (73/100) · Certificate: EF SET Certificate (PDF File)

    • UKBI Adaptif (Bahasa Indonesia) — III (Unggul)

  • Nada & Suara: jernih, to-the-point, ramah, anti-glamor-kosong; “jelas dulu, baru kencang”.

    : alt-text, aria-labels, dan kontras yang memadai pada semua bahasa.

    Architecture Decision Record (ADR) → “Catatan Keputusan Arsitektur (ADR)”

  • Kebijakan terjemahan: istilah yang lebih umum dipahami dalam English tetap English dan diberi padanan di kurung pada sebutan pertama.

  • Proses: terjemahan → review teknis → review gaya; simpan memori terjemahan sederhana (TM) agar konsisten.

  • — [Institusi], [Tahun] Jaringan, sistem operasi, dan hygiene DevOps pemula.
    [C, DevOps]
  • SMK Otomasi/IoT — [Institusi], [Tahun] Sensor, telemetry ringan, dan integrasi sistem. [C, D]

  • SMK Multimedia / Desain Komunikasi Visual (DKV) — [Institusi], [Tahun] Produksi konten, tata visual, dan UI copy dasar untuk dokumen & demo. [B, F, E]

  • SMA 10, 11, dan 12-IPS (Ilmu Pengetahuan Sosial) — [Institusi], [Tahun] Fokus pada ilmu sosial dan kemasyarakatan.

  • SMK Akuntansi & Perpajakan — [Institusi], [Tahun] Pencatatan, biaya, dan kontrol dasar—fondasi “Measured Impact”. [D, H]

  • SMK Logistik — [Institusi], [Tahun] Dasar supply chain, inventori, dan fulfillment. [H]

  • [B, E, F]
  • D3 Manajemen Logistik — [Institusi], [Tahun] Perencanaan persediaan, SLAs, dan metrik fulfillment. [H]

  • D3 Akuntansi — [Institusi], [Tahun] Biaya/ops, pelaporan, dan kontrol kepatuhan dasar. [D]

  • D3 Hukum Bisnis/Perpajakan — [Institusi], [Tahun] Kerangka legal kontrak & kepatuhan operasional. [D]

  • D4 Desain Interaksi (HCI Terapan)
    — [Institusi], [Tahun] UX, aksesibilitas, dan konten dapat diajarkan.
    [B, C, E]
  • D4 Keamanan Siber Terapan — [Institusi], [Tahun] ISMS praktis, kontrol akses, dan incident hygiene. [D, Firewall]

  • D4 Manajemen Rantai Pasok Terapan — [Institusi], [Tahun] Perencanaan supply chain, integrasi data, dan KPI operasional. [H]

  • S1 Teknik Industri
    — [Institusi], [Tahun] Value stream, optimasi proses, dan desain operasi.
    [D, H]
  • S1 Desain Komunikasi Visual / Desain Produk / UX — [Institusi], [Tahun] Informasi visual, UX writing, dan dokumentasi yang bisa diajarkan. [B, E, F]

  • S1 Manajemen (Teknologi/Operasi/Produk) — [Institusi], [Tahun] Discovery→delivery, prioritas, dan orkestrasi rilis. [D]

  • S1 Akuntansi / Keuangan — [Institusi], [Tahun] Kontrol biaya & pelaporan untuk “Measured Impact”. [D]

  • S1 Hukum Bisnis / Hukum TI — [Institusi], [Tahun] Kontrak, IP, dan kepatuhan data/teknologi. [D]

  • S1 Ilmu Komunikasi / Jurnalistik — [Institusi], [Tahun] Narasi teknis publik, DevRel, dan edukasi. [B, F]

  • S1 Data Science / Statistika — [Institusi], [Tahun] Analitik, eksperimen, dan pengambilan keputusan berbasis data. [D]

  • S1 Ekonomi / Keuangan / Bisnis Digital — [Institusi], [Tahun] Dasar tokenomics, model nilai, dan strategi komersial. [A, D]

  • S1 Pendidikan / Teknologi Pembelajaran — [Institusi], [Tahun] Kurikulum, evaluasi, dan program pelatihan komunitas. [E, F]

  • S1 Logistik / Manajemen Rantai Pasok — [Institusi], [Tahun] Integrasi pemasok—gudang—distribusi yang terdokumentasi. [H]

  • S2 Manajemen (MBA Teknologi / Product Management) — [Institusi], [Tahun] Strategi produk, GTM, dan metrik bisnis. [A, D, F]
  • S2 Data Science / Analytics — [Institusi], [Tahun] Telemetri, eksperimen, dan pengambilan keputusan kuantitatif. [D]

  • S2 Cybersecurity / Information Assurance — [Institusi], [Tahun] ISMS, risk management, dan kebijakan keamanan. [D, Firewall]

  • S2 Hukum (IP/IT/Data Protection) — [Institusi], [Tahun] Perlindungan data, kontrak, dan lisensi IP. [D]

  • S2 Kebijakan Publik (Digital Governance/Regulasi) — [Institusi], [Tahun] Kerangka regulasi dan kepatuhan lintas yurisdiksi. [A, D]

  • S2 Supply Chain Management — [Institusi], [Tahun] Optimasi jaringan distribusi dan integrasi data. [H]

  • S2 Technical Communication — [Institusi], [Tahun] Penulisan teknis tingkat lanjut & program dokumentasi. [B]

  • S3 Komunikasi / Technical Communication — [Institusi], [Tahun] Difusi inovasi, DevRel, dan literasi teknis publik. [B, F]
  • S3 Ekonomi/Keuangan (Game Theory/Token Economics) — [Institusi], [Tahun] Mekanisme insentif, token design, dan kebijakan ekonomi. [A, D]

  • Hack Your Future: Cyber Security Projects for Your Dream Job

    D

    React basic in just 1 hour [2022]

    C

    Vue JS and Firebase: Build an iOS and Android Chat App

    C

    Learn Angular 5 from Scratch

    C

    Learn Angular 4 from Scratch

    C

    Quickstart AngularJS 1.0 [First Version Of Angular]

    C

    Code Your First Game: Arcade Classic in JavaScript on Canvas

    C

    The Complete Full-Stack JavaScript Course

    C

    Learn to Program in Javascript: Beginner to Pro

    C

    Javascript Essentials

    C

    Agile PM 101 - Learn the Truth About Agile versus Waterfall

    A, D

    Basics of Scrum, Agile and Project Delivery

    A, D

    A Professional APP Development Course for iPhone and Android

    C

    Become an Android Developer from Scratch

    C

    Learn Android Application Development

    C

    Eclipse IDE for Beginners: Increase Your Java Productivity

    C

    Java Multithreading

    C

    Practice Java by Building Projects

    C

    Java Database Connection: JDBC and MySQL

    C, D

    Java Programming Basics

    C

    MongoDB Essentials - Understand the Basics of MongoDB

    C, D

    Foundations of Front-End Web Development

    C

    Git Started with GitHub

    B, D

    Wordpress Security: How To Stop Hackers

    D, H

    Learn Complete Wordpress Security

    D, H

    Complete WordPress Security Course: Go from Zero to Hero

    D, H

    Fundamentals of Internet Security: Secure Your Environment

    D

    Load Wordpress 400% Faster Without any Technical Skills

    H, D

    Django for WordPress Developers

    C, H

    WP-HTML: WordPress as Micro Apps in Any HTML Page

    C, H

    Unpacking the Internet of Things (IoT)

    A

    Big Data and Hadoop Essentials

    D

    Learn SEO For Wordpress Websites

    F, H

    Learn Advanced SEO From Scratch,Complete SEO Training Course

    F, H

    Make WordPress Hosting Easy with Plesk on Amazon Lightsail

    D, H

    Make WordPress Hosting Easy with Plesk on Google Cloud

    D, H

    Make WordPress Hosting Easy with Plesk on Hetzner Cloud

    D, H

    Make WordPress Hosting Easy with Plesk on Linode

    D, H

    Make WordPress Hosting Easy with Plesk on DigitalOcean

    D, H

    Cloud Computing With Amazon Web Services

    D

    A Practical Introduction to Cloud Computing

    D

    Introduction to Cloud Computing

    D

    Free SSL Certificate: Comodo SSL for Free Forever (HTTPS)

    D, H

    Bootstrap 4 Quick Start: Code Modern Responsive Websites

    C

    Advanced Databases and SQL Querying

    D

    Introduction to Databases and SQL Querying

    D

    Beginner PHP and MySQL Tutorial

    C, H

    PHP For WordPress Development

    C, H

    Practical PHP: Master the Basics and Code Dynamic Websites

    C, H

    How To Create A Website using WordPress (Step by Step)

    C, H

    Build Your First Website in 1 Week with HTML5 and CSS3

    C

    Web Development By Doing: HTML / CSS From Scratch

    C

    HTML: Learning the Basics Intro to HTML Website Coding

    C

    C++ Tutorial for Complete Beginners

    C

    Intro to Linux Shell Scripting (Free course)

    D

    Command Line Essentials: Git Bash for Windows

    D

    Introduction to Networking for Complete Beginners

    D

    ; diagram token flow —
    [tautan]

    SOP/Playbook — [tautan]

    /checkout (locations API)
    .
  • Role Gating: role switcher (Visitor/Guest; Partner; Family) — akses & harga dikendalikan oleh role.

  • Keterbukaan: identitas HFP dicantumkan di kontrak (internal/ke mitra), tidak untuk publik kecuali kebutuhan hukum/negara.

  • HFP dilarang mengungkap perannya ke publik selama kontrak berjalan; boleh dicantumkan sebagai pengalaman setelah kontrak sudah tuntas.

  • Wajah HFP harus bermasker saat didokumentasikan (foto/video) ketika bertugas sebagai HFP.

    Tanpa lisensi, penggunaan komersial oleh perusahaan eksternal wajib melalui kontrak kerja (seperti meng-hire SDM Prof. NOTA).

    Jika ada dokummen/URL tentang HFP di luar domain: endhonesa.com, skateshop.id, straight-line.org, maka itu dianggap phishing/scam/impersonation.

  • Semua pengungkapan sensitif harus berupa dokumen resmi (bukan chat/ucapan).

  • Email: nota{xx}@endhonesa.com (contoh: nota11@endhonesa.com).

  • Bio Singkat = 2–3 kalimat yang menautkan misi–cara kerja–dampak ke posisi yang di-apply.

  • Indonesia

    C1

    C1

    Udemy Course - (UDEMY.COM)

    Tag

    Link (Artefact/Proof)

    Udemy Course - (UDEMY.COM)

    A - H

    Udemy Profile

    1.2 Legal

    1.3 Tagline

    1.4 Lokasi & Waktu

    1.5 Kontak Publik

    1.6 Bio Singkat

    1.7. Contoh Satu Kalimat Tambahan Untuk Bio

    1.8 Verifikasi Resmi

    2) Misi, Nilai, & Prinsip Kerja

    2.1 Misi (one-liner)

    2.2 Nilai (yang tak berubah)

    2.3 Prinsip Kerja (urut aliran kerja)

    3) Services & Value (A–H)

    • Peta layanan untuk men-tailor resume.

    • Tiap klaster memuat Value, Deliverables (artefak bukti), dan KPI contoh.

    • Prinsip lintas-klaster: Audit-Ready, Release Rituals, Async-First, dan Legal & Verifikasi (byline “Prof. NOTA v.xx.xx”; detail lihat "15) Persona & HFP Canon").

    3.1 Strategic Vision & Consultation (A)

    3.2 Intellectual Property & Storytelling (B)

    3.3 Web3 Development & Prototyping (C)

    3.4 Business Architecture (D)

    3.5 Cultural & Social Innovation (E)

    3.6 Personal Brand Access (DevRel / Edukasi / Kampanye) (F)

    3.7 Custom Creation (Riset / Proposal / Krisis) (G)

    3.8 Global Trade & Distribution (Legacy) (H)

    4) Keahlian Teknis (Skill Matrix)

    • Cara baca: Bagian ini menekankan kemampuan eksekusi yang mendukung seluruh klaster A sampai H di atas.

    • Tooling pilihan: GitHub, Vercel, PNPM/Turborepo, Notion/Markdown, Mermaid/Draw.io, (opsional) db/schema ringan.

    4.1 Docs & Knowledge (Docs-as-Code)

    4.2 Web3 (Integrasi & Prototyping)

    4.3 Web/App (Frontend & DX)

    4.4 DevOps & Release Rituals

    4.5 Async-First Collaboration

    4.6 Ops & Produk

    4.7 Data & Arsitektur

    4.8 Testing & Quality

    4.9 Security & Compliance (praktis)

    Kata kunci (ATS/AI): Next.js, React, TypeScript, Tailwind, Thirdweb v5, ERC-4337, ERC-1155, Base/Optimism, SIWE, viem/wagmi, OpenAPI, ADR, Vercel, GitHub Actions, Playwright/Cypress, Changesets, Release Drafter, Docs-as-Code.

    5) Kompetensi Peran (Role Buckets → untuk ATS/AI)

    • Gunakan sebagai peta saat men-tailor resume.

    • Setiap bucket memuat Fokus, Deliverables, dan Kata Kunci ATS.

    • Core Competencies (lintas-bucket): Audit-Ready (dokumen = kontrak kerja tim), Release Rituals (versioning + evidence), Async-First (artefak-first, overlap WIB).

    5.1 Dokumentasi / Konten

    5.2 Engineering (Web3/Frontend/Integrations)

    5.3 Strategi / Arsitektur

    5.4 Produk / Operasional

    5.5 Komunitas / Publik (DevRel)

    5.6 Custom / Research

    5.7 E-commerce / Legacy

    6) Ketersediaan & Model Keterlibatan

    6.1 Ketersediaan

    6.2 Legal & Penandatangan

    6.3 Model Keterlibatan (selaras klaster A sampai H)

    6.4 Model Komersial

    6.5 Kompensasi & Pembayaran

    6.6 Ritme Kolaborasi (meta)

    7) Bahasa

    Ganti skor dan tautan sertifikat bahasa untuk memperbarui sesuai hasil tes/sertifikasi yang dilakukan HFP.

    7.1 Kemampuan Bahasa (diperkuat)

    7.2 Kebijakan Bahasa & Pronomina

    7.3 Gaya Editorial (Docs & Konten)

    7.4 Localisasi & i18n (untuk produk/kode)

    7.5 Glosarium & Terjemahan

    7.6 Channel & Penggunaan

    8) Pendidikan & Sertifikasi

    • Ganti [Institusi] dan [Tahun] sesuai yang dilakukan HFP.

    • Tag [A sampai H] merujuk ke klaster Services & Value.

    • Ganti link dengan URL verifikasi resmi sesuai hasil sertifikasi yang dilakukan HFP.

    • Gunakan Bagian 10 sebagai bukti praktis yang menguatkan kompetensi (tautan ke artefact/proof) sesuai yang sudah dilakukan HFP.

    • Kebijakan verifikasi & penandatangan lihat "15) Persona & HFP Canon" (byline: “Prof. NOTA v.xx.xx”).

    8.1 Pendidikan Formal

    8.1.1 Sekolah Taman Kanak-Kanak / Kindergarten School (TK/ KS Equivalent)

    8.1.2 Sekolah Dasar / Elementary School (SD/ES Equivalent)

    8.1.3 Sekolah Menengah Pertama / Junior High School (SMP/JHS Equivalent)

    8.1.4 Sekolah Menengah Kejuruan / Sekolah Menengah Atas / High School (SMK/SMA/HS Equivalent)

    8.1.5 Diploma 1 (D1) - Ahli Pratama

    8.1.6 Diploma 2 (D2) - Ahli Muda

    8.1.7 Diploma 3 (D3) - Ahli Madya

    8.1.8 Diploma 4 (D4) - Sarjana Terapan

    8.1.9 Sarjana (S1)

    8.1.10 Magister (S2)

    8.1.11 Doktoral (S3)

    8.1.12 Postdoctoral (PostDoc)

    8.2 Sertifikasi (Pendidikan Nonformal)

    8.2.1 Udemy Course - (UDEMY.COM)

    9) Pengalaman (Glossary of Experience)

    iBLOOMING / BGC — Web3 Transition & Tokenomics — 2023–sekarang (konfirmasi)

    ENDHONESA / SKATESHOP.ID — Ops & Distribution (Legacy) — [tahun–tahun]

    Pseudonim Pos (Base) — Social dApp — [tahun]

    10) Proyek & Portfolio (Artefak/Proof Public‑Safe)

    11) Publikasi, Talk, & Penghargaan

    12) Release Rituals & Operasional (Ringkas)

    13) Kebijakan Konten (Detail)

    14) Catatan Penyusunan & Pemakaian

    15) Persona & HFP Canon

    15.1 Pernyataan Persona (Canon)

    15.2 Human for Profile (HFP)

    15.3 Bahasa & Suara

    15.4 Identitas Visual (PFP & kostum)

    15.5 Kontrak, Tanda Tangan, & Atribusi

    15.6 Lisensi HFP & Komersial

    15.7 Privasi, Integritas, & Krisis

    15.8 Cara Apply & Verifikasi

    16) Changelog

    https://nota.endhonesa.com/
    https://github.com/myreceiptt/
    https://x.com/MyReceiptTT/
    HASIL PELATIHAN UKBI (Uji Kemahiran Berbahasa Indonesia)
    Remote Roles Living List

    C1

    SKOR TAUTAN ZIONIS

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Tanggal: 1 Oktober 2025 Penyusun: Internal Prof. NOTA Inc., including ChatGPT (OpenAI), atas permintaan dan untuk kepentingan Prof. NOTA (v.11).


    Dokumen ini merangkum seluruh obrolan dan hasil penilaian (scoring) yang disusun oleh Prof. NOTA Inc., mulai dari isu awal “Vercel is Zionist” yang disampaikan kepada Prof. NOTA, hingga daftar terkurasi lintas sektor, fokusnya adalah entitas yang paling dekat dengan Prof. NOTA, baik Teknologi (Web2/Web3) maupun Non‑Teknologi, mulai dari Produk/Jasa di Indonesia hingga di tingkat Global.

    Skor 1–10 = indikator keterkaitan institusional dengan Negara/Pemerintah/Militer Israel atau aktivitas permukiman, bukan vonis ideologis personal.

    Arti skor: 9–10 = kontrak langsung pemerintah/pertahanan Israel yang besar/strategis.

    7–8
    = infrastruktur/operasi/akuisisi strategis di Israel (region cloud, fab, kantor R&D besar) atau kemitraan pemerintah tingkat tinggi.
    5–6
    = dampak bermakna (tercatat di basis data PBB terkait permukiman, HQ Israel, pemasok siber utama).
    3–4
    = indikasi lemah/sekunder (R&D/PoP/akuisisi tanpa bukti kontrak pemerintah).
    1–2
    = tak ada bukti institusional yang material.

    1. Pemicu — Pertanyaan: “Vercel is Zionist?” → dibedah fakta publik tentang pertemuan CEO Vercel dengan PM Israel (Netanyahu), reaksi komunitas, dan batas dari klaim yang bisa dibuktikan.

    2. Ekspansi — Disusun daftar lintas sektor (termasuk F&B, fashion, pertahanan, perbankan) dengan skor 1–10.

    3. Fokus Teknologi — Disusun Top‑20 (Web2/Web3) berdasarkan validasi/nilai/pengguna/eksposur.

    4. Fokus Indonesia — Disusun Top‑100 produk/jasa teknologi yang beroperasi atau dipakai luas di Indonesia dengan skor yang sama.

    5. Fokus Prof. NOTA — Disusun daftar stack (Teknologi), termasuk ChatGPT/OpenAI, lalu Non‑Teknologi (skate/streetwear/F&B/ritel/logistik).

    6. Dokumentasi akhir — Menggabungkan semua hasil dalam satu paper agar publik mengetahui subjek utama adalah Prof. NOTA dan keterkaitannya.


    • Bobot utama: kontrak pemerintah/pertahanan Israel (nilai $, keterlibatan kementerian/angkatan), lalu operasi/investasi strategis (region cloud, fab, kantor R&D), kemudian kebijakan produk/operasi terkait permukiman, dan terakhir pernyataan/gestur publik pimpinan.

    • Apa yang TIDAK dinilai: sikap individu karyawan, opini viral tanpa verifikasi, atau perdebatan moral di luar indikator institusional.

    • Catatan hukum: di AS, korporasi tidak boleh menyumbang langsung ke kandidat federal; yang biasa ada adalah PAC karyawan (terdaftar). Ketiadaan PAC/kontrak menurunkan skor.


    Tabel ini mengompilasi hasil lintas bidang yang paling mungkin dan sering disentuh oleh Prof. NOTA, berpengaruh besar dan kerap dibahas publik. Selain ranah teknologi—stack/merek/tool, cakupan juga meliputi kategori non-teknologi—termasuk skateboarding/streetwear, F&B, ritel, logistik, dan sejenisnya. Memadukan entitas yang beroperasi di Indonesia atau digunakan luas oleh pengguna/perusahaan di Indonesia dengan pemain global (dipilih berdasarkan nilai/validasi, jumlah pengguna, dan eksposurnya), sehingga tabel hasil ini menjadi satu peta keterkaitan institusional yang utuh dan relevan terhadap ekosistem serta preferensi Prof. NOTA.

    #
    Entitas
    Domain
    Aktor Kunci
    Alasan Faktual
    The Receipt
    Skor

    Catatan: Tabel lintas sektor menekankan entitas berpengaruh lintas industri yang sering muncul dalam diskursus publik.


    • Eksposur tertinggi dalam stack Prof. NOTA ada pada hyperscaler cloud (Google & AWS) yang berada di skor 9. Bila ingin mengurangi paparan, pertimbangkan strategi multi‑cloud dan abstraksi infra (container, IaC, edge/CDN multi‑vendor).

    • Lapisan dev hosting (Vercel/Netlify) berada di skor rendah‑menengah; mitigasi melalui deployment adapters (Next.js SSR → Node/Edge adapters) agar portabilitas meningkat.

    • Web3 infra (Consensys/Chainalysis/Coinbase) menunjukkan paparan moderat‑rendah; kunci mitigasi adalah multi‑RPC/multi‑custody dan self‑hosted gateways untuk alur kritikal.

    • Non‑Teknologi: beberapa ritel & F&B global (McDonald’s, PepsiCo/SodaStream, Nestlé) berada di 5–6. Untuk aktivitas publik Prof. NOTA (kampanye, kurasi brand), bisa diberi label transparansi vendor atau alternatif lokal.

    • Kebijakan vendor internal: jadikan skor sebagai tiering (≥7 perlu justifikasi & mitigasi; 5–6 pantau dan siapkan opsi kedua; ≤4 risiko rendah namun tetap pastikan portabilitas).


    1. Klaim “Vercel is Zionist” tidak terbukti secara institusional; yang terbukti adalah gestur publik CEO (meningkatkan persepsi), bukan kontrak pemerintah/militer.

    2. Paparan terbesar berasal dari kontrak pemerintah/pertahanan yang terverifikasi (Google & AWS lewat Project Nimbus), diikuti lapisan vendor pertahanan/siber tertentu.

    3. Prof. NOTA sebagai subjek dan pengambil keputusan ekosistem dapat menggunakan skor ini untuk:

      • Menyusun kebijakan vendor (tiers/allowlist/exception).

      • Merancang rencana migrasi bertahap (prioritaskan layanan skor ≥7).

      • Mempublikasikan transparansi kepada publik/komunitas (#OiOi) terkait alasan teknis & etis di balik pilihan vendor.

    Dokumen ini adalah kompilasi berbasis sumber publik & diskusi internal, dengan fokus pada indikator institusional. Ia tidak menghakimi pribadi, melainkan membantu governance keputusan Prof. NOTA.


    • Kontrak Pemerintah/Pertahanan (40%): nilai, durasi, kementerian/angkatan terkait, bukti dokumenter.

    • Operasi/Investasi Strategis (30%): region cloud, data center, fab, R&D yang substansial.

    • Kebijakan Produk/Permukiman (20%): pencantuman di daftar PBB, kebijakan platform.

    • Gestur/Pernyataan Publik (10%): pertemuan, pernyataan dukungan eksplisit.

    • Penyesuaian: klarifikasi/bantahan resmi dapat menurunkan skor.

    • Tiering Vendor:

      • Tier‑A (≥7): perlu justifikasi kuat & mitigasi (multi‑vendor, exit plan).

      • Tier‑B (5–6): pantau berkala; siapkan opsi kedua.

      • Tier‑C (≤4): risiko rendah; pastikan portabilitas tetap dijaga.

    • Ritme Pembaruan: setiap kuartal atau saat ada perubahan kebijakan/kontrak besar.


    Subjek dokumen ini adalah Prof. NOTA. Setiap penggunaan ulang harap menjaga konteks dan tidak menyalahi interpretasi skor sebagai vonis ideologis personal.


    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.


    Ringkasan Eksekutif

    Latar & Alur

    Metodologi Penilaian (Ringkas)

    Tabel Hasil (Terpadu)

    Observasi & Implikasi (Untuk Prof. NOTA)

    Kesimpulan

    Lampiran A — Rubrik Skor (Detail)

    Lampiran B — Cara Memakai Dokumen Ini

    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    No Certificate
    Certificate
    Certificate
    No Certificate
    Certificate
    Certificate
    Certificate
    No Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    No Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    No Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate
    Certificate

    1

    Acer

    Perangkat

    —

    Tidak ada bukti institusional

    Dipakai luas

    2

    2

    Adidas

    Apparel

    Bjørn Gulden

    Ritel kehadiran di Israel; tanpa kontrak gov

    Streetwear/skate ref

    2

    3

    Adobe

    Desain

    Shantanu Narayen

    Tidak ada bukti institusional

    Dipakai desain

    2

    4

    Akamai

    CDN/Edge

    Tom Leighton

    Akuisisi Cotendo (Israel); operasi berlanjut

    Dipertimbangkan untuk CDN

    4

    5

    Akulaku

    Paylater

    —

    Tidak ada bukti institusional

    Digunakan konsumen ID

    1

    6

    Airbnb

    Travel

    Brian Chesky

    Riwayat kebijakan & pencantuman permukiman

    Dipakai publik luas di ID

    6

    7

    Alchemy

    Web3 infra

    Nikil Viswanathan

    Tidak ada bukti institusional

    Alternatif RPC

    1

    8

    Alphabet (Google / YouTube / GCP)

    Cloud/AI/Ads

    Sundar Pichai

    Kontrak Project Nimbus untuk pemerintah & militer Israel

    Dipakai dalam stack; paparan tinggi

    9

    9

    Apple

    Perangkat/R&D

    Tim Cook

    R&D Herzliya/Haifa

    Dipakai luas; umum

    4

    10

    Arweave

    Storage

    Sam Williams

    Tidak ada bukti institusional

    Dipakai/direncanakan

    1

    11

    Atlassian (Jira/Confluence)

    SaaS Dev/PM

    Scott Farquhar; Mike Cannon-Brookes

    Operasi global; tidak ada bukti institusional Israel

    Dipakai kolaborasi/PM

    2

    12

    Avalanche / Ava Labs

    L1

    Emin Gün Sirer

    Tidak ada bukti institusional

    Dirujuk

    1

    13

    Agoda

    Travel

    Omri Morgenshtern

    Bagian Booking Holdings

    Dipakai luas di ID

    3

    14

    ASUS

    Perangkat

    —

    Tidak ada bukti institusional

    Dipakai luas

    2

    15

    BANANOW LAND

    Web3 IP

    —

    IP/operasi Prof. NOTA

    Operasi internal

    1

    16

    Bank Jago

    Bank digital

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    17

    Barclays

    Keuangan

    —

    Kontroversi investasi; bantahan resmi

    Global/Referensi

    5

    18

    Biznet

    Fixed broadband

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    19

    Blibli

    E-commerce

    Kusumo Martanto

    Tidak ada bukti institusional

    Dipakai publik luas di ID

    1

    20

    Boeing

    Pertahanan

    Kelly Ortberg

    Penjualan F-15/JDAM (paket ekspor AS)

    Global/Referensi

    8

    21

    Box

    SaaS/Komunikasi

    —

    Tidak ada bukti institusional

    Dipakai stack komunikasi

    2

    22

    Bukalapak

    E-commerce

    Willix Halim

    Tidak ada bukti institusional

    Dipakai publik luas di ID

    1

    23

    Burger King

    F&B

    —

    Operasi/waralaba di Israel

    Non-tech referensi

    3

    24

    ByteDance (TikTok)

    Sosial/Commerce

    Shou Zi Chew

    Tidak ada bukti institusional

    Dipakai luas di ID

    2

    25

    Booking Holdings (Booking.com)

    Travel

    Glenn Fogel

    Pencantuman akomodasi permukiman (laporan)

    Dipakai publik luas di ID

    5

    26

    Carhartt WIP

    Apparel

    —

    Distribusi/retailer Israel

    Non-tech referensi

    2

    27

    Caterpillar

    Alat berat

    Joe Creed

    Penggunaan bulldozer oleh militer Israel (sorotan HAM)

    Non-tech referensi; relevan manufaktur

    8

    28

    Chainalysis

    Analytics/Web3

    Michael Gronager

    Kantor TLV; akuisisi Alterya

    Web3 analytics

    5

    29

    Check Point

    Keamanan

    Gil Shwed

    Perusahaan siber Israel berskala global

    Dipakai enterprise di ID

    6

    30

    Cisco

    Jaringan

    Chuck Robbins

    Akuisisi startup Israel; operasi berkelanjutan

    Referensi enterprise

    5

    31

    Cloudflare

    CDN/Edge

    Matthew Prince

    PoP Tel Aviv; operasi jaringan

    Dipertimbangkan untuk CDN

    4

    32

    Coinbase

    Exchange/L2

    Brian Armstrong

    Ekspansi peran Israel

    Dipakai/dirujuk

    3

    33

    Coca-Cola (CBC Israel)

    Minuman

    —

    Bottler eksklusif Israel

    Non-tech referensi

    3

    34

    Consensys (MetaMask/Infura/Linea)

    Web3 infra

    Joseph Lubin

    Kemitraan Blockaid (TLV)

    Dipakai/dirujuk

    4

    35

    Coursera

    EdTech

    Jeff Maggioncalda

    Tidak ada bukti institusional Israel

    Digunakan pembelajaran

    1

    36

    CUFI

    Organisasi religi

    John Hagee

    Misi pro-Israel eksplisit

    Global/Referensi

    10

    37

    CyberArk

    Keamanan (PAM)

    —

    Perusahaan Israel; operasi di ID

    Dipakai enterprise di ID

    6

    38

    DANA

    Dompet digital

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    39

    Databricks

    Data/AI

    Ali Ghodsi

    Kehadiran engineering di Israel; akuisisi terkait

    Dipertimbangkan untuk lakehouse/AI

    4

    40

    Decathlon

    Ritel olahraga

    Barbara Martin Coppola

    Toko & ekspansi Israel

    Non-tech referensi

    3

    41

    Dell

    Perangkat

    —

    Tidak ada bukti institusional

    Dipakai luas

    2

    42

    DOKU

    Payment gateway

    —

    Tidak ada bukti institusional

    Digunakan merchant ID

    1

    43

    Domino’s

    F&B

    —

    Operasi/waralaba di Israel

    Non-tech referensi

    3

    44

    Dropbox

    SaaS/Komunikasi

    —

    Tidak ada bukti institusional

    Dipakai stack komunikasi

    2

    45

    DigitalOcean

    Cloud

    —

    Tidak ada bukti institusional

    Alternatif infra

    2

    46

    Dickies

    Apparel

    —

    Distribusi/retailer Israel

    Non-tech referensi

    2

    47

    Elbit Systems

    Pertahanan

    —

    Perusahaan pertahanan Israel; kontrak ekspor luas

    Global/Referensi

    10

    48

    eToro

    Fintech/Web3

    Yoni Assia

    HQ Israel; pengguna global besar

    Referensi Web3/finansial

    3

    49

    Expedia Group

    Travel

    Peter Kern

    Pencantuman di isu permukiman (laporan)

    Dipakai publik luas di ID

    5

    50

    Fastly

    CDN/Cloud

    —

    Tidak ada bukti institusional

    Alternatif infra

    2

    51

    Figma

    Desain

    Dylan Field

    Tidak ada bukti institusional

    Dipakai desain

    1

    52

    Fireblocks

    Kripto infra

    Michael Shaulov

    Infrastruktur kustodi institusional

    Web3 infra; potensial dipakai

    4

    53

    First Media (Link Net)

    Fixed broadband

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    54

    Freshworks

    SaaS Enterprise

    —

    Tidak ada bukti institusional

    Dipakai enterprise

    2

    55

    Garuda Indonesia

    Maskapai

    —

    Maskapai nasional; tidak ada bukti institusional terkait Israel

    Dipakai luas di ID (transport udara)

    1

    56

    GitHub (Microsoft)

    Dev tooling

    Thomas Dohmke

    Di bawah Microsoft (lihat Microsoft)

    Dipakai di workflow

    3

    57

    GitLab

    DevOps

    Sid Sijbrandij

    Tidak ada bukti institusional

    Alternatif CI/CD

    2

    58

    GoPay

    Dompet digital

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    59

    Gojek

    Ride/On-demand

    Patrick Walujo

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    60

    Grab

    Ride/On-demand

    Anthony Tan

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    61

    Gramedia

    Buku/ritel

    —

    Tidak ada bukti institusional

    Dekat (penerbitan/ritel buku)

    1

    62

    H&M

    Fashion

    —

    Operasi ritel resmi Israel

    Non-tech referensi

    4

    63

    HP Inc.

    PC/Printer

    Enrique Lores

    Keterkaitan historis; bukti kini lebih lemah

    Dipakai umum; risiko rendah

    5

    64

    HPE

    TI enterprise

    Antonio Neri

    Keterkaitan historis infrastruktur pemerintah Israel

    Vendor enterprise; referensi

    7

    65

    Huawei

    Perangkat/Cloud

    —

    Tidak ada bukti institusional

    Dipakai luas

    2

    66

    IBM

    Riset/Cloud

    Arvind Krishna

    IBM Research Israel (Haifa, dll.)

    Referensi enterprise

    5

    67

    IKEA (Ingka)

    Ritel furnitur

    Jesper Brodin

    Operasi ritel Israel; investasi terkait

    Non-tech referensi

    4

    68

    Imperva

    Keamanan

    —

    Akar/operasi Israel

    Referensi enterprise

    4–5

    69

    IndiHome (Telkom)

    Fixed broadband

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    70

    Indosat Ooredoo Hutchison

    Seluler

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    71

    Independent Trucks

    Skate hardware

    —

    Tidak ada bukti institusional

    Dekat ekosistem skate

    1

    72

    Intel

    Semikonduktor

    Pat Gelsinger

    Fab Kiryat Gat & operasi besar

    Rantai perangkat; bergantung ekosistem

    6

    73

    Jenius (BTPN)

    Bank digital

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    74

    KFC

    F&B

    —

    Operasi/waralaba di Israel

    Non-tech referensi

    3

    75

    Kredivo

    Paylater

    —

    Tidak ada bukti institusional

    Digunakan konsumen ID

    1

    76

    Lazada (Alibaba)

    E-commerce

    James Dong

    Tidak ada bukti institusional

    Dipakai publik luas di ID

    2

    77

    Ledger

    Hardware wallet

    Pascal Gauthier

    Perusahaan hardware wallet; tidak ada bukti institusional Israel

    Dipakai/dirujuk di ekosistem Web3

    1

    78

    Lenovo

    Perangkat

    —

    Tidak ada bukti institusional

    Dipakai luas

    2

    79

    LINE Bank (Hana)

    Bank digital

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    80

    LinkAja

    Dompet digital

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    81

    Lockheed Martin

    Pertahanan

    Jim Taiclet

    Pemasok F-35 untuk Israel

    Global/Referensi

    9

    82

    L’Oréal

    Kecantikan

    Nicolas Hieronimus

    Operasi & R&D Israel; distributor lokal

    Konsumsi massal

    3

    83

    Mailchimp (Intuit)

    SaaS/Komunikasi

    —

    Tidak ada bukti institusional

    Dipakai stack komunikasi

    2

    84

    Marriott International

    Hotel/Akomodasi

    Anthony Capuano

    Operasi hotel di Israel (mis. Tel Aviv/Herzliya); kehadiran ritel

    Akomodasi global; relevan perjalanan

    3

    85

    Maxim

    Transport

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    86

    McDonald’s

    F&B

    Chris Kempczinski

    Akuisisi penuh waralaba Israel (2024)

    Non-tech referensi; mobilitas

    6

    87

    Meta (Facebook/Instagram/WhatsApp)

    Sosial/Ads

    Mark Zuckerberg

    R&D & akuisisi Onavo (Israel)

    Dipakai konten/komunitas

    4

    88

    Midtrans

    Payment gateway

    —

    Tidak ada bukti institusional

    Digunakan merchant ID

    1

    89

    Microsoft (Azure / M365 / LinkedIn / GitHub)

    Cloud/Office/Dev

    Satya Nadella; Brad Smith

    Region Israel; sorotan layanan terkait unit militer

    Dipakai (GitHub); mitigasi via multi-cloud

    7

    90

    Mobileye

    AutoTech/ADAS

    Amnon Shashua

    Perusahaan Israel (otomotif global)

    Referensi teknologi otomotif

    4

    91

    MyBluebird

    Transport

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    92

    Nestlé (Osem)

    F&B

    Mark Schneider

    Buyout Osem (Israel)

    Non-tech referensi

    5

    93

    Netlify

    Dev hosting

    Mathias Biilmann

    Tidak ada bukti institusional

    Alternatif/backup Vercel

    1

    94

    Netflix

    Streaming

    —

    Tidak ada bukti institusional

    Dipakai luas

    2

    95

    Notion

    Docs/PM

    Ivan Zhao

    Tidak ada bukti institusional

    Dipakai dokumentasi

    1

    96

    NSO Group

    Spyware

    —

    Pegasus; ekspor diawasi MoD Israel

    Global/Referensi kebijakan

    10

    97

    NVIDIA

    AI/Networking

    Jensen Huang

    Akuisisi Mellanox (Israel) → R&D/jaringan

    Rantai AI/DC; bergantung ekosistem

    6

    98

    Nike

    Footwear

    —

    Kehadiran/ritel Israel

    Non-tech referensi

    2

    99

    OVO

    Dompet digital

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    100

    OpenAI / ChatGPT

    AI asisten

    Sam Altman

    Tidak ada bukti institusional Israel

    Dipakai harian oleh Prof. NOTA

    1

    101

    OPPO

    Perangkat

    —

    Tidak ada bukti institusional

    Dipakai luas

    2

    102

    Oracle (OCI)

    Cloud

    Safra Catz

    DC bawah tanah di Yerusalem; ekspansi

    Dipertimbangkan/alternatif cloud

    6

    103

    Optimism (OP Stack)

    L2

    —

    Tidak ada bukti institusional

    Dirujuk

    1

    104

    Palantir

    Data/AI pemerintah

    Alex Karp

    Kemitraan strategis dengan Kemenhan Israel

    Global/Referensi kebijakan

    9

    105

    Palo Alto Networks

    Keamanan

    Nikesh Arora

    R&D/akuisisi Israel (Demisto)

    Dipakai enterprise di ID

    5

    106

    PayPal

    Pembayaran

    —

    Tidak ada bukti institusional

    Dipakai pembayaran global

    2

    107

    PepsiCo (SodaStream)

    Minuman/alat

    Ramon Laguarta

    Akuisisi SodaStream (Israel)

    Non-tech referensi

    5

    108

    Protocol Labs (IPFS/Filecoin)

    Storage/Web3

    Juan Benet

    Tidak ada bukti institusional

    Dipakai/direncanakan

    1

    109

    PRINCIPLE

    Fashion (kolab)

    —

    Brand/kolaborasi Prof. NOTA

    Kolaborasi

    1

    110

    Powell-Peralta

    Skate hardware

    —

    Tidak ada bukti institusional

    Dekat ekosistem skate

    1

    111

    QuickNode

    Web3 infra

    —

    Tidak ada bukti institusional

    Alternatif RPC

    1

    112

    Radware

    Keamanan

    —

    Akar/operasi Israel

    Referensi enterprise

    4–5

    113

    RTX (Raytheon)

    Pertahanan

    Christopher Calio

    Pemasok Iron Dome/David’s Sling

    Global/Referensi

    9

    114

    Samsung

    Perangkat

    —

    Tidak ada bukti institusional

    Dipakai luas

    2

    115

    Santa Cruz

    Skate

    —

    Tidak ada bukti institusional

    Dekat ekosistem skate

    1

    116

    SAP (incl. Gigya)

    SaaS/IDM

    Christian Klein

    SAP Labs Israel; akuisisi Gigya

    Dipakai enterprise

    4

    117

    SeaBank

    Bank digital

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    118

    SentinelOne

    Keamanan

    —

    Akar/operasi Israel

    Referensi enterprise

    4–5

    119

    ServiceNow

    SaaS Enterprise

    Bill McDermott

    Tidak ada bukti institusional

    Dipakai enterprise

    2

    120

    Shopee (Sea)

    E-commerce/Pay

    Chris Feng

    Tidak ada bukti institusional

    Dipakai publik luas di ID

    2

    121

    ShopeePay

    Dompet digital

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    122

    Siemens

    Industrial/Automation

    Roland Busch

    Operasi & proyek infrastruktur di Israel (umum)

    Referensi manufaktur/otomasi

    3

    123

    SKATESHOP.ID

    Skate retail

    —

    IP/operasi Prof. NOTA

    Operasi internal

    1

    124

    Snowflake

    Data Cloud

    Frank Slootman

    R&D/pusat tim di Israel; kemitraan enterprise

    Dipertimbangkan untuk data warehousing

    4

    125

    Spotify

    Musik

    —

    Tidak ada bukti institusional

    Dipakai luas

    2

    126

    Stripe

    Pembayaran

    —

    Tidak ada bukti institusional

    Dipakai pembayaran global

    2

    127

    Supabase

    Backend

    Paul Copplestone

    Tidak ada bukti institusional

    Alternatif backend

    1

    128

    Smartfren

    Seluler

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    129

    Telkomsel

    Seluler

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    130

    Tiket.com

    Travel

    George Hendrata

    Tidak ada bukti institusional

    Dipakai publik luas di ID

    1

    131

    Toyota

    Otomotif

    Koji Sato

    Kehadiran ritel/penjualan di Israel via distributor; tanpa kontrak gov

    Mobil umum di ID; relevan manufaktur/logistik

    2

    132

    TSMC

    Semikonduktor

    C. C. Wei

    Jejak Israel tidak material; pemasok global

    Rantai pasok chip

    2

    133

    Traveloka

    Travel

    Ferry Unardi

    Tidak ada bukti institusional

    Dipakai publik luas di ID

    1

    134

    TripAdvisor

    Travel

    Matt Goldberg

    Pencantuman isu permukiman (laporan)

    Dipakai publik luas di ID

    5

    135

    Twilio

    Komunikasi

    —

    Tidak ada bukti institusional

    Dipakai stack komunikasi

    2

    136

    Unilever (incl. Ben & Jerry’s Israel)

    FMCG

    Hein Schumacher

    Operasi Israel; kontroversi distribusi wilayah sengketa

    Konsumsi massal

    4

    137

    Vans

    Footwear

    —

    Kehadiran/ritel Israel

    Non-tech referensi

    2

    138

    Vercel / Next.js

    Cloud/Dev

    Guillermo Rauch

    Foto/rapat dengan PM Israel; tanpa kontrak gov

    Dipakai/terkait ekosistem front-end

    3

    139

    vivo

    Perangkat

    —

    Tidak ada bukti institusional

    Dipakai luas

    2

    140

    Workday

    HCM

    Carl Eschenbach

    Tidak ada bukti institusional

    Dipakai enterprise

    2

    141

    Wiz

    Keamanan cloud

    Assaf Rappaport

    Unicorn Israel; akuisisi besar

    Referensi security/cloud

    5

    142

    X Corp (Twitter/X)

    Sosial

    Elon Musk

    Tidak ada bukti institusional

    Dipakai komunikasi publik

    2

    143

    Xendit

    Payment gateway

    —

    Tidak ada bukti institusional

    Digunakan merchant ID

    1

    144

    Xiaomi

    Perangkat

    —

    Tidak ada bukti institusional

    Dipakai luas

    2

    145

    XL Axiata

    Seluler

    —

    Tidak ada bukti institusional

    Dipakai luas di ID

    1

    146

    Zara (Inditex)

    Fashion

    —

    Flagship besar Israel (2025)

    Non-tech referensi

    4

    147

    Zscaler

    Keamanan

    Jay Chaudhry

    Operasi global; tanpa keterkaitan gov spesifik

    Referensi enterprise

    3

    GLITCH RIWAYAT TRANSAKSI 30S2K25

    We don't belong in your reality, your real life. In your reality, your real life, you can merely meet our avatars in any version. So, stay alert and beware of scams!

    Riwayat Transaksi — Glitch 30 September 2025

    Individu (Prof. NOTA)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    2025-09-30

    ...

    ...


    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    Tanggal
    Kategori
    Deskripsi
    Jumlah (Rp)
    BI-FAST (Rp)
    Saldo (Rp)

    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 . 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.


    ...

    2,500

    1,747,474

    2025-09-30

    Masuk Stabil

    Pelunasan piutang kalau lancar

    18,255,026

    2,500

    20,000,000

    2025-09-30

    ...

    ...

    ...

    2,500

    2,449,747

    2025-10-01

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    2025-10-01

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -8,358,743

    2025-11-01

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    2025-11-01

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -6,101,502

    2025-12-01

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    2025-12-01

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -11,775,333

    2026-01-01

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    2026-01-01

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -13,976,882

    2026-02-01

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,673,800

    2026-02-01

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -7,789,079

    2026-03-01

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    2026-03-01

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -8,797,011

    Giro (Prof. NOTA Inc.)

    Riwayat Transaksi — Oktober 2025

    Individu (Prof. NOTA)

    Giro (Prof. NOTA Inc.)

    Riwayat Transaksi — November 2025

    Individu (Prof. NOTA)

    Giro (Prof. NOTA Inc.)

    Riwayat Transaksi — Desember 2025

    Individu (Prof. NOTA)

    Giro (Prof. NOTA Inc.)

    Riwayat Transaksi — Januari 2026

    Individu (Prof. NOTA)

    Giro (Prof. NOTA Inc.)

    Riwayat Transaksi — Februari 2026

    Individu (Prof. NOTA)

    Giro (Prof. NOTA Inc.)

    Riwayat Transaksi — Maret 2026

    Individu (Prof. NOTA)

    Giro (Prof. NOTA Inc.)

    Prof. NOTA

    2025-09-30

    Masuk Stabil

    Pelunasan piutang kalau lancar

    97,552,753

    2,500

    100,000,000

    -1,373,711

    2,500

    18,623,789

    2025-10-02

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -442,905

    2,500

    18,178,384

    2025-10-03

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -394,992

    2,500

    17,780,892

    2025-10-04

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -456,861

    2,500

    17,321,531

    2025-10-05

    Masuk Stabil

    Retainer pribadi (gaji/fee rutin)

    16,272,159

    2,500

    33,591,190

    2025-10-06

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -486,063

    2,500

    33,102,627

    2025-10-06

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,277,094

    2,500

    34,377,221

    2025-10-07

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,438,866

    2,500

    35,439,612

    2025-10-07

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -373,975

    2,500

    33,998,246

    2025-10-08

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -432,870

    2,500

    35,001,742

    2025-10-08

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,105,568

    2,500

    36,104,810

    2025-10-09

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -355,684

    2,500

    35,746,626

    2025-10-10

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,966,278

    2,500

    33,777,848

    2025-10-11

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -373,119

    2,500

    33,402,229

    2025-10-12

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,139,171

    2,500

    34,229,592

    2025-10-12

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -309,308

    2,500

    33,087,921

    2025-10-13

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -434,937

    2,500

    33,789,655

    2025-10-14

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -320,908

    2,500

    33,466,247

    2025-10-15

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -2,260,325

    2,500

    31,203,422

    2025-10-16

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -374,338

    2,500

    30,826,584

    2025-10-17

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -377,723

    2,500

    30,446,361

    2025-10-18

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -322,238

    2,500

    30,121,623

    2025-10-20

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -309,183

    2,500

    29,809,940

    2025-10-21

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -303,034

    2,500

    29,504,406

    2025-10-22

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -352,187

    2,500

    29,149,719

    2025-10-22

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,248,663

    2,500

    30,395,882

    2025-10-23

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -362,045

    2,500

    30,031,337

    2025-10-24

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -316,846

    2,500

    29,711,991

    2025-10-25

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,872,088

    2,500

    27,837,403

    2025-10-26

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -397,311

    2,500

    27,437,592

    2025-10-27

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -428,058

    2,500

    27,007,034

    2025-10-28

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -353,661

    2,500

    26,650,873

    2025-10-29

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -474,552

    2,500

    26,173,821

    2025-10-29

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,173,013

    2,500

    27,344,334

    2025-10-30

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -343,339

    2,500

    26,998,495

    2025-10-31

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -338,137

    2,500

    26,657,858

    2,500

    91,638,757

    2025-10-03

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,861,507

    2,500

    86,774,750

    2025-10-05

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    31,104,069

    2,500

    117,876,319

    2025-10-06

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,525,653

    2,500

    113,348,166

    2025-10-07

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,741,539

    2,500

    109,604,127

    2025-10-08

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,662,118

    2,500

    104,939,509

    2025-10-10

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -13,978,489

    2,500

    90,958,520

    2025-10-11

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,811,818

    2,500

    86,144,202

    2025-10-11

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,741,572

    2,500

    93,883,274

    2025-10-12

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,541,242

    2,500

    89,339,532

    2025-10-12

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,291,580

    2,500

    99,628,612

    2025-10-13

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,048,978

    2,500

    96,577,134

    2025-10-13

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,363,427

    2,500

    103,938,061

    2025-10-14

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,655,333

    2,500

    111,590,894

    2025-10-15

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -13,998,393

    2,500

    97,590,001

    2025-10-16

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,437,000

    2,500

    108,024,501

    2025-10-18

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,933,236

    2,500

    103,088,765

    2025-10-18

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,249,440

    2,500

    113,335,705

    2025-10-20

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    34,172,350

    2,500

    147,505,555

    2025-10-22

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,601,307

    2,500

    142,901,748

    2025-10-22

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,434,710

    2,500

    151,333,958

    2025-10-23

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,726,750

    2,500

    147,604,708

    2025-10-24

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,400,178

    2,500

    158,002,386

    2025-10-25

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -14,201,966

    2,500

    143,797,920

    2025-10-26

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,708,498

    2,500

    139,086,922

    2025-10-26

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    9,409,427

    2,500

    148,493,849

    2025-10-28

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,888,746

    2,500

    157,380,095

    2025-10-29

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,298,007

    2,500

    154,079,588

    -1,927,161

    2,500

    24,728,197

    2025-11-02

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -351,957

    2,500

    24,373,740

    2025-11-03

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -378,551

    2,500

    23,992,689

    2025-11-04

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -338,573

    2,500

    23,651,616

    2025-11-05

    Masuk Stabil

    Retainer pribadi (gaji/fee rutin)

    17,874,352

    2,500

    41,523,468

    2025-11-06

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -491,684

    2,500

    41,029,284

    2025-11-07

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -419,014

    2,500

    40,607,770

    2025-11-08

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -428,010

    2,500

    40,177,260

    2025-11-09

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -472,064

    2,500

    39,702,696

    2025-11-10

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -2,192,827

    2,500

    37,507,369

    2025-11-11

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -300,141

    2,500

    37,204,728

    2025-11-12

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -365,324

    2,500

    36,836,904

    2025-11-12

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,045,993

    2,500

    37,880,397

    2025-11-13

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -362,842

    2,500

    37,515,055

    2025-11-14

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -330,319

    2,500

    37,182,236

    2025-11-14

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,341,208

    2,500

    38,520,944

    2025-11-15

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -2,216,467

    2,500

    36,301,977

    2025-11-16

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -386,087

    2,500

    35,913,390

    2025-11-17

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -450,930

    2,500

    35,459,960

    2025-11-17

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,271,675

    2,500

    36,729,135

    2025-11-18

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -464,537

    2,500

    36,262,098

    2025-11-19

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -479,210

    2,500

    35,780,388

    2025-11-20

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -358,511

    2,500

    35,419,377

    2025-11-21

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -386,042

    2,500

    35,030,835

    2025-11-22

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -354,340

    2,500

    34,673,995

    2025-11-23

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -453,906

    2,500

    34,217,589

    2025-11-23

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,084,244

    2,500

    35,299,333

    2025-11-24

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -316,045

    2,500

    34,980,788

    2025-11-25

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,954,153

    2,500

    33,024,135

    2025-11-26

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -336,679

    2,500

    32,684,956

    2025-11-27

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -464,359

    2,500

    32,218,097

    2025-11-28

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -447,874

    2,500

    31,767,723

    2025-11-29

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -454,241

    2,500

    31,310,982

    2025-11-29

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,197,621

    2,500

    32,506,103

    2025-11-30

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -398,938

    2,500

    32,104,665

    2025-11-30

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,351,330

    2,500

    33,453,495

    2,500

    147,975,586

    2025-11-02

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,012,400

    2,500

    158,985,486

    2025-11-03

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,731,364

    2,500

    166,714,350

    2025-11-04

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,763,965

    2,500

    162,947,885

    2025-11-04

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    9,069,216

    2,500

    172,014,601

    2025-11-05

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    25,922,113

    2,500

    197,934,214

    2025-11-07

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,470,195

    2,500

    194,461,519

    2025-11-08

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,494,531

    2,500

    204,953,550

    2025-11-09

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,372,569

    2,500

    216,323,619

    2025-11-10

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -7,064,856

    2,500

    209,256,263

    2025-11-11

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,237,488

    2,500

    206,016,275

    2025-11-11

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,745,410

    2,500

    214,759,185

    2025-11-12

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,322,405

    2,500

    210,434,280

    2025-11-13

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,781,916

    2,500

    206,649,864

    2025-11-14

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,891,029

    2,500

    214,538,393

    2025-11-15

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -7,070,902

    2,500

    207,464,991

    2025-11-16

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,071,596

    2,500

    203,390,895

    2025-11-17

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,689,177

    2,500

    199,699,218

    2025-11-18

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,765,959

    2,500

    194,930,759

    2025-11-19

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,453,458

    2,500

    190,474,801

    2025-11-20

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    32,033,874

    2,500

    222,506,175

    2025-11-24

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,941,048

    2,500

    217,562,627

    2025-11-24

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,862,342

    2,500

    229,422,469

    2025-11-25

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -9,065,973

    2,500

    220,353,996

    2025-11-26

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,855,858

    2,500

    216,495,638

    2025-11-26

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,463,266

    2,500

    227,956,404

    2025-11-29

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    9,998,071

    2,500

    237,951,975

    2025-11-30

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,766,865

    2,500

    233,182,610

    -1,483,877

    2,500

    31,967,118

    2025-12-02

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -339,160

    2,500

    31,625,458

    2025-12-02

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,016,027

    2,500

    32,638,985

    2025-12-03

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -429,123

    2,500

    32,207,362

    2025-12-04

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -378,310

    2,500

    31,826,552

    2025-12-05

    Masuk Stabil

    Retainer pribadi (gaji/fee rutin)

    19,645,422

    2,500

    51,469,474

    2025-12-06

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -441,874

    2,500

    51,025,100

    2025-12-07

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -335,825

    2,500

    50,686,775

    2025-12-07

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,076,333

    2,500

    51,760,608

    2025-12-08

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -386,069

    2,500

    51,372,039

    2025-12-08

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,283,328

    2,500

    52,652,867

    2025-12-09

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -327,346

    2,500

    52,323,021

    2025-12-09

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,185,948

    2,500

    53,506,469

    2025-12-10

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,118,354

    2,500

    52,385,615

    2025-12-11

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -352,768

    2,500

    52,030,347

    2025-12-12

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -493,856

    2,500

    51,533,991

    2025-12-13

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -492,230

    2,500

    51,039,261

    2025-12-15

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,517,283

    2,500

    49,519,478

    2025-12-16

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -441,923

    2,500

    49,075,055

    2025-12-16

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,380,152

    2,500

    50,452,707

    2025-12-17

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -393,879

    2,500

    50,056,328

    2025-12-18

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -418,623

    2,500

    49,635,205

    2025-12-19

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -421,756

    2,500

    49,210,949

    2025-12-20

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -358,775

    2,500

    48,849,674

    2025-12-21

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -393,406

    2,500

    48,453,768

    2025-12-22

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -420,667

    2,500

    48,030,601

    2025-12-23

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -349,932

    2,500

    47,678,169

    2025-12-24

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -359,521

    2,500

    47,316,148

    2025-12-25

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,199,001

    2,500

    46,114,647

    2025-12-26

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -465,019

    2,500

    45,647,128

    2025-12-27

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -468,344

    2,500

    45,176,284

    2025-12-28

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -361,728

    2,500

    44,812,056

    2025-12-29

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -387,419

    2,500

    44,422,137

    2025-12-29

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,310,557

    2,500

    45,730,194

    2025-12-30

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -338,975

    2,500

    45,388,719

    2025-12-31

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -322,537

    2,500

    45,063,682

    2,500

    221,404,777

    2025-12-02

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,716,945

    2,500

    230,119,222

    2025-12-03

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,741,208

    2,500

    225,375,514

    2025-12-05

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    30,045,149

    2,500

    255,418,163

    2025-12-06

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,964,131

    2,500

    250,451,532

    2025-12-07

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,456,000

    2,500

    246,993,032

    2025-12-07

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,794,925

    2,500

    258,785,457

    2025-12-08

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,086,428

    2,500

    266,869,385

    2025-12-09

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,855,964

    2,500

    277,722,849

    2025-12-10

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -13,506,962

    2,500

    264,213,387

    2025-12-11

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,321,665

    2,500

    260,889,222

    2025-12-11

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,221,273

    2,500

    269,107,995

    2025-12-12

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,734,619

    2,500

    280,840,114

    2025-12-15

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -13,905,891

    2,500

    266,931,723

    2025-12-17

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,631,639

    2,500

    262,297,584

    2025-12-19

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,299,985

    2,500

    257,995,099

    2025-12-20

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    30,683,716

    2,500

    288,676,315

    2025-12-21

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    9,975,725

    2,500

    298,649,540

    2025-12-22

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,170,332

    2,500

    294,476,708

    2025-12-25

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -14,986,468

    2,500

    279,487,740

    2025-12-26

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,808,969

    2,500

    275,676,271

    2025-12-26

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,506,748

    2,500

    286,180,519

    2025-12-28

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,880,311

    2,500

    282,297,708

    2025-12-28

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,456,285

    2,500

    292,751,493

    2025-12-29

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,314,912

    2,500

    289,434,081

    2025-12-29

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,050,168

    2,500

    300,481,749

    2025-12-30

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,477,500

    2,500

    297,001,749

    2025-12-31

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,765,094

    2,500

    292,234,155

    -2,435,605

    2,500

    42,625,577

    2026-01-02

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -465,938

    2,500

    42,157,139

    2026-01-03

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -304,552

    2,500

    41,850,087

    2026-01-04

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -303,361

    2,500

    41,544,226

    2026-01-05

    Masuk Stabil

    Retainer pribadi (gaji/fee rutin)

    17,767,222

    2,500

    59,308,948

    2026-01-06

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -422,040

    2,500

    58,884,408

    2026-01-06

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,270,742

    2,500

    60,152,650

    2026-01-07

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -442,163

    2,500

    59,707,987

    2026-01-08

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -464,699

    2,500

    59,240,788

    2026-01-09

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -316,941

    2,500

    58,921,347

    2026-01-10

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,075,893

    2,500

    57,842,954

    2026-01-11

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -397,650

    2,500

    57,442,804

    2026-01-13

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -305,753

    2,500

    57,134,551

    2026-01-13

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,351,581

    2,500

    58,483,632

    2026-01-14

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -452,015

    2,500

    58,029,117

    2026-01-15

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -2,140,143

    2,500

    55,886,474

    2026-01-16

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -316,125

    2,500

    55,567,849

    2026-01-17

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -356,540

    2,500

    55,208,809

    2026-01-18

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -373,564

    2,500

    54,832,745

    2026-01-18

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,118,807

    2,500

    55,949,052

    2026-01-19

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -358,984

    2,500

    55,587,568

    2026-01-19

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,065,566

    2,500

    56,650,634

    2026-01-20

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -471,214

    2,500

    56,176,920

    2026-01-21

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -357,042

    2,500

    55,817,378

    2026-01-21

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,304,611

    2,500

    57,119,489

    2026-01-22

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -310,277

    2,500

    56,806,712

    2026-01-23

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -499,815

    2,500

    56,304,397

    2026-01-24

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -313,375

    2,500

    55,988,522

    2026-01-25

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,552,026

    2,500

    54,433,996

    2026-01-26

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -392,478

    2,500

    54,039,018

    2026-01-27

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -333,656

    2,500

    53,702,862

    2026-01-28

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -470,817

    2,500

    53,229,545

    2026-01-28

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,375,027

    2,500

    54,602,072

    2026-01-29

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -429,092

    2,500

    54,170,480

    2026-01-30

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -413,965

    2,500

    53,754,015

    2026-01-31

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -333,953

    2,500

    53,417,562

    2,500

    278,254,773

    2026-01-02

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,773,013

    2,500

    286,025,286

    2026-01-03

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,924,382

    2,500

    293,947,168

    2026-01-04

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,558,365

    2,500

    290,386,303

    2026-01-05

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    34,019,867

    2,500

    324,403,670

    2026-01-06

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,575,749

    2,500

    320,825,421

    2026-01-08

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,114,561

    2,500

    316,708,360

    2026-01-09

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,100,801

    2,500

    313,605,059

    2026-01-10

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -11,590,779

    2,500

    302,011,780

    2026-01-11

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,663,343

    2,500

    297,345,937

    2026-01-11

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,713,207

    2,500

    305,056,644

    2026-01-12

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,495,303

    2,500

    313,549,447

    2026-01-13

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,585,215

    2,500

    308,961,732

    2026-01-14

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,097,023

    2,500

    316,056,255

    2026-01-15

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -10,151,759

    2,500

    305,901,996

    2026-01-16

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,855,212

    2,500

    302,044,284

    2026-01-16

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,558,617

    2,500

    312,600,401

    2026-01-18

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,260,062

    2,500

    323,857,963

    2026-01-19

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,072,856

    2,500

    320,782,607

    2026-01-20

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    32,759,397

    2,500

    353,539,504

    2026-01-23

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,014,019

    2,500

    350,522,985

    2026-01-23

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,887,642

    2,500

    361,408,127

    2026-01-25

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -12,229,050

    2,500

    349,176,577

    2026-01-27

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,256,054

    2,500

    344,918,023

    2026-01-28

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,913,273

    2,500

    340,002,250

    2026-01-29

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,144,440

    2,500

    336,855,310

    2026-01-30

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    9,185,984

    2,500

    346,038,794

    2026-01-31

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,625,834

    2,500

    357,662,128

    2,500

    51,741,262

    2026-02-02

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -395,543

    2,500

    51,343,219

    2026-02-03

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -476,836

    2,500

    50,863,883

    2026-02-04

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -457,890

    2,500

    50,403,493

    2026-02-05

    Masuk Stabil

    Retainer pribadi (gaji/fee rutin)

    19,544,079

    2,500

    69,945,072

    2026-02-06

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -498,949

    2,500

    69,443,623

    2026-02-06

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,305,760

    2,500

    70,746,883

    2026-02-07

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -496,637

    2,500

    70,247,746

    2026-02-08

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -306,974

    2,500

    69,938,272

    2026-02-09

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -336,484

    2,500

    69,599,288

    2026-02-10

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -2,092,702

    2,500

    67,504,086

    2026-02-11

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -321,737

    2,500

    67,179,849

    2026-02-11

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,489,827

    2,500

    68,667,176

    2026-02-12

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -325,429

    2,500

    68,339,247

    2026-02-13

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -487,980

    2,500

    67,848,767

    2026-02-14

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -426,009

    2,500

    67,420,258

    2026-02-15

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -2,218,865

    2,500

    65,198,893

    2026-02-16

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -305,673

    2,500

    64,890,720

    2026-02-17

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -453,209

    2,500

    64,435,011

    2026-02-18

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -348,781

    2,500

    64,083,730

    2026-02-18

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,335,851

    2,500

    65,417,081

    2026-02-19

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -325,086

    2,500

    65,089,495

    2026-02-20

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -355,917

    2,500

    64,731,078

    2026-02-21

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -444,954

    2,500

    64,283,624

    2026-02-22

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -494,018

    2,500

    63,787,106

    2026-02-23

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -456,102

    2,500

    63,328,504

    2026-02-23

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,431,737

    2,500

    64,757,741

    2026-02-24

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -331,321

    2,500

    64,423,920

    2026-02-24

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,211,352

    2,500

    65,632,772

    2026-02-25

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,490,328

    2,500

    64,139,944

    2026-02-26

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -408,859

    2,500

    63,728,585

    2026-02-26

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,057,327

    2,500

    64,783,412

    2026-02-27

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -429,979

    2,500

    64,350,933

    2026-02-28

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -350,388

    2,500

    63,998,045

    2,500

    349,870,549

    2026-02-02

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,815,104

    2,500

    346,052,945

    2026-02-02

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,001,231

    2,500

    356,051,676

    2026-02-03

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    9,588,590

    2,500

    365,637,766

    2026-02-04

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,463,190

    2,500

    362,172,076

    2026-02-05

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    26,529,102

    2,500

    388,698,678

    2026-02-06

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,062,381

    2,500

    384,633,797

    2026-02-06

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    9,232,434

    2,500

    393,863,731

    2026-02-08

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,227,872

    2,500

    389,633,359

    2026-02-08

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    9,327,766

    2,500

    398,958,625

    2026-02-09

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,720,592

    2,500

    406,676,717

    2026-02-10

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -10,989,792

    2,500

    395,684,425

    2026-02-11

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,708,782

    2,500

    404,390,707

    2026-02-12

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,442,005

    2,500

    399,946,202

    2026-02-14

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,725,303

    2,500

    395,218,399

    2026-02-14

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,657,185

    2,500

    406,873,084

    2026-02-15

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -8,006,827

    2,500

    398,863,757

    2026-02-17

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,468,162

    2,500

    409,329,419

    2026-02-18

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,776,292

    2,500

    404,550,627

    2026-02-20

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    34,483,461

    2,500

    439,031,588

    2026-02-21

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,657,583

    2,500

    446,686,671

    2026-02-22

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,408,816

    2,500

    442,275,355

    2026-02-24

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,577,952

    2,500

    437,694,903

    2026-02-25

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -10,684,849

    2,500

    427,007,554

    2026-02-26

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,014,414

    2,500

    423,990,640

    2026-02-26

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,113,690

    2,500

    432,101,830

    2026-02-27

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,768,315

    2,500

    427,331,015

    2026-02-28

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,816,407

    2,500

    423,512,108

    -1,646,752

    2,500

    51,768,310

    2026-03-03

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -434,825

    2,500

    51,330,985

    2026-03-03

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,349,486

    2,500

    52,677,971

    2026-03-04

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -495,514

    2,500

    52,179,957

    2026-03-05

    Masuk Stabil

    Retainer pribadi (gaji/fee rutin)

    16,456,413

    2,500

    68,633,870

    2026-03-06

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -320,543

    2,500

    68,310,827

    2026-03-06

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,265,927

    2,500

    69,574,254

    2026-03-07

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -484,162

    2,500

    69,087,592

    2026-03-08

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -491,911

    2,500

    68,593,181

    2026-03-08

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,080,126

    2,500

    69,670,807

    2026-03-09

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -481,799

    2,500

    69,186,508

    2026-03-10

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,984,205

    2,500

    67,199,803

    2026-03-11

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -341,134

    2,500

    66,856,169

    2026-03-11

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,384,215

    2,500

    68,237,884

    2026-03-12

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -499,564

    2,500

    67,735,820

    2026-03-13

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -458,741

    2,500

    67,274,579

    2026-03-14

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -367,590

    2,500

    66,904,489

    2026-03-15

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -2,138,536

    2,500

    64,763,453

    2026-03-16

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -481,279

    2,500

    64,279,674

    2026-03-16

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,402,789

    2,500

    65,679,963

    2026-03-17

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -311,789

    2,500

    65,365,674

    2026-03-18

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -419,279

    2,500

    64,943,895

    2026-03-19

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -483,561

    2,500

    64,457,834

    2026-03-20

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -376,186

    2,500

    64,079,148

    2026-03-21

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -457,679

    2,500

    63,618,969

    2026-03-22

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -456,254

    2,500

    63,160,215

    2026-03-23

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -470,927

    2,500

    62,686,788

    2026-03-24

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -372,536

    2,500

    62,311,752

    2026-03-25

    Keluar Stabil

    Tagihan rutin (listrik/internet/kartu kredit/asuransi)

    -1,488,823

    2,500

    60,820,429

    2026-03-26

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -375,013

    2,500

    60,442,916

    2026-03-27

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -421,317

    2,500

    60,019,099

    2026-03-28

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -355,799

    2,500

    59,660,800

    2026-03-29

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -442,203

    2,500

    59,216,097

    2026-03-30

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -328,074

    2,500

    58,885,523

    2026-03-30

    Masuk Labil

    Fee proyek/royalti/transfer variatif

    1,401,588

    2,500

    60,284,611

    2026-03-31

    Keluar Labil

    Belanja harian & kebutuhan variatif

    -379,110

    2,500

    59,903,001

    2,500

    348,862,617

    2026-03-02

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,185,783

    2,500

    345,674,334

    2026-03-02

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,092,512

    2,500

    355,764,346

    2026-03-03

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,752,035

    2,500

    367,513,881

    2026-03-04

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,994,560

    2,500

    362,516,821

    2026-03-05

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    36,276,850

    2,500

    398,791,171

    2026-03-07

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,009,946

    2,500

    395,778,725

    2026-03-08

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,898,963

    2,500

    391,877,262

    2026-03-10

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -14,609,733

    2,500

    377,265,029

    2026-03-11

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,252,542

    2,500

    384,515,071

    2026-03-12

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,029,283

    2,500

    381,483,288

    2026-03-13

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    11,020,169

    2,500

    392,500,957

    2026-03-15

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -10,800,554

    2,500

    381,697,903

    2026-03-17

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,670,761

    2,500

    378,024,642

    2026-03-20

    Masuk Stabil

    Pembayaran kontrak/retainer klien

    29,107,064

    2,500

    407,129,206

    2026-03-21

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,536,121

    2,500

    402,590,585

    2026-03-21

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,831,085

    2,500

    410,419,170

    2026-03-23

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,534,891

    2,500

    406,881,779

    2026-03-23

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,480,492

    2,500

    415,359,771

    2026-03-24

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,752,348

    2,500

    424,109,619

    2026-03-25

    Keluar Stabil

    Gaji/sewa/pajak/langganan bisnis (rutin)

    -9,196,372

    2,500

    414,910,747

    2026-03-26

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,452,995

    2,500

    410,455,252

    2026-03-26

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    10,707,577

    2,500

    421,160,329

    2026-03-28

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,966,568

    2,500

    417,191,261

    2026-03-28

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    7,838,763

    2,500

    425,027,524

    2026-03-29

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -4,568,633

    2,500

    420,456,391

    2026-03-30

    Keluar Labil

    Pembayaran vendor/operasional variatif

    -3,074,423

    2,500

    417,379,468

    2026-03-30

    Masuk Labil

    Pelunasan invoice proyek (variatif)

    8,347,266

    2,500

    425,724,234

    HASIL PELATIHAN UKBI (Uji Kemahiran Berbahasa Indonesia)