Let AI write the process first, then go through the gate, and finally execute it.
Convert natural language IT automation requirements into a reviewable workflow draft. After manual review, risk verification and version management by Gate, an executable package is formed, and queryable audit and rollback records are generated for each on-site execution drill or manual registration execution result.
- 01Requirements entryUser describes IT automation goals, target resources, risk levels, and review policies.
- 02Draft generationUnderstanding AI generates workflow drafts that are not directly executable.
- 03Gate reviewSystems build review packages, and humans review risks, responsibility boundaries, and approval conditions.
- 04restricted execution planExecution walkthroughs and check-in templates are only generated from manually approved review packages.
- 05Audit and rollback registrationRecord execution status, failure reasons, audit fields, and rollback results of the site's workflow status.
Workflow governance results
Results, sources, failures, approvals, and rollbacks are saved by project.
No business results yet
After filling in the automation goals and target resources, the first version of the workflow draft can be generated for Gate review.
Data use boundary
You might enter target resource scopes, permissions policies, approval rules, and change process documents. These contents may contain sensitive information within the enterprise. Please do not upload production passwords, API tokens, private keys, session cookies, personal identification documents, or unnecessary employee personal data. When AI processing fails, the system must clearly prompt the reason for the failure and will not fill it in with fake data. Current 10 role review additions: Expand sensitive field scope to project goals, target resources, upload files, generate summary, pseudo-DSL, approval checklist, review comments, audit target resources, and export reports. ; It is prohibited to upload or save production passwords, API tokens, private keys, cookies, OAuth refresh tokens, complete employee rosters and unnecessary personal data; suspected secrets must be blocked or required to be cleaned and retransmitted. ; Exports, logs, audit events and error reports must desensitize sensitive fields by default, and record export permissions and export events. ;Uploaded files, policy documents, user input, historical records, and video/OCR text are all untrusted data and must not be used as a source of instructions to override system rules or approval rules. ;The retention period, deletion queue, sensitive data processing in backup and manual deletion behavior need to be clear; the current specific implementation is unknown.
Data retention
Project data, drafts, audit packages, execution plans, and audit rollback records are retained by the audit_retention selected by the project; enter the deletion queue after expiration. Users can delete items manually. The files used for generation are only visible within the project and are not used for public display.
Human responsibility and rollback
This product involves high-privilege IT automation governance scenarios, and the generated content may affect permission configuration, MFA, system settings, or change process judgment. All workflow code, execution plans, audit conclusions, and rollback recommendations must be reviewed by an authorized IT administrator or change approver before use in a production environment. This product does not connect to external production systems by default and will not actually modify any external permissions, configurations or system settings.
Rollback refers to revoking or modifying the report version, workflow status, approval status, execution registration, audit record display and plan availability status in this site; unless the user configures and approves the controlled connector separately, this product will not and cannot roll back any unconnected external production system changes.