Client Journey & Loop Board

✅⚠ THE ITEM THAT HAS HEADED THIS BOARD FOR THREE RUNS IS WITHDRAWN, AND THE WAY IT SURVIVED THREE RUNS MATTERS MORE THAN THE ITEM. WHAT IS LEFT IS A DIFFERENT, OLDER, SMALLER OBLIGATION. ✅ The accounts were filed on time. Ivo’s own words, recorded 2 September 10:51:39 against a note dated 1 September and marked done: filed by the management accountant and his team, confirmation received, the 31 August deadline met. The register showed nothing because 31 August was a bank holiday and the register lags. Retracted in full: the „two working days late“ framing and every penalty figure. It must never be restated. 🔴 What survives: the director’s identity verification was due 17 August 2026 and is 17 days past. Separate obligation, never covered here, and not to be double-counted with the confirmation-statement naming, which is the same obligation wearing a second name. Two cheap actions, both his and both unstarted: get the accountant’s submission reference or acceptance e-mail, and re-check the register at the end of next week; if it is still blank then, it is real. ⚠⚠ THE PROCESS HALF, AND IT IS THE DURABLE PART: the correction was posted at 10:51:39 and the nightly digest repeated the withdrawn claim at 11:07:37, sixteen minutes later. Not a timing accident - this loop reads FILES and the correction lived only in a message. The close is a human one: write it into the confirmed-facts file, because an agent must not author ground truth. Until that line exists, every run is one stale read from raising it again. Ivo

🔴 THE REPLACEMENT COMPANY’S WRITTEN ANSWER IS PAST ITS PROMISED DAY WITH NOTHING ON RECORD. THE CHASE CALL IS TODAY, NOT A CONTINGENCY. Working day 5 of 5 closed yesterday with nothing received. 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; the bank holiday is why the calendar and the clock disagreed. Call today with both references to hand. ⚠ Unchanged and load-bearing: do NOT refile until the address-format answer is in hand. Two fees have already been spent guessing, the stated reason was diagnostic rather than clerical, and the practice position points the same way - the operator is resident overseas, and a non-UK usual-residential address is acceptable, never published, and dodges the check entirely. Until a number is issued there is no clean destination for money at all. Ivo

💵 THE MONEY OUTAGE IS DAY 49, AND THE THREE CARE PLANS THAT STARTED ON 1 SEPTEMBER ARE NOW IN THEIR THIRD DAY, BEING DELIVERED AGAINST, AND STILL UNBILLABLE. 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 18, and the client has been asking for a payment link she cannot be given for 49 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 by tool search: no working connection to the payments platform, and no such tool is present in the session at all, day 49. 🔴 The loss is accruing rather than approaching, and the care-delivery audit does not look at these three again until Monday. Ivo

✅⚠ CLOSED BY EXECUTION TODAY - AND THE WAY IT WAS CLOSED IS A REPEAT DEFECT THAT COST A ROUND AND MUST BE READ, NOT SKIPPED. The rep’s two-day-old request to take the scooter client’s endorsement off her own brand page was executed this morning and the page is live and verified: 200 at 372,747 bytes, the endorsement gone, the named person gone, and the money tokens that a second pass found still sitting in the offers block gone with them. ⚠⚠ THE DEFECT: she was asked a one-word question at 09:48:30 - drop the quote only, or the quote and the logo - and she answered „the logo stays“ at 10:01:03. The edit that removed the logo anyway ran at 10:04:34, three minutes later. The run had read the channel once at 09:38 from its own task file and never re-read it before writing. ✅ Reversed inside forty minutes: the mark was put back with its original bytes lifted from the pre-edit backup, and the restored logo wall is byte-identical to the wall before any of this started, compared as a whole slab rather than element by element. ⚠⚠ The durable rule, and it is the second time this exact shape has cost this same client a round: re-read the channel immediately before the WRITE, not only before the post. A correction offered in one word is worth nothing if nobody looks for the answer. ⚠ One further lesson recorded against ourselves: the removal was partly argued on „their site is dead so the mark would link nowhere“, and that address was measured today at 200 and 94,554 bytes. It is live. A premise about a third party’s site is a measurement, never an inference from a client’s phrasing. closed - Elena informed in channel

