Go to file

Thomas Stallinger 217f672ddd docs: design Auftragskatalog as ad-hoc, revocable Merkmal assignment

ADR-0010 decides that an Auftrag is technically a Merkmal, not a new
parallel entity: it reuses the existing Merkmal/Blueprint/ansible-role
mechanism from ADR-0002, but adds a device-level, independently
toggleable assignment path (device_merkmale) alongside the existing
workspace-level one. Deselecting an Auftrag needs to actually revert
it, so checkin will need to declare a full present/absent state per
catalog entry rather than just an additive list; that role-level and
API-level work is deferred, this only settles the data model.

Also adds a single generic, append-only event log
(device_merkmal_events) for both selection changes and agent-reported
execution results, instead of several purpose-specific tables, so
future event types don't require schema changes. Extends
09-data-model-v1.md and the glossary accordingly.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-08-03 23:29:12 +02:00

adr

docs: design Auftragskatalog as ad-hoc, revocable Merkmal assignment

2026-08-03 23:29:12 +02:00

architecture

docs: design Auftragskatalog as ad-hoc, revocable Merkmal assignment

2026-08-03 23:29:12 +02:00