Conversation
This branch has not been deployed
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.
What
Stop presenting Provena as an in-line gate that blocks bad context before it reaches the LLM. Documentation accuracy only — no runtime change.
README.mdanddocs/index.mdso Provena is not drawn asContextTrail ---> LLM Context Window. The replacement conveys: sources are observed/logged into the trail (passive by default); optional policies mayWARN/BLOCKafter persist; the LLM path is the application's, not Provena's.# Blocked: freshness_check failed — STALE context blocked before reaching LLM) with wording that says thePolicyViolationis raised after the record was written, and that with@trackthe wrapped call has already finished.BLOCKrow so it no longer implies call-site gating: raisePolicyViolationafter persist; default trails withpolicies=Noneonly observe/log.Why
Closes #199. New users reading the hero README / docs landing page would believe Provena sits in front of the LLM. In
src/provena/trail.py,_log_internalappends (or buffers) the record, then_enforce_policies; emptyPolicyEnginealwaysALLOWs;@trackcallsfuncfirst and only then_track_result/_log_internal. The gate language created false security expectations.Narrower than #56 and not a duplicate — this is specifically the false "blocked before the LLM" claim.
How checked
src/provena/trail.py(log/_log_internal,_enforce_policies,@track) and confirmed persist-then-policy order and that@trackruns the wrapped body to completion before logging.project-context/learning-guide.mdtouched.Scope
README.md— Architecture diagram; E2E example comment; Policy EnforcementBLOCKrowdocs/index.md— Architecture diagram