Skip to content

chore - RFC 106 full graph/context conformance and evaluation #1019

Description

@dannymeijer

Area

  • Compiler (frontend/backend/codegen)
  • Tooling (CLI/formatter/test runner)
  • Editor integration (LSP/VS Code extension)
  • Documentation

Summary

RFC 106 is a v0.6 full-scope commitment. The initial JSONL exporter and individual graph consumers are necessary but not sufficient: the release needs one conformance and evaluation contract spanning checked and tolerant export, LSP, Architect, MCP task context, process-risk facts, Rust/Incan inspection, and external ingestion boundaries.

Scope

  • In scope:
    • A versioned compatibility corpus for required RFC 106 node, edge, provenance, identity, degraded-state, and snapshot/staleness semantics.
    • Cross-surface tests proving that CLI, live LSP, Architect, and MCP context use the same fact meanings and preserve source anchors, provenance, and stale-state behavior.
    • Hand-labelled task-context evaluation for precision, recall, budget use, determinism, freshness, broken-source behavior, and latency on stdlib-sized and workspace-sized projects.
    • Risk-signal evaluation with visible raw measures and a size or module control before any predictive claim.
    • Explicit evidence that external tools consume Incan facts without becoming a semantic authority.
  • Out of scope:
    • Hosted indexing, mandatory embeddings, or a generic polyglot parser.
  • Risks:
    • A passing exporter can still conceal divergent consumer semantics; this corpus must reject that split-brain outcome.

Plan

  1. Define the full RFC 106 fixture matrix and expected graph/context records.
  2. Exercise the matrix through every delivery child of feature - RFC 106 compiler-backed agent context graph #573.
  3. Publish machine-readable results and human-readable limitations.

Done when

  • Every full-scope RFC 106 delivery path passes the same compatibility corpus.
  • Context packing and risk evaluation have recorded, reproducible results and limitations.
  • Release evidence demonstrates one compiler-backed fact authority across all consumers.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationeditor integrationSuggestions, features, or bugs related to the Editor integration (`vscode extension` and LSP)incan compilerSuggestions, features, or bugs related to the Compiler (frontend/backend/codegen)toolingSuggestions, features, or bugs related to the Tooling (CLI/formatter/test runner)

    Type

    Projects

    • Status
      Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions