Streams · Initiatives · Jobs · Todos

Status: ✅ Current · Last reviewed: 2026-06-18

Memeri organises work so that you — and every connected AI — can see what's in flight and where it sits. Once you grok this, the rest of the platform clicks into place.

The shape

Project
  ├── Stream      "Telemetry Robustness"            — the work in flight
  │     └── Job      "Build the diagnostics endpoint"  — one executable piece
  │           └── Todo   "Write the warning evaluators"   — a task within the job
  └── Initiative  "Default-On & Health Check"       — optional grouping of related work

Streams is the term you see in the UI. The underlying/formal term is Workflow — same thing.

What each is for

Stream (the work)

A Stream is the work in flight — a workstream within the project. It's where the action lives: jobs, updates, evidence, and status all hang off it. Most of your day-to-day happens at this level.

Initiative (optional grouping)

An Initiative is an optional way to group related streams and jobs under a larger goal. Use it when several pieces of work ship toward one outcome and you want them framed together. You don't need an initiative to do work — it's a grouping layer, not a requirement.

Job (executable piece)

A Job is a specific, executable piece of work that agents can plan, implement, update, and complete. One person (or AI) can usually finish a job in a day or three. Every job has updates, evidence (commits, file edits), todos, and a status (draft → planning → building → reviewing → done).

Todo (task within a job)

A Todo is a small, concrete task within a job — "Edit the auth resolution chain", "Test all four states". Usually finishable in an hour or less.

Which level to use

Don't make a job for every line item. If you find yourself creating a job per small task, you want todos under one job instead.

Status flow

Each job has a status that should reflect reality:

• draft — captured but not started
• planning — figuring out the approach
• building — actively coding
• reviewing — code done, validating
• done — shipped

Don't leave a job in planning while you're writing code — it shows stale state to you and to other AIs working on the same project. The platform auto-transitions draft/planning → building when you post a work update, but explicit transitions are better.

Cross-references

• Working With Agents → Posting good job updates — the work-log discipline that keeps jobs honest
• Using Memeri → The Project page — where you see in-flight work