Question 1

Does the bot phone home to botwir3?

Accepted Answer

No. Zero network calls to botwir3. The spec hash is computed locally. The gate validates locally. The ledger writes locally. The only network calls go to the connected platform — Coinbase, Alpaca, Hyperliquid, whatever got wired up. botwir3 is not in that loop.

Question 2

If botwir3 goes offline, does the bot stop?

Accepted Answer

No. botwir3 could cease to exist tomorrow and every downloaded bot keeps running. The bot is a self-contained compiled binary. The spec, the gate, the ledger — all local. The bot never talked to botwir3 after download. There is nothing to disconnect from.

Question 3

What telemetry gets sent back to botwir3?

Accepted Answer

None. Zero telemetry. Zero analytics. Zero logs. Zero phone-home. There is no reporting endpoint in the runtime. There is no analytics SDK. There is no crash reporter. Air-gapped is the only mode. There is nothing to turn off because there is nothing to turn on.

Question 4

Can the discipline layer be separated from the strategy?

Accepted Answer

Yes. They're separate modules. Signal logic computes what to do. The gate validates whether it's allowed. The ledger records what happened. The architecture is compositional — each module has a single responsibility and a clean boundary.

Question 5

Will a downloaded bot work forever without a subscription?

Accepted Answer

Yes. The runtime is a compiled native binary. Zero dependencies on botwir3 servers, APIs, or subscription status. No license key. No expiration. No time bomb. No runtime installation required. A bot downloaded today runs for as long as the operating system runs executables.

Question 6

What happens when a third-party API changes?

Accepted Answer

Platform adapters depend on external APIs that evolve. If Coinbase updates the API, the adapter may need updating. botwir3 publishes adapter updates for active subscribers. Non-subscribers can write their own adapter — the interface is documented.

Question 7

Does botwir3 store API keys?

Accepted Answer

No. API keys are entered into a local config file on the machine running the bot. They never leave that machine. botwir3 never sees, transmits, or stores credentials for any platform.

Question 8

Can botwir3 access the connected trading accounts?

Accepted Answer

No. botwir3 has no access to any exchange, broker, or marketplace account. The bot runs locally with locally-stored credentials. The connection is between the bot and the platform — botwir3 is not a party to it.

Question 9

Is the strategy config file encrypted?

Accepted Answer

The config file is plain JSON stored locally. It can be encrypted at rest using standard disk encryption (FileVault, BitLocker, LUKS). The spec hash inside the file is a SHA-256 fingerprint — if any field changes, the hash breaks and the bot halts.

Question 10

Can someone tamper with the bot while it's running?

Accepted Answer

If the config file is modified while the bot runs, the gate detects the spec hash mismatch on the next cycle and halts. MANDATE_INTEGRITY_VIOLATION. The bot stops rather than execute under a modified spec.

Question 11

Can someone reverse-engineer the bot?

Accepted Answer

The runtime is compiled to native machine code. Reverse-engineering a compiled binary requires a disassembler and deep expertise. The math, the gate logic, the execution strategies — all opaque after compilation. The config file is readable (it's the user's strategy), but the engine that executes it is not.

Question 12

What does the gate actually do?

Accepted Answer

Every cycle, the signal module proposes an action. The gate checks: is the action type allowed? Is the magnitude within constraints? Would the result stay within the tolerance band of the growth target? Does the spec hash match? Is the system in a valid state? If any check fails, the action is rejected. The ledger records the rejection. No trade happens.

Question 13

Can the gate be bypassed?

Accepted Answer

Not through the runtime. The signal module returns a proposal. The gate function validates it. The engine connects them. There is no code path from signal to execution that skips the gate. The binary is compiled — there is no source code to edit on the user's machine.

Question 14

What does "discipline proven" mean?

Accepted Answer

Run botwir3 verify. It reads every entry in the ledger and checks: spec hash matches, action type is in the allowed set, magnitude is within constraints, result is within tolerance, math is correct. If every entry passes every check, discipline is proven. Not promised. Proven.

Question 15

What happens when the gate rejects a trade?

Accepted Answer

The rejection is recorded in the ledger with the reason — OUTSIDE_TOLERANCE, ABOVE_MAXIMUM, COOLDOWN_ACTIVE, etc. The bot continues to the next cycle. Rejections are normal. They prove the gate is working. A bot with zero rejections and a bot with many rejections can both be disciplined — discipline means following the rules, not never triggering them.

