Results for “proof-gate”

Audit whether a "current product focus receipt" (Decision/Now/Why-now/Evidence/Not-now/Cut-suspend/First-visible-proof/ Acceptance-gate/Kill-revisit-trigger/Owner/Review-date) and the work order it gates state a real, testable decision and a real agent launch — not planning-placeholder prose that sounds like an assignment but can't be proven. Use when deciding whether to launch an agent chain against a milestone or a stated "focus," when a work order lacks explicit input/output/owner/proof-gate, or when an acceptance gate would only prove a cached UI state instead of daemon truth. NOT for distinguishing roadmap items from energy-driven sidequests (legible-roadmap-with-sidequests), reviewing a PRD/prototype for product-completeness gaps like cold start or pricing (product-reality-reviewer), or accepting already-finished work against a personal acceptance bar (port-daddy-user-surrogate-pm-review).

The English summary is being prepared. Showing the original description.

Opens groups of OpenRig agent terminals as live herdr tiles for interaction or observation. Explains view selection, read-only access, saved groups, and how to interpret agents that are offline or cannot be displayed.

• Opening all live agents in a rig as terminal tiles
• Watching mission or slice agents in read-only views
• Reopening a custom group from a saved view

Open terminal views for OpenRig agents in cmux, grouped by rig, pod, mission, slice, or saved view. Inspect connection health and view agent sessions with read-only access where required, while keeping the underlying sessions running.

• View a rig's agent terminals together in cmux
• Monitor mission or slice terminals in read-only mode
• Reopen a saved terminal view

Audit an Excel workbook before editing, then verify the saved file with Python and openpyxl. Each requested requirement receives an explicit status, so completion depends on checks of the actual file.

• Verify exact sheet names and row counts
• Check sample size and category coverage
• Confirm required source sheets remain after editing

Own whether a multi-document product-architecture binder is internally consistent, complete against its stated customer/contingency/architecture coverage, and honest about which older product ambitions it has absorbed, superseded, deferred, contradicted, orphaned, or rejected. Use when running a binder Architect of Record pass, before an implementation chain cites a binder chapter as ready, when a proof-gate owner is missing, or when reconciling the binder against the older ambition corpus (website, plans, examples, ADRs). NOT for auditing a single Claude Skill bundle's structure or frontmatter (use skill-hygiene), rendering a single-PM accept/reject verdict on one finished deliverable (use port-daddy-user-surrogate-pm-review), or sequencing/stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (use legible-roadmap-with-sidequests).

The English summary is being prepared. Showing the original description.