{
  "trust_level": "claimed",
  "official_brand_source": false,
  "verification_method": null,
  "verified_domain": null,
  "verified_at": null,
  "verification_last_checked_at": null,
  "verification_expires_at": null,
  "status": "active",
  "customer_handle": "monday-com-4ca31c9f",
  "certification_status": "not_certified",
  "registry_certified": false,
  "certification": null,
  "brand_name": "monday.com",
  "response_scope": "full_tree",
  "integrity": {
    "version": 2,
    "publication_id": "1de3ef44a92785600a202725729ebe4e972a280602a7059d219cd2b50d4dcff5",
    "revision_id": "81ff9c4b-cdd3-45a0-8d66-f48af61fea8b",
    "manifest_sha256": "fb291b0bce2943d02f6ba0f37fd5e0a1016e0387cc2d910335142531a292843c",
    "manifest_signature": "Mi9dowE+Fj/RDuDqkOHiphczlu+Q1GiEb5s5BLPtbfm7XouVbBjQZ4zvntFkUvQcSY4OnmD3JUIVv7M+tQXQDA==",
    "manifest_signature_kid": "v1"
  },
  "verified": null,
  "schema": "bcp-readable-package-v1",
  "integrity_scope": "publication_manifest",
  "representation": "Derived readable representation; verify signatures against the canonical source files.",
  "canonical_registry_url": "https://registry.brandcontextprotocol.dev/brands/monday-com-4ca31c9f",
  "html_url": "https://registry.encodedbrands.ai/brands/monday-com-4ca31c9f",
  "files": [
    {
      "path": "/.well-known/brand/values.md",
      "content": "---\nbcp_version: \"0.8\"\nfile_type: values\nparent: https://registry.brandcontextprotocol.dev/monday-com-4ca31c9f/.well-known/brand.md\nlast_updated: 2026-08-21\n---\n\n# Values\n\nThese values are decision rules. They describe choices monday.com makes when the easier path would be something else — shipping faster, moving quietly, or letting an agent act without a check.\n\n---\n\n## 1. Radical Transparency\n\n**tier:** core\n\nmonday.com makes real-time business information visible to every employee, not just leadership. The decision this produces: internal metrics are open by default, not restricted by default. When a company goes public and the argument for restricting information grows louder, this value holds anyway.\n\nCo-founder and CTO Eran Zinman has stated publicly: \"I don't know of another tool has this value built into its DNA like monday.com.\" (Source: The Digital Enterprise interview, retrieved 2026-08-21.)\n\nAn independent profile of Chief Product and Technology Officer Daniel Lereya describes monday.com's culture of radical transparency as giving \"every employee access to real-time metrics, fostering accountability and alignment across the organization.\" The same profile notes the company explicitly chose to maintain this practice after becoming a public company — the moment when most organizations move in the opposite direction. (Source: Lenny's Newsletter, retrieved 2026-08-21.)\n\n**Manifestation in practice:** Every employee has access to real-time business metrics. Restricting that access requires active justification, not a default setting.\n\n**Demonstrated tradeoff:** Radical transparency creates friction with standard public-company information-control practices. monday.com accepts that friction rather than narrowing visibility.\n\n---\n\n## 2. Impact Over Output\n\n**tier:** core\n\nmonday.com's product development philosophy prioritizes solving real problems that drive business growth over shipping features. The question is not \"did we ship?\" but \"did it move something that matters?\"\n\nThe named principle — \"impact over output\" — is cited as a defining characteristic of monday.com's product culture by independent reporting on the company's path to $1B ARR, and is confirmed as owner-endorsed. (Source: Lenny's Newsletter profile of Daniel Lereya, retrieved 2026-08-21; owner confirmation on file.)\n\n**Manifestation in practice:** Product decisions are evaluated by business impact, not feature count or release cadence. A team that ships nothing but eliminates a category of customer friction has succeeded. A team that ships frequently but moves no meaningful metric has not.\n\n**Demonstrated tradeoff:** Prioritizing impact over output means accepting slower or fewer releases when there is no clear answer to \"what real problem does this solve?\"\n\n---\n\n## 3. Human Control Over Autonomous Action\n\n**tier:** core\n\nmonday.com builds AI agents that act alongside people, not agents that act instead of people. The platform design reflects a structural commitment: consequential actions require a human to confirm before they execute.\n\nThis is not a feature toggle. It is the operating principle that shapes how agents ship:\n\n- High-impact actions require human review before an agent may perform them. (Owner-confirmed; boundaries.md.)\n- Write tools (send, create, edit, delete) ship inactive in monday agents and require explicit human activation. (Owner-confirmed; boundaries.md.)\n- Each agent receives only the permissions it needs for its specific job, scoped by least privilege and reviewed regularly. (Owner-confirmed; boundaries.md.)\n\n**Manifestation in practice:** A monday.com agent that could send an email, delete a record, or approve a budget does not do so until a human has reviewed and activated that capability. The default state of an agent is read and surface, not act and send.\n\n**Demonstrated tradeoff:** This constraint limits autonomous throughput. An agent that must pause for human confirmation is slower than one that acts freely. monday.com accepts that cost because the alternative — agents acting on consequential tasks without review — is inconsistent with how the platform defines human-AI collaboration.\n\n---\n\n## Agent resolution order\n\nWhen values conflict in a judgment call, prioritize:\n\n1. Human Control Over Autonomous Action — agent behavior that bypasses human review is not a faster version of the product; it is a different product.\n2. Impact Over Output — a decision that ships a feature at the cost of real customer impact is the wrong decision.\n3. Radical Transparency — when in doubt, make information visible rather than restricted.\n\n**Note:** This order is inferred from public evidence and the structural weight given to human-control commitments in owner-confirmed boundary rules. The owner should confirm whether this priority sequence reflects internal decision-making practice.\n\n---\n\n## Owner confirmation needed\n\n- **Transparency — operational scope:** Does radical transparency apply only internally (employees), or does it extend to how monday.com communicates with customers (e.g., pricing, roadmap, incidents)?\n- **Impact Over Output — measurement:** How does monday.com define and measure \"impact\" when evaluating a product decision? Is there a named internal framework?\n- **Priority order:** Owner should confirm or revise the agent resolution order above before it is treated as binding brand law.\n\n## Evidence record\n\nThe following attributable source language is preserved because it materially constrains this profile.\n\n### Owner-confirmed evidence\n\n> monday.com's product development philosophy prioritizes impact over shipping features, choosing to solve real problems that drive business growth.\n\nSource: Public source\n",
      "signature": "19bBAG1879XNTV8/wxo1eqmIzgjFjU/6m6Atc6kea1EbnB8lpW3PwOwR/hnDtdVojGvyTJlhn6SmXZk09tYtBw==",
      "sha256": "3df77c7700ca5af8f0f90278262320f1b4bbb74c7fe8b398ea0d828c11a02c58",
      "kid": "v1",
      "content_type": "text/markdown; charset=utf-8",
      "html_url": "https://registry.encodedbrands.ai/brands/monday-com-4ca31c9f/files/values",
      "json_url": "https://registry.encodedbrands.ai/brands/monday-com-4ca31c9f/files/values/data.json",
      "source_url": "https://registry.encodedbrands.ai/brands/monday-com-4ca31c9f/source/values.md",
      "canonical_source_url": "https://registry.brandcontextprotocol.dev/monday-com-4ca31c9f/.well-known/brand/values.md"
    }
  ]
}