Skip to content
MICROBA — Return to Origin.

MANUAL / GUIDE

MICROBA KNOWLEDGE - User Manual

Version 1.0 Public access Updated August 19, 2026

Document: User Manual Module: MICROBA KNOWLEDGE Documentation version: 1.0.0 Date: 2026-08-20 Audience: Visitors, Members, Users, Customer Support Status: Current working user reference

1. Purpose

MICROBA KNOWLEDGE is the MICROBA module for discovering, reading, exploring, and engaging with canonical MICROBA knowledge materials.

Its role is to help users:

  • understand MICROBA concepts;
  • explore Articles and core reference materials;
  • continue learning across sessions;
  • converse with AI about available Knowledge material;
  • build meaningful Knowledge Mileage through genuine engagement.

KNOWLEDGE is not merely a page counter or document archive.

2. What You Can Find in KNOWLEDGE

The current Knowledge model may include:

  • Articles;
  • Website knowledge;
  • Science material;
  • Experience material;
  • Community material;
  • manuals;
  • specifications;
  • governance documents;
  • technical references;
  • controlled core documents;
  • other canonical MICROBA learning material.

The exact published collection may evolve as the system develops.

3. Articles

Articles are the main ongoing content layer once the core system stabilizes.

Articles may be used for:

  • new ideas;
  • current updates;
  • explanations;
  • educational material;
  • practical experience;
  • science-related content;
  • community knowledge.

After core documents become stable references, normal continuing content updates should happen mainly through Articles rather than repeatedly changing foundational documents.

4. Core Documents

Core documents can include:

  • User Manuals;
  • Admin Guides;
  • Developer Guides;
  • Governance;
  • specifications;
  • technical references;
  • controlled system documentation.

During development, these documents may be revised and versioned frequently.

After the system becomes stable, they should generally become fixed current references.

Later changes to stabilized core documents should be exceptional and handled through controlled document revision.

5. Document Authority

Canonical published Knowledge material is authoritative.

AI conversation is not the authority.

If an AI explanation conflicts with a published canonical document, the canonical document prevails.

6. Knowledge Categories

Knowledge Mileage may be organized into categories such as:

Website
Articles
Science
Experience
Community

These categories represent meaningful exploration and engagement rather than simple page visits.

7. Knowledge Mileage

Knowledge Mileage is a measure of meaningful content engagement and progress.

It is not intended to reward raw clicks or accidental page loads.

Examples of meaningful engagement may include:

  • reading a meaningful portion of an Article;
  • completing a significant section;
  • revisiting and continuing structured material;
  • exploring multiple related Knowledge resources;
  • completing a meaningful Knowledge interaction.

The exact scoring model remains controlled by KNOWLEDGE.

8. Recently Explored

The Knowledge experience may include a Recently Explored area.

This helps users return to content they have meaningfully viewed or engaged with.

Recently Explored is a convenience view and does not replace the canonical Knowledge record.

9. Continue Exploring

The Continue Exploring area may help users resume material that was started but not completed.

This can include:

  • partially read Articles;
  • continuing categories;
  • unfinished Knowledge paths;
  • recommended next material based on prior engagement.

10. Knowledge Mileage in My MICROBA

PROFILE may display a summary of Knowledge Mileage.

PROFILE does not calculate or own Knowledge Mileage.

The relationship is:

KNOWLEDGE
= authority for meaningful engagement and Mileage

PROFILE
= presentation layer for the member-facing summary

If the number shown in PROFILE differs from the KNOWLEDGE source record, KNOWLEDGE is authoritative.

11. Visitor Analytics vs Knowledge Engagement

Visitor/referral analytics and Knowledge engagement are separate concepts.

A page visit does not automatically mean meaningful Knowledge engagement.

KNOWLEDGE measures content engagement.

VISITOR measures visitor/referral activity.

These domains should not be mixed.

12. Using AI in KNOWLEDGE

AI is provided as a conversational companion.

It may:

  • explain published material;
  • summarize concepts;
  • answer questions about available Knowledge;
  • converse in multiple languages;
  • make the experience more engaging;
  • help users discover related material.

AI should be treated as an assistant, not as the document authority.

13. What AI Cannot Do

