NoumenaDocs
/
Documentation
Start here
Noumena Code documentationGetting started
Web app
Repositories and source browsingCode browser and historySearch
Workflows
Issue-driven workStack reviewsScoped workspacesCloud sessions
Source control
Source control in Noumena CodeJJ and SmartlogSapling and stacksGit and GitHub-compatible workflows
Account
Organizations, members, and teamsProfile and developer accessUsage and billing
CLI
CLI quickstartBuild the CLIAuthenticate the CLIConfigure models and endpointsCLI reference
Security
Security and safe operation
Reference
Compatibility and product boundariesTroubleshooting

Stack reviews

Review dependency-aware source changes without flattening the work into one opaque diff.

Create a stack review

Open a repository’s Stack Reviews page and choose New stack review. Select:

  • the base branch or bookmark;
  • the comparison branch or bookmark;
  • a title and description;
  • linked issues and suggested reviewers, when available.

The creation flow previews the commit count and changed-file count before allowing submission. If the selected refs have no real difference, choose another comparison range instead of creating an empty review.

Review a stack

Use the stack tabs to move between:

  • overview and review state;
  • commits in order;
  • changed files and diffs;
  • checks and conflicts;
  • timeline and linked issues;
  • merge or landing controls when the stack is eligible.

Review the stack as a unit, then inspect individual commits when the order or boundary matters. A later commit can depend on an earlier one even when the final diff looks correct in isolation.

Review decisions

The review state communicates whether work is open, draft, approved, changes requested, or closed. A review decision is not the same as a successful check: both the human decision and automated checks must be considered before landing.

Agent-produced changes

For agent work, review the issue context, workspace boundary, source diff, checks, and proposed landing action together. If a change is wrong, request a focused correction against the same stack rather than starting a disconnected replacement review.