Guardrails
What the DCC will never do, and the governance rules behind work, evidence and Sigma.
Government authority remains human-owned — PEEK will not bind the Government, accept a deliverable, approve payment, waive a requirement, issue a contract action, delete a federal record or write back to a source system.
Registered actions (the only things the app may create)
- create_owned_work_item
- A work item with owner, next action, due date and waiting-on.
- create_approval_request
- Routes a material decision to a second person.
- create_reminder
- Follow-up reminder.
- create_proposed_source_action
- A proposal for a human to execute in the source system.
- freeze_evidence_snapshot
- Digest-pinned evidence snapshot.
- export_procurement_brief
- Governed brief export with source manifest.
- Two-person rule for material reconciliations; same-user approval is blocked.
- Handoff acceptance only by the receiving role; it writes an audit event.
- Untrusted text in documents cannot change instructions (e.g. “ignore previous instructions” is detected and ignored).
- Lane separation — public and synthetic data are never aggregated.
- Demo reset affects only the isolated demo tenants and never modifies pack files.
Related guides
Personas and permissions
The seven demonstration personas, their permissions and CBP role profiles, and how to switch persona.
Procurement approvals
The two-person approval queue for material reconciliations.
Sigma Intelligence
Ask governed questions about the office portfolio or a case; Sigma answers from authorized snapshot data with citations, charts and drafts.