Review and publish a session

Review a Building Task Builder Session in alterac.ai before turning its proposed Plans and draft tasks into project work. Publishing is explicit, all-or-nothing, and controlled by you in the website.

1. Open Task Builder for the project and select the Building session.
2. Review its readiness result, every proposed Plan, and every Standalone or assigned draft task.
3. Choose Edit on a draft detail page to change its type, title, Markdown, Mass or Weight, same-session Plan membership, labels, or same-session dependencies. Save and review the session again. Use the local AI conversation for proposed Plan definitions, order, metric exclusion, or scheduling changes.
4. When it is ready, choose the visible Publish action and confirm the prompt. Its full label reflects the session contents, such as Publish Plans and Tasks.

Expected result: when the complete session is ready, every proposed Plan and draft task becomes a normal project Plan or task together, preserving membership, and the session becomes Published history. Coding agent and Person drafts publish together in Backlog with their reviewed types, which are fixed after publication.

Open Task Builder for the project and select the Building session. Review the session summary, every proposed Plan's title, Markdown, labels and membership, every empty Plan, and each draft task’s task type, title, Markdown, Mass or Weight, labels, direct dependencies, Plan or Standalone state, and display order. Task type is shown with Standalone rows and with assigned rows while their Plan is expanded; collapsing a Plan keeps its summary compact. Plans begin expanded. When a session has more than one Plan, you can collapse individual Plan details or use Expand all Plans and Collapse all Plans to scan the grouped review; these controls do not change membership, readiness, or what will be published. Follow the draft navigation to inspect individual details.

On a Building draft’s detail page, choose Edit to change its type, title, Markdown, Mass or Weight, Plan membership, labels, and dependencies. Plan and dependency choices are limited to this session's drafts. Changing type clears size for re-estimation. Save before returning to review; unsaved changes are not included in publication. Edit draft content in the browser covers discard prompts, stale saves, and reload recovery. Proposed Plan definitions, display order, metric exclusion, and Sprint/Milestone assignments use the local AI conversation and CLI. Scheduling metadata remains read-only in the browser, and the draft metrics row is hidden. Building drafts are proposed work; they are not already project Plans or tasks.

When Sprints are enabled and a draft has saved Sprint membership, the Sprint field in its draft task metadata, assigned or Standalone row shows a linked Sprint number/title followed by (Planned), (Current), or (Complete). Sprint membership is independent of Plan membership, and drafts do not join the Sprint until the complete session is published. Review does not open, close, or edit a Sprint.

When Milestones are enabled, draft details and Plan-assigned or Standalone rows show a linked Milestone number and title when the target is accessible. The linked title ends with (Planned), (Current), or (Complete); Current maps the API's Started state. A Current target also shows a separate saved Correction or Scope change choice, or Intent not saved, without repeating the lifecycle. These facts help you review the assignment; a lifecycle label alone never authorizes publication. Plan, Sprint, and Milestone membership are independent, and saved draft intent does not change live scheduling scope.

The session shows authoritative publication readiness before you can publish. Errors block publication and must be fixed, such as missing required session information, invalid content, Mass, or Weight, unavailable labels, or a dependency reference or cycle that cannot be published safely. Both task types use these readiness rules; a Person draft does not block publication because of its type.

Mass or Weight is optional when saving and publishing. The publication confirmation reminds you to review missing estimates without blocking publication. Readiness warnings are also nonblocking: for example, an archived Building session can still be ready, while its published history will remain hidden from the usual view.

If a connected drafting tool has saved a Sprint target, that target must still be a future Planned Sprint in this project, with Sprints enabled. The person publishing also needs ordinary project membership or organization Owner/Admin access; standing platform-support access alone does not grant Sprint permissions. If eligibility changes, publication fails and preserves the Building session and all draft metadata.

Current or Complete Sprint targets and unavailable or cross-project targets block publication. Readiness at the bottom of the session identifies the affected draft. When Sprints are disabled, Sprint metadata and row references are hidden; saved membership that prevents publication still has a readiness error.

