Skip to main content
Glama

OLCP documentation

Product

The product specification is one specification in two files. Neither may be implemented from alone; their own section 0 mandates a fusion into a single IMPLEMENTATION_PLAN.md before the first product code, and card 017 executes that fusion.

  • plan.md - the foundational plan: identity, OAuth, privacy, evaluation, idempotency, Voice, the practice loop and the four core tools. Governs those areas on any conflict.

  • teaching-intelligence.md - the complementary Teaching Intelligence specification: lessons, knowledge atoms, the Curriculum Track Compiler, the Session Compiler, pedagogical RAG, editorial ingestion, CEFR classification and the Model Gateway. Governs those areas on any conflict.

  • context.md - company stage and risk tolerance: what this project cannot afford to break.

  • identity/README.md - identity design for the remote MCP server: WorkOS AuthKit as authorization server, OLCP as resource server, provider comparison, minors and GDPR, endpoints, EU data residency.

Related MCP server: learn-cli

Operations

  • execution/s0-readiness.md - what runs today, what is blocked, and the human setup checklist that unblocks the identity spikes. Read before starting the first code card.

Operating contracts

Research

Primary-source reports, kept because the decisions they support are still live.

The proof of concept

poc/ in the repository root is a retained experiment, not a migration target. It accepts a learner_id and keeps state in JSON - both of which the product forbids. It is kept because its findings are what justified the product design, and it must not be extended.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers