Skip to content

REV-37: Specify stable team identity across async work - #15325

Draft
warp-agent-staging[bot] wants to merge 1 commit into
masterfrom
factory/rev-37-team-context-spec
Draft

REV-37: Specify stable team identity across async work#15325
warp-agent-staging[bot] wants to merge 1 commit into
masterfrom
factory/rev-37-team-context-spec

Conversation

@warp-agent-staging

Copy link
Copy Markdown
Contributor

Summary

  • Add the product contract for one immutable team identity per logical operation.
  • Add the technical design for sealed TeamContext construction, request-edge extraction, scoped spawn helpers, and Agent Mode owner snapshots.
  • Split implementation into foundation, Agent Mode/CLI, billing, catalog/policy, and scope-audit stages.
  • Map all twelve confirmed investigation risks to those stages.

Review focus

  • The recommended defaults for billing scope, workspace-global AI policy, and new-window-only team switching are marked as assumptions pending requester confirmation.
  • This PR contains specs only. It has no production code changes.

Jira: https://warp-dev-staging.atlassian.net/browse/REV-37
Origin: https://warpdev.slack.com/archives/C0BREN45G2D/p1787170237056799

Validation

  • Checked Markdown whitespace and balanced code fences.
  • Verified that only specs/REV-37/PRODUCT.md and specs/REV-37/TECH.md changed.

@warp-agent-staging

Copy link
Copy Markdown
Contributor Author

This PR was generated with Warp.

Comment @warp-factory on this PR to send it follow-up work.

View run View conversation View on Slack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants