Use cases · Why Onnie

Project management

Projects with a Work spine — not board chaos

Onnie project management is a real Project room: Work items on a shared spine, a Calendar Timeline for the horizon, and Routines that keep status warm without the status meeting.

Projects · containerWork · spineTimeline · horizonRoutines · cadence

// who it's for

Small teamsshared project roomsSoloone operator, full spine

// friction

Boards without a project room go cold

Columns fill; the “project” is still a channel and a spreadsheet. Status lives in DMs. Agents help one person. Nobody can open one place and see the horizon.

// on onnie

A Project is the room. Work is the spine.

Stand up a Project (name, people, standing context). Put real Work on it — goal, focus, plan. Use Work Calendar Timeline when the horizon matters. Let Routines drop digests so the room is warm when you return.

This is not another Kanban hero. It is multi-party continuity — humans and agents — inside a project that actually holds residue.

01Projects02Work03Calendar · Timeline04Routines05Blueprints

// workflow on the os

How a project actually moves

Click each step. Every stage is a real surface — not a feature bullet.

Open the Project — not a channel

Projects group Work, artifacts, and people. Standing context stays with the room so agents don’t re-learn the initiative every morning.

Projects (in-app)Work

// a week in the project

Residue, not theater

MONProject focus set

Q3 launch Work opens with goal + focus. Timeline shows the week.

Projects · Work
TUE–WEDRoutine pulse

Morning routine drops digests on Work. Open loops without a stand-up.

Routines · Work
THUNeeds you

Judgment gate on the send list. Agents wait; the record stays shared.

Work · Agents
FRIHorizon clear

Timeline: done bars, next week ghost. Project room still warm.

Timeline · Project
NEXTSame room

No re-brief. Standing context + plan still on the Project.

Projects

// proof · work calendar timeline

See the project across the horizon

Work Calendar → Timeline (product DNA): sticky Work rail, day axis, parent/child bars, rollups, ghost routine runs, amber today line. Filtered to the Project.

MonthWeekTimeline
Jul 14 – Jul 27Project · Studio · Q3 launchToday
LiveExecutingDoneGhost / routine│ today
Work
14
15
16
17
18
19
20
21
22
23
24
25
26
27
Messaging kit
Brief lock
Asset list
Stakeholder digest
Design pass
Morning project pulse
Kickoff notes
Parent rollup spans dated children · ghost bar is the routine that keeps the project warm · today line is judgment, not decoration.

// nearby domains

Same OS, different residue

Other use cases that reuse Projects + Work — different jobs and proof objects.

Product development
Ship with humans + agents
Client work
Delivery rooms that actually close
Agency ops
Multi-client ops without tool soup

// faq

Common questions

Yes. Projects live as Work on a shared spine — goal, focus, plan, blockers, and digests — so the room sees progress without rebuilding context in every chat.

Put one real project on the spine

Create a Project, bind Work, open Timeline — let a Routine keep it warm.

Start freeSee Work Calendar →