Prepare a local test store

Run from command-centre/ in a Team OS source workspace:

cd command-centre
$env:AGENTIC_OS_DIR="$env:TEMP\aios-team-manual"
$env:MEMORY_STORE_BACKEND="pglite"
$env:MEMORY_EMBEDDER="bge-m3"
$env:TEAM_OWNER_PASSWORD="<OWNER_PASSWORD>"
$env:TEAM_MEMBER_PASSWORD="<MEMBER_PASSWORD>"

Create a Team and owner:

npm run team:create -- --slug demo --name "Demo Team" --owner-email owner@example.test --owner-name "Owner" --owner-password $env:TEAM_OWNER_PASSWORD

This assigns the first Team Owner and the first Company Owner. Later Team creation must not replace the Company Owner.

Invite and join a member:

npm run team:invite -- --team demo --email member@example.test --by owner@example.test
npm run team:join -- --team demo --email member@example.test --token <INVITE_TOKEN> --password $env:TEAM_MEMBER_PASSWORD
npm run team:members -- --team demo

Create a client and grants:

npm run team:client -- create --team demo --slug acme --name "Acme" --by owner@example.test
npm run team:client -- grant --team demo --client acme --user member@example.test --access read --by owner@example.test
npm run team:skill -- grant --team demo --skill mkt-copywriting --user member@example.test --permission skill.use --by owner@example.test

Here, --by identifies the authorized maintenance actor for the permission check and audit record. It does not let a hosted request choose its identity.

The owner does not need explicit client or skill grants. Full access supplies implicit access. The explicit grants above are only for the Member test.

Next: Start the API