Orchestrata Ultimate / RTM / 070-team-tools
RTM: 070-team-tools
Requirement to symbol to test rows for 070-team-tools: Team Tools Specification.
At a glance
| Item | Value |
|---|---|
| Requirement IDs | 157 |
Traced from src/ |
0 (0.0%) |
| Untraced | 157 |
Cited from tests/ |
0 (0.0%) |
Traced in src/ but not cited from tests/ |
0 |
Reading this matrix
This matrix lists each of the 157 requirement IDs of spec 070-team-tools with the src/ symbols that cite it and the tests that cite it. 0 of them (0.0%) have at least one citing symbol and 157 have none.
0 requirements are also cited from tests/, and 0 are traced in code but never named by a test. A test citation is a @traces on a test function; it shows intent to cover, not that the test runs or reaches the symbol.
Rows showing none in the symbols column are the gaps to close first. The densest untraced groups are REQ-070-* (157).
Requirement to symbols to tests
| Requirement | Symbols in src/ |
Tests citing it |
|---|---|---|
REQ-070-001 A Team entity SHALL conform to the team.json schema — id (UUID), name, slug,... |
none | none |
REQ-070-002 Team settings SHALL comprise allow_external_invites (default true), require_mfa... |
none | none |
REQ-070-003 Team quotas SHALL comprise max_members (1–10000, default 100), max_storage_gb... |
none | none |
REQ-070-004 A TeamMember entity SHALL conform to the team-member.json schema — id, team_id,... |
none | none |
REQ-070-005 A Role entity SHALL conform to the role.json schema — id, team_id, name,... |
none | none |
REQ-070-006 A Permission SHALL comprise a required action drawn from create, read, update,... |
none | none |
REQ-070-007 A CreateTeamRequest SHALL conform to the create-team-request.json schema — name... |
none | none |
REQ-070-008 A DeleteTeamRequest SHALL conform to the delete-team-request.json schema — team_id... |
none | none |
REQ-070-009 A TeamResponse SHALL carry the subject team, the array of its roles, the... |
none | none |
REQ-070-010 The Team Tools module SHALL expose both REST API endpoints and MCP tool interfaces for... |
none | none |
REQ-070-011 The Team Tools module SHALL provide TeamService orchestrating team operations through... |
none | none |
REQ-070-012 The team module SHALL persist its state in the teams, team_members, roles,... |
none | none |
REQ-070-013 Team creation SHALL follow the ordered flow: the API gateway validates the JWT and... |
none | none |
REQ-070-014 The TeamCreateTool shall create a new team with unique identifier, name, and slug. |
none | none |
REQ-070-015 The TeamCreateTool shall generate three default roles upon team creation: ADMIN,... |
none | none |
REQ-070-016 The TeamCreateTool shall assign the creator as the initial team administrator. |
none | none |
REQ-070-017 The TeamCreateTool shall support optional parent team assignment for hierarchical team... |
none | none |
REQ-070-018 The TeamCreateTool shall validate team slug uniqueness across the platform. |
none | none |
REQ-070-019 The TeamCreateTool shall enforce quota limits based on platform configuration. |
none | none |
REQ-070-020 The ADMIN role shall include: manage, create, read, update, delete, list, invite,... |
none | none |
REQ-070-021 The MEMBER role shall include: create, read, update, list permissions for team... |
none | none |
REQ-070-022 The VIEWER role shall include: read, list permissions for all team resources. |
none | none |
REQ-070-023 Team name must be 1-100 characters, matching pattern ^[\w\s\-]+$. |
none | none |
REQ-070-024 Team slug must be 3-50 characters, lowercase alphanumeric with hyphens, starting and... |
none | none |
REQ-070-025 Parent team ID must reference an existing active team. |
none | none |
REQ-070-026 Owner ID must reference an existing user or service account. |
none | none |
REQ-070-027 The TeamDeleteTool shall support soft delete with configurable recovery window... |
none | none |
REQ-070-028 The TeamDeleteTool shall support hard delete for immediate permanent removal. |
none | none |
REQ-070-029 The TeamDeleteTool shall optionally cascade deletion to team resources when enabled. |
none | none |
REQ-070-030 The TeamDeleteTool shall support member migration to another team. |
none | none |
REQ-070-031 The TeamDeleteTool shall create backup before deletion when enabled. |
none | none |
REQ-070-032 The TeamDeleteTool shall maintain complete audit trail of deletion operations. |
none | none |
REQ-070-033 Team deletion shall be blocked if active child teams exist (unless force flag is set). |
none | none |
REQ-070-034 Team deletion shall be blocked if resources are actively in use (unless force flag is... |
none | none |
REQ-070-035 Team deletion shall validate migration target team exists and has capacity. |
none | none |
REQ-070-036 Soft-deleted teams shall have their slug reserved during recovery window. |
none | none |
REQ-070-037 The system shall support updating team name, description, settings, and quotas. |
none | none |
REQ-070-038 The system shall support adding and removing parent team relationships. |
none | none |
REQ-070-039 The system shall support team suspension and reactivation. |
none | none |
REQ-070-040 The system shall support inviting users to teams with expiration tokens. |
none | none |
REQ-070-041 The system shall support role assignment and modification. |
none | none |
REQ-070-042 The system shall support bulk member operations. |
none | none |
REQ-070-043 The system shall enforce maximum team member quota. |
none | none |
REQ-070-044 The system shall support custom role creation within teams. |
none | none |
REQ-070-045 The system shall support role inheritance from parent roles. |
none | none |
REQ-070-046 The system shall support permission conflict resolution via role priority. |
none | none |
REQ-070-047 System roles shall not be modifiable or deletable. |
none | none |
REQ-070-048 The system SHALL reject a team-creation request whose name or slug violates its format... |
none | none |
REQ-070-049 The system SHALL fail a team-creation request with HTTP 404 when the referenced parent... |
none | none |
REQ-070-050 The system SHALL fail a team-deletion request with HTTP 404 when the team does not... |
none | none |
REQ-070-051 The system SHALL fail a team-deletion request with HTTP 404 when the migration target... |
none | none |
REQ-070-052 The system SHALL fail a membership operation with HTTP 409 when the user is already a... |
none | none |
REQ-070-053 The system SHALL fail a role operation with HTTP 403 when a system role would be... |
none | none |
REQ-070-101 Team creation SHALL complete in under 500 ms at p99 under normal load. |
none | none |
REQ-070-102 Team deletion SHALL complete in under 2 s at p99 under normal load. |
none | none |
REQ-070-103 Listing 1000 teams SHALL complete in under 1 s at p99 under normal load. |
none | none |
REQ-070-104 A permission check SHALL complete in under 50 ms at p99 for all requests. |
none | none |
REQ-070-105 Ten parallel team creations SHALL complete in under 5 s in total at peak load. |
none | none |
REQ-070-106 The platform SHALL support up to 10,000 teams per tenant as a per-tenant quota. |
none | none |
REQ-070-107 The platform SHALL support up to 10,000 members per team, configurable per team. |
none | none |
REQ-070-108 The platform SHALL support a role hierarchy of up to 5 parent-child levels. |
none | none |
REQ-070-109 The platform SHALL support cross-team membership of up to 100 teams per user. |
none | none |
REQ-070-110 The Team Tools service SHALL meet a 99.9% uptime SLA. |
none | none |
REQ-070-111 Planned maintenance SHALL consume less than 4 hours per month. |
none | none |
REQ-070-112 The recovery time objective SHALL be under 1 hour. |
none | none |
REQ-070-113 The recovery point objective SHALL be under 5 minutes. |
none | none |
REQ-070-114 All team operations SHALL emit structured logs carrying correlation IDs. |
none | none |
REQ-070-115 The service SHALL emit the metrics team_create_total, team_delete_total,... |
none | none |
REQ-070-116 Traces SHALL include the full permission evaluation path. |
none | none |
REQ-070-054 POST /api/v1/teams SHALL accept a bearer-token-authorized JSON body carrying name,... |
none | none |
REQ-070-055 DELETE /api/v1/teams/{team_id} SHALL accept a bearer-token-authorized JSON body... |
none | none |
REQ-070-056 TeamCreateTool.execute() SHALL accept name, slug, description,... |
none | none |
REQ-070-057 TeamDeleteTool.execute() SHALL accept team_id, delete_resources,... |
none | none |
REQ-070-058 Team creation and deletion SHALL require approval from a tenant administrator or a... |
none | none |
REQ-070-059 All team administrative operations SHALL be logged with a full audit trail for... |
none | none |
REQ-070-060 A team creation SHALL include a business justification and a resource allocation plan. |
none | none |
REQ-070-061 A change to team quotas or permissions SHALL require approval when its impact exceeds... |
none | none |
REQ-070-062 Team deletion SHALL require 30 days advance notice to all members and a migration plan... |
none | none |
REQ-070-063 Platform administrators SHALL be able to suspend a team for a security violation, with... |
none | none |
REQ-070-064 All team operations SHALL be logged with the acting user ID, timestamp, IP address and... |
none | none |
REQ-070-065 A role change SHALL trigger a compliance review for the privileged roles ADMIN,... |
none | none |
REQ-070-066 Data residency requirements SHALL be enforced for teams in regulated regions. |
none | none |
REQ-070-117 Audit logs SHALL be retained for 7 years per SOC2 requirements. |
none | none |
REQ-070-067 The system SHALL enforce the change-management approvals and review timelines above: a... |
none | none |
REQ-070-068 Deletion of a team with more than 100 members SHALL require a security review,... |
none | none |
REQ-070-069 The system SHALL require a confirmation and a support ticket reference for every... |
none | none |
REQ-070-070 Team operations SHALL take the acting user_id from the JWT issued by the... |
none | none |
REQ-070-071 The service SHALL emit team.created to the owner and administrators, team.updated... |
none | none |
REQ-070-072 Notifications SHALL be delivered by email for all events, by in-app notification for... |
none | none |
REQ-070-073 Team tools SHALL integrate with SPEC-060 (Resource Management) for resource ownership... |
none | none |
REQ-070-074 Every team operation SHALL emit a structured audit event carrying event_type,... |
none | none |
REQ-070-075 The service SHALL consume the JWT claims sub as the user ID for permission... |
none | none |
REQ-070-076 The service SHALL validate every request by extracting the JWT from the Authorization... |
none | none |
REQ-070-118 The service SHALL expose the metrics... |
none | none |
REQ-070-119 The service SHALL alert when the team creation rate exceeds 100 per hour, the deletion... |
none | none |
REQ-070-120 Team creation SHALL succeed for 100% of valid requests, measured as an error rate... |
none | none |
REQ-070-121 100% of teams SHALL have their ADMIN, MEMBER and VIEWER default roles created correctly. |
none | none |
REQ-070-122 Hierarchical role inheritance SHALL verify correctly in 100% of inheritance tests. |
none | none |
REQ-070-123 100% of soft deletions SHALL be recoverable within the 30-day window. |
none | none |
REQ-070-124 Team deletion SHALL lose zero member records during migration. |
none | none |
REQ-070-125 P99 team creation latency SHALL stay under 500 ms for 99.9% of requests. |
none | none |
REQ-070-126 P99 team deletion latency SHALL stay under 2 s for 99.9% of requests. |
none | none |
REQ-070-127 P99 permission check latency SHALL stay under 50 ms for 99.9% of checks. |
none | none |
REQ-070-128 Ten parallel team creations SHALL all complete successfully in under 5 s. |
none | none |
REQ-070-129 Simple database queries SHALL complete in under 100 ms for 99% of queries. |
none | none |
REQ-070-130 There SHALL be zero unauthorized team access or privilege escalation incidents. |
none | none |
REQ-070-131 100% of team operations SHALL be logged with complete metadata. |
none | none |
REQ-070-132 All role-based access control permission matrix tests SHALL pass. |
none | none |
REQ-070-133 The annual security audit SHALL report zero critical penetration-testing findings. |
none | none |
REQ-070-134 Audit log coverage SHALL be 100% for SOC2 and GDPR compliance readiness. |
none | none |
REQ-070-135 The service SHALL achieve 99.9% availability against its SLA. |
none | none |
REQ-070-136 Team configuration data SHALL achieve 99.999999999% (11 nines) durability. |
none | none |
REQ-070-137 Service restoration SHALL complete within 1 hour. |
none | none |
REQ-070-138 The data loss window SHALL not exceed 5 minutes. |
none | none |
REQ-070-139 100% of backups SHALL be restorable and SHALL be verified monthly. |
none | none |
REQ-070-140 100% of critical operations SHALL be monitored with alerts. |
none | none |
REQ-070-141 Fewer than 0.1% of team operations SHALL result in errors. |
none | none |
REQ-070-142 Team-related support tickets SHALL stay below 10 per 1000 teams per month. |
none | none |
REQ-070-143 Every endpoint SHALL carry complete API documentation with examples. |
none | none |
REQ-070-144 The team management module SHALL hold above 95% code coverage. |
none | none |
REQ-070-145 A team SHALL go from request to active in under 5 minutes. |
none | none |
REQ-070-146 An administrator SHALL be able to configure a basic team structure in under 30 minutes. |
none | none |
REQ-070-147 The team management UI SHALL hold an average satisfaction score above 4.5/5. |
none | none |
REQ-070-148 The API SHALL ship a complete OpenAPI 3.0 specification with working examples. |
none | none |
REQ-070-149 100% of errors SHALL include actionable resolution guidance. |
none | none |
REQ-070-150 100% of JWT validation through the auth service SHALL work correctly. |
none | none |
REQ-070-151 Notification delivery SHALL succeed for 99.5% of notifications. |
none | none |
REQ-070-152 100% of operations SHALL be logged to the audit system. |
none | none |
REQ-070-153 Resource ownership SHALL transfer without interruption during team operations. |
none | none |
REQ-070-154 Real-time metrics and alerting SHALL be fully operational. |
none | none |
REQ-070-077 The platform SHALL define the global roles SUPER_ADMIN with full platform access able... |
none | none |
REQ-070-078 Each team SHALL carry the team-level roles ADMIN at priority 100 for full team... |
none | none |
REQ-070-079 Child team roles SHALL inherit permissions from parent team roles, permission... |
none | none |
REQ-070-080 A permission check SHALL evaluate the user's direct role permissions, then the... |
none | none |
REQ-070-081 Team deletion SHALL cascade through the stated levels — team memberships soft-deleted... |
none | none |
REQ-070-082 Team deletion SHALL follow the ordered flow: validate the deletion prerequisites,... |
none | none |
REQ-070-083 The system SHALL enforce the access control matrix above — SUPER_ADMIN may perform... |
none | none |
REQ-070-084 Every API request SHALL carry a valid JWT token. |
none | none |
REQ-070-085 Authorization SHALL be enforced by role-based access control with explicit permission... |
none | none |
REQ-070-086 All team operations SHALL be audit-logged with the acting user, the timestamp and the... |
none | none |
REQ-070-087 The service SHALL rate-limit each user to 100 requests per minute. |
none | none |
REQ-070-088 All inputs SHALL be validated against their schemas. |
none | none |
REQ-070-089 Database access SHALL use parameterized queries only. |
none | none |
REQ-070-090 A team slug SHALL remain reserved for the duration of the soft-delete recovery window. |
none | none |
REQ-070-091 The TeamCreateTool SHALL be covered by unit tests TC-UT-001 through TC-UT-010... |
none | none |
REQ-070-092 The TeamDeleteTool SHALL be covered by unit tests TD-UT-001 through TD-UT-010... |
none | none |
REQ-070-093 The module SHALL be covered by integration tests TC-IT-001 through TC-IT-006... |
none | none |
REQ-070-094 The module SHALL be covered by security tests TC-ST-001 through TC-ST-006 exercising... |
none | none |
REQ-070-095 The module SHALL be covered by performance tests TC-PT-001 through TC-PT-005 asserting... |
none | none |
REQ-070-096 The module SHALL depend on orchestrata-core >=2.0.0 for core platform abstractions,... |
none | none |
REQ-070-097 The module SHALL run against PostgreSQL >=14.0 as the primary data store, Redis >=7.0... |
none | none |
REQ-070-098 The module SHALL be developed against pytest >=7.0.0, pytest-asyncio >=0.21.0,... |
none | none |
REQ-070-155 The module SHALL log all major operations at appropriate log levels, SHALL include... |
none | none |
REQ-070-156 The module SHALL expose operation duration histograms, request and error rate... |
none | none |
REQ-070-157 The module SHALL propagate traces across component boundaries, SHALL attach... |
none | none |
REQ-070-158 The module SHALL raise critical alerts on error rate spikes, performance degradation,... |
none | none |
REQ-070-159 The module SHALL provide an operational dashboard showing real-time system health,... |
none | none |