Skip to main content
Version History

ArcaQ feature

§1 — How versioning works

Versioning is automatic and transparent — no manual commits needed.

Automatic snapshot on save

Every note save writes a versioned copy to <arcaq:versions/> with timestamp.

Timeline view

Chronological list of all snapshots with version number, date and content preview.

One-click restore

Restoring a version replaces current note content and creates a new version entry.

Content diff

Side-by-side diff highlights additions, deletions and rewrites between any two versions.

Linked to annotations

Annotations from the time of a save are reflected in that version's metadata.

Audit-ready

Every version record includes user ID, timestamp and note type — audit-ready out of the box.

§2 — API reference

One endpoint retrieves the full version history for any note.

MethodEndpointDescription
GET/second-brain/notes/{note_id}/historyRetrieve all version snapshots for a note
@prefix arcaq: <http://arcaq.com/> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . arcaq:versions/v-001 a arcaq:NoteVersion ; arcaq:forNote arcaq:notes/note-42 ; arcaq:versionNumber "3"^^xsd:integer ; arcaq:savedAt "2026-05-14T14:22:00Z"^^xsd:dateTime ; arcaq:savedBy arcaq:users/alice ; arcaq:content "Full note content as a string literal..." .

§3 - Runtime stabilization update

Recent hardening fixes removed transient gateway errors and restored stable module loading across the dashboard.

SSE proxy reliability

Notifications stream is now proxied in streaming mode to prevent chunked-read interruptions and intermittent 500 errors.

Ontology API resilience

Ontology stats/products now degrade gracefully on backend faults, eliminating prior 502 regressions in UI workflows.

Dashboard module routing fix

The expert_queue route alias is handled explicitly, preventing unknown-module rendering failures during HTMX loads.

Cluster stability verified

Post-fix checks on server01 confirmed running core pods with no CrashLoopBackOff on active platform services.

§4 — Release 1.1.12 (August 2026)

A stabilization and capability release: bulletproof SSO sessions, the OLM Enrichment Dashboard, full OOC internationalization, Kimi K2 as enterprise LLM (in-house or sovereign provider), automated backups and platform-wide observability.

SSO session stability

Keycloak realm (tour-operator) and token audience alignment across API and UI removed all session-expired errors. Tokens now last 8 hours with silent 24-hour refresh.

OLM Enrichment Dashboard

Live pipeline view (Qdrant, LLM, SHACL, Jena) with causal state machine SLA tracking, HGT consensus tiers (P1/P2/P3) and expandable PROV-O lineage per event.

OOC fully translated

Operational Ontology Contracts are now available in 17 languages with high-quality translations, consistent with the rest of the platform UI.

Kimi K2 enterprise LLM

Enrichment, classification and reasoning now run on the Kimi K2 enterprise LLM, operated in-house or by a sovereign provider, improving latency and answer quality.

Backups & OOM safeguards

Scheduled PostgreSQL backups protect platform state, and memory limits with eviction policies keep pods stable under image and data load.

Observability & pagination

Prometheus metrics across all microservices, Grafana dashboards, and paginated API responses for large result sets.

Get started