Projects
For users: a project is a venture and it belongs to its team. It has a name, a stage (idea, validating, building, or launched), and a roster of people who work on it. Each person is a lead or a member and can carry a short title such as “Product” or “Go-to-market.”
Organizations never own a project. A club, an accelerator, or an investor affiliates with it instead, and a project can hold several affiliations at once. The team decides where the project goes.
Starting a project
Section titled “Starting a project”Choose Projects in the top bar, then Start a project, or run:
vn projects create --name "Soil Sense" --stage validatingYou become its lead. A project’s address uses its id, https://venturenetwork.ai/projects/<id>.
Who runs it
Section titled “Who runs it”Leads run everything: the project’s details, its visibility, archiving, deleting, and the team. Anyone in the network can be added to a team, up to 50 people. Assigning someone already on the team changes their role or title instead.
The last lead cannot leave, be removed, or be made a member. Make someone else a lead first. Joining or leaving an organization never changes who is on a project.
Archiving freezes the team. Nobody can be added and roles and titles stay as they are until a lead unarchives it. People can still be removed or leave.
Visibility
Section titled “Visibility”| Setting | Who can see the project and its team |
|---|---|
| Network (the default) | Every signed-in member. It shows up in project search. |
| Private | The team, plus the owners and admins of organizations it is affiliated with or has asked to join. |
Private suits a venture in stealth that still wants an accelerator to see it.
Affiliations
Section titled “Affiliations”An affiliation ties a project to an organization. It has a kind:
| Kind | For |
|---|---|
| Community | A club or network the team belongs to |
| Program | An accelerator, incubator, or cohort |
| Investor | A funder or anyone holding a stake |
Both sides agree to every affiliation. Either the team asks and the organization accepts, or the organization invites and the team accepts. A lead asks from the project page or with vn projects affiliate <id> <org> --kind program. An owner or admin invites from the organization’s Settings, then Projects, or with vn projects invite <org> <id> --kind program.
When an organization accepts, it can also invite the team to join it as members, which is checked by default. Each person still gets an ordinary invitation and decides for themselves. The organization can send the team invitations later too.
Either side can end an affiliation. The history stays, and the team can ask again later. An organization can add a cohort label, such as “Spring 2027,” which shows next to the project on the organization’s Projects tab.
Other members see an affiliation only once it is active, and only for public organizations or ones they belong to. Requests, declines, and ended affiliations are visible only to the two sides involved.
Deal terms
Section titled “Deal terms”Every affiliation has a private deal terms field for any funding or stake arrangement, written as plain text. Only the project’s leads and the organization’s owners and admins can read or edit it. Nobody else ever sees it, including the rest of the team. Edit it from the affiliation on the project page or the organization’s Projects settings, or with vn projects terms <affiliation> --set "...".
From an MCP client
Section titled “From an MCP client”The project tools are list_projects, get_project, create_project, update_project, delete_project, assign_to_project, and remove_from_project. The affiliation tools are list_affiliations, request_affiliation, invite_project, respond_to_affiliation, update_affiliation, and invite_project_team. Reading needs the network:read scope and changes need network:write.