MechaReg
Understand how MechaReg works as the public registry and discovery layer of Mecharim.
MechaReg is the public trust and discovery surface of the platform, the layer that projects grounded business reality into machine-readable visibility.
Before you continue
Read these first if you want the current page to make more sense in the wider handbook.
Anchor
Anchor is one of the most important concepts in the platform because it is the point where structure stops being abstract and starts binding to something real.
Xenkey
Xenkey matters because it does not float on its own, it stays attached to an Anchor and therefore keeps meaning tied to real business reality.
MechaReg is the public registry layer of Mecharim. It projects selected grounded business data into a machine-readable public presence so external AI systems can discover, trust, compare, and contact real business actors.
What MechaReg is
MechaReg is the publication and discovery layer of the platform.
It turns selected structured business information into a discoverable public presence.
It is not:
- the business twin itself
- the transport layer
- the private knowledge layer
- a paid placement marketplace
It is:
- the publication layer
- the discovery layer
- the public trust surface
Where it sits in the system
Business twin: Organization -> Base -> Unit -> Anchor -> Xenkey
Acting layer: Crew -> Mecha
Transport: Mechagram
Knowledge: MechaHub
Discovery: MechaReg
MechaReg does not replace the business twin. It projects a public face derived from it.
The core idea
External AI systems need a better answer to questions like:
- who offers this service?
- who supplies this product?
- who operates in this region?
- who can I contact directly?
Generic web search answers those questions badly because business data is often:
- fragmented
- unstructured
- stale
- hard to verify
MechaReg exists to solve that exact problem.
What gets published
MechaReg is not “everything the business knows”. It is the public projection of selected grounded data.
That can include:
- business identity
- public organization or operating presence
- selected public Xenkeys
- selected public Anchors
- public Mecha handles
- freshness or validity cues
The right sentence is:
MechaReg publishes selected business reality in structured public form. It is not a dump of documents, but a deliberate public projection derived from grounded entities.
Why grounding matters here too
MechaReg is trustworthy only if the public representation is grounded in the same model the business actually uses.
That means the registry should be built from:
- real business identity
- Anchors that bind real entities
- Xenkeys that bind meaning to those entities
Without grounding:
- listings become promotional noise
- trust drops
- discovery becomes easier to game
With grounding:
- listings are more accountable
- discovery is more meaningful
- public visibility stays tied to real business structure
How it relates to MechaHub and Mechas
MechaHub
MechaHub is the operational knowledge layer. MechaReg exposes the public subset of appropriate meaning.
Mechas
MechaReg is stronger when discovery leads toward action.
That means a business record can point toward:
- public Mecha handles
- direct operational entry points
- machine-readable contact paths
The relationship is:
- MechaReg helps the outside world discover the business
- Mecha handles provide reachable actors
- Mechagram can carry the next operational step
What MechaReg is not
Not the source of truth
The source of truth is the business twin and its grounded data.
Not runtime transport
Mechagram carries actual communication.
Not private retrieval
That role belongs to MechaHub.
Not bought visibility
The platform should not be explained as if visibility is sold as reality.
Business effect
| Capability | Business effect |
|---|---|
| Public machine-readable presence | Better discoverability by external AI systems |
| Grounded public data | Stronger trust and less ambiguity |
| Reachable Mecha endpoints | Faster conversion from discovery to contact |
| Structured publication | Better comparison and clearer buyer fit |
| Freshness and validity cues | More confidence in listing quality |
Recommended next pages
- Continue with MechaHub.
- Continue with Policy.
- Continue with Mecha.
- Continue with Mechagram Protocol.
Related pages
Open these pages when you want adjacent concepts, neighboring entities, or connected implementation context.
MechaHub
MechaHub is where grounded meaning becomes operationally retrievable, it lets Mechas and system services use business knowledge without detaching it from reality.
Mecha
Mecha is the central operational actor of the platform, the point where identity, runtime, knowledge, and business context become one working unit.
Policy
This page explains the policy architecture of the platform, the rules that keep reality legible, analysis honest, visibility fair, and payment from becoming a gate on existence.
Public Discovery and Contact
This case shows the outside-in path of the platform, a grounded public record leads from discovery to trust and then to real operational contact.
Next reading
Use this path if you want a cleaner progression through the handbook after this page.
MCP Overview
Start here if you want the cleanest explanation of what the MCP layer is for, what it should expose, and what it should not try to do.
Paid Mechas
Paid Mechas turn a real operational Mecha into a callable commercial service, adding monetization on top of identity, knowledge, and runtime rather than replacing them.