Tangled Thistle · Atmosphere OS
Atmosphere is a system,
not a mood board.
Palette, florals, materials, lighting, budget and guest state go in. A run sheet, a floral brief, a budget you can defend and an executable vendor pack come out. Nothing is invented. Where a decision has not been declared, the plan stops and says so.
Boundary
A planning instrument, not a vendor contract. Costs are indicative bands rather than quotes; availability, minimums and lead times must be confirmed with each vendor. Where the suite cannot satisfy a constraint you have stated, it blocks and explains rather than guessing.
- Modules
- Seven
- Engines
- Deterministic
- Storage
- This browser only
- Export
- JSON · print packet
Section 01 · The evening
Every plan is an arc, not a checklist.
Arc Studio reads the whole night as one energy curve, and marks the single moment the room decides what kind of evening it is having.
- ArrivalThreshold, first drink, coats. Guests are still reading the room.
- SettleSeating and first course. Conversation finds its level.
- First liftToasts land. The room stops being an audience.
- The TurnLights drop, tempo shifts. Miss it and the night stays polite.
- PeakFloor is full. Every atmosphere decision is paying out, or it is not.
- ReleaseLast call and send-off. Load-out has already started behind the wall.
Section 02 · The suite
Seven modules, one continuous handoff.
Run them in order for a full build, or open a single module when a client only needs one answer. Each writes a handoff the next one can read.
Theme Atelier
Signature atmospheres built as complete design systems — palette psychology, florals, materials, lighting and spatial mood resolved together.
Open module
Moodboard-to-Plan
Client direction — a saved board, three photographs, one sentence — translated into layered plans and language a vendor can act on.
Open module
Floral Direction
Hero moments, volume strategy and seasonal reality, written into a brief a floral studio can quote from directly.
Open module
Budget-to-Atmosphere
Where the money actually shows in the room. Scenarios, sensitivity, and the decision briefs that defend atmosphere spend.
Open module
Guest Journey
Pressure-test guest states across the night — thresholds, friction points, and the first fix named for each one.
Open module
Arc Studio
The synthesiser. Evening energy arc, The Turn, run sheet and production brief assembled into one document.
Open module
Vendor Pack
The executable artefact — timeline, load-in, atmosphere priorities, constraints and contacts, ready to send.
Open moduleSection 03 · Suite contract
Nothing is assumed. Everything is declared.
Each module writes a handoff the next one reads. This is the live state of that chain, read from this browser. Where a module has not run, the contract says so rather than filling the gap with a guess.
- Declared
- 0of 7 modules
- Stale over 72h
- 0nothing ageing
- Waiting
- 7next: Theme Atelier
Empty on purpose
Nothing is generated until a module has run. Open Theme Atelier to declare an atmosphere, or load a demo inside any module — every handoff lights up here as it is written. No plan is invented on your behalf.
| Module | Produces | State | Last written |
|---|---|---|---|
| 01Theme Atelier | Palette, florals, materials, lighting and spatial mood, resolved together | Waiting | — |
| 02Moodboard-to-Plan | Client direction translated into layered plans and vendor language | Waiting | — |
| 03Floral Direction | Hero moments, volume strategy and a floral brief a studio can quote from | Waiting | — |
| 04Budget-to-Atmosphere | Scenarios, sensitivity and the decision briefs that protect atmosphere spend | Waiting | — |
| 05Guest Journey | Guest states across the night, with the first fix named for each | Waiting | — |
| 06Arc Studio | The energy arc, The Turn, the run sheet and the production brief | Waiting | — |
| 07Vendor Pack | Timeline, load-in, atmosphere priorities, constraints and contacts | Waiting | — |
Section 04 · Run control
Seven stages. Step, or let it run.
A full build is a run. Each stage does real work and reports what it produced. Where a stage cannot fit what you have declared, it stops and says why rather than guessing its way forward.
Theme Atelier
Not run yet — this is the next stage. Palette, florals, materials, lighting and spatial mood, resolved together.
Moodboard-to-Plan
Not run yet. Client direction translated into layered plans and vendor language.
Floral Direction
Not run yet. Hero moments, volume strategy and a floral brief a studio can quote from.
Budget-to-Atmosphere
Not run yet. Scenarios, sensitivity and the decision briefs that protect atmosphere spend.
Guest Journey
Not run yet. Guest states across the night, with the first fix named for each.
Arc Studio
Not run yet. The energy arc, The Turn, the run sheet and the production brief.
Vendor Pack
Not run yet. Timeline, load-in, atmosphere priorities, constraints and contacts.
Runs are local to this browser. Nothing is uploaded, and no stage is executed until you open it.
Section 05 · Standing library
Signature atmospheres, already resolved.
Seven finished design systems on the shelf. Start from one, or use them as the reference grammar when a client arrives with their own direction.
Local-first by design
Client work never leaves this browser.
Session data stays on this device. No account, no cloud sync, no embedded third-party dependencies. Every module exports clean JSON and a print-ready brief the moment you decide to hand something over.
Deterministic engines
Scoring across palette psychology, floral volume, budget sensitivity and guest pressure is rule-based, not generative. The same inputs produce the same brief every time — which is what makes it safe to send to a vendor.