architecture/generic.md

Project Architecture Preferences

Baseline architectural conventions for new projects. Claude Code should follow these defaults when scaffolding, implementing, or refactoring unless the project explicitly overrides them. When in doubt, ask before deviating.

These preferences are opinionated and have evolved from running real multi-site infrastructure. They optimise for: local-first operation, reproducible deployments, minimal release-time churn, and keeping secrets out of source control.

---

1. Workspace Layout

Projects are Rust cargo workspaces. The repository root contains:

<repo-root>/
├── Cargo.toml              # workspace manifest (workspace-level deps + version)
├── crates/                 # all Rust crates live here
│   ├── <app>-entities/     # domain types, DTOs, error enums — no I/O
│   ├── <app>-core/         # business logic, pure where practical
│   ├── <app>-data/         # data access: postgres, turso, filesystem, etc.
│   ├── <app>-crypto/       # shared cryptography (only if needed across bins)
│   ├── <app>-os-utils/     # shared OS/process/path helpers (only if needed)
│   ├── <app>-api/          # binary: REST / JSON / WebSocket daemon
│   ├── <app>-worker/       # binary: long-running processor / queue consumer
│   └── <app>-cli/          # binary: operator / admin CLI
├── <frontend-dir>/         # Vite + React + SWC + TS frontend(s) — see §4
├── asset/                  # deployment artifacts (see §6)
├── script/                 # deploy.sh and related operational scripts
└── readme.md

Crate naming

Use <app>-<role> throughout. The <app> prefix makes grep, cargo output, and systemd unit naming unambiguous across a multi-project host.

Separation of concerns (strict)

• entities — types only. No I/O, no async runtime deps. Serde, thiserror, chrono/time are fine. Everything downstream depends on this.
• core — business logic. Consumes entities. May define traits for data access (ports) that the data crate implements (adapters). No direct DB or network calls.
• data — implements the traits defined in core. Owns all sqlx/turso/reqwest usage relevant to persistence and external services.
• binaries — thin. Wire up config, logging, signal handling, and the appropriate core/data stack. Binaries should contain no business logic that could live in a library crate.

Shared utility crates

Only create <app>-crypto, <app>-os-utils, etc. when genuinely shared by two or more binaries. Premature extraction is worse than inlining — extract when the second consumer appears.

---

2. Cargo Workspace Conventions

Workspace-level versioning

Every crate in the workspace shares a single version, defined once in the root Cargo.toml:

[workspace.package]
version = "0.1.0"
edition = "2024"
rust-version = "1.85"
license = "GPL-3.0-or-later"   # adjust per project
authors = ["Rob Thijssen <rob@example>"]

[workspace]
resolver = "3"
members = ["crates/*"]

Each crate's Cargo.toml inherits:

[package]
name = "<app>-entities"
version.workspace = true
edition.workspace = true
rust-version.workspace = true
license.workspace = true
authors.workspace = true

Rationale: release tagging scripts only need to rewrite one version string. CI stamps and changelogs stay consistent across artifacts from the same tag.

Workspace-level dependencies

Declare every external dependency once under [workspace.dependencies] in the root manifest. Crates reference them via dep.workspace = true. This prevents version drift between crates in the same workspace.

[workspace.dependencies]
tokio = { version = "1", features = ["full"] }
serde = { version = "1", features = ["derive"] }
sqlx = { version = "0.8", default-features = false, features = ["postgres", "runtime-tokio-rustls", "macros", "migrate"] }
thiserror = "2"
tracing = "0.1"
# ...

Internal crate dependencies

Internal crates depend on each other via path + version:

<app>-entities = { path = "../<app>-entities", version = "=0.1.0" }

Use = pinning on the internal version to guarantee in-workspace coherence after publishing or vendoring.

Edition and toolchain

• Rust edition 2024.
• Commit a rust-toolchain.toml at the repo root pinning the stable channel to match CI.

---

3. Binaries and Runtime

Daemons run under systemd

API and worker binaries are managed by systemd unit files shipped from asset/systemd/. Binaries should:

