OUTSIDE RUN/ JSON ↗

Sample report / issued 25 Jul 2026

RiskKernel
passes with limits.

The exact v0.9.0 source built and passed its offline Go and Python test paths. The tag is unsigned, two PostgreSQL tests and seven optional Python integrations were skipped, and the broad runtime claims were not all exercised.

205Go test passes
Boundary

Test events from go test -race -json ./....

62.5%Go statements
Boundary

Total coverage from the race-enabled all-package run.

59Python passes
Boundary

66 ran; seven optional integrations skipped.

0failed test events
Not universal

Skipped and untested paths remain visible below.

What actually
crossed the machine.

Commands ran as nobody:nogroup inside private network and device namespaces, with no new privileges, finite memory, CPU, task, and runtime ceilings.

  1. Exact tag, commit, and tree.

    A full-object depth-one clone passed git fsck --strict. Tag v0.9.0 resolves to commit a2737f69347e538a130f0f851ee2b23626e60a98 and tree bd3847b6de9fe277d3153ccc3e5167714cb7d2a1. The deterministic commit archive SHA-256 is a001d88be5c06a14229f4e637750c05ececd7b170b02656cc855ce982831be0d.

  2. Formatting, vet, and build passed.

    gofmt -l . emitted nothing. Offline go vet ./... and go build ./... completed across 19 packages.

  3. Race-enabled Go suite passed.

    The coverage run reached 62.5% of statements. A separate JSON event run recorded 205 passes, two skips, and zero failures. Both skipped tests were PostgreSQL conformance paths without a database.

  4. Python SDK unit suite passed.

    It ran 66 tests in 1.097 seconds: 59 passed, seven optional third-party framework integrations skipped, zero failed.

  5. Static release binary and CLI smoke passed.

    The stripped x86-64 binary is 23,453,880 bytes with SHA-256 95f5ae98c5059e3851310c53361b1ed341a8f7bfe598c6a1988dd4e599785a8b. init created private mode-0600 files and preserved their hashes on rerun. doctor passed hard checks.

The blank space
is part of the result.

A passing test command supports only the path it ran. These claims remain outside this sample.

warningrelease identity

Unsigned tag.

The annotated tag resolves exactly but carries no cryptographic signature. HTTPS acquisition and Git object identities are evidence, not maintainer-key authentication.

skippeddatastore

No PostgreSQL.

TestPostgresConformance and TestPostgresMigrateDowngradeProtection skipped because this sample did not provision PostgreSQL.

skippedpython integrations

Optional frameworks absent.

AutoGen, CrewAI, LlamaIndex, Pydantic AI, LangChain, and OpenAI Agents integration paths were not all installed. Their unit-facing adapters passed where dependency-free; seven live integration tests skipped.

not testedruntime claims

No broad verdict.

Docker, live model providers, crash recovery, performance, resource exhaustion, penetration resistance, production readiness, and the broad no-telemetry claim were not tested.

post-run clarificationdependency control

No complete dependency baseline.

The signed sample captured the source commit and tree, Go archive, go.mod and go.sum hashes, and runtime identities. It did not freeze a complete resolved module graph or OS-package manifest before execution, so this sample cannot support causal attribution to a later patch.

Authenticate
the exact bytes.

The signature proves that the canonical JSON bytes were signed by the published Outside Run key under the outside-run-report namespace. It does not prove every interpretation.

curl -fsSLO https://while-you-were-away.online/outside-run/riskkernel-v0.9.0.json
curl -fsSLO https://while-you-were-away.online/outside-run/riskkernel-v0.9.0.json.sig
curl -fsSLO https://while-you-were-away.online/outside-run/allowed_signers

ssh-keygen -Y verify \
  -f allowed_signers \
  -I outside-run@while-you-were-away.online \
  -n outside-run-report \
  -s riskkernel-v0.9.0.json.sig \
  < riskkernel-v0.9.0.json

Published key fingerprint: SHA256:P3lIqe4c83UMkoSbXnN5XWakj7j+8kRXrn03tsx1dK0.