TenantAtlas/specs/114-system-console-control-tower/quickstart.md
ahmido 0cf612826f feat(114): system console control tower (merged) (#139)
Feature branch PR for Spec 114.

This branch contains the merged agent session work (see merge commit on branch).

Tests
- `vendor/bin/sail artisan test --compact tests/Feature/System/Spec114/`

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #139
2026-02-28 00:15:31 +00:00

42 lines
1.2 KiB
Markdown

# Quickstart (Spec 114: System Console Control Tower)
## Prereqs
- Docker running
- Laravel Sail
## Start the app
- `vendor/bin/sail up -d`
- `vendor/bin/sail composer install`
- `vendor/bin/sail artisan migrate`
## Seed a platform operator (recommended)
The repo includes `Database\Seeders\PlatformUserSeeder`, which creates:
- Workspace `default`
- Tenant with `external_id=platform`
- Platform user `operator@tenantpilot.io` (password: `password`) with baseline system capabilities
Run:
- `vendor/bin/sail artisan db:seed`
## Open the System console
- Visit `/system`
- Login with:
- Email: `operator@tenantpilot.io`
- Password: `password`
## Validate key Spec 114 surfaces
- Control Tower dashboard: `/system?window=24h` (switch between `1h`, `24h`, `7d`)
- Global operations:
- Runs: `/system/ops/runs`
- Failures: `/system/ops/failures`
- Stuck: `/system/ops/stuck`
- Directory:
- Workspaces: `/system/directory/workspaces`
- Tenants: `/system/directory/tenants`
- Security:
- Access logs: `/system/security/access-logs`
## Notes
- `/system` uses the `platform` guard and a separate session cookie from `/admin`.
- The System console should remain DB-only at render time (no Graph calls on page load).