-
Notifications
You must be signed in to change notification settings - Fork 69
chore - RFC 106 full graph/context conformance and evaluation #1019
Copy link
Copy link
Open
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationeditor integrationSuggestions, features, or bugs related to the Editor integration (`vscode extension` and LSP)Suggestions, features, or bugs related to the Editor integration (`vscode extension` and LSP)incan compilerSuggestions, features, or bugs related to the Compiler (frontend/backend/codegen)Suggestions, features, or bugs related to the Compiler (frontend/backend/codegen)toolingSuggestions, features, or bugs related to the Tooling (CLI/formatter/test runner)Suggestions, features, or bugs related to the Tooling (CLI/formatter/test runner)
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationeditor integrationSuggestions, features, or bugs related to the Editor integration (`vscode extension` and LSP)Suggestions, features, or bugs related to the Editor integration (`vscode extension` and LSP)incan compilerSuggestions, features, or bugs related to the Compiler (frontend/backend/codegen)Suggestions, features, or bugs related to the Compiler (frontend/backend/codegen)toolingSuggestions, features, or bugs related to the Tooling (CLI/formatter/test runner)Suggestions, features, or bugs related to the Tooling (CLI/formatter/test runner)
Type
Projects
- StatusShow more project fieldsBacklog
Area
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
Plan
Done when