Getting started with Kyormar

There is no public installer yet. The Download page shows signing, validation, and scheduling status. Do not obtain files claiming to be an official Kyormar release from third-party sources.

Choose the entry point you actually need

IM and Agent can both start independently and exchange only explicit data and events when linked. A separate Rust service provides necessary account and remote team capabilities, but the client does not depend on it to start.

Start with a small task that has acceptance criteria

1. Specify the object to change, such as one file, one page, or one API.
2. State constraints, such as not changing payment amounts, not inferring user identity, and preserving linear Git history.
3. Define completion, such as a test name, page state, or server response.
4. Keep tool calls, confirmation points, and final results in the execution record instead of replacing real state with a summary.

Goal: Fix content reveal order after navigating home
Constraint: Preserve the current visuals and Cookie prompt
Acceptance: Elements reveal in order on desktop and mobile, with no animation under reduced motion

Break “done” into verifiable evidence

Code checks, a successful build, desktop execution, and production validation are different evidence layers. A report must state which layer actually ran; without running the product UI, a static build cannot be described as complete dynamic acceptance.

Continue with Client architecture to understand module boundaries, or view public delivery status.