index.html

<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Vision | From one agent to an AI-native organization | PassionCode.ai</title><meta name="description" content="Why agents fall apart when nothing holds them together, the four principles PassionCode.ai builds by, and how one agent grows into a team and an organization. Local first, open source, on top of Claude Code, Codex and what comes next.">
  <link rel="canonical" href="https://passioncode.ai/vision/">
  <link rel="alternate" hreflang="en" href="https://passioncode.ai/vision/"><link rel="alternate" hreflang="ru" href="https://passioncode.ai/ru/vision/"><link rel="alternate" hreflang="de" href="https://passioncode.ai/de/vision/"><link rel="alternate" hreflang="fr" href="https://passioncode.ai/fr/vision/"><link rel="alternate" hreflang="pl" href="https://passioncode.ai/pl/vision/"><link rel="alternate" hreflang="ko" href="https://passioncode.ai/ko/vision/"><link rel="alternate" hreflang="es" href="https://passioncode.ai/es/vision/"><link rel="alternate" hreflang="pt-BR" href="https://passioncode.ai/pt-br/vision/"><link rel="alternate" hreflang="zh-Hans" href="https://passioncode.ai/zh-hans/vision/"><link rel="alternate" hreflang="ja" href="https://passioncode.ai/ja/vision/"><link rel="alternate" hreflang="x-default" href="https://passioncode.ai/vision/">
  <meta name="robots" content="index, follow"><meta name="theme-color" content="#0a070d">
  <meta property="og:type" content="article"><meta property="og:site_name" content="PassionCode.ai"><meta property="og:locale" content="en_US"><meta property="og:locale:alternate" content="ru_RU"><meta property="og:locale:alternate" content="de_DE"><meta property="og:locale:alternate" content="fr_FR"><meta property="og:locale:alternate" content="pl_PL"><meta property="og:locale:alternate" content="ko_KR"><meta property="og:locale:alternate" content="es_ES"><meta property="og:locale:alternate" content="pt_BR"><meta property="og:locale:alternate" content="zh_CN"><meta property="og:locale:alternate" content="ja_JP">
  <meta property="og:title" content="The PassionCode.ai vision"><meta property="og:description" content="What keeps an agent working, how one agent grows into a team and an organization, and what works today.">
  <meta property="og:url" content="https://passioncode.ai/vision/">
  <meta property="og:image" content="https://passioncode.ai/assets/passioncode-social-card.png">
  <meta property="og:image:width" content="1200"><meta property="og:image:height" content="630">
  <meta name="twitter:card" content="summary_large_image"><meta name="twitter:image" content="https://passioncode.ai/assets/passioncode-social-card.png">
  <link rel="icon" type="image/svg+xml" href="/assets/passioncode-mark.svg">
  <link rel="icon" type="image/png" sizes="64x64" href="/assets/favicon-64.png">
  <link rel="apple-touch-icon" sizes="256x256" href="/assets/icon-256.png">
  <link rel="stylesheet" href="/design-system/tokens.css"><link rel="stylesheet" href="/styles.css">
  <script type="module" src="/assets/site.js"></script>
  <script type="application/ld+json">{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "From one agent to an AI-native organization",
  "description": "What keeps an agent working, the four principles PassionCode.ai builds by, and how one agent grows into a team and an organization, each stage marked available now or direction.",
  "url": "https://passioncode.ai/vision/",
  "dateModified": "2026-10-10",
  "inLanguage": "en",
  "author": { "@type": "Person", "@id": "https://passioncode.ai/#sergey-sheleg", "name": "Sergey Sheleg", "url": "https://x.com/sshlg93" },
  "publisher": { "@type": "Organization", "name": "PassionCode.ai", "url": "https://passioncode.ai/" }
}</script>
  <script type="application/ld+json">{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    { "@type": "Question", "name": "Does PassionCode.ai replace Claude Code or Codex?", "acceptedAnswer": { "@type": "Answer", "text": "No. It works on top of them. Your coding agent keeps doing the work; PassionCode.ai gives it a home, accounts, its state, memory and evidence, and lets the next agent join the same project." } }
  ]
}</script>
</head>
<body class="story-site"><a class="skip-link" href="#main">Skip to content</a>
<header class="site-header">
 <a class="brand" href="/" aria-label="PassionCode.ai home"><img src="/assets/passioncode-mark.svg" width="40" height="40" alt=""><span>PassionCode<span class="brand-dot">.ai</span></span></a>
 <nav aria-label="Primary navigation"><a href="/vision/">Vision</a><a href="/start/">For you</a><a href="/business/">For organizations</a><a href="/#products">The tools</a><a href="/#about">About</a></nav>
 <div class="header-actions"><details class="lang-switch lang-menu"><summary aria-label="Language: English"><span lang="en">English</span></summary><ul><li><a href="/ru/vision/" hreflang="ru" lang="ru">Русский</a></li><li><a href="/de/vision/" hreflang="de" lang="de">Deutsch</a></li><li><a href="/fr/vision/" hreflang="fr" lang="fr">Français</a></li><li><a href="/pl/vision/" hreflang="pl" lang="pl">Polski</a></li><li><a href="/ko/vision/" hreflang="ko" lang="ko">한국어</a></li><li><a href="/es/vision/" hreflang="es" lang="es">Español</a></li><li><a href="/pt-br/vision/" hreflang="pt-BR" lang="pt-BR">Português (Brasil)</a></li><li><a href="/zh-hans/vision/" hreflang="zh-Hans" lang="zh-Hans">简体中文</a></li><li><a href="/ja/vision/" hreflang="ja" lang="ja">日本語</a></li></ul></details><a class="header-link header-download" href="/start/#setup">Set up <span aria-hidden="true">↓</span></a></div>
