Artefact Versioning

Description:

Actora should keep an immutable version history for every artefact (documents, policies, architecture diagrams, manuals, reference links). Each update creates a new version rather than overwriting the previous one. Users can view version metadata (who/when/why), compare versions, and roll back if needed. Versioning becomes the foundation for trusted summaries, review workflows, and conflict detection.

Value:

Prevents silent knowledge drift, supports auditability (who changed what and when), and enables reliable downstream AI (summaries tied to a specific version, not a moving target).

Acceptance criteria (short):

• Every artefact update creates a new version (previous versions remain readable).

• Each version stores metadata: created_by, created_at, source, checksum, storage pointer, size, MIME.

• API supports: list versions, fetch a version, set current version, rollback.

• Permissions enforced: only authorised users can create versions or rollback.