App 11 · FIG. 011
Chiko
Keep school gate activity in view
Customer Target
School administrators and staff managing gates, visitors and learner pickups
Status
In progress
Agent Surface B
MCP ReadyModel Context Protocol Enabled
Registered in /.well-known/mcp.json & /llms.txt with deterministic Zod schema validation.
About Product
Chiko is being developed to help schools organise arrivals, visits and pickups. It gives the school office and gate staff a shared record of who is expected and who has entered or left.
The planned workflow brings learner details, approved contacts, visitor passes and gate records together. Staff can check the relevant information before recording an entry or pickup.
The product is currently in development for school administrators and gate teams.
Dual-Surface Execution
Human vs. Agent Flow
Every action in Chiko is mapped bi-directionally across Surface A (Visual UI) and Surface B (Programmatic MCP Engine).
- 01Set up the school and staff accounts.
- 02Add learner and approved-contact details.
- 03Prepare the visitor or pickup details.
- 04Check the details and record the entry or pickup.
- 05Review arrivals, visits and departures.
1. Discovery: Scraper/Agent fetches /llms.txt or /.well-known/mcp.json manifest.
2. Tool Invocation: Executes deterministic Zod-validated tool contracts matching chiko 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.