Repository navigation
log plan lifecycle without a tracing vendor - #12
Merged
Merged
Conversation
Stdout carries intent id, plan id, policy codes, latency, and tokens without a tracing vendor.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully 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.
Problem
Plan decisions already land in Mongo as
AuditEventrows. Operators watching the API process had no structured lifecycle line with intent id, plan id, policy codes, planner latency, and tokens. A tracing vendor would have been extra machinery for a local demo.Solution
recordPlanEventstill writesAuditEvent, then prints one JSON object on stdout:event,intentId,planId,policyCodes,latencyMs,tokens. Intent create, policy reject, approve, and complete all go through it. No Langfuse or other tracing vendor.How to test
Check
src/observability/planLog.test.tsand theplan.rejected_policycase inintentPipeline.test.ts. Run the API and grep stdout for"event":"plan.awaiting_approval".