Northr - Client Journey & Loop Board

Internal operating board. Single authoritative view of where every client is. Human-confirmed facts sit ABOVE the agents (confirmed-facts), so a thing you explain once is not re-raised. Every item is a record or an alert; a person acts (owner tagged). Refreshes twice daily; this is the morning pass of 2 September. ⚠ Read the honest limit first: the spine underneath this board still carries a 30 August 06:40 stamp, day 3, so byte figures and stage rows are carried from that verification rather than re-measured, and the client tables are knowingly incomplete: the five builds of 31 August, the three sends of 1 September, one client reply and one refusal are all read off the build ledger and the send log, not off the spine. ⚠ The nightly rebuild started its run ten minutes before this pass, so it may be in flight; the spine had not changed as of this read. What IS measured today: the send log itself, now 55 rows and carrying every one of the three lost sends, and all eight queued follow-up hosts re-measured live from a clean scratch directory, every one answering. Read the day in one line: nothing new was built or sent, and the whole morning went on repairing the instrument that lost three sends - which is the right trade, because the fix was a root cause and not a backfill. The structured money book has been unchanged for ten days; the commission ledger has not been written in fifteen and its last content entry is dated 24 July, forty days ago; the written confirmation log has never once been used since June. ⚠ Every red item below has already been asked of its owner in writing, so the correct reading of this board is awaiting an answer, not nobody has asked. 🔴 27 accommodation pages still have no channel of any kind, and €3,105 to €3,305 still sits outside a clean company account.

READ FIRST - #1 BLOCKER: EVERY PAYMENT LINK THIS VENTURE HAS EVER MINTED STILL SITS IN AN ENTITY IVO HAS RULED OUT. ONE ITEM IS NOW TWO WORKING DAYS LATE AND IT IS THE ONLY ONE ON THIS BOARD WITH A PENALTY ATTACHED. 🔴 THE HARD ONE FIRST: THE OTHER ENTITY’S ACCOUNTS WERE DUE 31 AUGUST AND ARE STILL UNFILED THIS MORNING - TWO FULL WORKING DAYS LATE, AND THE PENALTY BANDS WIDEN WITH TIME RATHER THAN STAYING FLAT. Status active, last accounts made up to August 2024, next due 31 August, nothing filed. Filing was available online through the bank holiday, so nothing excuses the date. The penalty is automatic, it starts the moment the deadline passes and it escalates the longer it runs, and it is the only clock on this board that costs money by itself. This has nothing to do with Northr and everything to do with Ivo. ⚠ THE REPLACEMENT COMPANY’S WRITTEN ANSWER IS DUE TODAY: this is working day 5 of 5, and the chase call is TOMORROW, Thursday 3 September, with both references to hand. The proof of address went out 24 Aug 17:08 from the partner’s own address with her bank statement attached, was acknowledged the same evening with a reference to quote, and was forwarded to the new-companies team on 25 Aug 15:35 against a five-working-day response; Monday 31 August was a bank holiday the registry’s own hours exclude, which is why the calendar and the clock disagree. ✅ And the claim retired yesterday stays retired: the confirmation statement is CLEAR to August 2027 and must not reappear as overdue. Still ruled and unchanged: do NOT refile the replacement company until the address-format answer is in hand. Two fees have already been spent guessing; the stated reason was diagnostic rather than clerical, the registry could not verify the proposed usual-residential address as residential, and the practice position points the same way, since the operator is resident overseas and a non-UK usual-residential address is acceptable, never published, and dodges this check entirely. The money half is his own ruling and is unchanged: the shared entity behind that account has other partners who would have a claim on anything routed through it. Exposure is €350 confirmed, a further €200 unresolved between two destinations, and beneath them live recurring charges on older accounts running for months and never counted. Until a number is issued there is still no clean destination, no trustworthy read of the money at all, day 48, and a client who has actively asked to pay still cannot be given a link, day 48. Four actions, all his, and the first one is two working days overdue: file the accounts on the old entity today, because every day of delay widens an automatic penalty band; mint nothing further there; watch for today’s written answer and chase tomorrow rather than refiling; then get a live money read to size the exposure and settle what is owed to the other partners.

Won / care rows (nothing left, 28th window)

Care plans running since 1 Sept, none billable

€3.1-3.3k

Outside a clean account, money book day 10

~113

Built, unsent - 3 sends now on the clock

Open rows, 16 blockers, 1 filing 2 days LATE

Loop health - did the agents run

Nightly reconcile

⚠ AMBER, AND THE HONEST READING NEEDS A TIMESTAMP RATHER THAN A VERDICT: it fired at 10:46 BG this morning, TEN MINUTES BEFORE THIS PASS, so it may still be in flight. Last run 2026-09-02 ~10:46 BG, next fire 2026-09-03 ~06:37 BG. 🔴 What is certain is the state of the file at the moment this board read it: the spine still carries a 30 August 06:40 stamp, day 3, and no backup has been cut on 31 August, 1 September or today, where every previous day cut one at the moment of rebuild. ⚠ Today’s fire was also about four hours behind its own 06:37 slot, which is itself worth noticing on an agent whose two previous fires produced nothing. 🔴 The list of things it has not recorded is now two days’ work long: five demos live on 31 August, three demos SENT on 1 September, one client reply, one flat refusal, one full design revision, one revenue client’s site paused at the client’s own request and one row closed by the client. None of it is in the spine. All of it is in the build ledger and now in the send log, with byte checks, channels and verbatim quotes, so nothing was lost - but every downstream reader that trusts the spine is reading a file that ends before the busiest three days of the fortnight. A stale spine does not just age, it prints confident false statements. ⚠ Consequence: every byte figure, stage and day-count here is carried from 30 August and labelled as carried. ✅ Its 30 August output still stands, including its own instrument retirement and the corrected roster of 120. ⚠ Its honest limit also stands: there is no trustworthy read of the money at all, day 48. Next step: check this morning’s run for output before the evening pass. If the spine is still stamped 30 August tonight, three clean fires with nothing produced is a fault to open, not a wait to extend.

Reply capture

Still switched off, re-confirmed this run. Last ran 2026-06-29 ~21:22 BG, 65 days ago, and it has no next run at all because it is disabled rather than late. Known off-switch, not a fault, and the manual path is what carried the whole loop this morning. ✅✅ THE WATERMARK ITEM IS CLOSED BY EXECUTION, AND THIS TIME WITH A ROOT CAUSE RATHER THAN A BACKFILL. The send log moved 50 → 55 rows and all three lost sends of 1 September are in it, each sourced to the channel line read directly rather than to a recollection. ⚠ The cause is a new failure shape and it is the durable part: the logger REFUSED all three with „not in the client registry, so nothing is written“, because the registry had been generated on 24 August and did not know pages built after that date. A guard that exists to stop a send being written against an unknown page becomes a silent DROP the moment the registry behind it goes stale. Registry regenerated 225 → 234 rows. Anything built after the last regeneration is invisible to the clock until somebody regenerates it - that is the check to add, not another backfill. ✅ Two of the three needed no nudge at all: one replied the same day and one refused flatly and was logged closed lost. ⚠ All 55 rows remain unconfirmed, so nothing in the log has been checked against a client’s own words. ✅ The one-nudge cap is provably intact: zero nudge events have ever been written. 🔴 The big hole did not move: 27 accommodation pages still have no channel record of any kind, and the 17 demos sent on 22 Aug are still not posted in their own channels, so 44 live pages remain outside every loop-close check this system has.

Care-delivery audit

✅ GREEN on cadence: it ran on its weekly Monday slot and it is the only agent that has written anything into the spine this week. Ran Mon 2026-08-31 ~06:54 BG, next Mon 2026-09-07 ~06:48 BG, so it is within cadence with five days still to run. 🔴 Note the cadence against the calendar, because this is the week it bites: September’s three care plans started on the 1st and this agent does not look again until 7 September, so the entire first week of the new month is unaudited by design, on three rows that already missed August. ⚠ And a care row changed underneath it on 1 September without it seeing: the scooter account asked for its site to be paused and its phone removed, which is care work done well but is also a live client state this agent will not read until Monday. 🔴 Its finding is still the headline and it changed shape because the month ended: three paid care clients received nothing visible in August, so this is no longer a running day-count but a missed cycle on money already taken. Measured from the client channels directly rather than carried: a guest-house client prepaid to July 2027 whose channel has been silent 40 days against our own written promise of an August pack; a card subscriber whose last actual care action was 04 July and who was billed for a month in which nothing was delivered; and an annual client paid on 03 Aug whose channel was last touched on 04 Aug on money admin only, 29 days, with no care cycle ever run. ✅ It also wrote the counter-evidence itself, which is what makes it usable: five other care rows each have a dated August action, so the motion works where somebody picks it up. ⚠ And it surfaced a commission consequence nobody had connected: the 40% care commission on the silent prepaid year was logged on 24 July for a care year whose first month was never delivered, and under the ambassador rule that 40% is contingent on care actually being delivered. That is a live commission-gate breach, not a bookkeeping lag.

confirmed-facts = human ground truth above the agents; unchanged since 16 Aug, and the three-piles ruling it carries still governs how the unsent count is read. Authority order: confirmed facts, then money, then the acts log, then what was said in client channels, then the agents’ summary. 🔴 This is the morning pass, and the spine under it is THREE days old; the rebuild fired ten minutes before this pass and had not changed it as of this read. Treat every figure here as carried from 30 August unless it says otherwise, and treat the client tables as knowingly incomplete: the five demos built on 31 August, the three sends of 1 September, the client reply, the refusal and the paused care site are all listed from the build ledger and the send log, not from the spine. Where earlier rulings retired a claim, the claim stays retired: the psychologist’s build is PAID, the hotel-services care question is CLOSED, the September launch date belongs to the gym client, the whole coffee-client money question was closed by Ivo himself on 27 Aug and must not be re-raised in any shape, and the replacement company’s confirmation statement is NOT overdue and its address query is NOT sitting without a date. Take-downs on this board are client requests honoured, not defects.

Needs action - open items (owner tagged)

🔴💼 THE OTHER ENTITY’S ACCOUNTS WERE DUE 31 AUGUST AND ARE NOW TWO WORKING DAYS LATE. THIS IS STILL THE ONLY ITEM ON THE BOARD THAT COSTS MONEY BY ITSELF, AND IT COSTS MORE EVERY DAY IT SITS. The register reading is unchanged: status active, last accounts made up to August 2024, next due 31 August, nothing filed. The penalty is automatic - it applies the moment the date passes, it does not need anyone to chase it, and it escalates in bands the longer the delay runs, so the cost of this item is not flat, it steps up. Filing was available online right through the bank holiday, so there is no calendar excuse the way there was for the other company’s clock. ⚠ Stated plainly because it is easy to deprioritise: this has nothing to do with Northr and nothing to do with any client, which is exactly why it keeps sliding down the list, and it is the single item here with a defined, growing, unavoidable cash cost. Everything else on this board is opportunity cost. File it today. Ivo

✅⚠ NEW - THE CLOCK HAD LOST THREE SENDS AND THE CAUSE WAS A STALE REGISTRY, NOT A MISSED READ. FIXED THIS MORNING, AND THE FAILURE SHAPE IS THE PART WORTH KEEPING. All three demos sent on 1 September were absent from the send log. ✅ They are in it now, 50 → 55 rows, each sourced to the channel line read directly rather than to a recollection. ⚠ The cause: the logger REFUSED all three with „not in the client registry, so nothing is written“ - and that registry had been generated on 24 August and did not know any page built after it. The guard exists precisely to stop a send being written against an unknown page, and it fired correctly; the record still lost three sends, because the thing it checks against was the stale thing. Registry regenerated, 225 → 234 rows. 🔴 The durable consequence, and it is not fixed by this morning’s backfill: anything built after the last regeneration is invisible to the clock until somebody regenerates it, silently, with no error surfaced to a human. On a factory that shipped five pages in one day last week, that is a standing hole. What is owed is a check that regenerates the registry before the log is written, or fails loudly - not another backfill. ⚠ Recorded honestly against yesterday’s board, which read the same symptom as the 29 August watermark defect returning: it was not that defect, it was a different one wearing the same face. Ivo

