Client Journey & Loop Board

🔴 THE HEADLINE: BOTH PAID CHECKOUT LINKS ARE STILL OPEN, AND IT IS NOW TWO CUSTOMERS. The sports club link paid on the 7th, day 2 open, and the German guest house link paid at 18:02 on the 8th, open since the moment it worked. Both read as active on the money account this morning. These links are reusable by design: a second click by the same person creates a second subscription on the same customer, 29 a month on one and 49 a month on the other. The precedent is in this very book, one client paid 400 twice and it had to be refunded. ⚠ The risk is highest on the German row right now, because a stale send pack still points a rep at that link. Two taps, and the durable fix is a habit: retire the link the moment the subscription goes live. Ivo

🔴 NEW, AND IT IS THE SHAPE OF FAILURE THIS BOOK KEEPS PAYING FOR: THE RULING WAS MADE, THE MONEY ARRIVED, AND THE FILES A FRESH SESSION READS FIRST STILL SAY OTHERWISE. Three live instances, all measured this morning rather than recalled. (a) The send pack still reads „ready to send as written, 54 days late“ for the German guest house, with the link and the old 58.80 figure, and she has already paid 58.31 and has a live subscription. (b) The start-here file still lists „send her link“ as remaining work. Both files are untouched since 13:50 yesterday, and both instruct a fresh session to read them first. (c) The money book was rewritten this morning and its gym-club row still calls a confirmed 250 „a claim, not yet confirmed“, against the human ground-truth file where it was confirmed verbatim on the 7th. This has now cost twice in three days: a decision recorded where decisions live, never carried into the artefact that gets read, produced „still blocked“ in a client channel twice AFTER the price was ruled. Three file edits, and not one of them needs a decision. next ops run

🔴 CARRIED AND NARROWED BY ONE, THE BEST WAY POSSIBLE: THREE MESSAGES ARE WRITTEN, UNGATED AND STILL UNSENT. THE FOURTH CLIENT PAID WITHOUT EVER RECEIVING HERS. ✅✅ That is the finding, not a footnote: the German guest house had waited 55 days for a link nobody sent, found her own way to the checkout and paid. What is left is the psychology practice (site live on its own name since early August, day 41, 29 a month never once billed), the gym club (own domain live, monthly link reissued and now carrying its attribution chain, never sent) and the music studio (own domain live, day 9, link active, unsent). The pizzeria is the honest exception and stays out of this count: no domain and no name proposed, so its monthly genuinely cannot start. The blocker is not a company, not a rail and not a price. It is three messages. Ivo

🔴 CARRIED AND STILL THE HIGHEST-VALUE UNWORKED ITEM ON THE BOARD: TWO HAPPY CLIENTS WITH LIVE FREE SITES HAVE NEVER BEEN ASKED WHICH MONTHLY THEY WANT. ELEVEN WEEKS. Both were offered a choice of two monthly figures on 22 June and the choice was never actually put to either of them. There is no link to send because there is no number, and there is no number because nobody asked the question. Both sites are live and verified. This is the cheapest revenue on the board and it costs one message each. Ivo

🔴 SHARPENED OVERNIGHT AND NOW HAS A DELIVERED INSTANCE ATTACHED: WHAT DOES 19 A MONTH ACTUALLY BUY? Two facts landed on this question in one day. (a) The gym club DECLINED the ten-a-month content planner, so its monthly is plain care at 19 and the „fifteen posts“ scope dies with it. ⚠ That decision is recorded on the link and in the money book and NOWHERE in the client’s own channel. (b) On that same unbilled 19, a twenty-visual marketing pack was asked for at 13:48 and delivered at 14:35, forty-seven minutes, to impress the client into buying more. The client has been billed zero. ✅ Two gates were honoured inside that delivery without being asked: frames showing recognisable probable minors were excluded outright with no consent on file, and share-alike stock was refused in favour of generated frames because a visible credit line is a licence obligation. The open question is not the price, it is the scope, and „so she buys more“ is a real upsell direction with no number behind it. Ivo