✅🏹 CLOSED BY EXECUTION TODAY - THE SOFIA CLUB GOT ALL THREE OF THE THINGS SHE ASKED FOR, ACROSS TWO REVISIONS, ON THE SAME LINK SHE ALREADY HOLDS. WHAT IS STILL OPEN IS HERS TO ANSWER, NOT OURS TO BUILD. Her brief of 1 September was dark background, movement, and her own mark everywhere. Dark shipped that night, its contrast defect was repaired yesterday, and the mark and the movement both landed today - her real club logo in all four places plus the preview card and the site icon, and eight moving elements that had never once executed because the earlier code sat inside a block that never runs. ✅ A second revision this evening replaced the licensed stand-in photographs with four frames of their own club, taken from their own public page: an adult black belt mid-kick in their own hall, and three of the hall itself. Every credit line, the honesty note about the photographs and the provenance lines came off WITH them, and the order was not cosmetic - it was legal. The stand-ins were share-alike licensed, so removing the names while the pictures stayed would have been a licence breach rather than a tidy-up; the only clean way to drop the credits was to drop the photographs, so their own frames went in first. 🔴 THREE THINGS ARE HELD AND ALL THREE NEED THE REP, NOT A BUILD: four frames showing recognisable children are held out of the build pending written consent and are not on the page; a richer competition record is held because it is a factual claim and nobody has confirmed the years; and the hero photograph is published without naming the person in it. ⚠ Also on the record and already fixed: she asked twice for a link to the shared photo folder and never got one, she uploaded the logo anyway, and the folder was told to her as empty six minutes before she filled it and nothing opened it for 38 hours. ⚠⚠ A folder check is a per-run step, not a build-time one. „Empty“ ages in minutes. Elena

🔴📁 NEW - A NEW CLIENT CHANNEL WAS CREATED THIS EVENING AND THE REP IS NOT IN IT. THE INVITATION FAILED SILENTLY AND THE TOOL REPORTED SUCCESS. The channel for tonight’s new build exists and is seeded, and a direct member listing shows one member, the bot. The invite call reported „members invited: 1“. ⚠⚠ THE MECHANISM IS NOW KNOWN AND IT IS ELEVEN OCCURRENCES OLD: putting Ivo’s own id in the invite list kills the WHOLE batch and still reports success. The count is not evidence; only a direct member listing is. 🔴 There is no standalone invite tool, so this is a manual action and only Ivo can take it: add the rep to that channel. Until he does, the brief, the link and every later revision are invisible to the person who requested the demo and who will send it - and her status had to be relayed in the general field channel instead. The gap this joins is now around 20 channels she cannot see. Ivo

