Where you are. KAiM runs as three properties, one engine:
kaiminsights.com is this internal site — admin,
configuration, metrics, builds, and the sandbox for future verticals (the bridge
& engine room). kaimpartners.com
is the customer face — onboarding, enablement, support (the boarding gate).
kaimsystems.com
is the public marketing front (the hull). Same governed engine;
the front door each domain opens differs.
Total visibility
The fleet settings matrix: every agent, its tier, its Agent Operating Profile version, and every tunable threshold — escalation, confidence floor, retries, exception routing — on one screen, with review windows in view.
Governed mutation
Editing a setting drafts a governed change and shows the path it will travel: gate evaluation, signed Allow, versioned profile, next-boot pickup, measured outcome. The pane is wired to the gate — never around it.
Boundaries that hold
The five sacred lines render locked. Break-glass override demands a rationale and a named witness, is rate-limited, and is chained as evidence. A forged session or five failed sign-ins gets a refusal, not a retry hint.
Why a single pane is safe here: it is single in
visibility, never single in power. Every mutation path on the pane already
exists, already gated, evidenced, and separation-of-duties checked. The
screen adds convenience; it adds zero authority.