Current Scope

Current Scope

Queenshift is strongest when the task is explicit, file-named, and bounded.

Best Current Use Cases

These are the calmer current families:

1. small named-file updates
2. bounded source-and-test pairs
3. bounded docs-and-source sync
4. artifact-backed review and incident follow-up
5. calm first-run demos in a disposable repo

Shipped And Experimental Engines

1. swarmengine is the shipped bounded engine.
2. queenbee is experimental.
3. the existence of queenbee does not imply a default-engine switch.

What Queenshift Currently Supports

Queenshift currently supports:

1. a bounded coding CLI with explicit review, replay, and incident surfaces
2. a public implementation surface behind a governance-first architecture note
3. a more structured first-run path than earlier command-driven setup

What Is Out Of Scope For This Stage

Queenshift does not currently support:

1. broad general-use autonomous coding
2. open-ended repo-wide refactors
3. arbitrary medium or large repo dominance
4. broad packaged cross-platform parity
5. queenbee as the shipped public engine

Current Install Status

The current public install story is still bounded:

1. the simplest supported first-time install surface today is still the local Windows bundle
2. the checked-out repo path is still a contributor or evaluator path
3. the public product command is queenshift

Read the install docs here:

1. https://github.com/Vatsalc26/queenshift-cli/blob/main/docs/install.md
2. https://github.com/Vatsalc26/queenshift-cli/blob/main/QUICKSTART.md

Evidence And Task Families

For the live and experimental reading:

1. Evidence summary: https://github.com/Vatsalc26/queenshift-cli/blob/main/docs/evidence.md
2. Task families: https://github.com/Vatsalc26/queenshift-cli/blob/main/docs/task-families.md