Preview mode
Live connectors, billing, AI, and downstream writes are off. Your assessment workspace may still be saved when hosted persistence is active.
Operator view for GitHub staging activation, encryption, and durable evidence test flights.
Preview only — changes are not written to live systems yet.
| Provider | Activation State | Missing Configuration | Last Sync | Actions |
|---|---|---|---|---|
| GitHub Adapter Shell Controlled Staging Implementation Ready | staging_implementation_ready | Recently | ||
| Microsoft 365 Adapter Shell | disabled_by_default | MICROSOFT_CLIENT_ID MICROSOFT_CLIENT_SECRET | Never | |
| Google Workspace Adapter Shell | disabled_by_default | GOOGLE_CLIENT_ID GOOGLE_CLIENT_SECRET | Never |
Preview candidate evidence without GitHub API limits or DB writes.
Executes live GitHub fetch and applies evidence write gate rule.
Global Connector Enablement
ZAGOS_LIVE_CONNECTORS_ALLOWED
Enabled
GitHub Connected
GITHUB_CLIENT_ID
Connected
Durable Evidence Writes
ZAGOS_CONNECTOR_EVIDENCE_WRITES_ALLOWED
Enabled
Audit-Run Writes
ZAGOS_AUTOMATION_AUDIT_RUN_WRITES_ALLOWED
Disabled
Findings & Reports Writes
ZAGOS_AUTOMATION_FINDING_WRITES_ALLOWED
Disabled
Stripe Billing
ZAGOS_STRIPE_CONFIGURED
Disabled
Audit-Run Write Approval
System is Ready for audit-run write approval.
To enable persistence of automated audit execution metrics and scope tracking, set ZAGOS_AUTOMATION_AUDIT_RUN_WRITES_ALLOWED=true.
Must complete smoke test before proceeding.
Findings Write Approval
Do not enable findings/report writes until audit-run write smoke passes.
To enable automated injection of detected vulnerabilities or non-compliance into the findings and remediation queue, set ZAGOS_AUTOMATION_FINDING_WRITES_ALLOWED=true.
Ensure findings storage tables are provisioned.
Report Write Approval
To enable generation and vaulting of final compliance reports and executive summaries, set ZAGOS_AUTOMATION_REPORT_WRITES_ALLOWED=true.
Requires connected billing/entitlement subscription in production.
1. Apply SQL manually
2. Configure encryption key in Vercel
3. Configure GitHub OAuth app
4. Configure GitHub env vars in Vercel
5. Run token preflight
6. Run GitHub OAuth controlled test
7. Run dry-run sync
8. Enable evidence write flag only after review
9. Run controlled evidence write test
To revoke a token, operator must delete the row from `connector_sources`.
In event of token compromise, nullify `encrypted_access_token` and roll Client Secret.
This is a controlled staging environment.
Live production connector activation requires manual execution of the SQL storage pack, provision of client secrets, encryption keys, and global runtime enablement.