Business & Operations

[QA Method] Session-based exploratory testing: SBTM charters, heuristics (CRISP/SFDPOT), tours, session notes, debrief.

[QA Method] Triangulate an oracle against docs + live + source code, auto-apply confirmed changes, and reconcile test-case citations. Two axes: bl (business-logic.md invariants) and ecl (e-commerce-edge-cases-library.md sections). Delegates the live axis to qa-testing-expert; runs triangulation via ba-system-analyzer.

[Testing] Postman MCP collections — create, configure, verify, and export collections with proper variables, auth, and endpoints

Review task publication readiness through ten semantic dimensions, ordinary metadata revision or read-only archived review, and four typed exits.

Review one approved active-task Delivery slice through a fresh semantic gate and five minimal typed exits.

Review controlled contract wording through fixed change-request, planning-artifact, or explicit-path scope, semantic revision and classification, deterministic evidence, and typed exits.

Reconcile one exact active-task and evolved-base pair through a semantic impact review, controlled integration evidence, and six typed exits.

Qualify whether a proposed implementation mechanism can carry the required business authority without delegating it to OS, kernel, process, or descriptor primitives.

Merge one Ready task PR through a semantic live gate, or request an independent read-only review of an exact completed archive.

Maintain one traceable Requirements, Design, and Test repository authority through semantic profiles.

Create or exactly reuse a reviewed issue workspace and Trellis task through an AI-owned semantic gate, ephemeral scoped confirmation, deterministic execution, and four typed exits.

Create a reviewed Trellis task work commit after Phase 2, including finding-fix and revision commits, with exact staging and fresh evidence.

Approve current task planning through one AI-owned semantic review, compact private evidence, and four minimal typed exits.

Review task publication readiness through ten semantic dimensions, ordinary metadata revision or read-only archived review, and four typed exits.

Review one approved active-task Delivery slice through a fresh semantic gate and five minimal typed exits.

Review controlled contract wording through fixed change-request, planning-artifact, or explicit-path scope, semantic revision and classification, deterministic evidence, and typed exits.

Reconcile one exact active-task and evolved-base pair through a semantic impact review, controlled integration evidence, and six typed exits.

Qualify whether a proposed implementation mechanism can carry the required business authority without delegating it to OS, kernel, process, or descriptor primitives.

Merge one Ready task PR through a semantic live gate, or request an independent read-only review of an exact completed archive.

Maintain one traceable Requirements, Design, and Test repository authority through semantic profiles.

Create or exactly reuse a reviewed issue workspace and Trellis task through an AI-owned semantic gate, ephemeral scoped confirmation, deterministic execution, and four typed exits.

Create a reviewed Trellis task work commit after Phase 2, including finding-fix and revision commits, with exact staging and fresh evidence.

Approve current task planning through one AI-owned semantic review, compact private evidence, and four minimal typed exits.

Prepare and publish an official castbox/guru-trellis version through the repository-private two-stage release contract without joining the public Guru Team extension inventory.