Stamped paper forms, arched window, dust light

ActiveLoop

A platform an organization installs and builds its own services on, without code. Each service takes a request and issues a record.

StatusWorking
What it isServices and records
Read the essay

An office issues a certificate. The applicant leaves with a page that will be read, checked and kept for years. Everything before it is queueing. That page is the product.

Offices that issue certificates, permits and memberships still do it on paper and in queues. Each one has its own form, its own fee, its own review steps and its own document. Building a separate system for every office by hand does not scale.

So ActiveLoop lets an organization build its own services without code, and every service ends the same way: a record is created and a document is issued. We started from the document and worked backwards.

The document lives inside the workflow

There is no template library. The document is a step in the service’s workflow, and that step holds everything the page needs: the HTML in each language, the paper size, the signer’s name and title, the signature image, and whether the document belongs to the record or to the request.

A service carries everything it needs, and publishing freezes it. A shared template sitting outside the service would not be frozen with it, so a later edit could quietly change what a published service issues. Every service starts empty.

Turned downWhy not
A starter template galleryTemplates would live outside the service and escape the freeze on publish.

A version cannot go live until it passes the publish checks.

Publish checkWhat it refuses
Every path endsA workflow path that never reaches deliver or reject.
Every role existsA review task assigned to a role nobody holds.
Both languagesA form or document missing its English or Somali text.
Known placeholdersA document using a field the service does not collect.
A fee needs paymentA paid service with no payment step.

Frozen at first print

The first time a document renders, its row keeps three snapshots: the HTML as it was, the signer as they were, and the data that filled it, which is the answers, the record and the document number. The PDF itself sits in private storage.

A later edit to the step never changes an issued document. A reprint next year matches the original, because the snapshot can rebuild the PDF without the service version that made it. The test behind this re-renders a document after its step’s HTML has changed and expects the same file.

  1. 09:14renderREG-0142 issued · html, signer and data snapshots stored
  2. 11:02builderService v4 published · certificate wording changed
  3. 11:30renderREG-0143 issued with the v4 wording
  4. 14:45reprintREG-0142 · identical to the first print
Example. The wording changed between two documents. The first one still reprints exactly as issued.

Only the workflow issues

There is no Issue document button anywhere. A document exists because a request reached that step. Rendering runs on its own queue so a slow PDF never holds up a review, and the deliver step gathers every document the request produced. The applicant’s last screen is their download list, not a success message.

  1. Approve

    A reviewer approves. The workflow moves on by itself.

  2. Create the record

    The record is written as data, with the request it came from.

  3. Render

    The document renders on the documents queue and its snapshots are stored. A QR code goes on the page.

  4. Deliver

    Documents are collected and the applicant is notified. Downloads use a signed link that lasts ten minutes, and every download is logged.

There is no preview and no embedded PDF: a document is downloaded or it is not. Revoking one needs its own permission and a reason, and a revoked document downloads as a stamped copy. The QR code costs nothing extra, because the library was already installed for two-factor sign-in. Public checking by number or QR is planned for later.

Our own engine, a copy per request

When an applicant submits, the workflow of the live version is copied onto their request. The engine walks that copy, step by step. Editing the service tomorrow never touches a request filed today.

Published versions must never change. A snapshot is the only honest way.

Every step run writes one row, keyed on the request, the step and the attempt. The same wait released twice is refused by that key, so a retry can never issue twice.

  1. #1reviewsent back · 2 fields flagged
  2. #2reviewapproved
  3. #1recordrecord created
  4. #1documentrendered · snapshots stored
  5. #1deliverdownload list ready
Example steps for one request. A sent-back review runs again as attempt 2.
Turned downWhy not
BPMN and state-machine packagesThey bring their own vocabulary and their own editors.

The first version keeps the engine small: no parallel branches, no automatic revert, no sub-workflows. A step that fails marks the request as needing attention, and an admin retries it.

Send back, fix only what was flagged

A reviewer who sends a request back flags the fields that are wrong and adds a note. The applicant can edit only those fields. Resubmitting runs the same review step again as the next attempt, so the history shows both decisions.

RequestMeans
DraftBeing filled in. Expires after 90 days.
Awaiting paymentA pay-first service. Expires 14 days after the invoice is due.
SubmittedWaiting for its first review.
In reviewWith staff.
Sent backWith the applicant, flagged fields only.
CompletedRecord created, documents issued.
Rejected, withdrawn, expiredClosed, with the reason in its history.

Money and history only grow

Wallet movements and ledger entries are append-only, in whole minor units. At checkout the server rebuilds the invoice lines itself and refuses any line, amount or channel that does not match. The wallet was cut from the first plan and put back the same day.

Each permission has one name, and the menu item, the page, the action and the button all check that same name. The audit log is append-only: the app’s own database role cannot delete from it, it is partitioned by year, and reads of sensitive data are logged as well as changes.

If you build, dream, or make, you belong here.

Find your way in