Prompt #124

Variables

{'name': 'feature', 'description': 'e.g. agent-quality-supervisor'}, {'name': 'feature_description', 'description': 'what + why migrating'}, {'name': 'source_repo', 'description': 'glug|rag_stack|yoga'}, {'name': 'target_repo', 'description': 'glug|rag_stack|yoga'}, {'name': 'topic', 'description': 'backup-tag slug'}

Tags

stack-aware,migration,wave,strict-separation,rag-stack-45

Source

research-2026-05-01-stack-aware-handcrafted

Use count

0

Created

2026-05-01T18:30:35.938632+00:00

Updated

2026-05-01T18:30:35.938632+00:00

Content

Plan a strict-separation migration of `{feature}` between glug/rag-stack/yoga repos.

Per user 2026-05-01: glug = web framework only; rag-stack = agent platform + governance + RAG + automation; yoga = customer code (independent customer-shippable).

Wave-pattern (from rag-stack#45):
1. Identify ownership: which files belong where? Reference `feedback_strict_glug_ragstack_separation.md`.
2. Wave-A: ADD files to target repo (1 PR), keeps source untouched.
3. Wave-B: REMOVE from source repo + rewire imports (paired PR), merge atomically.
4. Wave-C (only if cross-language coupling): introduce HTTP API on target, refactor source to use HTTP client.

Audit requirement post-migration:
- `grep -rE "^(from {target_repo}|import {target_repo})" /nvmetank1/projects/{source_repo}/ --include='*.py'` MUST return empty
- Backup with `cp -r` to `/tank2/backups/$(date +%Y-%m-%d)/{topic}/` BEFORE move
- Use `sqlite-pre-write-check` if any DB is shared
- Each Wave PR runs full test suite + audit grep before merge

Feature being migrated: {feature_description}