Skip to content

WIP

Purpose

Owns experimental, in-progress, and opt-in feature workflows under active development inside Snap Studio Pro.

This territory exists as an intentionally isolated sandbox for unstable or evolving editor systems that are not yet considered finalized architecture.

Owns

  • Experimental feature workflows
  • Prototype editor systems
  • In-progress production tooling
  • Opt-in feature experimentation
  • Unstable workflow research areas

Does NOT Own

  • Stable production architecture
  • Core preview lifecycle ownership
  • Rendering pipeline ownership
  • Shared infrastructure ownership
  • Guaranteed API/workflow stability

Allowed Dependencies

WIP systems are allowed more flexibility internally than production territories.

However, WIP should still avoid: - leaking unstable dependencies outward - tightly coupling experimental systems into stable workflows - mutating core architecture unnecessarily

Notes

This folder is intentionally less strict.

The purpose of WIP is: - experimentation - rapid iteration - workflow validation - feature exploration

Systems inside WIP may eventually: - graduate into stable production territories - be rewritten - be deleted entirely

That is expected.

The architectural goal is isolation, not perfection.

WIP systems should remain opt-in wherever practical and should avoid contaminating stable production systems until workflows are proven.

Future Candidates

  • Promote stable workflows into proper feature territories once architecture settles.
  • Keep experimental dependencies isolated.
  • Avoid allowing WIP systems to become hidden production dependencies.