Request
The sender, action, consequences and time limit, presented clearly.
ACTION · CONTEXT · TRUST
Between identification and confirmation
Identification helps establish who performs an action. SGM connects a specific request with an explicit human decision and a verifiable result.
The participant sees who is asking, what action is requested and its consequences. They approve or reject the request; their decision is retained alongside the verification result.
Requests can concern identity confirmation, sign-ins, documents, transactions and other important actions — not only payments.
01 / Principle
A clear request. A personal decision.
Secure Glyph Module complements existing authentication by verifying the request, consent and participant decision. It does not replace Mobile ID, Smart ID, banking identification or cryptographic signatures.
Decision
Explicit consent to use Personal Glyph context, followed by approval or rejection.
Verification
The integrity of the request, context, decision and audit history is checked before a result is issued.
Privacy as a design principle
Personal Glyph context is used with explicit participant consent for a specific request. SGM preserves a verifiable confirmation history without changing the Personal Glyph or replacing a human decision with behavioral assumptions.
02 / Verification result
The human decision and its verification
Approval or rejection is the participant’s decision. A separate verification result shows whether the integrity of that decision and its request has been established.
Verification passed
The integrity of the request, context and decision is confirmed.
Review required
The result requires further review.
Verification failed
Confirmation integrity has not been established.
A verified rejection remains a rejection. The organization receives a signed result and is responsible for the subsequent action in its own system.
03 / Integration
An additional step in an existing process
SGM operates between an external request and the organization’s action. The platform binds the request to its exact recipient, the participant makes a decision, and the organization receives a signed result.
- 01Request
- 02Review
- 03Consent
- 04Decision
- 05Verification
- 06Secure Glyph
What holds the process together
Recipient
The request is addressed to an exact personal HUMAS identity and HUID.
Context
A one-time context handoff is bound to the request and participant consent.
Result
The Secure Glyph, signed result and verification history remain linked to the decision.
04 / Applications
SGM application scenarios
Confirmation of important actions within organizational infrastructure: from a request to the participant to a result that can be verified.
- 01Banking systems
- 02Mobile identification
- 03Telecommunications
- 04Digital signatures
- 05Cryptocurrency wallets
- 06Payment platforms
For the individual — HUMAS System Mobile
Mobile presents a personal trust space. SGM verifies the request and the participant’s explicit decision for connected infrastructure. These are related but distinct roles within the same architecture.
Explore HUMAS System Mobile →Discuss an integration
For organizations, digital services and infrastructure partners. Start with a specific request: what must the participant understand and confirm, and where would a verifiable result help?
Opens your email application