Find the feature and its evidence

This map routes tasks to the full procedures and exact references. A menu entry, tool definition or successful job is not qualification of every device or method. Start with the task, discover the admitted inputs, then inspect retained evidence.

Create, inspect and change a network

Projects explains opening/saving native projects, preserving IDs, diagrams and scenarios, and the difference between the human editor and detached AI candidates. Equipment gives every extracted native property with its declared unit/type/profile. Do not infer absent units or repair imported data silently. Upstream menus lists native actions without claiming each format, device or upstream study is admitted by PowerSystem.

Work with AI and retained engineering history

Chat covers Plan/Build, exact Implement plan, attachments, queued messages, questions, helpers, Stop, Retry, editing and recovered conversations. Accounts distinguishes the owner subscription from customer managed-API access and explains local /status; viewing it is not an inference turn. Commands gives actual command availability and shortcuts; disabled actions remain guarded.

History explains branch inspection, recorded parent graphs, Save version, working changes and exact-source conversations. Combine explains before/after comparison versus separately prepared multi-parent proposals, explicit conflict choices and undo/restore. None of those operations approves engineering or advances protected Main automatically. Examples provides a populated synthetic project in a separate window; the example is not an owner's model.

Run a study and understand a result

Studies starts without an AI message, then covers immutable case versions, one-shot/batch submission, the shared queue, cancellation and historical results. Study reference explains each registered method with input units, interpretation and recovery. A registered advanced method may be typed-tool-only; use its actual definition rather than assuming a native form.

First study is the bounded baseline workflow. Read convergence and warnings before tables/diagrams, and inspect input/configuration/solver hashes. Evidence explains compatible result comparison and separate human review. A failed/islanded/incomplete result remains non-passing, not zero output.

Extend, recover and share safely

Project tools explains discovery, create/install/test, real review, activation, invocation, cancellation, revocation and removal in isolated workers. Typed tools preserves every registered input schema. A schema does not grant filesystem, network, manufacturer-attestation or engineering-approval rights. Developer coding skills are not customer project tools and are not inherited.

Recovery explains retained work and failure recovery. Preserve unknown working edits, rollback markers and backups; they are not disposable cache. Portable handover requires exact source/destination consent and transfers no account or approval. Native controls explains each extracted control's intent and routes to the corresponding procedure.

Evaluate, install and close an account

Customer journey follows public evaluation, availability, pricing, installation, sign-in, first study, support, cancellation, export/deletion and uninstall. Website maps public routes. Pricing policy gives canonical units and allowances; planned prices are not active offers. Availability distinguishes local features from customer release qualification and enumerates limits. Reference provenance explains extracted native source declarations and license boundaries.