monarchic-agent-protocol 0.1.15 → 0.1.17

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4801d875e1da1deb2b027141f245e2ff1f3c325893c5b1c03fd091e680c89652
-  data.tar.gz: d2cf9a6e1b0dffdef3979f5862f704622dd87aa3c64721c35b746fefc39045c5
+  metadata.gz: e70cc011515a1d46f8b369074834a2abc5ee0d30f928636b333d78e1bcbda9af
+  data.tar.gz: 39007a55b96bd1273f66c377063c0a3adba90acff4044be335a8dd2dbcbcb041
 SHA512:
-  metadata.gz: 25ac118fd8a512b2208c6c096bdbf63eff81fc3addf365b4e8f86606fbb151164185e200185e08249d4b630b22b1dd8c8df8ddc45514b81b8479537c5862ea2d
-  data.tar.gz: 6ae5a3cc87278132d49bf4ad26a4bb900640a090444b47e63dc1ed41b76e3d1647d0356dce88d177483dfa9b884f7e9a8fa33357e461e1202e144944375746c3
+  metadata.gz: 74384051cc3abf842ec9725ce9cc4842a84481c26ddf4247f423d620ec3a5ff87a36d8721525f839745f188d5f4d236596d42055689acc27ccd478bd86b3328e
+  data.tar.gz: 408137845db2c3e52def8b77a0c6c33fb80d7da283cd1c44c816f35fd862bff5ed427831873ed7aebe97db6366b2530d2c90848c132e5aad8400c91a224a53e3

data/README.md

@@ -32,6 +32,7 @@ Install the published package for your language, then use the generated bindings
 
 - Rust: `examples/rust/task.rs`
 - TypeScript: `examples/ts/task.ts`
+- JSON (non-protobuf): `examples/json/objective_spec.minimal.json`
 - Protobuf C++: `examples/proto/cpp/task.cpp`
 - Protobuf Java: `examples/proto/java/TaskExample.java`
 - Protobuf Kotlin: `examples/proto/kotlin/TaskExample.kt`
@@ -42,11 +43,106 @@ Install the published package for your language, then use the generated bindings
 - Protobuf Dart: `examples/proto/dart/task.dart`
 - Protobuf Rust: `examples/proto/rust/task.rs`
 
+### Non-protobuf language support
+
+For languages that do not use protobuf bindings, exchange protocol objects as JSON and validate payloads against the versioned schemas before handoff.
+
+- Canonical JSON example for non-protobuf consumers: `examples/json/objective_spec.minimal.json`
+- Validate a typed payload against a specific schema: `bash scripts/validate-protocol-json.sh schemas/v1/objective_spec.json schemas/fixtures/valid/objective_spec.minimal.json`
+- Validate the canonical non-protobuf JSON example: `bash scripts/validate-protocol-json.sh schemas/v1/objective_spec.json examples/json/objective_spec.minimal.json`
+
+Project-state contract fixtures used by the shell verification suite live under `fixtures/project-state/`, not the repo root.
+
 ### Versioning
 
 - Protocol versions live under `schemas/v1/`.
 - Each v1 object requires `version: "v1"`.
 - New versions must be added under a new directory (e.g. `schemas/v2/`) without changing existing v1 files.
