mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00

Files

T

Renn F f48106cbb6 docs: reflow hard-wrapped prose to one line per paragraph

Markdown and editors soft-wrap on their own, so the manual ~75-char line
breaks across the docs added nothing but noise. Join wrapped prose, list
items, and paragraphs into single lines across 67 docs — README, CLAUDE.md,
deployment, usage, the RAG knowledge base, and the agent role prompts.
Whitespace-only: code fences, tables, and blockquote alerts are byte-identical
and the change is token-verified (no content altered). Applied with a
deterministic reflow tool (committed separately).

Also lands two doc edits that were awaiting commit: the measured under-load
resource numbers in usage.md and the pr_reviewer additions to the
org-structure RAG doc.

2026-06-16 23:18:55 +02:00

2.6 KiB

Raw Blame History

Task Model

Core Fields

Field	Type	Description
`id`	UUID	Primary key
`title`	String	Task title
`description`	Text	Detailed description
`acceptance_criteria`	Array	How we know it's done
`acceptance_criteria_ids`	Array	Stable per-criterion id (1:1 with `acceptance_criteria`)
`parent_ac_refs`	Array	Parent AC ids this subtask is responsible for
`status`	Enum	Lifecycle state
`priority`	Int	0=P0 (highest) to 3=P3
`team`	Enum	backend, frontend, ux_ui

Acceptance-Criteria Tracking

Every task's acceptance_criteria get a parallel list of stable acceptance_criteria_ids — one id per criterion, generated automatically when a task is created. The ids are stable across edits, so other tasks can reference a specific criterion.

When a parent task is decomposed, each subtask declares which parent criteria it covers in parent_ac_refs (set from the covers_parent_criteria argument to delegate). That child→parent link is what lets the org guarantee a decomposition actually covers the parent's full intent. See docs/rag/workflows/task-planning.md for the coverage gates and the PM's coverage briefing.

Task Types

Type	Description
`code`	Development work
`documentation`	Writing docs
`research`	Investigation
`planning`	Task breakdown
`design`	UX/UI design
`administrative`	Admin work

Git Fields

Field	Description
`project_id`	Associated project (required)
`branch_name`	Git branch for task
`work_session_id`	Active work session
`pr_number`	PR number
`pr_url`	Full PR URL
`docs_complete`	Documenter finished
`pr_created`	Developer created PR
`commits`	Linked commits

Assignment Fields

Field	Description
`created_by`	Agent who created
`assigned_to`	Currently assigned
`parent_task_id`	Parent for subtasks
`dependency_ids`	Blocking tasks

Context Fields

Field	Description
`plan`	Implementation plan
`quick_context`	2-3 sentence summary
`proactive_context`	RAG context at claim
`dev_notes`	Developer notes
`qa_notes`	QA feedback

Timestamps

Field	Description
`claimed_at`	When claimed
`started_at`	When started
`completed_at`	When completed
`target_date`	Target date

Indexes

ix_tasks_team_status - Team + Status queries
ix_tasks_assigned_status - Assignee + Status
ix_tasks_project_status - Project + Status

2.6 KiB Raw Blame History