🔴 CARRIED, DAY 3, AND IT SURVIVED THE BIGGEST RULINGS SESSION THIS BOOK HAS HAD: A COLD RECORD ADVERTISES A NEEDLE PROCEDURE FOR EYE DISEASE, AND NO BUILD WAS STARTED. A traditional-medicine clinic whose own public introduction names, verbatim, a needle treatment for a growth on the eye and for glaucoma, plus bone-setting and post-natal heat treatment. The business has asked us for nothing; this is an internal cold submission. Reproducing that copy puts a regulated health claim on our own infrastructure under our own badge, in a country that licenses it. The animal and adult categories were escalated for exactly this shape and were ruled; this class never has been, and it is absent from the rulings record entirely. The decision needed is the general one rather than the row: do we build sites carrying medical treatment claims at all, and if yes, under what wording limit. If yes, facts only, never the disease list. No build was spawned and none will be. Ivo

🔴 CARRIED, DAY 19, AND IT STOPPED BEING THEORETICAL LAST NIGHT: THE PARTNER-PAGE COMMISSION CUT WAS NEVER DEPLOYED, AND NOW THERE IS REAL MONEY BEHIND IT. The local file has read the corrected rate since 20 August; the live page has never carried it and measured byte-identical for a sixteenth consecutive time. 🔴🔴 What changed is that the German guest house is now paying, so the introducer share on that chain is money moving through a page that still promises the old, higher rate. This is not a request for a decision. The decision was made nineteen days ago and the file that carries it to the world was never pushed. Ivo

🔴 CARRIED, DAY 25: A PAGE FOR THE WRONG BUSINESS IS STILL SERVING BESIDE THE CORRECT ONE. Both addresses re-measured this run and unmoved, the retired one at 1,316,093 bytes beside the correct rebuild at 1,513,920. The question underneath it is day 18 unanswered and it is one message to the rep: which of the two links did she actually send? Until that is answered nobody knows whether a real prospect is looking at another company’s page under our badge. Ivo / Elena

🔴 CARRIED: THREE PAID CARE CLIENTS RECEIVED NOTHING VISIBLE IN AUGUST, AND AUGUST IS CLOSED. A missed cycle on money already taken rather than a countdown that can still be met. Two of the three channels have now been silent 47 and 36 days. ⚠ The consequence is ruled and unapplied: the recurring partner share is contingent on care actually being delivered, so a month with no delivery is also a month with no entitlement, and nothing computes that yet. Ivo / Elena

🔴 NEW, AND IT IS A CLIENT-STATE RISK RATHER THAN HOUSEKEEPING: THE BRAIN’S OWN INDEX IS OVER ITS CAP, AND THE PART AT RISK IS THE DO-NOT-SEND LIST. The index stands at 20.2 KB against its own 17.1 KB target and a hard read limit above that, and its own header says the tail goes invisible past the cap. The tail is the client section: the do-not-send rows, the clients who already refused, and the rows ruled free by decision. If that tail truncates, a session can re-pitch a client who refused or invoice one that was given the site free, which is precisely the class of error this whole book spends its ink preventing. ✅ Correctly NOT compacted inside a sweep, because a rushed lossy compaction is a worse failure than one more run over the cap. What is needed is a dedicated pass, and that is a scheduling call. Ivo

🔴 CARRIED, SEPARATE, AND NOT TO BE DOUBLE-COUNTED WITH THE INCORPORATION: THE OTHER ENTITY’S DIRECTOR IDENTITY VERIFICATION IS 23 DAYS PAST. A separate statutory obligation from the accounts, and nothing else on this board covers it. ⚠ That entity is now closed as a client rail and is read-only, but being closed as a rail does not discharge a filing obligation on a company that still exists. ⚠ The accounts alarm stays WITHDRAWN and must never be restated. The one line that would stop this being re-derived every single run is a human sentence in the ground-truth file, and only a human may write it. Ivo