• Log to stdout/stderr using tracing with structured JSON output when JOURNAL_STREAM is set (journald will ingest cleanly).
• Read config from /etc/<app>/config.toml by default, overridable via --config and env vars (figment-style layering: file → env → CLI).
• Handle SIGTERM gracefully: stop accepting new work, drain in-flight tasks with a bounded timeout, exit 0.
• Never daemonise themselves. systemd owns the lifecycle.
• Expose a health endpoint (for api) or emit periodic heartbeat logs (for workers) so systemd and monitoring can assess liveness.

API crate

• Axum is the default web framework unless there's a reason otherwise.
• Serves REST + JSON over TCP, with WebSocket upgrades where streaming is needed.
• TLS terminates at the site nginx reverse proxy (see §7) unless the binary itself is the ingress (e.g., Cichlid-style self-serving nodes), in which case use rustls with post-quantum-capable cipher suites.
• API surface versioned under /v1/ from day one.
• Request/response types live in <app>-entities so clients (including the desktop app) can depend on them.

Worker binaries

• Long-running processors (ingestion, indexing, queue consumers) use Postgres FOR UPDATE SKIP LOCKED for work-claiming where a central DB is already in play.
• Idempotent by design — crashes and restarts should never double-process.
• Backoff with jitter on transient failures; escalate to DLQ semantics on repeated failure.

---

4. Frontends

Web (default)

Vite + React + SWC + TypeScript. The frontend lives in a top-level directory named for what it is to the user, not a generic web/. Common names:

• web/ — the primary public-facing app, when there's only one frontend
• ui/ — equivalent, when the project prefers this naming
• dashboard/ — a user-facing dashboard UI
• admin/ — an operator/admin console distinct from the public UI

A project may have more than one of these (e.g., both dashboard/ and admin/). Each is an independent Vite app with its own package.json, built and deployed separately, typically served from its own nginx server_name or path prefix. Pick names that describe the audience or purpose; don't invent a generic wrapper directory to hold them.

Whatever the directory is called, the internal structure is the same:

<frontend-dir>/
├── package.json
├── vite.config.ts
├── tsconfig.json
├── index.html
└── src/
    ├── main.tsx
    ├── App.tsx
    ├── api/          # generated or hand-written client for the <app>-api
    ├── components/
    ├── routes/
    └── lib/

• Build output is static. Deployed to an nginx CDN endpoint — no Node.js in production.
• API base URL is configured at build time (Vite import.meta.env.VITE_API_BASE_URL) and stamped per environment during deploy.
• Prefer React Query or equivalent for server state. Keep business logic server-side; the frontend is a rendering and interaction layer.
• When a project has multiple frontends, they may share types via a local package (e.g., packages/shared-types/) or via generated TypeScript bindings from the Rust entities crate. Don't duplicate API clients across frontends — factor the shared bits out.

Web (Rust framework exception)

Use a Rust web framework (Axum + templating, or a fullstack framework) only when the deployment model requires a single self-contained binary with no external web server — e.g., distributed orchestration nodes that each serve their own UI over TLS. The Cichlid pattern. Default is still Vite + nginx.

Desktop

Tauri. Consumes the same <app>-api as the web client. Shares types via the <app>-entities crate (exposed to the Tauri frontend via generated TypeScript bindings — ts-rs or specta).

Mobile

Preferences TBD. When a project targets mobile, the goal is a framework that consumes the existing backend API (keeping business logic server-side) and produces responsive native-quality UIs for both Android and iOS from a shared codebase. Revisit this section once there's real-world experience to draw on.

---

5. Data

Central database: Postgres

Default for any app with a central data store.

