Codmir — Name, Vision, and Roadmap

Name & Meaning

• Code → creation, structure, logic.
• Mir (Мир) → “world.”

Together, Codmir means “the world of code.” It’s a place where any project can live — software, trading, content — coordinated by people and AI agents.

Vision

“You should be able to tell your AGI what to do — and it should create, manage, and evolve projects for you.”

Codmir is the AI‑first platform for creating and evolving projects. It acts as the shared brain and workspace where humans and agents:

• Plan, decompose, and assign work.
• Execute tasks (code edits, content generation, tests, docs, PRs).
• Preserve context, artifacts, and decisions as durable memory.

The long‑term ambition is a library of 200+ application types (project templates) spanning software, trading, content, data, research, and more — each powered by specialized agents.

First Concept: Collaboration + Task Management

We start with a rock‑solid foundation:

• AI‑assisted tickets (triage, enrichment, prioritization).
• Assignment to people or agents (including “code agents”).
• Live execution with streaming logs, artifacts, and diffs.
• A “Context Capsule” for every ticket: story, references, diffs, logs, PRs.

This is the scaffolding that future agents and project types build upon.

Why Codmir?

• Unified projects → Personal blog, trading bot, web app — same flexible core.
• AI‑native → Designed for agents to read/write context, not just humans.
• Scalable → Start with one task, grow into an orchestrated, multi‑agent program.
• Durable memory → Context Capsules and a Reference Graph link what changed and why.

Roadmap (High‑Level)

• Phase 1 — Collaboration Core
  • Tickets as Context Capsules with agent runs and streaming logs.
  • Kanban/List views, comments, mentions, attachments.
• Phase 2 — Multi‑Domain Templates
  • Software, Content, Trading, Data notebooks.
  • Integrations: GitHub/Vercel/Supabase/Slack/Discord.
• Phase 3 — AGI Orchestration
  • Sub‑agents that decompose work into small, verifiable steps.
  • Reusable workflows (YAML/JSON) and a marketplace of agent plugins.
  • Continuous memory for multi‑session progress.

Principles

• Context is the product → tickets carry story, signals, code refs, diffs, tests.
• Agents are first‑class → tasks are computable and auditable by AIs.
• Safety by design → permissions, isolation (Docker), and immutable history.
• Open ecosystem → plugins and tools that the community can build and share.

FAQ

• Is Codmir only for coding?
  • No. “Code” is the discipline; “world” is the scope. Content, trading, ops — all welcome.
• Why start with task management?
  • It’s the coordination layer for people and agents. Strong foundations unlock everything else.
• What’s next for agents?
  • Sub‑agents that plan, edit, test, and PR in small, reliable steps — then compose into larger programs.