1. Contracting and temporary access
A4 provides Maestro with a temporary token for activation. A4's master key is never installed in the client's environment.
- · Kit definition
- · Temporary token
- · Installation scope
How it works
From choosing a solution to a running operation
The A4 IA process exists to eliminate the hardest part of AI adoption: getting everything to work together, securely, and without relying on internal technical knowledge.
Steps
Four phases, clear responsibilities
Every phase has a verifiable deliverable. Nothing moves forward without validation.
2. A4 Manifest Reading
Maestro reads the a4-manifest.yaml, which acts as the kit specification: runtime, Skills, agents, dependencies, variables, and tests.
- · Kit version
- · 5 to 10 validated Skills
- · Four basic agents
3. Installation on Hostinger VPS
Maestro checks the VPS, installs OpenClaw or Hermes, sets up dependencies, connects Telegram, and installs the contracted kit.
- · VPS diagnostics
- · OpenClaw or Hermes
- · Telegram connected
4. Testing, reporting, and handover
The installation is tested and documented. Then, the client provides their own AI API key; Maestro is disabled, and the kit stays under the client's control.
- · End-to-end tests
- · Installation report
- · Swap for client's AI
Next step
What task is consuming your team's time?
Tell A4 which process is repetitive, slow, or hard to track. We will evaluate if it can become a digital employee.
- Initial diagnostic
- Guided installation
- Activation report