journal-capture-tck reads packages. A consumer that only reads needs this artifact alone.
From Java
2.0.0-20261108.225512-21, on the package from Getting started, with java ReadAndVerify out native. The usage view’s final observation reports uncached_input_tokens 2, output_tokens 76, cache_read_tokens 27204 and cache_write_tokens 400, each with its native pointer (for example /cache_read_input_tokens), and the view states "aggregation":"none: groups are never summed across scopes, sources, models or child runs". The program then prints ACCEPTED [].
PackageReader.open(Path)takesevents.jsonlor the directory holding it. The reader opens no network connection and consults no registry or cache. A refusal means “this reader does not implement that interpretation”; the raw lines are still returned.OcsfOracle.verify(pkg, nativeDir, expected)judges a package against its native input.OcsfReaderTool.acceptance(report)gives the verdict.
Analysis views
AnalysisViews.all(pkg) returns every view, and each linked child’s views under children, each computed on its own core:
Every row carries the rule it applied and the occurrences it read, so a derived result can be explained from the saved data. Nothing is reconciled or summed: conflicting observations are reported as conflicts, and missing identities as unresolved.
Usage comes in disjoint tranches (
uncached_input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, reasoning_tokens, reported_total_tokens), each with a measurement status: Measured, Possibly default, Conditional or Lower bound. Nothing is summed or split.
From the command line
OcsfReaderTool commands; each takes <events.jsonl|dir> first:
verify’s exit codes are listed in Getting started: only exit 0 is acceptance.