Skip to content

BEAI Harness for Codex v0.1.0 Public Candidate

Pre-release
Pre-release

Choose a tag to compare

View all tags
@nbeai nbeai released this 26 Jun 14:12
v0.1.0-public-candidate
45aaa11

GitHub Release Notes v0.1.0 Public Candidate

BEAI Harness for Codex v0.1.0 is a verified public-candidate source/archive distribution.

It is not published to npm yet. Use the source checkout or verified release archive path until hosted releases are prepared.

The source/archive distribution intentionally excludes generated .beai-harness evidence. After unpacking, regenerate evidence with the release checklist before expecting npm run readiness to report ready.

What It Is

BEAI Harness for Codex is a local CLI and documentation system for Codex-assisted development. It helps users move through preflight, product brief, build plan, verification, install, recovery, loop validation, and release readiness with evidence and rollback paths.

Highlights

  • Project intelligence for CLI, frontend, backend, full-stack, and OpenClaw plugin shapes.
  • Plain-language brief and plan flow for non-developers.
  • Completion gates that look beyond passing tests.
  • Review-first install, patch, uninstall, and rollback behavior.
  • Codex-facing AGENTS.md and skill draft/apply helpers.
  • Bounded loop flow with visual proposal, safe apply, and post-apply comparison.
  • Field-Readiness Engineering protocol for actor-based simulation, real-case sources, weighted rubric, reinforcement loop, and evidence contract.
  • Engineering-quality and self-check gates for responsibility maps, status models, field evidence schema, project-type quality checks, command/document sync, and release confidence.
  • Service operations rail for service planning, secrets, deploy plans, health checks, rollback/incident evidence, approval boundaries, and adapter dry-runs.
  • Multi-fixture benchmark for CLI, frontend, and full-stack projects.
  • Public smoke, external sample smoke, release archive verification, and archive bootstrap smoke.
  • Final hardening audit and readiness gate.

Verification

Latest public-candidate evidence:

  • npm run verify: passed.
  • Node test suite: 138 passed.
  • npm run smoke: passed, 42/42, including creator brief, response coach, scenario test-plan/run, design repair-plan, service plan, service blueprint, secrets check, deploy plan, health check, ops status/release/rollback/incident, approval gates, and Cloudflare/Supabase adapter plan/dry-run/scaffold.
  • node bin/beai.js perceived-quality --apply: passed, 210/210, covering audience, surface, risk, and work-size scenarios.
  • node bin/beai.js real-world-simulation --apply: passed, 20/20, covering external benchmark-derived repository execution, dialogue, webapp agency, harness adapter, and productivity-friction patterns.
  • node bin/beai.js field-readiness --apply: ready, with 8 components, 9 simulation actor profiles, 6 real-case source families, and a 100-point rubric.
  • node bin/beai.js engineering-quality --apply: ready, with harness-internal and project-type quality gates.
  • node bin/beai.js self-check --apply: ready, requiring engineering-quality readiness.
  • node bin/beai.js benchmark --apply: passed, 3/3.
  • Release archive verification: verified.
  • Release bootstrap smoke: passed.
  • Public readiness: ready.
  • Final review pack: module-level review map included.

Archive

Latest local candidate archive:

.beai-harness/release/beai-harness-for-codex-0.1.0-public-candidate.tar

Latest recorded SHA-256 is written by the release command to:

.beai-harness/release/PUBLIC-CANDIDATE-ARCHIVE-RECEIPT.json

Regenerate before publishing if any file changes. The archive SHA is intentionally not hard-coded in this included release note because doing so would make the archive hash self-referential. Treat .beai-harness/release/PUBLIC-CANDIDATE-ARCHIVE-RECEIPT.json and .beai-harness/release/FINAL-CONSISTENCY.md as the current hash authority.

Installation From Archive

From an unpacked archive root:

node scripts/install-from-archive.mjs
node scripts/install-from-archive.mjs --apply

The first command is preflight-only. The second applies the local bootstrap after review.

Known Limits

  • No npm package publication yet.
  • No signed release artifacts yet.
  • No hosted one-command installer yet.
  • No third-party security audit yet.
  • Completion gates are heuristic and do not prove business, security, accessibility, performance, or deployment correctness by themselves.

Ownership

MIT. Copyright (c) 2026 윤 (@aigis0927).

Contributors

aigis0927
Assets 3
Loading