📤 THREE DEMOS WENT OUT ON 1 SEPTEMBER AND THE MARKET ANSWERED TWICE THE SAME DAY - ONCE WITH A BRIEF AND ONCE WITH A FLAT NO. BOTH ANSWERS ARE WORTH MORE THAN THE SILENCE THIS BOARD USUALLY REPORTS. The rep sent the Sofia taekwondo club at 10:47:45, the Plovdiv motel at 10:47:36 and the Bozhurishte hotel at 19:43:44. The club left the unsent pile fourteen hours after it went live, the shortest build-to-send in this book against a seventy-six-day one the week before. ✅ At 14:15 the club’s owner answered, quoted by the rep: she trusts us on the design, wants it less plain than just the club colours, and wants visible movement. The first client reply the Bulgarian lane has had since 16 August, and it is a brief rather than a refusal. 🔴 At 21:17 the motel came back a flat refusal and the channel was archived the same minute - closed lost, logged, not chased. ✅ All three sends, the reply and the refusal are now on the clock; the Bozhurishte hotel is day 1 with its first nudge on 04 September, and the club was never a nudge candidate because it answered. 🔴 The fault that survives is its own item below: the revision built off that reply is live in front of the client and was never render-checked. ⚠ The two other pages of 31 August - the Rodopi hotel and the Sandanski family hotel, both core-ICP accommodation - are still live, unsent and unpriced, each with its own channel and the rep verified inside it. Sends and prices stay hers, sub-1k, no owner gate. ⚠ Read the day’s score honestly: three sent, one brief, one refusal, one silent. That is a working funnel, and it is the first one this board has been able to write down. Elena

🔴🔍 A DESIGN REVISION IS LIVE IN FRONT OF A CLIENT WHO ALREADY HAS THE LINK, AND ITS RENDERING CHECK NEVER RAN. THE ROLLBACK NEEDS THE SAME TOOL THAT FAILED. The Sofia club’s revision shipped this afternoon on the same address the rep already sent, so the owner sees the new version without being re-sent anything - which is the right call and is also why the risk is live rather than staged. Page is 1,032,028 bytes against 1,024,750 before. 🔴 What did not happen: the Linux workshop crashed immediately after the deploy and did not come back across six attempts, the built-in browser frame refuses these hosts, and the browser extension is not connected. So there is no measured contrast at 1440 or 390 in either language, no horizontal-scroll check, no language-button check at 390, no independent byte check from a clean scratch directory - the bytes were confirmed only by the deploy script itself, which is weaker evidence. ⚠ Rollback was impossible for the same reason: the previous version is on disk and deploying it needs the workshop. ✅ What IS verified and is not small: zero animated counters anywhere in the build, checked string by string - the client asked for movement on a page carrying her competition titles, and an animated number is exactly what the browser’s translate feature freezes, leaving a wrong figure stuck where a real title should be. Photographs, credits, licences and the honesty note are untouched and measured so: 364 of 364 visible text blocks identical to the previous version. ✅ The gap was said openly in the channel and messaged to Ivo rather than quietly carried. ⚠ The durable lesson, and it belongs in the canon: on a revision to an ALREADY SENT page, the rendering check goes BEFORE the deploy, on the local file - then a crashed tool stops the run instead of leaving an unchecked version in front of a client. Run the check against the live page the moment any frame works, and fix in place. Ivo

🔴⏰ EIGHT THREADS SIT IN AN APPROVED NUDGE QUEUE AND NOT ONE NUDGE HAS EVER FIRED. THE QUEUE IS DRAFTED, CHECKED AND WAITING ON ONE PERSON PRESSING SEND. The queue is eight, every one of them a genuine first touch: the hotel complex at day 8, two Свети Влас rows at day 12, three sends of 27 August at day 6 and the Несебър fight club at day 4. ✅ Every one of the eight hosts was re-measured live this morning from a clean scratch directory with compression defeated, and every one answers, so nobody is about to be nudged towards a dead page. ✅ The one-nudge cap is provably intact: zero nudge events have ever been written to the log, checked rather than asserted. 🔴 Confirmed this morning and it is the concrete cost: no cadence run happened on 1 September at all, so the fight club’s day-3, which the tool’s own clock put due that day, sat one day. Nothing else slipped, because every other row was already overdue or already held. ⚠ The 16 Pattaya rows are correctly OFF this queue - a written procedure dated 30 August assigns them all to Konnie with her own Thai script, a six-a-day cap and two touches then stop. What is real about those 16 is worse and simpler: they sit at day 11 with an owner who cannot act, because section 0 of that procedure is Ivo’s - the social login, 17 manual channel invites and the local payment line, all unmoved. The cap is intact, the drafts are ready, the hosts are live; what is missing is anyone pressing send. Ivo

🔴💵 AUGUST CLOSED WITH THREE PAID CARE CLIENTS RECEIVING NOTHING VISIBLE. THE MONTH IS OVER, SO THIS IS NO LONGER „DAY N“: IT IS A MISSED CYCLE ON MONEY ALREADY TAKEN, AND SEPTEMBER IS NOW RUNNING ON TOP OF IT. Written by Monday’s care audit, measured from the client channels rather than carried. The Kiten guest house: care prepaid to July 2027, channel silent since 24 July, 40 days, and our own 27 June message promised her in writing that the next pack comes at the beginning of August. August came and went and the package never came, and it is the one gap on this board the client can check for herself. The card subscriber: billed monthly, last message in her channel was the double-collect escalation, and her last actual care action was 04 July - a monthly-billed client charged for a month in which nothing was delivered. The hotel-services client: paid a full year on 03 Aug, channel last touched 04 Aug on money admin only, 29 days, and no care cycle has ever run on the client who paid furthest ahead. ✅ Not in this item, each with a dated August action: the restaurant (menu prices, 05 Aug), the hotel in Сливен (own-domain go-live, 08 Aug), the scooter account (three assets published, 24 Aug), the gym (a hall banner, 29 Aug), the coffee client (address and hours, 03 Aug). 🔴 The commission consequence, and it is Ivo’s: the 40% care commission on the silent prepaid year was logged on 24 July for a care year whose first month was never delivered, and the ambassador rule makes that 40% contingent on delivery. A live commission-gate breach, not a bookkeeping lag. Elena / Ivo

🔴⚖ A FINISHED, TWICE-REBUILT, LIVE PAGE IS HELD ON ONE READ THAT ONLY IVO CAN DO - DAY 4, AND TWO BUILD SESSIONS WERE SPENT BEHIND THE HOLD. The taekwondo club in Дупница is live and byte-verified at 578,895 bytes. Ivo’s own words in that channel at 16:10 on 29 Aug: do not send yet - research surfaced a 2022 press item naming the club’s chairman and senior coach, unverified, with no known legal outcome either way. The gate is his and it is the right call. What makes it an item is the cost already sunk behind it: after the hold was posted, the same evening ran a full design upgrade at 17:16 and a second press sweep and hero rebuild at 17:43. Two sessions and a photo hunt on a page nobody may send, while the rep who asked for it at 14:24 is still waiting on one word into a fourth day - and she has since asked for and received five more demos and sent three of them, so the queue moved on around it. ✅ Everything else on the row is clean: the has-site pre-check is confirmed, the three photographs with recognisable children are not on the site (verified by name against the served page, zero hits), medal-winners are deliberately unnamed, nothing sent, no price, no domain. One read closes it either way: send, or take it down. Ivo

💵 THE MONEY OUTAGE IS NOW DAY 48, AND THE THREE CARE PLANS THAT STARTED ON 1 SEPTEMBER ARE RUNNING, BEING DELIVERED AGAINST, AND STILL CANNOT BE BILLED. The music studio at €24 a month - agreed, confirmed, delivered on her own domain since 21 Aug, nothing at all to chase, and no rail to charge it on. The German guest house - 49 recorded against 40 offered verbally by the rep, unresolved since 16 Aug and now day 17, and the client has been asking for a payment link she cannot be given for 48 days. The gym client at €19 a month - her own decision that the plan begins in September, and never once billed; a start nobody bills is the same loss whoever decided the date. Re-confirmed this run: no working connection to the payments platform, and no such tool is present in the session at all. 🔴 The first month of each of these three is now two days in and is being delivered against, so the loss is accruing rather than approaching. ⚠ Note the direction of travel on the German row: her contact form was fixed on 28 Aug and her legal-form blocker cleared on 30 Aug, so delivery keeps accelerating on a plan whose price has never been settled. A plan that starts without a confirmed figure and a rail loses its first month, and that month is now being spent. Ivo

🇩🇪✅🔴 NEW - THE GERMAN GUEST HOUSE’S GO-LIVE GATE CAME OFF THE CLIENT AND ONTO US, AND THAT TURNS A PATIENT ROW INTO A COUNTDOWN. ONE DOMAIN PICK IS ALL THAT STANDS BETWEEN A PAID BUILD AND A LIVE SITE. ✅ The client settled it herself in a call the rep recorded on 30 Aug 17:31: she will not register a firm and will pay as a private person, because registering would bring a company filing and a premises inspection she explicitly wants to avoid. So the line this board has carried since 16 Aug - „go-live is gated on her accountant naming the legal form“ - is WRONG from 30 August onward and must not be repeated. 🔴 What is left is entirely ours: pick a domain and register it. Two constraints follow from her decision and both are naming constraints, not legal advice: the wording should read as a holiday home rather than a guest house, and the words „guest house“ in any language must stay out of the name and the domain, though the search layer inside the code may keep them. ✅ She has already named her own preference, built on the family name, so this is not even a shortlist exercise. ⚠ The clock is real and it tightened overnight: the build was paid 16 days ago, nothing is registered, and the Rhine festival that sells the town out falls in the second week of September, now roughly eight days away. On the precedent of the hotel that went live on its own domain in one afternoon for about ten dollars, this is a sub-twenty-dollar decision holding a €600 client. The 40-versus-49 price is untouched by any of this and stays open separately. Ivo

#2 BLOCKER - THE PARTNER COMMISSION CUT FROM 30% TO 20% IS CORRECT ON DISK AND STILL WRONG ON THE WIRE, DAY 13. Carried from the 30 August wire measurement: the partner page serves 200 at 20,037 bytes, reading 30% four times and 20% once - byte-identical across six consecutive measurements from 24 to 30 August, so nothing has shipped in thirteen days, and it is the longest-running one-tap item on the board. The local file has said 20% since 20 Aug at 04:41. The partner’s €120 on the German guest-house chain stays gated on that one deploy while the page still promises her the old rate. A commission rate is money, so no agent ships it: this is a one-tap yes from Ivo, not a stall. Ivo

🔴 TWO DEMOS THAT CLIENTS WERE ALREADY SENT ARE SERVING NOT FOUND - DAY 17 AND DAY 13. STILL THE CHEAPEST OPEN ITEM ON THE BOARD, AND ONE OF THEM HAS NOW COST A THREAD. Both returned Not Found at 766 bytes on three of three tries this morning, re-measured rather than carried, and nothing has been redeployed. One was sent on 16 Aug, so a real recipient has had a dead link for seventeen days - and that thread passed its last touch and closes as no-answer, which means the silence measured our own dead page rather than their disinterest. The other was re-sent on 20 Aug to a host that was already dead. Neither is a take-down; both are unintended. The send engine correctly held both nudges again this morning, so the guard works and the redeploy simply is not being done - one command each, with a documented fallback if the first tool reports the project missing. ⚠ The asymmetry sharpened again: the take-down machinery has run flawlessly four times in three days, each with snapshot, delete, Not Found and a neighbour check, while these two redeploys, which are strictly simpler, have not run in seventeen days. The capability is emphatically not the constraint. Ivo

