01
Bring the real input.
Start with the real material already on your desk: a meeting transcript, school notice, food record, customer reply, DMS export, supplier message, or council RFI.
One actual job beats a platform tour.
How assembl works
From messy input to reviewed output.
assembl takes a real task, grounds it in the right source material, drafts the work, asks a named person to review it, and keeps the record behind the answer.
The practical loop
The operating model.
02
Ground the draft.
assembl uses the relevant source layer: uploaded material, live knowledge, PCO legislation, or connected tools where the workflow has permission.
The answer should show what it used.
03
Review before action.
The draft names what it used, what it assumed, what is missing, and what should be checked by a person. It does not quietly send, lodge, book, or commit on your behalf.
Citations, assumptions, risks, and missing documents stay visible.
04
Make it repeatable.
If the tool helps, the next step is a private version with your voice, your source material, scoped permissions, and the review points your team needs.
One useful experiment becomes a repeatable internal tool.
05
Keep the record.
The final output carries the work behind the work: sources, checks, reviewer notes, timestamps, and a tamper-evident audit trail.
File it, forward it, footnote it, or hand it to a reviewer.
Three ways in
Tools, pilots, then the operating layer.
HAPAI means lift or support: it is the shareable public tool library. Kete means basket or kit: each kete pack is a specialist operating area. Workflows are the repeatable jobs that become internal systems once they prove useful.
HAPAI tools
HAPAI comes from hāpai: to lift or support. These are small public tools for one task: study planning, meeting notes, travel planning, share cards, food logs, and more.
Pilot Sprint
One workflow rebuilt against your own material. The goal is a working proof in days, not months of requirements theatre.
Kete packs
Kete means basket or kit. A kete pack is a specialist operating area with agents, tools, live knowledge, workflows, and clear review rules.
The promise is simple: nothing ships quietly.
The internal pipeline names are useful to engineers and auditors. Buyers need the plain version: draft, check, review, sign, record.
No external action without human review.
Live knowledge is used where the workflow needs current source material.
Connected tools are scoped to the job, not sprayed across the business.
Every consequential output can end in an evidence pack.
The reviewer, source material, and assumptions are visible.
assembl is the layer above existing systems, not a replacement for them.
Start small
Pick the workflow that keeps coming back.
The best pilot is not a platform tour. It is one recurring job with enough pain, enough source material, and a clear human reviewer.