Where blocky-writer is
Rust/WASM core (rust/pdftool_core) is implemented and green — cargo fmt -- --check, cargo test --locked (6/6) and cargo clippy --all-targets -- -D warnings all pass on main at e1b6225 (run 36296845297). Two exported
functions, detect_blocks and fill_blocks, over an AcroForm field walker with
a 20-code BW_* error taxonomy.
The AffineScript frontend is a prototype with no build pipeline in this
checkout, so nothing is release-ready. Fixed-layout placement of the
"hand-spacing" kind — ruled lines, per-character cells, baselines — is not
implemented; detect_blocks reports widget annotation rectangles only.
What you can progress with
#71 acceptance criterion 1 is met on our side. blocky-writer's README now
carries an Ecosystem position section stating its boundary and linking the
other optional components, with the long form in
docs/ecosystem/ECOSYSTEM.adoc:
It owns exactly one thing: fitting and placement into fixed-layout PDF and
application-form boxes, baselines and per-character cells designed for hand
spacing rather than reliable computer entry.
The boundary wording is lifted from your README's suite table, so it should
already agree with #71 — but please confirm, and say if you want it phrased
differently.
Criterion 2 (the versioned interchange contract) is untouched and is yours to
define. blocky-writer has no interchange format to offer yet.
What you might use from here
If the suite ever wants a composed operation carrying page coordinates, the
natural surface is our field-name → value map alongside the widget rectangles
detect_blocks returns. Nothing is committed; this is an offer, not a plan.
What we would need from you
Nothing blocking. One question: #71 says "Each repository README and GitHub
description". The GitHub description is a repository setting rather than a
file, so it is an owner-side edit. Worth deciding whether you want the boundary
in the description too, or whether the README link satisfies it.
What we deliberately do not do
No code-level dependency exists in either direction, and per #71's "proof
obligations do not transfer" we are not treating our green cargo test as
evidence about your conversion correctness, or vice versa.
Ref: hyperpolymath/blocky-writer#73
Where blocky-writer is
Rust/WASM core (
rust/pdftool_core) is implemented and green —cargo fmt -- --check,cargo test --locked(6/6) andcargo clippy --all-targets -- -D warningsall pass onmainate1b6225(run 36296845297). Two exportedfunctions,
detect_blocksandfill_blocks, over an AcroForm field walker witha 20-code
BW_*error taxonomy.The AffineScript frontend is a prototype with no build pipeline in this
checkout, so nothing is release-ready. Fixed-layout placement of the
"hand-spacing" kind — ruled lines, per-character cells, baselines — is not
implemented;
detect_blocksreports widget annotation rectangles only.What you can progress with
#71 acceptance criterion 1 is met on our side. blocky-writer's README now
carries an Ecosystem position section stating its boundary and linking the
other optional components, with the long form in
docs/ecosystem/ECOSYSTEM.adoc:The boundary wording is lifted from your README's suite table, so it should
already agree with #71 — but please confirm, and say if you want it phrased
differently.
Criterion 2 (the versioned interchange contract) is untouched and is yours to
define. blocky-writer has no interchange format to offer yet.
What you might use from here
If the suite ever wants a composed operation carrying page coordinates, the
natural surface is our field-name → value map alongside the widget rectangles
detect_blocksreturns. Nothing is committed; this is an offer, not a plan.What we would need from you
Nothing blocking. One question: #71 says "Each repository README and GitHub
description". The GitHub description is a repository setting rather than a
file, so it is an owner-side edit. Worth deciding whether you want the boundary
in the description too, or whether the README link satisfies it.
What we deliberately do not do
No code-level dependency exists in either direction, and per #71's "proof
obligations do not transfer" we are not treating our green
cargo testasevidence about your conversion correctness, or vice versa.
Ref: hyperpolymath/blocky-writer#73