Open
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
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.
Summary
Adds the first explicit Holmes NLP component alignment contract and expands the Holmes surface validator so the product spine covers lower-layer NLP families instead of only high-level investigation components.
This PR adds:
docs/NLP_COMPONENT_ALIGNMENT.mdcomponentFamiliesinexamples/holmes-surface.jsonnlpTaskscoverage for primitive, advanced, rule, classical ML, neural, transformer, task-model, graph, and governance lanesrequiredPromotionEvidencefields for algorithm family, task contract, and latency/footprint evidenceWhy
Holmes should absorb a disciplined NLP component taxonomy while remaining broader than a component NLP library. The target architecture is not a model zoo: it is a governed investigation fabric spanning primitives, extraction, classification, retrieval, evidence, graph conversion, policy, evals, and agent/tool orchestration.
Boundary
This PR makes the architecture enforceable at the Holmes contract layer. Runtime implementation and benchmarks belong next in
SociOS-Linux/nlplab, with stable service graduation intoSocioProphet/prophet-platformand pointer-backed retrieval throughSocioProphet/sherlock-search.Validation
Expected local validation:
The validator now requires: