Internal operating board. Single authoritative view of where every client is. Human-confirmed facts sit ABOVE the agents (confirmed-facts), so a thing you explain once is not re-raised. Every item is a record or an alert; a person acts (owner tagged). Refreshes twice daily; this is the evening cut of 21 September, ~19:30 BG. ✅ Freshness, stated exactly: the nightly rebuild fired at 07:45 (73 minutes after its 06:32 slot) and its rewrite landed on disk at 08:08, so the client stages, day counts and wire measurements here are the 21 Sept 07:55 reading, twelve hours old. The field sweep ran at 18:37 this evening, so its watermark is 50 minutes old and the capture queue it left is on this board; anything posted in a client channel after 18:38 is not. 💶✅ The money column is the 07:4x live read: 353.71 gross ever across four paid invoices, 112 a month net on four active subscriptions (renewals 7, 8, 11 and 15 Oct, nothing inside seven days), nine link objects with eight active and four of them already paid, TWO payouts ever (40.19 on the 14th, 56.03 today, both paid, neither confirmed landed in the company money account), balance 0.00 available and 208.29 pending, ZERO uncaptured authorisations. 🔴 The state in one line: nothing churned and the revenue base holds at 18; a brand-new client went from the rep's note to a live demo inside one afternoon on the 20th and sits unsent with her; the cold pile is ~117 with nine genuinely workable rows; three sends are running their clocks (day 4, day 3 today, day 2); and the care base, measured for the first time by its own log, is half silent.
🔴 TOP CLIENT ITEM, DAY 36 AND DAY 32: TWO SENT DEMOS RETURN NOT FOUND ON THE EXACT ADDRESS THE PROSPECT WAS GIVEN. RE-MEASURED AT 07:4x TODAY. Measured against the send log's own link field, the address of record. The Bozhura guest house, sent by the rep on 16 August: her link returns Not Found at 766 bytes, and the short preview address does not resolve at all. The Kalina and Milan rooms, sent on 20 August: that link also returns Not Found at 766 bytes, but the build is alive at a different address, 509,985 bytes. Wrong host, not a dead site; its share image points at the same dead host and clears with the same fix. 🔴🔴 The seat is not the obstacle: five sweeps, two builds, two deploys and a full photo swap have run on it since the 17th, and today it shipped four foundation rows. Neither of these rows was touched. Each row is one namespace deploy (or a repoint) plus a repost in its channel. No price, no send decision, nothing to rule. next ops run - redeploy / repoint + repost, then Elena commercially. NOT an Ivo decision
🔴💶 NARROWED SINCE THE MORNING, STILL RED: THE REP TOOK CASH FROM THE COFFEE SHOP ON THE 20th. IT IS NOW BOOKED, SHE CORRECTED THE FIGURE HERSELF, AND IT IS CONFIRMED BY NOBODY. Her line of 20:46 last night ("paid me 75 in cash today") was captured at 09:17 and booked as a build payment. At 11:57 she corrected it in the same channel: 74 in total, 24 for monthly care and 50 for the build. The correction was captured and the books now carry two rows dated the 20th: 50 build and 24 care, both unconfirmed, cash with the rep. ✅ So the build now stands at 100 (15 Aug) + 50 (20 Sept) = 150 paid, 150 open, not the 200 carried on every run since August. ⚠️ Three things are Ivo's: the ✅ that confirms both rows; one word on whether the 24 is the first care month, because the care clock was "deferred to launch" and no start month is written anywhere, and 24 in the care column starts it whether or not anyone says so; and the money book's 09:30 block, which still says 75 on the build and predates her correction, one record edit. 💶 This is post-cutover cash and sits outside the opening balance; it must be remitted, and her commission on it is the unruled sub-1k question. 🔴 Structural, stated once: the payments platform read cleanly and said nothing charged since the 15th, and it was completely true and completely blind. A cash rail leaves no object to read; only the channel and the capture word see it, and the fifth word is not in her copy. Ivo - one ✅, one word, one edit
🔴💶 FOUR PAID CHECKOUT LINKS ARE STILL OPEN: DAY 14, DAY 13, DAY 10 AND DAY 6. THE ONE ITEM ON THIS BOARD THAT IS FOUR TAPS. The fitness client (paid 7 Sept), the German guest house (8 Sept), the sports club (11 Sept) and the credit firm (15 Sept). All four read open on the platform at 07:4x today. 🔴🔴 The newest is the dangerous one: hers is a build-plus-subscription link, so a second click does not create a duplicate monthly, it charges 215 again. The first three are care-only, so a second open costs a duplicate subscription. The precedent is in this very book: one client accidentally paid 400 twice and it had to be refunded. ✅ The shape is proven on this account: the sports club's superseded link was retired on 8 September with a message in Bulgarian and reads closed today. One tap, done before. Retiring a link is a write on the payments platform, so it is Ivo's and nobody else's. The rep has been told three times not to forward any of the four. Ivo - four taps
⚠️💶 TWO PAYOUTS HAVE NOW LEFT THE PLATFORM, 96.22 IN TOTAL, AND NEITHER IS CONFIRMED AS LANDED IN THE COMPANY MONEY ACCOUNT. The second payout ever exists as an object since 03:04 this morning: 56.03, status paid, reconciliation complete, the figure the money check revised down from 65.07 on the 20th. The first, 40.19 dated the 14th, has still not been confirmed. Balance is now 0.00 available and 208.29 pending: the credit firm's net, which clears tomorrow, Tuesday the 22nd, and rides the payout after this one. That confirmation is the only reconciliation step nobody else can do. Ivo - two confirmations
🔴 NEW TODAY, AND IT CHANGES THE PRODUCT: CARE IS BOTH HALVES FROM ONE PULL, RULED AT 18:00. THE CARE LOG'S FIRST PAGE SHOWS 6 OF 12 PAYING CLIENTS GOT NOTHING IN SEPTEMBER AND ZERO SITE CHANGES FOR ANYONE. The care log was built at 15:00 (it writes a care event from the deploy itself when a care client's page changes, and by hand otherwise); the care call with the rep was recorded at 16:30; the ruling followed. Care is the monthly pull of news, prices and photos that updates the SITE, and the materials produced for social from the same pull; one message pulls both, one proof-of-work names both. The SOP listed social as optional; the field delivered ONLY social. 🔴 September as recorded: SERVED (posts only) the fitness client (pack sent, Ivo's word), the credit firm (first pack made), the sports club (posts received), the German guest house (pack MADE by the system but NOT sent to the client, the rep: "if the system gave them to me, I did not send them", sending it this week is hers), the coffee brand (one make-good post). NOTHING: the hotel brand, the coffee shop (by decision), the food brand (79 days, card charging), the beach club (two months behind), the Kiten family hotel (59 days, third missed cycle), the restaurant (its real menu edit of the 19th predates the writer; a hand-record is owed). ⚠️ Also from the call, recorded and unconfirmed: the hotel brand's care is 120 a year from July and the 7 July payment WAS the care, with 6-versus-12 months for Ivo to settle; the jewellery atelier's 24 a month is BLOCKED, not paid; the coffee brand's record stays at 150 although the rep said 120. The psychology practice's September pack is still owed. A scheduling tool is set up with two clients and not fully built out. The next list the rep is waiting on, from the call: the care pack that runs itself, a renewal clock, statistics for selling, a per-site technical proof. Elena delivers the September pulls / Ivo settles the three call items and the Kiten commission
⚠️💶 NEW AND IT CHANGES A PRICING SENTENCE, NOT JUST A ROW: THE FIRST REVERSE-CHARGE INVOICE ON THIS ACCOUNT WAS ISSUED AT ZERO TAX, SO THE "PRICES ARE NET, CLIENTS PAY ABOUT TWENTY PERCENT ON TOP" READING IS NOT TRUE FOR VAT-REGISTERED BUYERS. The credit firm supplied an EU VAT number at checkout, so her whole 215 was invoiced reverse-charge at zero tax; the real fee load on that invoice was about 2.6 percent against roughly 9 percent on the VAT-bearing ones. ✅ No commission consequence, because commission has always computed on the net. 🔴 What is owed is one sentence: business buyers with a VAT number pay the net figure and nobody should quote them the plus-twenty. The 7 September money header still reads the other way, a human writes that file, and the next business client will be quoted from it. Ivo - one sentence in the money header
🔴 DAY 53: THE PSYCHOLOGY PRACTICE IS LIVE AND 29 A MONTH HAS NEVER ONCE BEEN BILLED. THE ONE GENUINE REVENUE LEAK WHERE THE SENDER IS IVO. Her site has been live on her own name since 29 July and measured at 462,486 bytes at 07:4x today. The build of 300 is paid. The monthly is confirmed by the client. ✅✅ Measured rather than assumed: her checkout link reads OPEN and live, and NO subscription exists on that customer. Every infrastructure excuse this row ever carried is gone; what is left is the send. Cumulative unbilled is about 75 and grows by 29 every month this sits. ⚠️ His call whether the ten-a-month planner comes out of the link first, and if it does the link has to be re-minted BEFORE the send. ⚠️ Her September social package of 14 assets has been ready since 24 August and the care call recorded it as still owed, with nine days of the month left; the scheduling tool is set up with her, not fully built out. His client, his send, fifty-three days. Ivo
🔴 DAY 7 OF THE CORRECTION AND DAY 15 OF THE LOG DEFECT: A REP WAS TOLD A LIVE CLIENT PAGE IS DOWN AND NEITHER HALF HAS BEEN FIXED. RE-GREPPED AT 19:2x. On the evening of the 14th the sweep posted into the Sopot guest house's channel that the demo has been taken down since 6 September and that a neutral stub stands at the address. Measured at 07:4x today: the address returns 200 and 1,478,456 bytes. It has been live since the 10th, restored on the rep's own instruction to publish. No correction post in her channel, and the send log still carries the take-down event from the 6th with no restore event against it. ✅ Two correction posts of exactly the right shape went out in the jewellery client's channel on the 20th, so the pattern is proven twice over. ⚠️ The log half needs no machine at all: it is a one-line append with the file tool. A log without its closing event is a log that lies, and today is day 15 of that one. next ops run - post and append. NOT an Ivo decision
⚠️⛔ NEW ON THE SPINE: A SPAWNED SESSION CAN FAIL SILENTLY OR LATE AND NOTHING NOTICES; BOTH HAPPENED IN ONE AFTERNOON AND THE REP WAITED 2h45m ON A PROMISE. On the 20th the boutique build had a fire time of 14:45 and actually started at 17:38 (the app was closed); the jewellery photo swap ran at 15:06 and produced nothing at all, while Ivo had told the rep at 14:52 that the link would come "here, today". Both were caught by a later sweep reading file times, not by any mechanism. Two shapes, either closes it: (a) the sweep gains a spawn register and checks every spawn against file plus live 200 plus channel post, re-spawning once and naming it in the digest; or (b) no time is named to the rep before something is live. We currently do neither. A commitments row is open. Ivo - one standing sentence
⚠️💶 SIXTH RUN OWED: A NEW REP'S COMMISSION SPLIT IS PROPOSED BY THE REP AT 20 / 30, THE STANDARD SAYS 10 / 40, AND ONLY IVO SETS A RATE. Mitko, Karnobat, a beverage distributor; the rep's call of the 15th. She proposes 20 percent on build and 30 on monthly; the new-rep standard from the 22 June model is 10 and 40 (care is always 40); the sweep recommended 20 / 40 and escalated. ✅ The info pack is written, two messages in Bulgarian with a percentage slot, in the rep's thread since the 18th; message 1 can go now, message 2 waits for the number. ⚠️ Second half of the same decision: the partner sheet carries a "Mitko" owed 30 on the jewellery build (raised from 10 when that build was ruled at 600) plus 60 on the German guest house. If the rep's Mitko is that person he is already a paid-in-principle introducer at a rate, not a new rep at a new one. She has not been asked; the identity question travels with the rate. A commitments row is open. Ivo - one rate, one identity check
🔴 CARRIED, DAY 11, AND MEETING 3 FALLS INSIDE THIS WEEK: 1,100 IS IN HAND AND 2,200 IS CONTRACTED ON A RAIL THE GROUND-TRUTH FILE CLOSED ON 7 SEPTEMBER, WITH A STATED PLAN TO TAKE IT OUT IN CASH, AND IT IS STILL IN NO BOOK. A business consultation was sold at 2,200 in two parts of 1,100; the first part is paid into the other entity's account, the second has no date and is the largest open receivable on this board, larger than everything the payments platform has ever collected (353.71). Meeting 3 is due 24 to 28 September; the rep was asked to fix that date in channel and the channel has been silent since the 18th. Three things are owed and only Ivo can do any of them: say whether consultation money stays off the company by design, book the 1,100 and its 500 / 500 / 100 legs, and rule on the "register as self-employed to avoid the tax and the invoice" wording before it reaches a second client. ✅ The build side is closed: 600, not 200; the two introducers take 30 each and are unpaid; the rep's own side stays closed at zero; outstanding to partners is 153.60. ⚠️ One word remains: the same introducer is keyed two different ways in two files. Ivo
🔴📤 THE SEND ENGINE'S ONE-WORD CHOICE ON THE AGED-OUT ROWS, AND THREE FRESH CLOCKS ARE RUNNING BEHIND IT. The send log greps zero fired nudges across 72 rows, measured again at 19:2x, twentieth run at zero, so the safety cap is intact and nothing has gone out unapproved. 🔴 The farming company was sent on the 11th, day 10; its day-3 window closed on the 18th unfired and it is on the 10 / 12 / 30 ladder where it is not re-surfaced, like the Sandanski restaurant before it. ✅ Three clocks: the car service, sent 17 Sept, day 4, its day 7 is Thursday the 24th (and its logged clock reads two days younger, a capture-tool defect on record); the Dobrich hotel restaurant, sent the 18th, ITS DAY 3 IS TODAY; the Vratsa client, sent the 19th, day 2, day 3 tomorrow. ✅ Ivo ruled at 12:1x that the send engine STAYS; its June prompt is rewritten to write its list to a file BEFORE it messages anyone, so a declined post no longer erases the run. The paste is his. The clock today: 37 open, 34 owed, two replies unanswered for 96 and 97 days. The ladder group is 31 rows owed one word. Ivo - one word, one paste
⚠️⛔ CARRIED: SCHEDULED RUNS HAVE NO STANDING APPROVAL FOR THEIR OWN LOOP-CLOSE. The exposure is unchanged: which run gets to close its loop depends on which run happens to draw an approver. Either of two shapes closes it: (a) standing approval for client-channel and DM posts and shared-folder writes on the named scheduled tasks, or (b) a rule that a blocked send is always staged to a dated file AND the next sweep always reads that directory first. ✅ Cadence today: the nightly rebuild fired 73 minutes late, the field sweep ran at 18:37 (its "twice a day" promise to the rep held), and the books backup ran on the machine's own scheduler for the first time, kickstarted by a hand; the proof on a day nobody touches it is tomorrow 07:10. Ivo - one standing sentence
⚠️💶 CARRIED, DAY 10: THE SPORTS CLUB'S PAYMENT IS IN THE MONEY BOOK, IN THE CLIENT DATABASE AND IN A GENERATED COMMISSION ROW; IT IS STILL NOT IN HER CHANNEL. The rep's 3.80 a month exists as a GENERATED row on both database targets and renders on the partner page; the ledger FILE is the only place it is missing. Still fully open: (a) one post in the club's channel saying it was paid on 11 Sept at 11:26 and the link is not to be sent again; (c) the build cell in the money book that still reads "not yet confirmed by Ivo" although the ground-truth file confirmed the 250 on the 7th. Record edits, not decisions. next ops run - post and book
⚠️📄 CARRIED, DAY 13: THE READ-FIRST FILES STILL CARRY DEAD INSTRUCTIONS. All of it is record editing rather than deciding: the send pack has not been touched since 8 Sept and still says the German guest house is ready to send as written, 54 days late, and that a no-index tag must stay; the start-here file still says she has been asking for a payment link for 53 days, and she paid on the 8th; the ground-truth file says six live checkout links where eight are active, which a human writes, so that one is a note to Ivo; the sweep task's own text still describes the old preview-address deploy, contradicting the build spec since 1 August, and that prompt is Ivo's to see. ✅ One leg closed today: the coffee shop's cash is booked as two rows (50 build, 24 care). ⚠️ Still no ledger row for the credit firm's 215 (next sequential id skipped), and the ledger still books 100 on the coffee brand's build against 150 collected. next ops run - record edits / Ivo - the prompt lines and the fifth capture word
🔴⚖️ CARRIED, DAY 15: TWO REGULATED VERTICALS SIT AT AN UNRULED GENERAL GATE, AND THE NARROW RULING IS NOW LOAD-BEARING. (a) A traditional-medicine clinic, cold. (b) A licensed pawn lender, nothing built, day 11, and the rep's own "only if they have no site" test fails on it anyway because the lender's site is live. (c) 💶 The credit firm got a narrow ruling on the 11th, her own regulated wording, on pieces she ticks, no rate, no annual percentage rate, and she is now a PAYING client whose first September pack was made today, so that ruling stands between us and a regulated publication. What is still missing is the general sentence: do we build for regulated businesses at all and under what wording limit. Ivo - one standing sentence
⚠️🧾 CARRIED, DAY 10, AND IT HAS BEEN CHARGED: A TAX CODE WAS SET ON A BUILD PRODUCT TO GET A MINT THROUGH, AND ONE OF THOSE PRODUCTS IS NOW PAID. The fight club's build product and the credit firm's build product both carry the care tax code rather than a build one. Flagged on 11 Sept, unconfirmed since. 🔴 It stopped being hypothetical on the 15th: the credit firm's 200 build was charged under that classification and the invoice is issued, and that invoice is also the first reverse-charge one on the account. Nothing blocks the check; the product is readable. Ivo - one confirmation
⚠️🔇 CARRIED, DAY 11: THE SIX-BRAND FARMING GROUP'S CHANNEL STILL HAS ONE MEMBER AND IT IS NOT THE REP. A join link was sent to her on 11 Sept at 11:49 and has not been used; there is no way to add a member from the outside, so only she can join, and until she does the row is invisible to the person who has to sell it. Membership on every newer channel is clean, the boutique's included. Elena - one join
🔴 CARRIED, DAY 11, STILL UNFIXED AT SOURCE: OUR OWN LOOKUP MANUFACTURES DEAD DOMAINS, AND TWENTY-NINE PERCENT OF THE ROWS IT CONDEMNED ARE ALIVE. Eight of twenty-eight rows labelled dead are alive. ✅ The gate that catches it holds when it is run, and the boutique build ran it in full on a prospect with no site at all: nine domain guesses, does-not-exist from two public resolvers, a control domain resolving in the same call. The scan-time verdicts still lie at the source. The fix is Ivo's. Ivo
⚠️🌐 CARRIED, DAY 13: THE FITNESS CLIENT'S PREVIEW ADDRESS STILL SERVES THE PRE-EDIT BUILD. Measured at 07:4x: her own domain 4,161,267 bytes, the preview address 4,155,786, the older build. ✅ All three addresses carry a canonical pointer to her own domain, so this is a duplicate rather than a ranking leak. One command closes it, possible since the 17th. ⚠️ Separately and not a gate: the 4.16 megabyte page weight is Ivo's scheduling call. next ops run - one command
⚠️ CARRIED, DAY 22, WITH FOUR STRANDS: WHAT HAPPENS AUTOMATICALLY AT A REFUSAL? The Galabovo hotel's rep wrote "archiving" on the 11th and the channel is still not archived, two members. The Sopot guest house was archived at its refusal, unarchived when the client came back, taken down, then restored, and the take-down is still un-logged on day 15. 🔴 And two demos that were never refused at all are nonetheless returning Not Found on the address the client holds. Does a refusal take the page down by itself, does the channel get archived, what reverses both when the refusal is discharged, and what is supposed to keep a NON-refused page up. Ivo - one standing sentence
⚠️💶 CARRIED AND SHARPER AFTER TODAY'S RULING: WHAT 19 A MONTH BUYS, AND FOUR CLIENTS ARE NOW PAYING ON THAT LADDER. The sports club declined the planner and pays 19 care-only (and, per the call, pays for posts and not for the scheduling tool); the Vratsa client was sent at 250 plus 19 a month on the same unstated scope; the credit firm pays FIFTEEN with "two social pieces a month" written only into her price metadata. ✅ The 18:00 ruling gives the scope its shape at last: one monthly pull, site update plus social pack, proof-of-work naming both. The SOP was rewritten the same evening. What is still missing is the customer-facing sentence in the channel and on the care page, and the answer to why a 15 that includes social sits below a 19 that did not. Ivo - one scope sentence, customer-facing
🔴🧠 CARRIED, DAY 13: THE MEMORY INDEX IS OVER ITS OWN CAP AND THE TAIL AT RISK IS THE CLIENT DO-NOT-SEND LIST. Measured at 27.3 KB against a 24.4 KB load cap, with 13 of 90 lines cut at session start. The lines that fall off the end are the refused and do-not-approach clients, the one list where forgetting produces a client-facing mistake. Correctly NOT compacted inside a nightly rebuild; it needs a person. Ivo - schedule one session
⚠️🏢 CARRIED, 35 DAYS: THE DIRECTOR IDENTITY VERIFICATION ON THE SEPARATE VENTURE WAS DUE 17 AUGUST, AND ITS ACCOUNTS ARE NOW 21 DAYS OVER. Different company, nothing to do with this venture's clients, carried here only so it does not fall out of sight. The accounts alarm that was raised and then withdrawn stays withdrawn and must never be restated. Ivo
⚠️📱 NEW TODAY, FOUNDATION ROW 11 OF 11: THE SCAN WRITER FOR THE QR CODES IS BUILT, THE PRINT RUN IS RE-CUT, AND THE FIRST TWO PHONE TESTS FOUND A REAL COUNTING DEFECT THAT IS OPEN AT 19:25. Ivo ruled the QR codes a very important growth lever and the print run ON; the rep asked for the partner codes on the care call. Built: an append-only scan table that never stores a person (class and country only, minute grain, the typed code never stored), 19 tests, a reader that never prints a zero it did not measure, and 55 print files for the 11 codes under the rep, every code decoded back out of the rasterised file, 11 of 11 pass; the old 22 files of August encoded the English path and are marked do-not-print. The baseline this row exists to move: the Bulgarian partner codes have in practice never been in the wild (one code has 47 requests, the rest 0 to 2). 🔴 Staging is deployed and Ivo scanned it twice from his phone: scan, reload, language switch. Both times the reload was COUNTED as a second scan; the first fix was a hypothesis from an article and did not change the count. A staging-only diagnostic line now prints the request's own headers; production stays untouched until that log explains the second row. The pull request is open. Ivo - read the staging log, then the placements (the bus pack is the fastest real one)
⚠️ CARRIED, PROCESS: BRAND AND ASSET RESIDUALS, NONE OF THEM AN IVO GATE. Not re-measured at this pass; on the 18th the dormant business site served at 372,774 bytes, its logo tile still linked to a paused client domain, eleven printed codes still resolved to the English path (now superseded by today's re-cut, which decodes to the Bulgarian one), and the brand logo file this board hotlinks in its own header returned Not Found, which is why the header falls back to text. next ops run
✅ CLOSED TODAY, RECORDED ONCE SO THE MORNING BOARD'S ITEMS ARE NOT RE-RAISED. The database journal debt: the first scheduled books backup ran at 13:03 (after one permission failure fixed by Ivo at 12:5x), exported both databases, flushed 24 journal lines into production, committed as the schedule and pushed; the production mark is 290 and the seven lines written since (today's care events) ride tomorrow's 07:10 run. The "12 lines refused until the roster is rebuilt" reading was a misread of the staging mark for an hour and is retracted in the ground-truth file. The roster: rebuilt at 14:11, 255 rows, the boutique in it, so his first "sent" will land. The repository: the 42 stale lock files were cleared, the day's work is committed and pushed, the backup step now deletes lock litter each morning, and a staleness check runs at 08:00 and was seen to fail on purpose. A NEW trap on record: even a read-only status command from the seat leaves a lock behind; every repository command from a session carries the no-optional-locks flag. The fitness client's September pack: SENT, on Ivo's word on the care call; the commitments row is marked done. Foundation rows 8, 9 and 10: the partner page renders from ruled commission rows (five panels byte-verified from the founder terminal, outstanding to partners 153.60); the legacy partner page that promised 30 percent and 180 is a 893-byte notice with no number in it, and the rep's panel link is Ivo's message to her; a loop register exists with Ivo as monthly reviewer, next 5 October; the care log exists. record
⚠️ STANDING ITEMS, STATED ONCE AND NOT RE-ARGUED. The pre-7-September cash pile is the 161.60 opening balance and is closed. The 40 percent care split for the rep's unnamed neighbour-seller is unruled and has a commitments row. The rent-to-own PILOT (free site, 50 a month, month-6 handover of files and domain, month-7 to care at 19) is with the rep since the 16th with its clock running to 15 November; its channel placement stays open by Ivo's ruling of the 12th; pilot deal number one is not yet named and the first candidate's call outcome has not been posted, day 4. Seven commissions sit unbooked in the ledger file (the annual restaurant, the beach club, the coffee shop's 100 and now its 74, the annual coffee brand, the sports club's build, the consultation's 500 a side and the sports club's care leg of 3.80); the ledger file's newest edit is 7 September. ⚠️ One contradiction flagged rather than typed over: one cell says the coffee brand's 40 percent of 150 is booked and the list says it is not. One word from Ivo. ⚠️ The workwear client is the named carve-out of the "build paid but not live" check: 100 in hand since 16 August, day 36, serving only on an internal host at 474,107 bytes, total price and monthly recorded NOWHERE; the reading that the 100 is a deposit against September work is written down. Ivo's price call is the unblock, and September has nine days left. ✅ The shared-folder blocker is CLOSED and the canon was wrong about why: the connector can share folders it owns, so a client's drop folder is now created by the connector and shared to the rep in the same action (done for the boutique). One optional 30-second action of Ivo's, adding the rep as editor on the parent folder, would open every pre-existing client folder to her too. 🟠 The local mirror on Ivo's machine lists 11 files across 72 client folders; no longer client-blocking, housekeeping only. Three legacy subscriptions on the retired account remain unreadable through this connector and are awareness only; do not re-charge. The hot-signal poller has not run for 99 days (blocked on a token that is Ivo's). The Closing-stage client with no channel at all is the owner's action, standing. The finance channel is 90 days silent. The rep's production login link expires 26 September; the second partner's is not issued. The small debts today's sessions could not delete (lock litter in the platform repository, three temporary folders in the books) are one line from Ivo's terminal. Ivo