Senior Full-Stack Developer — WordPress, WooCommerce, Stripe, Lovable & Supabase Repair

CHILDREN'S UNIVERSITY ACHIEVEMENT CORPORATION (CUAC) HARXGN Systems Repair, Integration, Security, Launch and Performance Agreement Revised Consolidated Agreement — October 26, 2026 Organization: Children's University Achievement Corporation (CUAC) Platform: HARXGN / ReadBright Path Contractor Position: Senior Full-Stack Developer Total Fixed Price: $1,000 USD Project Type: One-time, fixed-price engagement Completion Target: Seven consecutive calendar days, including weekends and holidays Post-Launch Support: Seven consecutive calendar days after CUAC's written operational acceptance Contract Platform: Upwork 1. Project Purpose and Required Outcome Children's University Achievement Corporation (CUAC), a U.S.-based nonprofit literacy organization, seeks an experienced, hands-on senior full-stack developer to complete the repair, security stabilization, configuration, integration, and launch preparation of its existing HARXGN online literacy platform. The existing technology environment includes: WordPress and Hostinger Cloudflare, DNS, and SSL WooCommerce and Stripe GiveWP donations Lovable/HARXGN and React Supabase and PostgreSQL Authentication, authorization, and transactional email Protected instructional services and learner records APIs, payment webhooks, and automated course entitlements This is a repair, integration, completion, and operational verification engagement—not an investigation-only assignment, redesign, rebuild, or testing-only project. Previous technical specialists have investigated substantial system problems, performed partial repairs, and prepared extensive findings, test results, and handover documentation. The contractor must use the existing findings and records to avoid unnecessary duplication of completed investigations and repairs. The required outcome is a secure, fully functioning, integrated, operational, and verified launch-ready literacy platform. Reports, audits, recommendations, prepared but unconnected code, isolated demonstrations, and descriptions of unfinished repairs do not constitute completed contractual deliverables. Required repairs must be implemented, connected, demonstrated, and verified in the approved operational environment. CUAC is engaging the contractor for measurable operational results, not merely time spent or effort expended. 2. Mandatory Qualifications and Pre-Engagement Readiness The named lead contractor must demonstrate substantial hands-on experience with the technologies and responsibilities required by this engagement. Required Qualifications The contractor must: Demonstrate practical experience with WordPress, WooCommerce, Stripe integrations, Cloudflare, React applications, Supabase, PostgreSQL, authentication, database security, APIs, and webhooks. Identify any required technology with which the contractor lacks direct hands-on experience. Demonstrate the ability to repair and connect existing systems rather than defaulting to rebuilding them. Personally perform or directly verify substantial technical repair work. Explain the proposed approach to payment-to-learning-entitlement integration. Demonstrate sound account security, credential handling, and access-management practices. Confirm availability during the agreed seven-day project schedule, including weekends. Identify all additional personnel and their responsibilities. Disclose material dependencies, technical limitations, availability restrictions, and foreseeable delivery risks. Confirm the ability to perform the agreed scope within the $1,000 fixed-price budget without unauthorized additional charges. General assurances, immediate acceptance of all conditions, or unsupported claims of expertise shall not substitute for demonstrated technical understanding. Mandatory Pre-Start Readiness Before technical work begins, the contractor and CUAC must document: The approved technical scope and acceptance requirements. The essential systems requiring access. The status of required platform invitations. The approved team roster. Completed NDAs. Known configuration and integration dependencies. The approved first-day repair sequence. The planned seven-day execution schedule. The required active-repair and backup coverage hours. The agreed official start date. The contractor must check invitation delivery, including spam and junk folders, before reporting that access is unavailable. The contractor must not bypass a missing invitation through password recovery, personal-account login, or unauthorized security changes. Readiness and Deadline Feasibility The seven-day completion commitment shall begin only after mutually documented readiness and CUAC's provision of the agreed essential access and documentation. The contractor must disclose any known reason the proposed timeline is infeasible before accepting the contract. CUAC is not required to authorize additional funding, a reduced scope, or a deadline extension merely because the contractor subsequently discovers that the original commitment was unrealistic. Any revised schedule must be expressly approved through Upwork. 3. Required Systems and Repairs A. Security, Ownership, and Recovery The contractor shall: Verify usable backups and documented rollback procedures before material changes. Review the September 11, 2026 WordPress security incident using existing evidence. Correct remaining in-scope unauthorized access, vulnerable components, malicious persistence, exposed credentials, improper privileges, and access-control defects. Verify CUAC's ownership and authorized control of WordPress, Hostinger, Cloudflare, Lovable, Supabase, Stripe-connected systems, and organizational email. Identify the previously reported additional or external database, determine its actual role, and safely correct or isolate harmful connections when authorized. Preserve legitimate customer, learner, organizational, donation, and financial records. Document completed security corrections and demonstrate their effectiveness. Preserve existing authorized website builders, administrators, emergency recovery personnel, and approved technical collaborators. Maintain before-and-after records of approved access and security changes. A security audit without the required corrective action does not constitute completion. B. WordPress, WooCommerce, Stripe, GiveWP, and Email Repair and verify: Website availability and store functionality. Approved reading-kit product listings. WooCommerce checkout and payment processing. The correct CUAC-authorized Stripe connection and payment gateway. Webhooks and applicable subscription processing. Orders, purchase confirmations, and receipts. Refunds, cancellations, renewals, and failed-payment handling. Customer-account functionality. The unintended $0 product or unauthorized free-access problem. GiveWP donations, receipts, confirmations, and thank-you messages. Transactional email configuration and delivery. Authorized redirects, checkout completion, and notifications. Separation of donations from program purchases. GiveWP donations must not generate HARXGN course entitlements. No unauthorized changes may be made to pricing, payout destinations, taxes, shipping, subscription terms, or financial settings. CUAC must determine which Stripe account is authoritative before any production switching, reconnection, or other account-level payment configuration changes. The contractor may conduct authorized read-only investigation of existing connections but may not independently select, replace, or activate a Stripe account. CUAC's reading kits and program enrollment are not currently open for public sales. The contractor must not activate public purchasing or represent the system as launch-ready before written authorization. C. Lovable/HARXGN, Supabase, Identity, and Access Repair and verify: The live HARXGN/Lovable application. Correct connection to the approved production database and backend. Registration and authentication. Age-band intake. Guardian consent where required. Administrator and staff permissions. Secure user roles and access restrictions. Prevention of unauthorized or free learning access. Protected instructional content and lessons. Pre-assessments, post-assessments, and learner progress. Results, certificates, and teacher notes. Return-to-dashboard functionality. Applicable access expiration. Separation of production and isolated test environments. The duplicate in-app Stripe checkout must be safely removed or disabled only after the approved WooCommerce checkout and purchase-to-access integration have been verified as working. No unauthorized application route may generate learning entitlements. No production database deletion, material migration, privilege change, or modification of real learner records may occur without CUAC's separate written authorization. D. Automated Payment-to-Learning-Access Integration The contractor must implement, repair, and verify the complete automated process: Approved WooCommerce Purchase → Verified Stripe/WooCommerce Payment → Customer Identity → HARXGN/Supabase Account → Correct Learning Entitlement → Protected Course Access Authoritative data sources must be identified and documented for: Orders and qualifying products. Payment and subscription status. Customer and learner identities. Entitlements and expiration. The integration must correctly process: Successful payments. Renewals where applicable. Failed payments. Cancellations. Refunds. Entitlement expiration. Duplicate and repeated events. Unauthorized purchases must not create learning access. Repeated events must not create duplicate benefits, accounts, or promotional slots. Entitlements must be created and controlled through trusted server-side processes, not browser-controlled access grants. E. Founding 25 Promotional Offer Implement and verify CUAC's Founding 25 requirements: The first 25 eligible participants making a qualifying CUAC Reading Kit purchase receive 180 days of promotional program access. The benefit begins on the qualifying purchase date. Each participant may receive the benefit only once. Duplicate processing must not consume additional promotional slots. Refunded or cancelled qualifying purchases must revoke promotional access and release the slot for the next eligible participant under CUAC's approved policy. Donations, digital assessment books, and nonqualifying purchases alone do not qualify. No unauthorized recurring charge may be created. Qualifying reading kits must not be incorrectly excluded. The contractor must demonstrate these requirements through approved test cases before production acceptance. 4. Mandatory Hands-On Participation and Team Accountability The named lead contractor must be personally and actively engaged throughout the seven-day repair period. The contractor must directly perform or hands-on verify approved corrections, integrations, configurations, testing, restoration procedures, and production functionality. Supervision alone, unauthorized delegation, reporting, and administrative coordination do not satisfy the hands-on requirement. Team Identification Before work begins, the contractor must provide: Full name of every participating individual. Individually controlled professional email address. Assigned role and technical responsibilities. Required platform access. Working hours and backup coverage. Signed NDA confirmation. CUAC's written participation approval. Additional engineers, backup developers, project managers, and subcontractors require CUAC's prior written approval before receiving protected information or system access. A signed NDA does not itself authorize access to CUAC systems. Shared personal credentials and use of another team member's identity are prohibited. The lead contractor remains accountable for all approved team members and shall coordinate their work without requiring CUAC to independently manage the development team. Daily Reporting The contractor must provide written daily progress reports through Upwork identifying: Repairs actually completed. Systems and environments affected. Tests performed and results. Before-and-after evidence. Remaining defects and blockers. Next-day priorities and responsible personnel. Proposed changes requiring approval. A progress report without verifiable completed work does not establish milestone completion. 5. Account Ownership, Credentials, and Security Authorization CUAC retains exclusive ownership and recovery control over organizational accounts, systems, domains, databases, financial services, credentials, and intellectual property. All contractor access must follow least-privilege principles through approved individual accounts and delegated access procedures. A. Passwords, Personal Credentials, and Account Recovery Without separate, specific, prior written CUAC authorization, no contractor or team member may: Initiate or complete password-reset procedures. Initiate account recovery. Request CUAC's Yahoo or other personal email credentials. Request authentication codes, recovery codes, security answers, or multifactor authentication secrets. Change passwords, recovery email addresses, telephone numbers, authentication methods, or ownership settings. Bypass multifactor authentication or other security protections. Expand their assigned privileges. Use technical documentation to obtain unauthorized additional access. Access systems through another person's credentials. Initiate recovery of Hostinger, WordPress, WooCommerce, Stripe, Lovable, Supabase, Cloudflare, or organizational email accounts. The presence of account information or recovery details within technical handover documents does not constitute permission to use them. Owner-level recovery and authentication must remain under CUAC's direct control or occur through an expressly approved owner-controlled procedure. B. Access Request Requirements Every access request must identify: The exact platform and account. The individual requesting access. The task requiring access. The minimum necessary permission. The anticipated duration. Operational and security consequences. The method for revoking access afterward. CUAC may approve, deny, limit, or postpone access. Access to one system does not authorize changes to another. General project authorization does not constitute permission to alter account ownership, passwords, privileges, or production configurations. C. Existing Authorized Users All CUAC-approved administrators, website builders, emergency recovery personnel, and legitimate collaborators must remain authorized unless CUAC approves a change. Without prior written approval, the contractor may not: Remove, replace, or disable existing users. Downgrade or expand existing privileges. Cancel existing invitations. Modify ownership or recovery information. Disconnect approved services. Alter security settings. Unexpected changes must be reported immediately and relevant evidence preserved. D. Sensitive Changes Requiring Written Approval Separate written approval is required for: Live financial transactions and refunds. Stripe account switches or payout changes. DNS, SSL, MX, or domain changes. Modification of real learner or customer records. Production database deletion or material migration. Production administrator or user-role changes. Password resets and authentication recovery. Security configuration changes. Pricing, tax, shipping, or subscription changes. Public publishing and deployment. New recurring costs or paid tools. Destructive or materially risky production operations. Approval must identify the specific action and cannot be inferred from general access. E. Incident Reporting Suspected unauthorized access, credential exposure, unexpected permission changes, security incidents, or unintended production modifications must be reported immediately. The contractor must stop affected activity, preserve evidence, and seek CUAC's instructions before further changes, except narrowly defined emergency action previously authorized under an agreed incident-response procedure. Knowingly concealing a material incident or providing materially inaccurate reports constitutes a material breach. 6. Protection During Active Repairs The contractor must remain directly available during agreed repair, deployment, and launch windows. Before each material production intervention, the contractor must document: The exact approved change. Verified backups. Rollback procedures. The agreed work window. Success and failure tests. The responsible engineer and backup. The restoration procedure. No critical production change may proceed without the required safeguards and written authorization. Coverage schedules must be documented in U.S. Central Time. Any agreed continuous coverage must be provided by named, approved personnel. Emergency Restoration For a critical in-scope internal failure during agreed coverage, the contractor must immediately begin corrective work upon written notification. Where an approved, tested rollback or restoration path is available, the contractor commits to restoring the affected function or its verified prior operational state within 60 consecutive minutes after CUAC's written notice. The contractor must identify before the work window any critical system for which such restoration cannot reasonably be guaranteed. A critical failure caused by the contractor's unauthorized actions does not excuse the contractor from immediate remediation responsibilities. The contractor shall document the incident, response, restoration outcome, and supporting test evidence. A temporary rollback may satisfy the immediate restoration requirement, but permanent in-scope corrections remain part of the fixed-price engagement. A genuinely independent external-provider outage is subject to the evidence-based exception in Section 11. Explanations, acknowledgments, and promises to repair later do not constitute completed restoration. 7. Seven-Calendar-Day Completion Deadline and First-Day Checkpoint The completion period is seven consecutive calendar days, including Saturdays, Sundays, and holidays. The clock begins on the mutually recorded written start date after the first milestone is funded and CUAC has provided the agreed essential access and documentation. The contractor must identify known essential dependencies before accepting the contract. Missing prerequisites do not automatically extend the deadline. Any extension must identify: The specific dependency. Its actual effect on completion. Work already completed. The proposed revised deadline. No extension, additional charge, or scope reduction is authorized without CUAC's written approval through Upwork. Mandatory First-24-Hour Checkpoint Within 24 hours of the approved start, the contractor shall provide: Confirmation of accessible approved systems. Identification of unresolved access problems. Confirmation of team assignments. Evidence of initial technical work or a completed repair where reasonably possible. A schedule for the remaining project days. Identification of material delivery risks. Unresolved blockers must be promptly reported. The contractor shall not initiate unauthorized account recovery, password changes, access escalation, or production changes to overcome blockers. Failure to satisfy an applicable first-day requirement may result in immediate suspension pending correction. Such failure does not automatically establish failure of the entire contract or override Upwork's payment procedures. 8. Fixed-Price Milestones and Acceptance Requirements Total Fixed Contract Price: $1,000 USD Milestone 1 — Security Repair and Stabilization Payment: $100 Required outcome: Remaining in-scope security, ownership, access, backup, and recovery problems corrected and retested. Verified rollback evidence delivered. Existing authorized user access preserved unless CUAC approved changes. Milestone 2 — WordPress, WooCommerce, Stripe, GiveWP, and Email Repair Payment: $100 Required outcome: Checkout, payment processing, orders, receipts, refunds, cancellations, donations, transactional email, and unauthorized free-access problems repaired and verified. The appropriate Stripe account must be selected and authorized by CUAC before production account changes. Milestone 3 — Lovable, Production Database, Identity, and Access Repair Payment: $150 Required outcome: Working application/backend connection, database mapping, authentication, guardian consent, roles, protected learning access, and relevant checkout/access defects repaired and verified. Production and isolated testing environments remain separated. Milestone 4 — Automated Payment-to-Access Integration Payment: $150 Required outcome: Working WooCommerce/Stripe-to-HARXGN entitlement integration, payment lifecycle handling, duplicate protection, and Founding 25 functionality demonstrated and verified. Milestone 5 — Final Integrated Launch, Handover, and Seven-Day Support Payment: $500 Required outcome: Remaining in-scope repairs completed; connected-system testing passed; recorded end-to-end demonstration delivered; CUAC written operational acceptance obtained; complete handover provided; and seven consecutive calendar days of agreed launch support completed. TOTAL: $1,000 USD No additional labor fees or recurring expenses are authorized without CUAC's written approval. Milestone Acceptance Every milestone submission must include: The original problem or requirement. The correction actually implemented. The environment affected. Before-and-after behavior. Tests performed. Results and supporting evidence. CUAC-approved exceptions, if any. Reports, blocked tests, recommendations, isolated demonstrations, or unconnected code do not satisfy completed-repair acceptance. Verification must include the connected production system as safely authorized. Synthetic accounts and Stripe test-mode verification must precede payment-affecting live tests. Live transactions require separate written CUAC approval. CUAC must have the opportunity to inspect and verify each milestone before approving payment, subject to Upwork's applicable review rules. Failed in-scope acceptance tests must be corrected and retested within the agreed fixed price. Final Milestone and Support Sequencing The $500 final milestone is the single final performance allocation, not an additional charge or separate holdback. Operational launch acceptance and completion of post-launch support are distinct events: Operational Launch Acceptance: CUAC confirms in writing that the complete integrated platform passed the required acceptance testing and authorizes the start of the seven-day support period. Final Contractual Acceptance: CUAC confirms that the required seven-day support period has been completed, the final handover is satisfactory, and all final milestone conditions have been met. The contractor shall not represent future support as already performed. The final milestone shall be submitted for approval only when its required deliverables, including agreed support, have actually been completed. The parties shall arrange final-milestone funding and submission in accordance with Upwork's current escrow and milestone requirements. If Upwork's milestone structure prevents this exact arrangement, the parties must agree in writing to an Upwork-compliant schedule before funding, without increasing the $1,000 total contract price. No contract provision overrides Upwork's mandatory payment, review, escrow, or dispute procedures. 9. Final Operational Acceptance Final operational acceptance requires a recorded demonstration of the functioning connected system, including: Approved WooCommerce checkout, payment processing, and receipts. Payment-to-learner identity and entitlement automation. Protected course access. Renewal, failure, cancellation, refund, expiration, and duplicate-event processing. Correct Founding 25 qualification, promotional limits, duration, and refund handling. Registration, age-band intake, guardian consent, and authentication. Assessments, lessons, progress, results, certificates, and dashboard functionality. Secure administrator access and prevention of unauthorized learning access. Transactional emails and separate donations. Verified backups, restoration methods, production connections, and CUAC-controlled ownership. The contractor must provide actual test evidence and a recorded walkthrough. An unresolved known in-scope defect prevents operational acceptance unless CUAC approves a specific written exception. The seven-day post-launch support period begins only after CUAC's written operational acceptance. 10. Seven-Day Launch Support and Critical Restoration The contractor shall provide seven consecutive calendar days of operational launch support after written operational acceptance, including weekends and holidays, without additional labor charges. The contractor must remain personally available during agreed coverage hours, with named approved backup coverage where required. Support includes the diagnosis, correction, rollback, and verification of critical in-scope failures involving: Website availability. Checkout and payment processing. Registration and authentication. Account provisioning. Learning entitlements and access. Webhook processing. Application/database connections. Security roles and permissions. Assessments, results, progress, and certificates. Other agreed launch-critical functions. The contractor must promptly address unresolved preexisting in-scope defects, incomplete integrations, overlooked repairs, and regressions. For covered critical failures with a verified available restoration path, the 60-minute restoration commitment described in Section 6 applies. The commitment is to actual restoration or verified rollback, not merely acknowledging the incident. A temporary rollback may satisfy immediate restoration if it returns the function to its verified operating state. Permanent in-scope correction remains required without unauthorized additional charges. Any promised 24/7 support must provide continuous coverage by named, CUAC-approved personnel. Partial daily coverage is not 24/7 support. The parties must define the actual coverage schedule and escalation contacts in U.S. Central Time before launch. 11. Contractual Performance-Refund Requirement As a material condition of contract award, the contractor must expressly accept the agreement's 100% contractual performance-refund commitment covering funds actually paid under the contract when an expressly defined performance failure occurs. A. Delivery Failure The agreed in-scope platform is not fully operational and does not pass the required integrated acceptance tests by the agreed seven-calendar-day deadline, unless CUAC expressly approves a written extension or a documented contractual exception applies. B. Critical Restoration Failure During contracted active-repair or post-launch support coverage, the contractor fails to fulfill an applicable 60-minute restoration or verified rollback obligation for an in-scope critical internal failure, except to the extent a documented contractual exception applies. The performance obligation includes incomplete in-scope repairs, overlooked defects, integration failures, security defects, application/database failures, and regressions. A contractor may not automatically disclaim an agreed in-scope defect solely because it existed before the engagement. Upon an expressly defined performance failure, CUAC may terminate the engagement and request the contractual performance refund. The contractor shall cooperate with applicable Upwork refund procedures and initiate refunds within the contractor's control within 24 hours of a valid written demand. This is a contractual commitment between the parties, not a guarantee that Upwork will automatically refund released money or enforce the provision. Upwork's applicable payment, escrow, review, and dispute rules remain controlling. A genuinely independent external-provider outage may qualify for a limited exception only when supported by contemporaneous objective evidence and only for the period directly affected. Ordinary misconfiguration, improperly managed secrets, webhook failures, and other agreed in-scope defects do not automatically qualify. CUAC retains the right to provide truthful feedback consistent with Upwork's policies. No refund may be conditioned on withholding such feedback. 12. Confidentiality, Handover Documents, and Sensitive Information All CUAC records, findings, architecture information, credentials-related documentation, database information, and handover materials are confidential. They may be used only for expressly authorized project purposes. Protected information includes: Previous investigation reports. Repair records and technical handovers. Architecture and database mappings. Account inventories. Configuration details. Security findings and incident reports. Learner, customer, donation, and payment records. Access and recovery-related technical information. The contractor may not use information from the reports to initiate unauthorized account recovery, bypass security, expand permissions, or alter account ownership. Confidential materials may not be redistributed to unidentified personnel or third parties without CUAC's written authorization. Only approved individuals covered by executed NDAs may receive protected information. Copies and Preservation The contractor must maintain a record of personnel who receive or download confidential project materials. Upon termination or written request, the contractor shall return or securely delete copies as directed, except records required for applicable legal, Upwork, or dispute-preservation obligations. The contractor must confirm the disposition of copies retained by approved team members. No records relevant to a pending payment dispute, security incident, or legal preservation duty shall be destroyed. Actual passwords, recovery codes, API secrets, and security tokens must not be reproduced in ordinary handover reports. Potentially exposed active credentials must be reported immediately for owner-controlled remediation. 13. Suspension, Termination, and Withdrawal Either party may ordinarily terminate the engagement through Upwork upon two calendar days' written notice, subject to applicable platform procedures. Termination does not eliminate accrued obligations, security responsibilities, handover duties, or applicable payment and dispute rights. Immediate Security Suspension CUAC may immediately suspend work and revoke access upon a reasonable identification of: Unauthorized password-reset or recovery attempts. Requests for personal owner credentials or authentication codes outside an approved process. Unauthorized access escalation. Unauthorized modification or removal of existing user permissions. Access by unidentified or unapproved personnel. Unauthorized financial, production, or database changes. Material misrepresentation of access methods, completed work, or test results. Concealment of a material security incident. A credible threat to CUAC's ownership or system security. Upon written suspension notice, the contractor and team must cease system access, testing, credential recovery, and technical modifications unless CUAC expressly authorizes a limited action for evidence preservation or emergency protection. Immediate Termination CUAC may immediately terminate for material breach, serious unauthorized security activity, or other grounds permitting immediate termination under the agreement and applicable Upwork procedures. Ordinary termination without established material breach remains subject to the applicable notice and platform rules. A contractor may not use voluntary withdrawal to avoid accrued contractual obligations. Termination Cooperation Upon termination, the contractor must: Cease unauthorized technical activities. Identify all systems accessed and accounts used. Provide records of completed work and modifications. Disclose pending changes, access requests, and incidents. Preserve relevant technical and project evidence. Cooperate with access revocation. Return or properly dispose of protected materials under Section 12. Provide handover information for work actually performed. CUAC retains authority to revoke invitations and delegated permissions independently. Disputes and refunds shall be handled through applicable Upwork procedures and other available lawful remedies. 14. Final Handover Requirements The contractor must provide a complete CUAC-controlled handover package containing: Current system architecture. Production and external database mapping. Authoritative payment, order, identity, subscription, and entitlement sources. Complete repair register and verification matrix. Before-and-after testing evidence. Recorded end-to-end walkthrough. Backup, restoration, and rollback instructions. Administrator and staff access inventory. Confirmation of CUAC ownership and recovery control. Record of approved secret or credential rotations without exposing actual secrets. Documentation of recurring costs. CUAC-approved exceptions. Configuration and deployment instructions. Full list of personnel who accessed CUAC systems. Record of account-permission changes. Status of all temporary access and invitations. Confirmation that no undisclosed contractor-controlled dependency remains. List of unresolved defects or security issues. All paid work and applicable configuration information must remain available through CUAC-controlled accounts, subject to applicable third-party licenses. Temporary access must be safely revoked or transferred at the end of the engagement. No undisclosed contractor-controlled account or workspace may remain essential to CUAC's normal operations. 15. Required Contractor Acceptance Before Award Before contract funding, the selected contractor must expressly accept this entire agreement through Upwork. Mandatory Written Acceptance "I have reviewed and accept CUAC's complete $1,000 fixed-price HARXGN systems repair, integration, security, launch, and performance agreement. I acknowledge and accept the five milestones; the seven-consecutive-calendar-day completion target and agreed readiness conditions; weekend availability; personal hands-on technical participation; first-24-hour checkpoint; daily evidence-based progress reports; written authorization requirements; seven-day post-operational-acceptance support; and the defined 60-minute critical restoration obligation. I accept the contractual performance-refund provisions, subject to the express exceptions and applicable Upwork procedures. I understand that CUAC retains exclusive ownership and recovery control of its systems and accounts. I will not request or use personal owner credentials, initiate account recovery, modify authentication settings, remove authorized users, expand permissions, or perform sensitive production changes without specific written authorization. I will identify every participating team member, their individual email address, technical responsibilities, NDA status, access requirements, and coverage hours before work begins. I acknowledge that reports, isolated tests, recommendations, and unconnected code do not satisfy operational milestone requirements. I have disclosed my actual technical experience, material limitations, essential dependencies, and scheduling risks. I will not request unauthorized additional charges, substitute personnel without approval, represent incomplete work as completed, or rely upon conflicting earlier proposal terms. I accept the agreed confidentiality, security, verification, support, handover, suspension, termination, and Upwork dispute requirements." Required Information Before Contract Funding Named Lead Engineer: __________________________ Approved Additional Engineers: __________________________ Approved Backup Personnel: __________________________ Approved Project Manager (if any): __________________________ Individual Team Member Email Addresses: __________________________ Defined Responsibilities: __________________________ Coverage Hours (U.S. Central Time): __________________________ Written Project Start Date: __________________________ Seven-Day Completion Deadline: __________________________ Essential Access and Dependencies: __________________________ Pre-Start Readiness Confirmation: __________________________ NDA Completion: __________________________ CUAC Team Approval: __________________________ Contractor's Written Upwork Acceptance: __________________________ END OF CONSOLIDATED AGREEMENT Total Contract Value: $1,000 USD Completion Target: Seven Consecutive Calendar Days Post-Launch Support: Seven Consecutive Calendar Days Required Outcome: Fully Repaired, Integrated, Secure, Demonstrated, and Operational HARXGN Literacy Platform