Page 1 of 2

✺ LOGIC-READINESS AUDIT: INTAKE PROTOCOL

SECTION 1: IDENTIFICATION

1. Lead Point of Contact

Who is the primary recipient of the Red-Line Diagnostic and Scorecard?

2. Professional Email

Used for secure artifact delivery and Stripe invoicing.

3. Organization Name

4. Product/Company URL

SECTION 2: AUDIT TIER SELECTION

5. Selected Intervention Tier

✺ LIGHT AUDIT ($600) — 1 Core Flow / 24-Hour Turnaround

✺ STANDARD AUDIT ($1,200) — Up to 3 Core Flows / 72-Hour Turnaround

✺ COMPLEX AUDIT (CUSTOM) — Enterprise Systems / Multi-sided Platforms

6. Primary Asset Link

Link to Figma file, Notion spec, or GitHub PR.

Ensure has "View" access before submitting.

7. Defined Audit Scope

List the specific workflows to be stress-tested.

Tier Constraints:
Light: List exactly ONE flow (e.g., "The Stripe Integration").
Standard: List up to THREE flows (e.g., "Onboarding, Checkout, Invites").
Complex: Provide a high-level overview of the system architecture.

SECTION 4: THE DIAGNOSTIC CONTEXT

8. Primary Friction Point

The Human Tax: Engineers are spending 30%+ of the sprint on requirement triage.

The AI Tax: Coding agents (Cursor/Bolt) are hallucinating due to spec ambiguity.

The Roadmap Stall: High sprint carryover and unhandled edge-cases are slowing deployments.

9. Known Technical Constraints

Are there specific backend invariants or API limitations I should know about? (e.g., "Legacy database prevents guest checkout.")

SECTION 5: SUBMISSION PROTOCOL

10. Confirmation of Terms

I understand this is a clinical audit of logic, not a UX/UI critique. The delivery clock begins once the Stripe invoice for my selected tier is cleared.