Skip to content

MICROBA USER MANUAL · CHAPTER 01

What Is MICROBA?

MICROBA is a Living Platform that connects identity, knowledge, products, community, commerce, sponsorship, and member benefits within one digital ecosystem. MICROBA is not designed only as an online store, an affiliate programme, or a…

Version 1.0ManualUpdated 11 August 2026

1.1 Introduction

MICROBA is a Living Platform that connects identity, knowledge, products, community, commerce, sponsorship, and member benefits within one digital ecosystem.

MICROBA is not designed only as an online store, an affiliate programme, or a collection of separate applications. Its capabilities work together around one consistent member identity while remaining responsible for their own functions.

A person may join MICROBA simply to learn, purchase products, use member capabilities, and participate in the ecosystem. A member is not required to become an affiliate, recruit other people, or have a sponsor in order to purchase.

Members who choose to introduce MICROBA directly to others may participate in HIVE, MICROBA's direct sponsorship capability. Other capabilities, including Product, Commerce, SA, Knowledge, and Profile, operate independently according to their own rules.

The objective is a platform in which participation can remain simple for the member while the system maintains clear identity, transaction history, ownership, eligibility, and reconciliation in the background.

1.2 Core Principles

1.2.1 One Person, One Living Identity

Each member has one canonical MICROBA identity.

That identity connects the member to the capabilities they use, including Profile, Product, Commerce, HIVE, SA, and Knowledge.

Members should not need separate identities for different parts of MICROBA.

The platform is designed to discourage duplicate or dummy identities. Identity verification and administrative controls may be used where required to protect the integrity of membership, sponsorship, rewards, and transactions.

1.2.2 Membership Is Not Affiliate Participation

Becoming a MICROBA member does not automatically make someone an affiliate.

A member may maintain a Profile, purchase products, participate in Product experiences, learn through Knowledge, receive and use eligible SA benefits, and use other member capabilities without ever sponsoring another person.

HIVE participation is an additional capability for members who choose to introduce MICROBA directly to others.

1.2.3 A Sponsor Is Not Required to Purchase

MICROBA allows direct purchasing.

A customer or member may discover MICROBA independently and purchase without an affiliate or sponsor.

If no valid sponsor relationship exists, the purchase proceeds without a sponsorship commission.

If a genuine direct sponsor relationship exists and satisfies the applicable HIVE rules, the eligible purchase may generate a direct sponsorship commission.

MICROBA must not automatically assign an unrelated sponsor merely because a purchaser does not have one.

1.2.4 Genuine Activity Comes Before Network Depth

MICROBA's sponsorship model is based on direct relationships and eligible sales rather than multi-generation commission chains.

HIVE is designed as a single-level direct sponsorship model.

A sponsor may receive a benefit from eligible purchases made by the member or customer they directly introduced, subject to the HIVE rules.

A sponsor does not receive a commission merely because people exist further down another person's referral relationships.

1.2.5 Commerce Is the Commercial Transaction Authority

Capabilities that require payment submit commercial activity to Commerce.

Commerce owns the commercial transaction lifecycle, including orders, payment processing, transaction status, applicable commercial calculations, and related monitoring.

Other capabilities should not independently recreate payment or order logic.

1.2.6 SA and Sponsorship Are Separate Mechanisms

SA is not the same as a direct sponsorship commission.

Sponsorship relates to eligible direct sponsor activity.

SA follows its own provision, entitlement, circulation, Treasury, transfer, usage, and recycling rules.

The system may connect both mechanisms to Commerce events, but their ledgers and responsibilities remain distinguishable.

1.2.7 Complexity Belongs Behind the Experience

MICROBA may perform detailed calculations, reconciliation, transaction recording, and lifecycle management in the background.

The member-facing experience should remain understandable.

Where possible, members and ordinary administrators should see clear states and meaningful numbers rather than accounting terminology or unnecessary technical detail.

1.3 Membership and Identity

Membership begins with the creation of a MICROBA Living Identity.

A Living Identity represents the member throughout the ecosystem. It is not merely a login account.

The identity may connect to personal profile information, member status, authentication and verification, Product activity, Commerce activity, HIVE relationships, SA holdings and transactions, Knowledge progress, milestones, and future MICROBA capabilities.

Identity, authentication, authorization, consent, and ownership are separate system concerns even though they may appear as one seamless member experience.

