From f4e696e89a0232b7fa8bd15955ba869450fc450b Mon Sep 17 00:00:00 2001 From: docushell-admin Date: Wed, 24 Jun 2026 12:17:53 +0530 Subject: [PATCH 1/3] Refresh patch 0.1.1 execution status Signed-off-by: docushell-admin --- .github/scripts/test_execution_status.py | 36 ++++++--- CHANGELOG.md | 1 + docs/execution-status.md | 28 +++++-- docs/validation/README.md | 11 ++- ...on-status-refresh-validation-2026-06-24.md | 80 +++++++++++++++++++ 5 files changed, 136 insertions(+), 20 deletions(-) create mode 100644 docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md diff --git a/.github/scripts/test_execution_status.py b/.github/scripts/test_execution_status.py index 7c84477..fbe71b6 100644 --- a/.github/scripts/test_execution_status.py +++ b/.github/scripts/test_execution_status.py @@ -34,8 +34,10 @@ def test_status_is_scoped_to_internal_continuation(self) -> None: text = status_text() self.assertIn( - "Status: Public beta evaluation is approved for the GitHub source repository and the three bounded " - "Rust library crates `ethos-doc-core`, `ethos-verify`, and `ethos-pdf` at `0.1.0`.", + "Status: Public beta evaluation is approved for the GitHub source repository, the three bounded " + "Rust library crates `ethos-doc-core`, `ethos-verify`, and `ethos-pdf`, the Python " + "`ethos-pdf` wheel, the npm `@docushell/ethos-pdf` CLI package, the macOS arm64 CLI " + "artifact, and the Linux x64 CLI artifact at `0.1.1`.", text, ) self.assertIn("Internal Milestone D source-only closeout remains complete", text) @@ -81,21 +83,37 @@ def test_public_posture_boundary_remains_explicit(self) -> None: text = status_text() self.assertIn( - "Public language may use this exact approved sentence on the current source and Rust crate evaluation surfaces", + "Public language may use this exact approved sentence on the current source, Rust crate, Python wheel, " + "npm package, macOS arm64 CLI artifact, and Linux x64 CLI artifact evaluation surfaces", text, ) self.assertIn( - "Ethos is public beta for source and Rust crate evaluation. It verifies whether AI citations " - "are grounded in document evidence across native Ethos JSON and supported foreign " - "parser outputs. Rust library crates `ethos-doc-core`, `ethos-verify`, and `ethos-pdf` " - "are available on crates.io at `0.1.0` for evaluation. Hosted surfaces, production " - "positioning, and public benchmark claims remain blocked.", + "Ethos is public beta for source, Rust crate, Python wheel, macOS arm64 CLI artifact, " + "Linux x64 CLI artifact, and npm `@docushell/ethos-pdf` evaluation. It verifies whether " + "AI citations are grounded in document evidence across native Ethos JSON and supported " + "foreign parser outputs. Rust library crates `ethos-doc-core`, `ethos-verify`, and " + "`ethos-pdf` are available on crates.io at `0.1.1` for evaluation. The Python " + "`ethos-pdf` wheel, npm `@docushell/ethos-pdf@0.1.1` package, and macOS arm64/Linux x64 " + "CLI artifacts are available for evaluation with caller-provided PDFium. Hosted " + "surfaces, production positioning, Windows packaged artifacts, bundled project-maintained " + "PDFium builds, `ethos-doc`, `ethos-rag`, public benchmark reports, public benchmark " + "claims, and speed, footprint, parser-quality, table-quality, or production claims remain blocked.", text, ) self.assertIn("ethos-doc-core", text) self.assertIn("ethos-verify", text) self.assertIn("ethos-pdf", text) - self.assertIn("wheels, npm packages, binaries, hosted surfaces", text) + self.assertIn( + "Patch `0.1.1` closeout records supersede those historical blockers only for the approved " + "source, Rust crate, Python wheel, npm package, macOS arm64 CLI artifact, and Linux x64 CLI " + "artifact evaluation surfaces.", + text, + ) + self.assertIn( + "Hosted surfaces, Windows packaged artifacts, bundled project-maintained PDFium builds, " + "`ethos-doc`, and `ethos-rag` remain blocked.", + text, + ) self.assertIn("All wording beyond that sentence still requires claim-audit", text) self.assertIn("Closed for the exact approved pre-alpha sentence only", text) self.assertIn("milestone-e-public-beta-source-only-approval-validation-2026-06-20.md", text) diff --git a/CHANGELOG.md b/CHANGELOG.md index c0cc6c1..207a5cd 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,7 @@ ## Unreleased +- boundary-exception: refresh patch `0.1.1` execution status for published evaluation surfaces while retaining hosted, production, Windows, bundled PDFium, benchmark, `ethos-doc`, and `ethos-rag` blockers. - boundary-exception: document bounded patch `0.1.1` public install paths for published evaluation surfaces while retaining hosted, production, Windows, bundled PDFium, benchmark, `ethos-doc`, and `ethos-rag` blockers. - boundary-exception: close patch `0.1.1` Python PyPI publication with exact registry evidence; no public install wording, hosted, production, Windows, bundled PDFium, benchmark, `ethos-doc`, or `ethos-rag` boundary change. - boundary-exception: approve exact patch `0.1.1` deterministic Python PyPI wheel publication decision for later operator upload; no PyPI upload or support-boundary change. diff --git a/docs/execution-status.md b/docs/execution-status.md index ad8a1a4..310ee91 100644 --- a/docs/execution-status.md +++ b/docs/execution-status.md @@ -1,8 +1,10 @@ # Ethos Execution Status -Date: 2026-06-22 +Date: 2026-06-24 Owner: product / decider -Status: Public beta evaluation is approved for the GitHub source repository and the three bounded Rust library crates `ethos-doc-core`, `ethos-verify`, and `ethos-pdf` at `0.1.0`. Internal Milestone D source-only closeout remains complete, with Milestone E prep source-only closeout recorded for the internal prep boundary. Week 0 governance is accepted, WS-ENGINE Phase 1 has a real narrow PDFium path, WS-VERIFY-ALPHA has real deterministic evidence checks over native Ethos JSON and pinned OpenDataLoader output, WS-HARNESS has fail-closed readiness scaffolding, the Gate Zero corpus/hardware manifest and direct competitor lock are frozen/signed, ADR-0005 records an accepted `PROCEED` decision for internal Milestone B continuation, ADR-0006 closes package identifier/trademark validation, ADR-0007 locks the product direction, and public source plus bounded Rust crate evaluation wording is green. The exact current public sentence approved for source and Rust crate evaluation surfaces is: "Ethos is public beta for source and Rust crate evaluation. It verifies whether AI citations are grounded in document evidence across native Ethos JSON and supported foreign parser outputs. Rust library crates `ethos-doc-core`, `ethos-verify`, and `ethos-pdf` are available on crates.io at `0.1.0` for evaluation. Hosted surfaces, production positioning, and public benchmark claims remain blocked." Milestone C has a source-tree internal artifact-validation closeout for the RAG chunk and security-report trust-loop checks. Milestone D has a source-tree internal source-only closeout recorded in `docs/validation/milestone-d-final-closeout-validation-2026-06-19.md`; the narrow `verify_citations` v1 contract in `docs/milestone-d-verify-citations-contract.md` remains carried by the existing `ethos verify` path and fixture-backed validation. The D `crop_element` v1 contract in `docs/milestone-d-crop-element-contract.md` is carried by the source-bound `ethos crop_element` CLI command plus existing `ethos verify --crop-dir` evidence artifacts; `ethos-core::crop_element` validates request identity, resolves one native document element, and emits descriptor/rendered crop metadata for that source-only contract when caller-provided source PDF bytes are bound. The `sandbox_subprocess` v1 contract in `docs/milestone-d-sandbox-subprocess-contract.md` classifies existing PDF worker-process timeout, memory-limit, stable-error, and diagnostics-gated stderr behavior without adding hardened sandbox rules. The first Milestone E prep boundary is recorded in `docs/milestone-e-prep-scope.md`, the internal fixture-candidate inventory is recorded in `docs/milestone-e-fixture-candidates.json`, internal fixture-promotion criteria are recorded in `docs/milestone-e-fixture-promotion-criteria.json`, the internal trust-loop walkthrough plan is recorded in `docs/milestone-e-internal-trust-loop-walkthrough.json`, the internal trust-loop use protocol is recorded in `docs/milestone-e-internal-trust-loop-use-protocol.json`, the internal trust-loop rehearsal/evidence matrix is recorded in `docs/milestone-e-internal-trust-loop-rehearsal-evidence-matrix.json`, and the internal trust-loop blocker ledger is recorded in `docs/milestone-e-internal-trust-loop-blocker-ledger.json`; these E prep JSON artifacts are schema-validated by `schemas/validate_examples.py` and only identify tracked trust-loop fixture candidates, internal promotion criteria, internal walkthrough sequencing, source-checkout rules for internal use, internal evidence-lane rehearsal planning, blocked-output alignment, evidence-lane alignment, diagnostic-boundary alignment, promotion-status alignment at `not_promoted_beyond_internal_fixture_planning`, source-status alignment at `source-only-pre-alpha-internal-milestone-e-prep`, applies-to binding alignment across current E source artifacts, required-before alignment for current readiness gates including `make milestone-e-prep remains green`, validation-record source-head alignment for each `Validated source HEAD before this record` line, and explicit blocker tracking that does not resolve or soften blockers. The Milestone E prep source-only closeout is recorded in `docs/validation/milestone-e-final-closeout-validation-2026-06-20.md` and does not resolve or soften blockers outside the approved public beta and Rust crate evaluation surfaces. Public benchmark reports, release artifacts, wheels, npm packages, binaries, hosted surfaces, production positioning, project-maintained PDFium builds, `ethos-doc`, `ethos-rag`, and all performance/quality/footprint claims remain blocked. The controlled-run handoff remains `docs/gate-zero-evidence-runbook.md`; the accepted decision record is `docs/decisions/ADR-0005-gate-zero-decision.md`. +Status: Public beta evaluation is approved for the GitHub source repository, the three bounded Rust library crates `ethos-doc-core`, `ethos-verify`, and `ethos-pdf`, the Python `ethos-pdf` wheel, the npm `@docushell/ethos-pdf` CLI package, the macOS arm64 CLI artifact, and the Linux x64 CLI artifact at `0.1.1`. Internal Milestone D source-only closeout remains complete, with Milestone E prep source-only closeout recorded for the internal prep boundary. Week 0 governance is accepted, WS-ENGINE Phase 1 has a real narrow PDFium path, WS-VERIFY-ALPHA has real deterministic evidence checks over native Ethos JSON and pinned OpenDataLoader output, WS-HARNESS has fail-closed readiness scaffolding, the Gate Zero corpus/hardware manifest and direct competitor lock are frozen/signed, ADR-0005 records an accepted `PROCEED` decision for internal Milestone B continuation, ADR-0006 closes package identifier/trademark validation, ADR-0007 locks the product direction, and patch `0.1.1` publication/install wording closeouts are recorded for the approved evaluation surfaces. The exact current public sentence approved for source, Rust crate, Python wheel, npm package, macOS arm64 CLI artifact, and Linux x64 CLI artifact evaluation surfaces is: "Ethos is public beta for source, Rust crate, Python wheel, macOS arm64 CLI artifact, Linux x64 CLI artifact, and npm `@docushell/ethos-pdf` evaluation. It verifies whether AI citations are grounded in document evidence across native Ethos JSON and supported foreign parser outputs. Rust library crates `ethos-doc-core`, `ethos-verify`, and `ethos-pdf` are available on crates.io at `0.1.1` for evaluation. The Python `ethos-pdf` wheel, npm `@docushell/ethos-pdf@0.1.1` package, and macOS arm64/Linux x64 CLI artifacts are available for evaluation with caller-provided PDFium. Hosted surfaces, production positioning, Windows packaged artifacts, bundled project-maintained PDFium builds, `ethos-doc`, `ethos-rag`, public benchmark reports, public benchmark claims, and speed, footprint, parser-quality, table-quality, or production claims remain blocked." Milestone C has a source-tree internal artifact-validation closeout for the RAG chunk and security-report trust-loop checks. Milestone D has a source-tree internal source-only closeout recorded in `docs/validation/milestone-d-final-closeout-validation-2026-06-19.md`; the narrow `verify_citations` v1 contract in `docs/milestone-d-verify-citations-contract.md` remains carried by the existing `ethos verify` path and fixture-backed validation. The D `crop_element` v1 contract in `docs/milestone-d-crop-element-contract.md` is carried by the source-bound `ethos crop_element` CLI command plus existing `ethos verify --crop-dir` evidence artifacts; `ethos-core::crop_element` validates request identity, resolves one native document element, and emits descriptor/rendered crop metadata for that source-only contract when caller-provided source PDF bytes are bound. The `sandbox_subprocess` v1 contract in `docs/milestone-d-sandbox-subprocess-contract.md` classifies existing PDF worker-process timeout, memory-limit, stable-error, and diagnostics-gated stderr behavior without adding hardened sandbox rules. The first Milestone E prep boundary is recorded in `docs/milestone-e-prep-scope.md`, the internal fixture-candidate inventory is recorded in `docs/milestone-e-fixture-candidates.json`, internal fixture-promotion criteria are recorded in `docs/milestone-e-fixture-promotion-criteria.json`, the internal trust-loop walkthrough plan is recorded in `docs/milestone-e-internal-trust-loop-walkthrough.json`, the internal trust-loop use protocol is recorded in `docs/milestone-e-internal-trust-loop-use-protocol.json`, the internal trust-loop rehearsal/evidence matrix is recorded in `docs/milestone-e-internal-trust-loop-rehearsal-evidence-matrix.json`, and the internal trust-loop blocker ledger is recorded in `docs/milestone-e-internal-trust-loop-blocker-ledger.json`; these E prep JSON artifacts are schema-validated by `schemas/validate_examples.py` and only identify tracked trust-loop fixture candidates, internal promotion criteria, internal walkthrough sequencing, source-checkout rules for internal use, internal evidence-lane rehearsal planning, blocked-output alignment, evidence-lane alignment, diagnostic-boundary alignment, promotion-status alignment at `not_promoted_beyond_internal_fixture_planning`, source-status alignment at `source-only-pre-alpha-internal-milestone-e-prep`, applies-to binding alignment across current E source artifacts, required-before alignment for current readiness gates including `make milestone-e-prep remains green`, validation-record source-head alignment for each `Validated source HEAD before this record` line, and explicit blocker tracking that does not resolve or soften blockers. The Milestone E prep source-only closeout is recorded in `docs/validation/milestone-e-final-closeout-validation-2026-06-20.md` and does not resolve or soften blockers outside the approved public beta evaluation surfaces. Hosted surfaces, production positioning, Windows packaged artifacts, bundled project-maintained PDFium builds, `ethos-doc`, `ethos-rag`, public benchmark reports, public benchmark claims, and all speed/footprint/parser-quality/table-quality/production claims remain blocked. The controlled-run handoff remains `docs/gate-zero-evidence-runbook.md`; the accepted decision record is `docs/decisions/ADR-0005-gate-zero-decision.md`. + +Older Milestone E paragraphs below preserve historical review records and their blockers at the time they were written. Patch `0.1.1` closeout records supersede those historical blockers only for the approved source, Rust crate, Python wheel, npm package, macOS arm64 CLI artifact, and Linux x64 CLI artifact evaluation surfaces. Public approval lane blocker prep is recorded in `docs/milestone-e-public-approval-lane-blockers.json` and schema-bound by @@ -109,7 +111,7 @@ publication remain blocked. ## Current Reality -The repository is still pre-alpha, but it is no longer only contract/scaffold code. Real parsing and real alpha verification exist. They are narrow, fixture-backed, and now have an accepted internal Gate Zero decision for roadmap control. That decision is not a public benchmark report, release approval, package approval, production approval, or claim approval. +The repository is in public beta/evaluation for the approved source, package, and CLI artifact surfaces, but it is not production-ready. Real parsing and real alpha verification exist. They are narrow, fixture-backed, and now have an accepted internal Gate Zero decision for roadmap control. That decision is not a public benchmark report, release approval, package approval, production approval, or claim approval. The committed implementation now includes: @@ -124,7 +126,7 @@ The committed implementation now includes: - `ethos verify` now produces non-empty quote, value, presence, and table-cell verification checks over native Ethos document JSON and synthetic OpenDataLoader-style JSON through `--grounding opendataloader-json`; it also verifies quote/value/presence citations over pinned real OpenDataLoader 2.4.7 JSON, including grounded and ungrounded cases, maps explicit real OpenDataLoader-style row/cell structures to table-cell grounding, and normalizes conservative real-style text/child-container aliases when page/bbox/text data remains explicit. Citation/config inputs are rejected when they drift outside the closed schemas. The public demo harness covers grounded, ungrounded, split-quote, not-found, stale-fingerprint, unsupported non-v1 claim, capability-limited, malformed-citation, malformed OpenDataLoader-style input, and summary-format reject paths. - Verification semantics are now trust-honest at alpha scope: quote containment is explicitly labeled, value/table-cell checks require normalized equality, fingerprint-pinned citations fail closed when source fingerprints are unavailable, and structured capability limits explain why a run is downgraded. - `make verify-alpha` is the current alpha trust-loop command: it checks native examples, split-quote evidence matching, unsupported non-v1 claim reporting, synthetic OpenDataLoader-style examples, pinned real OpenDataLoader grounded/ungrounded examples, schema validation, verify-alpha case inventory coverage, usage diagnostics for malformed citations and malformed OpenDataLoader-style structures, byte-identical repeated verification reports, byte-identical native crop descriptors, summary diagnostics for an ungrounded native case, and foreign fixture manifest hash binding. `make milestone-b-internal-checks` composes the current internal Milestone B validation path across fixture validation, font-policy profile checks, verify alpha, layout evaluator, Python surface tests, and policy gates; CI has a static guard for that target's command wiring. -- An internal Python surface scaffold exists under `python/ethos_pdf`. It shells out to a caller-provided local `ethos` CLI binary for `ethos doc parse` JSON, Markdown, text output, and source-bound `ethos crop_element` JSON/artifact arguments, and has stdlib unit tests that use a fake local command. This is pre-alpha scaffolding for API shape work, not a public installation or publication path. +- The Python surface under `python/ethos_pdf` shells out to a caller-provided local `ethos` CLI binary for `ethos doc parse` JSON, Markdown, text output, and source-bound `ethos crop_element` JSON/artifact arguments, and has stdlib unit tests that use a fake local command. The published `ethos-pdf==0.1.1` wheel exposes this bounded wrapper for evaluation; it does not bundle the CLI or PDFium. - Native Ethos verification can emit deterministic, schema-backed crop descriptor JSON artifacts through `--crop-dir`; these bind `document_fingerprint`, page, bbox, and check ids. Native `crop_ref` filenames are logical evidence references derived from document fingerprint, check id, and page, while descriptors still record the exact observed bbox. When `--crop-source-pdf` is supplied, the CLI validates source-PDF fingerprint binding and emits PNG crop artifacts whose filenames, byte hashes, dimensions, and source fingerprint are bound from the descriptor. `make verify-rendered-crops` checks same-host repeated-run stability for the rendered artifact path, and `make compare-rendered-crops` classifies two rendered-crop runs by separating logical evidence identity from rendered artifact byte equality. Cross-platform rendered image determinism is not claimed; the 2026-06-14 macOS arm64 vs Linux x64 validation record in `docs/validation/rendered-crops-2026-06-14.md` preserved document fingerprint and `payload_sha256` but failed rendered artifact byte equality because the evidence bbox differed slightly across platforms. - `ethos rag chunk` has a committed-example artifact loop over `schemas/examples/document.example.json` and `schemas/examples/chunks.example.jsonl`. The current internal checks cover exact fixture/golden output, repeated-run byte identity, schema/example validation, stale page/element/bbox-page reference rejection, and default-chunk exclusion warning-reference rejection. - `ethos security report` has a source-only pre-alpha artifact check over the committed document example. The current internal checks cover deterministic report output, report/source identity grounding, security-warning lane and message diagnostics, locator grounding, inventory/report parity, summary drift, warning id uniqueness, deterministic warning numbering, and explicit rejection of unsupported current source-warning references. @@ -140,10 +142,15 @@ The committed implementation now includes: - `make milestone-d-internal-contracts PYTHON=/bin/python` composes the current Milestone D source-only contract gates and has a static guard for that target's command wiring and contract registry, plus the Milestone D contract closeout validation record in `docs/validation/milestone-d-contract-closeout-validation-2026-06-19.md` and final closeout validation record in `docs/validation/milestone-d-final-closeout-validation-2026-06-19.md`. Full 13-D exit is complete for the current source-only pre-alpha scope. - `make milestone-e-prep PYTHON=/bin/python` composes the Milestone E prep guard over `docs/milestone-e-prep-scope.md`, `docs/milestone-e-fixture-candidates.json`, `docs/milestone-e-fixture-promotion-criteria.json`, `docs/milestone-e-internal-trust-loop-walkthrough.json`, `docs/milestone-e-internal-trust-loop-use-protocol.json`, `docs/milestone-e-internal-trust-loop-rehearsal-evidence-matrix.json`, `docs/milestone-e-internal-trust-loop-blocker-ledger.json`, `docs/milestone-e-public-approval-lane-blockers.json`, `docs/milestone-e-public-beta-approval-prep.json`, `docs/milestone-e-package-publication-approval-prep.json`, status/roadmap posture checks, public-surface posture checks, the claims gate, public pre-alpha wording approval guard, release-readiness next-step approval guard, H1 public-safe comparison closeout guard, H2 source-snapshot scope approval guard, source-snapshot candidate audit guard, H2 source-snapshot candidate evidence guard, H2 source-snapshot closeout guard, schema validation, schema-registry alignment, public-boundary alignment, blocked-output alignment, evidence-lane alignment, diagnostic-boundary alignment, promotion-status alignment, source-status alignment, applies-to binding alignment, required-before alignment, public approval lane blocker validation, public beta approval prep validation, public beta required-evidence validation, public beta source-only approval validation, package publication approval prep validation, package publication prep approval validation, package publication evidence record validation, package publication metadata-readiness validation, package publication dry-run/smoke validation, package publication version/tag policy validation, package publication PDFium boundary validation, package publication dependency-ordering validation, validation-command indexing, validation-record indexing, validation-record source-head alignment, the prep guard-sequence index, current prep guard validation, the Milestone E prep source-only closeout record in `docs/validation/milestone-e-final-closeout-validation-2026-06-20.md`, and diff hygiene. This target is source-only and intentionally excludes public-report, release, package, hosted, and broad demo-generation workflows. -Still absent or not claimable: public benchmark reports, public competitor-comparison claims, public speed/quality/footprint claims, OCR/image-only support, real table extraction, mature list/heading/layout semantics beyond current fixture-backed alpha paths, semantic/arithmetic verification beyond deterministic evidence lookup, Phase 2 project-maintained PDFium builds, release packaging, and any public wording beyond the exact approved source-only public beta wording. +Still absent or not claimable: public benchmark reports, public competitor-comparison claims, public speed/quality/footprint claims, OCR/image-only support, real table extraction, mature list/heading/layout semantics beyond current fixture-backed alpha paths, semantic/arithmetic verification beyond deterministic evidence lookup, hosted surfaces, production positioning, Windows packaged artifacts, Phase 2 project-maintained PDFium builds, `ethos-doc`, `ethos-rag`, and any public wording beyond the exact approved patch `0.1.1` public beta/evaluation wording. ## Human / External Blockers +This section preserves the historical Gate Zero and Milestone E blocker ledger. Patch `0.1.1` +closeout records above supersede its old package/release blockers only for the approved source, +Rust crate, Python wheel, npm package, macOS arm64 CLI artifact, and Linux x64 CLI artifact +evaluation surfaces. + PM execution packet: `benchmarks/gate-zero/FREEZE_PACKET.md`. Resolved control point: ADR-0005 is accepted with `PROCEED` for internal Milestone B @@ -164,6 +171,10 @@ The corpus/hardware freeze and direct competitor pins are recorded in `benchmark ## Approved Next-Step Sequence +This sequence is retained as historical 2026-06-20 execution context. Later patch `0.1.1` +records closed the approved release/package/public-install lanes for the bounded evaluation +surfaces named in the current status summary. + Manual product approval on 2026-06-20 approved this execution sequence for the next release-readiness work. That sequence approval did not itself close H1 or H2. It does not approve public beta, does not approve public benchmark reports, does not approve release artifacts, does @@ -191,6 +202,9 @@ records close H1 and H2 only within their stated boundaries. ## Current Milestone Posture +Historical milestone-record summaries below keep their at-the-time blocker wording. The current +patch `0.1.1` status is the source of truth for approved evaluation surfaces and retained blockers. + Milestone A has an accepted internal Gate Zero decision for roadmap control, Milestone B is internally closed for the current source-tree validation scope, Milestone C has an internal artifact-validation closeout record, and Milestone D is internally closed for the current source-only pre-alpha scope. Milestone E prep is limited to the source-only boundary in `docs/milestone-e-prep-scope.md`, the internal fixture inventory in `docs/milestone-e-fixture-candidates.json`, the internal fixture-promotion criteria in `docs/milestone-e-fixture-promotion-criteria.json`, the internal trust-loop walkthrough plan in `docs/milestone-e-internal-trust-loop-walkthrough.json`, the internal trust-loop use protocol in `docs/milestone-e-internal-trust-loop-use-protocol.json`, the internal trust-loop rehearsal/evidence matrix in `docs/milestone-e-internal-trust-loop-rehearsal-evidence-matrix.json`, the internal trust-loop blocker ledger in `docs/milestone-e-internal-trust-loop-blocker-ledger.json`, the public approval lane blocker ledger in `docs/milestone-e-public-approval-lane-blockers.json`, public beta approval prep in `docs/milestone-e-public-beta-approval-prep.json`, public beta required-evidence records in `docs/validation/`, source-only public beta approval in `docs/validation/milestone-e-public-beta-source-only-approval-validation-2026-06-20.md`, package publication approval prep in `docs/milestone-e-package-publication-approval-prep.json`, package publication evidence records in `docs/validation/`, package publication metadata-readiness follow-up in `docs/validation/milestone-e-package-publication-metadata-readiness-closeout-validation-2026-06-21.md`, package publication current dry-run/smoke follow-up in `docs/validation/milestone-e-package-publication-current-dry-run-smoke-validation-2026-06-22.md`, package publication version/tag policy follow-up in `docs/validation/milestone-e-package-publication-version-tag-policy-closeout-validation-2026-06-21.md`, package publication PDFium boundary follow-up in `docs/validation/milestone-e-package-publication-pdfium-boundary-closeout-validation-2026-06-21.md`, package publication dependency-ordering follow-up in `docs/validation/milestone-e-package-publication-dependency-ordering-closeout-validation-2026-06-21.md`, package publication manifest-migration prep follow-up in `docs/validation/milestone-e-package-publication-manifest-migration-prep-validation-2026-06-21.md`, package publication manifest-activation prep follow-up in `docs/validation/milestone-e-package-publication-manifest-activation-prep-validation-2026-06-21.md`, package publication registry-assembly prep follow-up in `docs/validation/milestone-e-package-publication-registry-assembly-prep-validation-2026-06-21.md`, package publication registry-assembly activation prep follow-up in `docs/validation/milestone-e-package-publication-registry-assembly-activation-prep-validation-2026-06-21.md`, package publication real-version-selection prep follow-up in `docs/validation/milestone-e-package-publication-real-version-selection-prep-validation-2026-06-21.md`, and package publication tag-creation prep follow-up in `docs/validation/milestone-e-package-publication-tag-creation-prep-validation-2026-06-21.md` until explicit blockers are resolved. The public beta approval prep lane approves only source-only public beta evaluation for the GitHub source repository. The package publication approval prep lane approves only internal Rust crate publication preparation for the five ADR-0006 reserved priority crates.io identifiers; it does not approve package publication. The package publication evidence records document current prep blockers and do not approve package publication. The metadata-readiness follow-up records README, NOTICE, manifest metadata, and include-list readiness for `ethos-core`, `ethos-verify`, and `ethos-pdf`; it does not approve package publication. The current dry-run/smoke follow-up records local package assembly for `ethos-doc-core` and source-tree checks for `ethos-verify` and `ethos-pdf`; public installation and package publication remain blocked. The version/tag policy follow-up records separation between source-tree version, reserved placeholder version, source snapshot tag, and future package tag namespace; real package version selection, package tag creation, public installation, and package publication remain blocked. The real-version-selection prep follow-up records a future SemVer candidate review boundary while selecting no package publication version; real package version selection approval, package tag creation, public installation, and package publication remain blocked. The tag-creation prep follow-up records a future package tag creation review boundary while creating no package tag; package tag creation, public installation, and package publication remain blocked. The PDFium boundary follow-up records the current source-tree `ethos-pdf` boundary; project-maintained PDFium builds, public installation, and package publication remain blocked. The dependency-ordering follow-up records the future dependent-candidate ordering constraint; registry-backed dependent package assembly, package dependency manifest migration, public installation, and package publication remain blocked. The manifest-migration prep follow-up records future manifest shape while current Cargo manifests remain unchanged; registry-backed dependent package assembly, package dependency manifest activation, public installation, and package publication remain blocked. The manifest-activation prep follow-up records future package dependency manifest activation review while current Cargo manifests remain unchanged; registry-backed dependent package assembly activation, package dependency manifest activation, public installation, and package publication remain blocked. The registry-assembly prep follow-up records future non-public dependent candidate assembly rehearsal while no registry is created and current Cargo manifests remain unchanged; registry-backed dependent package assembly activation, package dependency manifest activation, public installation, and package publication remain blocked. The registry-assembly activation prep follow-up records future registry-backed dependent package assembly activation review while no registry is created and no registry-backed assembly is activated; registry-backed dependent package assembly activation, public installation, and package publication remain blocked. The public-facing readiness ledger in `docs/milestone-e-public-facing-readiness-ledger.json`, schema-bound by `schemas/ethos-milestone-e-public-facing-readiness-ledger.schema.json`, records current main `6019a97` / tree `f56fde854f6f6e4c4070209329f8c7b12310aa51` as the current-main source-only public beta source binding while retaining package-publication resolution gaps with package publication blocked. The Milestone E prep source-only closeout record in `docs/validation/milestone-e-final-closeout-validation-2026-06-20.md` closes only that current internal prep boundary. The E prep JSON files are schema-bound, but that does not promote any fixture beyond internal source-only planning, does not approve package publication, hosted surfaces, production positioning, public benchmark reports, or public benchmark claims, and does not resolve or soften blockers outside the source-only public beta approval and package prep approval boundaries. The product can demonstrate a narrow parser-backed grounding loop today, but the decision cannot be used as public benchmark credibility. The public beta current-main refresh prep in `docs/milestone-e-public-beta-current-main-refresh-prep.json`, schema-bound by `schemas/ethos-milestone-e-public-beta-current-main-refresh-prep.schema.json`, records current main `9262b28` / tree `9f18f9e40c57551aef9b0cb2a53641c87207546b` as a current-main refresh candidate only. This public beta current-main refresh prep does not refresh the reviewed source-only public beta source state, change the approved public beta wording, approve package publication, approve public installation, or soften any current public-facing blocker. @@ -260,7 +274,7 @@ The patch `0.1.1` readiness prep record in `docs/validation/patch-0-1-1-readines | Real PDF backend | Landed for simple born-digital PDFs: page count, quantized spans, worker execution, timeout, page filtering, and fingerprint path exist | Wider corpus coverage, failure fixtures, memory-limit behavior, quirk log, and Gate Zero run are still missing | | Layout groundwork | Landed: basic paragraph text blocks, fixture-backed alpha heading and flat list-item elements, simple column reading order over quantized spans, explicit alpha heading-confidence values, deterministic below-threshold confidence diagnostics, fixture metadata checks against committed extraction/layout goldens for current read-order and element-type expectations, and alpha text/Markdown export goldens derived from committed layout output | Tables, nested/richer list and heading semantics, broader rotation/quirk handling, and broader confidence dimensions remain future work | | Layout evaluator scaffold | Landed: deterministic internal evaluator over committed extraction/layout fixture expectations, with heading/list/reading-order/rotation/hyphenation/ligature/font-identity/span-expectation coverage checks, expected page/span-text/font-id checks, expected-spans metadata validation, warning-reference checks, confidence-policy checks, text/Markdown export-golden checks, expectation drift diagnostics, report JSON, Make target, unit coverage, PR CI wiring, and static CI workflow guard coverage | Broader evaluator dimensions remain future work | -| Python surface scaffold | Landed: internal stdlib wrapper over a caller-provided local `ethos doc parse` command, with explicit JSON/Markdown/text methods, page selection passthrough, diagnostics passthrough, timeout handling, command failure reporting, and mocked-command unit coverage | Native binding work, broader API design, and public setup path remain future work | +| Python surface | Landed: `ethos-pdf==0.1.1` public evaluation wheel wrapping a caller-provided local `ethos` CLI command, with explicit JSON/Markdown/text methods, page selection passthrough, diagnostics passthrough, timeout handling, command failure reporting, and mocked-command unit coverage; it does not bundle the CLI or PDFium | Native binding work and broader API design remain future work | | Font policy groundwork | Partially landed: substitution table and profile policy are present; substitution-table bytes are pinned by the deterministic profile and checked by schema/example validation; absent bundled fallback assets must remain represented by a null fallback-bundle hash; fixture output uses deterministic substitution IDs, committed embedded-font fixture metadata now binds expected extraction font identity, document schema/font extraction keep emitted font ids inside the deterministic ASCII `embedded:` / `subst:` contract, and CLI font-isolation PDFs are manifest/hash-bound | Bundled fallback asset introduction/hash pinning and broader font/CID validation remain open | | Schema/example validation | Landed: schemas, examples, deterministic profile, referential integrity, and bbox sanity pass the `jsonschema` validation gate | Contract changes still require explicit versioning and compatibility review | | Trust-layer implementation | Landed: `ethos verify` quote/value/presence/table-cell checks, explicit quote-containment labeling, normalized equality for value/table-cell checks, stale and unverifiable fingerprint handling, unsupported claim reporting, structured capability limits, native Ethos JSON path, ODL-style adapter path with synthetic table/cell mapping, explicit real OpenDataLoader-style row/cell table grounding, conservative real-style text/child-container alias normalization, pinned real OpenDataLoader 2.4.7 grounded/ungrounded fixtures, foreign fixture manifest hash validation, crop-ref evidence plumbing, stable logical native crop refs, native crop descriptor artifacts, internal `crop_element` source-bound resolver, raw BGRA crop rendering in `ethos-pdf`, CLI/Python source-bound crop descriptor and rendered artifact plumbing for bound native source PDFs, same-host rendered crop repeatability check, rendered-crop run comparison helper, strict citation/config input validation, citation input schema, split-quote fixture coverage, explicit unsupported non-v1 claim reporting, OpenDataLoader-style structure diagnostics for malformed bbox and unknown-page references, verify-alpha case inventory checks, demo fixtures, and a first Milestone D `verify_citations` v1 contract note that binds the current citation-input to verification-report contract without adding a new command or binding surface | Post-D blockers/future work: additional adapter hardening against broader real output shapes, future claim-kind expansion outside the current v1 alpha policy, sandbox/subprocess backend work, Node/MCP/hosted crop surfaces, foreign-adapter crop coordinate hardening, and any cross-platform rendered crop artifact byte-identity requirement; these are not D closeout requirements | @@ -271,4 +285,4 @@ The patch `0.1.1` readiness prep record in `docs/validation/patch-0-1-1-readines ## PM Rule -Public language may use this exact approved sentence on the current source and Rust crate evaluation surfaces: "Ethos is public beta for source and Rust crate evaluation. It verifies whether AI citations are grounded in document evidence across native Ethos JSON and supported foreign parser outputs. Rust library crates `ethos-doc-core`, `ethos-verify`, and `ethos-pdf` are available on crates.io at `0.1.0` for evaluation. Hosted surfaces, production positioning, and public benchmark claims remain blocked." All wording beyond that sentence still requires claim-audit and decider review for the exact surface. Do not describe Ethos as having public benchmark validation, release readiness, production readiness, or broad parser completeness. Wheels, npm packages, binaries, hosted surfaces, project-maintained PDFium builds, `ethos-doc`, and `ethos-rag` remain blocked. Internal parser work should proceed only when it supports accepted evidence paths or the trust layer; the product-differentiating path remains verification and grounding first, with parser expansion serving that path. +Public language may use this exact approved sentence on the current source, Rust crate, Python wheel, npm package, macOS arm64 CLI artifact, and Linux x64 CLI artifact evaluation surfaces: "Ethos is public beta for source, Rust crate, Python wheel, macOS arm64 CLI artifact, Linux x64 CLI artifact, and npm `@docushell/ethos-pdf` evaluation. It verifies whether AI citations are grounded in document evidence across native Ethos JSON and supported foreign parser outputs. Rust library crates `ethos-doc-core`, `ethos-verify`, and `ethos-pdf` are available on crates.io at `0.1.1` for evaluation. The Python `ethos-pdf` wheel, npm `@docushell/ethos-pdf@0.1.1` package, and macOS arm64/Linux x64 CLI artifacts are available for evaluation with caller-provided PDFium. Hosted surfaces, production positioning, Windows packaged artifacts, bundled project-maintained PDFium builds, `ethos-doc`, `ethos-rag`, public benchmark reports, public benchmark claims, and speed, footprint, parser-quality, table-quality, or production claims remain blocked." All wording beyond that sentence still requires claim-audit and decider review for the exact surface. Do not describe Ethos as having public benchmark validation, production readiness, broad parser completeness, speed, footprint, parser-quality, or table-quality claims. Hosted surfaces, Windows packaged artifacts, bundled project-maintained PDFium builds, `ethos-doc`, and `ethos-rag` remain blocked. Internal parser work should proceed only when it supports accepted evidence paths or the trust layer; the product-differentiating path remains verification and grounding first, with parser expansion serving that path. diff --git a/docs/validation/README.md b/docs/validation/README.md index ffe044e..ed8bd4e 100644 --- a/docs/validation/README.md +++ b/docs/validation/README.md @@ -10,10 +10,9 @@ in `docs/public-release-checklist.md`. Records: -Current package publication evidence records keep publication blocked while tracking reserved-name -inventory, metadata/readiness, dry-run planning, version/tag policy, and PDFium boundary blockers. -The public-facing readiness ledger keeps the current-main refresh candidate and package publication -resolution gaps explicit without approving package publication or public installation. +Patch `0.1.1` closeout records now document the approved public beta/evaluation surfaces for source, +Rust crates, the Python wheel, npm package, and macOS arm64/Linux x64 CLI artifacts. Historical +package-publication records below keep their at-the-time blocker wording for traceability. The public beta current-main refresh prep record keeps refreshed source approval blocked while recording the exact current-main source candidate and required follow-up evidence. @@ -644,6 +643,10 @@ recording the exact current-main source candidate and required follow-up evidenc public installation wording closeout validation documents published evaluation install paths for Rust crates, the Python wheel, npm package, and GitHub Release CLI artifacts while retaining hosted, production, Windows, bundled PDFium, benchmark, `ethos-doc`, and `ethos-rag` blockers. +- `patch-0-1-1-execution-status-refresh-validation-2026-06-24.md` - patch 0.1.1 execution + status refresh validation updates the current execution-status summary and PM rule for published + evaluation surfaces while retaining hosted, production, Windows, bundled PDFium, benchmark, + `ethos-doc`, and `ethos-rag` blockers. - `milestone-e-validation-command-index-validation-2026-06-20.md` - internal Milestone E validation-command index validation passed through command-alignment checks, schema enum checks, row-record checks, public-surface posture checks, `make milestone-e-prep`, and diff hygiene; the diff --git a/docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md b/docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md new file mode 100644 index 0000000..eb5dcad --- /dev/null +++ b/docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md @@ -0,0 +1,80 @@ +# Patch 0.1.1 Execution Status Refresh Validation - 2026-06-24 + +Validated source HEAD before this record: `ae99d8d`. + +Patch 0.1.1 execution status refresh source commit: +`ae99d8d32c3d80f4756b36f75263eb15992516ba`. + +Patch 0.1.1 execution status refresh source tree: +`c4b147b3092e430560d489ad0f87d1d8e7b50861`. + +Status: **patch 0.1.1 execution status refreshed for published evaluation surfaces** + +This record refreshes `docs/execution-status.md` after the patch `0.1.1` CLI artifact, +Rust crates.io, npm, Python PyPI, and public installation wording closeout records were merged. +It aligns the current execution-status summary and PM rule with the already-published evaluation +surfaces only. + +## Current Approved Evaluation Surfaces + +- GitHub source repository. +- Rust library crates `ethos-doc-core`, `ethos-verify`, and `ethos-pdf` at `0.1.1`. +- Python `ethos-pdf` wheel at `0.1.1`. +- npm `@docushell/ethos-pdf@0.1.1` CLI package. +- GitHub Release `v0.1.1` macOS arm64 CLI artifact. +- GitHub Release `v0.1.1` Linux x64 CLI artifact. + +## Files In Scope + +- `docs/execution-status.md` +- `.github/scripts/test_execution_status.py` +- `docs/validation/README.md` +- `CHANGELOG.md` + +## Non-Approvals + +- This record does not approve hosted surfaces. +- This record does not approve production positioning. +- This record does not approve Windows packaged artifacts. +- This record does not approve bundled project-maintained PDFium builds. +- This record does not approve public benchmark reports. +- This record does not approve public benchmark claims. +- This record does not approve speed claims. +- This record does not approve footprint claims. +- This record does not approve parser-quality claims. +- This record does not approve table-quality claims. +- This record does not approve `ethos-doc`. +- This record does not approve `ethos-rag`. + +## Retained Boundaries + +- Hosted surfaces remain blocked. +- Production positioning remains blocked. +- Public benchmark reports remain blocked. +- Public benchmark claims remain blocked. +- Windows packaged artifacts remain blocked. +- Bundled project-maintained PDFium builds remain blocked. +- `ethos-doc` remains blocked. +- `ethos-rag` remains blocked. +- PDFium remains caller-provided through `ETHOS_PDFIUM_LIBRARY_PATH`. +- The Python wheel remains a wrapper around a caller-provided local `ethos` CLI binary. + +## Commands + +```sh +python3 .github/scripts/test_execution_status.py +python3 .github/scripts/public_boundary_claims_gate.py +python3 .github/scripts/claims_gate.py +python3 .github/scripts/test_public_surface_posture.py +python3 .github/scripts/test_milestone_e_source_snapshot_candidate_audit.py +make light-check PYTHON=python3 +make release-candidate-prep PYTHON=python3 +git diff --check +``` + +## Result + +```text +patch 0.1.1 execution status refreshed +published evaluation surfaces are reflected without changing retained support boundaries +``` From 59eaf0381b0dc2665f4f3b3193763325a93f587e Mon Sep 17 00:00:00 2001 From: docushell-admin Date: Wed, 24 Jun 2026 12:24:06 +0530 Subject: [PATCH 2/3] Fix public wording approval guard Signed-off-by: docushell-admin --- docs/execution-status.md | 2 +- ...atch-0-1-1-execution-status-refresh-validation-2026-06-24.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/execution-status.md b/docs/execution-status.md index 310ee91..ba4214d 100644 --- a/docs/execution-status.md +++ b/docs/execution-status.md @@ -111,7 +111,7 @@ publication remain blocked. ## Current Reality -The repository is in public beta/evaluation for the approved source, package, and CLI artifact surfaces, but it is not production-ready. Real parsing and real alpha verification exist. They are narrow, fixture-backed, and now have an accepted internal Gate Zero decision for roadmap control. That decision is not a public benchmark report, release approval, package approval, production approval, or claim approval. +The repository is in public beta/evaluation for the approved source, package, and CLI artifact surfaces, and production positioning remains blocked. Real parsing and real alpha verification exist. They are narrow, fixture-backed, and now have an accepted internal Gate Zero decision for roadmap control. That decision is not a public benchmark report, release approval, package approval, production approval, or claim approval. The committed implementation now includes: diff --git a/docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md b/docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md index eb5dcad..048e1c8 100644 --- a/docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md +++ b/docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md @@ -63,6 +63,7 @@ surfaces only. ```sh python3 .github/scripts/test_execution_status.py +python3 .github/scripts/test_public_prealpha_wording_approval.py python3 .github/scripts/public_boundary_claims_gate.py python3 .github/scripts/claims_gate.py python3 .github/scripts/test_public_surface_posture.py From 724657ba17e7d983e6a48ebdbd9beea9edb9d354 Mon Sep 17 00:00:00 2001 From: docushell-admin Date: Wed, 24 Jun 2026 12:55:35 +0530 Subject: [PATCH 3/3] Align Milestone E status guards with patch 0.1.1 Signed-off-by: docushell-admin --- .github/scripts/test_milestone_e_prep_scope.py | 8 +++++--- ...lestone_e_public_evaluation_current_state_closeout.py | 4 ++-- docs/roadmap.md | 9 +++++---- docs/validation/README.md | 2 +- ...1-1-execution-status-refresh-validation-2026-06-24.md | 1 + 5 files changed, 14 insertions(+), 10 deletions(-) diff --git a/.github/scripts/test_milestone_e_prep_scope.py b/.github/scripts/test_milestone_e_prep_scope.py index e5b789d..08cf9b1 100644 --- a/.github/scripts/test_milestone_e_prep_scope.py +++ b/.github/scripts/test_milestone_e_prep_scope.py @@ -312,12 +312,14 @@ def test_status_and_roadmap_reference_prep_scope(self) -> None: ) self.assertIn("schema-validated by `schemas/validate_examples.py`", status) self.assertIn( - "later public-report, project-maintained PDFium build, stable CLI/Python docs, and " - "hosted demo work remain blocked on explicit claim-audit and release-scope decisions", + "hosted surfaces, production positioning, Windows packaged artifacts, bundled " + "project-maintained PDFium builds, `ethos-doc`, `ethos-rag`, public benchmark reports, " + "public benchmark claims, and speed/footprint/parser-quality/table-quality/production " + "claims remain blocked on explicit claim-audit and release-scope decisions", roadmap, ) self.assertIn("Still absent or not claimable:", status) - self.assertIn("exact approved source-only public beta wording", status) + self.assertIn("exact approved patch `0.1.1` public beta/evaluation wording", status) self.assertIn("Broader public result language remains blocked", status) self.assertIn( "intentionally excludes public-report, release, package, hosted, and broad " diff --git a/.github/scripts/test_milestone_e_public_evaluation_current_state_closeout.py b/.github/scripts/test_milestone_e_public_evaluation_current_state_closeout.py index 2d60655..a6f77ca 100644 --- a/.github/scripts/test_milestone_e_public_evaluation_current_state_closeout.py +++ b/.github/scripts/test_milestone_e_public_evaluation_current_state_closeout.py @@ -137,14 +137,14 @@ def test_record_captures_approved_surface_and_exact_wording(self) -> None: for blocker in RETAINED_BLOCKERS: self.assertIn(blocker, record) - def test_readme_and_status_docs_match_exact_public_wording(self) -> None: + def test_current_docs_use_current_public_wording(self) -> None: readme_text = re.sub( r"\s+", " ", " ".join(line.removeprefix("> ").strip() for line in read(README).splitlines()), ) self.assertIn(CURRENT_README_WORDING, readme_text, str(README)) - self.assertIn(EXACT_PUBLIC_WORDING, normalized(EXECUTION_STATUS), str(EXECUTION_STATUS)) + self.assertIn(CURRENT_README_WORDING, normalized(EXECUTION_STATUS), str(EXECUTION_STATUS)) def test_docs_reference_current_state_and_retained_blockers(self) -> None: for path in (PREP_SCOPE, ROADMAP, EXECUTION_STATUS, VALIDATION_README): diff --git a/docs/roadmap.md b/docs/roadmap.md index f1306ed..78a0a30 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -218,9 +218,10 @@ source repository plus `ethos-doc-core`, `ethos-verify`, and `ethos-pdf` at `0.1 evaluation while retaining hosted surfaces, production positioning, public benchmark claims, CLI distribution, wheels, npm packages, binaries, project-maintained PDFium builds, `ethos-doc`, `ethos-rag`, and broader public wording as blocked. -Current public evaluation wording is therefore limited to the GitHub source repository plus those -three Rust library crates at `0.1.0`; earlier package-publication blocker statements remain -historical record summaries for the steps that preceded the availability record. +Patch `0.1.1` closeout records now supersede those historical blockers only for the approved +source, Rust crate, Python wheel, npm package, macOS arm64 CLI artifact, and Linux x64 CLI artifact +evaluation surfaces; earlier package-publication blocker statements remain historical record +summaries for the steps that preceded the patch closeouts. The registry-assembly prep follow-up records future non-public dependent candidate assembly rehearsal while no registry is created and current Cargo manifests remain unchanged; registry-backed dependent package assembly activation, package dependency manifest activation, @@ -345,7 +346,7 @@ public-facing claims. | B | weeks 9-14 | **`ethos verify` alpha first**: native Ethos JSON + synthetic and pinned real OpenDataLoader verification demos, stale fingerprint checks, capability-limited reports, deterministic evidence matching including split-quote coverage, explicit unsupported non-v1 claim reporting, adapter structure diagnostics; then reading order, blocks, headings, lists, Markdown/text exporters, Python wheel scaffold, quality dashboard, Windows x64 nightly determinism | [13-B exit checklist](milestone-b-exit-checklist.md) | | C | weeks 15-22 | Simple/bordered tables; RAG chunker + citations; non-text region coordinates; security report + default-chunk exclusion; debug overlay; internal benchmark snapshot | Current artifact-validation checkpoint recorded in [Milestone C closeout validation](validation/milestone-c-closeout-validation-2026-06-18.md); broader debug/crop/table follow-ups remain explicit | | D | weeks 23-30 | [`verify_citations` v1 contract prep](milestone-d-verify-citations-contract.md); [`claim_kind_boundary` v1 contract prep](milestone-d-claim-kind-boundary-contract.md); [`grounding_source` v1 contract prep](milestone-d-grounding-source-contract.md); [`capability_downgrade` v1 contract prep](milestone-d-capability-downgrade-contract.md); [`opendataloader_adapter_shape` v1 contract prep](milestone-d-opendataloader-adapter-shape-contract.md); [`crop_element` v1 contract prep](milestone-d-crop-element-contract.md) plus internal resolver and source-bound CLI/Python descriptor/rendered carriers; [`crop_element_surface_shape` v1 contract prep](milestone-d-crop-element-surface-shape-contract.md); [`sandbox_subprocess` v1 contract prep](milestone-d-sandbox-subprocess-contract.md); [contract closeout validation](validation/milestone-d-contract-closeout-validation-2026-06-19.md); [final closeout validation](validation/milestone-d-final-closeout-validation-2026-06-19.md); Node/MCP/hosted crop surfaces, sandbox-backed crop behavior, foreign-adapter crop coordinates, and cross-platform rendered-crop byte identity are explicit post-D blockers, not D closeout requirements | 13-D exit complete for source-only pre-alpha scope | -| E | weeks 31-40 | Initial source-only prep scope in [`docs/milestone-e-prep-scope.md`](milestone-e-prep-scope.md), with current internal prep closeout recorded in [`docs/validation/milestone-e-final-closeout-validation-2026-06-20.md`](validation/milestone-e-final-closeout-validation-2026-06-20.md); source-only public beta evaluation is tracked in [`docs/milestone-e-public-beta-approval-prep.json`](milestone-e-public-beta-approval-prep.json) with exact wording and exclusions; current-main source-only public beta approval is recorded in [`docs/validation/milestone-e-public-beta-current-main-source-only-approval-validation-2026-06-21.md`](validation/milestone-e-public-beta-current-main-source-only-approval-validation-2026-06-21.md); public evaluation current-state closeout is recorded in [`docs/validation/milestone-e-public-evaluation-current-state-closeout-validation-2026-06-22.md`](validation/milestone-e-public-evaluation-current-state-closeout-validation-2026-06-22.md) for GitHub source repository plus the three Rust library crates at `0.1.0`; package publication approval prep is tracked in [`docs/milestone-e-package-publication-approval-prep.json`](milestone-e-package-publication-approval-prep.json) as internal Rust crate publication prep only, with evidence, metadata-readiness, dry-run/smoke, version/tag policy, PDFium boundary, dependency-ordering, and approval resolution-plan records under `docs/validation/`; current-main public-facing readiness is tracked in [`docs/milestone-e-public-facing-readiness-ledger.json`](milestone-e-public-facing-readiness-ledger.json) without approving package publication; current-main source-only public beta refresh prep is tracked in [`docs/milestone-e-public-beta-current-main-refresh-prep.json`](milestone-e-public-beta-current-main-refresh-prep.json) without changing approved wording or approving package publication; actual package publication outside the three approved Rust library crates, later public-report, project-maintained PDFium build, stable CLI/Python docs, and hosted demo work remain blocked on explicit claim-audit and release-scope decisions | Release 1 claim audit + source-only public-beta checkpoint | +| E | weeks 31-40 | Initial source-only prep scope in [`docs/milestone-e-prep-scope.md`](milestone-e-prep-scope.md), with current internal prep closeout recorded in [`docs/validation/milestone-e-final-closeout-validation-2026-06-20.md`](validation/milestone-e-final-closeout-validation-2026-06-20.md); historical source-only public beta approval, current-main source-only approval, and public evaluation current-state closeout records remain indexed for traceability; patch `0.1.1` closeout records now cover the approved public beta/evaluation surfaces for source, Rust crates, Python wheel, npm package, macOS arm64 CLI artifact, and Linux x64 CLI artifact; package publication evidence, metadata-readiness, dry-run/smoke, version/tag policy, PDFium boundary, dependency-ordering, approval, publication, and public-install wording records remain indexed under `docs/validation/`; hosted surfaces, production positioning, Windows packaged artifacts, bundled project-maintained PDFium builds, `ethos-doc`, `ethos-rag`, public benchmark reports, public benchmark claims, and speed/footprint/parser-quality/table-quality/production claims remain blocked on explicit claim-audit and release-scope decisions | Patch `0.1.1` public beta/evaluation closeout plus retained blocker tracking | | F / Release 2 | post-E | Complex tables, formula/LaTeX, chart classification, optional enrichment modules (never base) | Scoped after E from beta fixtures | Fallback charter: ADR-0005 selected `PROCEED`. If a future Gate Zero successor decision rejects diff --git a/docs/validation/README.md b/docs/validation/README.md index ed8bd4e..ff87626 100644 --- a/docs/validation/README.md +++ b/docs/validation/README.md @@ -12,7 +12,7 @@ Records: Patch `0.1.1` closeout records now document the approved public beta/evaluation surfaces for source, Rust crates, the Python wheel, npm package, and macOS arm64/Linux x64 CLI artifacts. Historical -package-publication records below keep their at-the-time blocker wording for traceability. +package publication evidence records below keep their at-the-time blocker wording for traceability. The public beta current-main refresh prep record keeps refreshed source approval blocked while recording the exact current-main source candidate and required follow-up evidence. diff --git a/docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md b/docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md index 048e1c8..3b2cbe0 100644 --- a/docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md +++ b/docs/validation/patch-0-1-1-execution-status-refresh-validation-2026-06-24.md @@ -64,6 +64,7 @@ surfaces only. ```sh python3 .github/scripts/test_execution_status.py python3 .github/scripts/test_public_prealpha_wording_approval.py +python3 .github/scripts/test_milestone_e_prep_scope.py python3 .github/scripts/public_boundary_claims_gate.py python3 .github/scripts/claims_gate.py python3 .github/scripts/test_public_surface_posture.py