ABKC — James Cooper Gate Pack

0 of 0 complete

ABKC — James Cooper Gate Pack

Every open question, policy decision, and verification the new ABKC website needs from you

From: Dane Cooper (operator) — prepared with Claude · Date: 2026-06-10 · Version: 1.0

Time needed: 60–75 minutes total. Two sittings is completely fine — your progress saves automatically.

How to answer (one rule): the easiest way is the questionnaire app — either the live link Dane sends (just tap SEND at the end) or the downloaded *-QUESTIONNAIRE-APP.html file (tap EXPORT ANSWERS and email Dane the file). Prefer paper or Word? Mark up THIS document and email it back — that works too. Pick one lane so nothing gets split.

Getting answers back to Dane: If you opened this at james.cooperluxe.com, just tap SEND at the end — Dane gets it automatically. If you opened a downloaded file, tap EXPORT ANSWERS and email the file back to Dane. Either way your answers also save on this device as you type.

Contents

§ Section Items ~Minutes
1 👋 Welcome — how this works 2 3
2 🐕 Breed standards, judges & pedigrees 7 12
3 🏆 Registrations, pricing & points 7 10
4 📋 SOP verification — what's documented vs. how ABKC really works 6 8
5 🏢 Office policy decisions (the six blanks) 8 10
6 🧭 Business & platform decisions 9 10
7 🚀 Launch posture — your sign-off path 6 6
8 🔒 Security & risk — what we found and what we're doing 6 6
9 📊 For your awareness — engineering status (no input needed) 4 3
10 🤝 Your joint test session with Dane 4 5
11 ✍️ Final sign-off 3 3

§1 — 👋 Welcome — how this works (~3 min)

Dane and the AI team have spent ~3 months building the new ABKC website (registrations, payments, judges, events, points, the office admin area). It is nearly launch-ready. This pack collects EVERYTHING that needs YOUR eyes: business decisions only you can make, registry facts only you can verify, and a few risk items you should see. There are no wrong answers — every question has a 'Not sure — discuss live' escape hatch, and anything you skip just lands on the agenda for your joint session with Dane.

ABKC-V-001 — You're James Cooper, ABKC co-owner, answering for ABKC ownership — and bullysupplies@gmail.com is the right email for anything we send you.

Context: This pack and the upcoming co-owner test session use this address.

If correction needed, what's the real state?

Your answer:

ABKC-D-001 — When Dane follows up on your answers, what works best?

Notes (optional):

§2 — 🐕 Breed standards, judges & pedigrees (~12 min)

This is where your decades of registry knowledge matter most. The new site carries content and rules forward from the old systems — you're the only one who can say whether they're RIGHT.

ABKC-V-002 — The breed standards shown on the new site are the CURRENT official ABKC versions.

Context: Breed standard pages were carried over from the legacy site's content. If any breed's standard has been revised and the site shows an old version, that's a registry-accuracy problem only you would catch.

What this means for you: If you confirm, the standards go live as-is. If anything is outdated, name the breed(s) and we fix before launch.

Which breed(s) show an outdated or wrong standard?

Your answer:

ref: abkc-website breed standards pages

ABKC-V-003 — The judges directory should show CURRENT judges only — and the current list is accurate.

Context: A recent fix hides retired/inactive judges from the public directory. Two things to verify: (1) 'current-only' is the right business rule, (2) nobody is missing and nobody is listed who shouldn't be.

Who's missing, who shouldn't be listed, or should retired judges be shown differently (e.g., an alumni page)?

Your answer:

ref: judges current-only fix (2026-06-02)

ABKC-V-004 — What must an ABKC pedigree certificate show to be registry-correct?

Context: When the office approves a registration, the member is automatically emailed a digital packet: certificate + pedigree + receipt PDFs. We need your definition of 'correct' for the pedigree: how many generations, how titles display, how registry numbers are formatted, anything else that makes it official in your eyes.

What this means for you: Your answer becomes the acceptance checklist for the pedigree output before launch.

Example: e.g., 3 generations minimum, champions in red, ABKC number format ABK-#####, sire/dam registry numbers shown…

Your answer:

ref: fulfillment engine PR #160

ABKC-V-005 — Events and show results on the new site (synced automatically from the old site) look correct and complete.

Context: The new site pulls judges, events, results, and venues from the legacy site's system on a sync schedule. Spot-check a couple of recent shows you know.

Which event/result is wrong or missing?

Your answer:

