Revise the Seriatim plan and workspace conventions

docs/roadmap/features/0002-audita-source-installation-and-configuration.md

@@ -0,0 +1,35 @@
+# Feature 0002: Audita Source Installation and Configuration
+
+Status: proposed
+
+## Planning Note
+
+Audita remains the likely next application role, but its previously drafted
+roadmap and implementation plan were withdrawn before implementation. They
+depended on the original Seriatim fingerprint, sidecar-state, staged-build,
+and corruption-recovery architecture, which is no longer an approved pattern.
+
+Do not implement this feature from the withdrawn plan. After the simplified
+Seriatim role has been implemented and reviewed, discuss Audita again and
+write a fresh feature roadmap using the workspace's minimal, module-driven
+conventions.
+
+## Preserved Upstream Research
+
+- The latest selected immutable release was `v0.9.1`, resolving to commit
+  `a84941d68168a1ed9ea7423b6477ae8218be73f9` when inspected.
+- The tag declares Go 1.24.0 and builds the package
+  `gitea.maximumdirect.net/eric/audita/cmd/audita` with `CGO_ENABLED=0`,
+  `GOWORK=off`, `GOTOOLCHAIN=local`, `-trimpath`, and the documented release
+  linker flags.
+- The release does not expose a CLI version command suitable for Seriatim's
+  version-based rebuild check. The simplest appropriate rebuild signal must be
+  decided during renewed roadmap discussion.
+- Audita configuration schema version is `1`. Its native validator accepts
+  `audita config validate --config <path>` and reports `config is valid` for a
+  valid file.
+- Default configuration discovery prefers
+  `/usr/local/etc/audita/config.yml` over `/etc/audita/config.yml`.
+
+These facts should be revalidated against the authoritative `../audita`
+repository before a new roadmap is approved.