Status · Implemented

Production status and operating boundaries

The deployed product surface, operating boundaries, and extension policy.

Available now

Public site, documentation, official video walkthrough, public demo, authentication, dashboard, and notebook workspace.
Source ingestion, chunking, concept relationships, teach-back, mastery, review, tutoring, evidence, activity, and trace views.
Typed prompts, tools, workflows, checkpoints, hybrid retrieval, graph projection, and OTLP trace export boundaries.
Versioned evaluation suites, CI gates, performance checks, and deployment health routes.

It is not a replacement for a teacher or domain expert.
It does not claim perfect understanding detection.
It does not treat chat completion as mastery.
It does not allow workflows to rewrite and deploy their own policies.
It does not use decorative streaks or fabricated confidence metrics as proof of learning.

Diagnosis quality depends on the quality and scope of the source material.
Production credentials are environment-specific and remain outside the repository.
Evaluation coverage must continue growing across subjects and failure types.
Long-running indexing may require a dedicated worker as workloads grow.

Additional sign-in providers can be added without changing canonical authorization boundaries.
Additional generation providers must satisfy the same prompt, schema, evaluation, and tracing contracts.
New learning formats must remain evidence-linked and preserve learner-state ownership in Postgres.
New source formats must preserve provenance, workspace isolation, and deletion cascades.
External references require explicit learner review before becoming source evidence.
Product extensions are admitted only after deterministic regression and production-observability checks pass.