You receive a message with an unexpected request. Or someone calls using a familiar name. The voice and the name on the screen seem convincing, but one question remains: is it really that person? HUMAS System Mobile gives you a way to pause and check who you are dealing with.
A Glyph message is meant for one person
This is not a public feed or an endless chat. To send a Glyph, you need the exact HUID of another HUMAS System participant. The application checks the recipient before sending. It deliberately has no contact list for saving other people's HUIDs.
So a message begins with a simple question: what do you genuinely want to say to this person? For example: “Thank you for helping when it mattered.” You create a short message that means something to you and its recipient, rather than posting to an unknown audience.
Sending is tied to the participant's verified identity and HUID. The recipient can see which participant sent the Glyph, rather than an anonymous or invented profile. The sender's personal words are still their own words: a Glyph does not turn every statement into a proven fact.
Two kinds of Glyph, two different origins
A canonical Platform Glyph is connected to a participant's confirmed contribution and energies in HUMAS System. It can be transferred through the application as a Platform Glyph. It belongs to the participant's verified history; the phone does not recreate that history.
A local Glyph is created and verified in the mobile application. It stays in the device's private history and can be sent separately as a Glyph message. For example, it can carry support or gratitude to a specific participant. A local Glyph does not become a canonical Platform Glyph, nor does it add confirmed contribution to the Platform history by itself.
Confirmation: when something feels uncertain
Imagine that a caller or a message asks you to send a document, money or a code urgently. You may even know the person, yet the request feels unusual. Rather than relying on a name in a messenger or on a voice, ask for the person's HUID and send an Identity Confirmation request to that HUID through HUMAS System.
The person sees who is asking and why, then decides whether to approve or reject the request. You check the result in the system instead of trusting a screenshot someone sends you. If there is no confirmation, or the request details do not match the conversation, do not carry out the unusual action.
Identity Confirmation answers who you are dealing with. It does not automatically prove that a request is safe. If someone says they represent an organisation, you also need to understand whether they are authorised to act for it.
Who can use the application
HUMAS System Mobile is free to install. To connect it, you need a HUMAS System participant account on the Platform. You cannot use the application without registering there.
A person participates through their own identity and HUID. An organisation or institution cannot register as a personal participant: it has a separate corporate membership path.
The application supports a simple habit: when a message matters, know who it is for; when an action raises doubt, ask for confirmation and make your own decision.