Rooftop Garden — Prototype Delivery Plan

The ask

You'd run the program end to end

The design is fully specified — 17 source documents cover the geometry, plant rendering, mechanics, irrigation, and detail views. What it needs now is someone to drive it to a shipped prototype: sequence the work, bring on and manage a build engineer, hold the cadence, own the handshake between the build and Adam's AI tooling, run quality gates, and coordinate launch. That program-management role is what this plan maps — your workstreams, milestone by milestone.

Delivery model

Who does what

Three roles. You drive; two owners execute. Your first job is to make the two execution seats productive and keep them in sync.

Drives the program

Program Manager

Mia (Resource #2)

Owns delivery of the prototype
Plan, cadence, sequencing, unblocking
Sources & manages the build engineer
Quality gates & milestone sign-off
Risk, change, and launch coordination

Executes the build

Build Engineer

To be sourced & managed by PM

Three.js prototype (Tracks A–E, G)
Geometry, plants, mechanics, irrigation
Detail modals & UI, landing page
Reports into the PM cadence

Executes AI tooling

AI Tooling Engineer

Adam (sponsor + Track F)

Nutrient & plant-management software
Data schema, dosing logic, harvest model
API feeding the live dashboard
Dependency the PM coordinates

Roadmap

Seven milestones

Indicative timeline assumes one build engineer working the prototype tracks in sequence, with Adam's AI tooling running in parallel from mid-program. Your focus shifts at each stage.

Weeks 1–2Setup + M1

M1PoC Validated

Two-track artifact proves chain articulation around the eave and click-to-detail interaction.

Your focus: stand up governance, source the build engineer, confirm the PoC baseline.

Weeks 3–5M2

M2Five-Track System

Scale to five crops, reservoirs, plumbing, exact 14-cube deploy, master toggle.

Your focus: lock the early design decisions (below) to prevent rework; hold first demo review.

Weeks 5–7M3

M3Plant Fidelity Locked

Billboard-texture plants at mature size and density with tuned per-crop palettes.

Your focus: enforce the billboard technique decision; sign off visual quality.

Weeks 7–10M4

M4Mechanical Detail Complete

Axles & bearings, free-hanging deployment below the eave, and the clickable solar-housing interior modal.

Your focus: eave approach is locked to free-hang — steer effort into axle/bearing detail and the housing interior, not another rail redesign.

Weeks 9–12M5

M5Integrated UI & Dashboards

Deploy sliders, unified reservoir, clickable tablet dashboard, 60fps performance pass.

Your focus: broker the data-contract handshake with Adam; run QA against the acceptance checklist.

Weeks 11–15M6 (parallel)

M6AI Tooling MVP

Live EC/pH, water-level, dosing and harvest data served via API into the tablet — no hardcoded values.

Your focus: keep Adam unblocked; coordinate integration between tooling and dashboard.

Weeks 15–16M7

M7Launch

Landing page deployed, playground linked, responsive + accessibility QA passed.

Your focus: coordinate launch, final QA sign-off, and handoff.

Your responsibilities

The program-management work

Every task you'll own to make the prototype happen, grouped into seven workstreams that run across the whole program.

Governance & Planning

Define scope, success criteria, and the definition of "done" per milestone
Own and maintain this roadmap and the backlog
Set up the repo, issue tracking, and working cadence (standups + milestone demos)
Build the stakeholder map and communications rhythm

Resourcing

Scope the build-engineer role and source the right person
Onboard the engineer to the 17 source docs and the design intent
Manage hours/budget and capacity across the two execution seats
Coordinate Adam as the AI-tooling dependency owner

Execution Management

Drive M1–M7 to completion; groom and prioritize the backlog
Run build cadence and demo reviews at each milestone gate
Track progress vs. plan; surface and remove blockers
Manage schedule and dependencies between tracks

Technical Coordination

Facilitate the early design decisions that prevent rework
Own the data-contract handshake between the dashboard and Adam's API
Keep build and AI tooling aligned on the integration point (the tablet)
Escalate technical trade-offs for a sponsor decision when needed

Quality

Coordinate QA against the 16-item acceptance checklist
Verify milestone exit criteria before advancing
Own visual-fidelity and performance sign-off (60fps target)
Track defects to closure

Risk & Change

Maintain the risk register and drive mitigations
Pre-empt the known rework threads (rails/eave, nozzles, plants)
Manage scope changes and their schedule impact
Protect against key-person risk on the AI track

Launch

Coordinate the landing page, preview capture, and deploy
Own responsive + WCAG-AA acceptance for the public page
Run the launch checklist and go/no-go
Handoff and retrospective

Ownership map

Tracks & ownership

You are accountable for all seven tracks landing. These are the doers you'll coordinate on each.

Track	What it delivers	Executes	PM role
A · Foundation & Geometry	Scene, house, chain path, raise/lower, deploy sliders	Build Engineer	Accountable · sequence & unblock
B · Plant Rendering	Billboard plants, textures, lushness, maturity slider	Build Engineer	Accountable · quality sign-off
C · Rails & Mechanics	Brackets, slope rails, axles/bearings, free-hang deploy (opt. bottom guide)	Build Engineer	Accountable · eave decision locked
D · Irrigation	Reservoirs, hoses, unified tank, drip nozzles	Build Engineer	Accountable · decision owner
E · Detail Modals & UI	Cross-section modal, controls, tablet dashboard, perf	Build Engineer	Accountable · integration point
F · AI Nutrient/Plant Tooling	Schema, dosing, harvest model, API, integration	Adam	Coordinates dependency & handshake
G · Landing Page & Launch	Public page, preview, deploy, QA	Build Engineer	Accountable · launch owner

Program Manager (you) — accountable across all Build Engineer — prototype execution Adam — AI tooling

Steer early

Decisions that prevent rework

The source prompts show the design changing its mind mid-build. One is now locked (eave mechanics → free-hang); locking the rest before M2–M4 is the single biggest thing you can do to protect the schedule.

Eave mechanics — DECIDED: free-hang

Locked: the site is calm, so the deployed chain hangs freely below the eave. No wall rails, no cantilever cage — both dropped as unnecessary weight, cost, and eave load. Optional light bottom-alignment guide only if the vision system later needs tighter cube positioning. Not to be reopened.

Drip-nozzle location moves three times (ridge → fixed → into housing)

Call: route nozzles inside the housing from the start, before plumbing is built.

Procedural plant geometry is a dead end

Call: use the billboard-texture technique immediately — don't repeat the failed geometry passes.

AI tooling needs a stable data contract

Call: lock the dashboard data schema (Adam's Track F1) before the tablet dashboard is finalized, so integration is clean.

Where you'd start

First 30 days

A concrete on-ramp so the program has momentum from week one.

Absorb the design. Work through the 17 source docs and the existing PoC; confirm what's already validated (chain articulation + click-to-detail).
Stand up governance. Set up the repo, issue board, milestone gates, and a weekly demo cadence.
Source the build engineer. Scope the role, run the search, and onboard them to the design intent.
Lock the remaining rework-prevention decisions with Adam before build scales past M1 — eave mechanics is already settled to free-hang.
Align the AI handshake. Agree the dashboard data schema with Adam so Tracks E and F converge cleanly.
Publish the plan. Put this roadmap in the repo as the shared source of truth and start tracking against it.