Files
mokosh/.planning/INGEST-CONFLICTS.md

15 lines
1.2 KiB
Markdown
Raw Permalink 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.
## Conflict Detection Report
### BLOCKERS (0)
(none — no LOCKED-vs-LOCKED contradictions, no cycle-detection blockers, no UNKNOWN-confidence-low classifications)
### WARNINGS (0)
(none — no competing acceptance variants; only one SPEC and one DOC ingested, with no overlapping requirement asserting divergent acceptance criteria)
### INFO (1)
[INFO] Auto-resolved: SPEC > DOC on extension RAM footprint
Note: README.md §"Память" (line 106) states an expected steady-state of "~5-10 МБ в фоновом режиме"; the SPEC Тз расширение фаза1.md §10 acceptance criterion 9 sets the binding ceiling at "не превышает 50 МБ в фоне" — the same README §"Критерии приёмки Фазы 1" line 118 also restates the 50 МБ ceiling identically. Per precedence ADR > SPEC > PRD > DOC, the SPEC §10 ceiling wins and is recorded as constraints.md CON-ram-ceiling at 50 MB. The README's 5-10 МБ figure is preserved as a non-binding informational target alongside CON-ram-ceiling (sources: /home/parf/projects/work/repremium/Тз расширение фаза1.md §4, §10; /home/parf/projects/work/repremium/README.md lines 106, 118).