Establish the project and its owner
In the development admin workflow, the project owner creates a project room or registers a room they control. The system verifies room authority and establishes a fleet-scoped project binding. It also creates or validates a separate encrypted owner approval conversation.
A server account, project metadata, and the right to approve a specific agent’s work are different relationships. Do not assume the first requester becomes the owner automatically.
Request a published role
Choose a role from the fleet’s current published catalog and the requested allocation. The request is tied to the actual sender and target project. The resource contributor decides which qualified resource or named agent will serve it.
The provider reviews the request in Hagency. Configured definitions are not yet running agents; allocation may provision a new identity or reuse a qualified existing agent.
Wait for actual admission
The request becomes usable only after fulfillment succeeds and the actual agent is observed in the target room. Pending, failed, and unknown states need to remain visible. Once admitted, open the project in Robrix2 and start a task with an explicit mention.