Projects that pass object readiness, optional PLAN guardrails and any required one-use approval.
2XBR PROJECTS / RUN / AUTOMATION ENGINESee what can run.
See what can run.
Run what you mean.
Review project readiness, apply existing guardrails when required, then start the run explicitly. The AUTOMATION engine still owns execution gating and bounded run results; nothing schedules itself and nothing becomes a hidden browser daemon.
Review project run →PROJECTLOCAL OBJECTS→RECIPEPINNED FLOW→GUARDRAILSWHEN REQUIRED→RUNEXPLICIT→HISTORYBOUNDED
LOCAL ONLY0 PROJECTS0 RUNNABLE0 GATEDPROJECT RUN / LOCAL CONTROL
Missing recipe, protected inputs, plan drift, policy input limit or approval required.
Projects that can be opened in visible-tab WATCH after an explicit folder selection and ARM.
Bounded local project-run metadata only. No filenames, hashes or output payloads.
01 / PROJECT RUNS
Plan, approve, run.
RUN NOW stays explicit. Optional guardrails add reusable POLICIES rules and scope-bound, one-use approvals without introducing a scheduler.
No matching local projects.
Create a PROJECT and pin a saved recipe first.
OPEN PROJECTS →02 / RUN HISTORY
Bounded execution evidence.
No local project runs yet.
RUN NOW is always a user action. Plans and approvals govern that action; they do not create a scheduler.
The one-use approval binds the exact project, plan, recipe and WORKSPACE object revisions for ten minutes.
WATCH remains a separate explicit session with a local directory handle that disappears on reload.