Project Tools

A project is one client engagement's record: its key, which prefixes every reference inside it, its status from discovery to maintenance, its methodology, visibility, health and leads.

A project is one client engagement's record: its key, which prefixes every reference inside it, its status from discovery to maintenance, its methodology, visibility, health and leads. These tools read the registry as the token sees it, the clients the projects are done for, the components each project is made of (its web app, API, mobile apps and services, with the slug their versions carry and the stack they are built with) and the environments each runs in (their addresses, the branch deployed there, the flags, the health the last check found and any change freeze) and the design references each keeps (links to Figma files, wireframes, prototypes, screenshots, API contracts and diagrams, attached to the whole project or to one component, with the version that is current); and, as far as the token's abilities allow, create and change them: a client (create_client, update_client), a project with a key suggested from its name (create_project, update_project) and its settings (update_project_settings), and the components, environments and design references under it, each with a delete that pauses for confirmation. Archiving and deleting a project, the health a monitor records and a change freeze stay in the application and the REST API, and the build, test, release and maintenance tools join as each module lands.

Tools

How is this guide?

Last updated on

On this page

What changed recentlyEvery release of Zuse Bifrost, with the pages it touched.

For AI agents: llms.txt · llms-full.txt