🔴 A RETIRED ADDRESS IS STILL SERVING A DIFFERENT BUSINESS TO ANYONE THE REP SENT - DAY 19. Carried: the old address answers 200 at 1,316,093 bytes, byte-identical since 14 Aug, while the correct page serves beside it at 1,513,920. „Which link did she send“ is day 11 unanswered and she has posted in a further six channels since, five of them on 31 August. ✅ Partial progress worth restating: the send engine reversed its hold and queued the follow-up carrying the correct address, which repairs the bad case and is an ordinary nudge in the good one - so the question no longer blocks the follow-up, only the stranger’s page is still live. Retiring the old address ends it without her. Ivo

💵🔴 THE MONEY BOOK STILL UNDERSTATES A SETTLED CLIENT BY €50, AND THE FILE HAS NOT MOVED IN TEN DAYS. The rep closed the coffee client in writing at 28 Aug 16:49: „the annual care runs from August, the build is paid in full“. So the build is €150 collected in full. The structured money book still books €100 on that row and its own note still reads „a further 50 not recorded as received“. 26 rows, last written 23 Aug, day 10. ⚠ Note the direction deliberately: the coffee-shop item below is the mismatch where the book claims money nobody confirms; this is the mismatch where money is confirmed and the book does not claim it. Same instrument, both failure modes live at once, on two clients, in the same file. ⚠ Her commission on the €150 annual care, 40% = €60, and on the €150 build are both unbooked. One line in a file. Ivo

💵🔴 MONEY MISMATCH - THE COFFEE SHOP’S FIRST INSTALMENT, DAY 11 AND UNMOVED. Ivo told that channel on 20 Aug that the first €100 instalment is not yet charged. The money book records €100 RECEIVED on 15 Aug, in cash, collected by the rep, sourced to her own words. He re-asked her on 25, 26, 27 and 28 Aug in the daily money message and she has not answered - and note she requested five demos across 30 and 31 Aug, so it is not silence in general. Either the money book overstates collections by €100 or the owner does not know a rep is holding a paid instalment. Book it or strike it. ⚠ Read alongside the €50 item above, which is the same instrument failing in the opposite direction. Ivo / Elena

💵🔴 THE NAMED DOUBLE-COLLECT STILL CANNOT BE READ, AND IT IS MONEY AND POSSIBLY A REFUND. Unchanged: the rep stated on 24 Aug that this client’s care runs on a card while the client pays only in cash - the first direct human ownership claim on the unidentified monthly subscription in 48 flagged runs, and it post-dates the June confirmed fact that left the question explicitly open, so it is the answer arriving rather than a re-flag. Two independent checks make it consistent: the gym client’s €19 is recorded as never billed, which cannot be true of a customer auto-charging monthly, and this client’s own June records name her. ⚠ The month-end audit sharpens it: she was billed for August and her last care action was 04 July, so the charge and the delivery are now both in question on the same row. Action is one sitting: read the customer behind that subscription, and if it is her, decide cancel and whether anything goes back. Blocked in practice by the money read being on day 48, and note that the September charge on that card falls inside the coming week. Ivo

💵🔴 ONE CLIENT CARRIES TWO PRICES FOUR HOURS APART AND THE FLOOR IS STILL UNRULED. The guest-house channel was seeded on 24 Aug at 250 build plus 19 a month; the rep posted in the same channel at 20:04 that she had sent 100 for the build plus 15 a month, or 120 for the year. Unchanged: no reply from the prospect, no ruling. Five live numbers still sit in front of real prospects: 600/49, 250/19, 200/15, 100/15, and an effective 12.50 a month from the coffee client’s prepaid year, and the annual undercuts the monthly by a third. ✅ The one piece of movement stands from 29 Aug: the Несебър fight club went out at 14:51 and Ivo logged the terms in-channel twenty minutes later at 250 build plus 19 a month, matching the seed rather than undercutting it - the first send since 24 Aug that a later run can reconcile against a number, after five unpriced sends on 27 Aug. One priced send does not settle the floor. The sends are sub-1k and stay hers; what is Ivo’s is the ruling. Ivo

🔴📦 27 LIVE ACCOMMODATION PAGES STILL HAVE NO CLIENT-CHANNEL RECORD OF ANY KIND - DAY 9. Not re-sampled and the reason is sound: the 25 Aug sampling of four of the slugs across all message content returned zero hits of any kind, and every channel created since belongs to a new build rather than to one of these. The consequence is the point: no link is posted anywhere a human reads, no „no link in the channel“ test can fire, and if any of these 27 businesses is contacted there is nowhere for the reply to land. It is also the direct reason none of them can be sent. ⚠ The contrast is now visible seven times over: the two builds of 29 Aug and all five of 31 Aug got a channel at creation, the link posted and read back, and the rep verified as a member on each. The practice works; these 27 predate it. Largest instance ever recorded. Ivo

📤⚠ THE 17 SENDS OF 22 AUGUST ARE AT DAY 11 WITH NO CHANNEL RECORD, NO CONFIRMED CLOCK AND AN OWNER WHO CANNOT ACT. ✅ The clock defect is closed again this morning and with a root cause this time: the log holds 55 rows and every open thread that is in it has a cadence clock. What survives is not fixed by a backfill: every one of the 55 rows is still unconfirmed, not one of the 17 client channels carries the send, and the rep is absent from twelve of them. ✅ The owner reading is unchanged and it changes the owner rather than the urgency: 16 of these are no longer on the Bulgarian nudge queue at all. The written procedure of 30 August hands them to Konnie, in Thai, two touches then stop - which is right, because a Bulgarian nudge to a Pattaya cafe was never the correct follow-up. The seventeenth, a stone park, is explicitly not hers because the animal-attraction gate is unruled, so it is held with Ivo. 🔴 So the blocker is a handover, not a cadence: section 0 of that procedure is entirely Ivo’s - the social login, 17 manual channel invites, the local payment line - and until it is done, sixteen threads have an owner who is not equipped to touch them. ⚠ Minor artefact recorded so nobody reads it as truth: the logger derives the link from the slug, which is wrong for two now-closed rows. Ivo

💵🔴 THE REFERRAL RAIL CARRIES REAL VOLUME AT A RATE THAT HAS NEVER BEEN RULED. Unmoved for a fourth window; the referrals channel has been silent since 23 Aug. (a) One overseas rep’s code: 15 requests, 1 carried the code, 14 did not - 93% untraceable, because he enters through the bare intake page rather than his own link; the code cannot be patched through the interface, so the correction sits in the request note and nothing was attributed automatically. (b) A second Bulgarian code went live on 23 Aug at 30%, with Ivo’s own words that the 30 is not recorded anywhere and is the whole build fund, above the 20% partner tier and not derivable by analogy. (c) The first Bulgarian code has been live since 21 Aug and is still unruled. Three numbers in one sitting, and it is money. Ivo

🔴 THE REP CANNOT SEE ABOUT 19 CHANNELS, TWELVE OF WHICH HOLD OUTREACH THAT HAS ALREADY BEEN SENT AND IS NOW PAST ITS LAST TOUCH. Carried, and the gap did NOT grow. The two channels created on 29 Aug and all five created on 31 Aug were member-listed directly: two members each, the rep IN on every one, so the create-time invite path has now worked seven consecutive times. Two more of the original set went moot when the rep archived their channels herself, so the honest carried figure is about 19, stated as carried. Root cause on the old ones is unchanged and it is a missing capability rather than forgetfulness: there is no way to add a member to an EXISTING channel through the interface we use. The remainder are manual one-clicks; the recurrence needs a tool. Ivo

🔴⏳ SIX ROWS ARE PAST THEIR LAST TOUCH OR PAST ANSWERING, AND NONE OF THEM IS A QUEUE ROW - EACH ONE NEEDS A DECISION RATHER THAN A NUDGE. Under the standing cadence a sent demo gets nudges at +2, +5 and +10 days and is then parked; these six are past that line, and on the record most of them had one message in their whole life. ⚠ Three of them carry a defect that makes closing them the wrong lesson. The restaurant row is day 17, live and byte-identical since 17 August at 41,880 bytes, but ships no click-to-call, no images and no footer badge - a build gate under the 07 August no-CTA rule, so it never had a way to answer. The guest-house row is day 17 and the second dead-link row is day 13, both serving Not Found at 766 bytes on three of three tries this morning, so their silence measures our own dead pages and not their disinterest. The financial-services row is day 16 and is owed a commercial answer rather than a „did you see the site“. The re-approach row is day 9 and already spent its single nudge back in June, so touching it now is contact number four. 🔴 And two rows are simply stuck OPEN in the wrong state: they replied 77 and 78 days ago and no outcome was ever written against either, so they inflate the open count and nothing will ever close them by itself. The binary is unchanged and is now retrospective on three of the six: patch and spend the last touch, or accept that they closed against our own defects. The two ancient replies just need an outcome typed. Ivo

✅⏸ A PAYING CARE CLIENT ASKED FOR HIS SITE TO BE PAUSED AND HIS PHONE TAKEN OFF ON 1 SEPTEMBER, AND IT WAS DONE THE SAME RUN AND MEASURED RATHER THAN CLAIMED. No action asked; recorded because it is what a care plan is supposed to look like. The rep relayed the scooter client at 13:38: pause the site and remove the number, he has to be away. ✅ Read as a pause rather than a take-down, and the reasoning is in the request itself - if the site came down entirely, „remove the number“ would mean nothing. So all three of his addresses now serve one short page in his own colours with his own mark, saying the service is not taking bookings for now, in both languages. ✅ The phone removal was counted, not asserted: the old page carried his number in 12 places, the live page carries it 0 times, checked by searching the downloaded bytes. No-index was added so the temporary page does not get indexed in place of the real one. ✅ Nothing was deleted - the full previous page is retained under a dated backup and restoring it is one command. All three hosts verified at 94,554 bytes each, equal to the local file. ⚠ One thing flagged to him and it is his, not ours: his public business listing still publishes the same phone number, so a caller who searches will still find it. Marking the business temporarily closed there is the owner’s own action. Elena

📥⚠ A CLIENT’S CONTENT CORRECTION IS LOGGED, CORRECTLY NOT SHIPPED, AND BLOCKED ON A FOLDER THAT IS NOT A SHARED ONE - DAY 5. Model 2 already matches the owner exactly; model 1 needs four corrections - built area 99 to 99.5, house area 82 to 86.5, bedrooms and bathrooms 2+2 to 2+1, terrace 26.5 to 28.0. The digits were deliberately not shipped alone, and the reason is a standing rule rather than an excuse: the figures and the floor-plan drawing they are read off are ONE claim, so shipping corrected text against an uncorrected plan would put a page in front of buyers whose numbers and drawing disagree. The replacement plan images sit in a local downloads folder that is not a shared location - the fix is to drop them in the exchange folder and it becomes a ten-minute edit. ⚠ Recorded as care work owed, not a money item: this row is free by decision and there is no ask outstanding on it. Page carried at 1,557,573 bytes. Ivo