ABKC-V-006 — The 12-month DNA rule on puppy registrations is the correct ABKC rule.

Context: The system now enforces: a puppy-permanent registration where the dog is over 12 months old requires DNA on file. This was implemented from the documented rule — confirm it matches actual ABKC policy (and whether any exceptions exist).

What's the actual rule / what exceptions apply?

Your answer:

ref: PR #164 (puppy-permanent DNA rule)

ABKC-V-007 — The outside-registry list on the registration form (UKC / AKC / ADBA provenance) is the right set.

Context: The form lets a member declare which other registry their dog's papers come from. A recent fix made this selector directly visible (it used to hide behind a yes/no question that defaulted wrong — a real paperwork-accuracy risk, now fixed).

Which registries should be added or removed?

Your answer:

ref: ABKC-10 / PR #151

ABKC-D-002 — 8,787 dogs in the legacy data have no linked owner. When do we clean that up?

Context: This predates the new website — it's old data, not new breakage. The new site works fine without fixing it, but those historical records are incomplete.

What this means for you: Pre-launch cleanup delays launch. Post-launch means the records stay incomplete a bit longer but nothing visible breaks.

Dane's recommendation (one-tap option in the app): After launch — start with a sample audit

Notes (optional):

ref: data-integrity audit 2026-03-20

§3 — 🏆 Registrations, pricing & points (~10 min)

The products the office sells, what they cost, and the championship points engine.

ABKC-V-008 — The registration product set is complete: single dog, litter, transfer, junior handler, duplicate/reprint (+ puppy-permanent and bulk multi-dog paths) — plus the ABKC shop.

Context: These are the registration types the new site sells today.

What does the office sell that's missing from this list?

Your answer:

ABKC-V-009 — Single-dog registration pricing is $62.00 total ($55 base + $7 processing).

Context: This is the live price on the new site. The same structure (base + processing) applies to the other types.

List any registration type whose price is wrong — and the correct full price sheet if you have it.

Your answer:

ABKC-D-023 — The $7 processing fee: keep showing it as its own line at checkout, or fold it into one flat price?

Context: Members currently see '$55 + $7 processing = $62' at checkout. The $7 covers what the card companies charge us. Showing it separately is transparent; folding it in looks simpler; absorbing it costs the club ~$7 per registration.

Dane's recommendation (one-tap option in the app): Keep it as a separate line

Notes (optional):

ABKC-V-010 — Championship points & titles: where is the authoritative rule set?

Context: 28 scoring rules are configured in the new system, but the computed standings are EMPTY until we run the historical import — and before we do, we need to be certain the rules themselves are right.

What this means for you: Points are ABKC's core promise to members. Wrong rules = wrong champions. This is the single most important domain check in this pack.

Notes (optional):

ref: points_rules (28 rows) / points_ledger import pending

ABKC-D-003 — Who should validate the first computed standings before they go public?

(check ALL that apply)

If a specific judge: who?

ABKC-V-011 — The office workflow statuses match reality: submitted → under review → approved (or: revision requested / returned / rejected).

Context: This is the pipeline every registration moves through in the new admin area, and what the office staff will be trained on.

What does the office actually do differently?

Your answer:

ABKC-V-012 — Watch the two demo videos (~4 minutes total) and check off what's true.

Context: Two recordings show the registration form + payment options exactly as a member sees them: (1) single-dog registration, (2) dual ABKC+UKC registration. Dane will include them with this pack. Honest note: these show the full flow structure in test mode; the fully-narrated real-payment recordings are a separate option you can request below in Launch Posture.

(check ALL that apply)

ref: demo-2026-05-23 recordings

§4 — 📋 SOP verification — what's documented vs. how ABKC really works (~8 min)

The team wrote the standard operating procedures (walkthroughs, training guides, the owner package). Documentation only counts if it matches reality — that's your check.

ABKC-V-013 — You received and can open the owner package (cover letter, compliance statement, sign-off form, board memo).

Context: It's in the same folder Dane shares with this questionnaire.

If correction needed, what's the real state?

Your answer:

ABKC-V-014 — The office training guide's 8 modules cover the office's REAL daily workflow.

