Files
LumaWeb/planning/tasks/S00-029.md
T
wt 28320ff35a S00-022: Record blocked task and remediation handoff
Changes: Preserve incomplete work and blocker metadata for S00-022. This checkpoint does not mark implementation accepted.
Validation: Session ended with status blocked.
Blocker: Pinned libomemo.js@3.0.0 supplies real embedded WASM but is a different unaudited ratchet and excludes consumer SCE; no approved decision reconciles it with S00-022 retained audited engine/persistence requirement.

Task: S00-022
Agent: auto-crypto-bcd7f2a71667
Role: crypto
Action: claim
Status: blocked

Task title: Confirm or source a verified browser/WASM-capable OMEMO2 backend for the Web client endpoint
2026-10-15 17:17:19 +07:00

59 lines
3.1 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# S00-029: Record an approved browser OMEMO backend sourcing strategy
- Remediation для: S00-022; root: S00-004; depth: 2
> Generated from planning/tasks.json; status is in state/tasks.json.
- Этап: S00
- Оператор: orchestrator
- Reviewer: security
- Зависимости: S00-001, S00-002, S00-021, S00-027
- Требования: ENC-003, ENC-009, ENC-011
## Один результат
One explicit architecture/security/product-owner sourcing decision naming the retained engine browser port or authorizing bounded evaluation of an alternative, with license/support/security-assessment and persistence compatibility requirements, without waiving ENC-003/009/011.
## Разрешённые пути
- `docs/decisions/0003-browser-backend-decision.md`
Не изменять другие modules, shared contracts или spec snapshots без изменения плана. Stem без расширения разрешает принятые stack-specific extensions и focused test рядом.
## Прочитать
- docs/WEB_PROFILE.md
- docs/ARCHITECTURE.md
- docs/CONTRACTS.md
- docs/TESTING.md
- roles/crypto.md
- docs/decisions/README.md
- state/blockers/S00-022.md
- state/blockers/S00-029.md
## Шаги
1. Obtain explicit owner input naming a backend strategy; do not infer approval from candidate availability.
2. Record traceable primary sources, exact target, license/support constraints and required independent security assessment and SCE path.
3. If alternative engine is selected, require separate reviewed plan change for preservation wording before S00-022 resumes implementation.
4. Submit only the bounded decision for independent security review; do not implement crypto.
## Приёмка
1. Explicit owner decision is recorded; the candidate is not declared audited or interoperable without evidence.
2. Decision preserves ENC-003/009/011 and identifies remaining browser/SCE/vector/persistence checks.
3. Any engine replacement is contingent on reviewed plan change; no silent replacement or implementation occurs.
## Focused checks
1. Verify owner input and primary-source traceability for named target/license/support/security and SCE boundaries.
2. Independent security review confirms decision addresses engine/persistence preservation and contains no requirement bypass.
## Блокер и завершение запуска
Для всех ролей scope — только эта задача. При блокере создать issue JSON по state/ISSUE_TEMPLATE.json, вызвать escalate с текущим ID/role/agent, проверить status=blocked и resolution_task, затем немедленно завершить запуск. Не решать blocker и не выбирать следующую задачу самому. Новый агент назначается runner. Правки metadata через CLI — единственное исключение scope.
## Передача
Сохранить evidence/handoff; submit → review и завершить запуск. Reviewer также выполняет только эту задачу, включая обязательное escalate при блокере.