TERNYLO WORKSPACE — VERIFICATION METHOD Version 1.0.0 | October 1, 2026 | Published by TERNYLO HISTORICAL REPORT This report describes the October 1, 2026 build before the October 3 payment requirement. Creating new profiles now requires a confirmed plan payment and an active Starter, Pro or Team plan. The former Free allowance is retired. PURPOSE Verify the available configuration workflow with three demonstration profiles. This first-party report covers specific observed behaviors. It is not an independent certification, a browser-engine benchmark or a competitor ranking. ENVIRONMENT Local Node.js 24 application on Windows. A separate SQLite database and two synthetic accounts were used. The customer's actual accounts, profiles and payment records were not used. The six automated workflow scenarios exercised the application's HTTP API. SIX VERIFIED SCENARIOS 1. Create three profiles: expect HTTP 201 for each, distinct record IDs, and matching names, groups, target systems, locations and notes. 2. Try to create a fourth profile on Free: expect HTTP 409 and three records still present in the account. 3. Revise the checkout profile's notes: save the full record and read it back. Expect the revised notes and a matching Profile updated activity event. 4. Sign out: expect the old session to receive HTTP 401. Sign in again and verify the same three records and revised notes. 5. Use a second account: expect empty profile lists and exports. Attempts to edit or delete the first account's record return HTTP 404. 6. Export the first account: expect format ternylo-profiles-v1 and exactly three records. Compare each field to the saved values. Do not depend on array order. BROWSER DEMONSTRATION The published screenshots show the actual TERNYLO interface with the example data. Searching for Checkout left the matching configuration in the table. Filtering by Release QA displayed all three configurations. Configure displayed the saved checkout instructions. The export includes all account profiles, regardless of a visible filter. EXISTING REGRESSION SUITE 107 automated tests passed with zero failures in the October 1, 2026 run. The suite covers local authentication, profile/order access boundaries, payment-state rules and chain-specific transaction validation. Quote and blockchain responses are simulated fixtures. No funds were sent. For a local copy of the project, run npm test to execute that suite. TRY THE USER WORKFLOW Create a free TERNYLO account. Open Browser profiles, choose New profile and recreate the three records in qa-configurations.json. Use the Release QA group. Edit a note, try name search and group filtering, sign out and back in, then select Export JSON. Compare the fields against your saved configurations. The sample file is a reference, not a supported import/restore file. AVAILABLE FILES qa-configurations.json — actual configuration export of synthetic demo records. qa-verification-results.json — timestamps and observed results for the six checks. No credentials, sessions, account IDs, customer data or payment records are included. SCOPE System and location fields describe configuration targets. They do not launch browsers, change IP addresses or run QA. Session isolation, fingerprint changes, proxy routing and an antidetect browser engine are outside this version. The regression results exercise defined cases; they do not prove that all possible defects are absent. Retest after changing the relevant implementation.