PKPEEK Docs
Docs/Workflows, rules & reference

Rules and guards

The system-wide rules every PEEK screen and command enforces, independent of the UI.

These rules come from the common enforcement requirements (SYS01–SYS24) and appear throughout the screen contracts. The server enforces each one even when the browser would allow the action.

RuleWhat it means in practice
Tenant isolationEvery query is scoped to tenants in your assignment; guessed IDs show nothing and reveal no enumeration detail.
Explicit contextOpening a customer sets tenant + environment and clears the previous tenant’s workspace.
Capability check per commandThe primary action’s capability is checked server side at commit, not just when the page loads.
Independent reviewRequester and reviewer/verifier must be different people; approvals bind to the exact proposal or diff hash.
Recheck at commitReadiness, versions and dependencies are reevaluated at commit; stale state returns a conflict.
Entitlement ≠ enablement ≠ accessPurchase, agency enablement and user record grants are always separate.
Core independenceNo base workflow requires a paid peer module.
Recommendations are not decisionsNothing PEEK publishes is adopted for an agency automatically.
No secrets in PEEKNo secret entry, reveal or export; audit and incidents carry metadata only.
Immediate restriction, reviewed restorationStops apply at once; restoration is separate and never replays queued work.
Synthetic previewsPreviews use fixture identities and mock responses; live writes and external calls are disabled.
Verified authority onlyUnverified references cannot be labeled binding.