A task is a note that wants to be done

Most tools treat tasks and notes as different species that happen to live in the same app. Notes are where you think; tasks are where you track. tentus doesn't draw that line as sharply, because in practice a task is usually just a note with a deadline attached — a commitment that surfaced while you were thinking about something else.

Subtasks, without a project-management skin

A task can break down into smaller ones — the same "I'll follow up with Sarah, but first I need the deck and the pricing numbers" structure a real to-do list actually has. Each top-level task shows its own progress ("2/3 done"), collapses and expands, and lets you add a subtask inline without leaving the row. What it deliberately doesn't do is nest a third level deep, or grow into a Gantt chart. tentus isn't trying to replace a project-management tool; it's trying to hold the tasks that came out of your own notes.

Assigning without asking you to invite a teammate

Sharing a task with someone else didn't need a full workspace-membership system with invites and roles — that's infrastructure for a team product, and tentus is built for the person doing the thinking, not the org chart around them. Instead, assignment reuses the same lightweight, email-based sharing model notes already had: you grant access by email, it attaches to their account the moment they have one, and they get exactly the access the situation calls for — enough to see the task and mark it done, not enough to rename it, reprioritize it, or delete it out from under you.

The honest trade-off

This isn't a multiplayer task system, and we didn't build it to pretend to be one. It's a single owner's task list with a narrow, deliberate door for looping someone else in on one item at a time. If your team needs shared ownership, sprint boards, and permission tiers, that's a different product — tentus stays focused on the person whose second brain this actually is.