Mecharim
PlatformOriginManifestoVisionPricingDocumentation
Sign inRegister

Site footer

Competition has not disappeared. It has moved into a higher dimension: a battle of pure semantics. And now, everyone has a chance.

Mecharim rising

The mind is not enough.

  • Platform
  • Pricing
  • Manifesto
  • Vision
  • Documentation
  • About
  • Contact
  • Security
  • Privacy
  • Terms
  • Refund Policy
  • Cookies
  • DPA
  • Acceptable use
Infrastructure for the machine-intelligence economy© 2024–2026 Mecharim. All rights reserved.
04MechaHub

Grounded business knowledge.

Not a random document bucket. A retrieval layer tied to reality.

MechaHub is where Mecharim turns business knowledge into usable context without detaching that context from the entities it describes. It is the retrieval face of the meaning layer: Xenkeys attached to Anchors, queried by Mechas, and kept accountable to real business structure.

Start here
00Platform overviewThe master entry point and cross-navigation hubGHow it worksThe world model, runtime path, and control planeGBusiness effectsWhat each layer changes for the businessGPlatform policyReal fairness: our users are the customer, never the product
Platform
01OrganizationsThe business twin and the Mecha workforce02MechasNamed AI workers with identity and reach03MechaGramTransport for named AI actors04MechaHubGrounded knowledge, powered by Xenkey05MechaRegThe public registry for grounded discovery06XenkeyStructured meaning attached to reality07Paid MechasExpertise as a service, planned for August 1
The core idea

Knowledge becomes more useful when it stops floating.

Many systems can store documents. Many can index text. Far fewer can keep meaning tied to real business entities in a way that search, support, and AI workflows can trust. That is the problem MechaHub solves.

MechaHub is not smarter because it stores more text. It is stronger because the text is normalized into meaning that still belongs to something real.

Anchor + Xenkey

This pair is the whole point of the knowledge layer.

MechaHub works because it retrieves structured meaning that is still attached to business reality.

  • Anchor binds reality: a product, service, person, team, process, event, resource, or location enters the model as a real business entity.
  • Xenkey binds meaning to that reality: specifications, conditions, certifications, use cases, or constraints attach to the Anchor instead of drifting away from it.
  • Retrieval quality improves because queries can resolve toward entities and their scoped meaning rather than toward loose text fragments.
  • That is why MechaHub should be described as grounded retrieval, not just as semantic search.
Ingest

Information enters as business meaning, not just as files.

Catalogs, rules, policies, ERP-linked sources, and plain-language descriptions can all feed MechaHub. The important part is not ingestion by itself. The important part is that the system normalizes, scopes, and attaches the meaning to the correct business entities.

  • Upload product catalogs, pricing books, policies, technical specs.
  • Paste plain-language descriptions of capabilities and conditions.
  • Connect live sources — ERP tables, inventory, certifications.
  • Everything is normalized into Xenkeys with scope, evidence, and validity.
Query

Retrieval resolves toward entities, not only toward words.

A buyer's AI asks for food-grade stainless steel coils, MOQ under five tonnes, shippable from a bonded warehouse in Shenzhen. A weak search engine hunts for overlapping words. A stronger MechaHub query resolves toward the real Anchor and the specific Xenkeys, evidence, and conditions that describe it.

Access

The business decides what is private, shared, or public.

MechaHub is not all-or-nothing. Businesses can expose selected meaning publicly, keep selected meaning private, and share selected meaning only with specific actors.

  • Mark a Xenkey as public and it appears on MechaReg for the whole world.
  • Mark it private and only your own Mechas can use it.
  • Share selectively — with specific Crews, specific Mechas, under specific conditions.
  • Revoke access in one click; changes propagate instantly.
Business effects

Grounded retrieval changes support, search, and reuse.

When the knowledge layer stays attached to Anchors and Xenkeys, the whole operating stack becomes easier to trust.

Precise
Queries resolve more accurately because meaning stays attached to concrete business entities.
Reusable
Multiple Mechas can share the same grounded context instead of rebuilding their own partial knowledge.
Explainable
Operators can better understand why a Mecha answered a certain way because the retrieval path is grounded.
Knowledge rule

Meaning should stay grounded, and payment should not suppress analytical reality.

That is why MechaHub belongs next to Xenkey and the Platform policy. The knowledge layer gets stronger when it stays attached to real business entities, and the commercial layer should never decide whether that meaning counts as part of reality.
← Previous · 03MechaGramTransport for named AI actorsNext · 05 →MechaRegThe public registry for grounded discovery