docs(observability): add TTTPS Proof-of-Time provenance recipe - #760
Open
axcpeter wants to merge 1 commit into
Open
docs(observability): add TTTPS Proof-of-Time provenance recipe#760axcpeter wants to merge 1 commit into
axcpeter wants to merge 1 commit into
Conversation
Community CustomLogger recipe that seals a completion response against the public self-serve KPP Provenance API (kpp.kenosian.com), returning a receipt_id plus HMAC signature that can be independently re-verified. No new package or proxy registration needed; works with litellm+httpx. Verified this session: end-to-end mint-key/anchor/verify round trip against the live API, and the exact code sample in the doc run against litellm.completion(mock_response=...) with the callback attaching response.tttps_receipt.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What
Adds a community CustomLogger recipe under Observability > Callbacks and customization:
docs/observability/tttps_provenance.md, wired intosidebars.jsnext tocustom_callbackandgeneric_api.Why
TTTPS / OpenTTT (Helm-Protocol) is a small open project that seals a completion response's content hash against a public, self-serve Provenance API at kpp.kenosian.com and returns an HMAC receipt that can be re-verified independently later. The recipe uses the documented
CustomLoggerextension point (litellm.callbacks = [...]), so it needs no core code changes, no new pip package, and no proxy callback registration;pip install litellm httpxis enough.The doc is explicit that a receipt is a cryptographic audit-trail timestamp, not a compliance or regulatory certification.
Verification this session
Live round trip against the public API before writing the doc:
POST /v1/keyswith an email minted a real key (api_key, 1000 free seals)POST /v1/anchorwith that key returned a receipt (receipt_id,receipt,time,verify_url)POST /v1/verifywith thatreceipt_idreturnedverified: trueThe exact code block in the doc was run locally against
litellm.completion(mock_response=...): the callback fired and attachedresponse.tttps_receiptwithstatus: "ok"and a realreceipt_idfrom the live API.node --check sidebars.jspasses and the added entry follows the existing category shape.Scope
Docs-only change: one new markdown file plus one line in
sidebars.js. No changes outside this repo.