Skip to content

feat: add normalized workflow evidence - #13

Merged
SetraTheXX merged 24 commits into
mainfrom
publish/phase12-evidence-core
Jul 25, 2026
Merged

feat: add normalized workflow evidence#13
SetraTheXX merged 24 commits into
mainfrom
publish/phase12-evidence-core

Conversation

@SetraTheXX

Copy link
Copy Markdown
Owner

Summary

  • add normalized, tamper-evident evidence receipts
  • verify versioned event health
  • add offline reports, comparisons, redaction, and usage provenance
  • expand lifecycle and human evidence

Validation

  • npm test
  • npm run smoke
  • npm run check
  • npm run pack:dry-run
  • npm pack --dry-run

This is part 3 of the ordered Phase 11-14 publication series.

Copilot AI review requested due to automatic review settings July 25, 2026 23:51

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@SetraTheXX
SetraTheXX merged commit 5885502 into main Jul 25, 2026
6 checks passed
@SetraTheXX
SetraTheXX deleted the publish/phase12-evidence-core branch July 25, 2026 23:57

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ae7cd6265c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/evidence/verify.js
Comment on lines +76 to +78
const rebuilt = buildEvidenceReceipt(found, { generatedAt: receipt.generatedAt });
if (JSON.stringify(rebuilt.integrity) !== JSON.stringify(receipt.integrity)) {
issue(issues, "receipt-integrity-inventory-mismatch", "Receipt integrity inventory does not match current canonical evidence.");

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Validate the entire rebuilt receipt

When any non-integrity field in evidence-receipt.json is altered—such as completeness, task status, or usage—this check still passes because only the rebuilt integrity inventory is compared and the receipt itself is excluded from that inventory. All canonical file hashes therefore remain valid while cewp run verify reports success for a falsified portable receipt; compare the complete rebuilt receipt using the stored generatedAt, not only its integrity property.

AGENTS.md reference: AGENTS.md:L5-L5

Useful? React with 👍 / 👎.

checkpointId: binding.workflow.checkpointId,
owner: binding.execution.owner,
backend: binding.execution.backend,
status: "active",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Release host-binding ownership after completion

For a binding with references.worktree, this record is created as permanently active, but checkpoint completion, workflow finalization, and binding replacement never transition or remove integration/ownership.json. Because loadOwnershipRecords treats every non-released record as live, a completed native or audit workflow can indefinitely block a later checkpoint or run from claiming the same host-owned worktree; release the claim on terminal checkpoint transitions or provide an explicit handoff path.

AGENTS.md reference: AGENTS.md:L6-L6

Useful? React with 👍 / 👎.

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.

2 participants