Landscape missing goose, an AAIF hosted project

[asish-singh]

The landscape currently lists MCP under Communication Protocols, but goose, which was donated to the AAIF at launch alongside MCP, is not on the landscape map. Suggesting it be added so the foundation's own hosted projects are fully represented.

Proposed entry under Agent Runtimes, Frameworks and Workflow Orchestration, subcategory Autonomous Agent Frameworks:

- name: goose
  logo: placeholder.svg
  homepage_url: https://block.github.io/goose/
  repo_url: https://github.com/block/goose
  description: Open-source, extensible AI agent that automates engineering tasks end to end, from planning through code execution, using MCP for tool integration.
  project: member

I used project: member to match how MCP is marked, happy to adjust if hosted projects should carry a different status. If helpful, I can follow up with a pull request adding this entry.

[thc1006]

Thanks for filing this and drafting the entry, @asish-singh. I opened #27 to add goose from your proposal.

One change from your draft: I used aaif-goose/goose and goose-docs.ai to match how the published aaif-landscape already lists goose, since the project moved under the AAIF org after it was donated. The original block/goose still redirects there, so both still work, but matching the existing entry keeps the two landscapes consistent. Happy to switch to the upstream URL if you or the editors prefer it.

I also noticed agentgateway and AGENTS.md are missing from this landscape. I left them out of the PR since neither has an obvious category here yet, but they seemed worth raising given this is about representing the foundation's hosted projects.

Thanks again for getting this started.

[asish-singh]

Thanks @thc1006, and agreed on the URLs. I checked, and block/goose now resolves to aaif-goose/goose, with goose-docs.ai serving the docs directly, so your metadata is the more durable choice. Worth keeping the PR exactly as it stands.

On project: member, I have no strong view. Matching MCP seemed like the safest default given both were donated at launch, so whatever the Domain Editors settle on for MCP should apply to goose too.

Good catch on agentgateway and AGENTS.md. The placement problem is real, since agentgateway is a gateway and control plane while AGENTS.md is a file format convention, and neither fits an existing subcategory cleanly. I would rather an editor name the category than invent one, so I am happy to open a follow up issue framing the question if that is useful.

[thc1006]

Thanks @asish-singh, that matches the redirects I checked, so I'll leave the PR as it stands.

Agreed on project as well: having goose follow whatever the Domain Editors decide for MCP keeps the two launch-donated projects consistent.

A follow-up issue for agentgateway and AGENTS.md would be helpful if you have the time. Framing it as a placement question for the editors rather than proposing a category makes sense, since agentgateway is a gateway and control plane while AGENTS.md is a file-format convention. I'm glad to prepare the landscape entries once a subcategory is chosen.