MICROBA PRODUCT - User Manual

Document: User Manual Module: MICROBA PRODUCT Current Product: MICROBA Moment™ Documentation version: 1.0.0 Runtime reference: PRODUCT 2.8.2 Date: 2026-08-20 Audience: Visitors, Guests, Members, Customer Support Status: Current working user reference

1. Purpose

MICROBA PRODUCT is the MICROBA module that defines and fulfils the current Product experience.

There is currently one Product only:

MICROBA Moment™

MICROBA Moment is offered to:

• Visitors / Guests; and
• registered MICROBA Members.

Registration is not required for a true Guest purchase.

2. What MICROBA Moment Is

MICROBA Moment is a calculated Moment / Time created from approved Product inputs and Product rules.

It is not a physical jar, drink, packet, shipment, medicine, treatment or diagnostic service.

MICROBA does not ship the sugar, honey or water used in the preparation.

The Product journey is fulfilled digitally through the:

MICROBA Moment of Truth Certificate

3. The Five-Step Journey

The current Product journey is:

1. Prepare Your Ingredients
2. Buy Your TIME
3. Receive Your Certificate
4. Process
5. Consume After 24 Hours

The page may display a Certificate Preview before purchase. Before the final Moment is known, fields that have not yet been determined should remain blank or show a restrained placeholder rather than fictional data.

4. Preparation Reference

One SET is:

For N SETs:

Sugar = 10 g × N
Honey = 20 g × N
Water = 70 ml × N

Examples:

The preparation may be performed by the Product Individual or by another person. The processor's identity is not part of the Moment formulation.

5. SET Quantity Rules

Current purchase range:

Minimum: 1 SET
Maximum: 30 SETs

Current daily-use reference:

Suggested: 1 SET per day
Maximum Product reference: 7 SETs per day

The daily-use reference is a Product rule, not individualized medical or nutritional advice.

6. Product Individual

Every MICROBA Moment belongs to one Product Individual.

The Product Individual is the person whose Product inputs define the Moment and Certificate context.

Member purchase

A signed-in Member must use that Member's approved registered identity.

Member mode cannot silently fall back to Guest mode.

Guest purchase

A true Guest may purchase for:

• themselves; or
• another Product Individual.

The Product Individual does not become a MICROBA Member merely because a Guest purchases for them.

7. Information Used by MICROBA Moment

The current Product context can include:

• Full Name;
• Date of Birth;
• Original / Dominant Gender used by the Product rule;
• Location of Process;
• latitude;
• longitude;
• timezone;
• sunrise;
• sunset;
• Founder Factor;
• selected SET quantity;
• applicable Product and rule versions.

The exact proprietary calculation is not user-editable.

8. Full Name, DOB and Gender

Member

For a registered Member, PRODUCT consumes approved identity data from PROFILE through the MICROBA identity contract.

PRODUCT does not create a second canonical Member identity record.

Guest

A Guest supplies the required Product Individual information directly to PRODUCT for that Product journey.

Guest Product information does not create a PROFILE account.

Sensitive information must not be unnecessarily exposed on a public Certificate.

9. Location of Process

The Location of Process is committed Product truth.

It is the location used for the Product calculation and Moment context.

Member

A Member selects an eligible reusable PROFILE Place.

Typical Place options may include:

• Home;
• Billing;
• Additional Place 1;
• Additional Place 2;
• Additional Place 3.

PROFILE owns those reusable Places.

Guest

A Guest provides a one-time Location of Process directly in PRODUCT.

The Guest may use:

• Search Address;
• Enter Manually;
• other PRODUCT-supported one-time resolution methods.

The Guest location does not create or modify a PROFILE Place.

10. Address and Location Resolution

A Location of Process may contain:

• display address;
• latitude;
• longitude;
• timezone;
• provider/reference information.

For Guest purchases, PRODUCT owns the one-time location resolver.

The Product may use Google Maps Platform when configured, with an OpenStreetMap fallback according to the current runtime.

11. Date for Your Moment

The selected date must be valid for the Product context.

A new purchase cannot intentionally select a past Moment date.

The correct interpretation of "today" should use the committed Location of Process timezone.

If validation fails because the selected date has passed, select the current date or a future date in that Location of Process timezone and continue again.

12. Certificate Preview

The Product page may show the real Certificate design before purchase.

Before finalization:

• Product Individual may populate when known;
• Location may populate when known;
• SET quantity may populate when known;
• Moment remains undetermined;
• Ready to Consume From remains undetermined;
• Certificate ID is not treated as issued truth.

The preview is not yet an issued Certificate.

13. Pricing and Currencies

PRODUCT owns Product price truth.

The current canonical Indonesia reference price is:

IDR 10,000 per SET

Admin may configure additional supported currencies.

Important rules:

• each currency appears only once in the Product price book;
• no live automatic FX conversion;
• countries sharing the same currency use the same configured Product price;
• current price changes do not reprice historical Product snapshots or Orders.

The browser display is not authoritative. PRODUCT validates price and currency again before commitment.

14. Starting Checkout

Once the Product context is valid:

PRODUCT
-> commits the Product snapshot
-> builds a Commercial Request
-> hands off to COMMERCE

The action is normally:

Continue to Checkout

After successful handoff, COMMERCE owns Checkout, Order and payment.

PRODUCT must not become the payment processor.