AI does not have authority to:

  • publish canonical Knowledge;
  • approve documents;
  • change governance;
  • create official policy;
  • change user accounts;
  • alter document versions;
  • replace the Document Controller;
  • make system/domain decisions.

If a question requires authoritative policy or document status, refer to the canonical published material.

14. Multilingual Conversation

AI may communicate with users in multiple languages.

A translated or conversational explanation does not create a new authoritative version of the source document.

The authoritative document remains the published canonical record.

15. Document Versions

Where version information is displayed, users should understand that:

  • newer approved/published versions supersede older active versions;
  • older versions may remain available as historical records where appropriate;
  • archived documents are not the current operational reference unless explicitly stated.

16. Current Document

A document marked as current is the active reference for that document family.

Where the system exposes version history, the current document should be clearly distinguishable from:

  • Draft;
  • Superseded;
  • Archived;
  • Historical versions.

17. Search and Discovery

KNOWLEDGE may provide search across published material.

Search should help users find:

  • Articles;
  • documents;
  • relevant sections;
  • categories;
  • related material.

Search results are navigation aids.

The source document itself remains authoritative.

18. Access

Some Knowledge may be:

  • public;
  • member-only;
  • role-restricted;
  • administrative;
  • internal;
  • archived.

Access is controlled by KNOWLEDGE according to the document/content record.

A user should only see material they are authorized to view.

19. Reading a Document

A document view should clearly identify important information where applicable:

  • title;
  • document type;
  • version;
  • status;
  • effective/published date;
  • current or archived state;
  • Document Controller information where appropriate;
  • related Articles or resources.

20. Reading an Article

An Article may include:

  • title;
  • summary;
  • category;
  • body content;
  • related material;
  • publication date;
  • version or revision reference where applicable.

Articles are intended to be the practical, ongoing content layer.

21. Meaningful Engagement

KNOWLEDGE should not treat every action equally.

Examples:

Open and immediately leave
= low/no meaningful Mileage

Read meaningful content
= potentially meaningful Mileage

Resume and continue learning
= potentially meaningful Mileage

Complete structured material
= potentially higher meaningful Mileage

The exact scoring algorithm is not user-editable.

22. No Raw Hit Farming

Refreshing pages, repeatedly opening the same page, or artificially generating hits should not create unlimited Knowledge Mileage.

KNOWLEDGE may use controls such as:

  • minimum meaningful duration;
  • progress thresholds;
  • content completion;
  • repeat limits;
  • session validation;
  • deduplication.

23. Privacy

Knowledge engagement should collect only what is reasonably needed to:

  • maintain progress;
  • calculate Mileage;
  • support Recently Explored;
  • support Continue Exploring;
  • improve the Knowledge experience.

KNOWLEDGE should not unnecessarily copy unrelated PROFILE, HIVE, COMMERCE, SA or Visitor data.

24. Content Corrections

If a user notices a possible error in a canonical document:

  1. report the issue through the appropriate support/feedback channel;
  2. do not assume the AI explanation is the corrected authority;
  3. wait for a controlled revision by the Document Controller where required.

25. Archived Content

Archived content may remain available for historical reference.

Archived content should be clearly marked so users do not mistake it for the current rule or current document.

26. Content That Changes Frequently

Routine ongoing information should generally be published as Articles.

Core documents should not be revised every time a routine update is needed.

This keeps the Knowledge system practical and understandable.

27. Typical User Journey

Open KNOWLEDGE
-> Discover material
-> Read / explore
-> Ask AI questions if helpful
-> Continue into related material
-> Meaningful engagement recorded
-> Knowledge Mileage updated
-> Resume later through Recently Explored / Continue Exploring

28. Important Boundaries

KNOWLEDGE does not own:

  • Member identity;
  • HIVE sponsorship;
  • Nectar;
  • Commerce Orders;
  • Product calculation;
  • Visitor referral analytics;
  • SA/Treasury accounting.

KNOWLEDGE owns content, document lifecycle, Knowledge engagement and Knowledge Mileage.

29. User Summary

MICROBA KNOWLEDGE exists to help users understand and explore MICROBA through controlled materials, Articles, and meaningful engagement.

The essential rule is:

Canonical content is authoritative.
AI is conversational.
Knowledge Mileage reflects meaningful learning activity.