Builder Command Group (~v): Building, Managing, and Memory Control

The ~v command group is your essential toolkit for creating, editing, and managing the components that make up your AI environments. It covers everything from building Alter-Egos, Assistants, and Custom slots to managing the vital memory and session state that keeps your AI workspace efficient and reliable.

Kernel vs DATA: Minimal Core, Full Data OS

• Core (the VAPA “kernel”): This is kept minimal—containing only the essential parser, security invariants, command hooks, and the smallest boot rules. The Core must remain compact to avoid consuming excessive reasoning capacity or causing instruction drift.
• DATA (the VAPA operating system): Everything else—command definitions, flags, example templates, persona metadata, help text, large rule tables, and behavioral knowledge—resides in the VAPA System Data.md file and user Data files. The Builder (~v) is responsible for creating and managing these DATA artifacts.
• Rationale: A small kernel ensures stable, predictable behavior, while a rich DATA layer provides flexible, editable features without bloating runtime.

Key Capabilities of ~v

With ~v, you can:

• Author & Edit: Create new components such as Alter-Ego files, Assistants, Custom slots, Patches, and Data files.
• Memory Control: View and control what the AI currently remembers; instruct it on what to keep or forget to maintain clarity.
• Session Snapshots: Save and restore session snapshots, allowing you to pause and resume work without losing context.
• Optimization: Compact and refresh memory to optimize performance and reduce token usage.
• Environment Management: Manage configurations that define how your AI stack operates and toggle modes like Sleep Mode (~vz).

Relationship to Alter-Ego (~a)

The Builder commands let you design, evolve, and maintain your AI projects, while Alter-Ego commands let you deploy and interact with those projects. Together, they provide a full lifecycle management system for your AI workflows.

---

~v Command Structure

Command	Name	Description	Example
~v	Builder Hub	Entry point to the VAPA Builder menu for creating/editing files.	~v
~vs	VAPA Status	Shows enhanced runtime status, including active stack and slot health.	~vs
~env	Env Report	Displays environment capabilities, host info, and detected profile.	~env
~ve	Env Profile	View or change environment optimisation profiles (e.g., auto, pro).	~ve auto
~vz	Sleep Mode	Toggles VAPA Sleep Mode (pauses slot-driven instructions).	~vz on
~vr	Region	Sets regional preferences (language, locale, currency, units).	~vr AU
~guide	Guide Toggle	Toggles proactive contextual suggestions on or off.	~guide off

Builder Sub-Modes (Conceptual via ~v Hub):

• ~vba — Build Alter-Ego
• ~vbv — Build Assistant
• ~vbc — Build Custom Slot
• ~vbp — Build Patch
• ~vbd — Build Data File

Examples of Use:

• ~v — Opens the interactive menu to start building a new Assistant or Alter-Ego.
• ~vs — Checks if your loaded slots are at 100% health or if memory is getting “sludgy.”
• ~vz on — Puts VAPA in sleep mode to perform generic tasks without project-specific interference.
• ~vr US — Quickly switches regional formatting to US standards for a specific document.

---

Recommendations:

• Memory Hygiene: Use ~vs regularly during long sessions to monitor “Slot Health.” If health drops, use the Builder to refresh or compact the session.
• Profile Optimization: Use ~env to see what your host supports. If you are in a tool-rich environment like Abacus, ensure ~ve is set to take full advantage of file and web tools.
• Sticky Settings: Most ~v sub-commands (like ~vr and ~ve) are “sticky,” meaning they persist until you manually change them or reset the session.