Client Journey & Loop Board

🔴 THE WHOLE OF THE MONEY QUESTION IN ONE LINE: SIX LINKS ARE MINTED AND ACTIVE, ONE HAS BEEN PAID, AND FIVE HAVE NEVER BEEN SENT. Read live off the account this morning, not carried. ✅ The sports lab paid EUR 57.60 last night and her EUR 29 a month is active and renews on 7 October. 🔴 The other five: the psychology practice, day 40 live with care never once billed; the German guest house at the ruled EUR 49, whose owner is on day 54 of asking for a way to pay and roughly EUR 87 of whose care has never been invoiced; the gym club, which now has a live domain and therefore no remaining reason to wait; the music studio, day 8; and the pizzeria, which is honestly still domain-gated and is the only one of the five with a real blocker in front of it. ✅✅ The rule that unblocked two of them fired yesterday: care starts one month after the build and only once the domain is live. Both domains went live at 16:24 and 16:25, so the stated reason expired on both and neither has been told. ⚠ The guest house needs one sentence written before she clicks: the price is ruled at 49, the 40 offered verbally does not stand, and she may well remember 40. The price is settled; how it is said is not. ⚠ Every message carries „plus tax“. Ivo

🔴 NEW AND IT COSTS MONEY EITHER WAY: TWO DIFFERENT DOMAINS WERE DECIDED FOR THE SAME CLIENT SIX HOURS APART, AND THIS MORNING’S OWN INSTRUCTION SAYS TO BUY THE ONE THAT DID NOT SHIP. At 16:02 the rep named a domain, at 16:25 it was registered, bound and serving, and it was verified on the wire this morning at 200 with the canonical rewritten and the old address redirecting. 🔴 Then at about 22:00 the same evening the ruling record and the morning briefing both name a DIFFERENT domain as the decision, describe it as the client’s own stated preference, and instruct in the imperative that it is not yet registered and should be bought first thing. Following that literally this morning buys a second name for a client who already has one live, and then either wastes it or forces a domain switch on somebody who has waited 54 days. ✅ The naming constraint she gave is not breached by what shipped; it simply is not the name the later record decided. Two lines, one client, both dated 7 September. Only Ivo can say which one stands. Ivo

🔴 NEW, AND IT WAS ONLY VISIBLE BECAUSE THE ACCOUNT BECAME READABLE: THE ONE LINK WHOSE PARTNER SHARE IS ALREADY RULED IS THE ONE THAT RECORDS NOTHING. Three of the six links carry a full attribution chain in their own metadata. Three carry none. For two of those three that is correct, because they are Ivo’s own contacts with nobody in the chain. 🔴 The third is the rep’s, and her share was ruled on 7 September at 10 percent of the build and 20 percent of the monthly care. So the first care payment on that client will land with no machine-readable claim attached, on a row whose rate is no longer in dispute. The payments platform does not know any of the partners exist, which is exactly why the chain has to be written onto the link rather than inferred afterwards. ⚠ One metadata edit, before it is sent, not after. ⚠ And when it is computed: on the net amount, never on the amount charged. Ivo

🔴 NEW: A DOMAIN THE COMPANY PAID FOR YESTERDAY IS LIVE AND TELLING SEARCH ENGINES TO IGNORE IT. Read out of the served bytes this morning rather than recalled: the new guest-house domain returns a no-index, no-follow instruction, three occurrences. ✅ The hold was deliberate and correct practice, pending the German legal-notice obligation. ⚠ What is new is that the legal notice now appears thirteen times in the same served bytes, so the condition that justified the hold may already be met and nobody has re-checked it since the domain went live. A guest house on a brand-new name is invisible on day one, and the client is the one who waited 54 days for it. One look at whether that notice is now legally complete closes this. Ivo

