Pressure Testing | ota repo readiness docs — ota

Recommended next

All pressure-testing posts CI validation Claim assurance

What pressure evidence is

Pressure testing exercises a bounded Ota surface against an exact repository revision and retains the resulting evidence. It is product discovery and validation, not a certification programme.

The Core-owned registry is canonical for the bounded cases on this page. This page is generated from its public-safe projection and cannot add claims that are absent from the registry. The pressure-testing blog tag is broader: it includes field notes that are not registered cases.

A case records its repository type, exact source revision, Ota source, hosted matrix, exercised surfaces, proven facts, and not-proved boundaries.
A green case never means the repository passed Ota, is fully governed, or is endorsed by its maintainers.
Draft engineering notes remain review artifacts; only published notes are linked as public case studies.

Registered pressure evidence

Each card links to retained hosted evidence. Read the listed limits with the same weight as the proven facts.

The declared consumer closure built after its generator and sibling prerequisites.

Evidence boundary

Exercised: generated language-server source, sibling VS Code extension consumer, pnpm hydration, workflow proof. Engineering note: published. Limits: Repository-wide generated-artifact correctness; package publishing or deployment; registry availability beyond the selected hydration lane.

Open retained linux/macos/windows evidence

One exact-scope live grant admitted the selected scaffold action and produced one completed crossing transaction with valid receipt history.

Evidence boundary

Exercised: prebound signed-file authority, exact selected-scope admission, expired, revoked, and out-of-scope refusal, crossing transaction and receipt archive. Engineering note: published. Limits: Provider-attested or independently administered authority separation; absence of every escalation path, mount alias, metadata credential, or host-control endpoint; verified human, CI, or platform identity; one-use authority or atomic broker consumption; repository-global safety, application correctness, or prevention of raw-shell bypasses; artifact retention beyond GitHub's configured retention policy.

Open retained linux evidence

Ordinary writes did not replace an existing contract.

Evidence boundary

Exercised: source-bound candidate, create-new application, Git carrier, Windows read-only refusal. Engineering note: draft. Limits: Caddy build, test, server, or runtime behavior; network, release, or repository-global governance.

Open retained linux/macos/windows evidence

Linux and macOS converged on byte-identical candidate evidence after exact path-spelling repair.

Evidence boundary

Exercised: candidate identity, case-sensitive source inventory, strict completeness refusal. Engineering note: draft. Limits: Rust, Turbo, Tauri, Playwright, desktop, packaging, or release behavior.

Open retained linux/macos/windows evidence

Caller-owned reusable-workflow inputs remained unresolved.

Evidence boundary

Exercised: candidate capture, reusable workflow inputs, Git LFS acquisition posture. Engineering note: draft. Limits: Complete LFS content; generators, language clients, release, or runtime behavior.

Open retained linux/macos/windows evidence

Check, formatting, unit, and PostgreSQL integration lanes remained distinct.

Evidence boundary

Exercised: CI lane detection, toolchain selection, service requirements, strict candidate refusal. Engineering note: draft. Limits: Compilation, formatting, tests, PostgreSQL state, shell integration, runtime, or release behavior.

Open retained linux/macos/windows evidence

Creation left only ota.yaml as repository residue.

Evidence boundary

Exercised: source-bound candidate, create-new contract application, semantic no-op. Engineering note: draft. Limits: Repository task execution; candidate approval; runtime or release behavior.

Open retained linux/macos evidence

The registered representation-only upgrade preserved semantic contract identity.

Evidence boundary

Exercised: registered legacy upgrade, Git-carrier application, semantic no-op. Engineering note: draft. Limits: Repository task execution; runtime, provider, or release behavior.

Open retained linux/macos evidence

Task and workflow canaries refused with explicit typed denial before their selected provider/database precursor, worktree/child precursor, outcome hook, and workflow setup sentinels.

Evidence boundary

Exercised: typed migration refusal, selected setup/dependency/hook witnesses, private archive, workflow-only assurance, review-only candidate. Engineering note: draft. Limits: Database correctness or actual mutation prevention; provider contact or behavior; arbitrary child-process absence; repository-wide immutability or readiness; positive assurance; archive export safety.

Open retained linux/macos evidence

Task and workflow canaries refused with explicit typed denial before their selected provider/database precursor, worktree/child precursor, outcome hook, and workflow setup sentinels.

Evidence boundary

