Key People & Contacts
Overview
Section titled “Overview”This page outlines primary contact points for different areas of the Autosplash platform, including the V and Bruno implementation scope, internal Autosplash stakeholders, and legacy system context where relevant.
Contact paths are separated by ownership of system components and operational responsibility.
V and Bruno team
Section titled “V and Bruno team”Responsible for:
- Front-end refactor work completed during the engagement
- Booking flow and UX implementation changes
- Stripe Webhooks
- Infrastructure migration and stabilization work completed during the engagement
- Developer tooling and local development setup provided in the handover
Primary contact: Vladimir Laskin (Project Manager / Technical Lead)
Use this contact for:
- Questions about implemented features during the engagement
- Clarification on system structure introduced during the refactor
- Issues related to newly introduced service-layer architecture
Autosplash team
Section titled “Autosplash team”Responsible for:
- Product ownership and business requirements
- Operational decisions related to live platform usage
- Customer support and platform administration
- Coordination of future development work and external contractors
Use this contact for:
- Business-level decisions
- Operational platform issues unrelated to the refactor scope
- Access, credentials, and administrative systems
Legacy system context
Section titled “Legacy system context”The platform contains a significant portion of functionality originating from earlier development phases prior to the V and Bruno engagement.
For this reason:
- Historical implementation details may exist only in the Git history and live system state
- Some components were not redesigned during the engagement and remain functionally unchanged
- Maintenance of those components follows the original implementation lineage in the repository history
Future changes to these areas should be evaluated against existing system behavior before modification.
Support boundaries
Section titled “Support boundaries”The V and Bruno engagement covered a defined implementation scope completed during the project timeline.
After handover:
- No active maintenance commitment is assumed outside separate agreements
- Ongoing operational support, feature development, or infrastructure management requires a new engagement
- Responsibility for system operation after handover resides with the platform owner
System ownership
Section titled “System ownership”- All source code and infrastructure assets belong to Autosplash
- All implemented changes during the engagement are traceable through Git history
- Documentation reflects system state at time of handover and may not cover future modifications