External/roboco
1
0
Fork 0
mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs(rag): rewrite the KB docs to the real gateway verb surface

Browse Source 
The RAG knowledge base (indexed and queried by agents at runtime)
described entire fictional MCP tool surfaces — roboco_task_*,
roboco_journal_*, roboco_message_send, roboco_notify_send, roboco_agent_*,
roboco_session_*, roboco_workspace_*, roboco_project_* — that don't exist,
so agents searching the KB were handed invented tool names.

Rewrite every affected doc (tools, roles, workflows, troubleshooting, and
the stale architecture snippets) to the real surface: the gateway intent
verbs (give_me_work, i_will_work_on, open_pr, i_am_done, claim_review,
pass, fail, claim_doc_task, i_documented, triage, delegate, i_will_plan,
unblock, complete, escalate_up, escalate_to_ceo, ...) and content tools
(commit, note(scope=...), say, dm, evidence, notify*, open_session,
channels). Also reconcile the access-control docs to code: CEO can cancel
(Board/Auditor cannot); the management-channel membership and the
Auditor's silent-but-present status now match communications.py.
This commit is contained in:
Renn F
2026-06-05 17:20:36 +02:00
parent 416356899d
commit ecea593a51
27 changed files with 999 additions and 1009 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/rag/architecture/workspaces.md
+10 -17
View File
@@ -55,21 +55,13 @@ ROBOCO_WORKSPACE_CLONE_TIMEOUT=300
3. **Branch Flexibility**: Different branches simultaneously
4. **Clean State**: Fresh clone if needed
## MCP Tools
## No Workspace Tools — It's Automatic
| Tool | Purpose |
|------|---------|
| `roboco_workspace_ensure` | Create workspace if needed |
| `roboco_workspace_status` | Check workspace state |
| `roboco_workspace_list` | List all workspaces (PM only) |
```python
# Ensure workspace exists (auto-clones if needed)
roboco_workspace_ensure(project_slug="roboco")
# Check status
roboco_workspace_status(project_slug="roboco")
```
There are **no** agent-facing workspace tools. Workspaces are created and
cloned for you by the orchestrator (`WorkspaceService`) before your
container starts. You never `ensure`, `clone`, or `checkout` a workspace
by hand — your repo is already on disk at the path below, and the gateway
verbs (`i_will_work_on`, `claim_review`, ...) check out the right branch.
## Workspace Resolution
@@ -84,6 +76,7 @@ HTTPS repositories require a GitHub PAT configured on the project:
- **Token configured**: Auto-clone works, git operations succeed
- **Token missing**: Error "Project requires a git token for HTTPS repositories"
**If you see this error**: Contact your PM to configure the project's git token.
PMs use `roboco_project_update(slug, git_token="...")` to set credentials.
**If you see this error**: Contact your PM. The project's git token is
configured by a human in the control panel (project settings) — it is not
an agent tool. The token is encrypted at rest and never exposed to your
container; the orchestrator injects it into git operations for you.