william-lu-stack/flawless

Overview

CISRE (Cloud Infrastructure Site Reliability Engine) connects infrastructure risk discovery, evidence collection, root cause diagnosis, manual approval, controlled changes, recovery validation, and experience accumulation into an auditable closed loop. The model is responsible for understanding, planning, and interpreting; Skill is responsible for domain handling knowledge; Plugins provide composability; Harness is responsible for state, permissions, and orchestration; Controlled executors are responsible for real changes; Verifiers are responsible for proving that the target has been restored. Execution API returns successful, the model claims success, or the old instance remains healthy—none of these are fault recovery. Only when new evidence of the real target meets the recovery contract does the task close the loop. - : Perform forensics, diagnostics, approvals, execution, and recovery validation around real resources. - : Discover risks at regular times or manually, and reuse the same operations kernel as SRE Run. - : Display resource dependencies, traffic, and explosion radius to assist with risk access control. - : Maintain issue trigger conditions, progressive forensics, actions, rollbacks, and success criteria. - : View plugin details, call conditions, service dependencies, security boundaries, and recent calls; Supports visualization or model-assisted creation, and allows one-click download of runnable Provider + Skill + Test + Deployment projects. - : Runtime overview, resource events, plugins and profiles, Agent Trace, and operational performance. - : Only counts issues that have passed recovery validation; Can expand root causes, skills, changes, and recovery evidence. "Contract ready" means interfaces, permissions, auditing, and closed-loop semantics are in place, but does not mean a specific product is connected. Pages must not forge resources or health data. CISRE has absorbed the combined concept of the official DeepSeek Harness but retains independent production execution boundaries: - Everything is a Plugin: Newly added domain capabilities are delivered first without modifying core orchestration. - Service Provider / Consumer: Plugins use provide/requires to declare capabilities and dependencies, which are parsed by runtime. - Profile / Bundle / Patch: Development, testing, and production can combine different Providers without being decided in the business code by the heap environment. - Event-driven: Supports observe, serial, parallel, and waterfall; High-risk access control can only be tightened and cannot be bypassed by plugins. - Reversible lifecycle: Loading, unloading, hot reloading, and resource release have a definite order. - Event Origination: Session events are added and written, desensitized, and hashed in tandem, supporting replay, fork, resume, and audit tombstone removal.

Overview (machine translated)

This page was translated automatically. Technical details may differ from the original.

Recommended Tools

Try a different keyword or remove a filter.

Install