This roadmap separates four gates: merge, release, publication, and flagship adoption. Passing one does not imply the next.
Portfolio role: standalone product candidate. Develop this as a focused standalone product with its own distribution and support boundary. Integrate with the flagship through versioned contracts, not shared private source.
Planned repository identity: Deathcharge/samsarix-story-studio (ready).
Current disposition: Versions 1.0 through 1.5 are merged product candidates; 1.6 is under verification. Reproducible source packaging is implemented, while an independent user pilot, public release, and flagship adoption remain separate gates.
- Keep the default branch buildable from a clean checkout and preserve exact-head CI evidence.
- Keep Samsarix LLC branding, package identity, license metadata, and compatibility aliases internally consistent.
- Preserve the pre-productization default under a rollback ref before merging; do not delete legacy history.
- Make review metadata truthful and show advisory outcomes only when the configured reviewer actually ran.
- Remove inactive UCF trajectory and agent-log routes from the product interface while retaining storage compatibility.
- Remove story text from continuation URLs.
- Make local persistence commits consistent after write failure.
- Persist content-free generation jobs, report live stages, recover interrupted work, and support cancellation.
- Complete a blank chapter plan in place without duplicating or reordering manuscript chapters.
- Run a small user pilot against the exact packaged artifact.
- Instrument only truthful, privacy-respecting product signals and define support ownership.
- Promote from prerelease only after recovery, upgrade, and failure paths are demonstrated.
Current hardening backlog:
- No live provider smoke test or packaged-artifact user pilot; both require owner credentials/spend approval or independent participants. Reproducible packaging and exact runbooks are present.
- No committed tests execute paid provider SDK calls, live MySQL, or disk failure/corruption paths. Credential-free behavioral tests cover generation cancellation, overlap prevention, job ownership, and restart recovery.
- Remove invented review success, UCF values, token counts, logs, and trajectories from the active contract.
- Provider defaults and response compatibility can drift; five adapters plus unrestricted
OPENAI_BASE_URLcreate ongoing maintenance/security work. - Project backups round-trip through schema-validating, copy-only import with conflict-safe identity remapping.
- Chapter plans have explicit status and synopsis fields, and persisted ordering maintains a single continuity chain.
- Ordered scene cards round-trip through both storage profiles and backups and guide planned-chapter preparation.
- Bounded tags and favorites organize the local archive.
- Optional MySQL expands scope without live database CI evidence; its import path is transaction-scoped and type/build checked only.
- No desktop installer or hosted distribution path; source checkout is the current route.
- Legal ownership, BSL parameters, and branding need explicit owner approval.
- Branch history is confusing because unrelated
mainand defaultmasterrepresent different products.
- Define a public API, event, schema, artifact, or deployment contract before connecting to Samsarix Unified.
- Add a consumer-owned contract fixture covering authentication, privacy, limits, errors, and version compatibility.
- Make one implementation canonical; remove or freeze duplicate behavior only after parity and rollback are proven.
- Record an owner, support level, compatibility window, and measurable adoption signal.
A milestone is complete only when its exact commit, commands and results, artifact digest, consumer or deployment, and rollback path are recorded in a pull request or release record. README claims must not exceed that evidence.