Skip to content

Add compile step to translate course manifest into LLM-consumable SudoLang interface object #36

@janhesters

Description

@janhesters

Description:

Problem

The current course.manifest.json format, while comprehensive and human-readable, may not be optimized for LLM consumption. Large manifest files could result in excessive token usage when processed by AI systems.

Proposed Solution

Implement a compile step that translates the standard JSON manifest into a more token-efficient SudoLang interface object format.

Benefits

  • Token Efficiency: Reduce token consumption when LLMs process course manifests
  • Performance: Faster AI processing of course structure and metadata
  • Cost Optimization: Lower API costs for AI-powered course features
  • Compatibility: Maintain existing JSON format while adding optimized variant

Implementation Ideas

  • Create a course.manifest.sudo file alongside the standard JSON manifest
  • Develop transpilation tools to convert JSON → SudoLang format
  • Ensure the SudoLang version contains all essential course structure information
  • Consider this for the manifest schema v2.1 or v3.0

Acceptance Criteria

  • Define SudoLang interface object schema for course manifests
  • Create transpilation utility (JSON → SudoLang)
  • Validate token reduction compared to JSON format
  • Update course structure specification
  • Maintain backward compatibility with JSON manifests

Priority

Future version (not MVP) - optimize after core functionality is established.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions