Concept
The versioned execution primitive.
A trajectory is Weles's reusable execution primitive: an authorized objective plus an ordered tool history, session policy, terminal contract, and evidence identity that can be reviewed, versioned, and replayed.
Primitive contract#
| Part | Meaning |
|---|---|
Identity | A stable action name and source path. Production admission binds it to one organization, origin, and allowlisted action. |
Objective | The exact external effect the run must reach; it is narrower than permission to automate an entire site. |
Steps | An ordered history of tool plus structured arguments. Generic replay stores { tool, args, result? }; checked-in trajectories can encode richer control flow in source. |
Session policy | Browser engine, persona, proxy/sticky identity, profile reuse, credential references, and whether keeper-first discovery is required. |
Terminal contract | Explicit completed, failed, or needs_human_approval state plus the observable result required before completion. |
Evidence identity | Trajectory path, source revision, browser release coordinate, action-log row, artifacts, and optional signed receipt. |
Lifecycle#
- Discovery starts from an authorized objective. The writer can produce a draft using navigate, click, fill, credential, email, CAPTCHA, state-reading, and terminal tools.
- Keeper-first discovery drives one persistent WSession with humanized atoms and records the successful action history.
- A successful keeper-first run saves that history as a reusable trajectory; a model draft alone is not production authorization.
- Review fixes the origin, action, credentials, browser/session policy, terminal condition, and failure behavior.
- Production resolves the reviewed version and replays it in a verified browser build. A scope or behavior change creates a new reviewed version.
Tool vocabulary#
The generic trajectory writer currently targets navigate, click, fill, fill_credential, store_credential, type_text, focus, press_key, scroll, wait, read, select_option, set_control, js_click, solve_captcha, check_email, generate_identity, save_account, done, and give_up. A checked-in trajectory may use WSession directly, but it still owes the same authorization, terminal-state, evidence, secret, and browser-release boundaries.
Failure and continuation#
Failure records the exact step, terminal reason, browser/session metadata, and retained artifacts. MFA, passkeys, legal ambiguity, unavailable mailbox access, or an unsolved challenge close or pause explicitly; retrying the same submission is not a substitute for a continuation token or reviewed trajectory change.