1
2
3
4
5
6
7
8
9
10
11
12
13
14
|
{
"name": "system-audit",
"description": "Comprehensive procedure for analyzing VFS health, module dependencies, and system configuration state.",
"tags": [
"audit",
"system",
"structure",
"verification"
],
"category": "system",
"created": "2026-06-23T12:15:26.571Z",
"updated": "2026-06-24T21:58:03.530Z",
"content": "---\nname: system-audit\ndescription: Comprehensive procedure for analyzing VFS health, module dependencies, and system configuration state.\ntags: [audit, system, structure, verification]\ncategory: system\n---\n## Steps\n1. **VFS Snapshot:**\n - Run `get_status` to check overall FS health, module load count, and memory usage.\n - Use `list_files` recursively on critical directories (`/`, `/_mods/`, `/_contexts/`, `/skills/`) to map the current landscape.\n\n2. **Module Verification:**\n - Execute `list_available_modules` to verify core vs extension distribution.\n - Use `get_module_status` to identify modified modules that may require synchronization or updates.\n - For critical path modules, use `view_module` to inspect logic for bottlenecks or security flaws.\n\n3. **Context & Skill Alignment:**\n - Check `/_contexts/` to ensure role manifests align with the actual skills available via `list_skills`.\n - Identify \"Skill Gaps\" (Roles requiring skills that do not yet exist in the `/skills/` directory).\n\n4. **Dependency Mapping:**\n - Use `nvfs_resolve` with concepts like \"security\", \"memory\", or \"network\" to see how semantic links are structured.\n - Cross-reference `session_recent` to ensure current architectural changes align with the project trajectory.\n\n5. **Reporting:**\n - Synthesize findings into a \"System State Report\" highlighting:\n - **Integrity:** (Are files where they should be?)\n - **Consistency:** (Do roles match skills?)\n - **Risks:** (Are there modified modules without tests?)\n"
}
|
