pl8ypus

Builder Log

Build notes from governed AI systems work.

The builder log tracks what shipped, what broke, what changed, and what comes next across the pl8ypus AI builds. It is a public record of the work behind the demos.

Read latest note View active builds

Latest Note

Building a secured review layer for Eloqua form protection.

Product build / June 2026

Building a secured review layer for Eloqua form protection

How a Cloudflare Turnstile, Worker, KV, and Access proof of concept became a secured review workflow for enterprise Eloqua form submissions.

Published
  • Cloudflare Turnstile verified server-side by a Worker
  • KV-backed review queue for failed, suspicious, and simulation records
  • Cloudflare Access secured dashboard and protected API flow
  • Accept, reject, and approved forwarding into Eloqua
  • Exact captured HTML field names preserved during forwarding
Read the build note →

Previous Note

Builder Log 003 / May 2026

Separating the Public Demo from the Live Dashboard

Why Audience Finder AI now has two separate pages — a clean public demo with zero API calls and a live dashboard that controls the Worker-backed review loop. Verified boundary, internal notice added, deferred auth noted honestly.

Published
  • Public page: simulated demo, localStorage only, zero API calls
  • Dashboard: live Worker status, pending queue, memory, accept/reject
  • JS boundary verified clean in both directions by grep
  • Internal notice banner added to dashboard
  • Auth protection deferred and noted honestly
Read Builder Log 003 →

Previous Entry

Builder Log 002 - Turning Audience Finder AI into a Protected Product.

Builder Log 002 / May 2026

Turning Audience Finder AI into a Protected Product

What changed when a portfolio demo became a controlled AI workflow: Cloudflare Access authentication, admin-proxy Worker for server-side writes, protected manual review, controlled candidate discovery, and production release discipline.

Published
  • Admin dashboard moved behind Cloudflare Access
  • Admin-proxy Worker: browser never receives token
  • Protected manual review: Accept / Reject / Watch
  • Controlled candidate discovery: deterministic seed pool, max 5
  • Read-only audit log from KV review history
Read Builder Log 002 →

Editorial Standard

The log is not hype. It is delivery evidence.

Decision

What changed

Each note should make the architecture or delivery decision clear.

Control

What became safer

Review states, audit trails, rollback paths, QA, and validation matter as much as features.

Evidence

What can be shown

Screens, demos, diagrams, code changes, and build notes should support the claim.

Next

What happens next

Every note should end with a controlled next step instead of vague momentum.

Log Index

Build records will stack here.

001

Active

Turning pl8ypus into an AI builder site

The foundation note covering positioning, static site structure, compiled CSS, navigation, contact modal, active build pages, visual evidence panels, lightbox previews, and the move toward proof-led AI system demos.

Read log entry →

Log Categories

The log tracks progress, decisions, controls, and lessons.

Build

Delivery

Pages, workflows, scripts, demos, releases, and visible system improvements.

Architecture

Architecture decisions

Build-route decisions, stack choices, governance decisions, and trade-offs.

Reality

Risks and corrections

Bugs, wrong turns, overbuild risk, data issues, failed assumptions, and corrective action.

Next

Controlled next steps

The next controlled step, not a vague backlog.

Contact

Want to discuss the build direction?

Use the signal form for demos, speaking requests, collaboration, or practical AI build conversations.