Name: subsystem-naming-policy
Author: Zynapses

Prompt file imported from Zynapses/Radiant (.windsurf/workflows/subsystem-naming-policy.md). Copyright stays with the author.

Subsystem Naming Policy

Core Rule

A subsystem name MUST either be globally unique OR explicitly scoped by its parent. If a name appears under the wrong parent, it MUST be renamed.

Naming Categories

Category	Rule	Examples
Unique names	Stand alone, no prefix needed	OMEGA, LIVS, SENTINEL, Delight, Curator, Dojo
Scoped children	`Parent-Child` format	CATO Genesis, Cortex Graph-RAG, OMEGA Firmware, OMEGA Quantum
Misplaced names	Rename to match actual parent	~~Genesis App~~ → OMEGA Lab, ~~Genesis Auto-Tool~~ → Tool Forge

Casing Conventions

Context	Convention	Example
File names	kebab-case	`tool-forge.service.ts`, `omega-lab/`
DB tables	snake_case	`tool_forge_requests`, `omega_brains`
TypeScript types	PascalCase	`ToolForgeRequest`, `OmegaForge`
Service instances	camelCase	`toolForge`, `economicCortex`
UI labels	Title Case	"OMEGA Lab", "Cato Genesis"
Acronyms in UI/docs	ALL CAPS	CATO, OMEGA, LIVS, SENTINEL
Acronyms in file names	lowercase	`cato/`, `omega/`, `livs/`

Directory Structure

Services MUST live under their parent subsystem directory:

lambda/shared/services/
├── cato/           # CATO subsystem (includes Genesis gates)
├── omega/          # OMEGA subsystem
├── organism/       # Organism subsystem (includes Tool Forge)
├── cortex/         # Cortex subsystem (includes Graph-RAG)
└── [subsystem]/    # Each subsystem gets its own directory

Pre-Flight Checklist for New Subsystems

Before creating a new subsystem or feature:

Search existing names: grep -r "YourProposedName" --include="*.ts" --include="*.tsx"
Check glossary: Read docs/17-GLOSSARY.md for existing term definitions
Verify uniqueness: The name must NOT already be used by another subsystem
Choose parent: If this is a child feature, prefix with parent name
Update glossary: Add the new term to docs/17-GLOSSARY.md
Update manifest: Add triggers to docs/DOCUMENTATION-MANIFEST.json

Known Exceptions (Do NOT Rename)

These are correctly scoped and must stay as-is:

Name	Parent	Reason
CATO Genesis	CATO	Developmental gate system — deeply entrenched (14+ importers, 2 DB tables, triggers, RLS)
Cortex Graph-RAG	Cortex	Already properly parent-scoped

Completed Renames

Old Name	New Name	Date	Migration
Genesis App	OMEGA Lab	2026-02-09	Directory rename
Genesis Forge App	OMEGA Forge	2026-02-09	Directory rename
Genesis Auto-Tool	Tool Forge	2026-02-09	`V2026_02_09_001__tool_forge_rename.sql`

Enforcement

AI agents MUST check this policy before creating new subsystems
Code reviewers MUST reject PRs that introduce naming collisions
The glossary (docs/17-GLOSSARY.md) is the canonical source of truth for subsystem names

Install subsystem-naming-policy and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Subsystem Naming Policy ## Core Rule > **A subsystem name MUST either be globally unique OR explicitly scoped by its parent.** > **If a name appears under the wrong parent, it MUST be renamed.** ## Naming Categories | Category | Rule | Examples | |----------|------|---------| | **Unique names** | Stand alone, no prefix needed | OMEGA, LIVS, SENTINEL, Delight, Curator, Dojo | | **Scoped children** | `Parent-Child` format | CATO Genesis, Cortex Graph-RAG, OMEGA Firmware, OMEGA Quantum | | **Misplaced names** | Rename to match actual parent | ~~Genesis App~~ → OMEGA Lab, ~~Genesis Auto-Tool~~ → Tool Forge | ## Casing Conventions | Context | Convention | Example | |---------|-----------|---------| | **File names** | kebab-case | `tool-forge.service.ts`, `omega-lab/` | | **DB tables** | snake_case | `tool_forge_requests`, `omega_brains` | | **TypeScript types** | PascalCase | `ToolForgeRequest`, `OmegaForge` | | **Service instances** | camelCase | `toolForge`, `economicCortex` | | **UI labels** | Title Case | "OMEGA Lab", "Cato Genesis" | | **Acronyms in UI/docs** | ALL CAPS | CATO, OMEGA, LIVS, SENTINEL | | **Acronyms in file names** | lowercase | `cato/`, `omega/`, `livs/` | ## Directory Structure Services MUST live under their parent subsystem directory: ``` lambda/shared/services/ ├── cato/ # CATO subsystem (includes Genesis gates) ├── omega/ # OMEGA subsystem ├── organism/ # Organism subsystem (includes Tool Forge) ├── cortex/ # Cortex subsystem (includes Graph-RAG) └── [subsystem]/ # Each subsystem gets its own directory ``` ## Pre-Flight Checklist for New Subsystems Before creating a new subsystem or feature: 1. **Search existing names**: `grep -r "YourProposedName" --include="*.ts" --include="*.tsx"` 2. **Check glossary**: Read `docs/17-GLOSSARY.md` for existing term definitions 3. **Verify uniqueness**: The name must NOT already be used by another subsystem 4. **Choose parent**: If this is a child feature, prefix with parent name 5. **Update glossary**: Add the new term to `docs/17-GLOSSARY.md` 6. **Update manifest**: Add triggers to `docs/DOCUMENTATION-MANIFEST.json` ## Known Exceptions (Do NOT Rename) These are correctly scoped and must stay as-is: | Name | Parent | Reason | |------|--------|--------| | **CATO Genesis** | CATO | Developmental gate system — deeply entrenched (14+ importers, 2 DB tables, triggers, RLS) | | **Cortex Graph-RAG** | Cortex | Already properly parent-scoped | ## Completed Renames | Old Name | New Name | Date | Migration | |----------|----------|------|-----------| | Genesis App | OMEGA Lab | 2026-02-09 | Directory rename | | Genesis Forge App | OMEGA Forge | 2026-02-09 | Directory rename | | Genesis Auto-Tool | Tool Forge | 2026-02-09 | `V2026_02_09_001__tool_forge_rename.sql` | ## Enforcement - AI agents MUST check this policy before creating new subsystems - Code reviewers MUST reject PRs that introduce naming collisions - The glossary (`docs/17-GLOSSARY.md`) is the canonical source of truth for subsystem names

