Trigger / Input
User opens http://127.0.0.1:4180/index.html.
Absolute Autonomous Systems Workflow Description
This client-demonstration pack documents the real implemented workflows in the static website: language settings, search recommendations, voice commands, video commands, automated consequence management, examples, training, shortcuts, contact capture, mobile navigation, and verification handover.
1. Homepage Command Console Workflow
Show the user the live autonomous status, language layer, command controls, and consequence queue from the first screen.
Responsible Component
index.html hero section, command bar, and app.js status renderer.
Gates
- All static assets must return HTTP 200.
- No blank hero, missing command status, or fatal console error is allowed.
Expected output
Expected output: the homepage displays the soft 3D console, translated hero text, ready command status, and working controls.
2. 11 Language Settings Workflow
Adapt every implemented screen section and dynamic component to the selected South African language.
Trigger / Input
User chooses a language from the top navigation selector.
Responsible Component
languageSelect control, translation packs, applyTranslations(), and localStorage.
Gates
- Unsupported language codes are ignored.
- Dynamic content must not keep English fallback text for non-English selections.
Expected output
Expected output: all visible app content follows the selected one of 11 South African languages.
3. Global Search Recommendation Workflow
Recommend searchable subjects from sections, examples, and training content across the whole app.
Trigger / Input
User clicks Search, presses Ctrl+K, or uses a search voice command.
Responsible Component
search panel, buildSearchIndex(), updateSearch(), and result navigation handlers.
Gates
- No-result state must remain readable.
- Result buttons must target real implemented sections.
Expected output
Expected output: recommended subjects appear immediately and jump the user to the correct section.
4. Voice Command Workflow
Let a supported browser navigate, search, read, change workflow state, and start video command mode using speech.
Trigger / Input
User clicks Voice or the hero Start voice control button.
Responsible Component
startVoice(), SpeechRecognition, handleCommand(), and command status UI.
Gates
- Unsupported browsers must show a readable fallback.
- Unknown phrases must show a no-match state instead of failing silently.
Expected output
Expected output: the command bar shows what happened and the requested action runs or displays a clear fallback.
5. Video Motion Command Workflow
Use camera motion to move between sections or open search without using the keyboard.
Trigger / Input
User clicks Video and grants camera access.
Responsible Component
startVideo(), getUserMedia(), motion canvas, and analyzeMotion().
Gates
- Missing camera or denied permission must show a readable fallback.
- Motion commands are rate-limited to prevent accidental rapid navigation.
Expected output
Expected output: camera command mode becomes active and deliberate motion updates navigation or search state.
6. Automated Consequence Management Workflow
Show automated accountability without requiring the user to manually trigger every follow-up.
Trigger / Input
The page loads and the consequence timer starts automatically.
Responsible Component
rule packs, tickRules(), renderRules(), and consequence section queue UI.
Gates
- Rules must stay visible in every language.
- Owner, severity, status, and next check must remain present.
Expected output
Expected output: users see a live consequence queue with owner, severity, status, and next action in the selected language.
7. 20 Demonstration Examples Workflow
Give prospective users realistic scenarios that make the system value concrete.
Trigger / Input
User opens Examples or filters the example list.
Responsible Component
demo subject packs, renderExamples(), and examples filter control.
Gates
- Every language must render exactly 20 examples.
- Filtering must never leave the grid in a broken layout state.
Expected output
Expected output: the user can browse or filter 20 realistic examples and see the human value of automation.
8. Training, Tutorial, and Manual Workflow
Teach users how to use language settings, search, voice, video, consequence management, and contact flows.
Trigger / Input
User opens Training or the full user manual.
Responsible Component
training section, docs/USER_MANUAL.html, screenshot evidence, and workflow PDF.
Gates
- Manual link must resolve to a real file.
- Screenshot paths must point to generated verification images.
Expected output
Expected output: the user has tutorials, screenshots, and multilingual training material for the implemented workflows.
9. Shortcut Prompt Workflow
Give users quick command phrases for search, examples, language switching, video, and reading the page.
Trigger / Input
User opens the command centre or reads the prompt pills.
Responsible Component
prompt packs, renderPrompts(), and handleCommand().
Gates
- Prompt text must match implemented command behavior.
- Unmatched prompt attempts must produce a readable no-match state.
Expected output
Expected output: users know the short commands and the app responds with visible action status.
10. Contact Request Capture Workflow
Capture a valid local request and give the user immediate confirmation without a backend dependency.
Trigger / Input
User completes the Contact form and submits it.
Responsible Component
contactForm submit handler and form status UI.
Gates
- The form must not navigate away from the static page.
- Success state must be visible to the user.
Expected output
Expected output: the form clears and the user sees that the next response task has been created.
11. Mobile Navigation Workflow
Keep the app usable on narrow screens without clipping or hidden workflows.
Trigger / Input
User opens the site on a mobile viewport and taps the menu button.
Responsible Component
responsive CSS, menuToggle, and navLinks state.
Gates
- No horizontal overflow is allowed.
- Menu state must become visible when opened.
Expected output
Expected output: mobile users can open navigation and access every implemented section without layout overflow.
12. Verification and Handover Evidence Workflow
Prove that the site, endpoints, workflows, screenshots, defects, and repair records are ready for handover.
Trigger / Input
Engineer runs npm run verify:all.
Responsible Component
tools/verify-site.cjs, tools/full-e2e-regression.cjs, workflow generator, and output/evidence.
Gates
- Open defects must be zero.
- Endpoint checks, workflow images, PDF verification, and dependency audit must pass.
Expected output
Expected output: evidence files show PASS, no open defects, validated workflow pack, and go-live readiness.