ACC 1.0.0

Installation

Verify the release evidence, run the repository-provided installer, and confirm a healthy ACC command before operational use.

Before you begin

System requirements

Install from a writable, extracted release directory with the required command-line tools available on your PATH.

Bash

Runs the installer and the ACC command entrypoint.

Git

Required by the installer environment gate and repository-aware workflows.

Python 3

Runs ACC documentation, release, architecture, and runtime commands.

The default CLI destination is /usr/local/bin/acc. Use an account that can write there, or set ACC_BIN_PATH to a writable location already included in your PATH.

Compatibility

Supported platforms

ACC 1.0.0 uses a Bash installer and platform-aware runtime collectors for Unix-like environments.

Linux

Supported by the installer and the Linux branches of ACC inventory, health, and monitoring collectors.

macOS

Supported by the Bash installer and the Darwin branches of ACC runtime collectors. Use the macOS checksum command shown below.

Windows

A native Windows installer is not included in this release. Do not treat an unverified compatibility layer as a supported production target.

Choose a source

Installation methods

The versioned release archive is the canonical installation path; a repository checkout is intended for development and review.

Release package

Recommended for installation. Keep the archive, release.manifest, checksum sidecar, and release report together while you verify version 1.0.0.

Repository checkout

Appropriate for contributors who need source history. Check out the intended version, review its release evidence, and run the same installer from the repository root.

Integrity gate

Verify the release package

Confirm release identity from the manifest, then verify the archive bytes against the published SHA-256 sidecar before extraction.

Place ACC-1.0.0-23ffa25.tar.gz, ACC-1.0.0-23ffa25.tar.gz.sha256, and release.manifest in the same directory.
Inspect the manifest and confirm that VERSION=1.0.0,COMMIT=23ffa25, and the PACKAGE value match the artifact you received.
Run the checksum command for your platform. Continue only when it reports success.

Linux

sha256sum --check ACC-1.0.0-23ffa25.tar.gz.sha256

macOS

shasum -a 256 --check ACC-1.0.0-23ffa25.tar.gz.sha256

A mismatch means the archive is not the artifact described by the published evidence. Do not extract or install it; obtain the package and evidence again from the approved release source.

Install

Run the installer

Extract the verified archive, enter its release root, and run the single installer entrypoint.

tar -xzf ACC-1.0.0-23ffa25.tar.gz
cd amin-control-center
./install.sh

If the default executable directory is not writable, choose an explicit user-owned path:

mkdir -p "$HOME/.local/bin"
ACC_BIN_PATH="$HOME/.local/bin/acc" ./install.sh

Keep the extracted release directory after installation. The installed command is a symbolic link to bin/acc in that directory, so moving or deleting the release root breaks the command.

Step 1

Environment

Checks Bash, Git, Python 3, and the resolved ACC root.

Step 2

Filesystem

Prepares ACC runtime, log, storage, backup, and data directories.

Step 3

Configuration

Creates the default configuration or preserves an existing one.

Step 4

CLI

Links the release CLI into the configured executable path.

Step 5

Validation

Confirms the core structure, configuration, runtime, and CLI entrypoint.

First checks

Verify the installation

Resolve the command, confirm its canonical version, and run read-only platform diagnostics.

command -v acc
acc version
acc status
acc doctor

Confirm that acc version reports the release you verified. Review status and diagnostic output before using ACC for operational work; warnings should be understood, not ignored.

Common blockers

Troubleshooting basics

Start with the failed installer stage or the first verification command that does not produce the expected result.

Environment check fails

Run command -v bash git python3. Install the missing prerequisite, confirm it is on PATH, and rerun the installer from the release root.

CLI destination is not writable

Set ACC_BIN_PATH to a writable executable path. Ensure its parent directory is on PATH, then rerun the installer.

`acc` is not found

Inspect the path printed by the CLI installer, confirm the symbolic link exists, and add its parent directory to PATH before opening a new shell.

The installed link is broken

Restore the extracted release directory to its installed location or rerun installation from a permanent directory. The link must continue to resolve to that release'sbin/acc.

Continue

Return to the guided flow

With the CLI verified, continue through Getting Started or return to the documentation gateway.

Continue Getting Started View Documentation