A member's identity should remain stable while their activities, permissions, achievements, and relationships evolve over time.

1.4 The MICROBA Ecosystem

At a high level:

                         MICROBA
                            |
                     LIVING IDENTITY
                            |
          +-----------------+-----------------+
          |                 |                 |
       PRODUCT           KNOWLEDGE           HIVE
          |                 |                 |
       Journey           Learning      Direct Sponsorship
          |              Milestones            |
          +-----------------+------------------+
                            |
                         COMMERCE
                            |
                            SA

This is conceptual rather than a statement that one capability technically owns another.

Profile represents the member. Product manages product-related experiences. Knowledge manages structured learning and progress. HIVE manages direct sponsorship relationships and applicable sponsorship benefits. Commerce manages commercial transactions. SA manages SA lifecycle, entitlement, circulation, serial identity, Treasury interaction, and related records.

1.5 Profile

Profile is the member-facing home of identity.

It presents information about the member and provides access to relevant MICROBA capabilities.

Depending on activity and permissions, Profile may present member identity, profile details, membership status, Product activity, SA, HIVE, Knowledge, milestones, settings, and activity history.

Profile does not own every piece of information it displays. Commerce remains responsible for commercial transactions, SA for SA records, and Knowledge for learning progress.

1.6 Product

Product represents MICROBA's product-related experiences.

A member may purchase and use products without participating in HIVE.

Product is responsible for its own product rules and experience, while commercial settlement is delegated to Commerce.

Member
  |
Selects Product
  |
Product validates required state
  |
Commercial Request
  |
Commerce
  |
Payment / Settlement
  |
Confirmed Order
  |
Product journey continues

Product should not create independent payment systems or duplicate Commerce responsibilities.

1.7 Commerce

Commerce is the commercial transaction engine of MICROBA.

Its responsibilities may include receiving commercial requests, creating and managing orders, preserving commercial snapshots, presenting payment choices, communicating with payment providers, recording payment status and transactions, processing applicable reversals, triggering eligible sponsorship events, recording SA-related commercial events, publishing transaction outcomes, and monitoring reconciliation.

Commerce processes transactions but does not become the owner of every business capability.

Purchasing Without a Sponsor

A sponsor is optional.

Direct Customer
      |
   Purchase
      |
   Commerce
      |
No Sponsor Relationship
      |
Sponsorship Commission = 0

The absence of a sponsor must not prevent a legitimate purchase.

1.8 HIVE

HIVE is MICROBA's direct sponsorship capability.

It allows an eligible member to introduce MICROBA directly to another person and, where programme conditions are satisfied, receive a direct sponsorship benefit from eligible purchases attributed to that relationship.

Single-Level Structure

A directly sponsors B
B directly sponsors C
C directly sponsors D

For an eligible purchase by C, B may qualify as C's direct sponsor. A does not receive a commission from C merely because A sponsored B.

There is no generation-two, generation-three, or deeper sponsorship commission in the current model.

Direct Sponsorship Rate

The current system model uses a 9% direct sponsorship commission on eligible direct sponsored sales.

Detailed eligibility, attribution, payout, reversal, and control rules belong to the dedicated HIVE chapter.

Personal Purchases

A member does not receive a direct sponsorship commission from their own personal purchase.

A purchaser does not need a sponsor. Where a genuine sponsor relationship exists, MICROBA may preserve it according to HIVE rules so legitimate attribution is not lost merely because a repeat customer later returns directly to MICROBA.

1.9 Purchasing Without a Sponsor

Open purchasing is a deliberate MICROBA principle.

A person may discover MICROBA independently, join, purchase a Product, participate in eligible member benefits, and continue using MICROBA without becoming an affiliate and without having a sponsor.

Both independent and genuinely sponsored journeys are legitimate.

1.10 SA

SA is a uniquely identifiable unit within the MICROBA ecosystem.

Each whole SA has its own unique serial number.

Entitlement
    |
Existing Treasury SA available?
    |
 +--+--+
 |     |
Yes    No
 |     |
Recycle  Mint New SA
 |     |
 +--+--+
    |
  Member
    |
Hold / Transfer / Gift / Donate
    |
Spend / Redeem
    |
 Treasury
    |
Available for Future Recycling

Whole Units

SA exists as a whole unit. A member should not hold 0.2 SA, 0.5 SA, or 0.9 SA.

