Pressure Testing | ota repo readiness docs — ota

Recommended next

Engineering notes 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. This page is generated from its public-safe projection and cannot add claims that are absent from the registry.

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.

Current evidence corpus

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

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

One exact workflow refusal archive promoted only its matching workflow claim.

Evidence boundary

Exercised: typed migration refusal, private archive, workflow-only assurance, review-only candidate. Engineering note: draft. Limits: Database correctness; provider behavior; complete migration coverage; repository-wide readiness.

Open retained linux/macos evidence

One exact workflow refusal archive promoted only its matching workflow claim.

Evidence boundary

Exercised: typed migration refusal, private archive, workflow-only assurance, review-only candidate. Engineering note: draft. Limits: Database correctness; provider behavior; complete migration coverage; repository-wide readiness.

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

Published engineering notes

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.

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.
Pre-release design-partner pressure is a fork-owned review artifact. It remains distinct from upstream adoption and released-version proof.
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.