Skip to content

Add NodeKit presentation evidence bridge - #4

Closed
HomenShum wants to merge 1 commit into
mainfrom
codex/nodekit-present-evidence
Closed

HomenShum wants to merge 1 commit into
mainfrom
codex/nodekit-present-evidence

Conversation

@HomenShum

@HomenShum HomenShum commented Jul 20, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • registers FeatureClipStudio as a deterministic NodeKit presentation-evidence protocol
  • projects real tracked clips/screenshots into a content-addressed nodekit.evidence-index/v1 artifact
  • adds strict manifest/receipt schemas and fail-closed path, media, digest, provenance, and drift checks
  • keeps generated media, artifact verification, and independent workflow proof explicitly distinct

Proof

  • 13/13 Node tests passed
  • authoring-worktree and fresh-detached-checkout npm run check passed
  • strict AJV 2020 schema validation passed
  • central NodeKit repo check passed
  • bundled Remotion example rendered 640 frames to H.264 1920×1080

Honest boundary

The three tracked artifacts are observed; there are zero independent browser/judge receipts. releaseReady=false and productWorkflowProof=not-certified. No package publication or production deployment occurred.

Pre-existing and not changed: npm ci lock/self-dependency failure and seven Remotion-chain audit findings.

Integration handoff (2026-10-07): This draft retains the deterministic media-evidence bridge at 36dd774; current main b06ab18 declares FeatureClipStudio manifest/receipt ownership but does not contain this adapter. Preserve the adapter, schemas, tests, manifest and both generated artifacts. Its initial three assets remain observed with zero independent workflow receipts, releaseReady=false and productWorkflowProof=not-certified; receipt matching alone does not validate a browser/judge outcome. Before integration, confirm current canonical NodeKit contract compatibility, add the evidence lane without replacing main's current check/render/dependency controls, and reconcile the README provenance basis and deterministic outputs. The old local test/render assertions and old dependency failures describe their historical source, not current main or a newly validated integration.

@HomenShum

Copy link
Copy Markdown
Owner Author

Superseded by the reviewed current-main port in #21, normally merged as 5f5dcbd. The complete canonical tree matches the reviewed replacement, and its natural main CI passed: 20 scenarios, retained source/citation/render-record gates, and the existing smoke render.

The eleven original bridge paths are retained or deliberately corrected within the fourteen-path port. Media remains observed; receipt references never certify outcomes. The branch-only v1 counter is corrected to workflowReceiptReferences without an alias, with productWorkflowProof not-certified and releaseReady false. Historical media and changed README/NODE-LOOPS digests are preserved without rebinding old captures to current documents. Current commands, dependency lock, wrapper, drivers and media remain intact.

This old conflicting draft is closed unmerged. Its original head 36dd774, branch and historical receipts remain preserved. The old schema-only verified behavior and stale projection bytes were not adopted as fresh proof. The before/after update log is in docs/NODEKIT_PRESENT_EVIDENCE.md on main. One moderate and one high install-audit finding remain; this closure adds no workflow, pixel, provider, release or full-security certification.

@HomenShum HomenShum closed this Oct 8, 2026
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