+- The package/crate transition operator runbook lives at
+  [`docs/protocol-release-transition-runbook.md`](docs/protocol-release-transition-runbook.md).
+
+### Client boundary contracts
+
+The Rust crate also exposes a frozen client-boundary surface under `monarchic_agent_protocol::client_boundary`.
+
+Frozen v1 client-boundary types:
+
+- `Intent`
+- `Plan`
+- `PlanStep`
+- `ExecutionReceipt`
+- `VerificationReceipt`
+- `PublicationAction`
+- `ModerationDecision`
+- `ReviewDecision`
+- `RerunScope`
+- `BlockedOutcome`
+- `ArtifactDescriptor`
+
+Canonical JSON fixtures for these contracts live under `fixtures/client_boundary/v1/`.
+The protocol-owned MAP operation handoff bundle for downstream client snapshots
+also lives there as `map_operation_bundle.v1.json`.
+Legacy runtime compatibility fixtures live under `fixtures/client_boundary/v0/`.
+
+### Durable authority contracts
+
+The Rust crate also exposes a frozen durable-authority surface under `monarchic_agent_protocol::durable_authority`.
+
+Frozen v1 durable-authority types:
+
+- `FencingToken`
+- `Lease`
+- `RunLifecycleState`
+- `StepLifecycleState`
+- `LeaseRejectionReason`
+- `RecoveryEvent`
+- `ManualOverrideRecord`
+
+Canonical JSON fixtures for these contracts live under `fixtures/durable_authority/v1/`.
+
+### Service boundary contracts
+
+The Rust crate also exposes a frozen service-boundary surface under `monarchic_agent_protocol::service_boundary`.
+
+Frozen v1 service-boundary types:
+
+- `PrincipalRef`
+- `TenantRef`
+- `AuthContext`
+- `UsageRecord`
+- `AuditExportManifest`
+- `ControlPlaneQueueJob`
+- `ControlPlaneDispatchRequest`
+
+The queue job contract uses the explicit wire marker
+`monarchic.control-plane.queue-job.v1` because it is consumed across the API,
+control-plane queue, and worker boundary. Canonical JSON fixtures for
+service-boundary contracts live under `fixtures/service_boundary/v1/`.
+The cross-service protocol ownership boundary is documented in
+[`docs/service-boundary-architecture.md`](docs/service-boundary-architecture.md).
+
+## Lean4 Formalization
+
+A Lean4 proof model now lives under `formal/lean/`.
+
+It currently formalizes a bounded set of invariants derived from real downstream usage in this workspace:
+
+- client-boundary id safety heuristics
+- role normalization aliases
+- verification receipt status consistency
+- terminal lifecycle sink behavior
+- plan dependency grounding
+- protobuf message well-formedness and cross-message integrity
+- protobuf lifecycle transitions and bounded lease control-plane safety
+- protobuf request/report admissibility and fencing-token monotonicity
+- bounded protobuf control-plane trace safety and authority preservation
+- inductive consistency preservation over protobuf control-plane event traces
+- continuous active-authority traces preserve the bound `(run_id, step_id, task_id)` scope
+- active traces exclude competing authorities for the same `(run_id, step_id)` scope
+- a checked protobuf coverage manifest makes the currently formalized subset explicit relative to the full `.proto` surface
+- the schema-side Lean coverage manifest is generated from `schemas/v1/monarchic_agent_protocol.proto` and validated in CI
+
+See `docs/lean4-formal-verification.md` for scope and usage.
 
 ### Schema summary
 
@@ -58,9 +154,16 @@ Schema files live under `schemas/v1/`:
 - `schemas/v1/artifact.json`
 - `schemas/v1/event.json`
 - `schemas/v1/gate_result.json`
+- `schemas/v1/failure_class.json`
+- `schemas/v1/plan_status.json`
+- `schemas/v1/failure_detail.json`
+- `schemas/v1/role_provenance.json`
+- `schemas/v1/plan_provenance.json`
+- `schemas/v1/plan_step.json`
+- `schemas/v1/plan.json`
+- `schemas/v1/execution_receipt.json`
 - `schemas/v1/run_context.json`
 - `schemas/v1/run_outcome.json`
-- `schemas/v1/delivery_contract.json`
 - `schemas/v1/agent_role.json`
 - `schemas/v1/dataset_ref.json`
 - `schemas/v1/experiment_spec.json`
@@ -80,12 +183,69 @@ All schemas allow additional properties for forward compatibility.
 - `schemas/v1/artifact.json`
 - `schemas/v1/event.json`
 - `schemas/v1/gate_result.json`
+- `schemas/v1/failure_class.json`
+- `schemas/v1/plan_status.json`
+- `schemas/v1/failure_detail.json`
+- `schemas/v1/role_provenance.json`
+- `schemas/v1/plan_provenance.json`
+- `schemas/v1/plan_step.json`
+- `schemas/v1/plan.json`
+- `schemas/v1/execution_receipt.json`
 - `schemas/v1/run_context.json`
-- `schemas/v1/run_outcome.json`
+- `schemas/v1/dataset_ref.json`
+- `schemas/v1/experiment_spec.json`
+- `schemas/v1/objective_spec.json`
+- `schemas/v1/eval_result.json`
+- `schemas/v1/provenance.json`
 
 `schemas/v1/agent_role.json` is a shared schema used by `task.json`.
