Banya LabsBanya Labs/Apps/EduGateKeeper
In progress

App 08  ·  FIG. 008

EduGateKeeper logo

EduGateKeeper

Schools, academies & educational institutions

Offline-FirstSecurityEducationPOPIA Compliance
App not yet live

Customer Target

Schools, academies & educational institutions

Status

In progress

Agent Surface B

MCP Ready

Model Context Protocol Enabled

Registered in /.well-known/mcp.json & /llms.txt with deterministic Zod schema validation.

About Product

Physical school gate check-ins suffer from peak-hour bottlenecks, poor compliance with POPIA regulations (unrestricted visibility of minor/guardian PII), and zero real-time campus visibility during emergencies.

GateKeeper is an offline-first gate access control and attendance logging system. It replaces paper logbooks with a tablet-based entrance kiosk, paired with a central Web Admin Dashboard.

The kiosk touch interface supports rapid student search, staff PIN-verified sign-ins, and guest registrations, using animated character avatars to guide users. The Admin Console features a live headcount roll-call, single/bulk roster CSV imports, Avery-compatible QR badge printing, and a one-click emergency fire evacuation list. The system leverages local caching (IndexedDB) and background synchronization pipelines to guarantee uninterrupted operation during network outages.

Dual-Surface Execution

Human vs. Agent Flow

Every action in EduGateKeeper is mapped bi-directionally across Surface A (Visual UI) and Surface B (Programmatic MCP Engine).

Surface A — Human Ergonomics Flow
  1. 01Visitor or guardian selects role on the tablet kiosk interface
  2. 02System evaluates current IN/OUT status of the student or staff member
  3. 03Guardian signs on screen / Staff enters their 4-digit PIN for verification
  4. 04Local database persists the movement log and queues background sync
  5. 05Central Web Admin Console updates live campus headcounts and attendance records
Surface B — Agentic Machine Execution Rails
Protocol: Model Context Protocol (MCP 1.0)Auth: Bearer banya_ag_...

1. Discovery: Scraper/Agent fetches /llms.txt or /.well-known/mcp.json manifest.

2. Tool Invocation: Executes deterministic Zod-validated tool contracts matching edugatekeeper operations.

3. Replay Protection: Enforces Idempotency-Key: <uuid> to prevent duplicate mutations during LLM retry loops.

4. Token Compression: Returns structured, PII-minimized Markdown/JSON stripping all layout noise.