research: qualify current MindGraph for public-core portability - #2
Closed
camerontjs-dot wants to merge 1 commit into
Closed
camerontjs-dot wants to merge 1 commit into
camerontjs-dot wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Question
Does the current standalone MindGraph implementation clear the bounded portability gate required for inclusion in the MainFrame v0.3.0 public core?
Frozen source under test
4d292179e1478b999bc6b7c36f9de564c07bd1d9ed7803dcf9718005fd190a12f0537b69dcb8b349f4f71641324120e85e1ab28a0bc48944c9877222345043110661016321546597f76a487d05a62f6ba2bdae40ad7a3d101597e077c5e230847b850dc00d4640Observed result
The clean GitHub-hosted Ubuntu / Python 3.11 installation completed, but the maintained MindGraph test suite failed during collection before the synthetic retrieval boundary could run.
Observed blockers:
src/mindgraph/query.pyreferencesLiteralwithout importing it, causingNameErroracross multiple test modules.mcp>=1.0.0resolved to MCP 2.2.0; MindGraph MCP tests importcreate_connected_server_and_client_session, which is unavailable in that installed version.tests/test_pruning.pyimportspruning_pass, which is unavailable in the clean checkout/package environment.sentence-transformers, Torch 2.14, and a large Linux CUDA dependency stack. This is materially heavier than the bounded retrieval surface MainFrame would need.The workflow preserved the failed test output and environment receipt as an Actions artifact.
Disposition
DEFER_MINDGRAPH_TO_LATER_MINORThis does not establish that the retrieval architecture is unsound. It establishes that the current standalone package does not clear the clean-install/test portability gate required for MainFrame v0.3.0 core promotion. MainFrame is already coherent without MindGraph, so this failure should not block the v0.3.0 release.
A later bounded MindGraph promotion should begin from a repaired, pinned dependency profile and a deliberately slim publication closure, then rerun clean install, ingest, query, provenance, negative-control, missing-state, rebuild, and CI qualification.