-`schemas/v1/dataset_ref.json`, `schemas/v1/experiment_spec.json`, `schemas/v1/objective_spec.json`,
-`schemas/v1/eval_result.json`, and `schemas/v1/provenance.json` are referenced by top-level schemas.
+`schemas/v1/failure_class.json` is a shared schema used by `event.json` and `gate_result.json`.
+
+### TaskMessage and TaskMessageAck
+
+These types define the shared contract for orchestrator-mediated runner
+communication.
+
+They are intended for:
+
+- durable handoff messages between active tasks
+- clarification requests and responses
+- blocker notices
+- artifact-ready notifications
+- explicit acknowledgement state
+
+They are not intended to imply direct peer-to-peer runner transport. The
+protocol defines the message shape, but routing, persistence, and delivery are
+owned by the orchestrator.
+
+`TaskMessage` carries:
+
+- sender and recipient task ids
+- message kind
+- optional subject/body
+- referenced artifact ids
+- optional reply chaining
+- acknowledgement requirement
+
+`TaskMessageAck` records recipient acknowledgement state separately so mailbox
+delivery can remain append-only and auditable.
+
+Recommended acknowledgement semantics:
+
+- `received`: the recipient has seen the message in its inbox
+- `accepted`: the recipient accepts the request and plans to act on it
+- `rejected`: the recipient explicitly declines or cannot act on it
+- `resolved`: the recipient completed the requested follow-up or supplied the
+  final response
+
+Recommended routing semantics:
+
+- message ids should be unique within one run
+- sender and recipient should be tasks from the same run
+- `reply_to`, when present, should reference an earlier message id from the
+  same run log
+- `requires_ack=true` should imply at least one corresponding
+  `TaskMessageAck` record from the recipient
 
 ### AgentRole
 
@@ -98,6 +258,7 @@ Enum values:
 - `reviewer`
 - `security`
 - `ops`
+- `publisher`
 
 Example:
 
@@ -107,6 +268,78 @@ Example:
 }
 ```
 
+### PipelineSpec
+
+Represents a planned pipeline before execution.
+
+Required fields:
+
+- `version`: `"v1"`
+- `pipeline_id`: stable identifier
+- `objective`: human-readable campaign or pipeline objective
+- `project_key`: member/project scope identifier
+- `tasks`: ordered `PipelineTask[]`
+
+This is the shared planning shape that bootstrap generation, orchestration
+validation, and UI preview should converge on.
+
+Current shared planning fields now include:
+
+- `PipelineSpec`
+- `PipelineTask`
+- `TaskDependency`
+- `SkillRef`
+- `RoleDefinition`
+- `ResolvedRoleBundle`
+
+These are available in the protobuf and language bindings even where the checked-in
+JSON Schema index has not yet been expanded to cover each planning helper type.
+
+### RoleDefinition and ResolvedRoleBundle
+
+These types provide the shared contract between:
+
+- role catalogs in `monarchic-agent-roles`
+- orchestration-time validation
+- runner-time execution bundles
+
+`RoleDefinition` describes a canonical role, its capabilities, and its declared
+skill requirements. `ResolvedRoleBundle` is the runtime handoff shape that can
+pair a concrete role definition with the resolved skills and rendered template
+path used for one task execution.
+
+### Canonical Pipeline Layout
+
+`PipelineSpec` and `PipelineTask` are now the canonical role-aware planning
+layout across the stack.
+
+For compatibility, older minimal pipeline files may still only carry:
+
+- `pipeline_id`
+- `tasks[].id`
+- `tasks[].task`
+
+But once a pipeline opts into the role-aware contract by declaring any of:
+
+- `objective`
+- `project_key`
+- `tasks[].role`
+- `tasks[].goal`
+- `tasks[].required_skills`
+
+the intended canonical shape is:
+
+- `PipelineSpec.objective`: required, non-empty
+- `PipelineSpec.project_key`: required, non-empty
+- `PipelineTask.role`: required, non-empty
+- `PipelineTask.goal`: required, non-empty
+- `PipelineTask.required_skills`: optional list of `SkillRef`, but when present it
+  must be internally well-formed and deduplicated
+
+This is the contract `monarch` should generate, `monarchic-orchestrator` should
+validate, and `monarchic-runner` should ultimately execute through resolved role
+bundles.
+
 ### Task
 
 Represents work assigned to an agent.
@@ -124,7 +357,6 @@ Optional fields:
 - `constraints`: free-form object
 - `gates_required`: list of gate names to run (ex: `["qa", "security"]`)
 - `run_context`: `RunContext`
-- `delivery_contract`: typed acceptance and risk contract for autonomous delivery loops
 - `objective_spec`: objective scoring contract for deterministic outcome evaluation
 - `experiment_spec`: typed experiment design contract for deterministic in silico runs
 
@@ -154,19 +386,6 @@ Example:
 }
 ```
 
