> ## Documentation Index
> Fetch the complete documentation index at: https://docs.app.useharmonia.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Verify the AWS edition locally before separately authorized cloud execution.

## Prerequisites

Use Node.js 20+, Python 3.12+, ffmpeg/ffprobe, and the pinned dependencies. Native persistence integration tests additionally require Java 21 and official DynamoDB Local. The integration harness requires a local MinIO binary for version-aware erasure tests.

```bash theme={null}
npm ci
python3 -m venv agent/.venv
agent/.venv/bin/pip install -r agent/requirements.lock
cp .env.example .env.local
```

Set a private shared `INTERNAL_API_TOKEN`. Keep both paid execution and queue consumers disabled while inspecting code. Local tests use isolated local services and scoped test records. Fixtures are never submission evidence.

## Verify without cloud calls

```bash theme={null}
npm run lint
npx tsc --noEmit
PYTHON_BIN=agent/.venv/bin/python npm test -- --run
MINIO_BINARY=/absolute/path/minio DYNAMODB_LOCAL_JAR=/absolute/path/DynamoDBLocal.jar npm run test:integration
PYTHONPATH=agent agent/.venv/bin/python -m pytest agent/tests -q
npm run build
npm run infra:synth
```

The checked-in integration harness owns its local DynamoDB and S3 process lifecycles and uses loopback ports 18766 and 18767. Unit tests and the harness do not establish authenticated AWS proof.

## Operator interface

`./scripts/dev.sh` starts the Next.js web app on port 3000 and worker on port 8080. Configure real Cognito-backed sign-in and the storage environment first; this script does not provide an authentication bypass or launch AWS emulators.

After account access and a spending budget are authorized, configure the managed AgentCore Runtime and providers using [Configuration](/configuration). Start with an authorized upload. The normal workflow pauses for digest-bound strategy approval, then plans and drafts before separate effect approval. In chat, model-parsed text cannot authorize strategy or an effect by itself.

A content export requires stored bytes and independent read-back. Public posting requires its own approved action and official provider credentials. Failed or uncertain effects remain visible for recovery and reconciliation.

Use [Deployment](/deployment) and the [evidence runbook](/evidence-runbook) for the authenticated rehearsal. Do not treat local preview, passing tests, or configured services as a completed demo.