Client Journey & Loop Board

🔴💼 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 LIVE PAGE IN FRONT OF A REAL PROSPECT WAS SERVING TEXT THE SAME COLOUR AS ITS BACKGROUND FOR A DAY, AND NO INSTRUMENT WE OWN COULD SEE IT. FIXED AND VERIFIED THIS EVENING; WHAT SHE ACTUALLY ASKED FOR IS STILL NOT DELIVERED. The Sofia taekwondo club has held that link since 1 September 10:47, and the link does not change, so every revision reaches her automatically without anyone sending anything. Measured on the live page before the repair: 29 text blocks below the contrast minimum, the 50px section headings at 1.07 to 1, the coach’s palmarès and every card title at 1.04 to 1, the red accents at 2.66 to 1, and the navigation bar on scroll at 1.13 to 1, near-white on white. ⚠⚠ THE CAUSE IS THE PART TO KEEP: the revision’s entire corrective colour block had been written inside a no-script fallback. Its own comment said it was appended last on purpose so it would outrank the light-theme rules above it, and it would have, except that a no-script block only applies when scripting is switched off, so none of it ever ran for a real visitor. The file read as though the dark theme was finished. ✅ Found by the owner’s own eye in four words, not by a check. The block was lifted into a real stylesheet, three controls the revision had missed were added, and one inline colour on the phone number that no stylesheet can outrank was removed at source. Re-measured after deploy: headings 13.35 to 1, palmarès 11.81 to 1, accents 5.88 to 1, phone 8.03 to 1, and a full sweep of 174 blocks with zero failures. Live and byte-verified at 1,145,118 bytes, identical to local. 🔴 THE FIX WAS DELIBERATELY PARTIAL AND THE REMAINDER IS THE CLIENT’S ACTUAL REQUEST: about a hundred lines covering the logo tiles, the splash and the hero motion stay inert where the revision left them, because they never once executed and have therefore never been tested; switching them on is a reviewable change, not a side effect of a colour repair. She asked for elements of movement, so that request is still open, and the rendering proof it needs is still blocked on browser tooling. ✅ One retraction is recorded on purpose: an earlier note in this session blamed a moving blurred layer for freezing the renderer and that is withdrawn, because a trivial control page failed to capture in the same session. One measurement from a degraded browser is not evidence of a defect in the page; take a control first. ✅ Three checklist rules came out of it, and the sharpest is that the QA harness was hiding the evidence: it raises a state in which the build itself hides the hero elements, so what the fallback hid, the harness could not measure. The contrast sweep now runs once, without it. ⚠ The standing lesson from the earlier revision holds and is now doubly earned: on a revision of an ALREADY-SENT page the rendering QA belongs BEFORE the deploy, on the local file. Nothing was sent, no price was quoted, the badge is intact and the package was cut last. 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

✅ CLOSED BY EXECUTION - THE NIGHTLY REBUILD PRODUCED AGAIN AFTER THREE EMPTY FIRES. No action asked; kept as a record because the way it was detected is the reusable part. It ran at 10:50 this morning, cut its dated backup, rebuilt the spine over a 76-hour window and caught every event of the three silent days. ⚠ The detection method is what to keep: its own run-state had reported success on 31 August and 1 September while writing nothing, so the only honest test was the physical artefact it leaves behind, a dated backup file, which existed for 30 August and then not again until today. Where an agent reports its own health, look for a file it cannot fake. 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

✅ CLOSED - SITE HEALTH DID RUN TODAY, AND THIS MORNING’S ENTRY SAYING OTHERWISE WAS THREE MINUTES EARLY. No action asked; the correction is recorded rather than quietly dropped. Its output is stamped 2 September 11:11 BG, three minutes after the morning pass was written, which is why that pass read it as quiet. The run covered 100 live sites: 83 OK, 17 warnings, 0 failures. ⚠ The warnings resolve to two harmless families and neither is a client-facing fault: eight are our own internal pages flagging the same missing shared logo image, and seven are unarmed redirects where a working address and its temporary one both serve the same page. Two are real and already named on this board: one guest-house preview card pointing at a host that is dead, and one third-party photo host refusing connections on a speculative page. Nothing in the run touched the revenue base. 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

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 RE-MEASURED this morning rather than carried, and it is the widest sweep this board has printed: 48 addresses curled from a clean scratch directory with caching and compression defeated, 45 answering and 3 Not Found, every one of the three accounted for - two named dead sent hosts already on this board and one deliberate take-down. The whole revenue base, all seven builds of the last four days, every host named in an open item and every row in the follow-up queue were all in that sweep. ✅ The site-health loop DID run today, at 11:11 BG, and read 100 live sites, 83 OK, 17 warnings, 0 failures, the warnings resolving to eight of our own internal pages flagging the same missing shared logo image, seven unarmed redirects, and two already named on this board. Nothing in it touched the revenue base. ✅ 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. ⚠⚠ One caution this evening added to the whole pile, and it is not about the pile’s size: a sent link never changes, so every later revision reaches the prospect the moment it deploys, with nobody pressing send. The Sofia club spent a day holding a page whose headings were the same colour as the surface behind them. An unsent row can wait; a sent row is a live shop window, and revising one is a client-facing act that needs its rendering check BEFORE the deploy, not after. Ivo

⚠ 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