⚠ NEW, SMALL, AND THERE IS A PRECEDENT FOR IT IN THIS VERY BOOK: THE PAID LINK IS STILL OPEN. The sports lab’s payment link remains active after the payment succeeded. These links are reusable by design, so a second click by the same person creates a second EUR 29 a month subscription on the same customer. ⚠ This is not hypothetical here: one client paid EUR 400 twice and it had to be refunded. One tap deactivates it, and the durable version is a habit rather than five taps: close a link once its subscription is live. Ivo

✅ YESTERDAY’S BEST OPERATIONAL RESULT, AND IT IS A LESSON RATHER THAN A TASK: A REFUSAL WAS ACTIONED IN ABOUT FOURTEEN MINUTES. The rep wrote „I have a refusal, stop the demo and I am archiving the channel“ at 16:02:40; the page was snapshotted, stubbed and verified by bytes rather than by whether it opens by 16:17. ✅ 608 bytes, no-index, preview image emptied, zero hits in the served bytes for the town, the business name or the telephone number, and the second possible address checked and confirmed not to exist at all. ✅✅ Compare 41 hours on 4 September and 12 and 50 days on the two rows the audit caught. The difference was the intake waterline, not the effort, and the waterline is now moving. The demo had been live and unsent for four days and had never carried a price, so nothing was quoted and nothing was lost but the build. Elena

🔴 CARRIED, DAY 3, AND IT SURVIVED THE BIGGEST RULINGS SESSION THIS BOOK HAS HAD: A COLD RECORD FROM PATTAYA ADVERTISES A NEEDLE PROCEDURE FOR EYE DISEASE, AND NO BUILD WAS STARTED. A traditional-medicine clinic whose own public introduction names, verbatim, treatments for a growth on the eye and for glaucoma, plus bone-setting and postpartum treatment. Those are medical claims in a country where advertising medical treatment is licensed and controlled, and reproducing their copy puts the claim on our infrastructure under our badge. ✅ The build was correctly NOT started, and the checking was done rather than assumed: the clinic appears nowhere in the 2,062 lines of the ruling record. The evening that ruled on tax, partner chains, the settlement, five domains and six links did not touch this. ⚠ The decision needed is the general one, not the row: do we build sites carrying medical treatment claims at all, and if so under what wording limit. If yes, facts only, never the disease list, Thai default with an English toggle. If no, the row closes. The animal and adult verticals were escalated for exactly this shape and were ruled; this class never has been. Ivo

⚠ CARRIED AND IT GOT SHARPER RATHER THAN SOFTER: THE STANDARD MONTHLY IS PROMISING FIFTEEN SOCIAL POSTS AGAINST A RULED TEN, ON A POSTING RAIL THAT DOES NOT EXIST. A 50 percent drift on the standard tier with no decision behind it. ✅ The delivery objection is already on the record in the client’s own channel: the automatic publishing channel is still waiting on platform review, group posting is no longer supported by that platform’s interface, so fifteen posts a month today is manual work rather than a system. 🔴 What changed this window is that the client now has a live domain and an active link, so the promise is about to start being billed against. Decide it before it becomes the reference price. Ivo

⚠ CARRIED, DAY 10, AND THIS WINDOW IS THE BEST EVIDENCE YET THAT THE MECHANICAL HALF IS FIXED: WHAT HAPPENS AUTOMATICALLY AT A REFUSAL? ✅ The watermark fix and the rule that a take-down is audited against the live address rather than against the table are both holding, and the running total is ten channels archived at a refusal since the question was raised. ⚠ The counter-precedent is still paid for: one pizzeria refused in August, its channel was archived, the owner came back by himself five days later, the rep had lost the link, and the row refused again on 4 September. What still needs one sentence is the policy, not the plumbing: does a refusal take the page down automatically and archive the channel, or do both wait for him? Ivo

🔴 CARRIED, DAY 18, AND IT IS THE LONGEST-RUNNING ONE-TAP ITEM ON THIS BOARD: THE PARTNER-PAGE COMMISSION CUT WAS NEVER DEPLOYED. The local file has read the new rate since 20 August; the live page has never carried it, and it has now measured byte-identical for a thirteenth consecutive time. This is not a record cleanup, it is a deploy that was never run, and the lesson is the one this venture keeps paying for: a local edit is deployed nowhere until the wire says so. ⚠ A partner’s EUR 120 on the guest-house chain is still gated behind it. Ivo

🔴 CARRIED AND CHEAPEST ON THE BOARD: TWO DEMOS THAT WERE SENT TO REAL PROSPECTS SERVE NOT FOUND, ON DAY 22 AND DAY 18. Neither was a take-down request; both are unintended, and both are still Not Found, re-confirmed at 766 bytes. One command each, and the machinery was demonstrably available and in use on the same days. ⚠ Read them beside the ten stubbed hosts and the shape is one defect twice over: this venture takes pages down that should be up and leaves up pages that should be down. The second half has now been fixed twice. The first half has not been fixed once. Ivo

🔴 CARRIED, DAY 24: A PAGE FOR THE WRONG BUSINESS IS STILL SERVING BESIDE THE CORRECT ONE. Both addresses re-measured this morning and neither moved a byte. The question underneath it is day 17 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 holding a page for somebody else’s business. Ivo

🔴 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 46 and 35 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 earned recurring share, and nobody has applied that to these rows. Delivery is the remedy, not a note. Ivo / Elena

⚠ CARRIED, AND YESTERDAY SHOWED WHY IT MATTERS IN BOTH DIRECTIONS: 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 after the fact. ✅ Three were confirmed by reading the account rather than by asking anybody, which is the control working for the first time. ✅✅ And the historic pile is now CLOSED by the settlement, which is an opening balance and must never be re-entered or re-chased. What survives is one collection, not a reconciliation. ⚠ The habit is the point: a payment is confirmed by the account or by the client, never only by the collector. Ivo

⚠ 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 outreach cannot read is the most direct cause of a missed reply on this board. ✅ The gap did not grow: no channel was created this window, and the one archived at yesterday’s refusal was hers already. ⚠ On any new channel, invite at creation and then verify the membership, because the member count is not evidence that the right person is in it. Ivo

⚠ CARRIED: THE SEND ENGINE IS ON DAY 3 OF WAITING FOR ONE WORD, AND THE AGED-OUT PILE GREW BY ONE TO EIGHT. The eight are handed 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 second day, and the one-nudge cap is provably intact because zero nudge events have ever been written. 🔴 The engine has also reported for a seventh consecutive run that it has no sensor at all: the interest instrument does not exist, blocked on a hosting token. Zero hot signals is evidence of no sensor, not evidence of no interest. 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, now day 18. This is the largest single block of built work the venture cannot act on, and it is a bookkeeping absence rather than a market one. 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 claimed it, which is why hosting projects are now never deleted at a take-down, only stubbed. ✅ That argument stopped being hypothetical when the registration guard refused to point a client’s brand-new domain at an address it could not prove was ours. ⚠ The two branded pages that were deliberately left alone are NOT refusals, one retired in July whose own record says pull on Ivo’s word and one 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 brand appears twice in the served bytes, both inside the logo wall, both pointing at the paused scooter site. One link, one edit, no approval needed, and the client behind it is cancelling anyway, which makes removing the tile easier to decide rather than harder. Ivo

⚠ CARRIED: THE REP’S OWN BRAND CHANNEL HAS AN UNANSWERED QUESTION FOR THE FOURTH CONSECUTIVE RUN, ABOUT 86 HOURS, 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 records point elsewhere. That is a limitation of the other tool, not a defect on our page, and her site re-measured byte-identical for a fifth consecutive time. ⚠ Answering her is automatic under the standing default-allow posture and needs no gate. The silence is channel-specific rather than a stopped rep; she posted four times elsewhere this window. Elena

⚠ CARRIED AND MATERIALLY 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, and the generator was never saved, so they cannot simply be reprinted. ✅✅ NARROWED: the estate is empty. There are zero codes in the wild and both placements were removed, so this tracks nothing for nobody and the exposure is latent rather than live. Interim instruction unchanged: hand out the working Bulgarian address by hand and do not rely on the printed code. Ivo

