Project documentation and versioned product planning
Create a Project section, reusable document version conventions and a candidate product portfolio, linked to existing knowledge.
Objective and authorization
Create a useful Project documentation section for the concept and future independently versioned plans, estimates and resources; represent possible commercial offerings as subprojects. Preserve the three supplied candidate directions without inventing details.1
Ownership and boundaries
Manager chat 01a1241c-b623-7df3-a0d7-a85aa4a02811 owns this maintenance task and shared records/Git. Astra defines the new placement/version convention and independently accepts Sol implementation. Existing site chat owns website code. This is document organization and existing-context curation; substantive product development/research keeps its own scope/chat gates. No fresh online research, estimates, commercial commitments or automatic publishing.
Deliverables and done criteria
A Project front door; sourced concept snapshot; candidate products catalog; explicit future homes for plan, estimates and resources; immutable comparable document versions with separate adoption decisions; consistent harness guidance/templates; website Project navigation with desktop/mobile checks. Original sources and existing authority paths stay intact. Product candidates remain proposals.
Progress and next action
Astra supplied the bounded placement/version design. Sol has implemented the Project front door, concept register and sourced v001 snapshot, candidate catalog, placement/workflow guidance, reusable snapshot template and entry-point navigation. Website Project navigation and actual desktop/mobile checks are complete. Independent Astra accepted the 13 frozen files; manager matched their hashes and completed integrated checks. Next: final checkpoint and reconciled manual website update, then record verified delivery. The manager interprets the new section request in the ongoing website update context as covering this bounded publication to the existing site. No substantive product development or concept adoption is implied.
Authority and dependent impact
Placement authority changed first in harness/file-structure.md; harness/workflow.md now
distinguishes immutable document snapshots and human adoption from execution-scope gates.
The new version template implements that distinction. README and the current project brief
link to Project docs without moving or replacing existing authority. Existing scope templates,
skills and role instructions remain applicable: no scope behavior, model routing or execution
authorization changes. Existing decisions collection holds future actual adoption decisions;
none is invented. Website navigation is a separate owner deliverable. The documentation worker changed no scripts, shared indexes, original inputs, scopes, receipts or captures. The separate site owner changed the generator navigation and its focused test; static-site guidance is synchronized.
Checks and results
Sol worker checks on 2026-10-10: .venv/bin/python scripts/validate_harness.py
passed with zero errors; .venv/bin/python scripts/validate_knowledge.py passed
(332 Markdown files, zero errors); git diff --check passed. These are read-only
format/link/provenance checks, not human adoption or independent semantic acceptance.
No online evidence was gathered and no new capture/extraction gaps were introduced.
Manager-owned indexes/log, coordinated checkpoint, site checks and Astra acceptance remain pending.
Manager acceptance
Integrated checks pass all 87 tests, harness validation and 337 Markdown files with zero errors. The site owner checked Project → Concept register → v001, Project → Possible products and existing current context at 1280 px and 390 px. Navigation wraps without horizontal overflow or covering the heading. Manager independently checked the phone Project/concept path. Astra semantic acceptance and both checkpoint/preview conditions are satisfied. Final publication is not yet claimed.
-
Exact supplied request; organizational naming is an implementation choice. ↩