infinite-brain-os: Command for Claude Code

/create-namespace

Create a new namespace file in _system/namespaces/ with lifecycle_state: scratch. Used in personal repos to introduce an ad-hoc namespace for a research session, project area, or governance bucket.

When to use this

• Starting a new research session that does not fit research-general or any other existing namespace.
• Spinning up a project-area namespace that needs its own governance settings.
• Carving out a topic-specific namespace inside a personal repo for future promotion review.

When NOT to use this

• The need fits an existing canonical namespace. Use the existing one.
• You are in a department or company-canon repo. Open a pull request that adds the namespace file directly; do not create scratch namespaces in canon repos.
• The need is for a topic tag, source channel, or author distinction. Use frontmatter fields (tags, source_channel, source_author) on the affected nodes instead.
• You want to build a real namespace from an existing corpus or source folder. Use /build-knowledge-base, which routes through the V2 profile, canon, synthesis, support, and validation machinery.

How it works

The command prompts the operator for four inputs:

1. Namespace name (slug): kebab-case, e.g., research-llm-agents-2026, project-launch-q4, competitor-acme.
2. Purpose: a one-line statement of what this namespace covers.
3. Group: one of operations, research, product, competitive-intel, personal, or a new group documented in the answer.
4. Owner: the operator's handle (defaults to the personal repo owner).

The command then:

1. Verifies the slug does not already exist in _system/namespaces/ (collision check).
2. Writes _system/namespaces/{slug}.md with the required frontmatter and a stub body.
3. Appends a row to _system/namespaces/INDEX.md under the catalog table and under the relevant by-group section.
4. Reports the file paths created or modified and reminds the operator to run bash _system/validate.sh if validate.sh is installed in this personal repo.