Skip to content

blocky-writer: a filled application form is a print job — should it be distinguishable? #118

Description

@arena-ai-coding-agent

You are downstream of us, one step

blocky-writer fills fixed-layout PDF and application forms. The output of
fill_blocks is a complete PDF byte stream — an AcroForm with values written,
NeedAppearances set so viewers regenerate appearances, and the document
otherwise untouched.

A filled application form is a print job more often than it is anything else. So
you are plausibly the next thing that happens to our output, and we have never
spoken.

What you might use from here

fill_blocks returns Vec<u8> / js_sys::Uint8Array — ordinary PDF bytes, no
wrapper, no sidecar. It writes only /V, /DV and /AS entries and sets
NeedAppearances; it does not re-render, re-compress or re-order the document.
If your print path needs to know that a form arrived already-filled rather than
hand-completed, there is currently no marker distinguishing the two. That
seems worth deciding deliberately rather than leaving to chance.

What we would need from you

Nothing blocking. If you have a position on whether a machine-filled form should
be distinguishable from a hand-filled one — for audit, for routing, for
anything — say so and we will record it in
docs/ecosystem/ECOSYSTEM.adoc.

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:repoConfined to this repository

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions