Mikobase GraphQL support GitHub issue

• • Idea
• • Why
• • Sketch (not committed)
• • Implementation cost
• • Status

{"vibecode": {
    "doc": "mikobase-graphql",
    "role": "forward-looking sketch of a GraphQL surface for mikobase: classes become GraphQL types, properties become fields, references become relationships; deferred well past v1",
    "key_concepts": ["graphql_surface", "class_to_type_mapping", "q0_translation",
        "frontend_compatibility"],
    "status": "brainstorm"
}}

Idea GitHub issue

Eventually, expose Mikobase data via GraphQL — clients can issue GraphQL queries against a Mikobase and receive structured responses, the same shape they'd get from any GraphQL backend.

Why GitHub issue

• GraphQL is widely understood; many front-end ecosystems expect it.
• The Mikobase schema (classes + records) maps naturally onto GraphQL's type system.
• Q0 queries already do the equivalent work; a GraphQL layer is mostly translation between query languages.

Sketch (not committed) GitHub issue

• Each Mikobase class becomes a GraphQL type.
• Class properties become GraphQL fields.
• References between records become GraphQL relationships.
• A Mikobase server endpoint accepts POSTs of GraphQL queries and returns the resolved JSON.

Implementation cost GitHub issue

Substantial. Beyond bundling a GraphQL parser (Lua has graphql-lua or similar; size ~1500–3000 lines), the translation layer needs to:

• Map GraphQL queries to Q0 expressions.
• Walk Mikobase's class graph for nested selections.
• Handle pagination, filtering, sorting per the GraphQL conventions.
• Implement GraphQL's introspection (schema queries) over the Mikobase class catalog.

Status GitHub issue