Scope - What V and Bruno Covers
Overview
Section titled “Overview”This page defines the implementation boundaries of the V and Bruno engagement.
The Autosplash platform was already operating in production before the V and Bruno engagement began. The current application therefore consists of both inherited functionality and work completed during the engagement.
This distinction is important when evaluating bugs, planning future development, or determining ownership of specific system components.
In Scope
Section titled “In Scope”The engagement included implementation of:
- Front-end redesign and user experience improvements
- Guest booking flow redesign
- Returning customer booking improvements
- Infrastructure migration and production stabilization
- Service-layer abstractions introduced during the engagement
- Developer tooling created during the engagement
Only components modified or introduced during the engagement fall within the implementation scope documented throughout this handover.
Out of Scope / Inherited from Previous Team
Section titled “Out of Scope / Inherited from Previous Team”Large portions of the Autosplash platform predate the engagement and were inherited as part of an existing production application.
Examples include:
- Legacy controllers
- Existing booking workflows not modified during the engagement
- Membership implementation
- Existing background execution model using
exec("php artisan ...") - Historical database structure
- Existing administration functionality
- Legacy business logic not refactored during the project
- Any other functionality not modified during the V and Bruno engagement
This list is illustrative rather than exhaustive. Unless explicitly documented elsewhere in this handover, functionality not modified during the engagement should be considered inherited.
Some of these systems are documented where appropriate but were not redesigned as part of the engagement.
Documentation of inherited behaviour exists solely to assist future maintainers and should not be interpreted as authorship, modification, or implementation responsibility.
Operational Responsibility After Handover
Section titled “Operational Responsibility After Handover”Following handover:
- Autosplash owns all source code, infrastructure, and application assets.
- Future contractors are responsible for work completed during their own engagements.
- V and Bruno assume no ongoing maintenance responsibility outside separate written agreements.
Hosting, infrastructure, third-party accounts, production operations, and ongoing maintenance are the responsibility of the platform owner unless covered by a separate agreement.
Intellectual Property
Section titled “Intellectual Property”All application code, documentation, infrastructure assets, and project deliverables produced during the engagement have been transferred to Autosplash.
The client owns the complete codebase, including both inherited components and work completed during the engagement.
V and Bruno retain no operational control over the platform following handover.
Who to Contact
Section titled “Who to Contact”Refer to the following pages for ownership and contact information.
As a general guideline:
- Questions about features implemented during the engagement should be directed to V and Bruno.
- Business decisions, operational support, infrastructure, credentials, and future platform management should be directed to Autosplash.
- Responsibility for inherited functionality should be determined through repository history rather than assumptions.