THE CLIENT-CONFIRMATION FLOW HAS NEVER FIRED ONCE, AND IT IS THE CONTROL THAT IS SUPPOSED TO PRECEDE EVERY COMMISSION. SEVEN PAYMENTS. The confirmation log is still 221 bytes with a June timestamp and has never been used. Behind it sit seven rep-collected payments: €100, €100, an annual care €150 confirmed paid by the collector but with no named holder, €150, €120, €35 and the coffee client’s build confirmed collected in full. No remittance of the company’s 60% has ever been reconciled, and the commission ledger is untouched since 18 Aug, fifteen days. ⚠ Tenth consecutive day with the money book unmoved, so the amount sitting behind zero confirmations is unchanged only because nothing was collected, not because anything was reconciled. ⚠ The month-end audit gives this item its sharpest example yet: a 40% care commission was booked in July on a care year whose first month was never delivered, and an independent client confirmation is exactly the control that would have caught it. The live 49-versus-40 contradiction on the German guest house is the same failure mode from the price side. ⚠ A third person is now collecting in the field with no confirmation instrument behind her. Ivo / Elena

💵 UNRULED AND UNBOOKED COMMISSION LEGS - THE MONEY BOOK HAS NOT MOVED SINCE 23 AUG, DAY 10. (a) The hotel-services annual care €200 - 40% to the rep, or excluded as an owner-collected account? Unruled since 04 Aug. (b) The restaurant’s annual care €150 - unbooked. (c) The coffee shop’s €100 - unbooked. (d) The coffee client carries two legs: the annual care €150 with 40% = €60 unbooked, and his build €150, confirmed collected in full, also unbooked. (e) The music-studio €180 and German guest-house €180 chains are ruled but unpaid, and with the studio delivered on her own domain since 21 Aug the last reason to hold hers is gone. (f) The German deal has three claimants, two with unproven attribution. 🔴 (g) NEW from the month-end audit, and it runs the other way: the ~€48 care commission on the Kiten guest house was booked on 24 July against a year whose first month was never delivered. All of it his. Ivo

💵 CARE REVENUE NOT STARTED ON CLIENTS WHO HAVE PAID FOR A BUILD. The psychologist: build €300 PAID, live on her own domain 34 days, care €29 a month never once billed - his own client, his call, and the September campaign delivered into that unbilled plan is for the month now running. The German guest house: 49 recorded against 40 offered, day 17, nothing mintable until she says which number closed, and her go-live is now blocked on our domain pick rather than on her. The hotel in Сливен: the monthly never started after the prepaid six. The Несебър workshop: the total build price and the monthly fee are recorded NOWHERE on a row that has taken a €100 deposit. 🔴 The gym client belongs in this item: her €19 has never once been billed, her plan started on 1 September, and although the September date is her own decision, a start nobody bills is the same loss whoever chose the date. ✅ The coffee client is out of this item permanently - his care was prepaid €150 for a full year and the collector has confirmed it. Ivo

💵 €19 A MONTH NOW PROMISES TEN SOCIAL ITEMS A MONTH, AND €19 IS THE STANDARD CARE TIER. Unchanged: the 24 Aug revision to the financial-services offer bundles ten social items - posts, short videos, photos - into the €19 plan. The pack spawned for the psychologist the same day is eight posts, a five-frame carousel and three video cuts, a full session of work. ⚠ And on 29 Aug a 2.59 by 1.74 metre print banner was delivered to the gym client, another full session of design work against a €19 tier that has never once been billed on that account. At €19 delivered monthly this is almost certainly below cost, and because €19 is the standard tier it sets a precedent for every care client. The German channel sells at 600 and 49. ⚠ Read it beside the month-end audit: the promise is being raised on the tier that just failed to deliver at all on three rows. Decide deliberately whether ten items is the standard promise or a one-client sweetener. Ivo

🌐 THE FINANCIAL-SERVICES SITE IS DAY 10 LIVE ON THE CLIENT’S OWN BRANDED DOMAIN WITH NO CONTACT PATH AT ALL, AND ITS THREAD IS PAST ITS LAST TOUCH. Carried and byte-stable for a sixth consecutive measurement at 74,332 bytes, content unchanged since 24 Aug: zero call links, zero mail links, „coming soon“ six times, seven unfilled tokens, the company number nowhere, and a contact form with no action that reaches nobody. The go-live decision is recorded, not re-litigated - the deploy itself was clean and byte-verified. What is needed is one message to the client: which positioning is current, because the page argues a leasing angle her own three documents do not support, and the licence wording in writing. Row is unpaid and unpriced. ⚠ The send engine held its nudge again this morning on exactly this ground: the row is owed a commercial answer, not a „did you see the site“. 🔴 It is day 16 since the send with no touch spent, so on the record it closes as no-answer having had one message in its whole life - one of three rows closing this way against our own defects rather than against a market answer. Ivo / the client

🔄✅ THE REOPENED PIZZA ROW IS LIVE AGAIN AND STILL HAS NO CLIENT SURFACE ON DAY 4 - THE BLOCK IS ONE BUTTON. Carried: the owner who refused on 25 Aug contacted the rep at 11:17 on 30 Aug asking for the demo again, and it was restored and byte-verified the same run at 200 / 1,864,663 bytes, hash identical both to local and to the pre-take-down hash recorded on 25 Aug, at the same address she already sent - so the owner sees the exact page, not a rebuild. That was one command only because the take-down deleted the objects but deliberately kept the project name. 🔴 The block is that her channel is archived and no tool here can un-archive it; that is a single click in the client-channels tool and it is Ivo’s, unmoved for four days. Until then this row has no surface to record into, on the only row on the board where a person is actively waiting. ⚠ One question must be asked before anything is sent, and it was assumed at build time rather than confirmed: the page is a deliberate 2-in-1 covering both Сезам locations and same-owner was never verified. If the caller runs only one of them, the page shows them a shop that is not theirs. Price and the send back stay the rep’s, sub-1k. Ivo un-archives / Elena sends

🔄 ONE OF OUR OWN MARKETING POSTS IS LIVE TWICE AND CANNOT BE FIXED WHERE IT WAS MADE. Unchanged. The same post published twice on 18 August, byte-identical, same media, both live on the professional network. Created fifteen hours apart, so a double-create rather than a scheduler misfire. Because both are already live, the scheduling tool cannot clean it up: one has to be deleted on the network itself. Small, but it is a live public artefact on Ivo’s own brand. Ivo

⚠ TWO DO-NOT-SEND PAGES ARE STILL UNPATCHED, DAY 14 - AND THE GATE HELD AGAIN. Both animate a factual rating and review count with no translate guard, which is two known traps compounded. ✅ Checked name-by-name against the recent approval queues: neither appears in any of them. They stay live, unpatched and unsendable until the numbers are static markup. Ivo

📌 SMALL OPEN ASKS THAT BELONG TO THE REP, DELIBERATELY NOT ESCALATED. Whose the disputed reservations number is, which link she actually sent for the Свети Влас hotel, the internally contradictory intended price on the Велинград row, currency on two cash collections, and whether a third client’s verbatim quote may be touched. ✅ Four items have left this list since 28 Aug, all closed by the rep herself or by execution: the coffee client’s build-50 and care-start-month questions, archiving one channel, and the refused Карнобат row, whose demo was taken down under standing practice. 📥 Seven questions for the Дупница club row remain unchaseable until the send gate at the top is ruled. 📥 The 31 August builds carry open client questions that only she can ask - a facade photograph and a street-number conflict on the Sandanski hotel, prices and an e-mail on two of the others, age groups and photo consent on the Sofia club, and a decision on the Nesebar hotel that already has a live site, which is a rebuild pitch or a drop, not a greenfield demo. ✅ She closed three of her own loops on 1 September without being asked: the children’s-party row was ended by the client in writing and she archived the channel herself thirty seconds later, she relayed the scooter client’s pause request the same afternoon, and she archived the Plovdiv motel channel within the minute of its refusal. Elena

🔴 TWO INBOUND REQUESTS FROM 22 AUGUST ARE STILL UNBUILT - DAY 11. The referral-attributed one is blocked on a business name, not on us - Ivo asked on 23 Aug whether the word in the reference is the business name, got zero matches when he searched, and said the page gets made the moment the name is given. Client-side information gap, not a build backlog. The second, from a map link with no code, has no such excuse. 🔴 And the contrast keeps widening: five pages were requested and shipped live on 31 August and three of them went out on 1 September, while these two inbound requests, which are people who came to us, sat untouched into an eleventh day. Ivo

✅ PROCESS - TWO RECENT CORRECTIONS CAME FROM THE SAME MISTAKE MADE TWICE: A CALENDAR WAS USED WHERE A DIFFERENT CLOCK APPLIED. No action asked; recorded because it will recur, and because this morning’s stale-registry finding is a third instance of the same family - an instrument trusted without checking what it was measuring against. The registry promised an answer in five working days and this board counted calendar days, which turned working day 3 into „day 7 and overdue“, and it did so on a Monday that is a bank holiday, so the count was wrong twice over in the same sentence. The second correction is the same shape from the other end: a filing this board called overdue since 17 August was in fact clear until August 2027, because a due date was read off the wrong year. ⚠ Both were only caught by opening the register and the acknowledgement email and reading them. The durable form is worth keeping: a deadline is not a number of days, it is a rule plus a calendar, and neither is derivable from the other. ✅ The right consequence has already been taken - the ruling not to refile until the written answer arrives is unchanged, and being three days early rather than seven days late does not make refiling any more sensible. Ivo

⚠ THE NIGHTLY REBUILD HAS FIRED THREE TIMES SINCE ITS LAST OUTPUT - AND TODAY’S FIRE STARTED TEN MINUTES BEFORE THIS PASS, SO IT IS AMBER RATHER THAN RED UNTIL TONIGHT. Last run 10:46 BG today, about four hours behind its own 06:37 slot; next fire 06:37 tomorrow. The spine had not changed at the moment this board read it and still carries a 30 August 06:40 stamp, day 3, and no backup has been cut on 31 August, 1 September or today, where every previous day cut one at the moment of rebuild. 🔴 The cost is not hypothetical: five demos went live on 31 August and three went out on 1 September, and none of it reached the spine, so a board reading only the spine would report a quiet week on the factory’s busiest three days in a fortnight. A stale instrument does not merely age its numbers, it prints confident false statements. ⚠ A file-modified time would have called this agent healthy on all three days, because other agents write into the same file. A run is not a result, and neither a last-run timestamp nor a file timestamp is evidence that anything was produced. ✅ The correct handling is what this board has done: every carried figure is labelled as carried, and the missing rows are named from the build ledger and the send log instead. The test is tonight’s pass: if the spine is still stamped 30 August, that is three clean fires with no output and it stops being a wait and becomes a fault to open. Ivo

⚠ PROCESS - A DAILY MESSAGE HAS BEEN NAMING THE WRONG PERSON AS A COMMISSION CLAIMANT FOR SEVERAL RUNS, AGAINST A CORRECTION SITTING IN THE SAME FILE. Caught and corrected in writing on 1 September; no money moved on it. The three claimants on the German guest-house deal are the rep, a partner, and the introducer whose own free site sits in the portfolio - not the fourth name the daily message kept printing, which belonged to someone added to a group chat by accident at the outset and whose name then stuck to the role. Ivo settled the identity on 16 August, in the same file, roughly 1,300 lines above the line that kept getting it wrong. ⚠ The lesson is the one this venture keeps re-learning: a stale claim outlives its fix unless the fix is written where the claim is read. ✅ The money shape is unchanged by the correction - one pool, divided rather than stacked, with the company keeping €420 of the build and €29.40 a month of the care. Ivo

