azaion/gps-denied-onboard

Fork 0

mirror of https://github.com/azaion/gps-denied-onboard.git synced 2026-06-23 05:11:13 +00:00

Files

T

Oleksandr Bezdieniezhnykh 1f634c2604

ci/woodpecker/push/02-build-push Pipeline failed

Details

Update demo replay validation and testing documentation

- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests.
- Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps.
- Updated architectural documentation to include the new demo replay operator flow and its dependencies.
- Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation.
- Added new entries in the dependencies table for upcoming tasks related to the demo replay flow.

These changes improve clarity and usability for operators and developers working with the demo replay system.

2026-06-20 11:24:43 +03:00

2.7 KiB

Raw Blame History

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/Config and API Capability Evidence apply 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 marked N/A per 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 (or 06_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]

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)

2.7 KiB Raw Blame History Unescape Escape