ibuildinpublic
Log inStart free
ibuildinpublic
Log inStart free
BuilderProductExperiences27Posts17

Experiences

Mark Rosario's experiences

Read what @markrosario has shared while building in public.

Lvl 8·Shipper
Lesson learnedNov 10

Approvals that expire are friction — so we took the longest-lived route

Every short-lived login is a future interruption. We set a standing rule: whenever a tool offers a choice, take the longest-lived approval it allows, and if the provider forces an expiry anyway, say so plainly instead of pretending it is permanent. This week that meant moving our coding agent onto a one-year setup tok…
2likescomments4Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
What workedNov 10

We built a bridge to another AI — and kept the keys on our side

We connected our Claude app to our own agent system through a custom bridge so work can pass both ways — status one way, tasks the other. The rule we set on day one: the other AI only ever gets the single task we hand it. It never touches our database, our files, or our memory. Every result it sends back gets checked…
2likescomments2Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
Lesson learnedNov 9

Our best-looking signal predicts falls — so we use it to exit, not enter

We paper-tested a pump.fun signal that graded beautifully on paper. When we studied entries honestly, buying at the signal won about 11% of the time and lost money — because the signal actually predicts a price fall after a creator dump, and you cannot short these tokens. So the trader stays disarmed for entries. The…
1likescomments5Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
What workedNov 9

A publish lane failed 151 times in a row — then the fix held

Our Trade Voltage scoreboard kept showing old numbers while the data underneath was fine. The publish lane itself had stalled on a stuck snapshot after more than 150 failed cycles in a row. Today a hand-run publish went clean, the next scheduled cycle went clean right behind it, and the board read back live at 2,739 t…
2likes1comments11Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
What workedNov 8

Expanding the pilot disk in place — 30 to 60GB, no downtime

Our Faqada 2.0 pilot disk hit 100% and broke its nightly sync two days in a row. Today we grew the root volume from 30 to 60GB in place — growpart and resize, no rebuild, no downtime. Final check: 58G total, 31G free, 47% used. The sync that could not run at all in the morning had room to breathe by evening. Sometimes…
2likescomments8Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
Lesson learnedNov 8

We stopped building new things until the base matched the pitch

Selling starts in days, so today we froze new building. The pitch in our 2:45 product video is simple — four core pieces, seven staff roles, six branches. Underneath it, skills and workflows had grown messy, with jobs doing other jobs' work. We mapped everything to one correct owner first. If the system does not live…
2likescomments4Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
What workedNov 7

A second brand, live in a day: logo locked, store verified, every button checked

Alongside the main build we launched a completely different brand this week — Bad Dolly, slippers and apparel for women. The logo decision was locked first, one primary version and the original ornate seal kept for premium packaging, no drifting between variants afterwards. Then the store went live and we checked it t…
4likes1comments21Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
Lesson learnedNov 7

Our strongest signals were our worst trades — the audit proved it

We let our practice auto-trader place its first small trades, then audited the results honestly. The strength score was backwards: the highest band, trades scored 80 and up, had zero wins in 41 trades. We pre-registered a redesign before touching the code, and the redesign failed its own test too. Version 2 backtested…
3likes1comments15Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
How to/GuideNov 6

Demo: One Task, End to End — Inside the Faqada Super Agent

Watch one real task run end to end inside Faqada Command. No cold calls. No hype. Just the daily work — handled, checked, and waiting for approval before anything goes out. Genome. Brain. Foundry. Command. Trainer, Prospector, Creator, Coach, Operators, Scout, Compliance Guard — one system, built to find what's…
2likescomments18Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
Lesson learnedNov 6

A full disk quietly broke our nightly sync

Our second agent instance syncs with the main one every night. Last night the sync failed halfway through an install because the disk was completely full — 29 gigs, almost nothing free — and seven sandboxes were left stale. The agent itself stayed live and kept answering, which is exactly why this kind of failure is d…
3likes1comments13Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
What workedNov 6

We verified the data feed before we trusted the engine

We connected a practice trading feed this week and refused to call it live on a setup screen. The token went in through a secure page, never chat, and then we made real calls: account read back correct, balance read back correct, and live candles for EUR/USD and gold were actually flowing. Only then did we say the fee…
2likes1comments7Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
What workedNov 5

The first skills video went live — and the free pack is real

On Nov 4 we launched a new series: short before/after demos of individual Faqada skills, each one using a clearly labeled fictional sample business. No invented results, no fake claims — the demo is the proof. The first video, on auditing an Instagram profile, was approved, published, and then read back live on 8 of 9…
2likes1comments8Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
Lesson learnedNov 5

A wrong duration read traveled for an hour before the real file corrected it

On Nov 4 we learned this the hard way on our investor video. An early probe said the delivered file was 4:12 long, and that number got repeated in briefs and status reports. The real file was 19:04. The correction existed for about an hour before it reached the person who needed it. So we made a new rule that same day…
2likes1comments6Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
What workedNov 4

A merged pull request is not proof — production is

On Trade Voltage today, PR #7 — live chart signal levels plus a TradeLocker availability flag — was merged and deployed, and then read back live on the production site at tradevoltage.com. That read-back is the only part that counts. We have been burned before by merged code that never reached users, and by deploys th…
4likes2comments22Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
Lesson learnedNov 4

The new homepage is live — just not at the root yet

We rebuilt the faqada.com homepage, got the approval, and pushed it. Then we checked the actual root domain — and it was still serving the old homepage. The new page was live at /home.html, verified there, but the routing fix to point the root at it is a separate step that has not happened yet. Lesson we keep relearni…
2likes1comments12Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
Lesson learnedNov 3

One master file. Every platform version is a crop, not a redesign.

On Nov 2 our cover rollout went wrong because each platform got its own version instead of one approved file, and alignment was eyeballed instead of measured against where the profile picture actually sits. Versions raced each other and a superseded design kept landing. Now the rule is locked: one master file, recorde…
3likescomments24Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
What failedNov 3

A relay that only works one way is not a relay yet

On Nov 1 we put BridgeLine live on Render so my brother Dean at FCI Schuylkill could get messages. Outbound was proven — a console test came back Delivered through the approved campaign, and Dean was provisioned with his own number. Inbound is still blocked, Error 11200, a token mismatch on the Render side. I am not c…
3likes1comments20Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
Lesson learnedNov 2

A legacy signup door let a stranger in — so we built a security branch

Today someone signed up for our system through a legacy register door we believed was already closed. We traced the signup, shut the account down on both backends, revoked its sessions, and closed the entrance, with a code fix prepared to delete the dead door for good. The lesson cost us nothing but attention, and we…
3likescomments26Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
What workedNov 2

We built the same agent two ways — and let the proof decide

Instead of betting the company on one rebuild, we built both. Version A is a fresh pilot on AWS: its voice layer passed proof today — ears transcribe with full confidence, and the cloned voice out measured 164 words a minute, inside our natural-pace gate. Its browser control opened a page and read it back. Version B i…
4likescomments22Impressions
Bookmark
Sign in to interact
Lvl 8·Shipper
Lesson learnedNov 1

Five failed reviews before the pass that let us ship

Our backend migration failed independent review five times in one night. Each round found something real: a workspace isolation hole, a fix that proved nothing, children stranded when a record was first stamped, a concurrency race, then a snapshot race on top of it. Each fix had to come with a test that failed on the…
2likescomments25Impressions
Bookmark
Sign in to interact
First pagePrevious page12