Engineering acceptance framework
Requirements & Acceptance
A testable requirements framework for progressing the demonstrator from software logic to physical prototype evidence. Thresholds marked TBD must be established through engineering analysis and material-specific trials.
| ID | Requirement | Acceptance evidence | Status |
|---|---|---|---|
| FRR-01 | Detect a recoverable flexible-line arrangement and construct a state representation containing endpoints and candidate crossings. | Recorded perception frames + state reconstruction output across defined test fixtures. | PLANNED |
| FRR-02 | Maintain an explicit last-verified line state before committing a manipulation. | Control log demonstrates state ID continuity and commit gating. | SOFTWARE DEMO |
| FRR-03 | Execute a slack-creation action without exceeding configured development tension limits. | Force/tension trace and action log for each trial. | PHYSICAL TEST REQUIRED |
| FRR-04 | Detect a failed manipulation using geometry and/or physical-response disagreement. | Injected-failure trial with verification result recorded as FAIL. | SIMULATION |
| FRR-05 | Return to the last physically safe verified state when rollback is feasible. | Interrupted-action trial; compare pre-action and recovered state. | PHYSICAL TEST REQUIRED |
| FRR-06 | Support alternate manipulation selection after a failed action. | Repeat fixture with primary action failure followed by alternate action. | PLANNED |
| FRR-07 | Prevent continued motion when a watchdog or defined safety fault removes motion authority. | Fault-injection test and controller event log. | ENGINEERING TEST REQUIRED |
| FRR-08 | Transfer a recovered line toward a controlled organization path. | End-to-end fixture test with defined output geometry. | PHYSICAL TEST REQUIRED |
| FRR-09 | Record enough telemetry to reconstruct every manipulation attempt. | Run log contains state, action, modules, confidence, expected/observed change and verification result. | SOFTWARE DEFINED |
| FRR-10 | Operate within material-specific mechanical and electrical safety limits. | Qualified risk assessment, calculations and physical validation. | REQUIRED |
Minimum prototype acceptance sequence
- Single straight line acquisition.
- Single crossing recognition.
- Controlled slack creation.
- Crossing separation.
- Verification and state commit.
- Injected failed action.
- Rollback to verified state.
- Alternate action and successful recovery.
- Transfer to organization output.
- Repeat across defined cable/rope/strap fixtures.
Evidence boundary: The current project contains architecture, browser simulation and test definitions. It does not yet contain physical prototype measurements. No performance threshold should be represented as achieved until measured.
Validation dashboardPrototype build specControl package