Public case study · architecture and implementation

Systems / Governance

Access review you can reconcile.

A review and evidence workflow that normalizes data from multiple sources, makes differences visible and publishes results deliberately.

Evidence path

  1. Collect
  2. Normalize
  3. Compare
  4. Review
  5. Publish
  6. Preserve evidence

Problem

Access sources disagree in schema, timing and meaning. Missing data is not proof of missing access.

Proof in the build
Source adapters handle link, URL and cursor pagination, then map each response into one shared report model.

Review model

Normalize before comparing, expose differences instead of hiding them, and keep human judgment before publication.

Proof in the build
Every selected collector is preflighted before collection begins, and discrepancies remain visible for human review.

Evidence

Record what was reviewed, decided and published without pretending incomplete source data is complete.

Proof in the build
CSV output is staged and published only after every selected collector succeeds; a failed replacement restores the last complete report.

Sanitized system view

Evidence before publication.

Representative workflow using no account, access or review data.

Reconciliation / Review

Discrepancy decision

Awaiting review

Compare normalized source evidence and make differences explicit before publishing a review result.

Collected evidence

Okta + SaaS source records

Review scope

Selected applications + reviewer decision

Publication checks

  • Every collector succeeded
  • Differences remain visible
  • Decision stays human
  • Publication remains atomic

Inside the review pipeline

Publication behaves like a transaction, not a folder of best-effort exports.

Collection

Go CLI with shared collector contracts

Vendor clients implement a minimal Collector interface and normalize each source into the same report model. Shared pagination handles link, URL and cursor styles.

Preflight

Validate every selected source first

Configuration is checked before collection or report creation begins, preventing a known setup problem from producing a partial review.

Publication

Stage, publish or restore

CSV reports are staged and published only after every selected collector succeeds. A failed replacement restores the last complete review.

Result

More defensible review work and a clearer handoff from evidence to action, without claiming compliance or completeness.