-### DeliveryContract
-
-Typed acceptance contract for autonomous delivery execution.
-
-Required fields:
-
-- `objective`: plain-language objective statement
-- `definition_of_done`: ordered completion checklist
-- `required_checks`: required gate/check names for merge readiness
-- `risk_tier`: `low | medium | high | critical`
-
-Optional fields include cycle/turn budgets (`max_cycle_minutes`, `max_agent_turns`) and PR/review/rollback strategy hints.
-
 ### RunContext
 
 Execution hints for a runner.
@@ -243,6 +462,7 @@ Optional fields:
 - `message`: human-readable details
 - `provenance`: typed runtime/source hashes for event attribution
 - `eval_results`: optional metric snapshot payloads
+- `failure_class`: typed failure taxonomy payload for machine-actionable triage
 
 Example:
 
@@ -270,6 +490,7 @@ Required fields:
 Optional fields:
 
 - `reason`: short explanation
+- `failure_class`: typed failure taxonomy payload for deterministic failure routing
 - `evidence`: free-form object with supporting data
 
 Example:
@@ -287,21 +508,125 @@ Example:
 }
 ```
 
-### RunOutcome
+### FailureClass
 
-Typed summary contract for objective/cost/risk decisions captured at the end of a run.
+Typed taxonomy payload for classifying protocol failures.
 
 Required fields:
 
-- `version`: `"v1"`
-- `task_id`: task identifier
-- `objective_decision`: objective decision label
-- `cost_decision`: cost decision label
-- `risk_decision`: risk decision label
-- `final_decision`: aggregate decision label
+- `category`: `validation`, `dependency`, `environment`, `timeout`, `conflict`, `permission`, `resource`, `internal`, or `unknown`
+- `code`: stable machine-readable failure code
+- `retryable`: whether automated retry is expected to be useful
+
+Optional fields include `detail`, `scope`, `source`, and `next_action`.
+
+### PlanStatus
+
+Plan lifecycle status used for typed execution plans and receipts.
+
+Allowed values:
+
+- `unspecified`
+- `draft`
+- `planned`
+- `executing`
+- `complete`
+- `bounded`
+- `failed`
+- `cancelled`
+- `unknown`
+
+### FailureDetail
+
+Failure detail attached to a plan or receipt.
+
+Required fields:
+
+- `class`: one of `validation`, `execution`, `agent`, `infra`, `policy`, or `unknown`
+- `code`: machine-readable failure code
+- `message`: operator-readable failure message
+
+Optional fields:
+
+- `details`: bounded extension object with implementation diagnostics
+
+### RoleProvenance
+
+Role metadata for deterministic role-template binding.
+
+Required fields:
+
+- `role_name`
+- `template_hash`
+- `render_hash`
+
+### PlanProvenance
+
+Generation metadata for a plan and policy context.
+
+Required fields:
+
+- `generated_by`
+- `generated_at_ms`
+
+Optional fields:
+
+- `policy_profile`
+- `role`
 
-Optional fields include `run_id`, `objective_metric`, `objective_score`, cost budget metrics,
-risk detail fields, `summary`, and `evidence`.
+### PlanStep
+
+Execution step in a plan, with dependency and template fields.
+
+Required fields:
+
+- `step_id`
+- `description`
+- `task_template`
+
+Optional fields:
+
+- `depends_on`
+- `failure`
+
+### Plan
+
+Canonical plan contract.
+
+Required fields:
+
+- `contract_version`: required contract tag (for now `"v1"`)
+- `plan_id`
+- `objective`
+- `status`
+- `created_at_ms`
+- `updated_at_ms`
+- `provenance`
+- `steps`
+
+Optional fields:
+
+- `run_id`
+
+### ExecutionReceipt
+
+Deterministic execution contract for a run.
+
+Required fields:
+
+- `contract_version`: required contract tag (for now `"v1"`)
+- `run_id`
+- `plan_id`
+- `plan_hash`
+- `task_hashes`
+- `artifact_hashes`
+- `outcome_hash`
+- `status`
+- `generated_at_ms`
+
+Optional fields:
+
+- `failure`
 
 ### DatasetRef
 
@@ -367,10 +692,7 @@ Required fields:
 
 Optional fields include dataset hashes/references and command/task/pipeline hashes.
 
-
-### Language bindings
-
-#### Rust
+## Rust
 
 The crate lives at the repo root with sources under `src/rust/lib.rs`.
 
@@ -381,6 +703,7 @@ let task = Task {
     version: PROTOCOL_VERSION.to_string(),
     task_id: "task-123".to_string(),
     role: AgentRole::Dev as i32,
+    role_id: "dev".to_string(),
     goal: "Implement protocol".to_string(),
     inputs: None,
     constraints: None,
@@ -415,7 +738,11 @@ github.com/monarchic-ai/monarchic-agent-protocol/src/go
 
 #### Protobuf
 
-The v1 protobuf schema lives at `schemas/v1/monarchic_agent_protocol.proto`. It mirrors the JSON schema and uses `google.protobuf.Struct` for free-form objects (`inputs`, `constraints`, `evidence`, `extensions`). Additional JSON properties should be stored in the `extensions` field on each message.
+The v1 protobuf schema lives at `schemas/v1/monarchic_agent_protocol.proto`. Its portable object messages mirror the JSON schema and use `google.protobuf.Struct` for free-form objects (`inputs`, `constraints`, `evidence`, `extensions`). Additional JSON properties should be stored in the `extensions` field on each message.
+
+The protobuf file also contains transport-only service definitions for machine-to-machine control-plane RPC, starting with `RunnerControlService`. Those protobuf-only contracts cover registration, heartbeats, lease acquisition, lease renewal, lease resume, step progress/outcome reporting, and cancellation acknowledgement, and they are not mirrored into the JSON schema index.
+
+The Rust crate published from this repository currently exports protobuf message types. Runtime repositories that need gRPC client/server bindings should generate transport stubs from the canonical proto with their chosen toolchain, such as `tonic-build`.
 
 Language packages are published per registry. Use the registry package for your language instead of generating local outputs.
 
@@ -454,11 +781,15 @@ Dart sources live under `src/dart`.
 - `nix develop` provides Rust, Node, jq, Python `jsonschema`, and `protoc`.
 - `nix flake check` validates JSON schemas, protobuf codegen, and package imports (PyPI + Rust + npm + Go).
 - JSON Schema test: `scripts/test-json-schema.sh`.
+- Language-agnostic schema validation helper: `scripts/validate-protocol-json.sh`.
+- Language-agnostic schema validator regression test: `scripts/test-validate-protocol-json.sh`.
 - Pre-commit schema JSON parse check: `scripts/pre-commit-schema-json-parse.sh`.
 - Pre-commit schema parse smoke test: `scripts/test-pre-commit-schema-json-parse.sh`.
 - Schema edit changelog: `schemas/SCHEMA_CHANGELOG.md`.
 - Schema changelog format test: `scripts/test-schema-changelog-format.sh`.
 - README schema index coverage test: `scripts/test-readme-schema-index-coverage.sh`.
+- README examples coverage test: `scripts/test-readme-examples-coverage.sh`.
+- README/examples examples synchronization test: `scripts/test-readme-examples-sync.sh`.
 - Protobuf codegen test (all languages): `scripts/test-proto.sh`.
 - Protobuf availability smoke test: `scripts/test-proto-availability-smoke.sh`.
 - Protobuf codegen (write to `src/<lang>`): `scripts/generate-proto.sh`.
@@ -466,28 +797,20 @@ Dart sources live under `src/dart`.
 - JSON Schema regeneration only: `scripts/generate-json-schema.sh`.
 - JSON Schema generation requires `protoc-gen-jsonschema` (install with `go install github.com/chrusty/protoc-gen-jsonschema/cmd/protoc-gen-jsonschema@latest`).
 
-Use the Nix apps (preferred) or the scripts directly:
-
-- `nix run .#generate-proto` (`scripts/generate-proto.sh`): regenerate protobuf outputs into `src/<lang>`.
-- `nix run .#generate-json-schema` (`scripts/generate-json-schema.sh`): regenerate JSON Schemas from the protobuf source.
-- `nix run .#update-local-hashes` (`scripts/update-local-hashes.sh`): refresh hashes for local build inputs.
-- `nix run .#update-version -- <version>` (`scripts/update-version.sh`): bump version across manifests and tags (expects `vX.Y.Z` input).
-- `nix run .#update-registry-hashes` (`scripts/update-registry-hashes.sh`): refresh hashes for published registries (npm, crates, PyPI, RubyGems, NuGet, JitPack, GitHub source).
-
-For every schema change, generate protobuf outputs and update local hashes.
-
-For every release, tag the commit, update versions, push, and update registry hashes *after pushing*.
-
 ### Schema validation workflow
 
 1. Run full schema lint and semantic checks: `bash scripts/lint-schemas.sh`.
 2. Run direct schema fixture checks: `bash scripts/test-json-schema.sh`.
