skills.rest
Growthub-ai
Growthub-aiOFFICIAL
Explore all skills by this author →
GitHub

governed-workspace-mutation

Enforce two canonical workspace mutation endpoints with 422 validation.

48|12|Updated Mar 27, 2026
Search Tags:#governance#api-security#runtime-verification#governed-workspace#workspace-mutation#contract-card
One-click install
npx skills add https://github.com/Growthub-ai/growthub-local --skill governed-workspace-mutation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: governed-workspace-mutation
Source: https://github.com/Growthub-ai/growthub-local/tree/main/.claude/skills/oss-investigative-architecture/skills/governed-workspace-mutation
Command: npx skills add https://github.com/Growthub-ai/growthub-local --skill governed-workspace-mutation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routing to a runtime-verified contract card that governs two canonical workspace mutation calls ensures safe and auditable changes to workspace configuration.

Core Features & Use Cases

  • Enforces strict mutation boundaries: only PATCH /api/workspace and POST /api/workspace/sandbox-run are allowed.
  • Validates mutation requests against the canonical contract, returning violations with 422 when breached.
  • Provides a reference anchor for all harnesses and forks to align on governance rules and history lineage.

Quick Start

Review the canonical workspace mutation contract before issuing any mutation requests and perform only the two allowed calls within the defined guardrails.

Frequently Asked Questions about governed-workspace-mutation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce strict workspace mutation boundaries in my API?▼

Workspace mutation boundaries are enforced by validating requests against a runtime-verified contract card, allowing only PATCH /api/workspace and POST /api/workspace/sandbox-run calls while blocking unauthorized state mutations.

What happens when a workspace mutation request violates the governance contract?▼

When a workspace mutation request breaches the governance contract, the validation layer blocks the operation and returns a 422 response to prevent invalid state changes and maintain run-history lineage.

How does runtime contract verification work for API workspace mutations?▼

Runtime contract verification validates mutation requests against a canonical contract card at execution time, ensuring only authorized workspace mutations pass while unauthorized attempts are intercepted before state modification.

Can I prevent non-mutation read operations from modifying workspace state?▼

Yes, the governance contract defines a strict boundary that prevents non-mutation reads from modifying state by restricting mutations to only PATCH /api/workspace and POST /api/workspace/sandbox-run calls.

Do I need a contract card to govern workspace sandbox-run requests?▼

Yes, a runtime-verified contract card is required to govern workspace sandbox-run requests, serving as the validation reference that ensures mutation calls comply with canonical governance rules before execution.

Related Skills

Explore More Software Engineering Skills→
MRiabovMRiabov

runtime-script-contract

Define canonical runtime contracts for benchmark_script.py and solution_script.py imports and bindings.

Community
Intermediate
gujiachun-rainbowgujiachun-rainbow
8

Tracing Knowledge Lineages

Trace current ideas and decisions back to their historical origins.

Community
Intermediate
Agent-FieldAgent-Field
969

swe-af

Coordinate autonomous AI agents to plan, code, and verify software builds.

Official
Advanced
cuenobicuenobi

release-readiness-check

Validate architecture boundaries, API contracts, security posture, and operational readiness for release.

Community
Intermediate