Product

Team charters for humans and computers.

One shape, every team. Linked. Versioned. Drafted from your Slack when you want it, written by hand when you don’t — and compiled into operating instructions for the agents you put on the work.

01

One shape, every team

Six sections, in the same order, on every charter. So a new manager can read across the org in an afternoon — not a quarter.

02

An org as a graph

Roles in one charter link to roles in another. Subteams nest under superteams. Mentions become real edges — not lost prose.

03

Versioned, not lost

Every save is a version. Subscribe to a charter and get notified when it changes. See who edited what.

Anatomy

What’s in a charter.

One page. Six sections. The same shape every time, so you can read across teams. We use DICE for decision rights, because it's better, clearer.

01Team PurposeOne sentence. The reason the team exists, in plain language.
02Focus AreasThe things this team prioritizes above all else. Not aspirations — territories.
03MeasuresHow we know it’s working. Lagging and leading.
04Decision RightsPer decision: who Decides, is Informed, Consulted, Executes (DICE).
05RolesEach role on the team gets its own focus statement and named person — or agent.
06GuidelinesWorking agreements. Short. Editable.
Agents

A role doesn’t care if its filler is carbon or silicon.

Connect an agent to a charter and it fills a role like anyone else — reading the charter as its operating instructions. The charter shapes the agent. Never the other way around.

Design Standards · roles
Design QAReviews shipped work against the standard
Priya Shah
Release notesWrites and ships the changelog every release
Open
Token stewardOwns the token set and its versioning
Leo Marchetti
Every role has a focus, interfaces, and authority. This one’s open.
Integrations

ccccharter writes itself from the tools you already use.

Read the channels, docs, and tickets a team already lives in. Draft a starting charter in minutes — and keep it honest as the work shifts.

SlackLive today

Read channel history. Draft charters. Detect drift between what the team says it does and what it's actually doing.

Google DriveComing soon

Pull docs and folder activity into reviews. Spot when work has shifted to a strategy a charter doesn't mention yet.

LinearComing soon

Cross-reference projects and issues with team responsibilities. See where the actual work lives.

How it works · Slack

Connect once at the org level. Every charter can opt in to specific channels.

halyard-labs.slack.com
Add to Slack
Read-only OAuth on the channels you authorize.
One click installs ccccharter into your Slack workspace.
Charter reviews

Your Slack tells the truth. Your charter should too.

Every other week, ccccharter reads the channel a charter is connected to and flags the gap between what the team says it does and what it's actually doing. Catches drift before it becomes confusion.

Charter Sandbox · 5 charters
  • Design StandardsActive0 roles
  • Campaign NTONeeds Review3 roles
  • Edge Account TeamActive4 roles
  • Omega Account TeamActive4 roles
  • Service SwarmActive3 roles
The work shifts. The charter doesn’t. Drift starts quietly.
Decisions

Decisions, logged where the authority lives.

Raise an issue, decide it, and the record lands against the decision right that authorized it. Latency, authority fit, throughput — measured, not vibed. A radar drafts candidates from your channels; editors confirm.

Decision latency2.1dmedian, raised → decided
Within stated rights92%of decisions this quarter
This month14decided, 3 still open
Jul 11
Ship the changelog weekly; retire the monthly digest.Dunder “Publishing cadence
Jul 08
New token proposals get 48h of consultation before merge.Cunder “Design standards
Do reader letters belong in print, on the site, or both?open 3d
The network

See the whole org. Find the overlap. Know your neighbors.

Because charters share one shape and @mentions are real edges, the org is a live graph. Zoom out to the shape of the company, filter to every team touching one kind of work, or read one team's immediate network — who it needs, and who needs it.

halyard labsProductOperationsGrowthOnboarding rewritePeople analyticsFinance opsBrand systems
Every team, every reporting line, every dependency — the shape of the whole company on one screen.
Editor

Built like a document, not a form.

Inline editing. Keyboard-first. Share publicly or scope to your domain. Subscribers get notified on change.

Team purpose
We turn HR data into decisions about hiring, leveling, and team design.
Focus areas
Workforce planning · Team-design diagnostics · Compensation analytics
Decision rights
DecideAnnual leveling framework
Roles
Lead · Analyst · Researcher
Versioning

Every save is a version.

Line-level diffs, named authors, restorable history. See exactly what changed in your mission, focus areas, decision rights, and roles — and roll back to any prior version.

Select a version to see what changed →
Type, save, keep going. Every save is captured, named, and attributed.

“Replaced four overlapping wikis. Now everyone knows who decides what.”

— COO, 120-person agency

Get started

Stand up your org's charters this week.