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).

This is the beginning of the README. Read the rest at the original. Read the full README ↗