Role-specific navigation and actions are projected from /api/permissions/matrix. The browser cannot supply tenant, entity, role, signer, or forwarded-header authority; never-allowed actions are omitted from the shell instead of rendered disabled.
Matrix source
api_server_derived_from_session_registry_context
Primary role lane
pci_operator from server matrix metadata
Visible actions
8
Suppressed actions
1 action(s) withheld without client-side disabled controls.
Viewer role accepted
false
Signer input accepted
false
Step-up reauthentication handoff
When the server-derived permission matrix marks an action as requiring step-up, this shell sends the operator to the same-origin PCI API/BFF step-up route. The browser never constructs Autheory authorize URLs and never supplies tenant, role, principal, subject, MFA, freshness, or permission authority.
Override inherited answerReauthenticate
Only sensitive_action=answer.override is sent as a non-authoritative retry hint.
Queue audit exportReauthenticate
Only sensitive_action=operator.audit_export is sent as a non-authoritative retry hint.
Step-up initiate
/api/session/step-up
Callback boundary
/api/session/callback is API/BFF-owned after provider reauthentication.
Allowed browser hint
sensitive_action / action only; the API must re-check session, CSRF policy for unsafe service retries, tenant registry, permissions, and freshness.
Visible server-allowed actions
Action
Category
Step-up
Reason
Review tenant
tenant
server authorized
role_allows_tenant_review
Review evidence package
evidence
server authorized
role_allows_evidence_review
Create evidence metadata intake
evidence
server authorized
role_allows_evidence_upload_metadata
Answer questionnaire
assessment
server authorized
role_allows_answer
Override inherited answer
assessment
server step-up required
operator_step_up_required
Invite submerchant
onboarding
server authorized
operator_scope_review_required
Save workflow state
workflow
server authorized
role_allows_workflow_metadata_save
Queue audit export
audit
server step-up required
role_allows_operator_audit_export_metadata
auth.session_refreshed
Module status
Data Collectionenabled / primary
Data Collection is enabled by trusted session context.
Monitoringenabled / integrated
Monitoring is enabled by trusted session context.
PCI application
PCI Compliance Command Center
Interactive compliance workflow workspace
Compliance cycle loaded: 22 of 24 responses answered, 3 evidence records, and 5 review lanes. Same-origin API refresh will keep this workspace current. Tenant authority, live data, payment traffic, restricted contents, and deployment authority stay server-side.
__Host-pt_pci_csrf same-origin session check for workflow saves.
Data boundary
Workflow state only; no live payment data, restricted evidence files, signed document files, export files, external queues, notifications, or partner-edge authority.
Next best action
Confirm scope
Review the business profile and SAQ path before moving questionnaire work forward.
Use a stage card to work, mark ready, or accept a section; every change goes through the same-origin workflow API.
Workflow
Run the compliance cycle
Compliance lead
Business profile & SAQ scope
SAQ_A recommended with needs review confidence.
18 inherited answers, 1 stale item, 2 evidence requirements.
This packet is the checklist behind final acceptance: each row names the reviewer, the workspace, the decision, and the criteria.
Business profile and SAQ scopeReviewer: submerchant adminDecision: Confirm payment channels and SAQ path or request follow-upCriteria: Merchant profile is complete; Payment channel scope is recorded; SAQ path recommendation is reviewable
Questionnaire and policy answersReviewer: submerchant adminDecision: Accept control answers or return them for changesCriteria: Required controls have answers; Stale inherited answers are cleared or explained; Policy exceptions have owner notes
Evidence request coverageReviewer: evidence uploaderDecision: Accept evidence records or request corrected referencesCriteria: Required evidence records are linked; Scanner status is recorded; Restricted contents are absent from the browser response
Monitoring dependency readinessReviewer: pci operatorDecision: Confirm Monitoring dependency state or request remediationCriteria: Monitoring dependency owner is visible; Evidence and assessment routes are linked; No browser scan, beacon, CSP, or status-feed mutation is available
AOC package and correction logReviewer: executive signerDecision: Accept package readiness or record correction requestCriteria: Sign-ready checklist is visible; Correction/addendum rows are reviewable; Only package status and correction rows are returned
Final operator acceptanceReviewer: pci operatorDecision: Record final product review or request follow-upCriteria: Authorized reviewers are visible; Role handoff state is reviewable; Final review action is CSRF-bound and server-derived
Loading SSF, customized approach, compensating control, ASV, TPSP, corpus rebase, and internal-record metadata from same-origin APIs. This is the working reporting state; supporting reporting tables below are secondary.
Read APIs
/api/compliance/ssf/status
/api/compliance/customized-approach
/api/compliance/compensating-controls
/api/compliance/asv/summary
/api/compliance/tpsp/records
/api/corpus/rebase-warnings
/api/compliance/internal-records
Action APIs
/api/audit/export-requests and /api/reports/operator are mounted below as CSRF-bound record-only actions.
No browser tenant, entity, cycle, report, export, standards-text, evidence, document, endpoint, download, signed URL, queue, notification, or live-data authority; no request bodies on read paths and no browser storage fallback.
Current service-backed compliance reporting state
Area
State
Service seam
SSF applicability from compliance service
SSF ref
Gate
Restricted text
Reason codes
Customized approach metadata from compliance service
Approach
State
Objective
Evidence bundle
Compensating controls from compliance service
Control
State
Requirement
Evidence requests
ASV metadata from compliance service
Scan
Status
Window
Remediation findings
TPSP records from compliance service
Record
Coverage
Validity
AOC metadata
Corpus rebase warnings from compliance service
Warning
State
Fail closed
Affected refs
Internal compliance records from compliance service
Record
State
Retention anchor
Browser visible
Compliance breadthService metadata
Compliance breadth and reporting
Review SSF applicability, control approach records, ASV/TPSP coverage, rebase warnings, and server-owned output metadata without rendering restricted standards text.
⏳Ready for review
2
SSF scope records
0/1
Customized controls accepted
0/1
Compensating controls accepted
1/2
ASV windows passed
2
TPSP records
1/2
Server export packages ready
30%
No browser tenant, compliance, report, export, download, signed URL, queue, notification, endpoint, account, PAN, PII, evidence-body, document-body, restricted-standards-text, or live-data authority.
ASV windows show scan scheduling and external report record only. This app does not execute scans, upload reports, queue reminders, or contact vendors.
Corpus rebase preview requires operator review before reports are regenerated; only refs and counts render.Rebase reason codes
reason_code_1
corpus_rebase_preview_required
Reports and exportsServer-owned output
Reports and exports
Report and export rows are API-shaped metadata. Generation, signing, delivery, retention anchoring, downloads, and notifications remain server-owned.
⏳Ready for review
Reporting actionsExisting CSRF seam
Server-owned reporting action controls
⏳Ready for reviewserver-owned-reporting
Operators can queue record-only audit exports and operator reports through the same-origin API. The browser never receives document bodies, standards text, evidence contents, download URLs, signed URLs, tenant authority, cycle authority, or live compliance data.
Audit export API
/api/audit/export-requests
Operator report API
/api/reports/operator
CSRF cookie
__Host-pt_pci_csrf double-submit session check for unsafe methods.
Last reporting API result
Waiting for operator action.
Report manifests2 server record(s)
Reports
Report manifests expose source counts, hashes, status, and policy only. Report bodies and restricted standards text stay server-side.
Operators can run the eligibility wizard, create a provisional assignment, and record operator review. The server derives corpus package, tenant, entity, cycle, workflow task, and audit refs.
Wizard API
/api/eligibility/wizard/run
Assignment API
/api/eligibility/provisional-assignment
Review API
/api/eligibility/operator-review
CSRF cookie
__Host-pt_pci_csrf double-submit session check for unsafe methods.
Last eligibility API result
Waiting for operator action.
Cycle workspace
Cycle working slice
Scope, corpus, inheritance, and evidence-required metadata refs only; no evidence contents render.
Loading question-group, evidence-request, workflow-task, and classification metadata from /api/compliance/collection-state. This is the working compliance collection state for the Command Center.