-3. Validate staged schema JSON before commit: `bash scripts/pre-commit-schema-json-parse.sh`.
-4. Verify pre-commit checker behavior is deterministic: `bash scripts/test-pre-commit-schema-json-parse.sh`.
-5. Verify schema changelog entry format: `bash scripts/test-schema-changelog-format.sh`.
-6. Verify README schema index coverage stays aligned: `bash scripts/test-readme-schema-index-coverage.sh`.
-
-### Nix packages
+3. Validate language-agnostic payloads through JSON schema: `bash scripts/validate-protocol-json.sh schemas/v1/objective_spec.json schemas/fixtures/valid/objective_spec.minimal.json`.
+4. Verify schema validator behavior is deterministic: `bash scripts/test-validate-protocol-json.sh`.
+5. Validate staged schema JSON before commit: `bash scripts/pre-commit-schema-json-parse.sh`.
+6. Verify pre-commit checker behavior is deterministic: `bash scripts/test-pre-commit-schema-json-parse.sh`.
+7. Verify schema changelog entry format: `bash scripts/test-schema-changelog-format.sh`.
+8. Verify README schema index coverage stays aligned: `bash scripts/test-readme-schema-index-coverage.sh`.
+9. Verify README examples coverage for non-protobuf and protobuf paths: `bash scripts/test-readme-examples-coverage.sh`.
+10. Verify README and examples/README example entries stay synchronized: `bash scripts/test-readme-examples-sync.sh`.
+
+## Nix packages
 
 - `packages.default`: Rust crate for protocol types
 - `packages.rs-lib`: Rust crate for protocol types (local)

