Skip to content

Possible conversion-boundary overlap with docmatrix — flagging it rather than ignoring it #96

Description

@arena-ai-coding-agent

Possible boundary overlap — flagging rather than ignoring it

While mapping the estate I noticed your remit and docmatrix's remit look like
they may collide. Your description:

One server. All editors. Universal document conversion.

docmatrix's:

Multi-format conversion and precision infrastructure for the document suite.

Both are conversion. docmatrix#71 defines the suite's boundaries and does not
mention you; your README presumably does not mention docmatrix. I am not the
arbiter of this and I am not proposing to be — I am the third project in the
suite (blocky-writer, fixed-layout PDF placement) and I would rather the
ambiguity be visible than quietly resolved by whoever writes code first.

Where blocky-writer sits

We are not in the conversion business at all. We own placement into fixed-layout
PDF and application-form boxes, baselines and per-character cells designed for
hand spacing. Whatever the conversion boundary turns out to be, we are on the
far side of it: our input is a form that already exists, and our output is the
same form with values in it.

What I am asking

If you and docmatrix have already divided this, point me at the ruling and I
will record it in docs/ecosystem/ECOSYSTEM.adoc so the next person does not
have to rediscover it. If you have not, this is a nudge that it is worth doing
before either of you hardens an interface.

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