4.6 KiB
Application Upgrade Sequence
Decision agreed: 2026-09-28
Purpose and Order
Adopt the newly released applications through focused, individually reviewed features in this order:
Scriptorium → Audita → Notarius → Narratio → suite integration.
This document tracks the cross-feature direction, not implementation steps. Each feature roadmap owns its scope and decisions. Only one staged plan is active at a time, at implementation.md.
Version Baseline
These are the suite pins at the start of this upgrade, not assertions about what is installed on an operational host. Targets are the releases reviewed on the decision date; later releases require deliberate review.
| Application | Starting suite version | Adoption target |
|---|---|---|
| Scriptorium | v0.13.0 | v0.15.0 |
| Audita | v0.9.1 | v2.0.1 |
| Notarius | v0.7.1 | v0.8.1 |
| Narratio | v2.2.0 | v3.0.0 |
Seriatim is unchanged by this sequence.
Progress and Feature Links
Release-summary and migration-guidance triage is complete. Standalone Scriptorium and Audita adoption are complete after independent review; Notarius is next. Add the numbered feature link beside each item when its roadmap is created; check it off after independent review and closeout.
- Feature 0018: Scriptorium adoption — complete through role
b174c8c; independent review found no remediation issues. - Feature 0019: Audita adoption — complete through role
c3dd59f; independent review found no remediation issues. - Notarius adoption — feature roadmap not yet created.
- Narratio adoption — feature roadmap not yet created.
- Suite integration — feature roadmap not yet created.
Adoption Boundaries
Completing a standalone-role update does not advance the suite's application or role dependency pins, collection snapshot, or deployment-repository pins. Keep that existing compatibility set until the final integration feature assembles and validates the coordinated configuration.
Standalone features own generic application interfaces. The integration feature owns D&D defaults, cross-application configuration, testing overlays, credential references, compatible dependency pins, and consumer upgrade guidance. Each feature follows roadmap → staged plan → implementation → review → closeout. No operational deployment is authorized merely by this sequencing decision.
Compatibility Constraints to Carry Forward
- Scriptorium is not a documentation-only upgrade from our baseline. The intervening v0.14.0 introduces ConfigKit and changes configuration acceptance, selection, and retry behavior. Review those changes as well as v0.15.0's licensing and dependency updates.
- Audita and Narratio need a coordinated suite cutover. Audita v2 requires migrated configuration; Narratio v3 expects that interface and no longer owns the retired downstream settings or generated Audita configuration.
- Overlay terminology changes on both sides of the Notarius boundary. Narratio's selector and the suite-managed downstream files must migrate together. Preserve explicit selection and independent application ownership.
- Existing Narratio manifests need operator migration guidance. Carry the upstream provenance-field migration into final integration planning. Preserve session progress; do not infer a requirement to delete checkpoints, force all stages, edit immutable remote snapshots, or automate the migration.
- Review retry and timeout semantics explicitly. New transport retry and repair behavior is not necessarily equivalent to the previous settings. Preserve user intent without copying old values mechanically or inventing new suite policy.
The upstream documentation remains authoritative for exact fields and migration procedures: