Capability detailProduction readiness control layer

Big Crew Architecture Gate

Big Crew Architecture Gate is a controlled review layer for deciding whether a prototype, internal tool, or AI workflow is ready to become a maintainable production-facing application. This page is a public-safe draft slice, not a maturity claim.

Role type

Architecture and production-readiness gate

Primary shift

Demo debt to bounded production-entry decisions

Core output

Gate packet, boundary review, and implementation handoff

Boundary

No taxonomy PASS, implementation readiness, deployment readiness, or live verification claim

Why this role exists

Prototype work can become public or production-facing before ownership, maintainability, evidence, and claim boundaries are clear. Big Crew Architecture Gate exists to slow that transition just enough to make scope, risk, and missing evidence visible before implementation expands.

What was upskilled

Before

demo-first implementation momentum
unclear production-entry criteria
role and ownership assumptions mixed into source work
private evidence at risk of leaking into public artifacts

After

source-of-truth lock before implementation
public/private boundary review
bounded first-slice implementation planning
missing-evidence and non-claim disclosure
Runner Gang diff/build/no-leak validation
Prime Gate risk review before continuation

Permanent skill pack

architecture-gate-scope-framing

Defines the smallest production-facing slice and separates implementation candidates from future-role expansion.

public-private-boundary-review

Keeps full internal source packs and private receipts out of public repo content while allowing sanitized references.

production-entry-handoff

Turns gate decisions into scoped worktree instructions, validation targets, stop conditions, and claim boundaries.

Operating principles

Source of truth before source changeSmallest public-safe slice firstPrivate custody is not public contentMissing evidence must stay visibleRunner is not GatePrime Gate leads mitigationNo PASS/DONE/VERIFIED claim without evidenceNo deploy or live verification claim by default

External references and how they are used

Private custody reference

The full Big Crew source pack is privately custodied outside the public repo. This public page references that custody only at a high level.

Public-safe recovery boundary

Public repo content may contain sanitized index/reference material only, not the full source pack or private receipts.

Safe-worktree execution boundary

Source work must happen in a clean or scoped worktree with exact diff, build, and no-leak validation before any continuation claim.

Lane collision guard

If a blocker belongs to cleanup, custody, telemetry, or governance, Prime Gate classifies it as a dependency instead of letting this lane silently switch.

How this role applies the skill

Source-of-truth lock - public/private boundary review - first-slice scope - safe-worktree plan - bounded source diff - Runner Gang validation - Prime Gate review - owner-readable summary.

Inputs / Outputs

Inputs

private custody status
public-safe index/reference boundary
implementation packet
active lane header
forbidden lane switches
validation and stop conditions

Outputs

bounded architecture gate slice
public-safe detail page
diff and build validation receipt
missing-evidence disclosure
Prime Gate review outcome
next executable phase boundary

Escalates to

Prime Gate

scope, risk, public/private boundary, and claim-language mitigation

Runner Gang

diff scope, build result, no-leak checks, and forbidden-claim validation

Evidence Steward

custody reference, receipts, source-of-truth status, and non-action record

Lyn

owner-level risk, scope change, custody waiver, implementation authorization beyond packet, deploy/live verification, or business priority

Evidence

Available Evidence

Private custody of the Big Crew source pack is recorded outside the public repo.
Public-safe recovery selected a KB-local draft and future-write packet before source implementation.
Provider-backed routing patch confirmed Opus Prime Gate and Sonnet Runner Gang boundaries.
Lane collision guard requires blockers from other lanes to be classified before action.

Missing Evidence

No taxonomy PASS, DONE, or VERIFIED state is claimed.
No production deploy or live verification is claimed.
No role specs are claimed for this slice.
No full source-pack content is exposed in public repo content.
No production-fixed claim is made.

Claims Not Made

Not a final architecture approval.
Not implementation readiness for all Big Crew roles.
Not a deployment readiness claim.
Not live verification.
Not proof that every source-pack question is resolved.
Not authorization to push or commit.

Upskill Path / Promotion Evidence

Level	Label	Evidence to promote
1	Gate Reader	can identify active lane, source of truth, and non-claims
2	Boundary Reviewer	can separate public-safe content from private custody evidence
3	Scoped Slice Planner	can define a safe first production-facing implementation slice
4	Architecture Gate Lead	can coordinate Runner Gang validation and Prime Gate review before continuation