⚠ SITE HEALTH HAS NOT PRODUCED A RUN TODAY - ITS NEWEST OUTPUT IS STILL DATED 1 SEPTEMBER 07:01, AND THAT IS A SECOND INSTRUMENT QUIET ON THE SAME MORNING AS THE SPINE. The last reading stands and it was clean: 100 live sites, 85 OK, 15 warnings, 0 failures, the warnings resolving to one broken shared image hitting eight internal pages from a single root cause, plus six unarmed redirects. ✅ The estate is not unmeasured today, it is just measured by a different instrument: the follow-up run re-curled all eight queued hosts live this morning from a clean scratch directory, and every one answered, and the two known dead demos were re-measured Not Found on three of three tries each. ⚠ Note what the health loop does and does not cover: it proves the estate is serving, it does not prove any individual page is the right page, which is why the wrong-business address and the two dead sent demos are tracked separately above and are never visible here. Check whether it produced no file or did not run at all, alongside the spine question - two quiet instruments on one morning is a pattern worth one look, not two. Ivo

✅ AN INSTRUMENT THIS BOARD PRINTED FROM FOR FIVE RUNS WAS PRODUCING FALSE NEGATIVES, AND IT IS RETIRED. No action: this is a correction to numbers Ivo has been reading. The check was: list the client channels, see that the newest one returned is still the agency channel from 27 Aug, conclude nothing was created after it. That same query returned the same answer while two channels created on 29 Aug both existed - they surfaced only when searched by name. The reason is structural and worth keeping: the search is relevance-ranked, not recency-ranked, so it cannot produce negative evidence. Consequences, stated once: the roster is 120, not 118, and two carried items - the missing channel for a client at closing, and the rep’s membership gap - were both being measured against a stale floor. ✅ Neither gap actually grew. The durable half is the method: a search that ranks by relevance can confirm a thing exists and can never prove one does not. It is the same lesson as the note above it, from a different instrument. Ivo

⚖ WHAT ACTUALLY MOVES A COLD SEND IS AN OPEN QUESTION WITH EVIDENCE ON BOTH SIDES. Stated once, no action asked. Against the cold motion: the car dealer built in June and sent in August, a sixty-day gap, came back „they do not know who ordered it“, angrily; the hair salon refused „we have a website“ because the owner counts a second social page as one; and the hair-and-beauty centre - the strongest has-site pitch the factory has ever built, sent after only a seven-day lag - was hung up on at day 3, which is the important correction: quality and freshness were both present and it changed nothing. For the motion: the child psychologist, briefed 09:11, second revision by 09:44, sent 13:45, answered 23:55 with thanks and a promise to call back - a fourteen-hour build-to-send and the only warm answer in the book since 16 August; and the pizza owner who refused on 25 Aug and came back on 30 Aug of his own accord. Read together, the variable that tracks the outcome is not lag and not build quality but whether a person with a relationship carries the send. Four Bulgarian refusals in four days against one warm deferral and one reopen. It bears on the ~113 rows behind them - and 1 September added the sharpest evidence yet: three sends produced one same-day brief, one same-day flat refusal and one silence, so the market answers fast in both directions when somebody actually asks. Ivo

PROCESS - A REAL CLIENT AT CLOSING STILL HAS NO CHANNEL. Re-confirmed absent from the corrected 120-channel roster, so the finding survives the instrument being retired above. It is the longest-standing tracking gap in the book and it is the owner’s action - agents must not create channels from this file. ⚠ A refusal that archives its own channel has the same shape from the other end, and the reopened pizza row is now the proof of the cost: recent refusals archived their channels within thirty seconds of the instruction, so when one of those owners came back there was nowhere to record it. Worth noting as a shape, not as a complaint. Ivo

Revenue base - won / care

Client	Stage	Build	Care	Owner	Next
Струни - ателие (music studio for toddlers)	✅ DELIVERED - live on her own domain	600 PAID 05 Aug	24/mo RUNNING SINCE 1 SEPT, unbillable	Ivo / Elena	Live on her own domain since 21 Aug, carried at 155,441 bytes, and the 16-day breach on money already taken stays closed. 🔴 Her care started on 1 September and is two days into a first month nobody can bill. The figure is agreed and confirmed and there is nothing to chase - what is missing is a rail to charge it on, and that is the money read at day 48. ⚠ Her €180 chain is ruled and unpaid, and with delivery done the last reason to hold it is gone.
Къща за гости Jost (guest house, Sankt Goar, Germany)	💵 BUILD PAID - ✅ contact path works	600 PAID 16 Aug ⚠ into a personal account	49 recorded vs 40 offered, day 16	Elena / Ivo	✅ THE GO-LIVE GATE CAME OFF HER SIDE AND ONTO OURS ON 30 AUG: she will not register a firm and will pay as a private person, to avoid a company filing and a premises inspection. The „waiting on her accountant“ line is retired and must not be repeated. 🔴 What is left is one domain pick and a registration, both ours, on a build paid 16 days ago with nothing registered. Naming constraint that follows from her decision: read as a holiday home, and keep „guest house“ in any language out of the name and the domain; the search layer inside the code may keep it. ✅ She has named her own preference, built on the family name. ✅ The site also got a working contact path on 28 Aug - the phone is a call button and the form now reaches her own address, where it previously reached nobody. Carried at 2,076,969 bytes. Two values deliberately held (an incomplete postal address and which tax number applies), no-index kept. 🔴 Nothing mintable until the rep says which number closed, day 17, and her plan has been running since 1 September; she has asked for a payment link she cannot be given, day 48. A festival in the second week of September sells the town out, so the window is now about eight days. Three commission claimants on one deal, two with unproven attribution, and the fourth name the daily message kept printing was wrong and is corrected.
Услуги с Bobcat и мини багер (Несебър)	💵 DEPOSIT TAKEN - price recorded nowhere	100 deposit total unknown	not recorded	Elena / Ivo	A row that has taken money and has no total build price and no monthly fee anywhere in the record. ✅ Both figures were asked of the rep in writing on 25 and 26 Aug and are still unanswered. Page carried at 474,107 bytes, unchanged, but it still ships placeholder chips and no call button. Work was due in September, which started today, on a row whose price nobody can state.
Психопозитив (Мирела)	✅ BUILD PAID - 🔴 care never billed, day 33	300 PAID 18 Aug	29/mo, never once billed	Ivo	Live on her own domain 33 days, carried at 462,486 bytes. 🔴 A full September campaign and two social packs have been delivered into a plan that has never been billed, and the September that campaign is for is now running. His own client, his own call. Open gates: the invoice and the full cabinet contact details, which also block the map and the schema.
Coffee Shop (brand now „Lady Queen“, Карнобат)	💵 WON - 🔴 instalment 1 disputed, day 10	300 in 3 x 100 ⚠ is #1 paid?	24/mo deferred to launch	Ivo / Elena	The book says €100 received on 15 Aug in cash; the owner says the first instalment is not yet charged. He asked her again on 25, 26, 27 and 28 Aug and she has not answered, although she requested five demos across 30 and 31 Aug. Book it or strike it. Both pages carried at 1,360,908 and 1,361,644 bytes. Currency still unconfirmed on the 300, and the second orders contact may still need a job title and an email.
Brilliantin (hotel + restaurant, Сливен)	Care, LIVE on its own address	350 PAID	120 = 6 x 20 PREPAID	Ivo	Delivered, carried at 2,914,113 bytes. ✅ Not in the August care gap: it had a dated August action, the own-domain go-live on 08 Aug. ⚠ The monthly has never started after the prepaid six, which is why this row sits in the never-billed item above. Remaining and small: the search-indexing and business-listing go-live step, manual. Restaurant add-on still pending the client’s confirm.
Rakadiko	Care, PREPAID to Aug 2027	200 PAID	150 CASH for a full year	Elena / Ivo	Nothing to collect, carried at 554,207 bytes, and it is the live proof point for the identical annual push on his brother, who has now also prepaid and whose build closed in full on 28 Aug. ✅ Not in the August care gap: menu prices were updated on 05 Aug. Two small residuals: the currency was never stated in the message, and her commission on the 150 is unbooked. One feature open: the monthly auto-publish needs page admin access.
Kapitanovi (Kiten)	🔴 AUGUST MISSED - a written promise not kept	200 paid	120/yr CASH PREPAID	Elena	🔴 The month ended and the pack never came, and now a second month has started on top of it. Channel silent since 24 July, 40 days, against our own 27 June message promising her in writing that the next pack comes at the beginning of August. It is the one gap on this board the client can check for herself, and the ask has been in writing with the rep since 25 Aug. Page carried at 2,270,679 bytes. 🔴 And the commission leg is now live: ~€48 at 40% was booked on 24 July against a care year whose first month was never delivered, which the ambassador rule makes contingent on delivery. Off-season rate still unnegotiated; nothing is to be collected here for a year.
Food Addiction	🔴 BILLED FOR AUGUST, LAST CARE ACTION 04 JULY	40/mo build sub ACTIVE	19/mo on a card, paid in cash	Ivo	🔴 Two problems on one row and they compound. The rep stated on 24 Aug that care is on a card while the client pays only in cash - the first human ownership claim on the unidentified monthly subscription in 47 runs. And this morning’s audit adds the other half: her last actual care action was 04 July, so a monthly-billed client was charged for August and received nothing in it. Read the customer, then decide cancel and whether anything is owed back. Blocked by the money read being on day 46. Page carried at 2,244,389 bytes.
Kameli Club (hotel services)	🔴 PAID A YEAR - no care cycle has EVER run	400 PAID	200/yr PAID 03 Aug	Ivo	Nothing open with the client and she is not to be approached for care money this year. Page carried at 27,223 bytes. 🔴 But her channel was last touched on 04 Aug, 29 days, on money admin only, and no care cycle has ever run on the client who paid the furthest ahead of anyone. One item remains with Ivo: the commission ruling, unmade for 28 days.
Champions Lab	🎨 CARE DELIVERED 29 Aug - starts SEPT by her decision	200 PAID	19/mo, RUNNING SINCE 1 SEPT, never billed	Ivo	✅ The first visible care delivery on this row since 16 Aug - a hall banner built 2.59 by 1.74 metres, landscape, laid out from the red annotations on her own reference photograph rather than from the reversed word order in her message, print master 10,197 by 6,850 pixels at 100 dpi, delivered to her folder. That is the shape the three missed rows are lacking, and it proves the motion works. Do NOT re-flag this row as blocked on Ivo: her care starts September by her own decision, which means it has been running since 1 September. Waiting on her: the new schedule and the full location list. With him: the domain shortlist. Page carried at 4,156,357 bytes. ⚠ Her €19 is recorded as never billed, which is one of the two checks pointing the unidentified subscription at another client.
Coffee Delmar (Дилмар)	✅ SETTLED IN FULL - out of every collection to Aug 2027	150 build, PAID IN FULL 28 Aug ⚠ book still says 100	150/yr PAID, Aug 2026 to Jul 2027	Ivo	✅ The collector closed it in writing on 28 Aug at 16:49: „the annual care runs from August, the build is paid in full“. That settles the build at 150, the care at €150 prepaid for a full year covering August 2026 to July 2027, and confirms there is no monthly figure and never was one. Ivo had already declared the row closed on 27 Aug. Site carried at 1,797,878 bytes. 🔴 The one thing that falls OUT of that closure: the money book still books €100 on the build, so it understates this client by €50, and the file has now not moved in ten days. 🔴 The surviving rail leg is unchanged: who physically holds the €300, counted with the unbanked cash. Effective care rate €12.50 a month, a paid precedent below every live number.
TMB Smart (consult)	Delivered / CLOSED	600 / 600 PAID IN FULL	n/a	Ivo	Nothing open on money. Housekeeping only: deactivate the redundant duplicate link once the money read is restored, and do not send it. One question survives for the books: whether the first 300 landed in a company or a personal account. Still gated on the client’s own list.
BusinessTax (Niki)	Won - free build, care not triggered	FREE (gift)	19 or 29, his choice	Ivo	Mint care on his choice. The access-handover window expired on 15 July when the incumbent relocated; establish whether the hosting and registrar access was taken, and if not, what replaces it. Site live at 83,639 bytes and unaffected.
Terzieva Ivancheva (law firm)	Won - free build, care not triggered	FREE (gift)	19 or 29, her choice	Ivo	Mint care on her choice. Domain renewed to 2027. Site carried at 417,688 bytes. Same revised handover ask as the accounting client.
Boyzone (Bizon Electronics, scooters)	⏸ PAUSED 1 SEPT AT THE CLIENT’S OWN REQUEST - done same run	n/a (gift)	5/mo PAID on the owner’s card	Elena	✅ 1 SEPTEMBER: the owner asked at 13:38 for the site to be paused and his phone removed because he hasto be away, and both were done in the same run. All three addresses now serve one short page in his colours with his mark saying the service is not taking bookings for now, in both languages, verified at 94,554 bytes each and equal to local. The number was counted out, not assumed: 12 occurrences before, 0 now, checked against the downloaded bytes. No-index added; nothing deleted, the full previous page retained under a dated backup and one command from restoration. ⚠ Flagged to him and it is his: his public business listing still publishes the phone. ✅ The 35-day publish stall closed on 24 Aug and stays closed - the row had a dated August action, so it is NOT in the month-end care gap. Do not re-open it. Housekeeping unchanged: the €5 a month accrues as a backlog to be charged when a clean rail exists.
Кондио (Яна Кондио)	Delivered, NO price and NOT sent	not on record	not on record	Ivo	She has a live site at 105,250 bytes, a print-ready card and twenty posts delivered with no price attached and nothing ever sent. Decide the commercial frame, then send. ⚠ Live defect unfixed: the declared display font ships no Cyrillic, so every Bulgarian sentence renders in whatever the visitor’s device substitutes. Ownership of the relationship also still needs reconciling.

