Download and install the Nexus v2 kit

Download the official file

Use the official lead360.io file below. Do not rename the extension, open and re-save the archive, or use a file received from an unverified source.

Verify the file before upload

The checksum confirms that the downloaded bytes match the published public kit. A mismatch means the file is incomplete, altered, or not the current release.

Windows PowerShell

Get-FileHash .\nexus.ask360 -Algorithm SHA256

macOS or Linux

shasum -a 256 nexus.ask360

The result must be 3cbddb7e4e1e2709e676407f1a068b1176c4813dc11854436ca2754006447abf. The separate checksum file is available from the download details.

Upload from the Ask360s area

The kit upload is beside the Ask360s heading, not inside Piece Studio, Memory Brain, Plugins, or Automation Pieces.

Confirm the destination and administrator

Before selecting the file, confirm that the correct Lead360 sub-account is open and that you have permission to create an Ask360 employee. Record who will own the imported employee, review its data access, approve its Piece, and respond when testing reveals a problem.

1. Sign in to Lead360 and choose the exact destination sub-account.
2. Open Dashboard, enter the Ask360 workspace, and select the Ask360s tab.
3. Select the upload icon beside the Ask360s heading.
4. Choose nexus.ask360 and wait for the preview to finish.
5. Review the kit name, suggested employee name, four-Piece count, provider requirements, memory mode, and resource counts.
6. Confirm the import. Lead360 creates a new employee and review-state resources without activating channels, schedules, automations, or source connections.

Understand the import preview

The preview should identify Nexus v2, structure-only memory, four draft Pieces, one disconnected provider-choice profile, 7 playbooks, 6 memory folder guides, one fresh Learning Collection, and disabled proactive settings.

• Cancel when the kit name, memory mode, Piece state or count, or resource counts differ from this page.
• Import creates a new employee with a unique destination name. It does not replace an existing bot.
• Memory guides start pending, the Learning Collection starts without observations, and all four Pieces start as unpublished drafts.
• Schedules and automations remain disabled, and channels and provider accounts are not inherited.

Complete setup after import

1. Open the new employee and review its connectors, plugins, effect policies, playbooks, learning definitions, schedule blueprint, and warnings.
2. Connect only destination-owned providers and choose exact resources.
3. Upload and review destination knowledge, make it available, and bind only the appropriate partitions to each Piece.
4. Validate and test each Piece in Arena with allowed, disallowed, missing-data, provider-outage, approval, and cross-tenant scenarios.
5. Publish each approved revision, assign exact provider capabilities, choose customer or internal channels by role, and test with controlled data.
6. Enable schedules, automations, customer channels, or provider writes one at a time after their owners approve them.