Describe your people and teams. Turn the conversation into a model you can inspect in Scenario Studio, without signing up to Orgonaut first.
Private V2 preview. Studio is read-only today.
Initial testing is on desktop. Cloud/mobile registration is still being verified.
Visual editing and AI context sharing are later gated stages.
Allocation shown.
FTE stays unknown.
Position seat: not supplied
Reporting relationship: not supplied
Start with a partial model. Missing information stays missing, so you can ask useful questions without filling every field first.
Explain the teams you know, paste existing org data, or start with a small fictional example. Guest modelling needs no account.
Open a compatible MCP Apps panel. Pan, zoom, select a placement and inspect its recorded allocation. People can have more than one membership.
Use the existing guest scenario tools to keep the original intact. Read the saved model before describing what changed; an old chart is not authoritative.
After you have private preview access, select Orgonaut Scenario Studio V2 in a new ChatGPT conversation and run these prompts in order.
Create a temporary fictional organisation with an Engineering department, Team A and Team B. Alex is in Team A at 80% allocation, Blair in Team A at 100%, and Casey in Team B at 50%. Do not invent pay, FTE or reporting lines. Open it in Scenario Studio.
Create a guest scenario called Studio Smoke Test from this model without changes. Keep the guest Live model unchanged, and open the saved scenario in Scenario Studio.
Read the current saved scenario. Explain the represented placements and allocations. Tell me what is unknown about FTE, cost, position seats and reporting lines. Keep private capabilities out of your reply.
A text description of a chart is not proof that the panel opened. Host support and the actual read-only experience are being verified in this private preview. See the test steps and expected results.
The original Orgonaut plugin candidate stays separate. You can keep both installed and choose one per conversation; connecting an account to one does not authorise the other.
Existing governed conversation tools retain their own preview and approval rules. They do not mean the new visual editor is active.
Read the MCP contracts →Guest modelling, saved scenario reads, a bounded organisation graph, selection, pan and zoom. Connected Studio also requires preview enrolment and normal account permissions.
Visual drafts, Undo/Redo, exact server previews and an explicit Confirm click are implemented behind gates and are not enabled in the current preview.
Minimal selection context, saved-source comparison and optional sidebar/fullscreen integration need their preceding host tests. Studio costs are not exposed, and missing data is never zero.
Explore a temporary guest organisation first. Save only when you choose; declining signup does not stop the conversation. Unclaimed drafts expire after seven days by default.
Connected reads respect the selected organisation, membership, connection scopes and permissions. Guest capabilities and claim links stay private.
The plugin cannot edit permanent Live, promote or restore a scenario, purchase a subscription or administer members. Allocation does not reveal salary or reporting relationships.
Building an integration? See MCP connections and the REST API reference. They have distinct contracts and write surfaces.