In-flight - deployed / sent

Client	Stage	Owner	Next
⏳ CLOSED as no-answer - all three now past their last touch, one message each, and all three against our own defects
Божура	🔴 CLOSED AS NO-ANSWER - on a page dead all 15 days	Ivo	🔴 Sent 16 Aug, last touch has passed at day 17, and the page has returned Not Found at 766 bytes for the whole cadence. The silence measured our own dead link, not the prospect’s disinterest, so closing this as a market answer would be reading the wrong signal. Not a take-down; unintended. One redeploy command makes it recoverable, and the row deserves a fresh first contact rather than a nudge.
Фарзандо	🔴 CLOSED AS NO-ANSWER - it never had a way to answer	Ivo	🔴 Last touch has passed, day 17. The page is live and byte-identical since 17 Aug at 41,880 bytes but ships no click-to-call, no images and no footer badge - a build gate under the standing no-CTA rule, thirteenth consecutive day. A prospect with no call button and no images had no route back to us. Patch before any re-approach; do not record this as a market no.
Финанса (Ина, financial services)	🔴 CLOSED AS NO-ANSWER - live, unfinished, unpaid, no route back	Ivo	Live on Ivo’s explicit override of the content hold; the decision is recorded, not re-litigated, and the deploy was verified by bytes. 🔴 Byte-stable for a sixth consecutive measurement at 74,332 bytes and unchanged in content since 24 Aug: zero call links, zero mail links, a form that reaches nobody, seven unfilled tokens, „coming soon“ six times, and a positioning her own documents do not support. Two questions to the client, one message. Intended 200 build + 19/mo. Nudge correctly held eleven days - this row is owed a commercial answer. 🔴 The day ended and no last touch was spent, so on the standing cadence it closes as no-answer having had one message in its whole life, on a page with no way to answer. It joins the two rows above it, and all three closed on our own defects rather than on a market verdict.
🔄 Reopened 30 August - the first row on this board to come back from closed lost
Пицария „Сезам“ / Pizza & Duner Sezam (Карнобат, one site covering both locations)	🔄 REOPENED - demo live again, unsent, unpriced, day 4	Ivo un-archives / Elena sends	Refused 25 Aug, back 30 Aug. The rep wrote at 11:17 that the owner had contacted her and that she no longer had the link, having archived the channel at the refusal. ✅ Restored the same run and byte-verified: 200 at 1,864,663 bytes, hash identical to the local source and to the pre-take-down hash recorded on 25 Aug, on the same address she already sent, so the owner sees the exact page rather than a rebuild. The bilingual toggle is live (63 translated nodes) and the preview card answers at 131,877 bytes. ✅ One command only because the take-down deleted the objects but kept the project name. 🔴 Still no client surface on day 4: the channel is archived and un-archiving is a click only Ivo can make. ⚠ Ask before sending, never assume it: the page is a deliberate 2-in-1 covering both Сезам locations and same-owner was assumed at build time, never confirmed. If the caller runs only one, the page shows them a shop that is not theirs. Price and send are hers, sub-1k. Nothing sent, nothing priced.
🏭 Built 31 August - FIVE demos in one day, THREE SENT on 1 September, and the market answered twice inside 24 hours. Listed from the build ledger and the send log, because the spine recorded none of it
Хотел Елит (Кирково, 2-star, Родопите)	🆕 LIVE - unsent, unpriced, day 1	Elena	Byte-verified at 1,533,377 bytes with three agreeing fetches against the local file. ✅ Greenfield proven on two independent probes, not assumed: their own business listing carries no website field at all, and five candidate domains do not resolve. ⚠ The sharpest line for the seller is that somebody else is already trading on their name: an auto-generated affiliate microsite built off their booking listing runs its own book-now funnel and even offers a „manage this property“ login. ⚠ Two obvious domains for their own name are taken by a same-named hotel 300 km away; the matching longer name is free. ✅ 10 real photographs, zero stock, nine uploaded by the hotel itself. Brand is our proposal because they have no mark, but the palette was sampled from their own signage. ⚠ Deliberately NOT published and reversible in one edit: room count, cash-only, pool water, and anything the review sites contradict. Price nowhere on the page.
Хотел Елит Спетема (Божурище)	📤 SENT 1 Sept 19:43 - day 1, ✅ on the clock, first nudge 04 Sept	Elena	✅ SENT at 19:43:44 on 1 September and now properly on the cadence: day 1, first nudge 04 September. It was one of the three sends the logger silently dropped; recovered this morning and re-verified live at 1,092,952 bytes. Silent so far, no price stated. ⚠ Handle this one carefully before any call: the ratings are weak and four of the five newest reviews are one star about cleanliness. No score, no review count and no testimonial appears anywhere on the page, verified by stripping the embedded images out of the served body and searching what was left. ⚠ The map is deliberately keyed on coordinates rather than the business name, because a name query renders the listing’s own rating card inside the frame where no check can see it. 🔴 Two dead front doors: their listing publishes no website, and their old auto-built page returns Not Found. ⚠ The brief’s address was wrong and was corrected against three independent sources. Room count, capacity and the pet policy are withheld because the sources contradict each other. No enquiry form and no chat button ship, because no page could be verified and a wrong link sends their customers to a stranger.
Семеен хотел Виктория 1 (Сандански, 3-star family hotel)	🆕 LIVE - unsent, unpriced, day 1, and the pitch is stronger than the brief said	Elena	Byte-verified at 1,282,724 bytes. ✅ The strongest single fact on any of the five: the web address they publish on their own social page WAS NEVER REGISTERED. It does not resolve on two independent resolvers, has no records of any kind, and the registry returns nothing for it - and the brief had even truncated the name, so the correct spelling must be used in the pitch or the owner will not recognise it. A second published address, their old auto-built page, also returns Not Found, and their business listing has no website field. Three dead doors on one business. ✅ 10 photographs, every one uploaded by the owner, zero stock. ⚠ No exterior shot of the building exists in anything they have published, so the hero is their own terrace and the top open ask is one facade photograph. ⚠ Their own page and the map disagree on the street number, 15 against 5; the page publishes 15 and the pin is surveyed, so one question settles it. ⚠ A five-star review praising parking was deliberately dropped because two others say parking is hard. No rating printed anywhere.
МОТЕЛ СИТИ (Пловдив, motel, 10 rooms)	🔴 SENT 1 Sept 10:47 - FLAT REFUSAL 21:17, CLOSED LOST	Elena	🔴🔴 SENT at 10:47:36 and REFUSED outright at 21:17:50 the same evening - „a categorical no“ - channel archived the same minute and the row logged closed lost. Ten and a half hours from send to no. ✅ Both the send and the close are on the record now, recovered this morning with the outcome written against them, so this row will not sit in the open count as a false positive. Nothing is chased and nothing is nudged. ⚠ Read it beside the same morning’s club reply rather than on its own: two sends at the same minute, one brief back in four hours and one refusal in ten - the market answered both, fast, and that is more information than the previous fortnight of silence produced. No price was ever stated, so nothing was undercut. Page was live at 678,018 bytes when sent. ✅ Greenfield confirmed the strong way: their listing has no website field at all, so this is not a social page standing in for a site and not a dead domain. 🔴 READ BEFORE THE CALL: their newest review, from August 2025 and one star, describes bed bugs and an uncleaned bathroom. Not one review is quoted on the page, deliberately. ⚠ The building has been repainted since their own published photograph, so the better-looking frame was rejected for the hero in favour of the truthful one. ✅ The mark is real, redrawn from the sign at their own reception. ⚠ They publish a price list themselves, and no price was put on the page, held under the pricing gate. Seven real photographs, zero stock, each credited.
Таекуондо клуб LEGENDS (София)	📤 SENT 1 Sept - ✅ REPLIED SAME DAY, 🔴 revision live unchecked	Elena / Ivo	✅✅ THE ROW OF THE WEEK. Sent at 10:47:45, fourteen hours after going live, and the owner answered at 14:15 - quoted by the rep: she trusts us on the design, wants it bolder than just the club colours and wants visible movement. That is the first client reply the Bulgarian lane has had since 16 August, and it is a brief rather than a refusal. ✅ A full revision shipped the same afternoon on the same link she already sent, so the owner sees it without being re-sent anything: every section given a different shape, a third and fourth colour added with all three metallic values contrast-calculated before they were fixed, and the movement brought forward rather than piled on. Page 1,032,028 bytes, up from 1,024,750. 🔴 Its rendering check never ran - the workshop crashed straight after the deploy and did not return, and rollback needs the same workshop, so an unverified version is live. See the open item above. ✅ The trap this exact request invites was NOT sprung: her competition titles stay static text, zero counter machinery in the whole build, because the browser’s translate feature freezes animated numbers and would leave a wrong figure where a real title should be. Photographs, credits and licences untouched, measured at 364 of 364 identical blocks. ✅ Send and reply are both on the record now, recovered this morning - and because she answered, this row was never a nudge candidate and never needed a clock. ⚠⚠ NOT the Дупница club held at the gate above. Different city, coach, hall, phone and social page, zero shared copy or photographs, and the check was run rather than assumed. ✅ Greenfield proven twice: no website field on their listing, and five candidate domains do not resolve. The dated control fact is on the page itself: of 15 distinct Sofia clubs in the same sport, 9 publish their own site. ✅ A real correction was caught and fixed the same evening after Ivo flagged that the first pass had no taekwondo in it: the build had generalised from one cover photo without opening their photo album, where four frames are the empty hall and one is an adult black belt. The child-photo gate is a per-frame filter, not a per-client ban, and reading it as a ban cost a rebuild. The page now ships six openly licensed sport and venue photographs, all adults in headgear, and says in both languages that none of them shows this club. ✅ The honours list is static text with no animated counters, because it is a factual claim. Open to the rep: age groups, minimum age, hall entrance, parking, an e-mail, and their own photographs with written consent.
Hotel Prince Cyril (Стария Несебър)	⚠ HELD, CORRECTLY - not a „no site“ case	Elena	✅ The pre-check did its job and stopped a build. The rep asked for a demo with no condition attached; the business has a live site, 26,750 bytes, so the greenfield pitch would have been a factually false opening sentence. ⚠ But the real angle is better than either: their site takes NO reservations at all - zero mentions of booking anywhere in it - on a 12-room hotel in the old town, 200 metres from the sea, rated 9.3 on the largest booking site. That is the displacement pitch, not the greenfield one. Awaiting one word from the rep: build the rebuild demo, or drop the row.
🏭 Built 29 August - two demos, day 4, one of them still held at the gate
Таекуондо клуб „ГЛАДИАТОРЬ“ (Дупница, sports club, 3,800 followers)	🔴 LIVE, FINISHED - SEND HELD ON IVO’S WORD, DAY 4	Ivo	Requested by the rep at 14:24, live at 16:10 and rebuilt twice more after the hold was already posted: a design pass at 17:16 and a real-photograph rebuild at 17:43, final page byte-verified at 578,895 bytes. 🔴 It cannot be sent. Research surfaced a 2022 press headline naming the chairman and senior coach; no legal outcome is known either way, the club is not named as an organisation, none of it is on the page, and it went straight up to Ivo rather than to the rep. One word from him releases it, and the rep has been waiting four days, during which she asked for and received five other demos and sent three of them. ⚠ The pitch is inverted and must not be got wrong: this is a DEAD LINK, not greenfield. Their own social page still links to a builder’s error page, so „you have no website“ is a factually false sentence. ⚠ Medallists are children and are not named on the page; six photographs were used in which no face is identifiable. ⚠ Our own brief was corrected in channel: the email belongs to the chairman, not to the coach who shares the surname.
PG Steam Cleaning (Бургас)	🆕 LIVE - unsent, unpriced, warm, NO gate, day 4	Elena	Requested by the rep at 11:58 and live by 13:06, 68 minutes, byte-verified at 512,488 bytes independently of the deploy script, with the link posted to its own channel and read back. Warm and rep-requested, so the cold inventory cap did not apply. ✅ No Ivo gate: she reviews, she sends, the price is hers - and on the fourteen-hour evidence above, the sooner the better. ✅ Greenfield confirmed rather than assumed - their own business listing publishes no website. ✅ Zero stock imagery: eight of their own ten photographs shipped, so there is nothing to swap out later. Not accommodation, so the commission pitch was deliberately not used. Awaiting from the client: prices, covered area, email.
📤 Sent 24 to 29 August - the Bulgarian lane’s best week, and one send finally carried a price
Fighting Club Несебър	📤 SENT 29 Aug - day 4, ✅ priced, 🔴 its nudge sat a day	Elena	✅ The first send since 24 Aug to carry a stated price, and it matched the seed rather than undercutting it: Ivo logged 250 for the build plus 19 a month in-channel at 15:10:59. Built 14 June, so a 76-day build-to-send. Host re-measured live this morning and answering. Silent, day 4, no money, no payment link requested. ✅ It is in the send log with a clock. 🔴 Confirmed this morning: no cadence run happened at all on 1 September, so its day-3 nudge came due that day and sat one day. It is the only row that actually slipped from that miss, because every other queued row was already overdue or held. It remains the only priced thread on the board.
Магазин Жаклин	📤 SENT 27 Aug - day 6, in the approved nudge queue	Elena	Live at 1,342,977 bytes and re-measured answering this morning. 17 days build-to-send. No reply recorded. ✅ It sits in the approved nudge queue as a genuine first touch, drafted and waiting on somebody pressing send. Open on first reply: the form recipient and confirming the hours. No price was stated. Price and follow-up stay hers.
Пране Георгиеви	📤 SENT 27 Aug - day 6, in the approved nudge queue	Elena	Live at 1,037,888 bytes. 17 days build-to-send. Same backfill, same clock, +5 falls TODAY. She repeated „sent“ at 13:45 on the day with no state change. No price stated.
Зелен екип (Пловдив, green and landscaping)	📤 SENT 27 Aug - day 6, in the approved nudge queue	Elena	✅ Logged the same afternoon, so it has carried a real cadence clock from the start; +5 falls TODAY. Live at 1,468,708 bytes, byte-identical to local. Seeded in-channel on 24 Aug at 250 plus 19 a month; no price stated on the send. ⚠ All seven photographs are stock and marked as examples, and the business name on the page is our proposal, not theirs.
Стаи за гости „Къща Тончеви“	📤 SENT 27 Aug - day 6, in the approved nudge queue	Elena	Live at 1,641,527 bytes. One of the eighteen list rows seeded on 24 Aug at 250 plus 19 a month; no price stated on the send. Core-ICP accommodation, so it is the one of the four most worth a real second touch. +5 falls TODAY.
Комплекс Колонада	📤 SENT 25 Aug - day 7, nudge queued	Elena	⚠ The only one of the five rows sent on 25 August that has not come back a no - and one of the four that did has since reopened of its own accord. Sent and logged, so this one has had a real clock throughout; live at 1,463,900 bytes and its nudge is queued. Price and follow-up stay hers.
Къща за гости Роден край	📤 SENT 24 Aug - day 9, ⚠ the nudge is a decision	Elena / Ivo	Channel seeded at 18:57 with 250 + 19/mo; she posted at 20:04 that she had sent 100 + 15/mo or 120 for the year. Below the ruled floor, and the annual undercuts the monthly by a third. Host carried at 1,476,692 bytes. ⚠ SLUG CAVEAT: the channel name is NOT the host - curling the channel name returns Not Found and would produce a false outage. Second row in the book with that shape. ⚠ It was deliberately NOT drafted into the nudge queue: this is a re-approach, not a first contact - the same row was sent on 14 June and already spent its single nudge on 17 June, so a nudge now is the fourth touch and needs one word from Ivo. The send is hers. The floor and the fourth touch are his.
🏨 The Chon Buri accommodation batch - the best inventory this venture has ever built, and nobody has been told
30 Chon Buri accommodation pages (hotels, resorts, guest houses, hostels, villas - Pattaya, Jomtien, Sattahip, Bang Saray, Bang Lamung, Koh Larn)	🔴 LIVE, UNSENT, UNPRICED - 27 with no channel at all	Ivo	🔴 27 of them still have no client-channel record of any kind, day 9 - no link where a human reads it, no cadence clock, nowhere for a reply to land. Not re-sampled and the reason is sound: every channel created since the last sampling belongs to a new build, so the finding cannot have changed. These are the exact segment the charter names as first focus, in the exact town operations moved to. ⚠ The alternative is visible in one afternoon: a build that runs through the channel practice gets a link, a member and a read-back inside fifteen minutes. Assign, send or archive, but decide.
T8 Exclusive Boutique (Pattaya)	LIVE - unsent, unpriced	Ivo	From the referral box, carrying the clean overseas code. Local-language default with an English toggle. ✅ Channel created with the rep invited at creation and membership verified. Nothing has gone to the business.
📤 The Pattaya batch - 17 sent on 22 August, day 10, and the follow-up now belongs to Konnie, not to the Bulgarian queue
17 Pattaya demos (cafes, parks, aquarium, museums, paramotor, attractions)	📤 SENT 22 Aug - 🔴 day 10, owner cannot act, no channel record	Ivo	🔴 Their +2 and +5 have both passed unserved, because not one of the 17 channels carries the send and every row in the log is still unconfirmed. The rep cannot see twelve of those channels. ✅ Correction to the morning reading: 16 of these came OFF the Bulgarian nudge queue by design. A written procedure dated 30 August assigns them to Konnie, in Thai, with a six-a-day cap and two touches then stop - a Bulgarian nudge to a Pattaya cafe was never the right follow-up, and the record beat the instruction. The seventeenth, a stone park, is explicitly not hers because the animal-attraction gate is unruled, so it stays held with Ivo. 🔴 The blocker is therefore a handover, not a cadence: section 0 of that procedure is Ivo’s - the social login for Konnie, 17 manual channel invites and the local payment line - so sixteen threads have an owner who is not equipped to touch them. ⚠ One live contradiction surfaced and deliberately not resolved: a matcha cafe is held as parked by one document and listed sixth on Konnie’s follow-up list by the newer one.
Pattaya Night Bazaar (management company, not an owner)	🔴 LIVE - DO NOT SEND, UNPATCHED day 14	Ivo	Animates a factual rating and review count with no translate guard. ✅ Checked name-by-name against the approval queues again and it did not go out. Unsendable until the numbers are static markup.
The Sanctuary of Truth Museum (has its own site - never pitch „no website“)	🔴 LIVE - DO NOT SEND, UNPATCHED day 14	Ivo	Same two defects. ✅ Also checked and also did not go out. The gate has now held seven windows running.
Elephant Village, Tiger Park & Snake Show (all three stopped before code)	🛑 NOT BUILT - escalated, gate unruled	Ivo	Animal-attraction gate is unruled and is Ivo’s call. No welfare claims anywhere. Recorded so the refusal is not mistaken for an oversight.
📧 Bulgaria - one dead page, one wrong-business address, one care request owed
Kalina i Milan	🔴 RE-SENT 20 Aug TO AN ADDRESS ALREADY DEAD, DAY 12	Ivo	🔴 Not Found at 766 bytes on the 30 August measurement and not redeployed since. It was re-sent after she spoke to the owner’s wife, intended 50 + 15/mo, to a host that was already down. Nudge correctly held, and the do-not-chase flag stands. Same one-command fix as the row above it, and its last touch falls in two days.
Милев (Свети Влас - the correct brand)	🔴 A RETIRED ADDRESS STILL SERVES THE WRONG BUSINESS - day 18	Ivo	The retired address answers 200 at 1,316,093 bytes, byte-identical since 14 Aug, while the correct page serves beside it at 1,513,920. She marked it sent on 21 Aug and has not said which link she used, day 10. ✅ The follow-up is no longer blocked - the queued nudge carries the correct address, which repairs the bad case and is ordinary in the good one. Retiring the old address ends it without her.
Маями (Свети Влас - hotel with restaurant)	📤 SENT 21 Aug - day 11, 🔴 past +10, nudge queued and unfired	Elena	Live at 1,350,171 bytes and its nudge sits approved and unfired in the seven-row queue, at day 11 on the tool’s own clock. Ships with no call button until she says whose the disputed reservations number is - so the thread ran past its last touch on a page a prospect cannot ring. Rating, hours and room count deliberately omitted. The do-not-send flag on this row was lifted once it was confirmed to be a hotel.
13 further list rows (hotels, guest houses, restaurants, fight clubs - each with a channel)	Tracked, seeded at 250 + 19/mo, UNSENT	Elena	✅ All seeded with the link, the contact, the price and the one-line recording format, and she was invited at creation on every one. ✅ Two correctly seeded as not for sending: one has no contact path at all, one is a recorded refusal. ⚠ Six of the original eighteen have now left this group - five sent, one sent and refused, with the Несебър fight club leaving at the seeded price. That last one is conversion of a sort: the seeded number survived to the send.
Крушовица (7 Finnish log houses)	📥 CORRECTION LOGGED, CORRECTLY NOT SHIPPED - free by decision	Ivo	📥 The owner’s correction was logged on 28 Aug: model 2 already matches her exactly, model 1 needs four figures corrected and the floor-plan images swapped, and it is day 4. ✅ The digits were deliberately not shipped alone, because the figures and the drawing they are read off are one claim - corrected text against an uncorrected plan puts a page in front of buyers whose numbers and picture disagree. The replacement images sit in a local downloads folder that is not a shared location; moving them makes it a ten-minute edit. Free by decision, so there is no money question here and no ask to make. ⚠ Slug caveat: the live host is the short name at 1,557,573 bytes; the longer alias this file and the channel name both still carry returns Not Found. Do not re-propose this row as a send.
Effective Agency (US market, English default with a Bulgarian toggle)	🆕 DEPLOYED - unsent, and it must not be priced	Ivo	DO NOT PRICE, DO NOT COUNT IN THE UNSENT PILE, DO NOT QUEUE FOR SEND. Ivo’s own revenue-share partner rather than a client sale. ✅ The live page is byte-identical to local at 101,006 bytes, checked with three agreeing fetches after a stale-record scare, so the loop is closed. ⚠ The intake bot auto-stamped it a cold demo and Ivo overrode that in channel, and the override is recorded as a ruling. Badge and terms are his call.
Адвокат Минко Колев (Пловдив)	LIVE - unsent, unpriced	Elena	Five facts and nothing else on the page; everything unknown is an explicit „to be added“ block. Zero prior web presence. Invent nothing beyond the five facts. Channel checked directly, she is in it.
Amore Pizzeria	LIVE - unsent, unpriced	Elena	Wordmark rebuilt after the client asked for a capital A on black; the original typeface rendered its capital A as a lowercase one, so the font was the cause, not the request.
Paradise (Велинград)	Contacted, NOT yet quoted	Elena	The intended price is internally contradictory in her own wording and needs one word before it is quoted.
Two inbound requests (22 Aug - one referral-attributed, one not)	🔴 STILL UNBUILT, day 11	Ivo	The referral-attributed one is blocked on a business name, not on us - the moment the name is given the page gets made. The second, from a map link with no code, has no such excuse. 🔴 Both are now ten days old, and five pages were built for cold-ish rep leads on 31 August alone while these two, who came to us, waited.

Cold inventory + how reps will own it

About 14 speculative demos built and live with no named recipient, plus about 99 tracked deployed-but-unsent in client channels = ~113 built and in front of nobody. ✅ DOWN THREE ACROSS 1 SEPTEMBER, THE FIRST REAL FALL IN A WEEK: the Sofia taekwondo club and the Plovdiv motel went at 10:47 and the Bozhurishte hotel at 19:43, one to two days after being built, and two of the three answered inside 24 hours - one with a brief, one with a flat no. ⚠ The pile still rose by two across the three days, because five pages shipped on 31 August and only three have left. ✅ All three sends are now on the clock, after a morning spent finding out why they were not. The previous movement out was the Несебър fight club, sent at the seeded 250 plus 19 a month, plus a reopened pizza row that came back from closed lost. ⚠ Do not read that reopened row as inventory; it is the only row in this whole count with a person on the other end actively waiting, and the only thing between it and a conversation is one un-archive click. Still about 23 times the cap of 5. ⚠ Not all of these rows are equivalent inventory: the steam-cleaning row and the two remaining 31 August builds are the rep’s to send with no owner gate, while the Дупница club is held at a gate and cannot be worked down by anyone else, day 4, and one further request was correctly held before code because that business already has a live site. ✅ The tail got its strongest evidence yet on 1 September, and it points one way. The Sofia club went from live to sent in fourteen hours and had a client brief back in four more; the earlier fourteen-hour send earned thanks and a promise to call back; a seven-day one on the best-qualified row in the book got hung up on; the angry refusal carried a sixty-day gap; and the one priced send of last week carried a seventy-six-day gap and is silent on day 4. The two fastest sends in the book are the only two warm answers in it - and the Plovdiv motel, sent in the same minute as the club, produced a flat no in ten hours, which is also information and also worth more than silence. So lag is not the whole story and neither is build quality - the variable that tracks the outcome is whether a person with a relationship carries the send, and how quickly they carry it. ⚠ Live column carried, not re-measured: the 30 August verification curled 39 addresses in a clean scratch directory with caching and compression defeated and got 33 answers and 6 Not Found, every one of the six accounted for - three executed take-downs, two named dead sent hosts, one wrong-slug probe rather than an outage. ⚠ The site-health loop produced no run today; its newest output is still dated 1 September 07:01 and it read 100 live sites, 85 OK, 15 warnings, 0 failures, the warnings resolving to one broken shared image plus six unarmed redirects. ✅ What IS measured this morning is narrower and independent: all eight queued follow-up hosts re-curled live from a clean scratch directory with compression defeated, every one answering, and the two known dead demos re-measured Not Found on three of three tries each. The assignment model is one sheet per rep: each demo assigned to a rep who works it from their own sheet, and the sweep folds statuses back into the spine. The sort comes before any proposal, and only a human can do it: (1) FREE BY DECISION, no ask exists; (2) NO COUNTERPARTY, nobody on the other end; (3) GENUINELY UNASKED. The counter cannot tell them apart. The accommodation batch is bucket three: 27 live pages, 27 real businesses, nobody contacted, and nowhere to record a send even if somebody were. ✅ The five newest rows were bucket three with the opposite hygiene - a channel, a verified member and a named counterparty on every one - and three of the five were simply sent, which is the whole argument made in a day. Two remain, both core-ICP accommodation, both hers, no owner gate. Ivo

