ACME for Heinzelmännchen

ACME is a fictional company you can install, explore and copy for your own team. It is the reference company for Heinzelmännchen, the open-source crew of AI helpers that drafts your team's busywork and asks before anything leaves your machine. Four plugins (heinzel-acme and its three layers) give a made-up team its company, organization, site and team layers, with a weekly-report playbook that drafts locally for you to edit.

uvx heinzel@latest

Explore ACME on the plugin page → · Install the team stack · Port it to your company

The running app in the ACME theme, with fictional data. Accounts are unconnected; the drafts you see are saved locally and sent nowhere. View the full gallery and soundscape →

Ada: "Here is how the pieces connect." Installing the Checkout team brings its Payments organization, Lisbon site and ACME company with it, stacked from general to specific.

• Explore a complete team stack: layers, recommended integrations, roles and calendars.
• Try a weekly-report playbook: templates and contracts that a team can adapt.
• Make it yours: use the porting runbook as a worked example for a private company repository.

Everything here is fiction: ACME (acme.example), its people, its teams and its documents. It follows the core's layer model and plugin playbooks.

Gallery

Real captures with fictional demonstration data and unconnected accounts.

The real company, org, site and team stack, with clearly named offline-demo adapters.

View the full gallery on the plugin page →

The layers

flowchart TB
    acme["<b>acme</b> · company<br/>capability bindings (gh, acli, gws, Gmail, Zoom summaries)<br/>roles tech-lead, report-owner<br/>hz acme seed (rehearsal only)"]
    payments["<b>acme-payments</b> · org<br/>playbook: the okr asset type"]
    lisbon["<b>acme-lisbon</b> · site<br/>the site calendar: time zone, working hours, meeting rhythm"]
    checkout["<b>acme-payments-checkout</b> · team<br/>playbook: the weekly report<br/>(asset types, hints, template contract)"]
    acme --> payments
    acme --> lisbon
    payments --> checkout
    lisbon -. site .-> checkout

Each box is a plugin, named after its path from the root (heinzel-<name>). A layer declares its parent and, for a team, its site; Heinzelmännchen stacks a person's layers general to specific: for Checkout that is acme, then acme-payments and acme-lisbon, then acme-payments-checkout. A more specific layer refines a more general one, and nothing any layer brings becomes your configuration until you accept it (hz setup).

Plugin	Layer	What it brings
heinzel-acme	company	Bindings for code host (GitHub, gh), tracker (Jira, acli), documents, calendar and mail (Google Workspace, gws) and meetings (Zoom's summary e-mails), offered by hz setup acme; roles; a doctor check per binding; hz acme layers; hz acme seed
heinzel-acme-payments	org	A playbook with the okr asset type: the org's quarterly OKR document
heinzel-acme-lisbon	site	The site calendar as data (hz acme-lisbon calendar): Europe/Lisbon, 09:00 to 18:00, stand-up, planning, demo, the Friday 17:00 report deadline
heinzel-acme-payments-checkout	team	The weekly report playbook: asset types (weekly report document, engineering tracker, tracker project, code repository) with discovery hints, and the template contract acme-payments-checkout:weekly-report, a draft by hand, schedulable for Friday 17:00

Install and look

You need Heinzelmännchen first. One command installs the app with its default plugins and opens it:

uvx heinzel@latest

No uv yet? The guided installer sets it up first:

curl -LsSf https://heinzel.team/install.sh | sh

Supported on macOS and Linux; Windows may work, but is not supported. Details: the standard app installation guide.

In a second terminal, add the Checkout team. Its layers come with it:

hz system plugin add "git+https://github.com/helmut-hoffer-von-ankershoffen/heinzel-acme#subdirectory=plugins/heinzel-acme-payments-checkout" --confirm

Then look around:

hz system layer list        # the tree, from the core
hz system layer show        # your stack: acme → acme-payments + acme-lisbon → acme-payments-checkout
hz acme layers              # the same tree as ACME declares it, on any core
hz acme info                # the bindings ACME recommends and how they stand on this machine
hz system doctor            # which adapter plugins and logins are missing
hz heinzel playbooks       # what each layer's playbook offers
hz setup acme               # accept the bindings you want, one by one
hz acme-lisbon calendar     # the site's week, at the site and on this machine

The first-party adapter plugins the bindings name are separate: use hz system plugin add github --confirm (or atlassian, zoom, google in place of github), each with its vendor CLI logged in as you; hz system doctor lists what is missing with the command that fixes it.

The weekly report

A locally saved fictional draft from a deterministic demo runner. See the Checkout gallery →

Otto: "A first draft. You decide what stays." The report is saved on your machine; nothing is posted or sent for you.

hz heinzel new weekly-report --template acme-payments-checkout:weekly-report \
  --asset weekly-report=<doc id> --asset engineering-tracker=<sheet id> \
  --asset tracker-project=CHK --asset code-repo=<owner>/acme-checkout
hz heinzel wake weekly-report --dry-run     # the inputs, fetched through gh, acli and gws; no model run, no cost
hz heinzel wake weekly-report               # the draft, saved locally for you to edit and send

To try it against a real (trial) world, docs/REHEARSAL.md walks a manager and an engineer through it on two machines, with hz acme seed creating the ACME world in your own trial accounts.

Port it to your company

docs/PORT_TO_YOUR_COMPANY.md is the runbook a coding agent (or you) follows to create a private heinzel-<company> repository with the same shape: what to rename, how to bind your company's own providers through a private layer, and what to verify first. This repository plus that runbook is the hand-off.

Compatibility

Each plugin declares its supported SDK range in its project metadata. The development lock records the SDK used by tests; users install the standard app without selecting an SDK version. No unreleased Core checkout is required. Plugin releases are independent of Core. An explicitly selected plugin tag or commit stays pinned when hz updates.

Theme

hz system theme use acme

The acme theme (src/heinzel_acme/themes/acme.toml) is deep teal on warm off-white, slate at night, with ACME's logo in themes/logo/: a peak shaped like an "A" standing on an anvil's base, hand-written SVG, teal #0f766e in light mode and #2dd4bf in dark mode.

Sound

The plugin offers the requested YouTube video as the acme soundscape. It pairs only with the ACME theme. It uses the core's privacy-enhanced player, with no downloaded or bundled media; installation leaves sound off, and the person still presses Play in the web player.

hz system sound list
hz system theme use acme
hz system config set system.sound.follow_theme true
hz system sound list       # effective: acme

For a direct choice, or to turn sound off:

hz system config set system.sound.follow_theme false
hz system sound use acme
hz system sound use off

Develop

make setup     # dependencies, pinned tools, git hooks
make check     # lint, types, unit and integration tests of all four plugins (offline)
make test-e2e  # installs Heinzelmännchen with uv and adds the team plugin from this checkout

See the threat model for what the plugins read, write and send. Run make setup before the PR or release helpers. Their direct tool invocations reuse the installed environment; delegated checks, fixes and Git hooks retain their own dependency installation and build steps.

Read AGENTS.md first. The plugins are one uv workspace: the company layer at the root, the others in plugins/, released together at one version. Tests use fakes and never reach a network; hz acme seed refuses to run the real CLIs inside a test session.

Release

Actions → Release → Run workflow opens a release pull request; merging it tags and publishes all four plugins. The version comes from conventional commits, the changelog from git-cliff. main changes only through pull requests.

This repository was generated from Heinzelmännchen's copier template; make update-template pulls in its latest standards, tooling and CI.