Instrument · designed
Glorya
Evaluating
Glorya is Solace’s humanitarian instrument. It does not fund a place because it appears on a map. It funds only when need is verified and money can actually become help: a partner who can deliver, access to the people in need, a workable environment, and the right window. Like Hermes in markets, stand down is the default. This field shows evaluations only. No live capital until the $1M revenue gate.
Drag to rotate · hover a city
Drag to rotate · tap a city
Process
Evaluation scoreboard
Integrity and restraint first. Most evaluations stand down. Performance metrics wait for sealed outcomes after the first disbursement.
Public ledger
Glorya decision ledger
First disbursement seals the first row. Until then the sheet is empty by design — not a hidden history.
| ID | Time | Place | Amount | Need | Partner | Predicted | Actual | Status | Hash |
|---|---|---|---|---|---|---|---|---|---|
| No sealed Glorya rows. Instrument is evaluating only. The live ledger begins with the first disbursement after the revenue gate. | |||||||||
How it decides
Need is not enough. The path has to hold.
Hermes asks whether markets can carry a trade. Glorya asks whether capital can become real help on the ground. The method is the same: gates before money moves, evidence over story, stand down when the chain is broken. The domain is different: humanitarian need, not liquidity.
Deploy only when need and path both pass. Most evaluations result in no allocation.
What “path” means
- Partners — who delivers on the ground with capacity and integrity, not a place name alone
- Access — whether that partner can reach the people in need (logistics, permissions, last mile)
- Regime — whether the environment is stable enough for aid to land and stick — not diverted, frozen, or made unsafe
- Timing — whether this is the right window: crisis open, partners ready, capital ready — not already past
Three gates before capital
- Need — is the need severe enough and verifiable, not rumor or headline alone?
- Path — do partners and access exist so money can become delivery?
- Regime & timing — can the environment and the window support a successful intervention now?
Then the lifecycle
- Selection — where attention is warranted
- Commitment — whether evidence is strong enough to allocate
- Monitoring — whether evidence still holds after money moves
- Exit / recycle — stay, reduce, or redirect when conditions change
Design layer
Evaluated places
Real cities and countries with WGS84 coordinates. Illustrative evaluations only — not offers, transfers, or impact claims.
- Ouagadougou, Burkina FasoGLY-EV-001
Primary schooling need is high; regime gate did not clear. No capital path.
- Goma, DR CongoGLY-EV-002
Literacy and school access evaluated. Commitment gate open for design review only.
- Cusco, PeruGLY-EV-003
Rural clinic access need recorded; timing gate failed. Unfunded on the map.
- Chattogram, BangladeshGLY-EV-004
Coastal school need is verifiable. Allocation dormant until instrument activation.
- Jijiga, EthiopiaGLY-EV-005
Water access severity high; environment not yet stable enough for deployment.
- Port-au-Prince, HaitiGLY-EV-006
Shelter need clear; regime gate held. Standing down until path can carry intervention.
- Freetown, Sierra LeoneGLY-EV-007
Clinic access evaluation on file. No disbursement until the revenue gate.
- Cox’s Bazar, BangladeshGLY-EV-008
Protection need evaluated at locality level. Instrument remains dormant.
- Maiduguri, NigeriaGLY-EV-009
Nutrition need severe; all three gates must clear before any path opens.
- Jalalabad, AfghanistanGLY-EV-010
Need is real; regime and verification gates require stand-down.
- Aleppo, SyriaGLY-EV-011
Evaluated and stood down. Empty capital path by design.
- Sana’a, YemenGLY-EV-012
Highest-severity water need in the sample set; environment cannot yet carry intervention.