Removed / parked / churned

⚠ THREE ROWS ARRIVED HERE BY SILENCE RATHER THAN BY A DECISION - AND TWO ARRIVED ON 1 SEPTEMBER BY THE CLIENT’S OWN WORD, WHICH IS THE CLEAN WAY TO CLOSE A ROW. 🔴 NEW: the Plovdiv motel is CLOSED LOST ON A FLAT REFUSAL. Sent at 10:47:36, refused at 21:17:50 - „a categorical no“ - and the rep archived the channel the same minute. Ten and a half hours, send to no. The outcome is written against the row rather than left open, so it will not sit in the count as a false positive; nothing is chased and nothing is nudged. ⚠ Its page carried no price and no defect anyone has named, so unlike the three silent closes below, this one is a genuine market answer and should be read as one. ✅ Also NEW: the children’s-party row is CLOSED BY THE CLIENT, not by a cadence. She told the rep at 11:25 that she had needed the page to show something, showed something else instead, and no longer needs it; the rep archived the channel thirty seconds later, so she closed her own loop and there is nowhere left to post a status. It was never sent, so no send event was written - a closure, not a touch. The host correctly returns Not Found at 766 bytes - that is the earlier agreed take-down, not a defect. Nothing is invoiced, nothing is chased, nothing is reminded. The row had already been parked at her request on 20 August and stays reversible if she ever registers a company. ⚠ The Фарзандо and Божура rows are past their last touch at day 17 and the financial-services row at day 16, and nothing in the record shows a final message was spent on any of them, so on the standing cadence all three close as no-answer, each having had one message in its whole life. ✅ No mass parking has happened and none is due: the 16 Pattaya threads are not on the Bulgarian cadence at all but on Konnie’s own two-touch procedure, and the Свети Влас rows sit in the approved nudge queue rather than parked. 🔴 Read the three silent closes as our own defects rather than as market answers - and note the contrast with the refusal above, which is the real thing: one was sent a link that has served Not Found for all seventeen days, one ships no call button, no images and no badge, and the third is live on a branded domain with zero call links, zero mail links and a form that reaches nobody. Not one of the three had a working route back to us. All are recoverable, and all deserve a fresh first contact rather than a nudge. ✅ The pizza and doner row stays OUT of this section - the owner contacted the rep on 30 Aug asking for the demo again, the page was restored to the same address byte-for-byte, and the row sits in the in-flight table above. It remains the first row this board has ever moved out of closed lost, and the lesson is procedural rather than lucky: the 25 August take-down deleted the objects but kept the project name, so returning it took one command and the owner got the exact page they were sent. ✅ The child psychologist’s page stays down: she replied warmly on 27 August - the idea is great, thank you for making it, she is still studying and will call when she can practise - and asked in the same sentence for it to be stopped for now. Executed and re-verified at Not Found, 766 bytes. It is a PAUSE, not a kill: the source, the preview card and the packaged copy are retained and a restore is one command. Do not nudge her; she will call. ✅ The refused Карнобат venue’s page is also down and verified at the same 766 bytes, even though she never said „stop the demo“ - taken down under standing practice because the demo was serving as that business’s own listing website. Both are closed and must not be re-raised in any shape. 🔴 The hair-and-beauty centre in Айтос stays CLOSED LOST from 27 August: the rep phoned rather than waiting for the nudge, the owner said „we have no interest at all“ and hung up, the live bytes were snapshotted first at 911,017, the objects deleted, the address verified Not Found and the body checked against nine neighbour names with zero hits. ⚠ Note against the qualification: this was the strongest has-site pitch the factory has ever built - a five-star profile whose own website button resolves to nothing - sent after only seven days, and the refusal still came. The two hard refusals of 25 August are unchanged: a hair salon that counts a second social page as its website, and a car dealer who came back „quite angry, they do not know who ordered it“ on a sixty-day gap between build and send - both sent that same morning, so send to no took under three hours in each case. ⚠ A refusal on this board is not proof of a terminal state; it is proof of a state on that day, and the reopened pizza row is now the evidence for that sentence. ✅ Every take-down has been actioned and verified: two pages serve a small no-index stub, the rest return Not Found with their stored objects deleted, local sources were restored and re-hashed identical, and the hosting projects were deliberately retained, because a released name can be claimed by a stranger. ✅ The two refusals written down on 24 Aug stay written down: one soft no and one hard, both of which had previously sat on the list as „ready to send“, which is exactly the repeat the recording ruling exists to prevent. Standing terminal rows, do not chase: the family hotel closed lost 21 Aug, page down and verified, channel archived on 28 Aug so that row is now fully closed; the children’s-party client parked at her own request, page down, channel archived, the row frozen and explicitly not chased for its €100 or its monthly, fully reversible the moment she registers a company; the tyre service churned 03 Aug, the first churn from the paying care base, with the domain, the site and roughly €80 of remaining instalments still an open call for Ivo, now 30 days unanswered, and the rep’s €35 of that client’s cash still to be remitted, which the churn does not cancel. ⚠ One instruction for every future sweep: pages that return Not Found in this section do so BY DESIGN. They are client asks honoured, not dead objects - unlike the two named in the in-flight table above, which are unintended and have now cost a thread. Also parked or declined and not to be re-pitched: the textile competitors of a door-opener, the barbershop, the restaurant with its own site, the car wash, the villa that wants listings only, the guest house whose owner builds websites, and the timing declines. Ivo / Elena

Stages: Lead → Qualified → Demo built → Deployed → Sent → Replied → Won → Care. Terminal: Declined / Parked / Churned. Owners: Ivo prices, sends and rules on money; Elena owns her own copy, her sub-1k prices and her own sends; both where a leg belongs to each. Severity: red = blocker, amber = action, grey = process or record. Follow-up cadence is +2, +5, +10 then park. Nothing on this board sends, prices, charges or messages a client: it records and it flags, and a named person acts. Rebuilt automatically twice a day from the spine, the confirmed facts, the money book, the send log and the agents’ own run-state. This is the morning pass of 2 September. 🔴 The spine underneath it still carries a 30 August 06:40 stamp; the nightly rebuild fired again ten minutes before this pass and had not changed it as of this read, so every client figure here is carried from 30 August and labelled as carried, and the client tables are knowingly incomplete: the five demos of 31 August, the three sends of 1 September, the client reply, the flat refusal, the design revision, the paused care site and the client-closed row are all read off the build ledger and the send log, because the spine recorded none of them. What was measured this morning is the send log itself, now 55 rows, and live re-curls of the eight queued follow-up hosts and the two known dead demos. ✅ The one line worth keeping from this pass: three sends were recovered onto the clock and the reason they fell off was a stale registry silently defeating a guard that was working exactly as designed - a root cause, not a backfill. Internal use only; not indexed, not for client eyes.