edithatogo/foi-process-event-logs

Synthetic FOI Process Event Logs

Registry status

• —Registry ID: edithatogo/foi-process-event-logs
• —Family: foi-research
• —Repository role: synthetic_benchmark_dataset
• —Canonical dataset: `edithatogo/foi-process-event-logs`
• —Operational status: active
• —Rights status: synthetic_reviewed_fixtures
• —Authoritative catalog: `edithatogo/dataset-estate-registry`

Origin and provenance

• —Origin repository: https://github.com/edithatogo/foi-process
• —Upstream source: Repository-authored synthetic process fixtures.
• —This card describes repository identity and relationships; it does not claim completeness beyond published manifests.

Rights boundary

Repository code, dataset compilation, and underlying source-record rights are separate. The registry currently records the rights state as synthetic_reviewed_fixtures. Where rights vary by record or source, downstream users must inspect the published provenance and rights fields.

Existing dataset documentation

Deterministic demonstration data for the foi-process replay, process-mining and dashboard contracts.

Data classification

This release contains synthetic, explicitly reviewed fixtures only. It is not a publication of real requester correspondence or personal information. A production export must pass the separate privacy, tikanga/data-governance and threat-model gates before it may replace or supplement these fixtures.

Contents

• —active public event log for process discovery and performance analysis;
• —full synthetic event revision history and EvidenceDelta replay stream;
• —process-map edges and variants;
• —OCEL events, objects and event-object links;
• —synthetic conformance findings;
• —deterministic baseline, demand-surge, concept-drift and correction-stress event logs;
• —synthetic scenario revision history, OCEL links, daily metrics and comparative summaries;
• —dashboard, public projection, OCEL and mining-run artefacts;
• —portable JSON Schemas and a SHA-256 publication manifest.

manifest.json records every deposited file, byte length, row count where applicable and SHA-256 digest. FOI-O remains authoritative for legal semantics; conformance examples are not certified legal conclusions. Repository code is Apache-2.0; source-derived artefact rights remain governed by docs/source-rights-and-licensing.md and are not inferred from the code licence.

Reconciliation policy

This repository is retained only while its recorded role is distinct from the canonical dataset. Renames, deletion, visibility changes, and replacement of immutable DOI snapshots require explicit human review.