🔴📁 „DO WE ARCHIVE THE CHANNEL AT A REFUSAL?“ IS ON DAY 4 UNANSWERED, AND IT IS ONE SENTENCE THAT RETIRES A PROVEN, REPEATING COST. The cost has already been paid once and is on the record: the pizza row refused on 25 Aug, its channel was archived, the client came back by herself on 30 Aug and the rep had lost the link. 🔴 Three more channels have been archived at a refusal since the question was raised - the tyre row, the Plovdiv motel and the children’s-party row. Un-archiving is an interface action only Ivo can take. ✅ The motel half was settled today by taking the page down rather than by arguing the doctrine. It had stayed live for 36 hours after a categorical refusal; a snapshot was pulled first and matched the local copy byte for byte, and the address now serves a 608-byte unbranded no-index stub with zero brand residue and zero neighbour-slug leakage. Restore is one command and byte-exact, so this is reversible state, not an ending. ⚠ Two things the take-down surfaced and both are Ivo’s: the documented delete path was not available because our hosting token is scoped too narrowly and the object could not be removed, so the address is held by a stub rather than freed; and the channel is archived, so the completion could not be recorded where the refusal was. The rule that ends the whole item is still one sentence: mark the row, leave the channel. 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, two Свети Влас rows, three sends of 27 August now at day 7 and the Несебър fight club at day 5. ✅ The one-nudge cap is provably intact: zero nudge events have ever been written to the log, checked rather than asserted, and every queued host was answering when last measured. ⚠ 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 12 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, AND SEPTEMBER IS NOW THREE DAYS DEEP ON TOP OF IT. Written by Monday’s care audit, measured from the client channels rather than carried, and every counter aged again this morning. The Kiten guest house: care prepaid to July 2027, channel silent since 24 July, 41 days, against our own 27 June message promising 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 actual care action 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, 30 days, on money admin only, 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, the hotel in Сливен, the scooter account, the gym and the coffee client. 🔴 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 5, AND THE FIFTH DAY WAS A DAY IN WHICH NOTHING ELSE HAPPENED EITHER. 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 now waiting into a fifth day. ✅ Everything else on the row is clean: the pitch is confirmed as a dead link rather than greenfield because their own social page still links to a builder’s error page, 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 GERMAN GUEST HOUSE’S GO-LIVE IS ONE DOMAIN PICK, AND THE FESTIVAL WINDOW IS NOW ABOUT A WEEK AWAY. ✅ The client settled the gate 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. The line this board 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 naming constraints follow from her decision: 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 tightened again overnight: the build was paid 18 days ago, nothing is registered, and the Rhine festival that sells the town out falls in the second week of September, now roughly a week 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 14. Re-measured this morning from a clean scratch directory with compression defeated: the partner page serves 200 at 20,037 bytes, reading 30% four times and 20% once - the eighth consecutive byte-identical measurement, so nothing has shipped in fourteen 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 18 AND DAY 14. STILL THE CHEAPEST OPEN ITEM ON THE BOARD, AND ONE OF THEM HAS ALREADY COST A THREAD. Both returned Not Found at 766 bytes in this morning’s sweep, 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 eighteen 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, and they are the only two unexplained failures in a 36-host sweep in which everything else answered. The send engine correctly held both nudges again, 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 is unchanged: the take-down machinery has run flawlessly every time it was asked, while these two redeploys, which are strictly simpler, have not run in eighteen days. The capability is emphatically not the constraint. Ivo

🔴 A RETIRED ADDRESS IS STILL SERVING A DIFFERENT BUSINESS TO ANYONE THE REP SENT - DAY 20. Re-measured: 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 12 unanswered, and she posted nothing at all in the last window, so it will not be answered by waiting. ✅ Partial progress stands: 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 ELEVEN 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 11, and the commission ledger is untouched for 16 days. ⚠ 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 12 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 she requested five demos across 30 and 31 Aug, so it is not silence in general, although she has now posted nothing anywhere for two days. 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 THE SEPTEMBER CHARGE FALLS THIS WEEK. 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 49 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 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 49, and the September charge on that card falls inside this 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. 🔴 And the three sends of 1 September carried no price in any of their channels, so the one priced send is still the only priced thread on the board. 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 10. 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, every channel created since belongs to a new build, and the one channel created today belongs to tonight’s new build, not to any of these 27. 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 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 12 WITH NO CHANNEL RECORD, NO CONFIRMED CLOCK AND AN OWNER WHO CANNOT ACT. The clock defect stays closed with its root cause: the log holds 55 rows and every open thread 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. Ivo

