Repository navigation
Human action 41
Canonical work item: #41.
When required: Before treating Gate B as satisfied. The issue carries current status, decisions, and completion evidence.
Owner role: Maintainer and participating users.
The maintainer accepted the refreshed standing evidence record after PR #86. The assembly/review item #41 is complete. This acceptance leaves all nine Gate B conditions unproven and downstream store/protocol work gated. The procedure below remains available for future evidence reviews; closing the assembly item does not satisfy its recorded conditions.
Prerequisites: Use the nine conditions in ADR-0014/product §15, actual workflow adoption from #19, and identified hosts including Windows/OneDrive and POSIX.
- For each of the nine conditions, identify an actual user/workflow observation or mark the condition unmet. Include schemas, host identity, run links, repository context, outcomes, and limitations.
- Collect evidence of user preference, recovered squash causality, useful IDs, forecast accuracy, workspace/checkpoint benefits, safe resolution reuse, real-corpus behavior, portability limitations, and material overhead.
- Review the standing evidence table with the maintainer. It distinguishes actual Windows compact delivery, workspace/checkpoint use, and a clean pinned forecast/application from the still-missing sustained, conflicted, and POSIX outcomes. Record either acceptance of the table as the standing record or specific corrections on #41. Accepting a table with unmet conditions does not accept Gate B.
- Retain run evidence on the issue or approved artifact store and record the resulting gate assessment. #19 owns participation and user outcomes, #42 owns representative performance/budgets, and #14 owns synced-folder evidence. Do not duplicate their follow-up issues.
Verification: All nine conditions must have adequate evidence before Gate B is treated as satisfied. Documentation of an unmet condition does not clear it.
Failure handling and cleanup: Preserve unmet conditions and keep downstream gates closed. Do not infer adoption or user preference from green tests.
Completion: attach the evidence/decision to issue #41, resolve its human-action label when satisfied, update the private board, and point the Human TODO entry to the completed outcome.
Publish only evidence suitable for the public issue/wiki. Redact private paths, repository content, and credentials from shared output. Sensitive vulnerability findings belong in a draft security advisory.