npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@daihum/team

v0.1.2

Published

DAIHUM seat-neutral team domain: governed groups of agent|person|service principals with roles, members, threads, session-links, events, and the runner/store ports that pair a team role with the agent infra. Domain + ports; orchestration/persistence impls

Downloads

253

Readme

@daihum/team

The seat-neutral team domain: governed groups of Principals (agent | person | service | …) with roles, members, an inbox thread, links to the sessions their roles run, and an event log — plus the ports that pair a team role with the agent infra.

import { createInMemoryTeamStoreV0, createTeamServiceV0 } from "@daihum/team";

const team = createTeamServiceV0({
  store: createInMemoryTeamStoreV0(),
  now: () => new Date().toISOString(),
  newId: (p) => `${p}_${crypto.randomUUID()}`,
  runner,                          // optional: the agent-infra pairing seam
});

const { value } = await team.createTeam({ workspaceId: "w1", name: "Research" });
await team.roleUpsert({ teamId: value.team.teamId, roleId: "lead", title: "Lead" });
await team.memberAdd({ teamId: value.team.teamId, principalKind: "agent", principalId: "ada", roleIds: ["lead"] });

// pairing: activate a role as a running session (runner = where @daihum/agent-loop plugs in)
await team.activateRole({ teamId: value.team.teamId, roleId: "lead", goal: "draft the brief", ownerPrincipalId: "sys" });

Boundaries

  • Domain + ports only. Orchestration (the TeamRunnerPortV0 that activates a role — where @daihum/agent-loop plugs in), durable persistence (TeamStorePortV0), and governance impls stay in products (carrel system-jobs/approval, ontal control-room). Mirrors @daihum/approval-resume.
  • Identity is the canonical Principal from @daihum/personaprincipalKind is PrincipalKindV0. A team member, a chat participant, a persona, an approval principal, and an agent run's owner are all one Principal.
  • Records carry NO frozen schema literal. carrel (carrel.system.team.*.v0) and ontal (ontal.team.*.v0) attach their own wire schema in their adapter (pending the canonicalization decision); the core types are neutral structural shapes (the union/superset of both).
  • Bounded, governed multi-agent — not a world-scale society. A team is the product-regime grouping (roles, governance, human-in-loop). The world-sim (emergent, ungoverned) is a separate substrate; team's seat-neutral roles/ principals are reusable there, but team is not that engine.