Project#
A registered definition of repositories, setup, checks, model/tool guidance and access policy. Use the exact project name returned by your environment.
Task and workflow#
The unit connecting a request, plan versions, operations, decisions, evidence and PR links. A workflow task follows Quick (one coding plan) or Full (requirements, design, then a coding plan). Direct tasks (chat: in Slack, agentx_start_task in a coding tool) are a separate path without plan approvals.
Plan and owner decision#
A saved document describes approved scope and approach. Its version and digest identify what the owner decided. A revised document requires a current decision. Only the task owner decides; teammates in the channel can reply, comment and suggest.
Task page#
The authenticated web page for one task, linked from every approval card. The owner answers the plan’s decisions and approves or requests changes there; teammates comment and suggest. Task page guide →
Workspace#
The remote project files and task context in your AWS account. Follow-ups can reuse it; workspace closure and task-record retention are different.
Candidate#
The identified code version being checked or reviewed. Results for one candidate do not qualify a changed candidate.
Checks and AI review#
Named command results are evidence of those checks in their recorded environment. Separate code and security AI reviews start once the checks pass; only problems the change introduced block. Review reports are attributed findings, not a guarantee of correctness.
Pull request and feedback#
GitHub hosts the proposed change, repository CI, comments and merge decision. Rovara Code opens a draft PR of exactly the checked and reviewed code, follows it through signed GitHub events, and proposes feedback fixes for owner approval.