Skip to content

fix(exports): retain recorded process provenance in JSON - #900

Merged
antropos17 merged 2 commits into
masterfrom
codex/export-provenance-20261011
Oct 11, 2026
Merged

antropos17 merged 2 commits into
masterfrom
codex/export-provenance-20261011

Conversation

@antropos17

Copy link
Copy Markdown
Owner

Problem and behavior

JSON activity exports previously dropped the recorded process-instance identifier and attribution evidence. Two observations with the same recycled PID could therefore become indistinguishable outside the app. The JSON projection now retains a bounded recorded instanceId, recognized source, and registry-filtered attributionEvidence while preserving the existing scalar attribution field and empty-agent behavior.

The projection uses explicit allowlists. Unknown or malformed provenance becomes null or an empty list; arbitrary nested fields, watched file contents and API-key-shaped extra properties are not copied. The current file-watcher producers do not set source, so that field remains null for those events until a producer records an allowed value.

Verification

  • Two focused new regressions failed before the change; all 32 export tests pass after it.
  • Scoped Prettier, ESLint and diff checks pass. Local Vitest 4.1.11 is provisional against the declared dependency; hosted CI with npm ci is authoritative.
  • Independent GPT-6.1 Sol review of frozen two-file hashes: GO, including review of producer contracts and export data boundaries.

CSV/HTML formats and the audit chain are unchanged. This does not qualify native provider attribution or a full enforcement stage.

@antropos17
antropos17 merged commit f1b77bd into master Oct 11, 2026
5 checks passed
@antropos17
antropos17 deleted the codex/export-provenance-20261011 branch October 11, 2026 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant