Governed Core Package
Versioned identity and personality, Raz–RiotSpark continuity, governed memory, drift and tamper protection, safe mode, hash-chained audit, backups and interchangeable model adapters.
P2.6 Review, Correction and Knowledge Editing is complete and accepted. Phase 2 now advances into personality continuity and the Behaviour Studio—making RiotSpark recognisably continuous while keeping behavioural evolution transparent, reversible and owner-controlled.
Current authorised checkpoint:
P2.7 Personality Continuity and Behaviour Studio
Versioned identity and personality, Raz–RiotSpark continuity, governed memory, drift and tamper protection, safe mode, hash-chained audit, backups and interchangeable model adapters.
Phase 1 frozen as an immutable, recoverable foundation. Runtime development separated cleanly without changing the constitutional Core.
Persistent runtime foundations, recovery and streaming behaviour, and the chat-first interface around the governed Core are complete.
Conversations now persist and resume correctly across restarts, allowing interaction to continue without losing its place.
Manual knowledge entry, candidate review, classification, owner-controlled approval and mandatory why-layer provenance are complete. Owner acceptance and release validation passed.
Tier inspection and placement, bounded tier-aware retrieval, owner-authored distillation with source links, storage and growth visibility, and Knowledge Studio inspection and actions are complete and owner-accepted. Distillation remains governed; automatic retention deletion and model-authorised memory mutation are excluded.
Release validation passed: 260 tests discovered, 258 passed and 2 skipped for symlink privileges. Live SQLite integrity passed. JavaScript execution checks were not run in the release environment because Node was unavailable.
Scheduled review queues, revision comparison, governed editing, correction and supersession, subject inspection, conflict visibility and recovery are complete. Corrections can supersede outdated knowledge while preserving provenance, revision history and an auditable record.
Checkpoint validation covered 330 automated tests: 328 passed and 2 were skipped. Live SQLite integrity and the committed checkpoint validation passed.
Building transparent, reversible and owner-controlled behavioural evolution: interaction preferences, personality inspection, change evidence, response previews, approval, version history and rollback.
Validate privacy boundaries, protected context, safe mode, Core tamper detection, audit integrity, backup, restoration and portable export.