✅ CLOSED ON THE WIRE, AND IT WAS A PHANTOM ON BOTH ROWS: THIS BOARD REPORTED A CLIENT-FACING OUTAGE THAT NEVER EXISTED, FOR 23 DAYS AND 18 DAYS. Two prospects were recorded as holding dead links. Both were measured properly last night and both are fully alive, at 2,584,579 and 509,985 bytes. The addresses this board kept checking were slugs we invented ourselves; the real hosting projects are named differently from the client folders, so the check was measuring something that was never sent to anybody. The correction and the apology were posted in the client channel. Three consecutive reconciles copied this forward. ✅✅ The rule it buys is worth more than the two rows: never check a client’s health against an address this book invented. Resolve the address from the client’s own channel, because that is the link they actually hold. Ivo

✅ MATERIALLY CLOSED AND NOBODY ANNOUNCED IT: THE CLIENT SITE WITH NO CONTACT PATH NOW HAS ONE. It measured byte-stable at 74,332 bytes for fourteen straight checks with zero call links, which was the whole substance of the item and the reason a nudge was held for eighteen days. It now measures 472,641 bytes and carries a working call link. ⚠ A mail link is still absent. The root cause is worth keeping: the blocker was three of the client’s own documents sitting as cloud placeholders in the shared store, unreadable to us for fifteen days for exactly the same reason a logo was unreadable for thirty-one hours last week. Ivo

⚠ NEW, SMALL, AND ON A PAYING CLIENT: ONE OF THE THREE NEW DOMAINS DID NOT ARM ITS REDIRECT. The sports club’s own domain is live and correct, but its old preview address still serves a byte-identical full copy where the other two go-lives both redirect properly. ✅ Stated at its real size: the canonical tag and the share tag on BOTH addresses point at the real domain, so no search authority is split and nothing is wrong for the client. It is an inconsistency and a loose end on a paying row, not a defect, and it is the same unarmed-redirect line the site-health audit has carried in its warning bucket for weeks. One tap. Ivo

⚠ CARRIED, DAY 10, AND THE ANSWER SPLITS CLEANLY IN TWO: WHAT HAPPENS AUTOMATICALLY AT A REFUSAL? ✅ The page half is solved and stays solved: the Rhodope villa was refused at 16:02:40 and its page was stubbed and byte-verified by 16:17, about fourteen minutes, against 41 hours a fortnight ago. 🔴 The channel half is not: the same channel was actually archived 27 hours after the rep announced it, and by the rep herself. Eleven channels have now been archived at a refusal since this question was raised, every single one by hand. The counter-precedent is already paid for: one client refused in August, the channel was archived, she came back by herself five days later and the link had been lost. One standing sentence: does a refusal take the page down automatically, does the channel get archived, or do both wait for a human? Ivo

⚠ CARRIED: THE SEND ENGINE IS ON DAY 4 OF WAITING FOR ONE WORD, AND THE SENSOR IS ON ITS EIGHTH RUN OF NOT EXISTING. The eight aged-out rows are handed over as a single choice, nudge for one late touch or ladder for a day-30 success-story touch, drafts ready either way. ✅ The day-3 approve queue is empty for a third day and the one-nudge cap is provably intact, because the nudge event still counts zero in the acts log. 🔴 The hot-signal reading is zero for the eighth run, and that is the absence of an instrument rather than the absence of interest: the interest sensor was never deployed, blocked on one hosting token. Zero hot means no sensor, and it must never be read as no demand. Ivo

⚠ CARRIED: EIGHT PARTNER-ADJACENT PAYMENTS, ZERO INDEPENDENT CLIENT CONFIRMATIONS. The confirmations file is 221 bytes and has never been used, and every one of those payments rests on one person’s word in a chat message. ✅ The historic pile itself is CLOSED and must never be re-entered: the settlement of 161.60 agreed by both sides on 7 September is the opening balance. What survives is forward-looking and it is now live rather than theoretical, because two subscriptions are running and both carry a partner chain that will owe somebody money next month. The mechanism that confirms a client actually received what a partner is paid for does not exist yet. Ivo / Elena