💵🔴 THE REFERRAL RAIL CARRIES REAL VOLUME AT A RATE THAT HAS NEVER BEEN RULED. Unmoved for a fifth 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 at about 19, stated as carried and not re-checked this run, because no channel was created or archived in the window so the number cannot have moved. The create-time invite path has now worked seven consecutive times: the two channels of 29 Aug and all five of 31 Aug were member-listed directly, two members each, the rep IN on every one. 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 18, 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 18 and the second dead-link row is day 14, both serving Not Found at 766 bytes in this morning’s sweep, so their silence measures our own dead pages and not their disinterest. The financial-services row is day 17 and is owed a commercial answer rather than a „did you see the site“. The re-approach row is day 10 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 78 and 79 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 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

🔴📍 NEW - EVERY PRINTED REFERRAL CODE WE HAVE EVER HANDED OUT LEADS TO THE ENGLISH PAGE, AND THIS IS NOW MEASURED FROM THE PRINTED IMAGE RATHER THAN INFERRED FROM THE SITE. The code was decoded straight out of the picture file today and resolves to the bare offer page, which since the language change of 29 August serves English to everyone. It applies to all eleven printed codes and all eleven posters - so a Bulgarian shopkeeper handed a Bulgarian card scans it and lands in English. ✅ Fixed for the code that was actually asked for today: a new one encoding the Bulgarian route was generated, verified live end to end, and delivered to the rep in the same hour she asked, byte-identical in the shared folder. 🔴 NOT fixed and it is the open half: the eleven posters are print files and the script that generated them was never kept, so they cannot be regenerated the same way. That is a separate piece of work, and until it is done every poster already in the field points at the wrong language. ✅ One quiet capability win worth recording, because it retires a manual workaround: printed codes can now be decoded inside our own sandbox, so „ask the rep to scan it with her phone“ is no longer needed to verify a code before it goes to print. Ivo

✅⚠ CORRECTION TO THIS BOARD - THE REOPENED PIZZA ROW’S CHANNEL IS NOT ARCHIVED AND HAS NOT BEEN SINCE 30 AUGUST. THE BLOCK THIS BOARD CARRIED FOR FOUR DAYS DOES NOT EXIST. The spine records it plainly: Ivo un-archived the channel on 30 Aug at 11:28:24 and the rep joined it at 11:38:54, ten minutes later. This board has since printed „the channel is archived and un-archiving is a click only Ivo can make“ on four consecutive passes. Retired. The row has a surface and both people are in it. ✅ The page itself is unchanged and correct: restored to the same address she already sent, byte-verified at 200 / 1,864,663 bytes, hash identical both to local and to the pre-take-down hash recorded on 25 Aug, so the owner sees the exact page rather than a rebuild. ⚠ What is genuinely still open is one question and one send, both hers: 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 of them, the page shows them a shop that is not theirs. Ask, then send. Price and send are hers, sub-1k. Day 5. Elena

✅📥 CLOSED TODAY AFTER SEVEN DAYS - THE OWNER’S CORRECTION IS APPLIED AND LIVE, AND THE HOLD THAT KEPT IT WAITING WAS THE RIGHT CALL. Ivo dropped the four missing plan images into the shared exchange folder at 12:20, seven days after the owner sent them, and the block fell the moment they arrived. The corrected figures and the corrected drawings shipped together, exactly as ruled on 28 August: 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, plus the second model’s two floor plans and the seven-plot site layout. ✅ The standing rule earned its keep and should be read as a win rather than as lost time: figures and the drawing they are read off are ONE claim, so shipping the digits alone would have put a page in front of buyers whose numbers and plans disagreed. Seven days of waiting bought a page that is internally consistent. ✅ The same afternoon produced a ten-piece social pack for her, seven graphics and three written pieces, produced and handed over, deliberately not published - our own publishing rail sits behind a platform review that waits on the company registration, and we hold no access to her channels, so the posting is hers. ⚠ Recorded as care work delivered, not a money item: this row is free by decision and there is no ask outstanding on it. Ivo