Context: The Office-Manager guide trains: the registration queue, reviewing + approving applications, assigning ABKC numbers, handling revision requests, orders/products, user roles, audit logs, and phone scripts. It deliberately does NOT train transfers yet (that admin screen isn't ready).

What does the office do every week that's NOT in that list?

Your answer:

ref: ABKC-ADMIN-OFFICE-MANAGER-WALKTHROUGH-V1 (M1–M8)

ABKC-V-015 — Members get a DIGITAL packet (certificate + pedigree + receipt PDFs by email) — and that matches what members are promised today.

Context: The system is digital-only; there is no paper certificate today. (Whether to ADD a paper program is a separate decision below.)

If correction needed, what's the real state?

Your answer:

ABKC-V-016 — Co-owner signature invitations expire after 14 days — is that the right window?

Context: When a registration lists a co-owner, the co-owner gets an email invitation to sign. If they don't sign within 14 days it expires and must be re-sent.

What window fits how members actually behave?

Your answer:

Context: Junior-handler registration is built with child-privacy protection (parental consent required for minors, per the COPPA law). We need the exact ABKC business rule: qualifying ages + whose consent + any extra requirements.

Example: e.g., ages 8–17, parent or legal guardian consents, must be ABKC member household…

Your answer:

ABKC-A-001 — Testing never uses real member data.

Context: All test registrations use clearly-marked fake dogs (names prefixed TEST-), stand-in photos/pedigrees, and the payment companies' official test modes. No real money, no real cards, no real member records.

If flagged, what would you change?:

§5 — 🏢 Office policy decisions (the six blanks) (~10 min)

Six policy questions the software can't answer — they're business calls. Dane finalizes these with you before the office staff get trained. Your answers here ARE the policy unless Dane flags a conflict.

ABKC-D-004 — ABKC registration numbering: what format, and what's the next number block?

Context: When the office approves a registration they assign the next ABKC number. The system accepts whatever scheme you define.

Example: e.g., format ABK-2026-#####, continue from the legacy sequence at #####…

Your answer:

ref: office walkthrough §9 blank 1

ABKC-D-005 — Queue promise: 'Your registration will be processed within ___ business days.'

Context: What the office is allowed to promise on the phone.

Notes (optional):

ref: office walkthrough §9 blank 2

ABKC-D-006 — Rush handling: if a member pays for rush, what do they get?

Notes (optional):

ref: office walkthrough §9 blank 3

ABKC-D-007 — Paper certificates: stay digital-only, or offer printed certificates?

Context: Today the system is digital-only (a 2026-05 ownership decision). Offering paper means choosing a price and a fulfillment process.

Notes (optional):

ref: office walkthrough §9 blank 4

ABKC-D-008 — Refund policy phrasing the office may read aloud to members.

Context: Refund DECISIONS stay with Dane — this is just the official sentence staff can say on the phone.

Example: e.g., 'Registration fees are refundable before processing begins; once your certificate is issued, fees are non-refundable except for billing errors.'

Your answer:

ref: office walkthrough §9 blank 5

ABKC-D-009 — Office hours + how the office escalates to Dane.

(check ALL that apply)

Office hours (e.g., Mon–Fri 9–5 ET) + anything else staff should know about reaching Dane:

ref: office walkthrough §9 blank 6

ABKC-D-010 — If payment problems ever spike (e.g., several failed captures in a day), who should be alerted immediately?

Context: The system already auto-refunds any member whose payment captured but whose registration failed to save — this is about who gets NOTIFIED when that safety net fires more than usual.

(check ALL that apply)

ABKC-D-011 — One documented rare edge case: if the auto-refund itself fails (payment company outage), the office fixes it manually from the audit log. Accept that as the procedure?

Context: Extremely rare (two systems must fail back-to-back). The alternative is building more automation before launch.

Dane's recommendation (one-tap option in the app): Accept — manual procedure is fine

Notes (optional):

§6 — 🧭 Business & platform decisions (~10 min)

The bigger-picture calls: domains, the old systems, accounts, and timing.

ABKC-D-012 — Domain strategy at launch: what happens to abkcdogs.com and abkcdogs.net?

Context: Today, abkcdogs.com redirects to the OLD WordPress site on abkcdogs.net. At launch we point abkcdogs.com at the NEW site. The open question is the old .net site: redirect it permanently to the new site (one clean brand, best for Google ranking), or keep it alive alongside (splits your search ranking and confuses members).

Dane's recommendation (one-tap option in the app): Redirect everything to the new site on abkcdogs.com

Notes (optional):

ABKC-D-013 — The legacy back-office system (the old database staff use today): how long does it stay?

Context: The new site is the source of truth for everything new. The legacy system stays read-only for reference during transition. Sunsetting it sooner = one system, less confusion; later = longer safety net.

Notes (optional):

ABKC-D-014 — Team documentation: pay for a documentation product, or use the free setup we already have?

Context: Procedures and training docs need one official home before staff training. Option 1: the free system the team already uses day-to-day (works today, costs nothing new). Option 2: Confluence — a paid documentation product some organizations prefer (adds a monthly cost per person). The board should make this call before training begins.

Dane's recommendation (one-tap option in the app): Free setup we already have

Notes (optional):

ABKC-D-015 — Payment accounts: whose Stripe and PayPal BUSINESS accounts process real member money at launch?

Context: Testing uses sandbox accounts. For launch, real payouts flow to ABKC's actual Stripe + PayPal business accounts — we need to confirm who owns/controls those and who hands Dane the production credentials (stored securely, never in documents).

Notes (optional):

ABKC-D-016 — Extra login security (a second verification step) for ADMIN accounts: before launch, or within 30 days after?

Context: Admin accounts can approve registrations and see member data. Today they're protected by password + Google sign-in. Adding a second step (code to phone) is planned either way.

Dane's recommendation (one-tap option in the app): Within 30 days after launch

Notes (optional):

ABKC-D-017 — Accessibility fixes (screen-reader labels, image descriptions — 22 items found by audit): before launch or first 30 days?

Context: None of them stop a member from registering. They matter for members who use screen readers, and fixing them reduces lawsuit risk under accessibility laws (online businesses are a common target). The industry-typical move is to fix them in the first 30 days after launch.

Dane's recommendation (one-tap option in the app): First 30 days after launch

Notes (optional):

ABKC-D-018 — Office staff training: when can the office manager start the 2-week training rollout?

Context: Training needs a stable system ('frozen' build) and the six policy blanks above filled. The office manager runs her own guide first (~90 min), then trains staff over 2 weeks.

Exact day/time if custom:

ABKC-D-019 — Before real members use the site, what do YOU personally insist on checking?

Context: This defines your personal review gates — the things that must pass YOUR eyes, not just Dane's.

(check ALL that apply)

Anything else you want eyes on:

ABKC-D-024 — Top-level access: besides Dane, who should hold full admin keys — and do you want your own copy of the registry data?

Context: Full admin can see everything and change anything (today: Dane; the office role is deliberately limited). Separately, you can get a read-only spreadsheet export of dogs/owners/registrations whenever you want — including as a standing monthly email to you.

(check ALL that apply)

§7 — 🚀 Launch posture — your sign-off path (~6 min)

The payment system passed an independent production-readiness review and live production checks (the full scorecard is in the owner package), and two structural demo videos exist. The remaining polish is in our internal test tooling, not the member-facing system. Pick how you want to get to sign-off.

ABKC-D-020 — Which sign-off path do you want?

Context: Option A: sign off on current evidence — members can be live ~24h after DNS access. Option B: Dane records a 30–60 min narrated video completing real test-mode payments first; you watch, then sign — ~48h. Option C: wait for the fully-automated test suite to be polished and re-scored — about 7 days.

Notes (optional):

ref: owner package cover letter, Three Options

ABKC-S-001 — Gut check: how ready does the SITE feel for real members?

Not ready [ ] 1 [ ] 2 [ ] 3 [ ] 4 [ ] 5 Fully ready

Notes (optional):

ABKC-S-002 — How ready does the OFFICE feel to run it (with the training plan above)?

Not ready [ ] 1 [ ] 2 [ ] 3 [ ] 4 [ ] 5 Fully ready

Notes (optional):

ABKC-S-003 — How much do you trust the DATA (dogs, pedigrees, points) as it stands?

Low trust [ ] 1 [ ] 2 [ ] 3 [ ] 4 [ ] 5 Full trust

Notes (optional):

ABKC-T-001 — Whatever you scored LOWEST above — what would raise it?

Example: The one thing that would most increase your confidence…

Your answer:

ABKC-A-002 — Making the new site live (pointing the abkcdogs.com web address at it) happens ONLY after sign-off.

Context: Nothing goes live to members until the sign-off form is signed and ownership hands over control of the web address. Your answers here don't flip any switches.

If flagged, what would you change?:

§8 — 🔒 Security & risk — what we found and what we're doing (~6 min)

Full transparency: the security review found these items. Each one already has a fix in motion — you're being told because it's your club. Endorse the fix, or flag it if you want it handled differently.

ABKC-A-003 — Kids' academy files were publicly visible — being locked down.

Context: The storage area holding the junior-handler academy's learning materials was set so anyone on the internet could list what's in it (a child-privacy red flag, even though no child's personal information was in there). Fix: it's being locked down so only the right signed-in people can open those files. This lands before launch.

If flagged, what would you change?:

ABKC-A-004 — Newsletter subscriber emails were visible to any signed-in member — being locked to self-only.

Context: A permissions setting was too loose: any logged-in member could technically pull up the full newsletter subscriber email list. Fix: each member can only ever see their own record. This lands before launch.

If flagged, what would you change?:

ABKC-A-005 — Bot protection on login is built but not yet switched on — it will be on before launch.

Context: After 3 failed login attempts a human-verification check appears. The pieces exist; the final wiring is in the pre-launch list.

If flagged, what would you change?:

ABKC-A-006 — Internal money/marketing dashboards were reachable if you knew the exact address — being fenced to admins only.

Context: Six internal reporting screens (revenue pipeline, customer-relationship dashboards) could be pulled up by anyone who knew the precise web address. Fix: they're being restricted to admin accounts only. No sign anyone ever found them.

If flagged, what would you change?:

ABKC-A-007 — A backup-recovery fire drill hasn't been rehearsed yet — it's scheduled before launch.

Context: Backups exist; what hasn't happened is a full fire-drill proving how fast we can bring everything back from a backup. One rehearsal on a test copy of the site is on the pre-launch checklist.

If flagged, what would you change?:

ABKC-A-008 — Card data never touches ABKC's servers.

Context: Members pay on Stripe's or PayPal's own secure pages. ABKC never sees, stores, or processes card numbers — this is the industry-standard setup that keeps ABKC's liability minimal. The one-page compliance statement in the owner package covers PCI, member privacy, and child-privacy posture.

If flagged, what would you change?:

§9 — 📊 For your awareness — engineering status (no input needed) (~3 min)

The rest of the engineering tracker, translated. Nothing here needs a decision from you — it's the honest state of the work. One optional comment box at the end.

ABKC-I-001 — DONE recently

Context: The login problem on Apple devices is fixed and double-checked · Approved registrations now automatically email the member their certificate, pedigree and receipt · The office can now clear out abandoned half-finished applications · Every payment leaves a complete paper trail · All of the site's building blocks are up to date.

(status report — nothing to answer)

ABKC-I-002 — IN PROGRESS

Context: One stubborn browser quirk on Firefox is being polished (members on Chrome, Safari and Edge are unaffected) · The historical championship-points import is staged — it starts once you answer the points question above.

(status report — nothing to answer)

ABKC-I-003 — QUEUED (pre-launch or first 30 days)

Context: A launch-day traffic stress test · Page-speed monitoring · A weekly automatic check that the old and new systems still agree · Loading historical photos and payment records · Registering the site with Google so members can find it in search.

(status report — nothing to answer)

ABKC-T-002 — Any comments or questions on the engineering status above? (optional)

Your answer:

§10 — 🤝 Your joint test session with Dane (~5 min)

One 45-minute live session, you + Dane on a call: he submits a registration listing you as co-owner, the invitation lands in your email, you sign on screen, and we watch the whole dual-owner flow work end-to-end. It also settles a real design question: whether payment is collected before or after the co-owner signs.

ABKC-D-021 — When works for the 45-minute session?

Exact day/time if custom:

ABKC-V-018 — Session readiness — check what's true:

(check ALL that apply)

ABKC-D-022 — Do you already have an ABKC member login on the new site?

Context: Either answer is fine — if you don't, the session deliberately tests the 'create account from invitation' path, which is one of the things we want to validate.

Notes (optional):

ABKC-A-009 — During the session we'll record one key observation: whether the system asks for payment BEFORE or AFTER the co-owner signs.

Context: It's currently undocumented which way the system behaves — observing it live settles the design question and unblocks the automated test that protects this flow forever after.

If flagged, what would you change?:

§11 — ✍️ Final sign-off (~3 min)

Last step. Your answers route back to Dane, become the policy + verification record, and anything marked 'discuss live' lands on the joint-session agenda automatically.

ABKC-V-019 — I reviewed this pack and my answers reflect my actual knowledge of ABKC operations.

If correction needed, what's the real state?

Your answer:

ABKC-T-003 — Anything we missed? Any question YOU have for Dane?

Example: Open floor…

Your answer:

ABKC-T-004 — Your name as you'd sign it + today's date.

Example: James Cooper — 2026-06-__

Your answer:

Appendix — question index (machine-generated)

ID Type Section
ABKC-V-001 confirm Welcome — how this works
ABKC-D-001 choice Welcome — how this works
ABKC-V-002 confirm Breed standards, judges & pedigrees
ABKC-V-003 confirm Breed standards, judges & pedigrees
ABKC-V-004 text Breed standards, judges & pedigrees
ABKC-V-005 confirm Breed standards, judges & pedigrees
ABKC-V-006 confirm Breed standards, judges & pedigrees
ABKC-V-007 confirm Breed standards, judges & pedigrees
ABKC-D-002 choice Breed standards, judges & pedigrees
ABKC-V-008 confirm Registrations, pricing & points
ABKC-V-009 confirm Registrations, pricing & points
ABKC-D-023 choice Registrations, pricing & points
ABKC-V-010 choice Registrations, pricing & points
ABKC-D-003 chips Registrations, pricing & points
ABKC-V-011 confirm Registrations, pricing & points
ABKC-V-012 chips Registrations, pricing & points
ABKC-V-013 confirm SOP verification — what's documented vs. how ABKC really works
ABKC-V-014 confirm SOP verification — what's documented vs. how ABKC really works
ABKC-V-015 confirm SOP verification — what's documented vs. how ABKC really works
ABKC-V-016 confirm SOP verification — what's documented vs. how ABKC really works
ABKC-V-017 text SOP verification — what's documented vs. how ABKC really works
ABKC-A-001 ack SOP verification — what's documented vs. how ABKC really works
ABKC-D-004 text Office policy decisions (the six blanks)
ABKC-D-005 choice Office policy decisions (the six blanks)
ABKC-D-006 choice Office policy decisions (the six blanks)
ABKC-D-007 choice Office policy decisions (the six blanks)
ABKC-D-008 text Office policy decisions (the six blanks)
ABKC-D-009 chips Office policy decisions (the six blanks)
ABKC-D-010 chips Office policy decisions (the six blanks)
ABKC-D-011 choice Office policy decisions (the six blanks)
ABKC-D-012 choice Business & platform decisions
ABKC-D-013 choice Business & platform decisions
ABKC-D-014 choice Business & platform decisions
ABKC-D-015 choice Business & platform decisions
ABKC-D-016 choice Business & platform decisions
ABKC-D-017 choice Business & platform decisions
ABKC-D-018 date Business & platform decisions
ABKC-D-019 chips Business & platform decisions
ABKC-D-024 chips Business & platform decisions
ABKC-D-020 choice Launch posture — your sign-off path
ABKC-S-001 scale Launch posture — your sign-off path
ABKC-S-002 scale Launch posture — your sign-off path
ABKC-S-003 scale Launch posture — your sign-off path
ABKC-T-001 text Launch posture — your sign-off path
ABKC-A-002 ack Launch posture — your sign-off path
ABKC-A-003 ack Security & risk — what we found and what we're doing
ABKC-A-004 ack Security & risk — what we found and what we're doing
ABKC-A-005 ack Security & risk — what we found and what we're doing
ABKC-A-006 ack Security & risk — what we found and what we're doing
ABKC-A-007 ack Security & risk — what we found and what we're doing
ABKC-A-008 ack Security & risk — what we found and what we're doing
ABKC-I-001 info For your awareness — engineering status (no input needed)
ABKC-I-002 info For your awareness — engineering status (no input needed)
ABKC-I-003 info For your awareness — engineering status (no input needed)
ABKC-T-002 text For your awareness — engineering status (no input needed)
ABKC-D-021 date Your joint test session with Dane
ABKC-V-018 chips Your joint test session with Dane
ABKC-D-022 choice Your joint test session with Dane
ABKC-A-009 ack Your joint test session with Dane
ABKC-V-019 confirm Final sign-off
ABKC-T-003 text Final sign-off
ABKC-T-004 text Final sign-off

Totals: 62 items · 57 requiring your input · 11 sections.

Source-of-truth: C:/Users/dcoop/ecosystem-abkc/abkc-website/.ai-notes/james-gate-pack-2026-06-10/questions.abkc.json · rendered 2026-06-10 · derived formats (HTML/PDF/DOCX) regenerate from this Markdown · per doc-format-strategy.md

📝 My notes

Auto-saves to this browser. Survives reloads. Click Export to download as .md.
Saved