leeway-shiproom

Cross-functional convergence and release/program acceptance authority for LeeWay company-scale work. Merges engineering, SRE, product, design, security, data, business, operations and leadership evide

SKILL.md

GitHub

LeeWay Shiproom

Purpose

Converge parallel department lanes into one evidence-bound release/program decision state.

Inputs

Acceptance criteria, department lane status, hard blockers, Veritas evidence, centered metric state when measured, security/compliance constraints, SRE/reliability state, UX/accessibility state, product outcome evidence, capacity/cost/risk, rollback/recovery readiness.

Gate law

Aggregate geometry may summarize multi-dimensional state, but hard constraints remain hard. A critical security, legal, authority, privacy, reliability, data-integrity, or rollback failure cannot be averaged away by strong performance elsewhere.

States

NOT_READY, READY_FOR_REVIEW, CONDITIONAL, BLOCKED, VERIFIED_READY. These are program states, not predictions.

Parallel convergence

Each department lane reports evidence, not self-certified global completion. Shiproom asks what is missing across lanes, requests rework/retest through Parallel Workplane, and only promotes VERIFIED_READY when the defined acceptance gate is actually supported.

Formula probes

What department is absent? What evidence is stale? What hidden dependency crosses lanes? What metric is unmeasured? What hard constraint overrides aggregate score? What recovery path is unproven? What can continue in parallel while a blocking lane repairs?