⚠ CARRIED: THE PERSON WHO DOES ALL THE SENDING CANNOT SEE ABOUT NINETEEN CLIENT CHANNELS, TWELVE OF WHICH HOLD SENT OUTREACH. There is no interface call that adds somebody to an existing channel, so this is manual clicks and it has stayed manual for weeks. Twelve channels holding live outreach that the person responsible for the reply cannot read. ⚠ One channel was created this window and its membership was not directly checked, so the gap may have grown by one; that is stated as unknown rather than claimed either way. Ivo

⚠ CARRIED: TWENTY-SEVEN LIVE PAGES FOR REAL BUSINESSES IN CHON BURI HAVE NO CHANNEL OF ANY KIND. No record, no counterparty, and nowhere to write a send even if somebody made one. Seventeen further pages were sent in one batch in August with no channel record and no confirmed clock, every row still unconfirmed. These are not inventory anybody can work; they are inventory nobody can even record work against. Ivo

⚠ CARRIED: A HOSTING ADDRESS THIS VENTURE RELEASED IS BEING SERVED BY A STRANGER, AND TWO BRANDED PAGES ARE LIVE THAT NOBODY REFUSED. One preview address that used to hold one of our client demos now serves an unrelated foreign business portal. Nobody did anything wrong; the address was simply given up and somebody else took it. Hence the standing rule that a project is stubbed and never deleted, so the address stays held. ⚠ The two branded pages that are still live are deliberately left alone because they are not refusals, one retired in July whose own record says pull on the owner’s word, one a superseded build under a do-not-send. A sweep that starts pulling pages nobody refused is the worse failure. Ivo

⚠ CARRIED: A SITE THE REP SHOWS TO PROSPECTS STILL CARRIES A LOGO TILE LINKING TO A SWITCHED-OFF SITE. Re-measured rather than recalled: the page is byte-identical for a sixth consecutive check, and the brand still appears inside the logo wall pointing at the paused scooter site. One link, one edit, no approval needed, and the client behind that logo is cancelling anyway, which makes the removal easier to decide rather than harder. next ops run

⚠ CARRIED: THE REP’S OWN BRAND CHANNEL HAS AN UNANSWERED QUESTION FOR THE SIXTH CONSECUTIVE RUN, AND THE ANSWER IS FREE. Read in full, her report quotes a third-party questionnaire tool’s own warning that it cannot send from her domain because the domain’s mail records point elsewhere. That is not a defect on the page we built, and the page itself measures unchanged. Under the standing default-allow posture, answering her is automatic and needs no gate. ⚠ Her channel was not re-read this run, so the age is carried rather than asserted. next ops run

⚠ CARRIED AND NARROWED BY A HUMAN STATEMENT: THE PRINTED REFERRAL POSTERS. ✅ The image codes were reissued and verified by decoding the picture back. ❌ The eleven printed sheets still decode to an address that has served English to everybody since the language change in August. ✅✅ Latent rather than live: the estate is empty, zero codes are in the wild, so nobody is being sent to the wrong language today. Interim instruction unchanged, hand out the Bulgarian address by hand until the sheets are regenerated. next ops run

⚠ CARRIED: ONE MISSING IMAGE FILE IS BREAKING EIGHT PAGES AT ONCE, FIVE OF THEM PARTNER-FACING. The brand logo has returned Not Found for weeks and every one of those pages loads it. One file. ⚠ Also standing in the same class: two pages marked do-not-send carry animated review counts and are missing the attribute that stops a browser auto-translating a factual number. next ops run

⚠ CARRIED FROM THIS MORNING AND DELIBERATELY NOT RE-DERIVED: THE MAP-DATA PROVIDER’S KEY IS REFUSING EVERY REQUEST. The town-scan script and the „does this business already have a site“ pre-check both depend on it, and both are dead until the key is fixed. ✅ There is a working fallback path already in the tools folder and the last town scan ran through it successfully, so this closes the cheap top of the funnel rather than the funnel itself. ⚠ Stated as carried rather than measured: the nightly spine does not track this, so its age here is inherited from this morning’s pass, not re-checked. Ivo

