Use projects on your workstation¶
Studio downloads a runnable project based on
ImmuKnow-Template, with your selected
notice, settings and assets. Use a standalone ImmuKnow executable matching
immuknow-revision.txt. Setup, checks and runs use the executable directly; no
Python, uv or Template checkout is needed.
Download and extract your project¶
In Studio, open Project at the top-right and choose Download project.
Keep Complete project for the runnable ZIP described below. Choose
Authored .typ files only to copy the active notice, settings and referenced
.typ companions into an existing matching repository instead; that smaller ZIP
uses your repository’s existing ImmuKnow components, fonts and assets.
Include fictional client data is selected by default for a local test run.
Clear it to omit Studio’s fictional inputs and sample setup. Custom imported
sample data is preserved. Without a sample, use your own CSV and assignments
as described under Run your own notices.
Extract immuknow-project.zip into a folder you control.
| Item | Purpose |
|---|---|
immuknow-revision.txt |
Reviewed standalone ImmuKnow source revision |
README.md |
Native setup, sample checks and notice instructions |
templates/ |
Your selected notice, Settings, supporting files, images and shared components |
config/ |
Configuration for native ImmuKnow runs |
input/sample/, sample.json |
Selected fictional client and notice, when included |
examples/ |
Explanation of the fictional examples |
templates/fonts/ |
Fonts and licences for manual installation, when included in the download |
template-source.json |
Template package source commit and original scaffold file hashes |
immuknow-project.json |
Studio import format, selected notice, build identity and current file hashes |
Keep the complete directory structure and relative paths. Leave
templates/lib/immuknow/ unchanged. The ZIP includes the selected notice and its dependencies. When combining projects, review
shared Settings and assets before replacing files.
Install and check the project¶
Obtain the standalone immuknow executable matching immuknow-revision.txt from
ImmuKnow releases when a matching
archive is available, or ask your project maintainer. ImmuKnow's
release guide
explains platform choices and checksums. Developers can follow Template's
build instructions. Put it on PATH, or use its full path in place of immuknow in commands.
There is no separate Typst or Python installation.
Install the supplied fonts on your workstation for matching typography. If you
cleared Include fonts for installation when downloading, use the same fonts
already installed on the workstation or download them from Studio separately.
Extracting them does not install them; ImmuKnow uses system fonts.
Open a terminal in the extracted folder:
immuknow project sync
immuknow project check --sample
immuknow run --sample
The first command installs or verifies the complete shared library. The ZIP
includes no executable or Python environment. immuknow project check verifies
the shared library and configuration without sample data. With --sample, the
check also prepares and renders the selected sample in a temporary folder.
The last command keeps a run and prints its report location. Warnings can be
expected; review them in the report. You can also run the executable directly:
immuknow run input/sample/sample_students.csv --project . \
--template overdue_diseases.en.typ
When Include fictional client data is selected, Studio supplies copies of
the selected preview client's CSV in input/sample/ and records it with the
active notice in sample.json. The sample retains the client's facts, so an
incompatible notice can produce findings or a failed notice. An imported
project's existing sample selection and authored sample bytes are preserved,
even when you change the preview client. Without fictional data or a prepared example, a project can
still be downloaded: provide inputs and a sample.json selection before running
--sample. Changing source CSVs does not change Studio's fixed browser facts.
Fresh downloads omit Python scripts, environment files and maintainer tools. Imported projects keep their existing authored files, including legacy helpers. The supplied ignore rules keep conventional client inputs and run outputs out of Git. Maintainers can install additional commit checks from Template's source repository; those checks are separate from project setup and production runs.
You can also use the complete config/ and templates/ trees with an existing
compatible ImmuKnow installation. See ImmuKnow versions.
Run your own notices¶
Review configuration, wording, dates, contacts, branding, signatures and QR
destinations before using your own records. Replace the fictional input with
your own validated cohort and assignments, kept under input/:
# One notice for every client
immuknow run input/clients.csv --project . \
--template overdue_diseases.en.typ
# An explicit notice for each client
immuknow run input/clients.csv --project . \
--notice-assignments input/assignments.json
Use the actual filename of your downloaded notice. Each assignment must name a
notice present in templates/. --project . selects this project's configuration and templates. Results go
to runs/; use --output to choose another output folder.
ImmuKnow's CSV guide
explains the input fields; its configuration guide
covers assignments, duplicate IDs and run settings. Template's
customization guide
explains its starter notices and project settings.
Review the generated notices¶
Review the terminal summary, printed records.csv and findings.csv paths,
and actual PDFs before delivery. A Studio preview checks layout with fictional
examples; native runs use your supplied data. ImmuKnow's
review guide
explains findings, delivery routes, holds and rebundling. Use immuknow refresh-exports RUN_DIR to repair derived CSV exports.
Run files and PDFs contain client information and stay on your workstation under
your organization's handling procedures.
Update the executable¶
Obtain the reviewed executable recorded in immuknow-revision.txt. Refresh the
complete shared library with immuknow project sync --replace, then run
immuknow project check --sample and inspect a retained sample run. Sync changes
only templates/lib/immuknow/; keep your authored notices and configuration.
Output filenames¶
Downloaded projects preserve the filename patterns in config/parameters.yaml.
Configure those patterns in the downloaded project; see ImmuKnow's
filename settings
for supported fields and naming rules. The run-wide CSVs are separate from
batch PDF filenames.