Resolving a new-room request
A new-room request (the new-room label) asks for a room that does not yet
exist.
On a stack running a room provisioner, the concierge has the provisioner create a room on the spot for a user it admits. The provisioner files that request's issue itself (its body records the Room id being created), then comments on and closes it once the room is live. Such an issue left open needs a look:
- with a provisioner comment: the comment says what failed, or which steps remain
- with no comment: the provisioner stopped mid-run
The rest of this page covers a request the concierge filed for an
administrator to carry out. Resolving it is two jobs: read the spec the requester provided, then
build the room with the soliplex-template
skill. The soliplex-concierge-admin skill handles the first job and records
the outcome; soliplex-template does the provisioning.
1. Read the spec
Find the open new-room requests and read one:
uv run scripts/gitea_issues.py search --type new-room \
--owner <owner> --repo <repo>
uv run scripts/gitea_issues.py show <number> --owner <owner> --repo <repo>
The body follows the room-skill's new-room template, which captures:
- Name and purpose — what the room is for.
- Knowledge sources — the documents or data it should draw from (this drives whether a RAG database is needed).
- Access — who should be able to use it (public, or a specific set of users).
- Tools / skills — any capabilities the room should provide.
Any field the requester left blank shows as *(not provided)*; comment on the
issue to fill the gap rather than guessing (see
Administering requests).
2. Create the room
Use the soliplex-template skill against the target stack to create and
configure the room. Follow soliplex-docs for the configuration details:
- Room configuration — create the room and set its prompt, tools, and skills per the spec. See the room configuration docs.
- RAG database — if the request named knowledge sources, create and ingest a
RAG database for them, then wire it into the room's
skill_configs(rag_lancedb_stem). Thesoliplex-templateskill can generate and ingest the database; see the RAG DB docs. - Access — if the room should be private, apply the requested access the
same way as for an access request (
soliplex-cli room-authz).
3. Record the outcome
Once the room is live, comment what you did and close the issue:
uv run scripts/gitea_issues.py close <number> --owner <owner> \
--repo <repo> --body "Created room 'marketing' with a RAG DB over the 2024 decks; granted the marketing team access."
If the request could not be fulfilled, comment what is blocking it and leave the issue open.