Fractional economic progress remains a backend provision until the applicable threshold for one whole SA is reached.

1.11 SA Provision and Sales

The current economic model uses a 3% SA provision/allocation reference on eligible sales.

The current programme reference value is:

1 SA = Rp30,000

Therefore:

Rp1,000,000 x 3% = Rp30,000

At the current reference, that is sufficient for one whole SA entitlement.

A Rp10,000 eligible purchase produces Rp300 of backend provision at 3%. Rp300 is not a fractional SA.

As eligible activity accumulates, provision can increase until the whole-SA threshold is reached.

Sales create economic provision and entitlement. They do not necessarily require a newly minted SA.

1.12 Treasury and SA Recycling

Treasury is the balancing reservoir for SA circulation.

When a valid SA entitlement needs to be fulfilled, the system checks available Treasury SA before creating a new SA.

Recycle First. Mint Only the Shortage.

Example:

Required SA:             10
Recycled from Treasury:   7
New SA minted:            3
                         --
Fulfilled:               10

Only three new serial numbers are created.

An SA that returns to Treasury does not cease to exist. Its serial number remains unchanged.

The public-facing SA Pool does not need to be a separate stock owner. It may simply be a view of SA currently available from Treasury.

1.13 Holding, Transferring, and Using SA

Once a whole SA has been allocated to a member, programme rules may allow the member to hold it, transfer it, give it as a gift, donate it, use it toward an eligible MICROBA purchase, or redeem it through an available programme mechanism.

Every movement should be recorded against the SA's unique serial identity.

A transfer is not a new Product sale and must not automatically generate a new sponsorship commission or new SA provision.

Unformed backend provision cannot be transferred.

When an SA returns through an applicable spend or redemption event, Treasury receives that existing SA and may later recycle it.

1.14 SA Registry, Flow, and Reconciliation

MICROBA distinguishes SA stock from SA flow.

The SA Registry monitors the current location and history of every minted SA.

With the Pool treated as a Treasury availability view:

Total SA Minted
=
SA Held by Members
+
SA Held by Treasury

Commerce monitors transaction flow, including eligible sales, SA provision, SA entitlement, new SA issuance, recycled fulfilment, Product usage of SA, applicable redemption, returns to Treasury, and reversals.

New SA and recycled SA must remain distinguishable to prevent double counting.

The objective is automatic check-and-balance in the background while presenting simple information to ordinary users and administrators.

1.15 Knowledge

Knowledge is MICROBA's structured learning capability.

It provides members with a way to deepen their understanding of MICROBA and relevant knowledge areas, including MICROBIOSM/Science content.

Member learning progress can be measured through confirmed reading activity.

For example:

Articles available: 100
Confirmed read:       50
Knowledge progress:   50%

Detailed Knowledge rules belong in the dedicated Knowledge chapter.

1.16 Membership Without Recruitment

A complete MICROBA member journey does not require recruitment.

Join
 |
Create Living Identity
 |
Complete Profile
 |
Learn
 |
Purchase
 |
Use Product
 |
Receive / Use Eligible SA Benefits
 |
Continue the MICROBA Journey

HIVE provides an optional additional path for members who choose to introduce MICROBA directly to others.

Purchasing, learning, membership, and Product participation are not conditional on building a referral network.

1.17 Example Member Journeys

Journey A — Independent Member

A person discovers MICROBA through the website, joins without a sponsor, completes their Profile, reads Knowledge content, and purchases a Product.

No direct sponsorship commission is created because no valid sponsor exists. Applicable SA provision follows SA rules.

Journey B — Sponsored Member

A HIVE participant directly introduces a new person. A valid direct sponsor relationship is recorded.

When the new member makes an eligible purchase, the applicable direct sponsorship event may be created.

The purchaser is not required to become an affiliate.

Journey C — Member Who Never Sponsors Anyone

A member purchases products, learns through Knowledge, progresses through Product, and participates in SA without ever sponsoring another person.

Their membership remains complete and valid.

Journey D — Member Later Participates in HIVE

A member initially joins only as a customer and later chooses to introduce MICROBA to another person.

Eligible direct sales may generate sponsorship benefits once applicable HIVE requirements are satisfied. No deeper-generation commission is created.

Journey E — SA Is Recycled

A member receives SA-000250, later uses it in an eligible transaction, and the SA returns to Treasury.

When another valid entitlement occurs, the system checks Treasury first. If SA-000250 is available, it can be recycled rather than minting a new SA.

