Documents need attachments and generated files (SPEC 9.4) before the UI of
M3 can show them, and the spec forbids external libraries for PDF and
spreadsheets.
- VolumeFileStore keeps files under <data>/files/<COMPANY>/<yyyy>/<guid>,
writing a .part file in the same folder with size limit and SHA-256, then
quota and scanner checks (IFileScanner hook, no-op by default).
- attachments table (migration 007) with kind, version series, lock, trash
and the uploading user; AttachmentService uploads, adds generated files as
the next version, lists, opens, zips, locks, trashes, restores and purges
after 30 days (new system job system.attachments-trash).
- FileGenerationService runs IFileGenerator implementations into the store;
three generators for the fictitious test document (PDF, CSV, XLSX).
- CsvWriter (Italian Excel defaults, formula-injection guard), XlsxWriter,
ZipStreamWriter and PdfWriter (standard Type1 fonts, WinAnsi, AFM widths,
JPEG, Flate, xref) only write asynchronously, so they can stream to an
HTTP response.
- ADR 0021 records versioning, storage layout, PDF scope and CSV defaults.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pages built so far now live inside the shell of the mockups instead of the
M0 placeholder, every interface text comes from Resources/it-IT, and each user
keeps their own look and start page.
- Shell: top bar, collapsible side menu with fly-out sub-menus, status bar and
tabs that keep each page alive (page type and route values per tab, so a tab
never shows another page); at most 12 tabs, least-used clean tab evicted.
- One shortcut table with Alt variants for the combinations browsers keep
(Ctrl+W, Ctrl+Tab, Ctrl+N); command palette for pages and commands.
- ITexts over embedded JSON; tests forbid literal texts in .razor components
and check that every key used exists.
- User settings in sys_user_settings / user_settings; theme written on the
server; profile page with live preview, start page, sessions and shortcuts.
- Home, coming-soon pages for later milestones, localized sign-in and error
pages; ADR 0020; wiki, CHANGELOG, STATUS and data model updated.
Refs #25#26#31#33
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The instance now starts on its own from KHAEMHAT_* variables: it migrates the system
and company databases, creates the super user and the first company, and only then
reports ready. Users sign in with password and TOTP through revocable database
sessions, and licences decide which modules and how many companies are available.
- Configuration: every wrong variable reported at once (exit code 2), _FILE variants
- Accounts, password policy and lockout, TOTP with recovery codes, session states
with token rotation, security audit with a hash chain
- Sign-in pages (mockups 001-003), authorization attributes, security headers and a
CSP without inline scripts, login rate limit
- Signed licences, activation codes, test mode, licence tool
- DataProtection keys in the system database, encrypted with the instance key
- Memory or Redis cache (in-house RESP client) that falls back to memory
- Database log by section with trace id; cron scheduler with locks and system jobs;
record history (audit_log)
- Company creation, states, company context and X-Company, 503 in maintenance
- In-memory SQLite databases stay alive for the process (tests, demo)
- Tests for all of the above, ADR 0019, wiki, SECURITY, CHANGELOG, STATUS, DATA-MODEL
Refs #15#16#17#18#19#20#21#22#23#24
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
M1 is tagged v0.1.0. STATUS now points at M2 and lists what M1 handed over to it (migration log section, startup
refusal without a valid KHAEMHAT_SECRET_KEY, PostgreSQL performance numbers); the wiki explains the encrypted
company registry and the two engines in plain words.
Refs #14
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every later milestone stores its data through this layer, so it has to behave the same on both engines and be safe
by construction:
- Khaemhat.Data: explicit entity maps, typed queries over a safe expression subset, SqlFragment where every
interpolated value becomes a parameter, unit of work with transactions, repositories with audit columns and
optimistic concurrency on row_version, retries on transient errors.
- SQLite provider (STRICT tables, WAL, exact decimals as integers scaled by 10^6, Unicode case-insensitive LIKE,
serialised writes) and PostgreSQL 16+ provider (numeric(19,6), timestamptz, jsonb, advisory locks, database
creation and server info). Databases are configured from postgres:// and sqlite:// URLs whose password never
appears in messages.
- C# migrations with system and company catalogues, schema_version with checksums, one transaction per migration
under a lock, refusal of unknown applied versions; first system tables sys_companies and sys_settings.
- CompanyRegistry stores each company's database URL encrypted with the instance key (AES-256-GCM, HKDF-derived key,
purpose as associated data), so a copied row cannot be read for another company.
- tools/Khaemhat.DataModelTool, scripts/gen-datamodel.sh and scripts/new-migration.sh: the current schema section of
docs/DATA-MODEL.md is generated from the migrations and a test fails when it is stale.
- C# 14 binds array.Contains to MemoryExtensions over spans; the query translator unwraps the span conversion.
- Tests run every data scenario on SQLite and PostgreSQL (PostgreSQL in CI); ADR 0018 records where the contracts
differ from SPEC 5.1. Docs, wiki, changelog and status updated.
Closes#7, #8, #9, #10, #11, #12, #13, #14
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Start development with the skeleton every later milestone builds on, so
that code, image and release path exist and are verified from day one.
- Khaemhat.sln with the ten projects of SPEC section 3 and six MSTest
projects; shared build rules with warnings as errors, analyzers and
Central Package Management restricted to the allowlist.
- Architecture tests and scripts/check-packages.sh fail on any project
reference or package that SPEC does not allow.
- Khaemhat.Web serves an Italian "under construction" page with the
official icons and version, plus /health/live, /health/ready and
/health (ADR 0012); honours KHAEMHAT_URLS and KHAEMHAT_LOG_LEVEL.
- docker/Dockerfile (non-root app user aligned to PUID/PGID by the
entrypoint, pg_dump 17, healthcheck, OCI and Unraid labels) and
compose files for PostgreSQL and a standalone SQLite demo.
- Gitea Actions: ci.yml (build, tests, image smoke test, PostgreSQL
16/17 on tags, YAML check), release.yml (image and release from a
vX.Y.Z tag, skipping versions already published) and wiki.yml.
- Development scripts, VS Code launch/tasks for debugging, and ADR
0012-0017 deciding the M0 open points of docs/STATUS.md.
Closes#1, #2, #3, #4, #5, #114
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gitea flags en dash, multiplication sign, minus sign and single angle
quotes as confusable characters, which put a warning on most pages;
use plain equivalents (docs/SPEC.md stays untouched). STATUS.md now
lists the issue numbers per milestone, the items waiting for the owner
and the open specification questions tracked by issue #114.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Prepare everything needed before development starts on Khaemhat, the
ERP + CRM for Italian SMEs:
- docs/SPEC.md: the original project specification, unchanged, plus
CLAUDE.md with operational rules and amendments (Gitea instead of
GitHub/GHCR, Docker image as the only deliverable).
- ADR 0001-0011 for the baseline decisions.
- Mockups: 22 high-resolution screens, the full gallery, 88 thumbnails
cropped from it, mockup.css and an index.
- Technical docs (architecture, data model, modules, API, MCP, deploy,
security, development process, status with open spec questions).
- Full draft wiki in docs/wiki (already published to the Gitea wiki).
- Icons in assets/ and deploy files for Docker Compose and Unraid,
pointing to the Gitea package registry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>