Exercised: typed migration refusal, selected setup/dependency/hook witnesses, private archive, workflow-only assurance, review-only candidate. Engineering note: draft. Limits: Database correctness or actual mutation prevention; provider contact or behavior; arbitrary child-process absence; repository-wide immutability or readiness; positive assurance; archive export safety.

Open retained linux/macos evidence

Typed refusal occurred before the selected fixture's setup and environment-rendering paths.

Evidence boundary

Exercised: typed run, up, and proof refusal, CI and sandbox policy re-evaluation, negative canaries, private archive and Doctor assurance, review-only archive candidate. Engineering note: draft. Limits: Provider contact or mutation; arbitrary child-process absence; repository-wide immutability; database correctness; positive assurance; archive export safety.

Open retained linux/macos evidence

An explicit typed deny produced a blocked preview with one admitted application plan and its explicit deny decision.

Evidence boundary

Exercised: typed up dry-run admission, blocked preview envelope, Core plan-to-executor continuity, sandbox admission continuity. Engineering note: draft. Limits: Provider contact or mutation; arbitrary child-process absence; repository-wide immutability; database correctness; positive assurance; archive export safety.

Open retained linux/macos evidence

Selected native lanes exposed one existing site-format failure without Ota weakening the verifier.

Evidence boundary

Exercised: selected native verification lanes, digest-pinned Node container context, detection and candidate review. Engineering note: draft. Limits: MCP runtime loading; credentialed CAEP; GitHub merge; communications; Liminal lifecycle; Pythia ALLOW as execution authority.

Open retained linux evidence

The selected SQLite contributor lanes and the non-blocking synthetic PostgreSQL lane passed at the reviewed PR head and its upstream check matrix.

Evidence boundary

Exercised: contract-to-CI drift, SQLite contributor suite, disposable synthetic PostgreSQL 16 lane, strict positive and controlled negative validation. Engineering note: published. Limits: Production-data safety or arbitrary database state; MySQL or release behavior; the separate date-classification edge case; repository-wide governance, ongoing adoption, endorsement, or behavior beyond the merged selected lanes.

Open retained linux/macos/windows evidence

The native and container lanes passed their separately selected local-index freshness tasks at the fork revision.

Evidence boundary

Exercised: contract-to-CI drift, Ubuntu native local index, Linux container local index, disposable two-revision graph and query fixture. Engineering note: draft. Limits: Aggregate task selection in container mode; cloud-index equivalence or universal parser correctness; every MCP consumer or repository-wide governance; maintainer merge or adoption.

Open retained linux evidence

The non-blocking execution lane passed at the fork revision with a fresh evaluation and repository-owned evidence checks.

Evidence boundary

Exercised: contract-to-CI drift, pinned PINT-format evaluation task, repository-owned fresh-measurement verifier, generated-data artifact retention. Engineering note: draft. Limits: Lakera's official PINT benchmark or certification; all filesystem mutations or arbitrary runner integrity; repository-wide evaluation correctness; maintainer merge or adoption.

Open retained linux evidence

The non-blocking Linux fixture passed its preflight, matching-build, and injected-drift checks at the fork revision.

Evidence boundary

Exercised: contract-to-CI drift, disposable Rust fixture configuration preflight, two-build byte comparison, controlled archive-byte drift refusal. Engineering note: draft. Limits: Upstream release determinism matrix or package publishing; cross-platform behavior, signing, or production artifact identity; agent-safe execution; maintainer merge or adoption.

Open retained linux evidence

Published notes for registered cases

Published notes explain a reusable lesson from a case. Draft notes remain unlinked review artifacts until their evidence and publication posture are approved.

EventCatalog

The declared consumer closure built after its generator and sibling prerequisites.

create-chrome-extension authority fixture

One exact-scope live grant admitted the selected scaffold action and produced one completed crossing transaction with valid receipt history.

dbmask

The selected SQLite contributor lanes and the non-blocking synthetic PostgreSQL lane passed at the reviewed PR head and its upstream check matrix.

How to read a case

Immutable pressure means a retained hosted matrix binds the listed source and controls. It does not broaden the result beyond the case's explicit facts.
Design-partner pressure is a fork-owned review artifact. Its listed Ota version may be pre-release or released; neither status implies upstream adoption or endorsement.
Merged design-partner evidence records maintainer acceptance of the bounded integration, not repository-wide governance, ongoing use, or endorsement.
When a case exposes an Ota defect, the correction requires separate regression and pressure evidence. The original green matrix does not retroactively prove the repair.