01
Phase // 01
Verify the release
Use the Download Center to confirm the Windows package, version, release notes, and integrity information before installing.
Operational flow // 03Set up deliberately.
Set up deliberately.
Operate with oversight.
Artemis is designed around a simple discipline: verify the software, establish controlled account access, then enable only the workflows an operator can review.
The desktop product is local-first. The public website, account, billing, analytics, and error-monitoring surfaces use network services; see the architecture note for the scoped disclosure.
Section // 01
Three deliberate steps
02
Phase // 02
Establish account access
Use the verified sign-in flow for your member account. Subscription and billing controls live in the Command Deck, not in a support chat.
03
Phase // 03
Configure with oversight
Start with a narrow workflow, review its result, and keep an operator responsible for every automation and recovery decision.
Section // 02
The operator checkpoint
Review before scale
Automation should reduce repetitive work, not remove accountability. Define who owns a rule, what gets reviewed, and how it can be reversed before it runs widely.
- Verify the release version and package source.
- Keep account credentials out of support conversations.
- Document an owner and rollback path for each workflow.