Oleksandr Bezdieniezhnykh
846670a5c5
Updated various documentation files to clarify the handling of splittable artifacts, allowing for folder equivalents of key markdown files when they exceed size limits. Adjusted references in multiple sections to reflect this new structure, ensuring consistency across the research methodology. Enhanced clarity on the saving actions and artifact organization, particularly for `01_source_registry.md`, `02_fact_cards.md`, and `06_component_fit_matrix.md`. This change aims to improve usability and maintainability of the research documentation.
2.7 KiB
Solution Draft
Assessment Findings
| Old Component Solution | Weak Point (functional/security/performance) | New Solution |
|---|---|---|
| [old] | [weak point] | [new] |
Product Solution Description
[Short description. Brief component interaction diagram. Written as if from scratch — no "updated" markers.]
Architecture
[Architecture solution that meets restrictions and acceptance criteria.]
Applicability — the table columns
Pinned Mode/ConfigandAPI Capability Evidenceapply only to technical-component runs (per SKILL.md → Research Output Class). For non-technical assessment outputs (e.g., reassessing a policy approach, comparing organizational designs), this Architecture section may be replaced with the assessment content that does not use these columns; or the columns may be markedN/Aper row for non-technical "components". For mixed runs, fill the columns only on rows that describe libraries/SDKs/frameworks/services/protocols/data formats/algorithms.
Component: [Component Name]
| Solution | Tools | Pinned Mode/Config | Advantages | Limitations | Requirements | Security | Performance | API Capability Evidence | Fit |
|---|---|---|---|---|---|---|---|---|---|
| [Option 1] | [lib/platform] | [exact mode/config used: inputs, outputs, runtime] | [pros] | [cons] | [intrinsic requirements] | [security] | [perf] | MVE: [link to MVE block]; docs: [Source #] | [Selected / Rejected / Experimental only / Needs user decision — cite exact-fit evidence and disqualifiers] |
| [Option 2] | [lib/platform] | [exact mode/config used] | [pros] | [cons] | [intrinsic requirements] | [security] | [perf] | MVE: [link]; docs: [Source #] | [Selected / Rejected / Experimental only / Needs user decision] |
Exact-fit evidence:
- Project constraints checked: [inputs/outputs, operating context, lifecycle, NFRs, acceptance criteria]
- Evidence: [Fact # / Source #]
- Disqualifiers: [none or list]
- Restrictions × Candidate-Modes sub-matrix: see
06_component_fit_matrix.md(or06_component_fit_matrix/if split) § - API capability gates: ✅ MVE saved / ⚠️ partial — see disqualifiers / ❌ no MVE — candidate is Experimental only or Rejected
[Repeat per component]
Testing Strategy
Integration / Functional Tests
- [Test 1]
- [Test 2]
Non-Functional Tests
- [Performance test 1]
- [Security test 1]
References
[All cited source links]
Related Artifacts
- Tech stack evaluation:
_docs/01_solution/tech_stack.md(if Phase 3 was executed) - Security analysis:
_docs/01_solution/security_analysis.md(if Phase 4 was executed)