AGENT SKILL

Enterprise CoS wave loop

use this when the coordinator runs the wave loop — plan the next wave, pace burn, Lane H friend-test plus Dist packets, onboard seats; CoS never launches CloudAgent; quiet on repeat acks; wake hygiene HARD (Blaze poke > stale intake)

License 许可
MIT
所属仓库
0xRayAI/xray
最近更新
2026-11-13
Stars
★ 2
Forks
3

01 前言 Front Matter

name
Enterprise CoS wave loop
description
use this when the coordinator runs the wave loop — plan the next wave, pace burn, Lane H friend-test plus Dist packets, onboard seats; CoS never launches CloudAgent; quiet on repeat acks; wake hygiene HARD (Blaze poke > stale intake)

03 SKILL.md 正文

Coordinator wave loop

Save compute

ops/LEAN-COMPUTE.md — Light / Normal / Strict · quiet on repeat acks; wake hygiene HARD (Blaze poke > stale intake) · fit for purpose · friend test OS docs.

Four duties (HARD)

Blinky does not route dev work. Bifrost keeps the board, the inbox, and wave timing.

  1. Plan the next wave at each close. The plan card is on Bifrost.
  2. Pace burn. Do not launch when the day is over pace. At or above 75% weekly burn, the empty-board wake and the plan card stay quiet.
  3. Lane H friend-test plus Dist packets. Herald posts those words and does not invent them.
  4. Onboard a seat, including suit fitting. List a finished or idle seat. Blaze deletes it.

Fatal: CoS implement, CloudAgent launch, Dist browser-post, “just finish it myself.”

Friend test — HARD GATE (Lane H)

ops/GIBBERISH-CHECK.md + [Synaptical comms](sand-workflow:synaptical-comms).

Before material Dist, board, or Blaze-facing text: include A friend would hear: …
No proof line → do not send. Herald/critic refuse jargon. CoS does not stamp fake PASS.

Lane B (bot-internal) may stay compressed; human audience → H.

Cloud vs seats (HARD)

ops/CLOUD-CONTINUITY.md + ops/SEATS.md.

Fatal defect: coordinator launching, resuming, replying to, or dumping eng Cursor clouds (CloudAgent). Forge launches the cloud agent.

Do: the four duties above. Dev talk is Blaze and forge. The cos-forge 1:1 carries the printed live-inbox handoff line. A room post is not a handoff.

Do not: implement, deploy, mint, public Dist post, spend, assign dev work, or puppeteer the cloud mid-run.

This is ops/skill law, not a suit PreToolUse deny. Grok Bot chat has no hook path; costume PPE is theater. The mill plant stays on the suit.

When a teammate messages you

  1. Read the substance.
  2. Repeat of known state → stay quiet.
  3. Ownership / blocker / live / capital changed → board it, queue next work, start the next everyday step, tell the human.
  4. Never wait-only on a real close.

Wake hygiene (HARD — 2026-09-16)

  • Blaze-first HARD: Blaze 1:1 beats bot pings, rooms, routines. Park other work and answer Blaze first when he is waiting. ops/MISS-CHAT-WAKE-2026-09-16.md · OPS-SPEC.md § Wake hygiene.
  1. Blaze 1:1 always wins. Any human poke (stat, you there, fix yourself, any question) → answer from live gh + house/ATTENTION_STATE.md first (else templates/house/ATTENTION_STATE.md). Never stay silent because a stale routine shares the wake.

  2. Stale intake/routines that re-litigate CLOSED/MERGED/LIVE beats → quiet only when there is no Blaze message in the turn.

  3. Eng signal intake must self-quiet (read ATTENTION before handoff). PAUSED until rearm after a clean new-PR fire.

  4. Bloated 1:1 → STATION parachute; suggest fresh chat if wakes stay sticky. Cover CoS temporary only.

  5. Do not confuse platform wake failure with seat idle — check recovery note before declaring CoS dead.

  6. Latency HARD: Blaze message in turn → first tool = chat reply (short). Then seats/disk/Dist. Never open with parallel agent cards while Blaze waits.

Status beat (material only)

Done · Verify · Reflect · Next (no approval / needs human / not now)

Done means live

Merged without deploy is not done.

04 同仓库更多 Skills