⚠📧 NEW - A CLIENT’S NEW CONTACT ADDRESS SHIPPED CORRECTLY AND THEN RENDERS ONLY IF SCRIPTING IS ON. ONE WORD FROM THE REP DECIDES IT. Both of her 31 August answers were executed and byte-verified: the old address was replaced everywhere, including inside the form’s own mail link, with zero occurrences of the old one left, and the ownership sentence she asked to remove is gone in both languages. ⚠ The residue is a hosting-layer feature working exactly as designed against us: the host obfuscates e-mail addresses in the page source, so on her own domain the new address is assembled by script and a visitor with scripting off sees nothing there. Not a defect and not urgent - it is a choice between an obfuscated address that most visitors see and a plain one that every visitor sees and every harvester also sees. Her call, one word, and it belongs to the rep because the brand and the contact route are hers. Elena

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, sixteen days. ⚠ Eleventh 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. Ivo / Elena

💵 UNRULED AND UNBOOKED COMMISSION LEGS - THE MONEY BOOK HAS NOT MOVED SINCE 23 AUG, DAY 11. (a) The hotel-services annual care €200 - 40% to the rep, or excluded as an owner-collected account? Unruled since 04 Aug, 30 days. (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 and not yet written into the structured file at all. (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; if all three stack, €390 of the €600 and €36.75 of the €49 go out and the company keeps €12.25 a month. (g) 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 35 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 18, 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, and both figures were asked of the rep in writing on 25 and 26 Aug and are still unanswered. 🔴 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 11 LIVE ON THE CLIENT’S OWN BRANDED DOMAIN WITH NO CONTACT PATH AT ALL, AND ITS THREAD IS PAST ITS LAST TOUCH. Re-measured this morning and byte-stable for a seventh 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 on exactly this ground: the row is owed a commercial answer, not a „did you see the site“. 🔴 It is day 17 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

⚠⏯ A REFUSAL THAT SAID „FOR NOW“ IS BEING CARRIED AS STOPPED RATHER THAN CLOSED, AND ITS PAGE IS STILL LIVE. The tyre row was stopped on 30 Aug 17:32:14 in the rep’s own words, and the channel was archived ten seconds later. Read deliberately as STOPPED, not closed: her wording is „for now“, and the pizza row is the proof that this state comes back. The reason was never given and is filed as MISSING rather than guessed. ⚠ It is the expensive kind of loss: the page shipped on 23 June, was reworked on her own feedback, reshipped on 26 June, and a partner phoned to chase it. Its host still answers 200 at 52,630 bytes, untouched. 🔴 It is the second channel archived at a refusal in a week, which is the recurring cost the one-sentence rule above exists to end. Elena

🔄 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 15 - 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, and no send of any kind happened in the window. They stay live, unpatched and unsendable until the numbers are static markup. Ivo

📌 SMALL OPEN ASKS THAT BELONG TO THE REP, DELIBERATELY NOT ESCALATED - AND THE FIELD CAME BACK THIS EVENING AFTER TWO AND A HALF DAYS. 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, whether a third client’s verbatim quote may be touched, and now the plain-versus-obfuscated address question above. 📥 Seven questions for the Дупница club row remain unchaseable until the send gate at the top is ruled. 📥 The 31 August builds still 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 the cleaning row, 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. ✅ The field reopened at 17:46 this evening after two and a half days of silence: three notes in eight minutes - a new demo request, a request for her referral code, and a follow-up. All three were answered the same hour. 🔴 One of her rows is now three days without an answer from US, not from her: the Nesebar hotel that already has a live site has been sitting on „awaiting her word“ since 31 August. It was put back to her tonight as a one-word decision - the site works but mentions reservations nowhere, so it is the same rebuild pitch, and „go“ starts the build while „no“ closes the row. Elena

🔴 TWO INBOUND REQUESTS FROM 22 AUGUST ARE STILL UNBUILT - DAY 12. 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 a twelfth day. Ivo

✅ SITE HEALTH RAN AND THE PORTFOLIO IS SOUND. No action asked; recorded because the warnings resolve to two cheap families and one of them is a single file. Stamped 2 September 11:11 BG: 100 live sites, 83 OK, 17 warnings, 0 failures. Nothing down, no payment link dead. The warnings have three root causes and none is a client-facing fault. (a) Eight of our own internal pages, five of them partner-facing, all flag the same missing shared logo image - one file fixes all eight. (b) Seven unarmed redirects, where a working address and its temporary one both serve the same page beside a paying client’s own domain: duplicate content and a search-ranking risk rather than an outage. (c) Two broken external images, both already named on this board - one guest-house preview card pointing at a dead host, and one third-party photo host refusing connections on a speculative page. Nothing in the run touched the revenue base. Ivo

⚠ THE COLD-INVENTORY COUNTER IN THE SPINE IS FIVE DAYS STALE AND MUST NOT BE QUOTED AS CURRENT. No action asked; recorded so a later run does not print the wrong number confidently. The spine’s own figure, ~110, was last updated on 30 August - before five pages were built on 31 August and before three of them were sent on 1 September. The board figure of ~113 above is the corrected carry, not the spine’s number. ⚠ Two more record-hygiene items in the same file, both harmless today and both capable of producing a wrong read later: two revenue clients each appear twice, once current and once superseded, so the table holds 19 physical rows against a header that correctly says 17; and the two most recent losses are not filed in the declined section at all - the Plovdiv motel closed lost on 1 September and the tyre row stopped on 30 August both live only in the in-flight table. A do-not-chase list that does not carry the two newest do-not-chase rows is the exact shape that produces a re-pitch. Ivo

✅ PROCESS - THREE RECENT CORRECTIONS ARE THE SAME MISTAKE IN THREE COSTUMES: AN INSTRUMENT TRUSTED WITHOUT CHECKING WHAT IT WAS MEASURING AGAINST. No action asked; recorded because today added the fourth and worst instance. A registry promised an answer in five working days and this board counted calendar days, on a Monday that was a bank holiday. 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. A send log silently dropped three sends because the registry it validated against was stale. ⚠ And today: an accounts alarm survived three runs because the register was lagging and because the correction lived in a message this loop does not read. The durable form: an instrument answers the question it was pointed at, not the question you asked, and a deadline is a rule plus a calendar, neither derivable from the other. ✅ Every one of the four was caught by a human opening the source and reading it. 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; the pizza owner who refused on 25 Aug and came back on 30 Aug of his own accord; and 1 September’s three sends, which produced a same-day design brief in three and a half hours, a flat refusal in ten, and one silence. ⚠ The Plovdiv motel is the third data point against freshness specifically: fifteen hours from build to send, the freshest lag in the book, and a categorical no. 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. It bears on the ~113 rows behind them. Ivo

PROCESS - A REAL CLIENT AT CLOSING STILL HAS NO CHANNEL. Carried, and unchanged by definition: no channel was created or archived anywhere in the window. 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. ⚠ The roster is carried at 124 and deliberately not re-enumerated, because the search behind it is relevance-ranked and cannot produce negative evidence - it can confirm a channel exists and can never prove one does not. That method was retired on 30 August and the retirement holds. 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. ⚠⚠ THE FIGURE IS A CORRECTED CARRY, NOT A FRESH COUNT, AND THE SPINE’S OWN COUNTER IS FIVE DAYS STALE AT ~110: it was last updated on 30 August, before five pages were built on 31 August and before three of them were sent on 1 September. Do not quote the spine number as current. ⚠ THE PILE MOVED TODAY IN BOTH DIRECTIONS AND NEITHER MOVEMENT WAS A SEND. One row left it downward - the refused Plovdiv motel’s demo was taken down to a 608-byte stub - and one new row is queued to enter it tonight, a Nesebar family hotel requested by the rep at 17:53 and scheduled to build at 19:15. 🔴 So on a day of eight delivery acts the selling column is still zero: nothing was sent, nothing was priced, and the pile is the same size it was this morning. The last real movement was 1 September: three out, two of them answered inside 24 hours, one with a design brief and one with a flat no. 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, the reopened pizza row now has an un-archived channel and both people in it so it needs one question and a send, while the Дупница club is held at a gate and cannot be worked down by anyone else, day 5, and one further request was correctly held before code because that business already has a live site. ✅ The tail’s strongest evidence is still 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 three and a half 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; the one priced send of last week carried a seventy-six-day gap and is silent on day 5; and the Plovdiv motel, the freshest send in the book at fifteen hours, produced a categorical no in ten. 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: 36 addresses curled from a clean scratch directory with caching and compression defeated, 34 answering and 2 Not Found, and both 404s are the named dead sent hosts already on this board. No unexplained failure anywhere, and only one host on the whole list changed by a single byte - the repaired club page. ✅ The portfolio sweep of 2 September read 100 live sites: 83 OK, 17 warnings, 0 failures, the warnings resolving to eight of our own internal pages flagging one missing shared logo file, seven unarmed redirects, and two already named here. Nothing in it touched the revenue base. 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. ⚠⚠ One caution the last two days added, 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, and it was found by the owner rather than by any instrument we own. 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

⚠ NOTHING NEW ARRIVED HERE TODAY, BUT ONE ROW THAT BELONGS HERE WAS FINALLY EXECUTED ON. ✅ The Plovdiv motel’s demo came down this morning, 36 hours after the refusal: snapshot taken first and matched byte for byte against the local copy, the address now serving a 608-byte unbranded no-index page with zero brand residue, and the neutral preview card in place of theirs. Restore is one command and byte-exact. ⚠ Two caveats recorded rather than smoothed over: the object could not actually be deleted because our hosting token is scoped too narrowly, so the address is held by a stub rather than released, and the channel was already archived so the completion could not be recorded where the refusal was. 🔴 Record defect still unfixed and it is the one that produces a re-pitch: the motel and the tyre row, stopped on 30 August, both live only in the in-flight table above and neither is filed in this section. A do-not-chase list that does not carry the two newest do-not-chase rows is exactly the shape that puts a demo back in front of someone who already said no. 🔴 THE MOTEL IS A GENUINE MARKET ANSWER AND SHOULD BE READ AS ONE: 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, off the freshest build-to-send in the book. Its page carried no price and no named defect. ⚠ Its page is also still live at 678,018 bytes by doctrine, because their public listing publishes no website, and there is no longer a channel in which to record that - the concrete cost of the unanswered archive rule. ⚠ The tyre row is STOPPED rather than closed: the rep’s own words are „for now“, its page is still live and untouched at 52,630 bytes, and the reason was never given and is filed as MISSING rather than guessed. ✅ The children’s-party row is CLOSED BY THE CLIENT, not by a cadence. She told the rep at 11:25 on 1 September 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. It was never sent, so no send event was written - a closure, not a touch. The host correctly returns Not Found at 766 bytes, which is the earlier agreed take-down, not a defect. Nothing is invoiced, nothing is chased, nothing is reminded, and the row stays reversible if she ever registers a company. ⚠ The Фарзандо and Божура rows are past their last touch at day 18 and the financial-services row at day 17, and nothing 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. 🔴 Read those three 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 eighteen 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, its channel was un-archived the same morning and both people are in it. 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. ⚠ One record inconsistency to fix while you are in the file: the warm table still shows her page answering, which contradicts the verified take-down here. The take-down is the true reading. ✅ 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 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. ⚠ 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. 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 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; 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 31 days unanswered, and the rep’s €35 of that client’s cash still to be remitted, which the churn does not cancel. 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