Know if the milestone lands, from the documents themselves.

Every document says who has it, when it is due, its status and its review. Live views gather any set into a board, a table or a timeline, and the progress view draws a burn-up toward your target date from the recorded status history.

Start free Open the Alpha milestone

Saltmarrow is a sample project: its studio, team and game are fictional.

Every document says who has it, by when, and where it stands

Give a document an assignee and a due date, and move its status from draft to in review to done. Ask for a review, and the workspace’s owners and admins approve it or send it back with a note. Label a link blocks or depends on and it becomes a blocker, drawn on the map with an arrow toward the document that waits. Every status change is recorded with who and when.

Assign a document and the person is notified
Group any set into a board by status, and drag a card to change it
Request a review; it is approved or sent back with a note
Typed properties such as priority, estimate and sprint, from a preset

What it does not do Status history starts on 29 September 2026: the burn-up does not guess the pace before then. A review goes to the workspace’s owners and admins; you do not pick a named reviewer.

Nodary’s progress view for Saltmarrow’s Alpha milestone: 6 of 19 documents finished, today’s statuses in one bar (done, in review, blocked, draft), the burn-up toward the 12 February 2027 target with the verdict still too early to tell, and the documents still to finish, the late ones first, each with who has it.

Cut the vertical slice to its budget

In a list or table view, sort features by priority and set a cut line: after a number of documents, or where their estimates pass a budget in days or points. What falls below the line is cut, dimmed but still readable. Drag the line or move it with the arrow keys, and the budget follows it.

A budget on any number property: days, points, hours
The line reads what it holds against the budget, and how many are cut
Shared pages, print and Markdown say where the line falls

What it does not do The line follows the view’s order: a smaller feature further down is never pulled above the line to fill the gap.

Title	Priority	Estimate (days)	Assignee
Core loop	1	6	Sanna Lindqvist
Harvest economy	2	12	Sanna Lindqvist
Tide clock and storms	3	9	Sanna Lindqvist
Co-op roles and revives	4	14	Sanna Lindqvist
Cut line: 41 of 45 days, 4 cut
Drop tables	5	5	Sanna Lindqvist
Crafting recipes	6	8	Sanna Lindqvist
Tide moth	7	7	Idris Okafor
The leaning lighthouse	8	10	Sanna Lindqvist

Drag the cut line, or focus it and use the arrow keys, to move it.

Roadmaps and chronologies on a timeline

The timeline view places each document by its due date, a date property or a number such as an in-world year. With an end, a document becomes a bar; without one, a milestone. Lanes split by status or by a choice property, and dragging a bar saves its new dates.

A roadmap by due date, or a lore chronology by year
Drag along the axis, or press Alt with the arrow keys
Documents without a date are listed under the axis, never hidden

What it does not do A timeline does not schedule: moving one document never shifts the ones that depend on it.

Saltmarrow’s world chronology as a live timeline from year -400 to 300: the drowned archive and the leaning lighthouse in the archive city lane, the Drowned Archivist in the Drowning lane, the tide calendar, Marrowstead and the factions of the flats in the salt years lane, and the documents with no in-world year listed below. — The same view places production documents by due date for a roadmap.

See who changed what, and when

The activity feed records edits, status changes, assignments, owners, due dates, moves, renames, reviews requested and decided, picture decisions, comments, and documents created, deleted or restored, newest first. Owners and admins see the workspace’s feed on the home page, and every member sees their own in their profile.

Each entry says who did what, to which document, and when
Click a teammate who is online to join them, double-click to follow
Agents read the same events to write a weekly summary

What it does not do Changes to custom properties are not in the feed, and the workspace feed on the home page is shown to owners and admins only.

The Recent activity feed on the Saltmarrow studio’s home in Nodary: Maëlle Rocher, Sanna Lindqvist, Idris Okafor and Tomás Ferreira editing Playtest notes, the tide calendar, the harvest economy, the Drowned Archivist and the core loop, newest first, beside a panel on how each project is doing.

What changed since your last visit

Open a document others changed since you last read it, and a note above it says what changed and who did it. One click opens the history on the version you saw, compared with now, the changed words marked. Your own edits are never presented to you as news.

Typing in a shared document saves versions, credited to whoever typed
Restore one block, or a whole version, from the history
Agents ask recent_changes what moved this week

What it does not do The note compares saved versions: if every version kept is newer than your last visit, it says so instead of guessing.

The tide calendar open in Nodary after Sanna Lindqvist changed it: a note above the page says it changed since the last visit and by whom, and the version history beside it compares her save with now, with buttons to restore that block or the whole version.

Ask an agent whether the milestone lands

get_progress gives an agent the same burn-up in words and data: in scope, finished and left, the weekly pace, the landing date against your target, and what is left with links. list_stars filters by assignee, review, due date, lateness and blockers, recent_changes returns the week’s events, and update_stars or set_due_dates change many documents in one call, each change signed in your name.

Connect an agent

You askIs the Saltmarrow Alpha milestone on track for 12 February? List what is late, who has it, and what is blocked.

Tools it calls

get_progress
list_stars
recent_changes

Questions

How does the burn-up decide whether a milestone will land?

Scope is the documents in the view today, each counted from the day it was created. Finished means done or published, read from the recorded status history, and the pace comes from the last two weeks. Until a week of history exists the view says too early to tell, and it never projects from guesses.

Does the burn-up know when a document joined the milestone?

No. Tags and properties have no recorded history, so a document added to the set later still counts in scope from the day it was created. Statuses do have a history, from 29 September 2026.

Can I plan a vertical slice against a budget?

Yes. Give features a number property such as an estimate in days, sort a list or table view by priority, and set a cut line at a budget. Everything above the line fits, what passes the budget is cut, and moving the line updates the budget.

Does Nodary sync with Jira, Linear or GitHub?

No, there is no sync with Jira, Linear or GitHub today. Work lives as documents in Nodary, and agents connected over MCP can create up to 25 documents or change up to 50 in one call.

Who can approve a review?

Anyone who can edit a document can ask for a review. The workspace’s owners and admins are notified and decide: approve, or ask for changes with a note. The request and the decision both appear in the activity feed.

Is there time tracking or sprint planning?

There is no time tracking. Documents take typed properties, and a preset adds priority, an estimate and a sprint; views filter and sort by them, and a cut line can use the estimate as its budget.

Put the milestone on the same map as the work.

Start free with your team and add a live view to any document, or open the live demo first.