Map NodeMem to canonical runtime events#3
Draft
HomenShum wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
Restacks NodeMem's truthful NodeKit L1/L2 brownfield map directly on the merged P0 contract.
nodeagent.event/v1and ProofLoop certificationdevcommand to run the actual TypeScript demo in watch modeProof
git diff --check: passDependency status
The branch's local product proof and security checks pass. Hosted
node-platform / conformancefetchesnode-platform/mainand is expected to remain red until the event-consumer ownership in node-platform #4 lands.Boundary
The Convex lane validates schema shape only; it is not a deployment proof. This PR does not publish npm or implement the event translator.
Supersedes #2, whose pre-P0 base became conflicting after P0 merged.