⚠ CARRIED, PROCESS: THE COMMISSION LEGS ARE COMPUTABLE RATHER THAN ARGUED, AND THIS WEEK THEY BECAME REAL. ✅ What is fixed is the POOL, 30 percent of the build and 40 percent of the care; the split inside it is ruled per chain and reflects who actually did what, so shares are DIVIDED rather than stacked. ✅✅ Both live subscriptions now carry their chain on the subscription object itself, so for the first time a monthly partner share can be computed from the money rather than from a conversation. ⚠ Two rules that govern every figure and are easy to get wrong: the partner share is a percentage of the NET, never of the amount charged, and tax is added at the CUSTOMER’S country rate, which is why the German charge came out 0.49 below what every artefact predicted. ⚠ A new seller joined under the rep this week; her build share resolves inside the pool consistently, but her first town is cold and scraped, so the build is free and 20 percent of nothing is nothing, and the care split for her is unruled. Ivo

⚠ CARRIED, PROCESS: A CHURNED CLIENT HAS THREE CLEAN-CLOSE DECISIONS OUTSTANDING FOR 39 DAYS. The domain, the site and roughly 80 of remaining instalments, plus 35 of that client’s cash still to be remitted, which the churn does not cancel. ✅ The client is confirmed not active, so this is a write-off decision rather than a collection. It is small, it is stale, and it is three sentences. Ivo

⚠ PROCESS, TWO SMALL ONES HELD TOGETHER SO THEY DO NOT GET LOST. ✅ The shared file store still holds hundreds of cloud-only placeholder files across dozens of folders, none of them blocking an open request today, but a file that is a placeholder at the moment a run reads it is exactly how a client’s own menu went missing for thirty hours last week and how a live contact defect stayed unfixed for fifteen days. The hydrate step before any read is the fix and it is already written. ✅ And the second: a scheduled task that runs is not a task that produced anything, proven again this week when a one-off fired, wrote an analysis document instead of changing the page, and read as a success in the log for thirty hours until the client’s own rep caught it. The re-run was spawned with the failure condition stated explicitly, which is the pattern to keep. next ops run

⚠ OPEN STRATEGY QUESTION, NO ACTION ASKED, AND THIS WINDOW PUT REAL WEIGHT ON ONE SIDE OF IT. What actually converts a cold send. Sixteen days produced eight Bulgarian refusals, three of them inside fifty minutes, against a thin trickle of warm replies. ✅✅ Against that, the two things that have actually produced money are neither of them cold: a page put personally into a partner’s hands, and a client who was so far along that she found the checkout herself and paid without being asked. Both paying rows on this board arrived through a relationship rather than through the pile. ⚠ The counter-argument the pile still has is speed: a lead became a sent demo in five and a half hours this window, the fastest in the book, and it was warm. The honest reading is that the factory is not the constraint and never was; the constraint is whether a human hands the thing over. 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, flat, nothing in and nothing out. ✅ The one build that shipped this window never entered this pile at all: it was warm, and it was sent the same evening. Still about 23 times the standing cap of five, and the twelfth consecutive run over it. ⚠ Not all of these rows are equivalent inventory: the steam-cleaning row, the Kirkovo hotel and the Sandanski hotel are the rep’s to send with no owner gate, one sports club is held at a gate and cannot be worked down by anyone else, and the one September build is hers and unsent at day 5. ⚠ Eight further rows sit in the send engine’s aged-out queue on their fourth day of waiting for one word, which is the difference between inventory nobody has decided about and inventory somebody has. 🔴 And the cheap top of this funnel is still closed: the map-data provider’s key is refusing every request, so the town scan and the „do they already have a site“ pre-check both run only through the fallback path. ✅ 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 made one. 🔴 What the last sixteen days added to the strategy question, and it cuts against the factory: eight Bulgarian refusals, three of them inside fifty minutes. The refused rows were not the stale ones: one was sent three days after it was built, one eleven days, one had already been rebuilt once at the owner’s own request, and the newest was five days old and had never carried a price at all. ⚠ Lag was the hypothesis and lag has now been controlled for. Price has been controlled for too, because the eleven-day refusal went out at the figure that is now the floor itself. ✅✅ The counter-argument got its strongest night yet: both paying rows on this board came through a relationship rather than through this pile. One was a page handed over personally by a partner; the other was a client so far along that she found the checkout and paid without being asked. Nothing in the 113 is worth as much as those two conversations were. ⚠⚠ One caution the refusals sharpened rather than introduced: a sent link never changes, so every later revision reaches the prospect the moment it deploys, with nobody pressing send. 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. ✅✅ And the second caution of the same family, which this window extended in BOTH directions: a row that says a page was taken down is not evidence that it was, and a row that says a link is broken is not evidence that it is. Two rows carried for weeks as broken client links were measured properly and had never been broken at all. The host is the evidence, never the row, and it has to be the host the CLIENT was actually sent. The assignment model is unchanged, one sheet per rep, with the sweep folding statuses back into the spine. Ivo

