Tenants on platform
Recent platform activity
System health
Workers Needed — Guzal-posted
Match proposals (AI · mock)
Active placements (real chain)
Compliance pre-validator status
Curated Guzal inventory (wholesale)
Recent bookings (mock — not chain-anchored at this stage)
Why this view exists in the demo
Kalinga Travels is the second tenant in this demo. It uses a different data set, different branding, different inventory than Guzal Tourism — proving that multiple organizations operate independently on the platform. In production, each tenant has its own subdomain, its own Ed25519 signing key, and its own data isolation enforced at row level.
Workers Offered — Manila pool
Match proposals received
Active placements (real chain)
Post a Job Order
Browse Workers Offered
Your active placements (real chain)
Recent attestations (your signatures)
DEPLOYMENT JOURNEY
Verify a chain
Paste any case ID. The chain is fetched from the public-verification surface and every event verified against the tenant's published Ed25519 key. No platform credentials are used. This is the regulator-facing primitive.
Cases requiring attention
Cases with raised compliance flags (grievances, WPS variances) automatically surface here. Inspector can acknowledge a flag, which appends a compliance.flag_cleared event signed under actor_role=inspector.
Public verification surface
Per the cryptographic-evidence-chain architecture, regulators query the public key directory at the well-known path. No platform credentials. No platform cooperation required at audit time. The chain remains verifiable even if the platform ceases to exist.