Back to Vibely

Documentation

CLI reference, architecture docs, and strategic briefs.

CLI Reference

vibely init <name>

Scaffold a new Vibe project with .vibely SIR file and .env

--topology sequential|parallel|hierarchical--model mercury-pro
vibely dev

Start local hot-reloading environment with Vibe-Sync file watcher

--open (launch Graph Canvas in browser)--port 4200
vibely check

Lint the graph for circular dependencies, dangling nodes, vibe risks, and tool-auth errors

--file project.vibely
vibely run [intent]

Execute a swarm from the terminal — compile intent on-the-fly or load from .vibely file

--step (pause after each node)--dry (show plan only)--file project.vibely
vibely push

Sync local SIR changes to the cloud engine

--file project.vibely--cloud <url>
vibely trace <run_id>

Stream live thought-logs and state transitions from a running swarm

--live (default)

# Quick start

$ npm run vibely -- init my-swarm

$ cd my-swarm

$ npm run vibely -- dev --open

$ npm run vibely -- run "Build a team that researches and writes"

Documentation Index

V1.0 Product Status

Complete factory inventory — what V1.0 IS and is NOT

docs/V1.0-PRODUCT-STATUS.md

Strategic Alignment

Canonical strategic reference across all 6 dimensions

docs/STRATEGIC-ALIGNMENT-FINAL.md

Master Lifecycle Graph

The RootGraph — 6-phase lifecycle DAG with 4 Queen Hives

docs/MASTER-LIFECYCLE-GRAPH.md

Platform Status

Deployed asset summary — what we have today

docs/PLATFORM-STATUS.md

VoiceCosmos Product Brief

Sales playbook v1.1 with 4 pillars, demo script, ROI

docs/VOICECOSMOS-PRODUCT-BRIEF.md

Team Execution Brief

6 tasks, 12-week timeline, MRR targets

docs/VOICECOSMOS-TEAM-EXECUTION-BRIEF.md

Activation Playbook

Day Zero deployment, SONA wiring, NL Critic setup

docs/VOICECOSMOS-ACTIVATION-PLAYBOOK.md

Strategic Directives

North Star + engineering guardrails + edge quarantine

docs/STRATEGIC-DIRECTIVES.md

Studio Munich Integration

Fashion production DAG — first vertical deployment

docs/STUDIO-MUNICH-INTEGRATION-PLAN.md

Architecture Map

4-layer technical architecture for CTO audiences

docs/ARCHITECTURE-MAP.md

.vibely File Format (SIR Schema)

{
  "version": "1.0.0",
  "metadata": {
    "project_name": "research-swarm",
    "vibe_author": "developer",
    "global_temperature": 0.7,
    "description": "A research team that scrapes and summarizes"
  },
  "topology": {
    "type": "hierarchical",
    "max_concurrency": 5,
    "entry_node": "orchestrator"
  },
  "nodes": [
    {
      "id": "orchestrator",
      "role": "Coordinator",
      "persona": "Manages task distribution and collects results.",
      "model": "mercury-ultra",
      "tools": [],
      "dependencies": []
    },
    {
      "id": "researcher",
      "role": "Researcher",
      "persona": "Expert at finding information from multiple sources.",
      "model": "mercury-pro",
      "tools": ["web_search", "arxiv_api"],
      "dependencies": ["orchestrator"]
    }
  ],
  "edges": [
    { "from": "orchestrator", "to": "researcher", "type": "control" }
  ],
  "telemetry": { "log_level": "info", "streaming": true }
}