bc0edb1827
The Knowledge Base directory was entered in two places — the Configuration node's knowledge_base path and the Knowledge Base Loader node's path — a duplication with no benefit. Remove the Knowledge Base Loader node and have the Configuration node load the Knowledge Base itself, emitting it on a new knowledge_base output wired into the Resolver. - New nodes/kb_loading.py holds the shared, process-wide load-once cache and package-relative path resolution (extracted from the deleted loader node). - Configuration node: gains a knowledge_base_reload input and a KNOWLEDGE_BASE output; RETURN is now (config, knowledge_base, warnings, errors). A KB load failure surfaces on errors while the config is still emitted (the Analyzer and Validator do not need the KB). - Remove SceneCompilerKnowledgeBaseLoader from the node registrations. - Rebuild the example workflow to wire Configuration.knowledge_base -> Resolver. - Docs (README, docs/nodes.md) updated; tests moved to test_kb_loading.py. BREAKING CHANGE: the Knowledge Base Loader node is removed. Workflows that used it must load the Knowledge Base via the Configuration node's knowledge_base output. Co-authored-by: kunail0804 <kunail0804@gmail.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Documentation
Project documentation is maintained primarily in the
GitHub Wiki, and the
authoritative specification is MASTER_SPEC.md at the
repository root.
This docs/ directory holds documentation that is not part of the wiki —
for example design notes, developer guides, and generated references added in
later phases.
Where to look
- Overview & vision — wiki Overview and Vision
- Requirements — wiki Requirements and Success Criteria
- Architecture & pipeline — wiki Architecture and Pipeline
- Data model & schemas — wiki Data Model, Scene JSON and Schemas
- Knowledge Base — wiki Knowledge Base
- Contributing —
CONTRIBUTING.md