sjbower.com
Technical Marketing practice and the starting point for CI and lab exploration.
Put the story
to the test.
My Cloudflare environment connects identity, protected access and security evaluation to a concrete customer workflow. Explore the architecture, follow a guided exercise and inspect what the evidence actually establishes.
Cloudflare Access sign-in is required for the lab, demos and detailed guides. Access is limited to approved reviewers.
One domain. Separate purposes.
Cloudflare Access
Sign-in and approval protect the CI method and the hands-on environment.
lab.sjbower.com
Lab portal, guided setup, demonstrations, evidence and operating instructions.
READINESS / BASELINE OCTOBER 31, 2026Know what
Know what
has been tested.
Recorded as verified: protected human access and local Python, Terraform mock-provider and Rust checks.
Still pending in the recorded baseline: native AI enforcement tests and deployment of the Terraform sample to Cloudflare. A working website or local test does not establish those controls.
Current control-test status: UNKNOWN until the protected readiness record and new test evidence confirm it.
Check the evidence and readiness record ↗HANDS-ON / CODE AND EVIDENCEBuild the demo.
Build the demo.
Show the evidence.
Automate the test. Define access. Check the results. Each tool has a clear role and a measurable outcome.
Make tests repeatable.
Start isolated test services, send requests with time limits and collect the results. Python handles setup and cleanup. Three unit tests and nine scenarios passed.
Define who can connect.
Describe an Access application and named-user policy in Terraform. Six tests passed with a mock provider. The configuration has not been deployed to Cloudflare.
Catch incomplete results.
Use Rust to reject missing cases, unexpected results and unsupported Cloudflare claims. Nine unit tests passed. The verifier checks consistency; it does not prove authenticity.
Scott repeated the integrated check successfully. The next exercise is an independent code change, diagnosis and recovery. Inspect the code and walkthrough ↗
GUIDES AND DEMONSTRATIONS
Choose your next step.
Open the code, follow the security evaluation or review the go-to-market samples. Sign-in required. Each guide distinguishes completed work from proposed outcomes.
01Lab portalChoose a reviewer, builder or operator route02Setup walkthrough28 setup steps with checks and troubleshooting03Programming labPython, Terraform, Rust, source and negative tests04TPMM work samplesResearch, campaign, seller card, product and launch work05Evidence and readinessVerified results, proposed work and remaining tests06Project presentation12 slides, 15 minutes, with speaker notes07Environment inventoryArchitecture, services, access and the two-hour agenda08Email security guideConfigured baseline and trial-dependent tasks09Operations and troubleshootingFind logs, diagnose failures and recover10Server access instructionsProtected SSH and browser desktop guidance
How the lab supports Technical Marketing.
Product validation establishes what can be claimed. Repeatable demos make the use case observable. Evaluation plans and evidence help customers assess fit. Guides and presentations turn the technical work into reusable field content.
Return to the eight responsibilities →