Repository navigation
Preview — reproduce one source-bound release and tutorial #45
Description
Outcome
A second developer reproduces the selected release artifact and useful Composition journey from its tutorial, with stated support limits.
Next planning checkpoint: Preview. This is the earliest scope/review conversation, not an assignment or a promise to finish the whole outcome in that week. Selected work starts at #52.
Remaining acceptance
Independent second-operator coordination from #109 is part of this outcome.
- Select exact source, package/image artifacts, supported environment and checksums; record their actual relationship.
- On a clean supported host, qualify exact Python/package artifacts, OCI image digest, dependency/platform and legal inventory.
- A second operator follows the tutorial through init → bind → start → actual reply → stop/restart and at least one useful selected Composition, without undocumented author rescue. Repair the instructions and repeat affected steps.
- Inspect source/artifact identity, permissions, setup errors and the agreed interruption/recovery case.
- Record what was tested and unsupported. Match tutorial/video claims to that exact result; no production or general desktop support is implied.
The 21 December developer preview is a fixed planning date with flexible selected scope. Voice is high priority. Minecraft and Atelier/Broadcast are candidate useful demonstrations, not blanket completion commitments. Select missing bounded tasks from Enter/Init findings; do not infer a release from green repository CI.
Evidence and handoff
Start from current State of Work and its linked source/tests and owning ADRs. The linked original acceptance remains binding unless a named replacement outcome records its disposition. Detailed scope, negative cases and dated campaign evidence are preserved in preserved scope and evidence; historical evidence does not establish current qualification on its own. Any accepted requirement not selected for this profile needs an explicit route in #62 before this issue closes.
Choose one small implementation or verification slice when this outcome is admitted. Record the responsible contributor, exact profile/revision, observed result, failure/unknown boundary and next checkpoint. The founder reviews and approves all code for this campaign; merge and promotion follow CONTRIBUTING.
Activity
zenithruneblade commentedon Nov 6, 2026
Planning reset — 6 November 2026. The original acceptance below remains binding unless a named replacement outcome records its disposition. This is a preserved historical body, not a fresh capability/qualification claim.
Original issue scope and dated evidence before the planning reset
Bind one source revision to tested Python archives and a retained Vessel image, then prove the installation journey.
Starting point: Current delivery: candidate/archive checks exist; a maintained paired package/image and clean-host acceptance receipt are missing.
First working slice
Connections: Uses #3/#18/#11 and #37. Accepts an ordinary reviewed source revision; #40 is an optional future candidate producer, not a prerequisite. Recovery coordinates are covered by #44.
Later: Separately authorized public release, more platforms and coupled-extension build manifests; no byte-identical image claim without proof.
References: ADR 17 · ADR 04.
Contribution entry: Reproduce one archive/image identity check or clean-host installation step.
Verification: Build artifacts and isolated supported host for final receipt. Shared contribution and touched-docs rules: #52.
Delivery review — 12 October 2026
Published source: a913bff.
Source-bound candidate artifact checks and legal-identity fixtures are maintained, and native systemd parsing now verifies quoted executable paths containing spaces for Vessel and Reactor. Published main still lacks the paired anonymously installable PyPI/immutable OCI candidate and complete clean-host operator journey required here. Offline parser and artifact checks do not prove install/start/reply/stop on a second host.
Delivery evidence
[-]Packaging — verify a source-bound release candidate on a clean host[/-][+]Preview — reproduce one source-bound release and tutorial[/+]