Skip to main content

Assembly Line Weaver: Suffolk LIT Lab Document Assembly Line

PyPI version

drawing of two cartoon people collaborating on building a web application

The Assembly Line Project is a collection of volunteers, students, and institutions who joined together during the COVID-19 pandemic to help increase access to the court system. Our vision is mobile-friendly, easy to use guided online forms that help empower litigants to access the court remotely.

Our signature project is CourtFormsOnline.org.

We designed a step-by-step, assembly line style process for automating court forms on top of Docassemble and built several tools along the way that you can use in your home jurisdiction.

This package contains an automation and rapid prototyping tool to support authoring robust, consistent, and attractive Docassemble interviews that help complete court forms. Upload a labeled PDF or DOCX file, and the Assembly Line Weaver will produce a runnable, clean code, draft of a Docassemble interview that you can continue to edit and refine.

Read more on our documentation page.

Documentation

https://suffolklitlab.org/docassemble-AssemblyLine-documentation/

ALWeaver API

When installed on a docassemble server, ALWeaver exposes a custom Flask API:

  • POST /al/api/v1/weaver (primary)
  • GET /al/api/v1/weaver/jobs/{job_id} (async job polling)
  • DELETE /al/api/v1/weaver/jobs/{job_id} (async job cleanup)
  • GET /al/api/v1/weaver/openapi.json (OpenAPI spec)
  • GET /al/api/v1/weaver/docs (human-readable docs)

The API uses docassemble's API key authentication via api_verify(). The POST endpoint defaults to synchronous behavior, and supports optional asynchronous execution with mode=async (or async=true).

Celery worker configuration

Uploaded-document project generation in the graphical editor, importing a template already in a project, publishing a project to GitHub, and asynchronous API requests require ALWeaver's task module to be registered with Docassemble's global Celery configuration. Add the module to the existing celery modules list in the Docassemble configuration; preserve any modules already listed:

celery modules:
  - docassemble.ALWeaver.api_weaver_worker

After changing the configuration, restart or redeploy both the Docassemble web service and every Celery worker so that they load the same task registry. Blank project creation, ordinary graphical/source editing, and synchronous API calls do not require this module.

ALWeaver checks this setting when its editor module starts and whenever the editor page loads. If it is missing, the server logs a warning and the editor shows a persistent setup notice before a developer selects a file to generate. An attempted background request fails with HTTP 503, a structured async_not_configured API error (or editor_async_not_configured from the graphical editor), and a link back to these instructions. Weaver does not enqueue an unregistered task or fall back to an in-process thread.

The revisioned graphical source-patch API is an opt-in beta. Set WEAVER_ENABLE_PATCH_MODEL: true in the Docassemble configuration (or the same environment variable) to enable it. The default production path remains off until graphical editing paths have migrated to exact source-range commands.

The editor's interview debugger is enabled by default for authenticated developers and administrators. It runs the real interview in a separate test session beside current-question details, a step recorder, variable inspection, scenario seeding, and back navigation. Set weaver: {runtime inspector: false} (or WEAVER_ENABLE_RUNTIME_INSPECTOR: false) to turn it off. Its server API uses owner-scoped target sessions and a fixed read-only al_weaver.inspect_* action allowlist; Docassemble remains the only interview runtime.

History

See the CHANGELOG for more information.

Authors

Quinten Steenhuis, qsteenhuis@suffolk.edu
Michelle
Bryce Willey, bwilley@suffolk.edu Lily
David Colarusso
Nharika Singh

Installation requirements

Using auto drafting mode

To use auto-drafting mode, you can get an Open AI API Key and set it in your docassemble configuration.

open ai:
  key: ...

Metadata

Release files for docassemble.ALWeaver 2.3.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for docassemble.ALWeaver 2.3.1
File Size Uploaded
docassemble_alweaver-2.3.1.tar.gz 1.4 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for docassemble.ALWeaver 2.3.1
File Interpreter ABI Platform
docassemble_alweaver-2.3.1-py3-none-any.whl Python 3 none any Details

Total release size: 2.8 MB

Release files / docassemble_alweaver-2.3.1.tar.gz

Download URL docassemble_alweaver-2.3.1.tar.gz
Size 1.4 MB
Tags Source
SHA-256 checksum
How to use checksums
45edb83ba2e5c8b5269ea7d29bbe5b28750b256858912f46e8aeac3acb9f8612
BLAKE2b-256 checksum
How to use checksums
5dce885ae6a6793b71798147c3811055da7e0ad818113340d72dd909c4cfdce2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.

Transparency log

Release files / docassemble_alweaver-2.3.1-py3-none-any.whl

Download URL docassemble_alweaver-2.3.1-py3-none-any.whl
Size 1.5 MB
Tags Python 3
SHA-256 checksum
How to use checksums
d37907f3b1b4d28034a3146d53675a016673df5d90cd959133ff4d2a4bbe9126
BLAKE2b-256 checksum
How to use checksums
ce0bd4b40b9cc0384a58ae900cfab4f79fd65327d4cec4afe935eeb417cbc2b5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

2.3.1 This release

2 release files

2.3.0

2 release files

2.2.0

2 release files

2.1.0

2 release files

2.0.0

2 release files

1.10.3

2 release files

1.10.2

2 release files

1.10.0

2 release files

1.9.0

2 release files

1.8.0

2 release files

1.7.0

1 release file

1.6.3

1 release file

1.6.1

1 release file

1.6.0

1 release file

1.5.1

1 release file

1.5.0

1 release file

1.4.6

1 release file

1.4.5

1 release file

1.4.4

1 release file

1.3.1

1 release file

1.3.0

1 release file

1.2.3

1 release file

1.2.2

1 release file

1.2.1

1 release file

1.0.3

1 release file

1.0.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page