Adventive Engineering

Plans, runbooks, and platform standards for Adventive Platform Engineering.

Projects Platform standards Working with Claude

Single source of truth for Adventive Platform Engineering plans, runbooks, architecture reviews, and standards. Authored by Jeffrey Lambert, produced through Cowork sessions, delivered as WeasyPrint PDFs alongside the source Markdown.

Layout

Adventive Engineering/
├── projects/        Time-bounded engineering work — migrations, rebuilds, rollouts.
├── platform/        Evergreen standards and references — SOPs, vendor practices.
├── _templates/      Project skeleton + PDF house style. Copy from here when starting.
├── _shared/         Cross-project diagrams and vendor docs. Reference, not output.
└── _archive/        Closed-out projects retained for history.

Project skeleton

Every project under projects/ follows this structure once it matures:

projects/<project-name>/
├── README.md                          One-paragraph status, owner, links.
├── 00-context.md                      Problem, motivation, scope, success criteria.
├── 01-architecture-assessment.md      Current state with diagrams.
├── 02-code-updates.md                 Diffs, migrations, refactors.
├── 03-deployment-management.md        How it ships, observability (New Relic).
├── 04-runbook.md                      How to operate it.
├── 05-appendix.md                     References, inputs, raw notes.
├── Adventive_<Project>_<DocType>.pdf  Final deliverable, WeasyPrint.
├── decisions/                         Dated ADRs: 2026-MM-DD-<slug>.md.
├── handoff/                           Kickoff prompts for Claude Code or contractors.
├── code/                              Working code (mirror, not source-of-truth).
└── inputs/                            Source materials, exports, snapshots.

Start a new project by copying _templates/project-skeleton/ and renaming.

Active projects

Project	Status	Folder
Admin Dashboard Cloudflare Migration	Plan delivered	`projects/admin-dashboard-cf-migration/`
Stripe Billing Transition	Plan delivered	`projects/stripe-billing-transition/`
Public API Cloudflare Migration	Implementation handed off to Claude Code	`projects/public-api-cf-migration/`
Google Data Studio Connector	Plan delivered (V8 migration)	`projects/google-data-studio-connector/`
Cloudflare Tunnel Rollout	Plan delivered — pending implementation	`projects/cloudflare-tunnel-rollout/`

Platform standards

Area	Folder
Cloudflare Workers SOP (naming, wrangler, secrets, QA, DR)	`platform/cloudflare/workers/`
Cloudflare Tunnel reference (post-rollout)	`platform/cloudflare/tunnel/`

Future areas under platform/cloudflare/: access/, pages/, r2/, d1/, zero-trust/. Add a new subfolder per service rather than letting one folder grow unbounded.

House style

All engineering PDFs use the WeasyPrint HTML/CSS style defined in _templates/STYLE.md. Do not use Quartz, macOS print, or LibreOffice. The CSS is fixed; copy and adapt the HTML source for each project.

Conventions

Folder names: lowercase kebab-case. No spaces.
PDF filenames: Adventive_<Project>_<DocType>.pdf in TitleCase with underscores.
Decision records: decisions/YYYY-MM-DD-<slug>.md, append-only.
Observability: every 03-deployment-management.md references New Relic.

You’re reading the published version: this content is rendered by Astro Starlight on Cloudflare Pages at docs.adventive.dev, gated by Cloudflare Access bound to JumpCloud. See projects/engineering-docs-site/ for the build/deployment design.