commit f49774e7781183f560348b2567bb7b3686d70984
Author: zemion <albrecht@degering.name>
Date:   Sat Aug 1 16:31:51 2026 +0200

    Sync Repo-README from project files

diff --git a/Repo-README.-.md b/Repo-README.-.md
new file mode 100644
index 0000000..e7aeb8e
--- /dev/null
+++ b/Repo-README.-.md
@@ -0,0 +1,41 @@
+<!-- codex-wiki-sync:5f5c064a906bf69861425fbe -->
+
+> Mirrored from `/mnt/DATA/git/govoplan-forms/README.md`.
+> Origin: `repository`.
+> Active tasks and changing state belong in Gitea issues; this wiki page is durable project context.
+
+---
+# GovOPlaN Forms
+
+<!-- govoplan-repository-type:start -->
+**Repository type:** module (domain).
+<!-- govoplan-repository-type:end -->
+
+`govoplan-forms` owns reusable, immutable form definitions, validation rules,
+and form package fragments. Submission runtime behavior remains in
+`govoplan-forms-runtime`.
+
+The module persists exact tenant-bound revisions, exposes bounded catalogue,
+history, and write APIs, and provides `forms.definitions` for consumers. A
+published revision can be used by Forms Runtime without importing Forms tables;
+existing submissions keep their exact revision when a new schema is published.
+
+The `/forms` designer uses shared application controls to create, revise,
+publish, retire, search, and inspect definitions. It edits field order, types,
+choices, validation constraints, draft behavior, attachment and signature
+requirements, policy references, and permitted handoff kinds. Saving always
+creates an exact immutable revision; it never mutates a published schema in
+place.
+
+Definition writes use optimistic concurrency. Replaying the same object and
+revision is safe only when the payload is identical. Published definitions may
+be retired but not silently returned to draft.
+
+Focused verification:
+
+```bash
+PYTHONPATH=src:/mnt/DATA/git/govoplan-core/src \
+  /mnt/DATA/git/govoplan/.venv/bin/python -m unittest discover -s tests
+```
+
+See [docs/FORMS_BOUNDARY.md](docs/FORMS_BOUNDARY.md) for the boundary decision.