NZ context packet
The client records the workflow, decision, examples, deadline, owner, and constraints during its working day. A short narrated screen recording can remove hours of ambiguity.
Map / Delivery relay
Use the time-zone gap as a relay.
New Zealand and the eastern United States rarely share a full workday. The delivery system therefore has to move decisions forward without relying on constant meetings.
US build window
Faith Forge Labs reviews the packet, records assumptions, implements the bounded change, and prepares evidence while New Zealand is outside its normal day.
Review packet
The next packet contains the changed route, screenshots or test evidence, open decisions, known limits, and exact steps for the client to review.
Decision return
The client accepts, corrects, or stops the route. High-impact releases use an agreed overlap window and named rollback owner rather than the ordinary relay.
A decision packet should be answerable.
“What do you think?” creates delay. A good packet states the decision, why it matters now, two or three viable choices, the recommended choice, evidence, impact of waiting, and the person authorised to answer. If the question cannot be compressed, the underlying work may need discovery before development.
Delivery controls stay the same across distance.
- A written scope and explicit exclusions.
- A durable source repository and named deployment target.
- Access granted to the minimum necessary systems.
- Backups and a verified rollback route before material release.
- Static and live validation appropriate to the affected path.
- A change record showing what changed, why, who authorised it, and what evidence passed.
- A monitoring period and named owner for incidents or unexpected effects.
When synchronous overlap is necessary.
Use a shared window for production cutovers, sensitive access, incident response, complex discovery, stakeholder conflict, or a decision that cannot safely wait. The exact window is agreed per project because daylight-saving changes can shift the relative time. Dates and deadlines should include the city or UTC offset, not only “tomorrow”.
Direct model: Logan Pendragon leads the engagement and engineering work. If a specialist or third-party service is proposed, the role and data path should be disclosed before access or delivery.
What the client still owns.
The New Zealand organisation owns its business decisions, user acceptance, regulatory interpretation, internal communication, production authority, and the accuracy of the operational examples it provides. Faith Forge Labs owns the agreed engineering work, evidence, documentation, and truthful escalation of risk or uncertainty.
Prepare the relay
Send one bounded operational problem.
We will respond with the questions needed to form a buildable route.