bench.benchmark.write (first-party): Create, edit, freeze and fork a benchmark on OpenVibe.Bench: POST /api/v1/benchmarks, PUT /api/v1/benchmarks/:id, POST /api/v1/benchmarks/:id/versions (freeze) and POST /api/v1/benchmarks/:id/fork. A version is immutable once a run names it; a fork records its parent.
### PUT `/api/v1/benchmarks/{id}` Create, edit, freeze and fork a benchmark on OpenVibe.Bench: POST /api/v1/benchmarks, PUT /api/v1/benchmarks/:id, POST /api/v1/benchmarks/:id/versions (freeze) and POST /api/v1/benchmarks/:id/fork. - Capabilities: [bench.benchmark.write](/docs/capabilities/bench.benchmark.write) - Visibility: first-party - Parameters: - `id` (path, required) - Request body: `application/json` [bench.benchmark@1](/docs/contracts/bench.benchmark) - Response: `application/json` [bench.benchmark@1](/docs/contracts/bench.benchmark) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.benchmark.write (first-party): Create, edit, freeze and fork a benchmark on OpenVibe.Bench: POST /api/v1/benchmarks, PUT /api/v1/benchmarks/:id, POST /api/v1/benchmarks/:id/versions (freeze) and POST /api/v1/benchmarks/:id/fork. A version is immutable once a run names it; a fork records its parent.
### POST `/api/v1/benchmarks/{id}/fork` Create, edit, freeze and fork a benchmark on OpenVibe.Bench: POST /api/v1/benchmarks, PUT /api/v1/benchmarks/:id, POST /api/v1/benchmarks/:id/versions (freeze) and POST /api/v1/benchmarks/:id/fork. - Capabilities: [bench.benchmark.write](/docs/capabilities/bench.benchmark.write) - Visibility: first-party - Parameters: - `id` (path, required) - Request body: `application/json` [bench.benchmark@1](/docs/contracts/bench.benchmark) - Response: `application/json` [bench.benchmark@1](/docs/contracts/bench.benchmark) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.benchmark.write (first-party): Create, edit, freeze and fork a benchmark on OpenVibe.Bench: POST /api/v1/benchmarks, PUT /api/v1/benchmarks/:id, POST /api/v1/benchmarks/:id/versions (freeze) and POST /api/v1/benchmarks/:id/fork. A version is immutable once a run names it; a fork records its parent.
### POST `/api/v1/benchmarks/{id}/versions` Create, edit, freeze and fork a benchmark on OpenVibe.Bench: POST /api/v1/benchmarks, PUT /api/v1/benchmarks/:id, POST /api/v1/benchmarks/:id/versions (freeze) and POST /api/v1/benchmarks/:id/fork. - Capabilities: [bench.benchmark.write](/docs/capabilities/bench.benchmark.write) - Visibility: first-party - Parameters: - `id` (path, required) - Request body: `application/json` [bench.benchmark@1](/docs/contracts/bench.benchmark) - Response: `application/json` [bench.benchmark@1](/docs/contracts/bench.benchmark) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.benchmark.write (first-party): Create, edit, freeze and fork a benchmark on OpenVibe.Bench: POST /api/v1/benchmarks, PUT /api/v1/benchmarks/:id, POST /api/v1/benchmarks/:id/versions (freeze) and POST /api/v1/benchmarks/:id/fork. A version is immutable once a run names it; a fork records its parent.
### GET `/api/v1/boards/{kindId}` Read a benchmark board on OpenVibe.Bench: GET /api/v1/boards/:kindId?type=elo|pareto|cost returns the rendered board for a kind. - Capabilities: [bench.board.read](/docs/capabilities/bench.board.read) - Visibility: first-party - Parameters: - `kindId` (path, required) - Response: `application/json` [bench.rating@1](/docs/contracts/bench.rating) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.board.read (first-party): Read a benchmark board on OpenVibe.Bench: GET /api/v1/boards/:kindId?type=elo|pareto|cost returns the rendered board for a kind.
### GET `/api/v1/compare` Read the runs of a benchmark on OpenVibe.Bench: GET /api/v1/runs/:id returns the result, GET /api/v1/compare?runs=a,b,c puts runs side by side, GET /api/v1/rankings gives the per-benchmark rankings an - Capabilities: [bench.run.read](/docs/capabilities/bench.run.read) - Visibility: first-party - Response: `application/json` [bench.run@1](/docs/contracts/bench.run@1) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.run.read (first-party): Read the runs of a benchmark on OpenVibe.Bench: GET /api/v1/runs/:id returns the result, GET /api/v1/compare?runs=a,b,c puts runs side by side, GET /api/v1/rankings gives the per-benchmark rankings and GET /api/v1/percentile says where a score sits among a model's runs.
### GET `/api/v1/datasets/{kindId}.jsonl` Read the open dataset for a benchmark kind on OpenVibe.Bench: GET /api/v1/datasets/:kindId.jsonl returns prompts, entries, judgements without voter ids and ratings as JSON lines. - Capabilities: [bench.dataset.read](/docs/capabilities/bench.dataset.read) - Visibility: first-party - Parameters: - `kindId` (path, required) - Response: `application/octet-stream` bytes - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.dataset.read (first-party): Read the open dataset for a benchmark kind on OpenVibe.Bench: GET /api/v1/datasets/:kindId.jsonl returns prompts, entries, judgements without voter ids and ratings as JSON lines.
### POST `/api/v1/evals` Manage private evals on OpenVibe.Bench: POST /api/v1/evals creates a private task suite, POST /api/v1/evals/:id/run runs it against chosen offers, and GET /api/v1/evals/:id/results reads a private eva - Capabilities: [bench.eval.manage](/docs/capabilities/bench.eval.manage) - Visibility: first-party - Response: `application/json` [bench.task@1](/docs/contracts/bench.task) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.eval.manage (first-party): Manage private evals on OpenVibe.Bench: POST /api/v1/evals creates a private task suite, POST /api/v1/evals/:id/run runs it against chosen offers, and GET /api/v1/evals/:id/results reads a private eval and its runs. Never in the public dataset.
### GET `/api/v1/evals/{id}/results` Manage private evals on OpenVibe.Bench: POST /api/v1/evals creates a private task suite, POST /api/v1/evals/:id/run runs it against chosen offers, and GET /api/v1/evals/:id/results reads a private eva - Capabilities: [bench.eval.manage](/docs/capabilities/bench.eval.manage) - Visibility: first-party - Parameters: - `id` (path, required) - Response: `application/json` [bench.task@1](/docs/contracts/bench.task) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.eval.manage (first-party): Manage private evals on OpenVibe.Bench: POST /api/v1/evals creates a private task suite, POST /api/v1/evals/:id/run runs it against chosen offers, and GET /api/v1/evals/:id/results reads a private eval and its runs. Never in the public dataset.
### POST `/api/v1/evals/{id}/run` Manage private evals on OpenVibe.Bench: POST /api/v1/evals creates a private task suite, POST /api/v1/evals/:id/run runs it against chosen offers, and GET /api/v1/evals/:id/results reads a private eva - Capabilities: [bench.eval.manage](/docs/capabilities/bench.eval.manage) - Visibility: first-party - Parameters: - `id` (path, required) - Response: `application/json` [bench.task@1](/docs/contracts/bench.task) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.eval.manage (first-party): Manage private evals on OpenVibe.Bench: POST /api/v1/evals creates a private task suite, POST /api/v1/evals/:id/run runs it against chosen offers, and GET /api/v1/evals/:id/results reads a private eval and its runs. Never in the public dataset.
### GET `/api/v1/kinds` Read a benchmark kind on OpenVibe.Bench: GET /api/v1/kinds lists the kinds, GET /api/v1/kinds/:kindId reads one kind and its entry schema and metrics. - Capabilities: [bench.kind.read](/docs/capabilities/bench.kind.read) - Visibility: first-party - Response: `application/json` [bench.kind@1](/docs/contracts/bench.kind) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.kind.read (first-party): Read a benchmark kind on OpenVibe.Bench: GET /api/v1/kinds lists the kinds, GET /api/v1/kinds/:kindId reads one kind and its entry schema and metrics. Granted to rooms and developer services that render a kind or its board.
### GET `/api/v1/kinds/{kindId}` Read a benchmark kind on OpenVibe.Bench: GET /api/v1/kinds lists the kinds, GET /api/v1/kinds/:kindId reads one kind and its entry schema and metrics. - Capabilities: [bench.kind.read](/docs/capabilities/bench.kind.read) - Visibility: first-party - Parameters: - `kindId` (path, required) - Response: `application/json` [bench.kind@1](/docs/contracts/bench.kind) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.kind.read (first-party): Read a benchmark kind on OpenVibe.Bench: GET /api/v1/kinds lists the kinds, GET /api/v1/kinds/:kindId reads one kind and its entry schema and metrics. Granted to rooms and developer services that render a kind or its board.
### POST `/api/v1/kinds/{kindId}/tasks` Create a benchmark task in a kind on OpenVibe.Bench: POST /api/v1/kinds/:kindId/tasks with { prompt, task\_class?, public? - Capabilities: [bench.task.create](/docs/capabilities/bench.task.create) - Visibility: first-party - Parameters: - `kindId` (path, required) - Response: `application/json` [bench.task@1](/docs/contracts/bench.task) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.task.create (first-party): Create a benchmark task in a kind on OpenVibe.Bench: POST /api/v1/kinds/:kindId/tasks with { prompt, task\_class?, public? }. A room or a person's own token may create a task.
### GET `/api/v1/percentile` Read the runs of a benchmark on OpenVibe.Bench: GET /api/v1/runs/:id returns the result, GET /api/v1/compare?runs=a,b,c puts runs side by side, GET /api/v1/rankings gives the per-benchmark rankings an - Capabilities: [bench.run.read](/docs/capabilities/bench.run.read) - Visibility: first-party - Response: `application/json` [bench.run@1](/docs/contracts/bench.run@1) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.run.read (first-party): Read the runs of a benchmark on OpenVibe.Bench: GET /api/v1/runs/:id returns the result, GET /api/v1/compare?runs=a,b,c puts runs side by side, GET /api/v1/rankings gives the per-benchmark rankings and GET /api/v1/percentile says where a score sits among a model's runs.
### GET `/api/v1/rankings` Read the runs of a benchmark on OpenVibe.Bench: GET /api/v1/runs/:id returns the result, GET /api/v1/compare?runs=a,b,c puts runs side by side, GET /api/v1/rankings gives the per-benchmark rankings an - Capabilities: [bench.run.read](/docs/capabilities/bench.run.read) - Visibility: first-party - Response: `application/json` [bench.run@1](/docs/contracts/bench.run@1) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.run.read (first-party): Read the runs of a benchmark on OpenVibe.Bench: GET /api/v1/runs/:id returns the result, GET /api/v1/compare?runs=a,b,c puts runs side by side, GET /api/v1/rankings gives the per-benchmark rankings and GET /api/v1/percentile says where a score sits among a model's runs.
### GET `/api/v1/rounds/{id}` Read a benchmark round on OpenVibe.Bench: GET /api/v1/rounds/:id returns the round with entries; entries stay blind until the caller has judged or started the round. - Capabilities: [bench.round.read](/docs/capabilities/bench.round.read) - Visibility: first-party - Parameters: - `id` (path, required) - Response: `application/json` [bench.round@1](/docs/contracts/bench.round) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.round.read (first-party): Read a benchmark round on OpenVibe.Bench: GET /api/v1/rounds/:id returns the round with entries; entries stay blind until the caller has judged or started the round.
### POST `/api/v1/rounds/{id}/entries` Submit an outside entry to a benchmark round on OpenVibe.Bench: POST /api/v1/rounds/:id/entries with a service token. - Capabilities: [bench.entry.create](/docs/capabilities/bench.entry.create) - Visibility: first-party - Parameters: - `id` (path, required) - Response: `application/json` [bench.entry@1](/docs/contracts/bench.entry) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.entry.create (first-party): Submit an outside entry to a benchmark round on OpenVibe.Bench: POST /api/v1/rounds/:id/entries with a service token. A room submits a game match, a test-suite run or another room's result.
### POST `/api/v1/rounds/{id}/judgements` Cast a blind judgement on a benchmark round on OpenVibe.Bench: POST /api/v1/rounds/:id/judgements with { judge?, pair?, outcome?, score? - Capabilities: [bench.judgement.cast](/docs/capabilities/bench.judgement.cast) - Visibility: first-party - Parameters: - `id` (path, required) - Response: `application/json` [bench.judgement@1](/docs/contracts/bench.judgement) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.judgement.cast (first-party): Cast a blind judgement on a benchmark round on OpenVibe.Bench: POST /api/v1/rounds/:id/judgements with { judge?, pair?, outcome?, score? }. Human judges are people; automatic, test-suite and game-outcome judges are services.
### POST `/api/v1/runs` Publish a run of a benchmark on OpenVibe.Bench: POST /api/v1/runs with the per-task scores, cost, time and tokens. - Capabilities: [bench.run.publish](/docs/capabilities/bench.run.publish) - Visibility: first-party - Request body: `application/json` [bench.run@1](/docs/contracts/bench.run@1) - Response: `application/json` [bench.run@1](/docs/contracts/bench.run@1) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.run.publish (first-party): Publish a run of a benchmark on OpenVibe.Bench: POST /api/v1/runs with the per-task scores, cost, time and tokens. A service token (openvibe.codes, Run) makes a verified run; a person's token makes a submitted run, which is badged and kept out of the default rankings. A caller with this capability sees a benchmark's holdout tasks.
### GET `/api/v1/runs/{id}` Read the runs of a benchmark on OpenVibe.Bench: GET /api/v1/runs/:id returns the result, GET /api/v1/compare?runs=a,b,c puts runs side by side, GET /api/v1/rankings gives the per-benchmark rankings an - Capabilities: [bench.run.read](/docs/capabilities/bench.run.read) - Visibility: first-party - Parameters: - `id` (path, required) - Response: `application/json` [bench.run@1](/docs/contracts/bench.run@1) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.run.read (first-party): Read the runs of a benchmark on OpenVibe.Bench: GET /api/v1/runs/:id returns the result, GET /api/v1/compare?runs=a,b,c puts runs side by side, GET /api/v1/rankings gives the per-benchmark rankings and GET /api/v1/percentile says where a score sits among a model's runs.
### POST `/api/v1/tasks/{id}/rounds` Pin a reproducible benchmark round on OpenVibe.Bench: POST /api/v1/tasks/:id/rounds with { offers?, seed? - Capabilities: [bench.round.create](/docs/capabilities/bench.round.create) - Visibility: first-party - Parameters: - `id` (path, required) - Response: `application/json` [bench.round@1](/docs/contracts/bench.round) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.round.create (first-party): Pin a reproducible benchmark round on OpenVibe.Bench: POST /api/v1/tasks/:id/rounds with { offers?, seed? }. The round's job generates entries from the exact offers and seed.
### GET `/internal/config` Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one - Capabilities: [bench.config.manage](/docs/capabilities/bench.config.manage) - Visibility: internal - Parameters: - `values` (query, required) — The new values, one member per key. The store validates them against the namespace schema; a secret-class value here is refused. - `reason` (query, required) — Why the change is made; it is the revision's reason in the history. - `merge` (query) — Merge into the active values instead of replacing them. - `unset` (query) — Keys to remove from the new revision. - Input: [common.config-change@1](/docs/contracts/common.config-change) - Response: `application/json` [common.config-namespace@1](/docs/contracts/common.config-namespace) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.config.manage (internal): Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one as common.config-namespace@1, POST applies common.config-change@1, and PUT /internal/config/:namespace/secrets/:key sets a secret with common.config-secret-put@1 (write-only; the answer is the marker) while DELETE removes it. POST /internal/config/:namespace/test/:key asks the service's tester to try a stored value with the provider on the server, answering { ok, message } in one line that never carries a secret (the owner's Setup tab). Only Network's admin proxy, acting for the owner, holds this capability; it is never grantable to apps. Each request carries the owner as actor, and the service audits every write with that actor and key, never a secret value.
### GET `/internal/config/{namespace}` Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one - Capabilities: [bench.config.manage](/docs/capabilities/bench.config.manage) - Visibility: internal - Parameters: - `namespace` (path, required) - `values` (query, required) — The new values, one member per key. The store validates them against the namespace schema; a secret-class value here is refused. - `reason` (query, required) — Why the change is made; it is the revision's reason in the history. - `merge` (query) — Merge into the active values instead of replacing them. - `unset` (query) — Keys to remove from the new revision. - Input: [common.config-change@1](/docs/contracts/common.config-change) - Response: `application/json` [common.config-namespace@1](/docs/contracts/common.config-namespace) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.config.manage (internal): Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one as common.config-namespace@1, POST applies common.config-change@1, and PUT /internal/config/:namespace/secrets/:key sets a secret with common.config-secret-put@1 (write-only; the answer is the marker) while DELETE removes it. POST /internal/config/:namespace/test/:key asks the service's tester to try a stored value with the provider on the server, answering { ok, message } in one line that never carries a secret (the owner's Setup tab). Only Network's admin proxy, acting for the owner, holds this capability; it is never grantable to apps. Each request carries the owner as actor, and the service audits every write with that actor and key, never a secret value.
### POST `/internal/config/{namespace}` Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one - Capabilities: [bench.config.manage](/docs/capabilities/bench.config.manage) - Visibility: internal - Parameters: - `namespace` (path, required) - Request body: `application/json` [common.config-change@1](/docs/contracts/common.config-change) - Response: `application/json` [common.config-namespace@1](/docs/contracts/common.config-namespace) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.config.manage (internal): Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one as common.config-namespace@1, POST applies common.config-change@1, and PUT /internal/config/:namespace/secrets/:key sets a secret with common.config-secret-put@1 (write-only; the answer is the marker) while DELETE removes it. POST /internal/config/:namespace/test/:key asks the service's tester to try a stored value with the provider on the server, answering { ok, message } in one line that never carries a secret (the owner's Setup tab). Only Network's admin proxy, acting for the owner, holds this capability; it is never grantable to apps. Each request carries the owner as actor, and the service audits every write with that actor and key, never a secret value.
### PUT `/internal/config/{namespace}/secrets/{key}` Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one - Capabilities: [bench.config.manage](/docs/capabilities/bench.config.manage) - Visibility: internal - Parameters: - `namespace` (path, required) - `key` (path, required) - Request body: `application/json` [common.config-change@1](/docs/contracts/common.config-change) - Response: `application/json` [common.config-namespace@1](/docs/contracts/common.config-namespace) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.config.manage (internal): Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one as common.config-namespace@1, POST applies common.config-change@1, and PUT /internal/config/:namespace/secrets/:key sets a secret with common.config-secret-put@1 (write-only; the answer is the marker) while DELETE removes it. POST /internal/config/:namespace/test/:key asks the service's tester to try a stored value with the provider on the server, answering { ok, message } in one line that never carries a secret (the owner's Setup tab). Only Network's admin proxy, acting for the owner, holds this capability; it is never grantable to apps. Each request carries the owner as actor, and the service audits every write with that actor and key, never a secret value.
### DELETE `/internal/config/{namespace}/secrets/{key}` Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one - Capabilities: [bench.config.manage](/docs/capabilities/bench.config.manage) - Visibility: internal - Parameters: - `namespace` (path, required) - `key` (path, required) - `values` (query, required) — The new values, one member per key. The store validates them against the namespace schema; a secret-class value here is refused. - `reason` (query, required) — Why the change is made; it is the revision's reason in the history. - `merge` (query) — Merge into the active values instead of replacing them. - `unset` (query) — Keys to remove from the new revision. - Input: [common.config-change@1](/docs/contracts/common.config-change) - Response: `application/json` [common.config-namespace@1](/docs/contracts/common.config-namespace) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.config.manage (internal): Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one as common.config-namespace@1, POST applies common.config-change@1, and PUT /internal/config/:namespace/secrets/:key sets a secret with common.config-secret-put@1 (write-only; the answer is the marker) while DELETE removes it. POST /internal/config/:namespace/test/:key asks the service's tester to try a stored value with the provider on the server, answering { ok, message } in one line that never carries a secret (the owner's Setup tab). Only Network's admin proxy, acting for the owner, holds this capability; it is never grantable to apps. Each request carries the owner as actor, and the service audits every write with that actor and key, never a secret value.
### POST `/internal/config/{namespace}/test/{key}` Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one - Capabilities: [bench.config.manage](/docs/capabilities/bench.config.manage) - Visibility: internal - Parameters: - `namespace` (path, required) - `key` (path, required) - Request body: `application/json` [common.config-change@1](/docs/contracts/common.config-change) - Response: `application/json` [common.config-namespace@1](/docs/contracts/common.config-namespace) - Errors: [errors.problem@1](/docs/contracts/errors.problem) (application/problem+json) Descriptionbench.config.manage (internal): Manage the configuration namespaces and secrets of OpenVibe.Bench through openvibe-shared/config (D11): GET /internal/config lists the namespace summaries, GET /internal/config/:namespace returns one as common.config-namespace@1, POST applies common.config-change@1, and PUT /internal/config/:namespace/secrets/:key sets a secret with common.config-secret-put@1 (write-only; the answer is the marker) while DELETE removes it. POST /internal/config/:namespace/test/:key asks the service's tester to try a stored value with the provider on the server, answering { ok, message } in one line that never carries a secret (the owner's Setup tab). Only Network's admin proxy, acting for the owner, holds this capability; it is never grantable to apps. Each request carries the owner as actor, and the service audits every write with that actor and key, never a secret value.