</header>
<main id="main">
<section class="hero page-hero" aria-labelledby="hero-title">
 <div class="hero-copy">
  <p class="eyebrow"><span></span> The vision · as of October 2026</p>
  <h1 id="hero-title">From one agent to an <em>AI-native organization</em></h1>
  <p class="hero-body">Agents are easy to start and hard to keep. We are building what holds them together, so each new agent makes the others stronger</p>
  <p class="hero-caption"><span class="status-dot" aria-hidden="true"></span> Local first, open source, vendor-neutral <span>On top of Claude Code, Codex and what comes next</span></p>
 </div>
 <nav class="page-toc" aria-label="On this page"><a href="#harness"><span>01</span> What holds an agent</a><a href="#beliefs"><span>02</span> What we believe</a><a href="#path"><span>03</span> The path</a></nav>
</section>

<section class="section" id="harness" aria-labelledby="harness-title">
 <span id="problem" class="legacy-anchor" aria-hidden="true"></span>
 <div class="section-heading story-heading"><p class="section-number">01 / WHAT HOLDS AN AGENT</p><h2 id="harness-title">The model is not the problem<br>What holds it is</h2><p>Most organizations already experiment with agents, yet <a href="https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai">no more than 10% scale them</a> in any one function. An agent built alone forgets between sessions and loses track of its accounts. It leaves no record of what it did, and the next agent knows nothing about it. We call what holds it together <strong>a harness</strong>: everything around a model that keeps an agent working over time. The labs use the word too: <a href="https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents">Anthropic</a>, <a href="https://openai.com/index/harness-engineering/">OpenAI</a>.</p></div>
 <ol class="work-cycle">
  <li class="reveal"><span class="cycle-number">01</span><h3>A home</h3><p>Each project has one place for its purpose, board, decisions and releases, shared by every agent that works on it. That is Fabric.</p></li>
  <li class="reveal"><span class="cycle-number">02</span><h3>Accounts</h3><p>Each agent runs on the account it should, with its limits in view. That is Fabric Switchboard.</p></li>
  <li class="reveal"><span class="cycle-number">03</span><h3>State and control</h3><p>Every agent service, what it is doing and what it spends, in one window that people and agents can drive. That is Fabric Dashboards.</p></li>
  <li class="reveal"><span class="cycle-number">04</span><h3>Memory and evidence</h3><p>What changed, what was decided and what needs attention, with the proof beside it. That is Project Observatory.</p></li>
 </ol>
</section>

<section class="section vision" id="beliefs" aria-labelledby="beliefs-title">
 <div class="vision-copy">
  <p class="section-number">02 / WHAT WE BELIEVE</p>
  <h2 id="beliefs-title">Four principles<br><em>we build by</em></h2>
  <ul class="vision-principles">
   <li><strong>Projects are the axis</strong><span>Every agent works for a project, and the project keeps the purpose, decisions and releases, so the work outlives the session that did it.</span></li>
   <li><strong>The work improves itself</strong><span>A run leaves evidence you can open, and Observatory keeps it today. Retrospectives that turn it into lessons the next agent learns from are the direction.</span></li>
   <li><strong>Any agent, on your machines</strong><span>Vendor-neutral, local first and open source under the GNU AGPL-3.0, on top of Claude Code, Codex and what comes next.</span></li>
   <li><strong>Analytics, never surveillance</strong><span>Analytics are about agents and the outcomes of processes. Nothing watches people in secret.</span></li>
  </ul>
  <div class="pipeline-note" id="pipeline">
   <p class="section-note">For the changes your agents make, we recommend <strong>task-pipeline</strong>, a separate open-source skill from the <a href="https://github.com/ssheleg/sshlg-skills">sshlg-skills</a> collection: it carries each change from the brief to the acceptance and does not move on until each gate passes.</p>
   <pre class="copyable"><code>npx sshlg-skills install</code></pre>
   <p class="section-note"><a href="https://github.com/ssheleg/task-pipeline">task-pipeline on GitHub</a> · it is not part of PassionCode.ai and needs nothing from it</p>
  </div>
 </div>