⚠ CARRIED, DAY 15: A CLIENT’S BRANDED SITE HAS NO CONTACT PATH AT ALL. Live on the client’s own domain, byte-stable for a fourteenth measurement, with zero call links, zero mail links and a form that reaches nobody. That is a delivered product that cannot do the one job it was sold to do, and the send engine has correctly held its nudge for eighteen days on exactly that ground. Ivo / partner

⚠ CARRIED: ONE MISSING IMAGE FILE IS BREAKING EIGHT PAGES AT ONCE, FIVE OF THEM PARTNER-FACING. The brand logo has been returning Not Found for weeks and is loaded by every one of them. One file. ⚠ Also standing in the same class: two pages marked do-not-send carry animated counts and are missing the attribute that stops a browser translating the brand name, and each is a single edit. Ivo

🔴 CARRIED, SEPARATE, AND NOT TO BE DOUBLE-COUNTED WITH THE INCORPORATION: THE OTHER ENTITY’S DIRECTOR IDENTITY VERIFICATION IS 22 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 two must not be conflated. ⚠ The accounts alarm remains withdrawn and must never be restated, and the confirmed-facts entry that would stop this being re-derived every run still does not exist, which only a human can write. Ivo

⚠ CARRIED, PROCESS: THE COMMISSION LEDGER MOVED FOR THE FIRST TIME IN TWENTY DAYS, AND THE LEGS BEHIND IT ARE NOW COMPUTABLE. ✅ 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. ✅ Several legs were computed exactly, per chain rather than from a general table of names to percentages. ⚠ Every one of them must be computed on the net figure, never on the amount charged, and the one link whose chain is ruled still carries no chain at all, which is the red item above. Ivo

⚠ CARRIED, PROCESS: A CHURNED CLIENT HAS THREE CLEAN-CLOSE DECISIONS OUTSTANDING FOR 37 DAYS. The domain, the site and roughly EUR 80 of remaining instalments, plus EUR 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. Small, stale, and it will not close itself. Ivo

⚠ OPEN STRATEGY QUESTION, NO ACTION ASKED, AND THIS WINDOW ADDED THE STRONGEST DATA POINT YET ON ONE SIDE OF IT. What actually converts a cold send. Sixteen days have now produced eight Bulgarian refusals, three of them inside fifty minutes, against one warm reply and one design brief. ✅✅ And the first euro this venture has ever collected into its own account came from a client who had already said yes, had already paid for her build in June, and had never been part of a cold batch. The two things that have ever converted are unchanged and both involve a person carrying the page: a page put personally into a partner’s hands produced two inbounds in eighty minutes, and the rep’s own field leads. Exposure is not the mechanism; a person handing it over is. 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 was built and nothing was sent, so nothing came in and nothing went out. The stubbed hosts do not decrement this counter, because refused rows had already left the pile; they come off the in-flight table instead. 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 and the two remaining 31 August builds 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, day 12, and the one September build left is hers and unsent at day 4. ⚠ Eight further rows sit in the send engine’s aged-out queue on their third day of waiting for one word, which is the difference between inventory nobody has decided about and inventory somebody has. ✅ 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. 🔴 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. ✅✅ And the sharpest evidence arrived from the other direction: the first euro this venture has ever collected into its own account came from a client who had already said yes and had never been part of a cold batch. ⚠⚠ 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, learned at a cost of fifty days: a row that says a page was taken down is not evidence that it was. The host is the evidence, never the row. 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 THE WHOLE SECTION WAS RE-MEASURED RATHER THAN CARRIED. Ten addresses across seven refused clients, every one confirmed this morning 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 for the first time since this audit began. ✅✅ 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 on 4 September. 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 on 25 August, twelve days, on a row that already read „demo taken down“. One declined on 18 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 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 Ivo’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 EUR 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, and it closed on a rep decision without ever being escalated. 🔴 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, unlike the two named in the in-flight table above, which are unintended. 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