DUO.bz — Protected & Private Content Pull (authenticated)

Pulled 2026-08-08 via wp-admin login (Jetpack Protect captcha solved) + REST application password

Auth method: `Marcus` (id 1, admin) — app password `(revoked after this pull)` (revocable in wp-admin → Profile → Application Passwords)

Files: `full/` directory alongside the public dump. Complements `DUO-SITE-AUDIT.md`.

What the authenticated pull added (vs the public dump)

1. Private posts (7) — full content in `full/posts_any_1.json`

3121cc11The Covenant vs. Contract – claude74K**Claude-generated lesson** (interesting: AI content already being produced for the site)
2982iw1The Inner Work78KFull lesson app
2750ho11-2The Household54KApp
2679compass-2-2compass 260K**Alternate Compass build** (dims + flight plan, no zones)
2673compass-2compass 243K**Alternate Compass build** (dims + flight plan, no zones)
2392mc13The Marriage Compass49KEarlier Compass concept (zones, no dims array — different structure)
2355ho1The Hidden Operating System34KApp

2. Private pages (9) — full content in `full/pages_any.json`

2991co2-2Connection102KConnection hub variant
2978ho3Household61Kvariant
2975co3Connection60Kvariant
2910fo3The Foundations Category58Kvariant
2803ho2The Household68Kvariant
2763fo2The Foundations45Kvariant
24592459-2Home 234Khomepage variant
1923join-duojoin old79Kold join page
1805homeold home314K**old full homepage** (largest page on site)

3. Draft pages (3)

  • **pricing (id 1571, 118K)** — ⚠️ template junk: lorem-ipsum, “$50 Pro / $155 Membership” from an old Kadence demo. **Not real pricing — do not use for 2.0 pricing decisions.**
  • privacy-policy (draft, 4.9K), refund-and-returns-policy (draft, 4.6K) — boilerplate legal pages, never published.
  • 4. No password-protected content exists

    content.protected = false on every post/page. The only gating on the site is Paid Member Subscriptions (member-login based). With admin auth we see all of it.

    5. Commerce reality check (⚠️ important for the product target)

  • **WooCommerce: 1 product, 0 orders, 0 coupons, 0 refunds — ever.** (`full/wc_orders.json`, `full/wc_report_totals.json`)
  • **2 customers:** mvk8000@gmail.com (admin) + gskmentor@gmail.com (test) — no real buyers
  • **20 WP users, all test/dummy** (`full/users.json`): Alina Lohr, Chadwick Chan, gskmentor, “test”, Kermit Deegan (slug hellenbush39), etc. — no real member accounts
  • **0 form submissions** (`full/feedback2.json`, `full/kadence_forms2.json`, `full/jetpack_forms2.json`) — the Compass→email-capture funnel was never live
  • **Payment gateways:** WooPayments (Stripe) + PayPal enabled, Apple Pay/Google Pay on; `full/wc_gateways.json`
  • **Jetpack Payments (jp_pay_*):** 0 products, 0 orders
  • **Bottom line: the product is fully built; the business has never transacted.** Every “revenue” figure for 2.0 is greenfield.
  • 6. Stack details (for migration planning) — `full/plugins.json`, `full/themes.json`, `full/settings.json`

  • 34 plugins; key actives: Blocksy Companion, Breeze, Code Snippets, **DUO Email Capture 1.0 (custom)**, GenerateBlocks, Jetpack, Kadence Blocks, Klaviyo, Paid Member Subscriptions 3.0.3, Permalink Manager, Post Type Switcher, ReactPress 3.4.0, WP Sheet Editor, WooCommerce 10.6.1, WooPayments, PayPal Payments, Google/Meta/Reddit/Snapchat for WooCommerce, All-in-One WP Migration + Migrate Guru (migration tools installed)
  • Theme: Blocksy 2.1.35 active (Kadence theme installed, inactive)
  • Site: “DUO for Couples”, admin email mvk8000@gmail.com, page_on_front 3493
  • Menu (8): Book, Compass, Pillars, Household, Foundations, Connection, Repair, 28 Days — `full/menu_items.json`
  • 7. Version graveyard (content-fork evidence)

    The private items confirm the copy-paste sprawl: 3+ Compass variants, 6+ hub/pillar variants, 3+ homepage versions, multiple lesson re-builds — same concepts, divergent code/copy. Duo 2.0 must reconcile to ONE canonical curriculum (see PRODUCT-TARGET.md §4.4).

    Credential hygiene note

    The application password (revoked after this pull) grants API access to duo.bz. Revoke it (wp-admin → Users → Profile → Application Passwords) once the migration export is done, or keep for the Builder migration work if approved.