[System] [Sync] [2026-05-13] Capturing GEPA mutations from AROS runtime

Author: wong-ziyi

Grant_Write_Pipeline/KIs/grant_funder_profiles/metadata.json

@@ -15,5 +15,10 @@
       "title": "SPReAD Form 1 constraint reference"
     }
   ],
-  "tags": ["grant-writing", "funder-constraints", "universal-pipeline", "compliance"]
-}
+  "tags": [
+    "grant-writing",
+    "funder-constraints",
+    "universal-pipeline",
+    "compliance"
+  ]
+}

KAKENHI_Pipeline/KIs/kakenhi_e_application_system/metadata.json

@@ -2,5 +2,11 @@
   "name": "kakenhi_e_application_system",
   "summary": "Comprehensive operational guide for the JSPS KAKENHI e-Application System, covering all post-award procedures for researchers including F-6/F-7, F-19-1, and budget change requests.",
   "updated_at": "2026-05-11",
-  "tags": ["kakenhi", "e-rad", "jsps", "grant-reporting", "application-system"]
-}
+  "tags": [
+    "kakenhi",
+    "e-rad",
+    "jsps",
+    "grant-reporting",
+    "application-system"
+  ]
+}

KAKENHI_Pipeline/KIs/kakenhi_management_pipeline/metadata.json

@@ -1,6 +1,12 @@
 {
   "name": "kakenhi_management_pipeline",
-  "summary": "Core specification (SPEC.md), README, Templates, and Tools for the KAKENHI_Pipeline v2.0.0 — a universal, researcher-agnostic JSPS KAKENHI grant lifecycle management system. Contains runtime variable reference, grant folder canonical architecture, component contracts, cross-platform compatibility rules, and AROS integration map.",
+  "summary": "Core specification (SPEC.md), README, Templates, and Tools for the KAKENHI_Pipeline v2.0.0 \u2014 a universal, researcher-agnostic JSPS KAKENHI grant lifecycle management system. Contains runtime variable reference, grant folder canonical architecture, component contracts, cross-platform compatibility rules, and AROS integration map.",
   "updated_at": "2026-05-11",
-  "tags": ["kakenhi", "pipeline", "spec", "grant-management", "aros"]
-}
+  "tags": [
+    "kakenhi",
+    "pipeline",
+    "spec",
+    "grant-management",
+    "aros"
+  ]
+}

KAKENHI_Pipeline/KIs/kakenhi_report_forms/metadata.json

@@ -2,5 +2,11 @@
   "name": "kakenhi_report_forms",
   "summary": "Quick-reference for all JSPS KAKENHI post-award form codes, reporting timeline, submission decision trees, and the official F-19-1 Word template (cf-19.docx).",
   "updated_at": "2026-05-11",
-  "tags": ["kakenhi", "forms", "cf-19", "f-19-1", "reporting"]
-}
+  "tags": [
+    "kakenhi",
+    "forms",
+    "cf-19",
+    "f-19-1",
+    "reporting"
+  ]
+}

KAKENHI_Pipeline/KIs/publication_grant_map/metadata.json

@@ -2,5 +2,10 @@
   "name": "publication_grant_map",
   "summary": "Generic structure and rules for the publication-to-grant attribution matrix used across all KAKENHI reporting. Contains the template format, not researcher-specific data.",
   "updated_at": "2026-05-11",
-  "tags": ["kakenhi", "publications", "attribution", "grant-mapping"]
-}
+  "tags": [
+    "kakenhi",
+    "publications",
+    "attribution",
+    "grant-mapping"
+  ]
+}

workspace_management/Workflows/wiki-update.md

@@ -123,6 +123,16 @@ Ensure `.wiki/index.md` acts as a complete table of contents.
 Prompt the agent:
 > "Rebuild `.wiki/index.md` so that it categorizes and links to every file within the `.wiki/` directory."
 
+## Step 4.5: AROS Policy Evolution (Phase 4)
+
+Trigger the RL-Informed Context Evolution loop to analyze recent curator rewards and propose updates to `CURATION_POLICY.md`.
+Run the following python script via the terminal. It checks the DB lock internally to ensure it doesn't collide with the dashboard daemon.
+
+```bash
+# // turbo
+python3 -c "import sys; import os; sys.path.insert(0, os.path.expanduser('~/.gemini/antigravity/antigravity-evolution/src')); from antigravity_evolution.policy_evolver import propose_policy_update; from antigravity_evolution.policy_analyst import generate_performance_report; report = generate_performance_report(); propose_policy_update(report) if 'error' not in report and report.get('status') != 'insufficient_data' else print('No evolution required: ' + str(report))"
+```
+
 ## Step 5: Auto-Commit
 
 Delegate to the canonical `/lab-commit` workflow. Do NOT write inline `git add` / `git commit` commands here — the lab-commit workflow handles staging, Obsidian symlink verification, project registry updates (e.g., INDEX.csv or PIPELINE_REGISTRY.md), and commit message formatting automatically.