• Connection is mTLS with passwordless auth. Host-level client certificates issued by the internal step-ca, with cert CN → pg role mapping via pg_ident.conf.
• No passwords in config files, ever. Connection strings reference cert paths.
• Migrations via sqlx-cli or refinery; migration files live in crates/<app>-data/migrations/.
• Migrations are sequentially versioned and immutable once committed. File naming follows the tool's convention (V0001__init.sql, V0002__add_users.sql, … for refinery; 0001_init.sql, 0002_add_users.sql, … for sqlx). Each new schema change lands as a new file with the next sequence number — never edit a migration that has already been committed, even if it hasn't been deployed yet, because checksums diverge and the migration runner will refuse to start (or worse, leave production out of sync with dev).
• Schema changes are forward-only in production. Destructive migrations require a dedicated maintenance window and an explicit plan.
• If you catch a bug in a recently-added migration before it's been merged or deployed anywhere, amending is fine — but the moment it's landed on main or run against any database, treat it as frozen and write a follow-up migration to correct the mistake.
• Use sqlx with compile-time query checking (sqlx prepare) and commit the generated .sqlx/ offline query cache so CI builds don't need a live database.
• Agentic contributors working in a project with a Postgres dependency will usually have MCP access to a Postgres MCP server scoped to that project's database(s). Prefer using the MCP server to inspect schema, verify query shapes against real tables, and sanity-check migrations before applying them — don't guess at column names or types when you can look them up. The scope is limited to the project's own databases; don't assume access to unrelated ones.

Distributed database: Turso

When the app's data model is distributed (edge replicas, per-site local copies with sync), use Turso. Auth via Turso-issued tokens stored in the per-host secret store, not in manifest.yml.

Caching / ephemeral state

Prefer in-process (moka, quick-cache) over introducing Redis. Only add Redis when multiple processes genuinely need to share ephemeral state and Postgres LISTEN/NOTIFY won't do.

---

6. Deployment Assets (asset/)

asset/ is the single source of truth for what gets deployed where. No secrets in this directory, ever — it's in source control.

asset/
├── manifest.yml            # environments → components → hosts
├── systemd/
│   ├── <app>-api.service
│   ├── <app>-api.socket        # if socket-activated
│   ├── <app>-worker.service
│   ├── <app>-indexer.timer
│   ├── <app>-indexer.service
│   └── <app>.sysusers.conf     # systemd-sysusers drop-in
├── firewalld/
│   ├── <app>-api.xml           # named firewalld service per §9
│   └── <app>-worker.xml
├── selinux/                    # only if custom policy is required
│   ├── <app>.te
│   └── <app>.fc
├── nginx/
│   └── <app>.<site>.conf   # per server_name configs
├── config/
│   ├── config.toml.tmpl    # templated; {{SECRET_NAME}} placeholders
│   └── ...
└── sql/
    └── bootstrap.sql       # idempotent role/db creation

manifest.yml structure

app: <app>
environments:
  prod:
    components:
      api:
        hosts: [oolon.hanzalova.internal]
        config:
          bind: 127.0.0.1:8080
          log_level: info
      worker:
        hosts: [gramathea.kosherinata.internal, oolon.hanzalova.internal]
        config:
          concurrency: 4
      web:
        hosts: [cdn.hanzalova.internal]
        root: /var/www/<app>
  dev:
    components:
      api:
        hosts: [quadbrat.hanzalova.internal]
        config:
          bind: 127.0.0.1:8080
          log_level: debug
      # ...

Top-level keys: app, environments. Each environment defines components, each component defines hosts (one or many) and config (non-secret values only). Secret references are placeholders resolved by deploy.sh at deploy time.

Templated config

Config file templates use a simple {{VAR_NAME}} syntax. deploy.sh substitutes values from the host's pass store (or equivalent) into the template before shipping to the target. The unrendered template is committed; the rendered file never is.

---

7. Deployment Script (script/deploy.sh)

A bash script with a stable CLI:

./script/deploy.sh <environment> [component...]

./script/deploy.sh prod api worker
./script/deploy.sh dev all
./script/deploy.sh prod default

Contract

