STATIC PAGE Interactive levers, live recompute, and Record decision run in the app build; every figure, formula, evidence row, and WHY below is the real render, pre-computed. Evidence panels are opened for review.
Configuration Studio
Configuration is product: the tenant document below is the same one the route gates, the assistant, and the server enforcement read. A configuration change is a ledgered decision.
| Site | Region | BU | System of record |
|---|---|---|---|
| DET-01 | AMER | Industrial | SAP S/4HANA |
| STG-02 | EMEA | Industrial | NetSuite |
| OSK-03 | APAC | Consumer | Oracle Fusion |
A decider needs sourced authority whether or not the decider is a person. Agent principals appear here beside human ones, distinguished on sight, and every delegation names its source, its verbs, its threshold, and its expiry; an agent whose delegation nobody sourced can decide nothing. The runtime already refuses over-threshold and out-of-verb attempts; twelve conformance checks hold that promise in the battery.
| Principal | Type | Delegation source | Verbs | Threshold | Expires |
|---|---|---|---|---|---|
| maria.chen | HUMAN | HRIS employment record | approve, defer, escalate | $250,000.00 | on role change |
| agent:forecast-bot-v3 | AGENT | HRIS service-account record, SYNTHETIC | propose, defer | $25,000.00 | 2026-12-31 |
SYNTHETIC rows on the walkthrough tenant; in production this table reads your directory and your service-account registry, and the record of what an agent was allowed to do is held here while the acting happens in your systems, never through ours.
| Role | workspace | supply | operations | finance | customer | workforce | knowledge | technology | governance | graph | ai | config | admin |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Executive | yes | yes | yes | yes | yes | yes | yes | yes | yes | yes | yes | no | no |
| Functional | yes | yes | yes | yes | yes | yes | yes | yes | yes | yes | yes | no | no |
| Operational | yes | yes | yes | no | no | no | no | no | no | no | no | no | no |
| Administrative | yes | no | no | no | no | no | no | no | yes | no | no | yes | yes |
| Step | What it does |
|---|---|
| 1. Confirm your role | Your directory role decides entitlements; this step only confirms the lens. |
| 2. Pin what leads | Choose up to five modules that open your day; they lead your rail and your Command Center. |
| 3. Quiet what does not | Hidden modules leave your rail only; access, search, and direct navigation are untouched. |
| 4. Set your report cadence | Your recurring report generates on this rhythm with your filters, from the Report Studio. |
Worked example: rail workspace/command, rnd, finance, marketing-ops, operations becomes finance, workspace/command, operations. hiding shapes the rail, never the entitlement: a hidden module leaves your rail only; entitlement, search, and direct navigation stay untouched, asserted, not promised.
The client mirrors this matrix for navigation honesty; the server enforces the same resourceKeys. Module-level server enforcement beyond the live term gates is AT_ACTIVATION and labeled so.
COGS / average inventory value
Owner M. Keller · KPI-TURNS
on-time receipts / total receipts, trailing 26w
Owner M. Keller · KPI-OTD
1 - MAPE, trailing 12w
Owner T. Ando · KPI-FA
Nothing is recorded on a synthetic dataset; editing previews the exact ledger payload. In a tenant session the change posts as recordDecision, authority-checked, policy-flagged never blocked, hash-chained. Read-only by architecture toward your systems of record.