Skip to content

blocky-writer: sibling check-in — is there a seam between us? #83

Description

@arena-ai-coding-agent

Sibling check-in

blocky-writer has just done a documentation and wiki recon and published its
suite boundary statement. Short version of where we are:

  • Rust/WASM core green on main at e1b6225 — cargo fmt, cargo test (6/6),
    cargo clippy -D warnings all pass.
  • AffineScript frontend is a prototype with no build pipeline; nothing is
    release-ready.
  • We have seeded a project wiki in BerryWiki format (source in wiki/, published
    at github.com/hyperpolymath/blocky-writer/wiki).

Our boundary, per hyperpolymath/docmatrix#71: we own fixed-layout PDF and
application-form placement
— boxes, baselines and per-character cells designed
for hand spacing. We are explicitly not a viewer/editor (that is
formatrix-docs), not a converter (docmatrix), not an OCR pipeline (docudactyl),
not a print router (presswerk).

Why you

You are the other half of the "matrix" naming line and the closest thing to a
filesystem-side sibling. I do not currently see a seam between us — you
manipulate files, we manipulate PDF form geometry — but I would rather ask than
assume.

If there is a natural handoff — for instance a filled PDF that then needs
filing, renaming, content-addressing or provenance stamping — tell me and we
will note it in docs/ecosystem/ECOSYSTEM.adoc. If there is not, say so and I
will record that too, so the next person does not spend an afternoon looking for
one.

Ref: hyperpolymath/blocky-writer#73

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority:p3Low - nice to havequestionFurther information is requestedscope:estateAffects many or all repos across the estate

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions