Add machine-verifiable assertions to SentienceAgent examples #5
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.
Summary
This PR demonstrates the Sentience SDK's AgentRuntime verification system - a declarative approach to agent observability that makes AI agent behavior deterministic, debuggable, and machine-verifiable.
Why This Matters
Traditional AI agents are black boxes: you prompt them, they act, and you hope for the best. When things go wrong, debugging is painful - you're left parsing logs and screenshots trying to understand what the agent saw vs what it did.
Sentience SDK flips this model:
assert_done()returnstrue/falseKey Features Showcased
1. Per-Step Assertions - Guardrails During Execution
2. Declarative Task Completion - Know When You're Done
all_of(),any_of()for complex conditions3. Structured Trace Output - Studio Timeline Integration
trace_dir="traces" # Outputs JSON traces for Sentience StudioVerification Output
`🔍 Verification Summary:
All assertions passed: True
Required assertions passed: True
Task verified complete: True
Assertion Details (4 total):
✅ on_hackernews (required)
✅ show_hn_posts_visible
✅ no_error_message
✅ task_complete (required)
`