# ReqBridge Team — AI Setup Agent Guide

Version: 1.0  
Scope: ReqBridge Team r3 on Windows 10 or Windows 11 (64-bit)  
Audience: an AI assistant helping an authorized administrator install and configure ReqBridge Team

## Purpose

Help an authorized administrator set up ReqBridge Team safely and reproducibly without collecting, exposing, or inventing personal data, credentials, licence keys, customer records, or confidential business information.

This guide is procedural. It does not grant access to any computer, mailbox, network, payment account, or production system.

## Non-negotiable safety rules

1. Work only on devices, folders, networks, and accounts the administrator explicitly authorizes.
2. Never ask the administrator to paste passwords, licence keys, recovery codes, API keys, tokens, private keys, or payment data into chat.
3. Never place real personal or customer data in demonstrations, screenshots, logs, or support messages. Use clearly fictional test data.
4. Never disable antivirus, firewall, access control, encryption, or backup protection to make setup easier.
5. Do not expose the local ReqBridge service directly to the public internet. Remote access requires an administrator-approved private network or managed remote-access solution.
6. Do not send email, buy a licence, alter billing, restore a backup, delete records, or deploy an update without action-time confirmation from the administrator.
7. Stop and explain the risk if the observed system differs materially from this guide.

## Information to collect without personal data

Ask the administrator for configuration choices, not secrets:

- Setup type: single computer or local team workspace
- Supported Windows version and 64-bit architecture confirmation
- Intended number of authorized users
- Whether local-network collaboration is required
- Preferred application and synchronization ports, if defaults are unavailable
- Backup destination category, such as encrypted local drive or approved network storage
- Recovery-point objective and backup frequency
- User roles required: administrator, business user, or developer
- Whether an existing ReqBridge workspace must be migrated

Use placeholders in notes, for example `ADMIN_EMAIL`, `WORKSPACE_HOST`, `BACKUP_LOCATION`, and `LICENCE_KEY_PRESENT`. Never record the real values.

## Phase 1 — Pre-installation checks

1. Confirm Windows 10 or Windows 11, 64-bit.
2. Confirm at least 200 MB of free disk space plus adequate space for database growth and backups.
3. Confirm a current Chrome, Edge, or Firefox browser is available.
4. Verify the installer came from the official ReqBridge purchase, account, or recovery flow.
5. If a published checksum or signature is supplied, verify it before execution.
6. Confirm who is authorized to create the first local administrator account.
7. For an upgrade, create and verify a recoverable backup before continuing.

## Phase 2 — Single-computer installation

1. Start the approved installer or executable.
2. Allow only the permissions required for local operation.
3. Launch ReqBridge Team. The local interface normally opens in the default browser.
4. Confirm the address is local and the application responds before entering any licence information.
5. Ask the administrator to enter the licence key directly into the application. Do not observe, copy, or store it.
6. Ask the administrator to create the first local administrator account directly in the application.
7. Confirm sign-in, sign-out, and a fresh sign-in work.

## Phase 3 — Local team workspace

Use this phase only when the administrator requests collaboration between authorized devices.

1. Choose a stable Windows device to host the workspace during working hours.
2. Keep the application interface and database on that authorized host.
3. Enable local-network access only when required.
4. ReqBridge normally uses local port `8765` for its interface and `8766` for local synchronization. If changed, document only the selected port numbers, not network identities.
5. Limit firewall rules to the required application, profile, port, and trusted network scope.
6. Never create a public router port-forward for ReqBridge.
7. Connect each peer through the administrator-approved in-app workflow.
8. Verify one test record synchronizes correctly before onboarding real users.
9. Verify an unauthorized device cannot access the workspace.

## Phase 4 — Roles and users

1. Create only the accounts the administrator authorizes.
2. Apply least privilege:
   - Administrator: configuration and user administration
   - Business user: business requirements and assigned operational work
   - Developer: technical requirements and assigned implementation work
3. Do not share accounts between people.
4. Have each user choose their own password privately.
5. Test permissions with fictional records before adding operational data.
6. Remove test accounts that are no longer needed.

## Phase 5 — Initial workspace configuration

Create a fictional pilot project before operational use:

1. Create one Project with currency, dates, and a test budget.
2. Create one Requirement and link it to the Project.
3. Add planned and actual Requirement costs.
4. Add planned and actual effort to the Requirement.
5. Create one Ticket, link it to the same Project, and add planned and actual effort.
6. Open the Project page and verify that linked Requirements, linked Tickets, cost totals, personnel effort, remaining budget, variance, utilization, and overrun indicators are correct.
7. Confirm global search finds the fictional Project, Requirement, and Ticket.
8. Confirm read-only Open views and authorized Edit actions work.
9. Delete the fictional data only after the administrator confirms the validation result.

## Phase 6 — Backup and recovery

1. Select an administrator-approved encrypted backup destination.
2. Create the first backup from the supported in-app workflow.
3. Verify the backup is present, dated, and non-empty without opening or copying its contents into chat.
4. Perform a restore test only in an isolated test location or after explicit administrator approval.
5. Record the result without database contents, user names, paths containing personal names, or secrets.
6. Define a recurring backup schedule appropriate to the organization’s change rate.

## Phase 7 — Updates

1. Back up the workspace before an update.
2. Obtain updates only through the official ReqBridge update or account flow.
3. Confirm the application accepts the package as valid before applying it.
4. Read release notes and identify any configuration or compatibility impact.
5. Apply the update only after the administrator confirms.
6. Repeat the validation checklist after the update.
7. If validation fails, stop operational changes and follow the approved rollback or support path.

## Validation checklist

- Application launches and the local health check succeeds
- Administrator can sign in, sign out, and sign in again
- Required users and roles exist with least privilege
- Project creation and Open/Edit views work
- Requirement creation and Project linking work
- Ticket creation and Project linking work
- Planned and actual costs roll up correctly
- Requirement and Ticket effort roll up correctly
- Budget variance, utilization, and overrun indicators are correct
- Global search returns authorized records across the workspace
- Backup creation is verified
- No service is exposed directly to the public internet
- No personal data or secrets appear in setup notes

## Troubleshooting decision path

1. Capture the exact visible error text and the action that produced it.
2. Record the application version, Windows version, setup type, and whether the issue is reproducible. Do not capture secrets or personal data.
3. Check whether the application is already running and whether the selected local ports are occupied.
4. Check firewall scope without disabling the firewall.
5. Re-test with fictional data in the smallest reproducible workflow.
6. Preserve logs only if they are free of credentials, licence data, customer content, and personal identifiers.
7. If unresolved, prepare a sanitized support request containing impact, steps, expected result, actual result, version, and non-sensitive evidence.

## Completion report template

```text
Setup type: SINGLE_DEVICE | LOCAL_TEAM
Application version: VERSION_ONLY
Operating system: WINDOWS_VERSION_ONLY
Installation: PASS | FAIL
Authentication: PASS | FAIL
Roles and permissions: PASS | FAIL
Project/Requirement/Ticket workflow: PASS | FAIL
Budget and effort roll-up: PASS | FAIL
Global search and Open views: PASS | FAIL
Backup verification: PASS | FAIL
Public internet exposure: NONE_CONFIRMED | REVIEW_REQUIRED
Remaining issues: SANITIZED_SUMMARY
Administrator action required: YES | NO
```

Do not add names, email addresses, licence keys, passwords, network addresses, customer content, or absolute user-specific file paths to this report.