• First positional arg is the environment name, matched against manifest.yml environments.*.
• Subsequent args name components, or all (every component in the environment), or default (a project-defined sensible subset — often everything except disruptive migrations).
• Parses manifest.yml with yq.
• For each (component, host) pair:
  1. Build the artifact locally (cargo build release, vite build, etc.) if not already built for the current commit.
  2. Resolve secrets from pass (or the project's configured secret backend) and render config templates.
  3. rsync binary + rendered config + systemd units + sysusers drop-in + firewalld XML + any SELinux assets to the target host over ssh (quantum-safe key exchange).
  4. On the target, in this order: a. systemd-sysusers to create the service account if missing (§8). b. Create/chown /etc/<app>, /var/lib/<app> with correct modes. c. restorecon -R on installed paths; apply semanage changes and load any policy module (§10). d. Install firewalld service XML, firewall-cmd --reload, ensure the service is enabled in the appropriate zone, persistently and at runtime (§9). e. systemctl daemon-reload and restart the unit(s).
  5. Verify health (HTTP probe for api, systemctl is-active for all).
• Exit non-zero on any failure. Report per-host status at the end.

Requirements

• Idempotent. Running twice with no changes is a no-op beyond file copies.
• Quiet on success, loud on failure.
• Supports --dry-run to print what would happen.
• Never writes secrets to disk on the build host outside of the rendered template being rsynced.

---

8. Deployment: Service Accounts

All targets run Fedora Server (current stable, 43 at time of writing). Claude Code should assume this and target the idiomatic Fedora way of doing things.

Services run as dedicated non-root system users by default. Root is an exception requiring explicit justification (e.g., a service that genuinely needs to bind < 1024 without CAP_NET_BIND_SERVICE, manage kernel modules, or similar).

Creating the service account

Ship a sysusers.d drop-in with the app and let systemd-sysusers create the user at deploy time. Place it at asset/systemd/<app>.sysusers.conf:

#Type Name          ID    GECOS                         Home directory    Shell
u     <app>         -     "<App> service account"       /var/lib/<app>    /usr/sbin/nologin

deploy.sh installs this to /etc/sysusers.d/<app>.conf and runs systemd-sysusers on the target. This is idempotent and survives package reinstalls.

Directory ownership

Services typically need:

• /etc/<app>/ — config (root:, 0750; files 0640) so the daemon can read but not write.
• /var/lib/<app>/ — mutable state (:, 0750).
• /var/log/<app>/ — only if the service logs somewhere other than journald (rare; prefer journald).

deploy.sh must create these with correct ownership and modes, not rely on the service creating them at runtime.

systemd unit hardening

Unit files in asset/systemd/ should use the user, not run as root, and include the standard hardening knobs unless a specific feature prevents it:

[Service]
Type=notify
User=<app>
Group=<app>
ExecStart=/usr/local/bin/<app>-api --config /etc/<app>/config.toml

# Hardening — enable unless the service genuinely needs otherwise
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
PrivateDevices=true
ProtectKernelTunables=true
ProtectKernelModules=true
ProtectControlGroups=true
RestrictRealtime=true
RestrictSUIDSGID=true
LockPersonality=true
MemoryDenyWriteExecute=true
SystemCallArchitectures=native

# Writable paths (minimum necessary)
ReadWritePaths=/var/lib/<app>

# Network
RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6

If a setting breaks the service, relax only that one — don't disable hardening wholesale.

Privilege exceptions

If the service must run as root or with extra capabilities, document the reason in a comment at the top of the unit file. Prefer narrow AmbientCapabilities= (e.g., CAP_NET_BIND_SERVICE) over full root.

---

9. Deployment: Firewall (firewalld)

All hosts run firewalld. Every service that listens on a port must ship a named firewalld service definition rather than opening bare ports in a zone. The service name matches the systemd unit name (minus .service).

Why named services

Named services are self-documenting (firewall-cmd --list-services tells you what's actually running), removable atomically on app decommission, and survive zone reassignment without reconfiguration.

Shipping the definition

Place the XML in asset/firewalld/<app>-<component>.xml:

<?xml version="1.0" encoding="utf-8"?>
<service>
  <short><app>-api</short>
  <description>REST/WebSocket API for <app></description>
  <port protocol="tcp" port="8443"/>
  <!-- multiple ports fine if the app needs them -->
  <port protocol="tcp" port="8444"/>
</service>

What deploy.sh must do

For each component with a firewalld service definition:

1. rsync the XML to /etc/firewalld/services/<app>-<component>.xml on the target.
2. firewall-cmd --reload to pick up the new definition.
3. Resolve the host's default zone (firewall-cmd --get-default-zone) and check if the service is already enabled there:

   zone=$(firewall-cmd --get-default-zone)
   firewall-cmd --zone=$zone --query-service=<app>-<component>
   

4. If not, enable it persistently and in the runtime config:

   firewall-cmd --permanent --zone=$zone --add-service=<app>-<component>
   firewall-cmd --zone=$zone --add-service=<app>-<component>
   

5. On component removal (future concern), the reverse: --remove-service then delete the XML.

Steps must be idempotent — re-running a deploy is a no-op on the firewall layer if the service is already installed and enabled.

Zone selection

The infrastructure uses only the default zone created at OS install time — FedoraServer on servers, FedoraWorkstation on workstations. There are no custom zones (no internal, no wg), and deploy.sh should not create any. Always add services to whatever firewall-cmd --get-default-zone reports on the target host.

If a future need arises to segment traffic by interface (e.g., restricting a component to the WireGuard interface only), revisit this section before introducing custom zoning — don't add it silently.

Port ranges, ICMP, sources

If a service needs port ranges, ICMP types, or source-IP restrictions, put them in the same XML using firewalld's standard elements (<port port="x-y" />, <source address="..."/>). Don't split these across multiple named services.

---

10. Deployment: SELinux

All hosts run SELinux in enforcing mode. Deployments must either operate cleanly within the default targeted policy or ship the labels and policy modules they need. Running setenforce 0 to "just get it working" is never acceptable, and Claude Code should flag any suggestion to do so.

Order of preference

Try these in order. Go no further down the list than necessary:

1. Fit the default policy. Install binaries to /usr/local/bin/ (or /usr/bin/ for packaged apps), state under /var/lib/<app>/, config under /etc/<app>/, logs to journald. These paths already have sensible default labels and most Rust daemons will run unmodified under unconfined_service_t or init_t.
2. Apply existing contexts with semanage fcontext. When files land in non-standard paths, map them to an appropriate existing type:

   semanage fcontext -a -t bin_t '/opt/<app>/bin(/.*)?'
   semanage fcontext -a -t etc_t '/opt/<app>/etc(/.*)?'
   semanage fcontext -a -t var_lib_t '/opt/<app>/var(/.*)?'
   restorecon -Rv /opt/<app>
   

3. Use booleans for common permissions the service needs (e.g., setsebool -P httpd_can_network_connect on if nginx needs to reach the API). Document every boolean flipped in the deployment.
4. Register non-standard ports. If the API binds to a port not already known to SELinux, label it:

   semanage port -a -t http_port_t -p tcp 8443   # if not already labelled
   

   Check first with semanage port -l | grep <port> and skip if the label is correct.
5. Ship a custom policy module only when the above don't cover it. Place sources in asset/selinux/<app>.te (and .fc, .if as needed). Build and install at deploy time:

   checkmodule -M -m -o <app>.mod <app>.te
   semodule_package -o <app>.pp -m <app>.mod -f <app>.fc
   semodule -i <app>.pp
   

   Custom modules should be as narrow as possible. If the policy ends up allowing everything, it's wrong — generate rules from audit2allow only after confirming the denial is actually legitimate, never as a blanket suppression.

What deploy.sh must do

• After installing files, always run restorecon -R on their installation paths so filesystem labels match the policy.
• Apply semanage fcontext / semanage port / setsebool changes permanently (no runtime-only hacks).
• Load or reload any shipped policy module with semodule -i.
• Keep these operations idempotent. semanage fcontext -a on an already-registered path errors; deploy scripts should check with semanage fcontext -l first, or use -m (modify) with a guard.

Dev loop

During development on a test host, ausearch -m AVC -ts recent and audit2why are the primary tools for diagnosing denials. Capture the clean set of rules once stable, fold into asset/selinux/<app>.te, and commit. Never leave a host with permissive mode set — if you set it during debugging, put it back before ending the session.

Podman quadlets

For containerised workloads: quadlets run confined under container_t by default. Bind mounts of host paths need :Z (private relabel) or :z (shared relabel) depending on whether the volume is shared across containers. Default to :Z unless sharing is required.

---

11. Infrastructure Context

This is the environment these apps deploy into. Claude Code should assume it.

Network

• Multi-site WireGuard mesh. Sites are numbered; host IPs follow 10.<site>.0.0/16 (currently 10.3.0.0/16 and 10.6.0.0/16, but the second octet encodes the site and is the stable part).
• Per-site OPNsense router handles WAN/LAN and the WireGuard endpoints.
• Internal DNS split-horizon via .internal domains (hanzalova.internal, kosherinata.internal, etc.).

TLS / PKI

• Internal PKI via Smallstep step-ca at ca.internal.
• Host certs renewed via systemd timers.
• mTLS everywhere internal services talk to each other.
• Quantum-safe SSH (sntrup761x25519 KEX) and TLS (X25519MLKEM768 where peers support it) are the default. External peers that don't support PQ fall back to classical curves — document the fallback explicitly in nginx config.

Ingress

• Per-site nginx reverse proxy terminates all WAN inbound 443.
• Public DNS via Cloudflare, unproxied by default (CF's mTLS origin-pull has been unreliable). Revisit if/when that changes.
• nginx serves static frontends directly from /var/www/<app> and reverse-proxies API traffic to the internal host:port from manifest.yml.

Hosts

• Fedora Server, current stable (43). Workstations run the same release.
• Services run as dedicated non-root users per §8.
• firewalld with named services per §9.
• SELinux enforcing per §10.
• Podman quadlets for containerised workloads; bare-metal systemd units for native Rust binaries (preferred where feasible).

Source hosting

• New projects are hosted on the self-hosted Gitea instance at git.lair.cafe (or git.internal on the WireGuard mesh — both resolve to the same instance). Agentic contributors will usually have MCP access to this Gitea and should prefer it over any public forge when creating repos, issues, or PRs.
• Legacy projects live under various GitHub / GitLab orgs tied to my public username (grenade). These will continue to exist but are being migrated to Gitea over time, especially when they come up for a refactor.
• When a project has been relocated, the original public repo should carry a prominent notice at the top of its readme.md (or a GitHub archival notice) pointing to the new Gitea URL. If you're working in a repo that looks stale or superseded, check for such a notice before assuming it's still the canonical location.
• Default to git.lair.cafe / git.internal for new scaffolds. Only push a new project to GitHub/GitLab if there's a specific reason (OSS visibility, CI integration that only the public forge offers, etc.) — and note the reason in the project readme.md.

---

12. Code Quality and Tooling

Formatting and linting

• cargo fmt on commit (pre-commit hook or CI gate).
• cargo clippy --all-targets --all-features -- -D warnings must pass.
• Frontend: eslint + prettier, configured to match the team style. Type errors fail the build.

Testing

• Unit tests live alongside the code they test (#[cfg(test)] mod tests).
• Integration tests under crates/<crate>/tests/.
• End-to-end tests that require a database use a dedicated test DB per run, created and torn down by the test harness.
• Target: core business logic has meaningful test coverage. Binaries have smoke tests.

Observability

• tracing with tracing-subscriber. JSON output in production, pretty output when stdout is a TTY.
• Structured log fields for request IDs, user IDs (where applicable), and operation names.
• No println! or eprintln! in committed code outside of CLI binaries' user-facing output.

Error handling

• Library crates use thiserror for typed errors.
• Binaries use anyhow at the outermost layer, with .context(...) at call boundaries.
• Never unwrap() in production code paths. expect("...") with a clear message is acceptable for invariants that are genuinely impossible to violate.

Documentation

• Every public item in library crates has a doc comment.
• Each crate has a readme.md or top-level module doc explaining its role in the workspace.
• The repo readme.md covers: what the project does, how to build, how to run locally, how to deploy. Point readers to this document for architectural conventions.
• Name readme files readme.md (lowercase), not README.md. The shouty all-caps spelling is a convention I don't share; filenames aren't where emphasis belongs. Every forge in use (Gitea, GitHub, GitLab) renders readme.md as the repo landing page just as readily as README.md. Other conventional top-level docs — license, changelog, contributing — follow the same rule: lowercase, no shouting.
• Exception: CLAUDE.md and AGENTS.md stay in uppercase. These are agent-facing instruction files and are easy to miss in a file listing when lowercased. The all-caps spelling is the established convention and the one that tooling (Claude Code and other agent harnesses) looks for, so leave them as-is.
• Agents may modify CLAUDE.md and AGENTS.md at their own discretion — no approval needed to add, update, or remove guidance when it's warranted. Diffs get reviewed, so unintentional drift will surface in the normal flow. Treat these as living instructions that should be kept accurate and current.

Commits

• Use Conventional Commits syntax for every commit. type(scope): subject, with types drawn from the standard set (feat, fix, docs, refactor, test, chore, build, ci, perf, style). Scope is the crate, component, or area touched. Subject is imperative and under ~70 characters. A body may follow if the why isn't self-evident.
• Agentic contributors may commit without asking, provided the change is a coherent, complete unit of work — the feature works, the bug is fixed, the refactor is finished. No approval prompt is needed for good commits that end a thread of work.
• Don't declare victory prematurely. If there's a realistic chance that follow-up commits on the same topic will be needed to finish the job (because the implementation is speculative, the tests haven't been run, or edge cases haven't been considered), stop and think before committing. A stream of sequential commits all fixing up the same incomplete attempt pollutes history and is more annoying than an approval prompt.
• When in doubt, consolidate before committing rather than landing half-done work and patching it afterwards. One commit that resolves the task cleanly beats five commits that thrash around getting there.
• Never --amend a pushed commit, never --no-verify, and never bypass pre-commit hooks to get a commit in. If a hook fails, fix the underlying issue.

---

13. Conventions Summary for Claude Code

When scaffolding or extending a project:

1. Default to the workspace layout in §1. Ask before deviating.
2. Put new types in entities, new logic in core, new I/O in data. Binaries stay thin.
3. Add dependencies to the workspace root first, then reference with dep.workspace = true.
4. Version strings live in exactly one place — the workspace root.
5. Any new deployable component gets an entry in asset/manifest.yml, a systemd unit in asset/systemd/, a sysusers drop-in, a firewalld service XML, and any required SELinux assets — in the same change.
6. Config templates go in asset/config/ with {{PLACEHOLDER}} secrets. Never commit a rendered config.
7. Postgres connections are mTLS, passwordless. If writing connection code that accepts a password, stop and ask.
8. Frontends are Vite + React + SWC + TS, served as static assets from nginx. Name the directory after its audience (web/, ui/, dashboard/, admin/) — web/ is not a mandated convention. Rust web frameworks require a stated reason.
9. Services run as dedicated non-root users with hardened systemd units per §8. Root requires explicit justification.
10. Every listening port gets a named firewalld service per §9. No bare --add-port calls.
11. SELinux stays enforcing. Work with the default policy first; ship a custom module only when necessary (§10). Never suggest setenforce 0.
12. Prefer fewer dependencies. Prefer bare-metal systemd over containers unless there's a reason.
13. Commit in Conventional Commits syntax. Commit autonomously when the work is done; hold off when follow-ups on the same topic are likely (§12 Commits).
14. Default new repos to git.lair.cafe / git.internal (self-hosted Gitea). Public forges only with a stated reason (§11 Source hosting).
15. When unsure, ask — these preferences are defaults, not mandates, but deviations should be deliberate.