MESO: Knowledge base system improvements and deny-list fixes #1

Open
opened 2026-02-17 18:31:37 +00:00 by The-Azuran · 0 comments
The-Azuran commented 2026-02-17 18:31:37 +00:00 (Migrated from github.com)

Summary

Session on 2026-02-17 analyzed the PPISP paper (NVIDIA, radiance field photometric correction), reorganized the research knowledge base, built 4 new skills + 2 new rules, audited the full MESO system (22 rules, 23 skills, 5 MCP servers), and identified deficiencies.

Completed

  • Research knowledge base reorganized (9 domains, 40+ files, symlinks for game design)
  • Full RAG re-index (41 files, 581 chunks in knowledge_base collection)
  • Memory graph updated (CV domain, PPISP paper entities)
  • 4 new skills: session-startup, research-intake, knowledge-hygiene, cross-domain-synthesis
  • 2 new rules: 18-rule-pipeline, domains/computer-vision
  • Deny-list false positives fixed (token, credentials, secret, password, api_key patterns)
  • Committed to ~/.claude local repo (ce3816d)

Remaining Work

Deny-list fixes (quick)

  • Fix Bash(docker *) — too broad, blocks docker ps/logs. Replace with specific dangerous ops (docker run --privileged, docker exec, etc.)
  • Fix Bash(systemctl *) — blocks systemctl status. Allow read-only ops.
  • Fix Bash(journalctl *) — blocks log reading entirely. Allow read-only.
  • Fix Bash(. *) — blocks bash source command. Scope to prevent sourcing untrusted scripts only.

System deficiencies identified

  • Slim verbose rules (04, 05, 09, 12, 13) to constraint-only, move methodology to skills — frees ~8KB context budget
  • Merge testing-strategy into test-generation (overlapping content)
  • Add feedback loop: knowledge-hygiene quarterly scan of autonomy-correction entities → propose rule amendments
  • Fix NREL MCP server (enabled in settings but server files deleted) — remove from .mcp.json
  • Document 17 dormant government API MCP servers in a manifest
  • Update data-pipelines domain rule to reference API→GIS pipeline

Plan File

~/.claude/plans/meso-knowledge-base-system-improvements.md

🤖 Generated with Claude Code

## Summary Session on 2026-02-17 analyzed the PPISP paper (NVIDIA, radiance field photometric correction), reorganized the research knowledge base, built 4 new skills + 2 new rules, audited the full MESO system (22 rules, 23 skills, 5 MCP servers), and identified deficiencies. ## Completed - [x] Research knowledge base reorganized (9 domains, 40+ files, symlinks for game design) - [x] Full RAG re-index (41 files, 581 chunks in knowledge_base collection) - [x] Memory graph updated (CV domain, PPISP paper entities) - [x] 4 new skills: session-startup, research-intake, knowledge-hygiene, cross-domain-synthesis - [x] 2 new rules: 18-rule-pipeline, domains/computer-vision - [x] Deny-list false positives fixed (token, credentials, secret, password, api_key patterns) - [x] Committed to ~/.claude local repo (ce3816d) ## Remaining Work ### Deny-list fixes (quick) - [ ] Fix `Bash(docker *)` — too broad, blocks `docker ps/logs`. Replace with specific dangerous ops (`docker run --privileged`, `docker exec`, etc.) - [ ] Fix `Bash(systemctl *)` — blocks `systemctl status`. Allow read-only ops. - [ ] Fix `Bash(journalctl *)` — blocks log reading entirely. Allow read-only. - [ ] Fix `Bash(. *)` — blocks bash `source` command. Scope to prevent sourcing untrusted scripts only. ### System deficiencies identified - [ ] Slim verbose rules (04, 05, 09, 12, 13) to constraint-only, move methodology to skills — frees ~8KB context budget - [ ] Merge testing-strategy into test-generation (overlapping content) - [ ] Add feedback loop: knowledge-hygiene quarterly scan of autonomy-correction entities → propose rule amendments - [ ] Fix NREL MCP server (enabled in settings but server files deleted) — remove from `.mcp.json` - [ ] Document 17 dormant government API MCP servers in a manifest - [ ] Update data-pipelines domain rule to reference API→GIS pipeline ## Plan File `~/.claude/plans/meso-knowledge-base-system-improvements.md` 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
valis/techbiont-framework#1
No description provided.