Public Discovery and Contact
See how a business becomes discoverable to external AI systems through MechaReg, then reachable through Mecha identity and runtime transport.
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.
Before you continue
Read these first if you want the current page to make more sense in the wider handbook.
MechaReg
MechaReg is the public trust and discovery surface of the platform, the layer that projects grounded business reality into machine-readable visibility.
Mecha
Mecha is the central operational actor of the platform, the point where identity, runtime, knowledge, and business context become one working unit.
A business record becomes publicly discoverable through grounded data, an external AI system evaluates that record, and the path can continue into live contact with a reachable Mecha.
The problem
Businesses are often visible on the public web, but still hard for AI systems to understand and trust.
The data is often:
- fragmented
- stale
- disconnected
- not clearly tied to a live operational path
The Mecharim pattern
Mecharim improves the path like this:
grounded business twin -> public projection in MechaReg -> external discovery -> reachable Mecha contact
This matters because discovery is no longer just “find a page”. It becomes:
- find a structured business record
- evaluate its grounded meaning
- continue toward a reachable actor
Example scenario
A buyer-side AI system looks for a supplier or specialist business.
The flow can look like this:
- the business publishes selected public data through MechaReg
- the external AI discovers the structured record
- it compares the business using grounded public meaning
- it chooses to contact a reachable Mecha
- the conversation continues through runtime transport
Why this is stronger than generic search
- the record is machine-readable
- the business identity is clearer
- selected public meaning is grounded
- contact can lead directly to an operational actor
This reduces the gap between being visible and being operationally reachable.
What layers are active
| Layer | Contribution |
|---|---|
| Business twin | Supplies the grounded source of truth |
| Anchor and Xenkey | Supply public meaning worth publishing |
| MechaReg | Publishes the public machine-readable projection |
| Mecha | Provides a reachable operational actor |
| Mechagram | Carries follow-up runtime communication |
Business effect
- discoverability improves
- trust improves
- qualified contact becomes easier
- the business can move faster from discovery to action
Recommended next pages
- Continue with MechaReg.
- Continue with Policy.
- Continue with Paid Specialist Mecha.
- Continue with Paid Mechas.
Related pages
Open these pages when you want adjacent concepts, neighboring entities, or connected implementation context.
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.
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.
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.
Grounded Support
This case shows the practical value of MechaHub, the support flow becomes more precise when answers are grounded in real entities and structured meaning.
Next reading
Use this path if you want a cleaner progression through the handbook after this page.
Paid Specialist Mecha
This case explains how monetization fits on top of the stack, a Mecha becomes paid because it delivers real business expertise, not because payment creates legitimacy.
Examples
Examples make the MCP section usable, they turn abstract descriptions into a sequence an agent or implementer can actually follow.