</section>

<section class="section growth-path" id="path" aria-labelledby="path-title">
 <span id="today" class="legacy-anchor" aria-hidden="true"></span><span id="trust" class="legacy-anchor" aria-hidden="true"></span>
 <div class="section-heading story-heading"><p class="section-number">03 / THE PATH</p><h2 id="path-title">Six stages<br>Each one useful on its own</h2><p>The same setup grows from one person to a whole organization. Each stage says whether it works today or is where we are building.</p></div>
 <ol class="work-cycle path-cycle">
  <li class="reveal"><span class="cycle-number">01</span><p class="availability">AVAILABLE NOW</p><h3>One agent</h3><p>Your coding agent builds an agent for one job, with a contract, a dashboard and tests.</p><a href="/#how">How it works, step 3</a></li>
  <li class="reveal"><span class="cycle-number">02</span><p class="availability">AVAILABLE NOW, IN PART</p><h3>Two agents that talk</h3><p>Agents connected to Fabric share one project’s board, memory and hand-offs, so one picks up where the other stopped. Fabric is an early preview.</p><a href="/#how">How it works, step 5</a></li>
  <li class="reveal"><span class="cycle-number">03</span><p class="availability">DIRECTION</p><h3>A chain</h3><p>Agents line up into one process: one prepares, the next checks, a person approves.</p></li>
  <li class="reveal"><span class="cycle-number">04</span><p class="availability">AVAILABLE NOW, IN PART</p><h3>Agents kept in good order</h3><p>Dashboards shows each agent’s state and spend, the tools update themselves, and Observatory keeps what changed. Agents watching over each other is the direction.</p></li>
  <li class="reveal"><span class="cycle-number">05</span><p class="availability">DIRECTION</p><h3>A team</h3><p>People join the same loops: each gets a workplace, the agents of their role and what they may do.</p></li>
  <li class="reveal"><span class="cycle-number">06</span><p class="availability">DIRECTION</p><h3>An organization</h3><p>Agents reach every workplace. People act as the experts who verify agents’ work and build agents of their own, and those agents spread through the network.</p><a href="/#how">How it works, step 6</a></li>
 </ol>
</section>

<section class="section faq" id="faq" aria-labelledby="faq-title">
 <div class="section-heading"><p class="section-number">QUESTIONS</p><h2 id="faq-title">Before you start</h2></div>
 <details><summary>Does PassionCode.ai replace Claude Code or Codex?</summary><p>No. It works on top of them. Your coding agent keeps doing the work; PassionCode.ai gives it a home, accounts, its state, memory and evidence, and lets the next agent join the same project.</p></details>
</section>

<section class="closing" aria-labelledby="closing-title"><span id="organizations" class="legacy-anchor" aria-hidden="true"></span><img src="/assets/passioncode-mark.svg" width="72" height="72" alt=""><p class="section-number">START WITH ONE AGENT</p><h2 id="closing-title">Your agents start<br>with one command</h2><p>Set up the tools with one command and build the first agent, or take a whole organization along: PassionCode for Enterprise is in development and offered on request.</p><div class="hero-actions closing-actions"><a class="button button-primary" href="/start/">For you, free <span aria-hidden="true">→</span></a><a class="button button-secondary" href="/business/">For your organization <span aria-hidden="true">↗</span></a></div></section>
</main>
<footer class="story-footer">
 <div><a class="brand footer-brand" href="/"><img src="/assets/passioncode-mark.svg" width="32" height="32" alt=""><span>PassionCode<span class="brand-dot">.ai</span></span></a><p>From vibe coding to passion coding</p></div>
 <nav aria-label="Footer navigation"><a href="/start/">Get started</a><a href="/vision/">Vision</a><a href="/business/">For organizations</a><a href="/switchboard/">Switchboard</a><a href="/observatory/">Observatory</a><a href="/inbox/">Inbox</a><a href="/dashboards/">Dashboards</a><a href="/fabric/">Fabric</a><a href="/#source">GitHub &amp; source</a><a href="/#about">About</a><a href="/#investors">Investors</a><a href="/#contributors">Contributors</a><a href="/#press">Press</a><a href="/design-system/">Design system</a><a href="/privacy/">Privacy</a><a href="mailto:commercial@passioncode.ai">commercial@passioncode.ai</a><a href="https://x.com/sshlg93">X <span aria-hidden="true">↗</span></a></nav>
</footer>
</body></html>