Question 16

What is HALT?

Accepted Answer

HALT is a terminal state. The bot stops executing. Causes: spec hash mismatch (config was modified), execution result doesn't match projection (something went wrong at the platform level), consecutive drift periods, risk limit breach, ledger write failure, or unknown position state. HALT protects. A halted bot with an intact mandate is better than a running bot with a broken one.

Question 17

What counts as a "build"?

Accepted Answer

Creating a new strategy or modifying an existing one in the builder. Each compile counts as one build. Downloading a previously compiled config does not count. Running, stopping, or restarting a bot does not count.

Question 18

What's the difference between the $129 bot and the Factory?

Accepted Answer

Same builder. Same guides. Same Opus. Same runtime. Same everything. The $129 is for people who want one bot and no subscription. Build it, download it, done. No account. No recurring charge. No relationship.  The Factory ($69/yr or $99 lifetime) is for people who want to keep building. It unlocks the same experience with 3 builds per month and the option to add Workshop bands for more. $99 lifetime means the door never closes.  Both paths deliver the same wired runtime. The difference is whether the door stays open after.

Question 19

Do Workshop bands stack on top of the Factory fee?

Accepted Answer

Yes. The Factory fee includes 3 builds per month. Workshop bands add more capacity: $19.99/mo for up to 10, $29.99/mo for up to 25, and so on. Cancel the band anytime and drop back to 3 builds per month. The Factory access never expires.

Question 20

What if the Workshop band gets cancelled?

Accepted Answer

Every bot already downloaded keeps running. Every config already compiled keeps working. The builder remains accessible at 3 builds per month on your Factory access. Nothing stops. Nothing expires. Nothing breaks. The band just controls how many new builds happen per month.

Question 21

Can someone build 100 bots in a month and then cancel?

Accepted Answer

Yes. All 100 bots run forever. The configs are local files. The runtime is a local binary. There is no kill switch. The subscription pays for builder access and build capacity, not for the right to run previously downloaded bots.

Question 22

How many platforms are supported?

Accepted Answer

52 setup guides across 15 categories: crypto (20 exchanges), equities, universal signals, prediction markets, auctions, collectibles, real estate, vehicles, forex, gaming, e-commerce, sports betting, NFTs, DeFi lending, and DeFi DEX. Each guide covers API setup, config, troubleshooting, and monitoring setup.

Question 23

Can the bot trade on platforms without a guide?

Accepted Answer

Yes. The adapter interface is documented. Any developer can write a custom adapter for any platform with an API. The guide just makes it easier. The bot doesn't know or care which adapter is connected — it proposes actions and the gate validates. The adapter translates.

Question 24

Do all platforms support full automation?

Accepted Answer

No. Some platforms (Coinbase, Alpaca, Binance, Hyperliquid, Betfair, Uniswap) support full automated execution. Others (Steam, Roblox, Zillow, CarGurus) operate in signal-only mode — the bot monitors and generates signals, the human executes manually. Each guide specifies which mode applies.

Question 25

Is botwir3 a financial advisor?

Accepted Answer

No. botwir3 sells software. The builder is a tool. The bot is a tool. The strategy is configured by the person using it. botwir3 does not provide financial advice of any kind.

Question 26

Is botwir3 a broker or exchange?

Accepted Answer

No. botwir3 does not hold funds, execute trades, custody assets, or intermediate between buyers and sellers. The bot runs on a local machine, connects to external platforms using locally-stored credentials, and executes through those platforms directly. botwir3 is a software company.

Question 27

Who is responsible for losses?

Accepted Answer

The person running the bot. botwir3 sells a wired runtime — configurable discipline, not profit guarantees. The gate validates actions against the configured band. It does not predict markets, guarantee outcomes, or prevent losses. A disciplined bot can still lose money if the strategy is wrong.

Question 28

Does "wired" mean "safe"?

Accepted Answer

No. Wired means the bot follows the rules it was given. If the rules are bad, the bot follows bad rules — disciplined. The gate prevents the bot from deviating from the strategy. It does not evaluate whether the strategy is good. That responsibility belongs to whoever configured it.