### Task Queue Entry (Planner) JSON

Source: https://github.com/marv1nnnnn/rooroo/blob/main/README.md

Example structure for a task entry in `.rooroo/queue.jsonl` generated by the `rooroo-planner`. Each line is a JSON object representing a sub-task derived from a parent plan.

```JSON
{"taskId": "ROO#SUB_parent_S001_setup_database", "parentTaskId": "ROO#PLAN_project_init_123", "suggested_mode": "rooroo-developer", "context_file_path": ".rooroo/tasks/ROO#SUB_parent_S001_setup_database/context.md", "goal_for_expert": "Set up the initial database schema as per specs in context. User spec at 'project_docs/db_schema.md'."}
```

--------------------------------

### Activity Log Entry (Queue Dispatch) JSON

Source: https://github.com/marv1nnnnn/rooroo/blob/main/README.md

Example structure for a log entry in `.rooroo/logs/activity.jsonl` indicating that the `rooroo-navigator` has dispatched a task to a specific expert agent. Includes task ID, agent, severity, and dispatch details.

```JSON
{"timestamp": "2024-07-25T10:00:05Z", "agent_slug": "rooroo-navigator", "severity": "INFO", "task_id": "ROO#SUB_parent_S001_setup_database", "event_type": "QUEUE_DISPATCH", "details": {"message": "Dispatching to rooroo-developer with goal: Set up the initial database schema..."}}
```

--------------------------------

### Activity Log Entry (Planner Report Done) JSON

Source: https://github.com/marv1nnnnn/rooroo/blob/main/README.md

Example structure for a log entry in `.rooroo/logs/activity.jsonl` reporting successful completion of a planning task by the `rooroo-planner`. Includes status, a summary message, and references to plan artifacts.

```JSON
{"timestamp": "2024-07-25T09:55:00Z", "agent_slug": "rooroo-planner", "severity": "INFO", "task_id": "ROO#PLAN_project_init_123", "event_type": "EXPERT_REPORT", "details": {"status": "Done", "message": "Planning complete. Generated 5 sub-tasks."}, "output_references": [".rooroo/plans/ROO#PLAN_project_init_123_plan_overview.md"]}
```

--------------------------------

### Task Queue Entry (Navigator Temp) JSON

Source: https://github.com/marv1nnnnn/rooroo/blob/main/README.md

Example structure for a temporary task entry in `.rooroo/queue.jsonl` generated by the `Rooroo Navigator` for direct actions. These tasks typically lack a `parentTaskId` and use a `ROO#TEMP_` prefix.

```JSON
{"taskId": "ROO#TEMP_20240101130000_update_readme", "suggested_mode": "rooroo-documenter", "context_file_path": ".rooroo/tasks/ROO#TEMP_20240101130000_update_readme/context.md", "goal_for_expert": "Update the README.md (located at 'README.md') with the latest version number and features."}
```

--------------------------------

### Activity Log Entry (Expert Report Failed) JSON

Source: https://github.com/marv1nnnnn/rooroo/blob/main/README.md

Example structure for a log entry in `.rooroo/logs/activity.jsonl` reporting failure of a task by an expert agent. Includes status, a failure message, and specific error details.

```JSON
{"timestamp": "2024-07-25T10:10:00Z", "agent_slug": "rooroo-navigator", "severity": "ERROR", "task_id": "ROO#SUB_parent_S002_api_integration", "event_type": "EXPERT_REPORT", "details": {"status": "Failed", "message": "API endpoint returned 503.", "error_details": "Connection timed out after 3 retries to foobar.com/api."}}
```

--------------------------------

### Activity Log Entry (Expert Report Done) JSON

Source: https://github.com/marv1nnnnn/rooroo/blob/main/README.md

Example structure for a log entry in `.rooroo/logs/activity.jsonl` reporting successful completion of a task by an expert agent. Includes status, a completion message, and references to generated output files.

```JSON
{"timestamp": "2024-07-25T10:05:00Z", "agent_slug": "rooroo-developer", "severity": "INFO", "task_id": "ROO#SUB_parent_S001_setup_database", "event_type": "EXPERT_REPORT", "details": {"status": "Done", "message": "Database schema created."}, "output_references": [".rooroo/tasks/ROO#SUB_parent_S001_setup_database/schema.sql"]}
```

--------------------------------

### Rooroo Project Directory Structure v0.5.5

Source: https://github.com/marv1nnnnn/rooroo/blob/main/README.md

Illustrates the standard directory layout for a Rooroo project as of version 0.5.5, highlighting the core `.rooroo` operational directory and its subdirectories for queues, logs, tasks, plans, and brainstorming. It shows examples of task-specific directories and artifacts stored within them.

```plaintext
<Project Root>/\n├── .rooroo/                  # Core rooroo operational directory\n│   ├── queue.jsonl           # Pending Tasks (JSON objects, one per line, ROO# IDs, strictly parsable)\n│   ├── logs/\n│   │   └── activity.jsonl    # Activity Log (JSON objects, one per line, written by Navigator with escaped JSON)\n│   ├── tasks/                # Directory for all task-specific data\n│   │   ├── ROO#PLAN_20240101120000_initial_project/ # Example Planner Task Directory\n│   │   │   └── context.md      # Briefing FOR the Planner for this planning task\n│   │   ├── ROO#SUB_initial_project_S001/ # Example Sub-Task Directory (ROO#SUB_... ID from Planner)\n│   │   │   ├── context.md      # Task briefing FOR the expert (Created by Rooroo Planner)\n│   │   │   ├── feature_component.py # Example artifact directly in task folder\n│   │   │   └── data_analysis_report.md # Another example artifact\n│   │   ├── ROO#TEMP_20240101130000_fix_login/ # Example Temp Task Directory (ROO#TEMP_... ID from Navigator)\n│   │   │   ├── context.md      # Task briefing FOR the expert (Created by Navigator for simple task)\n│   │   │   └── login_fix.diff    # Example artifact directly in task folder\n│   │   └── ...\n│   ├── plans/                # Optional: High-level plan overview documents from Rooroo Planner\n│   │   └── ROO#PLAN_20240101120000_initial_project_plan_overview.md\n│   └── brainstorming/        # Optional: Summaries from Rooroo Idea Sparker sessions\n│       └── brainstorm_summary_ROO#IDEA_20240101140000.md\n│\n└── src/                      # Example source code directory (Potentially modified by Rooroo Developer)\n    └── ...
```

--------------------------------

### Example Agent Output Envelope (JSON)

Source: https://github.com/marv1nnnnn/rooroo/blob/main/changelog.md

This JSON structure represents the new standardized 'Output Envelope' format used by agents (like rooroo-planner, rooroo-developer) to report their status, messages, and paths to generated artifacts back to the Rooroo Navigator. This replaces the previous method of writing state files.

```json
{"status": "Done", "message": "...", "output_artifact_paths": [...]}
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.