10 - Operations Runbook

Runbook singkat untuk operasi harian setelah refactor context-based.

1. Runtime Verification

cek health route framework: /up

cek route API aktif:

cek schedule:

cek queue worker (wajib untuk provisioning async):

2. Database Lifecycle

Fresh environment

Urutan command:

migrasi central (database/migrations/central)

seed cluster registry minimal

migrasi tenant cluster (clusters:migrate)

seed central data

Seeder Notes

Pastikan tenant seed berjalan setelah migrasi tenant tables tersedia.

3. Auth/Billing Incident Triage

cek log API terstruktur di log channel aktif

cari pola 401/403 spike pada endpoint auth/tenant

cek webhook billing failure per provider

verifikasi token ability mismatch dan tenant context mismatch

untuk provisioning tenant gagal:

cek log key tenancy.taxonomy.provision_failed

re-run tenant provisioning manual

verifikasi data tenant DB setelah re-run

Referensi komponen:

app/Logging/StructuredApiLogger.php

app/Services/Central/Billing/PaymentWebhookService.php

app/Http/Middleware/Tenant/Context/*

app/Services/Central/Tenancy/Provisioning/TenantProvisioningOrchestrator.php

4. Tenant Provisioning Recovery

Per tenant:

Checklist setelah re-run:

command exit success

summary created/updated masuk akal

data tenant di cluster sesuai ekspektasi

tidak ada warning provisioning berulang di log

5. Change Management

Setiap perubahan arsitektur wajib update:

docs/01-project-structure.md

docs/02-context-boundaries.md

dokumen domain terkait (auth/billing/tenant runtime)

6. Archive Policy

Dokumen lama jangan dihapus langsung; pindahkan ke:

docs/archived/<tanggal>-<label>/

Agar histori desain tetap bisa ditelusuri saat incident review.

10 - Operations Runbook

1. Runtime Verification#

2. Database Lifecycle#

Fresh environment#

Seeder Notes#

3. Auth/Billing Incident Triage#

4. Tenant Provisioning Recovery#

5. Change Management#

6. Archive Policy#