TASK-0020: make NetGuard host evidence durable - #12
Closed
lr00rl wants to merge 1 commit into
Closed
Conversation
A successful host mutation must report the canonical managed-table SHA without re-executing after lost responses, crashes, or process duplication. Add the bounded SHA helper, pass the absolute running agent into the hardened task environment, and journal only server-marked NetGuard leases and exact results in a private single-owner outbox. Constraint: The installed agent binary is outside the clean task PATH. Constraint: Generic task types do not share the NetGuard atomic replay contract. Rejected: Resolve lattice-agent through PATH | task execution intentionally uses a minimal PATH. Rejected: Journal every task type | server follow-up handlers are heterogeneous and not uniformly crash-idempotent. Confidence: high Scope-risk: moderate Reversibility: clean Directive: Never upload a published outbox result until its directory durability is confirmed, and preserve full task identity for redelivery. Tested: Full normal and race suites; go vet; install syntax and integrity checks; diff check; independent code review APPROVE. Not-tested: Live nft execution, release packaging, and deployment remain outside this development slice.
Contributor
Author
|
Superseded by #13 after immutable-object review requested changes. PR #12 had the correct final tree and valid trailers, but unlawfully squashed the original two-commit topology and changed non-defective object metadata. PR #13 preserves both original trees, identities, timestamps, topology, and the already-valid second message; it changes only the malformed first message separators. This remote branch remains preserved. |
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
1 participant
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.
Clean-base replacement for #11. The content tree is identical to the independently approved final tree, but the history is rebuilt as one git-native Lore commit directly on integration base 97eff2e.
What this proves:
Exact-head verification:
No release, deployment, live nft execution, credential, or ops action is included.