Audience and language
Name the Peru users, service area, devices, task, accessibility needs, English/Spanish scope, translation reviewer, and assisted-support route.
The packet is not a form and does not approve work. It gives the first technical conversation enough real context to separate engineering tasks from provider, local-business, and professional decisions.
Current pages, screenshots, messages, sample records, provider documentation, invoice examples with sensitive data removed, staff notes, complaint cases, and reports expose the real work better than a generic feature list.
Name the Peru users, service area, devices, task, accessibility needs, English/Spanish scope, translation reviewer, and assisted-support route.
Describe service, availability, price display, currency, selected provider, payment states, invoice/document handoff, fulfillment, refunds, and claims.
List necessary fields, purposes, roles, databases, current systems, vendors, locations, retention, support access, source authority, and known risks.
Assign business, Spanish, data, payment, tax, invoice, consumer, fulfillment, support, technical, acceptance, release, incident, and rollback owners.
Provide current source/access, workflows, content, analytics, failures, provider references, records, and what must stay available.
Mark items for authority research, provider confirmation, qualified Peru review, data recovery, integration discovery, or a product decision.
Define devices, language cases, data requests, transaction/document failures, staff actions, accessibility, security, performance, and live proof.
State backup, staging, approval, cutover, rollback, monitoring, reconciliation, support, documentation, and outcome-review needs.
Faith Forge Labs reviews scope, authorization, screening, safety, lawful delivery, timing, source authority, and verification requirements before any Peru-connected work begins.