{ "prompt": "# Subsystem Naming Policy\n\n## Core Rule\n\n> **A subsystem name MUST either be globally unique OR explicitly scoped by its parent.**\n> **If a name appears under the wrong parent, it MUST be renamed.**\n\n## Naming Categories\n\n| Category | Rule | Examples |\n|----------|------|---------|\n| **Unique names** | Stand alone, no prefix needed | OMEGA, LIVS, SENTINEL, Delight, Curator, Dojo |\n| **Scoped children** | `Parent-Child` format | CATO Genesis, Cortex Graph-RAG, OMEGA Firmware, OMEGA Quantum |\n| **Misplaced names** | Rename to match actual parent | ~~Genesis App~~ → OMEGA Lab, ~~Genesis Auto-Tool~~ → Tool Forge |\n\n## Casing Conventions\n\n| Context | Convention | Example |\n|---------|-----------|---------|\n| **File names** | kebab-case | `tool-forge.service.ts`, `omega-lab/` |\n| **DB tables** | snake_case | `tool_forge_requests`, `omega_brains` |\n| **TypeScript types** | PascalCase | `ToolForgeRequest`, `OmegaForge` |\n| **Service instances** | camelCase | `toolForge`, `economicCortex` |\n| **UI labels** | Title Case | \"OMEGA Lab\", \"Cato Genesis\" |\n| **Acronyms in UI/docs** | ALL CAPS | CATO, OMEGA, LIVS, SENTINEL |\n| **Acronyms in file names** | lowercase | `cato/`, `omega/`, `livs/` |\n\n## Directory Structure\n\nServices MUST live under their parent subsystem directory:\n```\nlambda/shared/services/\n├── cato/ # CATO subsystem (includes Genesis gates)\n├── omega/ # OMEGA subsystem\n├── organism/ # Organism subsystem (includes Tool Forge)\n├── cortex/ # Cortex subsystem (includes Graph-RAG)\n└── [subsystem]/ # Each subsystem gets its own directory\n```\n\n## Pre-Flight Checklist for New Subsystems\n\nBefore creating a new subsystem or feature:\n\n1. **Search existing names**: `grep -r \"YourProposedName\" --include=\"*.ts\" --include=\"*.tsx\"`\n2. **Check glossary**: Read `docs/17-GLOSSARY.md` for existing term definitions\n3. **Verify uniqueness**: The name must NOT already be used by another subsystem\n4. **Choose parent**: If this is a child feature, prefix with parent name\n5. **Update glossary**: Add the new term to `docs/17-GLOSSARY.md`\n6. **Update manifest**: Add triggers to `docs/DOCUMENTATION-MANIFEST.json`\n\n## Known Exceptions (Do NOT Rename)\n\nThese are correctly scoped and must stay as-is:\n\n| Name | Parent | Reason |\n|------|--------|--------|\n| **CATO Genesis** | CATO | Developmental gate system — deeply entrenched (14+ importers, 2 DB tables, triggers, RLS) |\n| **Cortex Graph-RAG** | Cortex | Already properly parent-scoped |\n\n## Completed Renames\n\n| Old Name | New Name | Date | Migration |\n|----------|----------|------|-----------|\n| Genesis App | OMEGA Lab | 2026-02-09 | Directory rename |\n| Genesis Forge App | OMEGA Forge | 2026-02-09 | Directory rename |\n| Genesis Auto-Tool | Tool Forge | 2026-02-09 | `V2026_02_09_001__tool_forge_rename.sql` |\n\n## Enforcement\n\n- AI agents MUST check this policy before creating new subsystems\n- Code reviewers MUST reject PRs that introduce naming collisions\n- The glossary (`docs/17-GLOSSARY.md`) is the canonical source of truth for subsystem names", "variables": [], "notes": "Policy - Subsystem names must be globally unique or explicitly parent-scoped. No name collisions allowed.", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/Zynapses/Radiant", "path": ".windsurf/workflows/subsystem-naming-policy.md", "ref": "dfcafdfbbf2191ee48921207c5c8a8ca77da957b", "url": "https://github.com/Zynapses/Radiant/blob/dfcafdfbbf2191ee48921207c5c8a8ca77da957b/.windsurf/workflows/subsystem-naming-policy.md", "key": "Zynapses/Radiant/.windsurf/workflows/subsystem-naming-policy.md" } } }

subsystem-naming-policy

About