gurta-context

Working on the Gurta trading dashboard backend requires core context covering repository structure, production topology, API endpoints, and safety rules to ensure consistency and adherence to non-negotiable constraints.

To follow safety rules when modifying the Gurta trading dashboard, load the core context Skill before starting any task to access non-negotiable constraints, holdout policies, and known bug classes that prevent critical errors.

Yes, the Gurta backend context includes detailed production topology describing infrastructure components and services, alongside critical API endpoints for health checks and data retrieval to guide development.

The default workflow for executing a Gurta task involves loading the context Skill first to map the repository structure, review internal agents like Gerald and Lucille, and verify safety rules before making changes.

Prior knowledge of the Gurta system is required because this context provides foundational conventions, validated findings, and details on Camber research compute setup without explaining the underlying system components from scratch.

Yes, the Gurta backend context documents known bug classes and potential issues to be aware of, alongside free-tier key factory instructions and holdout policies, helping you anticipate limitations before updates.