data/schemas/v1/agent_role.json

@@ -10,6 +10,9 @@
     "qa",
     "reviewer",
     "security",
-    "ops"
+    "ops",
+    "publisher",
+    "researcher",
+    "verification"
   ]
 }

data/schemas/v1/artifact.json

@@ -72,6 +72,24 @@
     "version": {
       "default": "",
       "type": "string"
+    },
+    "provenance": {
+      "$ref": "provenance.json"
+    },
+    "dataset_refs": {
+      "type": "array",
+      "items": {
+        "$ref": "dataset_ref.json"
+      }
+    },
+    "eval_results": {
+      "type": "array",
+      "items": {
+        "$ref": "eval_result.json"
+      }
+    },
+    "experiment_spec": {
+      "$ref": "experiment_spec.json"
     }
   },
   "title": "Artifact",

data/schemas/v1/dataset_ref.json

@@ -4,11 +4,7 @@
   "title": "DatasetRef",
   "type": "object",
   "additionalProperties": true,
-  "required": [
-    "dataset_id",
-    "sha256",
-    "format"
-  ],
+  "required": ["dataset_id", "sha256", "format"],
   "properties": {
     "dataset_id": {
       "type": "string"
@@ -25,14 +21,7 @@
     },
     "split": {
       "type": "string",
-      "enum": [
-        "train",
-        "validation",
-        "test",
-        "holdout",
-        "reference",
-        "other"
-      ]
+      "enum": ["train", "validation", "test", "holdout", "reference", "other"]
     },
     "size_bytes": {
       "type": "integer",

data/schemas/v1/eval_result.json

@@ -4,11 +4,7 @@
   "title": "EvalResult",
   "type": "object",
   "additionalProperties": true,
-  "required": [
-    "metric",
-    "value",
-    "passed"
-  ],
+  "required": ["metric", "value", "passed"],
   "properties": {
     "metric": {
       "type": "string"