Its serial number and history remain intact.

1.18 Frequently Asked Questions

Do I need a sponsor to join MICROBA?

No.

Do I need a sponsor to purchase a MICROBA Product?

No. Direct purchases are allowed.

What happens if I purchase without a sponsor?

The purchase proceeds normally. No direct sponsorship commission is created when no valid sponsor relationship exists. Other applicable programme rules may still apply.

Is every MICROBA member an affiliate?

No. Membership and HIVE participation are separate.

Do I have to recruit people?

No.

How many sponsorship levels does HIVE use?

One direct sponsorship level.

What is the current direct sponsorship commission?

The current system model uses 9% on eligible direct sponsored sales, subject to detailed HIVE rules.

Can I earn sponsorship commission from my own purchase?

No.

Is SA the same as sponsorship commission?

No.

What is the current SA provision reference?

3% of eligible sales in the current system model.

What is the current reference value of one SA?

Rp30,000 programme purchasing/redemption reference value.

Does a Rp10,000 purchase create a fractional SA?

No. At 3%, it may create Rp300 of backend provision, but fractional SA does not exist as a transferable coin.

Does the system always create a new SA?

No. Treasury SA is recycled first.

What happens if Treasury has fewer SA than required?

Available Treasury SA is recycled first. Only the shortage is newly minted.

Does a recycled SA receive a new serial number?

No.

Can SA be transferred, gifted, or donated?

Whole SA may support these actions according to programme rules.

Can unfinished SA provision be transferred?

No.

Can SA be used for a purchase?

The system model supports SA as a purchasing benefit for eligible MICROBA transactions according to applicable rules.

Can an eligible purchase be paid entirely using SA?

The architecture can support 100% SA-funded eligible purchases where programme rules allow it.

Can SA be redeemed for cash?

Cash redemption is a system scenario under discussion and must follow approved Treasury, Commerce, programme, and legal rules before public release. The final public rule belongs in the dedicated SA chapter.

Does SA expire?

The current architecture treats issued SA as non-expiring unless an approved future rule changes this.

What is Treasury?

Treasury is the balancing reservoir for SA circulation. It receives eligible returned SA and supplies recycled SA when valid entitlements need to be fulfilled.

Is the SA Pool separate from Treasury?

It does not need to be. The Pool can be a member-facing view of Treasury-available SA.

What does "Recycle First" mean?

Existing available Treasury SA is used before a new SA is minted.

Can moving SA between members generate additional commission or SA?

No. A transfer is movement of an existing SA, not a new Product sale.

How does MICROBA know whether SA is balanced?

The SA Registry records every minted serial and its current location, allowing total minted SA to reconcile against member-held and Treasury-held SA.

What is Knowledge?

Knowledge is MICROBA's structured learning capability, allowing members to read approved content, confirm completed reading, and progress through milestones.

Can I use MICROBA without participating in HIVE?

Yes.

1.19 Chapter Summary

MICROBA is designed as an interconnected Living Platform rather than a single-purpose sales or affiliate system.

Its foundation can be summarized as follows:

  • one member uses one canonical Living Identity;
  • membership does not require affiliate participation;
  • a sponsor is not required to purchase;
  • HIVE uses direct, single-level sponsorship;
  • personal purchases do not generate self-sponsorship commission;
  • Commerce manages commercial transactions;
  • SA operates separately from sponsorship;
  • eligible sales can create SA provision and entitlement;
  • Treasury SA is recycled before new SA is minted;
  • whole SA has a unique serial identity and transaction history;
  • Knowledge measures structured learning progress; and
  • a member can have a complete MICROBA journey without recruiting
  • anyone.

1.20 Source-of-Truth Note

This chapter provides the general foundation for understanding MICROBA.

Where a later dedicated chapter defines a more specific operational rule for Membership, Profile, HIVE, Product, Commerce, SA, Knowledge, or another capability, the dedicated chapter is the authoritative source for that capability.

Public wording, legal terminology, financial-accounting classification, and jurisdiction-specific programme terms may be refined before publication without changing the underlying system architecture unless an approved architecture revision is made.

SOURCE & VERSION

Knowledge identity
8be679a9-2f41-455d-92b3-8861b7639a9a
Canonical source
MICROBA User Manual/01-what-is-microba.md
Version read
1.0

Sign in to save private reading progress.