15. What Happens in COMMERCE

COMMERCE receives the committed Product truth and handles:

• commercial customer/contact;
• Checkout;
• Order;
• payment state;
• payment verification;
• refund/reversal;
• transaction notifications.

COMMERCE does not recalculate the MICROBA Moment.

If PRODUCT validation fails before handoff, the user remains on the Product page and no Commerce Order should be created.

16. When the Exact Moment Is Determined

The exact MICROBA Moment is finalized only after COMMERCE reaches an authoritative successful paid state.

The committed pre-payment Product snapshot is not rewritten.

Conceptually:

Product selection
-> PRODUCT snapshot
-> COMMERCE Checkout
-> COMMERCE Order
-> authoritative PAID event
-> PRODUCT finalizes Moment
-> PRODUCT issues Certificate

17. Moment Must Be in the Future

The current formulation engine must never produce a backtime Moment for a new journey.

If the draft calculation would resolve to a time that has already passed, the runtime rolls the Moment forward so that the final Moment is in the future.

Historical committed contexts may be reproduced for verification without rewriting their original truth.

18. Ready to Consume Rule

Consumption is permitted only after:

Ready to Consume
= canonical MICROBA Moment + 86,400 elapsed seconds

That is 24 full elapsed hours after the Moment, not 24 hours after checkout and not 24 hours after Certificate issuance.

19. Travel and Timezones

The readiness instant is absolute.

After the Moment has been finalized:

• travel does not reset the 24-hour period;
• changing timezone does not shorten it;
• crossing the international date line does not change it;
• consumption may occur anywhere once the readiness instant has been reached.

The Certificate displays the readiness time using the stored Location of Process timezone.

20. Certificate Issuance

The Certificate does not have to wait 24 hours before it exists.

After successful payment and Product finalization, PRODUCT may issue the Certificate immediately.

The Certificate shows:

• the MICROBA Moment;
• Location of Process;
• preparation information;
• Ready to Consume From;
• Certificate identity/verification information where applicable.

Before readiness, the Certificate may display a status such as:

MATURING — NOT YET READY

After readiness:

READY TO CONSUME

21. Certificate Is Historical Truth

Opening the Certificate later must not recalculate the Moment using current Profile or location data.

The Certificate represents the committed Product history.

Later changes to:

• name records;
• reusable Places;
• Founder Factor;
• Product rule version;
• certificate artwork

must not silently rewrite the historical Moment.

22. Guest Referral Context

A true Guest purchase may enter PRODUCT through a referral link.

That referral is transaction context only.

It does not permanently bind the Guest purchaser to the referral owner.

PRODUCT may preserve the neutral referral attribution through the Product snapshot and Commercial Request.

HIVE decides whether the purchase creates any Nectar entitlement.

PRODUCT does not calculate the 9% Nectar entitlement.

23. Member Sponsorship Is Separate

For a signed-in Member, registered identity and existing Sponsor rules take precedence.

PRODUCT does not appoint or replace a Member's Sponsor.

Guest purchase referral and registered Member sponsorship are separate concepts.

24. No Physical Goods

MICROBA Moment currently has no physical Product shipment.

The person prepares the ingredients locally according to the Product preparation reference.

COMMERCE may process payment, but it does not create a courier or shipping workflow for the current Product.

25. Product Images

The Product Journey currently uses these optional presentation assets:

/wp-content/uploads/product/images/

Expected Journey filenames:

microba-step-01-ingredients.webp
microba-step-02-buy-time.webp
microba-step-03-certificate.webp
microba-step-04-process.webp
microba-step-05-drink.webp

Presentation assets must not become authoritative sources for Product rules or values.

26. Certificate Template

The canonical Product-owned Certificate template is packaged with PRODUCT.

The Product page may also support a presentation override in uploads.

The final issued Certificate must render validated Product data rather than sample text embedded in artwork.

27. Common Situations

"Moment date cannot be in the past"

Choose today or a future date in the Location of Process timezone.

Checkout does not open

PRODUCT validation may have failed. Review the visible notice and Product fields before retrying.

Guest location cannot be resolved

Try Search Address again, enter a more complete manual address, or use another supported PRODUCT location method.

Member PROFILE is incomplete

Review the required PROFILE identity/Place information. Signed-in Member purchase cannot silently become Guest purchase.

Paid but Certificate not visible yet

PRODUCT fulfilment may still be processing. COMMERCE preserves the paid Order. Authorized operations may retry Product fulfilment idempotently.

Certificate exists but says not ready

That is expected before Moment + 24 full elapsed hours.

28. Product Ownership Summary

PROFILE
= registered Member identity and reusable Places

PRODUCT
= MICROBA Moment Product truth
= Product Individual
= formulation
= Product snapshots
= Moment Result
= readiness
= Certificate

COMMERCE
= Checkout
= Order
= payment
= commercial transaction

HIVE
= sponsorship and Nectar eligibility

29. User Summary

The current journey is:

Choose MICROBA Moment
-> identify Product Individual
-> commit Location of Process
-> choose date and SET quantity
-> Continue to Checkout
-> COMMERCE payment
-> PRODUCT determines exact Moment
-> Certificate issued
-> process at the Moment
-> wait 24 full hours
-> consume when Ready

MICROBA Moment is the same Product for Visitors/Guests and Members; only the identity source and reusable Place source differ.