Skip to content

feat: separate internal and external trace schemas #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
spbkgw-beep wants to merge 1 commit into from
Closed

feat: separate internal and external trace schemas #79

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Added
- Separate internal vs external trace schemas with strict Pydantic validation and checked-in JSON Schema artifacts for API, billing, pipeline, inbox, and dispatch events.

## [0.4.0] - 2026-02-26

### Changed
Expand Down
16 changes: 16 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,6 +146,22 @@ The Claude plugin skill remains at:

Both skills cover the same CLI capabilities (`estimate`, `validate`, `calibrate`) but are phrased for their respective ecosystems.

## Trace Schema Foundation

The repo now includes strict trace schemas for two surfaces:

- internal operational traces: agent coordination, inbox protocol, dispatch lifecycle
- external customer-visible traces: API request/response, billing events, pipeline stages

Source models live in `src/agent_estimate/tracing/schema.py`.
Checked-in JSON Schema artifacts live in `schemas/trace/`.

Regenerate the schema artifacts after model changes:

```bash
python scripts/render_trace_schemas.py
```

## Usage Examples

Estimate tasks from a text file:
Expand Down
Loading