{
  "generated": "2026-10-26",
  "count": 46,
  "items": [
    {
      "slug": "12fc",
      "url": "https://manifesto.md/12fc/",
      "badge": "https://manifesto.md/badge/12fc.json",
      "name": "12-Factor AI-enabled CLI",
      "short": "12fc",
      "kind": "specification",
      "line": "Twelve testable factors for a command-line tool whose operator may be a human or an AI agent, from machine-readable capabilities to meaningful exit codes, with a conformance gate.",
      "canonical": "https://github.com/hop-top/spec-12fc/blob/main/specs/v0.1/spec.md",
      "repo": "https://github.com/hop-top/spec-12fc",
      "version": "0.1",
      "status_of_text": "draft",
      "maintainer": "hop.top, published by Idea Crafters",
      "publisher": "project",
      "first_published": "2026-04",
      "listing": "claimed",
      "claimed_at": "2026-10-25",
      "claimed_by": "maintainer",
      "tenets": [
        "Capability introspection. The CLI exposes its capabilities in a machine-readable format.",
        "Intent clarity. Commands express intent, not syntax.",
        "Structured I/O. Machine-readable output with a stable schema, strict channel discipline.",
        "Corrective error model. Errors carry a stable code, the failing input, a transience class and a suggested fix.",
        "Explicit contracts. Idempotency, side effects, retry semantics, schema versioning and partial failure are declared.",
        "Previewability. Every mutating operation can be previewed; nothing blocks on a prompt without a TTY.",
        "Idempotency by default, or declared otherwise with a safe retry strategy.",
        "State transparency. All implicit state is inspectable.",
        "Contextual guidance. Help that answers the situation, not the flag list.",
        "Delegation safety. Scoped permissions, confirmation policies, sandboxing, rate limits, policy enforcement.",
        "Exit code semantics. Zero means success, never a swallowed error; failure classes are distinguishable.",
        "Evolution guarantees. Changes announce themselves; renaming an error code is a breaking change."
      ],
      "tenets_label": "The twelve factors",
      "related": [
        "aop",
        "pact",
        "12-factor-app",
        "12-factor-agents"
      ],
      "family": "ideacrafters",
      "order": 10
    },
    {
      "slug": "pact",
      "url": "https://manifesto.md/pact/",
      "badge": "https://manifesto.md/badge/pact.json",
      "name": "Purpose-bound Access Control and Trust",
      "short": "PACT",
      "kind": "specification",
      "line": "How an AI agent proves who it acts for, with what declared purpose and evidence, to a gateway that already authenticates and authorizes; a PACT pass never grants access and a native denial always wins.",
      "canonical": "https://github.com/hop-top/poly-pact/tree/next/spec/v1.0",
      "repo": "https://github.com/hop-top/poly-pact",
      "version": "1.0.0-alpha.0",
      "status_of_text": "draft",
      "license": "MIT",
      "maintainer": "hop.top, published by Idea Crafters; brand home context.help",
      "publisher": "project",
      "first_published": "2026-10",
      "listing": "claimed",
      "claimed_at": "2026-10-25",
      "claimed_by": "maintainer",
      "tenets": [
        "Native authority is preserved. Admission and reputation cannot override native authentication or authorization.",
        "Required fields have required provenance. Security-relevant claims need a trusted source with authority over them.",
        "The presenter is bound to the subject. No reuse of another agent's identity or evidence without a recognized delegation.",
        "A result is request-specific. Profile, intent, principal, gateway, requirement version and operation are bound together.",
        "No positive result from uncertainty. Missing evidence, stale state or an unavailable dependency never yields admissible.",
        "Learning stays within policy. Autonomous changes cannot remove immutable requirements or expand native authority.",
        "Reputation follows evidence; incidents survive decay.",
        "Every completed authenticated evaluation has a receipt."
      ],
      "tenets_label": "Behavioural invariants",
      "related": [
        "aop",
        "12fc"
      ],
      "family": "ideacrafters",
      "order": 20,
      "note": "The text is edited in the poly-pact repository; a read-only mirror named spec-pact is planned and this link moves there when it exists."
    },
    {
      "slug": "aop",
      "url": "https://manifesto.md/aop/",
      "badge": "https://manifesto.md/badge/aop.json",
      "name": "Agent Operation Protocol",
      "short": "AOP",
      "kind": "specification",
      "line": "Six laws a system must enforce at its API boundary so that any actor, human or agent, can act on a shared operational graph without breaking it.",
      "canonical": "https://agentoperationprotocol.org/v0.6/",
      "repo": "https://github.com/AgentOperation/Protocol",
      "version": "0.6",
      "status_of_text": "draft",
      "license": "CC BY 4.0 (text), MIT (checker)",
      "maintainer": "AgentOperation, published by Idea Crafters",
      "publisher": "project",
      "first_published": "2026-03-12",
      "listing": "claimed",
      "claimed_at": "2026-10-25",
      "claimed_by": "maintainer",
      "tenets": [
        "Read before write. A mutation of an entity the actor has not read in the current operation context is rejected.",
        "Validate schema before mutation. Writes that do not match the declared schema are rejected.",
        "Preserve graph integrity. No dangling relations, no missing targets, no forbidden cycles; deletes follow the declared rule.",
        "Emit an event for every mutation, before success is returned. No silent writes.",
        "Check capabilities at action time. A revoked grant takes effect on the next request.",
        "Respect lifecycle gates. No undeclared transitions; each declared one needs its capability.",
        "Rejections are typed and structured, four fields, never silent; governance rejections are audited."
      ],
      "tenets_label": "The six laws",
      "related": [
        "pact",
        "12fc",
        "owsf"
      ],
      "family": "ideacrafters",
      "order": 30
    },
    {
      "slug": "owsf",
      "url": "https://manifesto.md/owsf/",
      "badge": "https://manifesto.md/badge/owsf.json",
      "name": "Open Workspace Schema Framework",
      "short": "OWSF",
      "kind": "specification",
      "line": "A portable, append-only workspace artifact model for execution continuity, replay, handoff and forking across tools; structure and invariants, not orchestration or transport.",
      "canonical": "https://github.com/hop-top/spec-owsf/blob/main/specs/v1.0/core.md",
      "repo": "https://github.com/hop-top/spec-owsf",
      "version": "1.0",
      "status_of_text": "draft",
      "maintainer": "hop.top, published by Idea Crafters",
      "publisher": "project",
      "first_published": "2026",
      "listing": "claimed",
      "claimed_at": "2026-10-25",
      "claimed_by": "maintainer",
      "tenets": [
        "A workspace is an append-only artifact; history is never rewritten.",
        "Continuity, replay, handoff and forking are properties of the artifact, not of the tool that wrote it.",
        "Invariants are normative; runtime orchestration and transport are out of scope.",
        "Integrations declare how they reference a workspace, not how they run it."
      ],
      "tenets_label": "What it fixes",
      "related": [
        "crtx",
        "vstar",
        "aop"
      ],
      "family": "ideacrafters",
      "order": 40
    },
    {
      "slug": "crtx",
      "url": "https://manifesto.md/crtx/",
      "badge": "https://manifesto.md/badge/crtx.json",
      "name": "crtx",
      "kind": "specification",
      "line": "The wire and storage shape for AI agent conversations, sessions, turns, content parts, tool calls and the envelope that carries them, so runtime tools agree on one record.",
      "canonical": "https://github.com/hop-top/spec-crtx/blob/main/specs/v0.1/envelope.md",
      "repo": "https://github.com/hop-top/spec-crtx",
      "version": "0.1",
      "status_of_text": "draft",
      "maintainer": "hop.top, published by Idea Crafters",
      "publisher": "project",
      "first_published": "2026-05",
      "listing": "claimed",
      "claimed_at": "2026-10-25",
      "claimed_by": "maintainer",
      "tenets": [
        "One envelope for a conversation, versioned by a field, so implementations speak several versions side by side.",
        "Sessions, turns, content parts and tool calls have one shape across tools.",
        "A bus event taxonomy names what happened to a conversation.",
        "Pin to a spec version; the main branch is not a contract."
      ],
      "tenets_label": "What it fixes",
      "related": [
        "owsf",
        "vstar"
      ],
      "family": "ideacrafters",
      "order": 50
    },
    {
      "slug": "vstar",
      "url": "https://manifesto.md/vstar/",
      "badge": "https://manifesto.md/badge/vstar.json",
      "name": "V*",
      "short": "vstar",
      "kind": "specification",
      "line": "Agentic-system state, worlds, missions, players, turns, observations and decisions, represented as iCalendar and vCard components so agent work rides existing calendar and contact tooling instead of a bespoke protocol.",
      "canonical": "https://github.com/hop-top/poly-vstar/tree/main/spec/v1.0",
      "repo": "https://github.com/hop-top/poly-vstar",
      "version": "1.0.0-alpha.1",
      "status_of_text": "draft",
      "maintainer": "hop.top, published by Idea Crafters",
      "publisher": "project",
      "first_published": "2026-09",
      "listing": "claimed",
      "claimed_at": "2026-10-25",
      "claimed_by": "maintainer",
      "tenets": [
        "Time, identity and sequence semantics already exist in RFC 5545 and RFC 6350; agent state maps onto them instead of inventing a protocol.",
        "Each state component has one canonical mapping and a canonicalization rule, so two implementations produce the same bytes.",
        "Versions are independent directories; breaking changes open a new one."
      ],
      "tenets_label": "What it fixes",
      "related": [
        "owsf",
        "crtx"
      ],
      "family": "ideacrafters",
      "order": 60,
      "note": "Two public copies exist today, an older v0.1 in spec-vstar and this v1.0 line in poly-vstar; the link points at the newer text until the two are reconciled."
    },
    {
      "slug": "clear",
      "url": "https://manifesto.md/clear/",
      "badge": "https://manifesto.md/badge/clear.json",
      "name": "CLEAR",
      "kind": "specification",
      "line": "Contractual Labor Exchange of Agents and Resources, an economic coordination layer where agents contract, delegate work and settle outcomes under deterministic rules.",
      "canonical": "https://manifesto.md/clear/",
      "version": "0.1",
      "status_of_text": "unpublished",
      "maintainer": "Idea Crafters",
      "publisher": "project",
      "first_published": "2026-03",
      "listing": "listed",
      "tenets": [
        "Deterministic settlement, binary outcomes, no proportional scoring.",
        "Escrow is locked at acceptance and released by rule, not by discretion.",
        "Reputation is a settlement statistic reconstructed from the ledger, not an opinion.",
        "Every contract state transition is declared; arbitration is a declared path, not an exception.",
        "Interoperability through a compatibility shim; providers remain swappable."
      ],
      "tenets_label": "Core principles",
      "related": [
        "pact",
        "aop",
        "owsf"
      ],
      "family": "ideacrafters",
      "order": 70
    },
    {
      "slug": "agile-manifesto",
      "url": "https://manifesto.md/agile-manifesto/",
      "badge": "https://manifesto.md/badge/agile-manifesto.json",
      "name": "Manifesto for Agile Software Development",
      "short": "Agile Manifesto",
      "kind": "manifesto",
      "line": "Four value pairs and twelve principles for developing software, written by seventeen practitioners in 2001; the document the word agile points at.",
      "canonical": "https://agilemanifesto.org/",
      "status_of_text": "historical",
      "maintainer": "The seventeen signatories, hosted at agilemanifesto.org",
      "publisher": "community",
      "first_published": "2001-02",
      "listing": "listed",
      "tenets": [
        "Individuals and interactions over processes and tools.",
        "Working software over comprehensive documentation.",
        "Customer collaboration over contract negotiation.",
        "Responding to change over following a plan."
      ],
      "tenets_label": "The four values",
      "related": [
        "12-factor-app"
      ],
      "order": 100
    },
    {
      "slug": "12-factor-app",
      "url": "https://manifesto.md/12-factor-app/",
      "badge": "https://manifesto.md/badge/12-factor-app.json",
      "name": "The Twelve-Factor App",
      "kind": "principles",
      "line": "Twelve factors for building software-as-a-service applications that are portable, declarative and ready to scale, written at Heroku from experience operating hundreds of thousands of apps.",
      "canonical": "https://12factor.net/",
      "repo": "https://github.com/heroku/12factor",
      "status_of_text": "stable",
      "maintainer": "Adam Wiggins, Heroku",
      "publisher": "company",
      "first_published": "2011",
      "listing": "listed",
      "tenets": [
        "Codebase. One codebase tracked in revision control, many deploys.",
        "Dependencies. Explicitly declare and isolate dependencies.",
        "Config. Store config in the environment.",
        "Backing services. Treat backing services as attached resources.",
        "Build, release, run. Strictly separate build and run stages.",
        "Processes. Execute the app as one or more stateless processes.",
        "Port binding. Export services via port binding.",
        "Concurrency. Scale out via the process model.",
        "Disposability. Maximize robustness with fast startup and graceful shutdown.",
        "Dev/prod parity. Keep development, staging and production as similar as possible.",
        "Logs. Treat logs as event streams.",
        "Admin processes. Run admin and management tasks as one-off processes."
      ],
      "tenets_label": "The twelve factors",
      "related": [
        "12fc",
        "12-factor-agents"
      ],
      "order": 110
    },
    {
      "slug": "12-factor-agents",
      "url": "https://manifesto.md/12-factor-agents/",
      "badge": "https://manifesto.md/badge/12-factor-agents.json",
      "name": "12-Factor Agents",
      "kind": "principles",
      "line": "Principles for building LLM-powered software reliable enough to put in front of production customers, modelled on the Twelve-Factor App and maintained in the open.",
      "canonical": "https://github.com/humanlayer/12-factor-agents",
      "repo": "https://github.com/humanlayer/12-factor-agents",
      "status_of_text": "stable",
      "maintainer": "Dex Horthy, HumanLayer",
      "publisher": "company",
      "first_published": "2025-04",
      "listing": "listed",
      "tenets": [
        "Natural language to tool calls.",
        "Own your prompts.",
        "Own your context window.",
        "Tools are just structured outputs.",
        "Unify execution state and business state.",
        "Launch, pause, resume with simple APIs.",
        "Contact humans with tool calls.",
        "Own your control flow.",
        "Compact errors into context window.",
        "Small, focused agents.",
        "Trigger from anywhere, meet users where they are.",
        "Make your agent a stateless reducer."
      ],
      "tenets_label": "Factors (titles as published)",
      "related": [
        "12-factor-app",
        "12fc"
      ],
      "order": 120
    },
    {
      "slug": "reactive-manifesto",
      "url": "https://manifesto.md/reactive-manifesto/",
      "badge": "https://manifesto.md/badge/reactive-manifesto.json",
      "name": "The Reactive Manifesto",
      "kind": "manifesto",
      "line": "Four traits of systems built to meet modern demands, responsive, resilient, elastic and message driven, published in 2013 and revised in 2014, with thousands of signatories.",
      "canonical": "https://www.reactivemanifesto.org/",
      "status_of_text": "stable",
      "maintainer": "Jonas Bonér and co-authors",
      "publisher": "community",
      "first_published": "2013",
      "listing": "listed",
      "tenets": [
        "Responsive. The system responds in a timely manner if at all possible.",
        "Resilient. The system stays responsive in the face of failure.",
        "Elastic. The system stays responsive under varying workload.",
        "Message driven. Asynchronous message passing establishes boundaries between components."
      ],
      "tenets_label": "The four traits",
      "related": [
        "12-factor-app"
      ],
      "order": 130
    },
    {
      "slug": "local-first",
      "url": "https://manifesto.md/local-first/",
      "badge": "https://manifesto.md/badge/local-first.json",
      "name": "Local-first software",
      "kind": "principles",
      "line": "Seven ideals for software that keeps the primary copy of data on the user's device while still supporting collaboration, from the Ink and Switch essay that named the category.",
      "canonical": "https://www.inkandswitch.com/local-first/",
      "status_of_text": "stable",
      "maintainer": "Martin Kleppmann, Adam Wiggins, Peter van Hardenberg, Mark McGranaghan (Ink and Switch)",
      "publisher": "individual",
      "first_published": "2019-04",
      "listing": "listed",
      "tenets": [
        "No spinners. Your work at your fingertips.",
        "Your work is not trapped on one device.",
        "The network is optional.",
        "Seamless collaboration with your colleagues.",
        "The Long Now. Your data for the long term.",
        "Security and privacy by default.",
        "You retain ultimate ownership and control."
      ],
      "tenets_label": "The seven ideals",
      "related": [
        "owsf"
      ],
      "order": 140
    },
    {
      "slug": "zen-of-python",
      "url": "https://manifesto.md/zen-of-python/",
      "badge": "https://manifesto.md/badge/zen-of-python.json",
      "name": "The Zen of Python",
      "kind": "principles",
      "line": "Nineteen aphorisms for the design of the Python language and of Python code, recorded as PEP 20 and printed by import this.",
      "canonical": "https://peps.python.org/pep-0020/",
      "status_of_text": "stable",
      "maintainer": "Tim Peters, Python Software Foundation",
      "publisher": "individual",
      "first_published": "2004-08-19",
      "listing": "listed",
      "tenets": [
        "Beautiful is better than ugly.",
        "Explicit is better than implicit.",
        "Simple is better than complex.",
        "Readability counts.",
        "Errors should never pass silently, unless explicitly silenced.",
        "In the face of ambiguity, refuse the temptation to guess.",
        "There should be one, and preferably only one, obvious way to do it."
      ],
      "tenets_label": "Selected aphorisms",
      "related": [],
      "order": 150
    },
    {
      "slug": "semver",
      "url": "https://manifesto.md/semver/",
      "badge": "https://manifesto.md/badge/semver.json",
      "name": "Semantic Versioning",
      "short": "SemVer",
      "kind": "specification",
      "line": "A version number of the form major.minor.patch and the rules for when each part increments, so dependency declarations mean the same thing to everyone.",
      "canonical": "https://semver.org/spec/v2.0.0.html",
      "repo": "https://github.com/semver/semver",
      "version": "2.0.0",
      "status_of_text": "stable",
      "license": "CC BY 3.0",
      "maintainer": "Tom Preston-Werner and the semver maintainers",
      "publisher": "community",
      "first_published": "2013-06-18",
      "listing": "listed",
      "tenets": [
        "Major version when you make incompatible API changes.",
        "Minor version when you add functionality in a backward compatible manner.",
        "Patch version when you make backward compatible bug fixes.",
        "Pre-release and build metadata are available as extensions."
      ],
      "tenets_label": "The rule",
      "related": [
        "conventional-commits",
        "keep-a-changelog"
      ],
      "order": 160,
      "adopted_here": "https://github.com/manifesto-md/manifesto.md/blob/main/CHANGELOG.md"
    },
    {
      "slug": "conventional-commits",
      "url": "https://manifesto.md/conventional-commits/",
      "badge": "https://manifesto.md/badge/conventional-commits.json",
      "name": "Conventional Commits",
      "kind": "specification",
      "line": "A lightweight convention on top of commit messages, type, scope and description, that machines and people can read and that maps onto semantic versions.",
      "canonical": "https://www.conventionalcommits.org/en/v1.0.0/",
      "repo": "https://github.com/conventional-commits/conventionalcommits.org",
      "version": "1.0.0",
      "status_of_text": "stable",
      "license": "CC BY 3.0",
      "maintainer": "The Conventional Commits maintainers",
      "publisher": "community",
      "first_published": "2019",
      "listing": "listed",
      "tenets": [
        "type(scope): description, then an optional body and footers.",
        "fix correlates with a patch, feat with a minor, a breaking change footer or an exclamation mark with a major.",
        "Types beyond fix and feat are allowed and recommended, such as build, chore, ci, docs, style, refactor, perf, test."
      ],
      "tenets_label": "The shape",
      "related": [
        "semver",
        "keep-a-changelog"
      ],
      "order": 170,
      "adopted_here": "https://github.com/manifesto-md/manifesto.md/commits/main"
    },
    {
      "slug": "keep-a-changelog",
      "url": "https://manifesto.md/keep-a-changelog/",
      "badge": "https://manifesto.md/badge/keep-a-changelog.json",
      "name": "Keep a Changelog",
      "kind": "specification",
      "line": "A format for a changelog file that people can read, one entry per version, grouped by the kind of change, newest first.",
      "canonical": "https://keepachangelog.com/en/1.1.0/",
      "repo": "https://github.com/olivierlacan/keep-a-changelog",
      "version": "1.1.0",
      "status_of_text": "stable",
      "maintainer": "Olivier Lacan",
      "publisher": "individual",
      "first_published": "2014",
      "listing": "listed",
      "tenets": [
        "Changelogs are for humans, not machines.",
        "There should be an entry for every single version.",
        "The same types of changes should be grouped.",
        "Versions and sections should be linkable.",
        "The latest version comes first.",
        "The release date of each version is displayed.",
        "Mention whether you follow Semantic Versioning."
      ],
      "tenets_label": "Guiding principles",
      "related": [
        "semver",
        "conventional-commits"
      ],
      "order": 180,
      "adopted_here": "https://github.com/manifesto-md/manifesto.md/blob/main/CHANGELOG.md"
    },
    {
      "slug": "contributor-covenant",
      "url": "https://manifesto.md/contributor-covenant/",
      "badge": "https://manifesto.md/badge/contributor-covenant.json",
      "name": "Contributor Covenant",
      "kind": "specification",
      "line": "A code of conduct for open source communities, adopted by tens of thousands of projects, stating the pledge, the standards, the enforcement responsibilities and the consequences.",
      "canonical": "https://www.contributor-covenant.org/version/2/1/code_of_conduct/",
      "repo": "https://github.com/EthicalSource/contributor_covenant",
      "version": "2.1",
      "status_of_text": "stable",
      "license": "CC BY 4.0",
      "maintainer": "Organization for Ethical Source",
      "publisher": "community",
      "first_published": "2014",
      "listing": "listed",
      "tenets": [
        "Our pledge. A harassment-free experience for everyone.",
        "Our standards. Behaviour that contributes to a positive environment, and behaviour that does not.",
        "Enforcement responsibilities and scope.",
        "Enforcement guidelines, from correction to permanent ban."
      ],
      "tenets_label": "Structure",
      "related": [],
      "order": 190,
      "adopted_here": "https://github.com/manifesto-md/manifesto.md/blob/main/CODE_OF_CONDUCT.md"
    },
    {
      "slug": "gnu-manifesto",
      "url": "https://manifesto.md/gnu-manifesto/",
      "badge": "https://manifesto.md/badge/gnu-manifesto.json",
      "name": "The GNU Manifesto",
      "kind": "manifesto",
      "line": "Richard Stallman's 1985 statement of why a complete free Unix-compatible system was being written and what free software means, the founding document of the free software movement.",
      "canonical": "https://www.gnu.org/gnu/manifesto.html",
      "status_of_text": "historical",
      "maintainer": "Richard Stallman, Free Software Foundation",
      "publisher": "community",
      "first_published": "1985-03",
      "listing": "listed",
      "tenets": [
        "Software should be free to share and change; the golden rule requires it.",
        "GNU is a complete Unix-compatible system that is not Unix.",
        "Programmers can be paid without restricting users.",
        "Free software is a matter of freedom, not price."
      ],
      "tenets_label": "What it argues",
      "related": [],
      "order": 200
    },
    {
      "slug": "cluetrain",
      "url": "https://manifesto.md/cluetrain/",
      "badge": "https://manifesto.md/badge/cluetrain.json",
      "name": "The Cluetrain Manifesto",
      "kind": "manifesto",
      "line": "Ninety-five theses from 1999 on how networked markets talk and what that does to companies that still broadcast at them.",
      "canonical": "https://www.cluetrain.com/",
      "status_of_text": "historical",
      "maintainer": "Rick Levine, Christopher Locke, Doc Searls, David Weinberger",
      "publisher": "community",
      "first_published": "1999-04",
      "listing": "listed",
      "tenets": [
        "Markets are conversations.",
        "Markets consist of human beings, not demographic sectors.",
        "Conversations among human beings sound human.",
        "Companies that do not realize their markets are now networked person-to-person are missing their best opportunity."
      ],
      "tenets_label": "Opening theses",
      "related": [],
      "order": 210
    },
    {
      "slug": "a2a",
      "url": "https://manifesto.md/a2a/",
      "badge": "https://manifesto.md/badge/a2a.json",
      "name": "Agent2Agent Protocol",
      "short": "A2A",
      "kind": "specification",
      "line": "An open protocol for communication and interoperability between opaque agentic applications, with JSON-RPC, gRPC and HTTP+JSON bindings and an Agent Card for discovery.",
      "canonical": "https://a2a-protocol.org/latest/specification/",
      "repo": "https://github.com/a2aproject/A2A",
      "version": "1.0.0",
      "status_of_text": "stable",
      "license": "Apache 2.0",
      "maintainer": "A2A Technical Steering Committee, Linux Foundation",
      "publisher": "foundation",
      "listing": "listed",
      "tenets": [
        "Simple: reuse existing, well-understood standards (HTTP, JSON-RPC 2.0, Server-Sent Events).",
        "Enterprise Ready: address authentication, authorization, security, privacy, tracing, and monitoring by aligning with established enterprise practices.",
        "Async First: designed for (potentially very) long-running tasks and human-in-the-loop interactions.",
        "Modality Agnostic: support exchange of diverse content types including text, audio/video, structured data/forms, and potentially embedded UI components.",
        "Opaque Execution: agents collaborate based on declared capabilities and exchanged information, without needing to share their internal thoughts, plans, or tool implementations."
      ],
      "tenets_label": "Guiding principles",
      "related": [
        "mcp",
        "aop"
      ]
    },
    {
      "slug": "openappa",
      "url": "https://manifesto.md/openappa/",
      "badge": "https://manifesto.md/badge/openappa.json",
      "name": "Agentic Permissions Policy Algebra",
      "short": "OpenAPPA",
      "kind": "specification",
      "line": "A declarative policy format and deterministic engine that labels data flowing between an LLM agent and its tools, so restricted data cannot reach audiences it was never allowed to reach.",
      "canonical": "https://www.openappa.com/contracts",
      "repo": "https://github.com/archestra-ai/OpenAPPA",
      "version": "v0.37.0",
      "status_of_text": "draft",
      "license": "MIT",
      "maintainer": "Archestra.AI",
      "publisher": "company",
      "first_published": "2026-08-18",
      "listing": "listed",
      "tenets": [
        "An OpenAPPA policy defines restrictions on tool results and requirements for tool calls.",
        "An audience identifies who can receive data.",
        "Trust describes how much OpenAPPA can rely on the data the agent has received.",
        "Effects record successful actions.",
        "Attention requires fresh approval for each call.",
        "An annotator classifies a tool call.",
        "A sanitizer cleans or validates data before an agent or tool receives it.",
        "An authority reviews a tool call that would otherwise be blocked.",
        "Remedy plans give the agent ways to continue when a call is blocked or a result would add restrictions."
      ],
      "tenets_label": "Core concepts",
      "related": [
        "pact",
        "aop",
        "mcp"
      ],
      "note": "Labelled Preview and RFC by its authors; the policy file format is version 2 and the wire protocol version 1."
    },
    {
      "slug": "agents-md",
      "url": "https://manifesto.md/agents-md/",
      "badge": "https://manifesto.md/badge/agents-md.json",
      "name": "AGENTS.md",
      "kind": "convention",
      "line": "A Markdown file at the root of a repository that gives AI coding agents the context and instructions a new teammate would need, kept separate from the human README.",
      "canonical": "https://agents.md/",
      "repo": "https://github.com/agentsmd/agents.md",
      "status_of_text": "stable",
      "license": "MIT",
      "maintainer": "Agentic AI Foundation, under the Linux Foundation",
      "publisher": "foundation",
      "listing": "listed",
      "tenets": [
        "A simple, open format for guiding coding agents.",
        "Think of AGENTS.md as a README for agents, a dedicated, predictable place to provide the context and instructions to help AI coding agents work on your project.",
        "README.md files are for humans, quick starts, project descriptions, and contribution guidelines; AGENTS.md complements this by containing the extra, sometimes detailed context coding agents need.",
        "Create an AGENTS.md file at the root of the repository.",
        "Cover what matters; add sections that help an agent work effectively with your project, such as project overview, build and test commands, code style guidelines, testing instructions and security considerations.",
        "Commit messages or pull request guidelines, security gotchas, large datasets, deployment steps, anything you'd tell a new teammate belongs here too.",
        "Large monorepo? Use nested AGENTS.md files for subprojects; agents automatically read the nearest file in the directory tree, so the closest one takes precedence.",
        "There are no required fields; AGENTS.md is just standard Markdown.",
        "The closest AGENTS.md to the edited file wins; explicit user chat prompts override everything.",
        "Will the agent run testing commands found in AGENTS.md automatically? Yes, if you list them.",
        "Treat AGENTS.md as living documentation.",
        "One AGENTS.md works across many agents."
      ],
      "tenets_label": "How to use AGENTS.md",
      "related": [
        "12fc",
        "llms-txt",
        "mcp"
      ],
      "adopted_here": "https://github.com/manifesto-md/manifesto.md/blob/main/AGENTS.md"
    },
    {
      "slug": "amazon-leadership-principles",
      "url": "https://manifesto.md/amazon-leadership-principles/",
      "badge": "https://manifesto.md/badge/amazon-leadership-principles.json",
      "name": "Amazon Leadership Principles",
      "kind": "principles",
      "line": "The sixteen principles Amazon says it uses every day when discussing ideas, solving problems and hiring, published on its jobs site.",
      "canonical": "https://www.amazon.jobs/content/en/our-workplace/leadership-principles",
      "status_of_text": "stable",
      "maintainer": "Amazon",
      "publisher": "company",
      "listing": "listed",
      "tenets": [
        "Customer Obsession",
        "Ownership",
        "Invent and Simplify",
        "Are Right, A Lot",
        "Learn and Be Curious",
        "Hire and Develop the Best",
        "Insist on the Highest Standards",
        "Think Big",
        "Bias for Action",
        "Frugality",
        "Earn Trust",
        "Dive Deep",
        "Have Backbone; Disagree and Commit",
        "Deliver Results",
        "Strive to be Earth's Best Employer",
        "Success and Scale Bring Broad Responsibility"
      ],
      "tenets_label": "The principles",
      "related": [
        "netflix-culture",
        "google-ten-things"
      ]
    },
    {
      "slug": "unix-philosophy",
      "url": "https://manifesto.md/unix-philosophy/",
      "badge": "https://manifesto.md/badge/unix-philosophy.json",
      "name": "Basics of the Unix Philosophy",
      "kind": "principles",
      "line": "Eric Raymond's seventeen rules distilling the Unix design tradition, alongside Doug McIlroy's original maxims, from The Art of Unix Programming.",
      "canonical": "http://www.catb.org/~esr/writings/taoup/html/ch01s06.html",
      "status_of_text": "stable",
      "maintainer": "Eric S. Raymond",
      "publisher": "individual",
      "listing": "listed",
      "tenets": [
        "Rule of Modularity: Write simple parts connected by clean interfaces.",
        "Rule of Clarity: Clarity is better than cleverness.",
        "Rule of Composition: Design programs to be connected to other programs.",
        "Rule of Separation: Separate policy from mechanism; separate interfaces from engines.",
        "Rule of Simplicity: Design for simplicity; add complexity only where you must.",
        "Rule of Parsimony: Write a big program only when it is clear by demonstration that nothing else will do.",
        "Rule of Transparency: Design for visibility to make inspection and debugging easier.",
        "Rule of Robustness: Robustness is the child of transparency and simplicity.",
        "Rule of Representation: Fold knowledge into data so program logic can be stupid and robust.",
        "Rule of Least Surprise: In interface design, always do the least surprising thing.",
        "Rule of Silence: When a program has nothing surprising to say, it should say nothing.",
        "Rule of Repair: When you must fail, fail noisily and as soon as possible.",
        "Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.",
        "Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.",
        "Rule of Optimization: Prototype before polishing. Get it working before you optimize it.",
        "Rule of Diversity: Distrust all claims for one true way.",
        "Rule of Extensibility: Design for the future, because it will be here sooner than you think."
      ],
      "tenets_label": "The rules",
      "related": [
        "boring-technology",
        "zen-of-python",
        "tao-of-hashicorp"
      ],
      "note": "The page also quotes McIlroy's summary, write programs that do one thing and do it well, work together, and handle text streams. Served over HTTP only; the HTTPS certificate on catb.org does not match the host."
    },
    {
      "slug": "boring-technology",
      "url": "https://manifesto.md/boring-technology/",
      "badge": "https://manifesto.md/badge/boring-technology.json",
      "name": "Choose Boring Technology",
      "kind": "principles",
      "line": "Dan McKinley's argument for spending a company's few innovation tokens deliberately and preferring well-understood technology with known failure modes.",
      "canonical": "https://boringtechnology.club/",
      "status_of_text": "stable",
      "maintainer": "Dan McKinley",
      "publisher": "individual",
      "listing": "listed",
      "tenets": [
        "We all get a limited number of innovation tokens to spend; early on in a company's life, we get maybe three.",
        "Software that's been around longer tends to need less care and feeding than software that just came out.",
        "Pick the smallest set of tech that covers our problem domain, and lets us get the job done.",
        "Adding the technology is easy, living with it is hard.",
        "You should have a process for adding technology to your stack that involves talking to other humans.",
        "Prefer technology that's well understood, with failure modes that are known.",
        "Prefer things that let you focus your attention on what really matters.",
        "Happiness comes from shipping stuff."
      ],
      "tenets_label": "The argument",
      "related": [
        "unix-philosophy",
        "12-factor-app"
      ]
    },
    {
      "slug": "citation-cff",
      "url": "https://manifesto.md/citation-cff/",
      "badge": "https://manifesto.md/badge/citation-cff.json",
      "name": "Citation File Format",
      "short": "CFF",
      "kind": "convention",
      "line": "A CITATION.cff file in the root of a repository that gives human- and machine-readable citation metadata for software or a dataset, in YAML.",
      "canonical": "https://citation-file-format.github.io/",
      "repo": "https://github.com/citation-file-format/citation-file-format",
      "version": "1.2.0",
      "status_of_text": "stable",
      "license": "CC BY 4.0",
      "maintainer": "Stephan Druskat and Jurriaan H. Spaaks",
      "publisher": "project",
      "listing": "listed",
      "tenets": [
        "CITATION.cff files are plain text files with human- and machine-readable citation information for software (and datasets).",
        "Code developers can include them in their repositories to let others know how to correctly cite their software.",
        "Copy and paste the example into the root of your code repository, and adapt the information to your software.",
        "The file must be named CITATION.cff (note the capitalization) and be valid YAML 1.2.",
        "The keys cff-version, message, title and authors are required.",
        "The type of the work that is being described by this CITATION.cff file is software or dataset; the default is software.",
        "preferred-citation is a reference to another work that should be cited instead of the software or dataset itself.",
        "references are reference(s) to other creative works, for example to make visible the work that your own work builds on.",
        "When there are multiple licenses, it is assumed their relationship is OR, not AND.",
        "If you publish your software in an archive or registry, they (or their systems) can re-use the citation metadata; GitHub, Zenodo and Zotero read the file."
      ],
      "tenets_label": "The format",
      "related": [
        "reuse",
        "spdx"
      ],
      "adopted_here": "https://github.com/manifesto-md/manifesto.md/blob/main/CITATION.cff"
    },
    {
      "slug": "editorconfig",
      "url": "https://manifesto.md/editorconfig/",
      "badge": "https://manifesto.md/badge/editorconfig.json",
      "name": "EditorConfig",
      "kind": "convention",
      "line": "An INI-like .editorconfig file, read from the file's directory upward, that tells any editor the indentation, line endings, charset and whitespace rules of a project.",
      "canonical": "https://editorconfig.org/",
      "repo": "https://github.com/editorconfig/specification",
      "version": "0.17.2",
      "status_of_text": "stable",
      "license": "BSD-2-Clause",
      "maintainer": "EditorConfig Team",
      "publisher": "project",
      "listing": "listed",
      "tenets": [
        "EditorConfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs.",
        "EditorConfig files are easily readable and they work nicely with version control systems.",
        "An EditorConfig file is named \".editorconfig\", all lowercased; plugins look for it in the directory of the opened file and in every parent directory.",
        "The search shall stop if the root filepath is reached or an EditorConfig file is found with the root key set to true in the preamble.",
        "Properties from matching EditorConfig sections are applied in the order they were read, so properties in closer files take precedence.",
        "EditorConfig files are in an INI-like file format; section names are filepath globs, similar to the format accepted by .gitignore, and are case sensitive.",
        "Currently all properties and values are case-insensitive.",
        "For any pair, a value of unset removes the effect of that pair, even if it has been set before.",
        "indent_style: set to tab or space to use hard tabs or soft tabs respectively.",
        "indent_size: a whole number defining the number of columns used for each indentation level.",
        "tab_width: a whole number defining the number of columns used to represent a tab character.",
        "end_of_line: set to lf, cr, or crlf to control how line breaks are represented.",
        "charset: set to latin1, utf-8, utf-8-bom, utf-16be or utf-16le to control the character set.",
        "trim_trailing_whitespace: set to true to remove any whitespace characters preceding newline characters.",
        "insert_final_newline: set to true to ensure file ends with a newline when saving.",
        "root: special property that should be specified at the top of the file outside of any sections.",
        "It is acceptable and often preferred to leave certain EditorConfig properties unspecified."
      ],
      "tenets_label": "The file format",
      "related": [
        "conventional-commits"
      ],
      "adopted_here": "https://github.com/manifesto-md/manifesto.md/blob/main/.editorconfig"
    },
    {
      "slug": "gitlab-values",
      "url": "https://manifesto.md/gitlab-values/",
      "badge": "https://manifesto.md/badge/gitlab-values.json",
      "name": "GitLab Values",
      "short": "CREDIT",
      "kind": "principles",
      "line": "The six values GitLab's public handbook uses to guide behaviour and decisions across the company, summed up by the acronym CREDIT.",
      "canonical": "https://handbook.gitlab.com/handbook/values/",
      "repo": "https://gitlab.com/gitlab-com/content-sites/handbook",
      "status_of_text": "stable",
      "license": "CC BY-SA 4.0",
      "maintainer": "GitLab",
      "publisher": "company",
      "listing": "listed",
      "tenets": [
        "Collaboration",
        "Results for Customers",
        "Efficiency",
        "Diversity, Inclusion & Belonging",
        "Iteration",
        "Transparency"
      ],
      "tenets_label": "CREDIT",
      "related": [
        "posthog-values",
        "netflix-culture"
      ]
    },
    {
      "slug": "humans-txt",
      "url": "https://manifesto.md/humans-txt/",
      "badge": "https://manifesto.md/badge/humans-txt.json",
      "name": "humans.txt",
      "kind": "convention",
      "line": "A plain text file in the site root, next to robots.txt, that names the people who built a website and the standards and tools it uses.",
      "canonical": "https://humanstxt.org/",
      "status_of_text": "stable",
      "license": "CC BY-NC-SA 3.0",
      "maintainer": "The humans.txt H-team",
      "publisher": "community",
      "listing": "listed",
      "tenets": [
        "We are people, not machines.",
        "It's an initiative for knowing the people behind a website.",
        "It's a TXT file that contains information about the different people who have contributed to building the website.",
        "Because it's something simple and fast to create. Because it's not intrusive with the code.",
        "We want to provide some guidelines to make the humans.txt as standard as possible.",
        "The file is named humans.txt, in lower case, UTF-8 encoded, in the site root. Just next to the robots.txt file.",
        "TEAM: role and name, contact, Twitter username and location of each person.",
        "THANKS: name or URL of those you want to thank.",
        "SITE: last update, standards, components and software used in development.",
        "Add a link tag in the head of the site, with rel=\"author\" and type=\"text/plain\", pointing at /humans.txt."
      ],
      "tenets_label": "The guidelines",
      "related": [
        "robots-txt"
      ],
      "adopted_here": "https://manifesto.md/humans.txt"
    },
    {
      "slug": "linear-method",
      "url": "https://manifesto.md/linear-method/",
      "badge": "https://manifesto.md/badge/linear-method.json",
      "name": "Linear Method",
      "kind": "principles",
      "line": "Linear's principles and practices for building software products, from setting product direction to launching and building in public.",
      "canonical": "https://linear.app/method",
      "status_of_text": "stable",
      "maintainer": "Linear",
      "publisher": "company",
      "listing": "listed",
      "tenets": [
        "Set the product direction",
        "Set useful goals",
        "Prioritize enablers and blockers",
        "Scope projects down",
        "Generate momentum",
        "Write issues not user stories",
        "Manage design projects",
        "Build with users",
        "Launch and keep launching",
        "Build in public"
      ],
      "tenets_label": "Principles and practices",
      "related": [
        "shape-up",
        "agile-manifesto"
      ]
    },
    {
      "slug": "mcp",
      "url": "https://manifesto.md/mcp/",
      "badge": "https://manifesto.md/badge/mcp.json",
      "name": "Model Context Protocol",
      "short": "MCP",
      "kind": "specification",
      "line": "An open protocol, built on JSON-RPC, for connecting LLM applications to external data sources and tools through hosts, clients and servers.",
      "canonical": "https://modelcontextprotocol.io/specification/2026-07-28",
      "repo": "https://github.com/modelcontextprotocol/modelcontextprotocol",
      "version": "2026-07-28",
      "status_of_text": "stable",
      "license": "Apache 2.0",
      "maintainer": "MCP Steering Group, Model Context Protocol a Series of LF Projects, LLC",
      "publisher": "foundation",
      "first_published": "2024-11-05",
      "listing": "listed",
      "tenets": [
        "Users must explicitly consent to and understand all data access and operations.",
        "Users must retain control over what data is shared and what actions are taken.",
        "Implementors should provide clear UIs for reviewing and authorizing activities.",
        "Hosts must obtain explicit user consent before exposing user data to servers.",
        "Hosts must not transmit resource data elsewhere without user consent.",
        "User data should be protected with appropriate access controls.",
        "Tools represent arbitrary code execution and must be treated with appropriate caution.",
        "Hosts must obtain explicit user consent before invoking any tool.",
        "Users should understand what each tool does before authorizing its use.",
        "Base protocol: JSON-RPC message format, stateless self-contained requests, per-request capability negotiation.",
        "Servers offer Resources, Prompts and Tools; clients may offer Elicitation.",
        "Extensions are always opt-in and require explicit support from both client and server."
      ],
      "tenets_label": "Key principles",
      "related": [
        "12fc",
        "pact",
        "a2a",
        "openappa"
      ]
    },
    {
      "slug": "netflix-culture",
      "url": "https://manifesto.md/netflix-culture/",
      "badge": "https://manifesto.md/badge/netflix-culture.json",
      "name": "Netflix Culture Memo",
      "kind": "manifesto",
      "line": "Netflix's statement of how it works, from the dream team it hires to the preference for people over process, published on its jobs site.",
      "canonical": "https://jobs.netflix.com/culture",
      "status_of_text": "stable",
      "maintainer": "Netflix",
      "publisher": "company",
      "listing": "listed",
      "tenets": [
        "The Dream Team",
        "People Over Process",
        "Uncomfortably Exciting",
        "Artistic Expression",
        "Great and Always Better"
      ],
      "tenets_label": "Sections",
      "related": [
        "amazon-leadership-principles",
        "gitlab-values"
      ]
    },
    {
      "slug": "posthog-values",
      "url": "https://manifesto.md/posthog-values/",
      "badge": "https://manifesto.md/badge/posthog-values.json",
      "name": "PostHog Values",
      "kind": "principles",
      "line": "The five values in PostHog's public handbook that describe how the company expects its team to work and decide.",
      "canonical": "https://posthog.com/handbook/values",
      "repo": "https://github.com/PostHog/posthog.com",
      "status_of_text": "stable",
      "maintainer": "PostHog",
      "publisher": "company",
      "listing": "listed",
      "tenets": [
        "You're the driver",
        "Make it public",
        "Do more weird",
        "Why not now?",
        "Optimistic by default"
      ],
      "tenets_label": "The values",
      "related": [
        "gitlab-values",
        "linear-method"
      ]
    },
    {
      "slug": "reuse",
      "url": "https://manifesto.md/reuse/",
      "badge": "https://manifesto.md/badge/reuse.json",
      "name": "REUSE Specification",
      "short": "REUSE",
      "kind": "convention",
      "line": "A standardised way to declare copyright and licensing for every file in a project, using SPDX identifiers in comment headers, a LICENSES directory and REUSE.toml.",
      "canonical": "https://reuse.software/spec-3.3/",
      "repo": "https://github.com/fsfe/reuse-website",
      "version": "3.3",
      "status_of_text": "stable",
      "license": "CC BY-SA 4.0",
      "maintainer": "Free Software Foundation Europe",
      "publisher": "foundation",
      "first_published": "2024-11-14",
      "listing": "listed",
      "tenets": [
        "This specification defines a standardised method for declaring copyright and licensing for software projects.",
        "The goal of the specification is to have comprehensive, unambiguous, human- and machine-readable copyright and licensing information for each individual file in a project.",
        "A Project MUST include a License File for every license under which Covered Files are licensed, in the LICENSES directory.",
        "The name of the License File MUST be the SPDX License Identifier of the license; for a license not in the SPDX License List, its SPDX License Identifier MUST be LicenseRef-[idstring].",
        "Each Covered File MUST have Licensing Information associated with it.",
        "It is RECOMMENDED to use the SPDX-FileCopyrightText tag for Copyright Notices.",
        "The SPDX-License-Identifier tag MUST be followed by a valid SPDX License Expression.",
        "Comment headers are the RECOMMENDED method.",
        "Licensing Information MAY be associated with a file through a REUSE.toml file, which MUST be a valid TOML file.",
        "REUSE.toml and DEP5 are mutually exclusive. You MUST NOT use both simultaneously; DEP5 is deprecated and you SHOULD create a REUSE.toml file instead.",
        "You SHOULD use SPDX snippets to license Snippets; each opened snippet MUST be closed with SPDX-SnippetEnd."
      ],
      "tenets_label": "The requirements",
      "related": [
        "spdx",
        "citation-cff"
      ],
      "adopted_here": "https://github.com/manifesto-md/manifesto.md/blob/main/REUSE.toml"
    },
    {
      "slug": "robots-txt",
      "url": "https://manifesto.md/robots-txt/",
      "badge": "https://manifesto.md/badge/robots-txt.json",
      "name": "Robots Exclusion Protocol",
      "short": "robots.txt",
      "kind": "convention",
      "line": "The rules a service publishes at /robots.txt to tell crawlers which URIs they may access, as standardised by the IETF in RFC 9309 from Martijn Koster's 1994 method.",
      "canonical": "https://www.rfc-editor.org/rfc/rfc9309.html",
      "status_of_text": "stable",
      "license": "IETF Trust Legal Provisions (BCP 78)",
      "maintainer": "IETF; authors Martijn Koster, Gary Illyes, Henner Zeller and Lizzi Sassman",
      "publisher": "foundation",
      "first_published": "2022-09",
      "listing": "listed",
      "tenets": [
        "This document specifies the rules originally defined by the \"Robots Exclusion Protocol\" that crawlers are requested to honor when accessing URIs.",
        "The rules MUST be accessible in a file named \"/robots.txt\" (all lowercase) in the top-level path of the service, UTF-8 encoded and served as text/plain.",
        "A group is one or more user-agent lines that are followed by one or more rules; a rule is a line with a key-value pair that defines how a crawler may access URIs.",
        "Crawlers MUST use case-insensitive matching to find the group that matches the product token; if no group matches, they follow the \"*\" group if one exists.",
        "Allow and disallow lines indicate whether accessing a URI that matches the corresponding path is allowed or disallowed; the matching MUST start with the first octet of the path.",
        "The most specific match found MUST be used; the most specific match is the match that has the most octets.",
        "If no matching rule exists, the URI is allowed.",
        "Crawlers MUST support the special characters \"#\" (line comment), \"$\" (end of the match pattern) and \"*\" (0 or more instances of any character).",
        "The crawlers SHOULD follow at least five consecutive redirects, even across authorities.",
        "A 4xx status code means robots.txt is unavailable and the crawler MAY access any resources on the server.",
        "A 5xx status code means robots.txt is unreachable and the crawler MUST assume complete disallow.",
        "Crawlers SHOULD NOT use the cached version for more than 24 hours, unless the robots.txt file is unreachable.",
        "The parsing limit MUST be at least 500 kibibytes."
      ],
      "tenets_label": "The rules",
      "related": [
        "llms-txt",
        "security-txt"
      ],
      "adopted_here": "https://manifesto.md/robots.txt"
    },
    {
      "slug": "security-txt",
      "url": "https://manifesto.md/security-txt/",
      "badge": "https://manifesto.md/badge/security-txt.json",
      "name": "security.txt",
      "kind": "convention",
      "line": "A machine-parsable file at /.well-known/security.txt in which an organisation states how security researchers should report vulnerabilities to it, defined by RFC 9116.",
      "canonical": "https://www.rfc-editor.org/rfc/rfc9116.html",
      "repo": "https://github.com/securitytxt/security-txt",
      "status_of_text": "stable",
      "license": "IETF Trust Legal Provisions (BCP 78)",
      "maintainer": "IETF (Informational); authors Edwin Foudil and Yakov Shafranovich",
      "publisher": "foundation",
      "first_published": "2022-04",
      "listing": "listed",
      "tenets": [
        "When security vulnerabilities are discovered by researchers, proper reporting channels are often lacking.",
        "In this document, we define a richer, machine-parsable, and more extensible way for organizations to communicate information about their security disclosure practices and ways to contact them.",
        "For web-based services, organizations MUST place the \"security.txt\" file under the \"/.well-known/\" path.",
        "The file MUST be accessed via HTTP 1.0 or a higher version, and the file access MUST use the \"https\" scheme.",
        "The file MUST have a Content-Type of \"text/plain\" with the default charset parameter set to \"utf-8\".",
        "The format of this file is machine parsable and MUST follow the ABNF grammar defined in Section 4.",
        "Unless otherwise stated, all fields MUST be considered optional.",
        "The \"Contact\" field MUST always be present in a \"security.txt\" file.",
        "The \"Expires\" field MUST always be present and MUST NOT appear more than once.",
        "The \"Canonical\" field indicates the canonical URIs where the \"security.txt\" file is located.",
        "The \"Encryption\" field indicates an encryption key that security researchers should use for encrypted communication; keys MUST NOT appear in this field.",
        "The \"Policy\" field indicates a link to where the vulnerability disclosure policy is located.",
        "If the \"Preferred-Languages\" field is absent, security researchers may assume that English is the language to be used.",
        "The \"Acknowledgments\" field indicates a link to a page where security researchers are recognized for their reports.",
        "The \"Hiring\" field is used for linking to the vendor's security-related job positions.",
        "It is RECOMMENDED that a \"security.txt\" file be digitally signed using an OpenPGP cleartext signature."
      ],
      "tenets_label": "The format",
      "related": [
        "robots-txt",
        "well-known-uris"
      ],
      "adopted_here": "https://manifesto.md/.well-known/security.txt"
    },
    {
      "slug": "shape-up",
      "url": "https://manifesto.md/shape-up/",
      "badge": "https://manifesto.md/badge/shape-up.json",
      "name": "Shape Up",
      "kind": "principles",
      "line": "Basecamp's method for product development in six-week cycles, in three parts, shaping the work, betting on it, and building it, written as a free online book.",
      "canonical": "https://basecamp.com/shapeup",
      "status_of_text": "stable",
      "maintainer": "Ryan Singer, 37signals",
      "publisher": "company",
      "listing": "listed",
      "tenets": [
        "Principles of Shaping",
        "Set Boundaries",
        "Find the Elements",
        "Risks and Rabbit Holes",
        "Write the Pitch",
        "Bets, Not Backlogs",
        "The Betting Table",
        "Place Your Bets",
        "Hand Over Responsibility",
        "Get One Piece Done",
        "Map the Scopes",
        "Show Progress",
        "Decide When to Stop",
        "Move On"
      ],
      "tenets_label": "Chapters",
      "related": [
        "linear-method",
        "agile-manifesto"
      ]
    },
    {
      "slug": "sitemaps",
      "url": "https://manifesto.md/sitemaps/",
      "badge": "https://manifesto.md/badge/sitemaps.json",
      "name": "Sitemaps XML format",
      "short": "Sitemaps",
      "kind": "convention",
      "line": "An XML file listing the URLs of a site, with optional last-modified, change-frequency and priority hints, that webmasters publish so search engines can crawl more intelligently.",
      "canonical": "https://www.sitemaps.org/protocol.html",
      "version": "0.90",
      "status_of_text": "stable",
      "license": "CC BY-SA 2.5",
      "maintainer": "sitemaps.org, sponsored by Google, Yahoo! and Microsoft",
      "publisher": "community",
      "listing": "listed",
      "tenets": [
        "Sitemaps are an easy way for webmasters to inform search engines about pages on their sites that are available for crawling.",
        "The Sitemap protocol format consists of XML tags; the file itself must be UTF-8 encoded.",
        "Begin with an opening <urlset> tag and end with a closing </urlset> tag, specifying the namespace http://www.sitemaps.org/schemas/sitemap/0.9.",
        "Include a <url> entry for each URL, as a parent XML tag.",
        "Include a <loc> child entry for each <url> parent tag.",
        "The <lastmod>, <changefreq> and <priority> tags are optional.",
        "All data values in a Sitemap must be entity-escaped.",
        "Each Sitemap file that you provide must have no more than 50,000 URLs and must be no larger than 50MB (52,428,800 bytes).",
        "A Sitemap index file lists multiple Sitemaps, up to 50,000; it can only specify Sitemaps that are found on the same site as the Sitemap index file.",
        "The location of a Sitemap file determines the set of URLs that can be included in that Sitemap; all URLs must share its protocol and host.",
        "Point search engines to a Sitemap with a Sitemap line in robots.txt, for example Sitemap: http://www.example.com/sitemap.xml."
      ],
      "tenets_label": "The protocol",
      "related": [
        "robots-txt",
        "llms-txt"
      ],
      "adopted_here": "https://manifesto.md/sitemap.xml"
    },
    {
      "slug": "stripe-operating-principles",
      "url": "https://manifesto.md/stripe-operating-principles/",
      "badge": "https://manifesto.md/badge/stripe-operating-principles.json",
      "name": "Stripe Operating Principles",
      "kind": "principles",
      "line": "The six principles Stripe lists under \"How we operate\" on its careers site to describe how it expects people to work.",
      "canonical": "https://stripe.com/jobs/culture",
      "status_of_text": "stable",
      "maintainer": "Stripe",
      "publisher": "company",
      "listing": "listed",
      "tenets": [
        "Users first",
        "Create with craft and beauty",
        "Move with urgency and focus",
        "Collaborate egolessly",
        "Stay curious",
        "Obsess over talent"
      ],
      "tenets_label": "How we operate",
      "related": [
        "amazon-leadership-principles",
        "linear-method"
      ]
    },
    {
      "slug": "spdx",
      "url": "https://manifesto.md/spdx/",
      "badge": "https://manifesto.md/badge/spdx.json",
      "name": "System Package Data Exchange",
      "short": "SPDX",
      "kind": "convention",
      "line": "An open standard data model and serialisations for communicating bill-of-materials information about software, including licensing, security, build, AI and dataset metadata.",
      "canonical": "https://spdx.github.io/spdx-spec/v3.0.1/",
      "repo": "https://github.com/spdx/spdx-spec",
      "version": "3.0.1",
      "status_of_text": "stable",
      "license": "Community Specification License 1.0 (earlier portions CC BY 3.0)",
      "maintainer": "The Linux Foundation, SPDX project",
      "publisher": "foundation",
      "listing": "listed",
      "tenets": [
        "The System Package Data Exchange (SPDX) specification defines an open standard for communicating bill of materials information for different topic areas.",
        "A data exchange format so that information about software packages and related content may be collected and shared in a common format, with the goal of saving time and improving data accuracy.",
        "Accurate identification of software is key for many supply chain processes.",
        "SPDX defines an underlying data model as well as multiple serialization formats to encode that data model.",
        "SPDX metadata includes software composition (packages, files and snippets), build information, AI models and datasets.",
        "SPDX metadata includes creator, supplier and distributor identity, and provenance and integrity.",
        "SPDX metadata includes licenses and copyrights, including a curated list of licenses and exceptions.",
        "SPDX metadata includes security vulnerabilities, defects and other quality data, relationships between system elements, and software usage and lifecycle.",
        "SPDX metadata includes mechanisms for annotating SPDX elements and linking multiple SPDX Documents.",
        "SPDX is organized in areas of interest or profiles focused on specific user needs; the Core Profile is mandatory, all others are optional.",
        "Conformance to the Core Profile compliance point is mandatory for all other SPDX profiles.",
        "The Lite Profile captures the minimum set of information required for license compliance.",
        "The SPDX specification is a freely available international open standard (ISO/IEC 5962:2021)."
      ],
      "tenets_label": "Scope",
      "related": [
        "reuse",
        "citation-cff"
      ],
      "adopted_here": "https://github.com/manifesto-md/manifesto.md/blob/main/REUSE.toml"
    },
    {
      "slug": "google-ten-things",
      "url": "https://manifesto.md/google-ten-things/",
      "badge": "https://manifesto.md/badge/google-ten-things.json",
      "name": "Ten things we know to be true",
      "kind": "principles",
      "line": "Google's ten-point philosophy, first written when the company was a few years old and kept as a public statement of how it builds products.",
      "canonical": "https://about.google/company-info/philosophy/",
      "status_of_text": "stable",
      "maintainer": "Google",
      "publisher": "company",
      "listing": "listed",
      "tenets": [
        "Focus on the user and all else will follow.",
        "It's best to do one thing really, really well.",
        "Fast is better than slow.",
        "Democracy on the web works.",
        "You don't need to be at your desk to need an answer.",
        "You can make money without doing evil.",
        "There's always more information out there.",
        "The need for information crosses all borders.",
        "You can be serious without a suit.",
        "Great just isn't good enough."
      ],
      "tenets_label": "The ten things",
      "related": [
        "amazon-leadership-principles",
        "unix-philosophy"
      ]
    },
    {
      "slug": "llms-txt",
      "url": "https://manifesto.md/llms-txt/",
      "badge": "https://manifesto.md/badge/llms-txt.json",
      "name": "The /llms.txt file",
      "short": "llms.txt",
      "kind": "convention",
      "line": "A proposal for a Markdown file at /llms.txt that gives language models a curated overview of a website and links to clean Markdown versions of its pages.",
      "canonical": "https://llmstxt.org/",
      "repo": "https://github.com/AnswerDotAI/llms-txt",
      "version": "2",
      "status_of_text": "stable",
      "license": "Apache-2.0",
      "maintainer": "Jeremy Howard",
      "publisher": "individual",
      "first_published": "2024-09-03",
      "listing": "listed",
      "tenets": [
        "We propose adding a /llms.txt markdown file to websites to provide LLM-friendly content.",
        "Context windows, while larger than they were, are still too small for most websites in their entirety.",
        "The llms.txt file is unusual in that it uses Markdown to structure the information rather than a classic structured format such as XML.",
        "An H1 with the name of the project or site. This is the only required section.",
        "A blockquote with a short summary of the project, containing key information necessary for understanding the rest of the file.",
        "Zero or more markdown sections (e.g. paragraphs, lists, etc) of any type except headings.",
        "Zero or more markdown sections delimited by H2 headers, containing file lists of URLs where further detail is available; each item is a markdown link, optionally followed by a colon and notes.",
        "The \"Optional\" section is used, by convention, for secondary information that can be skipped if a shorter context is needed.",
        "Provide a clean markdown version of those pages at the same URL as the original page, but with .md appended.",
        "llms.txt is designed to coexist with current web standards.",
        "While sitemaps list all pages for search engines, llms.txt offers a curated overview for LLMs.",
        "It can complement robots.txt by providing context for allowed content."
      ],
      "tenets_label": "The proposal",
      "related": [
        "agents-md",
        "robots-txt"
      ],
      "adopted_here": "https://manifesto.md/llms.txt"
    },
    {
      "slug": "mozilla-manifesto",
      "url": "https://manifesto.md/mozilla-manifesto/",
      "badge": "https://manifesto.md/badge/mozilla-manifesto.json",
      "name": "The Mozilla Manifesto",
      "kind": "manifesto",
      "line": "Mozilla's ten principles for an internet that is open, accessible and enriches people's lives, with a 2017 addendum pledging a healthy internet.",
      "canonical": "https://www.mozilla.org/en-US/about/manifesto/",
      "status_of_text": "stable",
      "maintainer": "Mozilla Foundation",
      "publisher": "foundation",
      "first_published": "2007",
      "listing": "listed",
      "tenets": [
        "The internet is an integral part of modern life, a key component in education, communication, collaboration, business, entertainment and society as a whole.",
        "The internet is a global public resource that must remain open and accessible.",
        "The internet must enrich the lives of individual human beings.",
        "Individuals' security and privacy on the internet are fundamental and must not be treated as optional.",
        "Individuals must have the ability to shape the internet and their own experiences on it.",
        "The effectiveness of the internet as a public resource depends upon interoperability (protocols, data formats, content), innovation and decentralized participation worldwide.",
        "Free and open source software promotes the development of the internet as a public resource.",
        "Transparent community-based processes promote participation, accountability and trust.",
        "Commercial involvement in the development of the internet brings many benefits; a balance between commercial profit and public benefit is critical.",
        "Magnifying the public benefit aspects of the internet is an important goal, worthy of time, attention and commitment.",
        "We are committed to an internet that includes all the peoples of the earth, where a person's demographic characteristics do not determine their online access, opportunities, or quality of experience.",
        "We are committed to an internet that promotes civil discourse, human dignity, and individual expression.",
        "We are committed to an internet that elevates critical thinking, reasoned argument, shared knowledge, and verifiable facts.",
        "We are committed to an internet that catalyzes collaboration among diverse communities working together for the common good."
      ],
      "tenets_label": "Principles",
      "related": [
        "gnu-manifesto",
        "cluetrain",
        "local-first"
      ]
    },
    {
      "slug": "tao-of-hashicorp",
      "url": "https://manifesto.md/tao-of-hashicorp/",
      "badge": "https://manifesto.md/badge/tao-of-hashicorp.json",
      "name": "The Tao of HashiCorp",
      "kind": "principles",
      "line": "The eight design principles HashiCorp states as the foundation of its products and the way it approaches building infrastructure tooling.",
      "canonical": "https://www.hashicorp.com/en/tao-of-hashicorp",
      "status_of_text": "stable",
      "maintainer": "HashiCorp",
      "publisher": "company",
      "listing": "listed",
      "tenets": [
        "Workflows, not technologies",
        "Simple, Modular, Composable",
        "Communicating Sequential Processes",
        "Immutability",
        "Versioning through Codification",
        "Automation through Codification",
        "Resilient Systems",
        "Pragmatism"
      ],
      "tenets_label": "The principles",
      "related": [
        "12-factor-app",
        "unix-philosophy"
      ]
    },
    {
      "slug": "valve-handbook",
      "url": "https://manifesto.md/valve-handbook/",
      "badge": "https://manifesto.md/badge/valve-handbook.json",
      "name": "Valve Handbook for New Employees",
      "kind": "principles",
      "line": "Valve's guide for new hires on working in a company with no managers, which it describes as an abbreviated encapsulation of its guiding principles.",
      "canonical": "https://cdn.fastly.steamstatic.com/apps/valve/Valve_NewEmployeeHandbook.pdf",
      "version": "First edition",
      "status_of_text": "stable",
      "maintainer": "Valve Corporation",
      "publisher": "company",
      "first_published": "2012-03",
      "listing": "listed",
      "tenets": [
        "Welcome to Valve",
        "Welcome to Flatland",
        "Settling In",
        "What to Work On",
        "Teams, Hours, and the Office",
        "Risks",
        "How Am I Doing?",
        "Your Peers and Your Performance",
        "Choose Your Own Adventure",
        "Valve Is Growing",
        "Your Most Important Role",
        "What Is Valve Not Good At?"
      ],
      "tenets_label": "Parts",
      "related": [
        "netflix-culture",
        "gitlab-values"
      ],
      "note": "Linked from Valve's publications page at https://www.valvesoftware.com/en/publications."
    },
    {
      "slug": "well-known-uris",
      "url": "https://manifesto.md/well-known-uris/",
      "badge": "https://manifesto.md/badge/well-known-uris.json",
      "name": "Well-Known Uniform Resource Identifiers",
      "short": "/.well-known/",
      "kind": "convention",
      "line": "A reserved path prefix, /.well-known/, under which registered site-wide metadata such as security.txt lives, so applications can discover information about an origin, defined by RFC 8615.",
      "canonical": "https://www.rfc-editor.org/rfc/rfc8615.html",
      "status_of_text": "stable",
      "license": "IETF Trust Legal Provisions (BCP 78)",
      "maintainer": "IETF; author Mark Nottingham",
      "publisher": "foundation",
      "first_published": "2019-05",
      "listing": "listed",
      "tenets": [
        "Some applications on the Web require the discovery of information about an origin, sometimes called \"site-wide metadata\", before making a request.",
        "This memo reserves a path prefix in HTTP, HTTPS, WebSocket (WS), and Secure WebSocket (WSS) URIs for these \"well-known locations\", \"/.well-known/\".",
        "A well-known URI is a URI whose path component begins with the characters \"/.well-known/\", and whose scheme is \"HTTP\", \"HTTPS\", or another scheme that has explicitly been specified to use well-known URIs.",
        "Well-known URIs can also be used with other URI schemes, but only when those schemes' definitions explicitly allow it.",
        "Applications that wish to mint new well-known URIs MUST register them, following the procedures in Section 5.1.",
        "Registered names MUST conform to the \"segment-nz\" production in RFC 3986; this means they cannot contain the \"/\" character.",
        "At a minimum, a registration will reference a specification that defines the format and associated media type(s).",
        "Well-known URIs are rooted in the top of the path's hierarchy; they are not well-known by definition in other parts of the path.",
        "Clients should not expect a resource to exist at \"/.well-known/\" itself.",
        "Registration requests consist of at least the following information: URI suffix, change controller, specification document(s), status and related information.",
        "Because well-known locations effectively represent the entire origin, server operators should appropriately control the ability to write to them."
      ],
      "tenets_label": "The rules",
      "related": [
        "security-txt",
        "robots-txt"
      ],
      "adopted_here": "https://manifesto.md/.well-known/security.txt"
    }
  ]
}