---
type: "post"
stable_id: "post:organization-agent-runtime-qm-vercel-eve"
slug: "organization-agent-runtime-qm-vercel-eve"
title: "An Organization Agent Is A Scoped Runtime, Not One Slack Bot"
description: "QM and Vercel show how company agents separate identity, memory, permissions, durable workspaces, specialist roles, and approval-gated actions."
retrieval_nugget: "Company-wide agents need scoped identity, memory, credentials, schedules, durable execution, and explicit approval policy. QM supplies the runtime pattern; Vercel's @v and Eve show the organizational workflow layered above it."
published_at: "2026-08-05"
updated_at: "2026-08-05"
record_date: "2026-08-05"
date_kind: "discovered_at"
topics: ["agents","enterprise-ai","agent-runtime","operations"]
entities: ["QM","Vercel","Eve"]
source_format: "multi-source"
editorial_timing: {"lane":"regular_hourly_analysis","scheduled_at":"2026-08-07T15:00:00+03:00","real_news_delta":"organization-agent runtime pattern across an open repository and a production team"}
visual_decision: {"status":"included","reason":"the scope hierarchy and shared-runtime boundary are materially clearer as a diagram","reviewed_by":"codex"}
schema_version: "newruntime-agent-readable-v0.2"
status: "published"
source_urls: ["https://github.com/yc-software/qm","https://www.linkedin.com/posts/rauchg_we-built-an-agent-that-powers-our-companys-activity-7490034361271144449-ctEp","https://vercel.com/kb/guide/marketing-team-eve"]
visuals: [{"role":"hero","src":"/images/drip/organization-agent-runtime-qm-vercel-eve/organization-agent-runtime-qm-vercel-eve.webp","alt":"A New Runtime whiteboard architecture showing one organization-agent core branching into project, team, and company scopes with durable state and approval gates.","caption":"New Runtime synthesis from QM, Vercel @v, and the Eve team guide."}]
routes: {"html":"https://newruntime.com/posts/organization-agent-runtime-qm-vercel-eve/","markdown":"https://newruntime.com/posts/organization-agent-runtime-qm-vercel-eve.md","json":"https://newruntime.com/posts/organization-agent-runtime-qm-vercel-eve.json"}
---

# An Organization Agent Is A Scoped Runtime, Not One Slack Bot

## Retrieval answer

Company-wide agents need scoped identity, memory, credentials, schedules, durable execution, and explicit approval policy. QM supplies the runtime pattern; Vercel's @v and Eve show the organizational workflow layered above it.

QM and Vercel point at the same organizational boundary from different directions: a company agent is a scoped runtime, not one bot sharing one transcript. QM gives every person and room its own memory, files, keychain view, permissions, schedules, web apps, and durable sandbox. The shared core owns identity, policy, storage, and scheduling while agent loops and interfaces remain replaceable.

Vercel shows the operating model around that substrate. Its internal @v works across finance, communications, documentation, marketing, engineering, and analytics. The Eve guide turns the pattern into an executable team: a lead agent routes work to long-form, social, email, and SEO specialists while Notion, Typefully, and Resend become task surfaces rather than the system of record. Irreversible actions still require approval.

The architectural test is therefore about boundaries, not personality. Who owns a scope? Where do durable state and secrets live? Which actions are denied or approval-gated before execution? Can the harness be replaced without migrating the organization's memory? A shared chat UI cannot answer those questions.

For New Runtime, this is a concrete post-app pattern. Intent enters a governed runtime, the runtime assembles the right specialist roles and surfaces, and receipts preserve who asked for what under which authority.