L3dgr Beta — Participant Quick Start

Onboarding steps for approved participants. Legal terms are in the beta participation PDF; this page is operational guidance only.

Prerequisites Test Script Mismatch Glance Key Delivery First Seal Timeline Feedback Report a Bug Support Graduation

Before you begin

Confirm these items before checkout and your first seal workflow.

Docker Desktop

Installed on the OS you listed in your application.

Approved application

Promotion code received by email after verification and review.

Checkout window

Complete checkout within seven days of your offer email (three monthly invoices at $0, then standard Pro rates unless you cancel).

Sample data

Use synthetic or non-production sample data unless your organization has explicitly approved production datasets on your own infrastructure.

Required test script

Use the L3dgr Dashboard workbench (the Lobby Auditor shell does not include the full Jobs tab). Submit blocking issues via the support form (L3dgr Beta) or the bug template below.

Required (activation and graduation)

These items satisfy mandatory participation in the beta participation PDF (L3DGR-BETA-1.9).

  1. Activation seal: Select a sample directory, run Seal preflight, confirm seal, verify the sealed tree. Save the Readout excerpt.
  2. Independent verify: From Readout, run verify on the sealed output and confirm pass/fail matches expectations.
  3. One pipeline journey: Complete one of: file processor sample CSV on /host; live network ingest (Test Connection then Start Ingest, then stop); or a scheduled job (once, interval, or UTC cron) through queue to History. Record job_id.
  4. Support bundle export: Settings → Help & Support → Run Preflight → Download Support Bundle.
  5. Bug report: Submit one structured defect or friction report via support form with program L3dgr Beta (or the email template in Report a bug).
  6. Account readout: Sign in at Plans and Billing and confirm L3dgr Beta checklist items update as you complete surveys, seal, and pipeline.
  7. Graduation readiness: Before week 10, confirm onboarding survey, pulse survey, bug report, first seal, one pipeline journey, and exit survey.

Optional extras

Pause/resume queue and additional connector types after the Required pipeline journey. Not required for graduation.

  1. Queue pause and resume: Pause queue dispatch, enqueue a job, confirm deferred dispatch, then Resume.

Mismatch glance

Scan and Verify freeze a baseline per folder. Later runs compare against that freeze. This is a watch, not a seal. Full operator copy: Operator's Guide.

Key delivery

After checkout, provision your extension API key.

  1. Complete Stripe checkout from your offer email.
  2. Open Key Delivery and copy your F33 API key.
  3. Paste the key into L3dgr Docker Extension Settings (F33_API_KEY).

First seal (activation)

Your beta activation requirement is one completed seal workflow in the L3dgr Dashboard.

  1. Select the dataset or directory you will seal.
  2. Run Seal preflight and resolve any blocking items.
  3. Confirm seal when preflight passes.
  4. Verify the sealed tree and retain the readout for your records.

This wave is Pro (one seat). Lab Operator attestation is not part of this cohort.

Program timeline

Milestones, surveys, and participation checkpoints across the 10-week cohort window.

Week 1

Onboarding survey (emailed after your first seal, or by day 7).

Weeks 2–3

Complete first seal and one pipeline journey (file processor, live ingest, or scheduled job). Billing reminder email covers the three $0 months.

Week 4

First-seal reminder if not yet recorded (day 21).

Week 5

Mid-program pulse survey (structured feedback #1).

Weeks 5–8

Pipeline journey if not already complete; pulse survey around week 5.

Week 6

Participation warning at day 35 if seal or pipeline is missing; final warning day 49; revocation day 56 if either journey is still missing.

Week 10

Exit survey (structured feedback #2).

Graduation

Exit survey + first seal + one pipeline journey may unlock a graduate discount offer by email.

Surveys and feedback

Submit onboarding and exit surveys when emailed. Complete the week-five pulse survey and at least one structured bug report via the support form or email template. Slack is optional community space when invited after checkout.

Graduation

Complete the exit survey, first seal, and one pipeline journey. Graduates may receive a single-use promotion code for paid Pro; terms are in the offer email and participation PDF.

Report a bug

Use the L3dgr support form with program L3dgr Beta, or email l3dgr-beta@fors33.com with this template (copy and fill in). Do not include production secrets, credentials, or unredacted PII.

Subject: [L3dgr Beta] <short summary>

Tier: Pro
Docker Desktop OS and build:
Connector type (file | live network | seal | other):
Schedule kind (manual | once | interval | cron | none):
Job ref (from Readout, if applicable):
Steps to reproduce:
Expected:
Actual:
Readout excerpt (if applicable):
Support bundle: attach l3dgr_support_bundle_v1 JSON from Settings → Help & Support → Download Support Bundle

Support and community

Program contacts, office hours, and billing during the beta window.

Beta support

l3dgr-beta@fors33.com — two business days during beta.

Office hours

Biweekly 30-minute live Q&A; schedule and link are pinned in the private beta Slack #beta-readme after you join.

Known issues

See the cohort status page for confirmed blockers.

Billing

Manage seats and plans at Plans and Billing.

  • Cohort Status
  • L3dgr Beta
  • Operator's Guide