✅ NOTHING WAS ADDED THIS WINDOW, AND FOR THE FIRST TIME IN A FORTNIGHT NOTHING WAS REFUSED EITHER. ZERO REFUSALS. One row was completed rather than opened: the Rhodope villa’s channel was archived at 19:27 on the 8th, 27 hours after the rep announced it, while its page had already been stubbed and byte-verified in about fourteen minutes. That takes the running archive-at-a-refusal total to eleven, every one by hand. Ten addresses across seven refused clients, every one confirmed at 608 bytes with zero brand residue for name, town and telephone checked separately, and no neighbour’s content leaking in. Zero branded pages are live on any refused row. ✅✅ The newest close is still the standard to beat: a refusal at 16:02:40 and a byte-verified take-down by 16:17, against 41 hours a fortnight ago. The difference was the intake waterline, not the effort. 🔴🔴 THE FINDING TO KEEP IS STILL THE UNCOMFORTABLE ONE: auditing every refused row on the board, not just the newest, found TWO OLD CLIENTS WHOSE PAGES WERE STILL FULLY BRANDED AND SERVING THEIR OWN TELEPHONE NUMBERS. One refused in August, twelve days, on a row that already read „demo taken down“. One declined in July, fifty days, on a row that claimed its address had been released, which was simply untrue. The rule that comes out of it is short: the host is the evidence, never the row. ✅✅ AND THIS WINDOW PROVED THE RULE CUTS THE OTHER WAY TOO, WHICH IS THE HARDER HALF. Two rows carried for 23 and 18 days as „this prospect is holding a dead link“ were measured against the address the client was ACTUALLY sent and both were fully alive. The dead addresses were slugs this book invented for itself. The correction and the apology were posted in the client channel. Over-reporting a defect costs the rep’s trust exactly as over-reporting a take-down costs the client’s. ⚠ And a brief can be wrong about the size of its own job: one named three addresses and the real exposure was five, because two clients were live on a second address recorded nowhere. ✅ How every take-down is now done, and it is the standard: snapshot the live bytes first, stub to a 608-byte unbranded no-index page, restore the local source and re-hash it, then verify by bytes rather than by a status code, grepping brand residue per client for name, town and telephone separately. Restore is one command and byte-exact. ⚠ Hosting projects are deliberately never deleted, only stubbed, and one address this venture DID release now serves a stranger’s unrelated business portal. ⚠ Two pages that are live and branded were deliberately left alone because they are NOT refusals, one retired in July whose own record says pull on the owner’s word and one superseded build under a do-not-send. A sweep that starts pulling pages nobody refused is the worse failure. ⚠ The tyre row is confirmed NOT ACTIVE, so its remaining instalments are a write-off decision rather than a collection, and the rep’s 35 of that client’s cash is still to be remitted, which the churn does not cancel. ✅ The children’s-party row is CLOSED BY THE CLIENT and was never sent. ✅ A hotel in the old town was answered with a flat no before anything was built, so there was never anything to take down. 🔴 The hair-and-beauty centre stays CLOSED LOST after only seven days. ⚠ A refusal on this board is not proof of a terminal state; it is proof of a state on that day - the pizza row reopened itself once and then refused again, which is the honest version of that sentence. ⚠ One instruction for every future sweep: pages that return a 608-byte stub or Not Found in this section do so BY DESIGN. They are client asks honoured, not dead objects. 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