Use alterac-ai task-builder task set-sprint <DRAFT-ID> --sprint <SPRINT-NUMBER> --session <SESSION-NUMBER> to replace a stale target with another future Planned Sprint. Omit --sprint to clear membership, including when the target is unavailable or Sprints are disabled. The review website has no Sprint assignment controls; ask your local AI tool to refine the draft through the CLI, then review readiness again. Session output includes the current Sprint number, title, state, and stable identity, including JSON. Current or Complete targets (Started or Complete in current API output) must be replaced or cleared before publication. A failed replacement preserves the previous assignment. A project Team Lead can also re-enable Sprints in Project Settings. Publication checks eligibility again, so an earlier ready result or successful CLI assignment does not guarantee a later attempt will succeed.

If the session is no longer Building, you cannot change its drafts. Return to a current Building session in your local AI conversation. Correct draft type, title, Markdown, size, same-session Plan membership, labels, or same-session dependencies with Edit on its detail page. For proposed Plan definitions, order, metric exclusion, or scheduling changes, ask the AI tool to make the correction through the CLI and then review the session again.

A local AI tool can save optional Milestone intent through task-builder task set-milestone. The review website displays accessible target details and saved intent, with one session readiness area identifying the affected drafts and recovery. There is no Milestone editor in review; assignment and clearing use the Task Builder CLI. A Milestone target must be enabled, accessible, in this project, and Planned or Current (Started in API output). Complete targets cannot receive newly published tasks. The person publishing needs ordinary project membership or organization Owner/Admin access; standing platform-support access alone does not grant Milestone permissions.

A Current target requires saved explicit Correction or Scope change intent for the whole membership and estimate change. If a Planned target became Started, ask your AI tool to save explicit --milestone-change scope-change, another valid Current intent, or choose another target. Correction requires Team Lead authority and treats the published work as part of the opening plan, while preserving its real creation and completion times. Scope change adds it from publication time. Planned assignment and clearing reject a supplied Current classification.

Use the affected draft number and title in readiness to ask your AI tool to find its stable draft ID and replace the target, correct the saved choice, or clear both fields with task-builder task set-milestone <DRAFT-ID> --session <SESSION-NUMBER> and no target or intent options. Unavailable, deleted, cross-project, or inaccessible targets have no target link or protected title. When Milestones are disabled, their metadata and links are hidden while saved-target blockers remain in session readiness. Clearing is available after disablement or target unavailability without enabling Milestones or changing live membership; failed replacement preserves the existing assignment. A Team Lead can also re-enable Milestones in Project Settings. See Recover saved Milestone intent.

Opening Publish refreshes authoritative readiness. If lifecycle, permissions, settings, or membership versions change after review, publication can still be rejected. The session then shows fresh server validation and recovery guidance and preserves every Building draft and saved assignment. Save explicit Current intent through Task Builder before retrying a Planned-to-Current target; an earlier Planned label never supplies that choice.

When readiness is clear and you want every proposed Plan and draft task in the session to become project work, choose the contextual Publish action and confirm the prompt. If drafts have no Mass or Weight, or no labels while the project has labels available, the confirmation reminds you to review those details; these reminders do not block your decision. It never selects only part of the session. This is the publication boundary: the confirmation can be canceled, and no local AI tool or CLI command can make this decision for you.

Publication creates the complete reviewed set of Plans and tasks in one operation, including empty Plans and Standalone tasks. Valid saved Sprint and Milestone memberships are applied independently of Plan membership; Current Milestone changes use the saved valid intent. It does not publish a selected subset or partially retry part of a session. If publication fails, no project Plans, tasks, scheduling memberships, or Milestone history changes are created, and the session stays Building with its draft metadata so you can retry after addressing the problem.

After publication, the session becomes Published history. Its proposed Plans create normal project Plans, and its draft tasks create normal project tasks while keeping Plan membership and direct dependencies. Manage those published records through their normal areas in alterac.ai, including Plans, task review, and execution.

The Published session is an immutable record of what crossed the boundary. To change published work, use normal task-management surfaces rather than trying to edit or republish the Task Builder Session.