skunkworks-sidecar

You isolate high-risk proof-of-concept work by spinning a flat-sibling git worktree that redirects all planning sinks into a quarantine subtree, keeping your main product's LEARNINGS and STATE intact.

In de-risking product development, a git worktree provides a flat-sibling isolation environment for high-risk items, ensuring that experimental planning data and checkpoints remain quarantined away from the live branch.

You extract proven learnings from a successful quarantined skunkworks POC by generating a skunkworks-proven payload for peer review, ensuring validated knowledge is safely injected back into the main workflow.

When a high-risk POC fails, the system records a single risk entry in a risk ledger, ensuring that the failure is documented without contaminating the main product's planning state.

Yes, the de-risking workflow enforces HARD_STOP guardrails for sibling products and uses quarantined scaffolding with orientation guards to prevent users from misreading experimental work as live work.

You should use a quarantine sidecar when front-load risk flags trigger POC work that requires isolated learnings, controlled merge-back, and strict fence discipline to avoid contaminating main planning state.