When an enemy's forces are too numerous to confront, entangle them so that their own burdens diminish their strength.
The Thirty-Six Stratagems, The Chain Stratagem
Previously on this series:
#30: Lena Signed the Client. The parent company moved its annual certification to VeriTest. The group's overseas subsidiary and another business line continued using ACL's services.
#31: Lena Took the Seat. The council secretariat accepted all five of her conditions within forty minutes. She accepted the seat without agreeing to endorse a methodology that VeriTest had not independently validated.
#34: Derek Gave Up Acceptance Sign-Off. The work package closed within a limited acceptance scope. Resubmission remained untested. No tactical advantage from the additional transfer of authority had been established.
More Than One Contract This Time
When the old client invited Lena back, two more areas of the business appeared on the meeting invitation.
The financial-services group had moved its parent company's annual certification to VeriTest. Its overseas subsidiary and a separate business line within the parent company still used ACL.
Lena put VeriTest's report on the table. The ACL representative took out the other two and handed them to procurement. Procurement laid all three side by side.
“Each one is valid,” the client lead said, opening the scope page. “We need to decide whether to keep buying separately next year or move to a group-wide arrangement.”
Lena opened the control-item list. One report split a single set of requirements into several items. The overseas report had a separate appendix listing local exclusions. She turned from the conclusions to the footnotes.
“Are these check marks against the same requirements?”
“That's why we asked you here,” he said. “What do we gain by bringing them together?”
The ACL representative projected the proposed approach. Lena enlarged the page and stopped at the inputs:
Group Integration Proposal | ACL AI-assisted; confirmed by project personnel Proposed framework: 7.3 Reuse basis: existing site capabilities at the overseas subsidiary and internal business line Parent-company certification results: proposed external input; materials not received She kept a hand on the parent company's report. She did not pass it over.
“We can use the site capabilities already in place,” the representative said. “We don't need to rebuild everything. For the parent company, we take the results you're authorized to provide, check the mapping, then proceed with the group comparison.”
Lena opened the input notes. They listed only the project requirements and the capability information approved for this use.
“First, specify who provides the extracts, how they can be processed, and which conclusions you intend to cite.”
The representative expanded the parent-company entry. Provider, permitted use, and supporting validation evidence were all still awaiting confirmation.
The project notice set submission for the sixth working day. On the tenth, the group's governance budget owner would decide whether to reserve additional budget and personnel for this round of next year's supplier planning. Existing contracts would continue. Any extension had to identify the resources that would remain assigned.
Lena opened the overseas subsidiary's acknowledgment. It had received the application for group-level use. The existing local permission did not directly cover processing across the units.
“We'll coordinate that,” the ACL representative said. “It doesn't affect the local service.”
“Separate preparation from activation. Separate the data processing needed for local service, optional reuse, and public examples too.”
Procurement handed her the client's formally issued, separate engagement letter. VeriTest would review control-item mappings and methodology applicability during preparation, for a separately listed fee. Review of the full basis for a group comparison would proceed only if the client committed resources to the next phase. The parent's existing annual certification contract was unchanged.
Client-side integration needed an engineering firm. Lena disclosed VeriTest's earlier consulting relationship with CoreStack and recommended it. Procurement asked CoreStack to submit a separate proposal for independent evaluation and selection.
The ACL representative left the original proposal on the shared page. Lena put away her copy of the engagement letter. The parent-company entry was still blank. The line connecting it to the group service had not been deleted.
Two Revenue Columns
Only half the spreadsheet fitted on the boardroom's small screen. Lena reduced the font size until both revenue columns were visible:
Preparation: base review fee, payable under the client's separate engagement Later stage: group report and ongoing service revenue, subject to funding and staffing for the next phase Preparation costs: capped staffing allocation requested for this round One director asked her to stop at the later stage.
“If they don't consolidate, what's left in that column?”
“No ongoing service revenue. Completed preparation is paid under this engagement.”
“Will it cover the costs?”
Lena opened the staffing plan, removed a longer allocation that had not been approved, and listed the preparation costs separately. “There's a cap on this part. Anything beyond it comes back for a decision.”
At the far end of the table, the older director turned to the page about the industry example.
“You join the council, and the company has to validate their entire methodology?”
“No.” She opened the conditions accepted with her appointment. “No joint endorsement without our independent validation.”
“You can control your name. You can't control how someone else sells it.”
“Which is why we specify permitted use before the materials go out.”
Lena put the company's authorization for project-specific citations beside the council's acceptance letter. Uses outside that authorization still required approval.
The board approved limited preparation spending. Additional personnel would need another request. The person taking minutes added the conditions next to the projected expansion revenue. The older director read them and left them there.
Lena moved the opportunity to appear in the example out of the revenue notes and into the end of the project description. She sent the approved preparation allocation to the staffing coordinator.
Once It's Connected
After the client confirmed CoreStack's engagement, Lena received the kickoff invitation. She picked up her phone and texted Leo.
“You coming tomorrow too? Just ordered dinner and saw the invite.”
“Yes. Still in a meeting here. Go ahead and eat.”
She replied “Okay,” put the phone facedown beside her place at the table, and opened the dinner that had arrived.
The next day, Leo held the meeting-room door for her.
“What time did you get out last night?”
“After your dinner.” He put a half-eaten roll back in its paper bag.
Lena pushed the box of napkins toward him. “Let's try for earlier today.”
Leo wiped the crumbs from his fingertips and connected the projector. The project diagram showed the client-side interfaces leading to ACL's shared service.
CoreStack's CEO arrived a few minutes late with a half-eaten sandwich. He nodded to Lena and sat down to hear Leo's explanation.
“We can do the integration. Synthetic data first. The overseas subsidiary's actual results will have to wait until that use is approved.” Leo pointed to the group output. “This part needs their service. We can't call it our independent deliverable.”
The CEO put down his sandwich.
“You say you can connect it. Who signs off on all the work that's still pending?”
Leo opened the engineering delivery schedule. He separated client-side integration and record retention from the later work of reconciling the group results.
“The integration and records can stay. I'm not marking the group deliverable complete.”
“You wrote the adapter,” Lena said. “How do I cite it in my report?”
“List the self-tests separately. Keep the records witnessed by the client. You can review the originals within this project's agreed scope.”
Lena opened the files awaiting handover and checked the extract versions one by one. The parent-company representative's authority covered the internal business line. VeriTest and ACL had each confirmed which parts of their own reports could be provided. The final page listed the receiving conditions:
Recipient for this project: ACL; designated AI environment operated by ACL Permitted purpose: comparison preparation and methodology applicability review Training / model improvement / cross-client reuse: not authorized Retention: as agreed for this project; applicable processing conditions attached Overseas subsidiary's actual results: not handed over She opened the attachment, checked where the processing conditions applied, then confirmed the extracts. An acknowledgment appeared in the project channel.
The CEO read the two separate engagements and pushed CoreStack's resource plan back toward Leo. “Don't count the later work as money already coming in.”
The client confirmed the test interface. ACL's engineers checked the instance and the records they could provide. Leo sent the engineering scope. In her review plan, Lena listed the adapter's self-tests separately.
Names on the Same Page
Lena opened the public agenda from her council email and expanded the project entry under 7.3:
Implementation example | planning stage; not complete Parent-company certification results: proposed external input Two ACL services: local capability base VeriTest: preparation-stage control-item mapping and methodology applicability review Public content: authorized plans, participant roles, and scope awaiting validation She scrolled through the attachments. There were no actual overseas results or detailed control-item records.
Her own name was in the membership list above. She scrolled down to the proposed-results description beside her company's name.
The secretariat's notice included the chair's arrangements for this item: members with an interest in the project had to withdraw from its discussion and decisions. Lena entered her company's engagement details, submitted her recusal, and opened the company project mailbox.
Leo sat beside her in the project room. He waited until she confirmed she could share the screen before looking at the page.
“The role isn't wrong,” he said.
“What are they planning to say that role proves?”
She selected the proposed-results description beside the company name and replied to the project contact: the role could remain as stated, but the name and report extracts could refer only to the scope VeriTest had confirmed. The client received a copy.
“You're not taking part in this item?” Leo asked.
“I'm recused from this one. I'm still responsible for our report.”
Leo opened his watch-q4 bookmark. He placed the public framework beside a selected naming comparison from his older material. The annotation still read “same design habits, not the same syntax.”
“I saw it in an industry brief at the time. Didn't send it to you.” He pointed to the environment field. “That's why I check this part. It doesn't establish anything about this project's results.”
Lena read it, put the client proposal beside the public agenda, and called ACL's project representative.
The representative asked an engineer to open the technical appendix. The shared aggregation service was already in the dependency list.
“Independent means local processing,” the engineer said. “The group package needs shared aggregation. That wasn't hidden.”
“Then confirm independence at the local level.” Lena brought the citation page forward. “You can't sell the whole package, validate only part of it, then cite the whole thing again. Price, timing, and delivery scope follow the same revision. Our report too.”
“We'll revise to that scope.” The representative attached her company response to the project change requirements and retained the technical appendix.
Procurement confirmed the changes requested. Lena's name remained on the member list. The discussion acknowledgment showed her recusal.
The Local Results Remained
The air conditioner in the test room was blowing toward the door. Lena moved her chair half a step out of the draft, where she could still see Leo's screen. An ACL engineer checked service status at the other end. The client's designated witness confirmed the procedure sheet before the test began.
The frozen synthetic dataset covered three simulated sites. Task, methodology, component, configuration, and dataset digest were the same in both runs. Run IDs differed. Caches and pending queues had been checked empty in clean instances. The 120-second observation window, retry policy, and end conditions had been approved on the procedure sheet in advance. They were the same for both runs.
In the first run, the shared test service was reachable.
Local results appeared at the three simulated sites in sequence. Finally, the group package formed too.
Leo did not switch windows. He opened the input associations, checked the identifiers and received results one by one, and saved the event records. Lena marked the first run as valid on her checklist.
For the second run, only the approved shared test service was isolated. Identity services and other necessary connections remained available. That one change distinguished the isolation rules from the original rules.
Local results appeared again. Leo kept the aggregation-record window open. He did not rerun the test.
The 120-second window ended. The group package was incomplete. He saved the record for that interval.
The ACL engineer brought up the technical appendix.
“That's the dependency we declared. Local processing still works without the shared service. The group package has to wait for aggregation.”
“Right.” Leo put the two original-record references side by side. “Now we can distinguish them.”
He saved the two sets of raw event files in the project's A and B directories. In the terminal, he generated a checksum list and checked it:
shasum -a 256 A/events.json B/events.json > originals.sha256 shasum -a 256 -c originals.sha256 A/events.json: OK B/events.json: OK Lena opened the list. Each of the two digests pointed to its file.
“File fingerprints,” Leo said. “The list can be changed too. It doesn't prove that the events in the files happened.”
Keeping the original-record references, he organized the run conditions, statuses, and evidence locations in runs.json, then ran the comparison script:
import json from pathlib import Path runs = json.loads(Path("runs.json").read_text()) keys = ("task", "method", "component", "config", "dataset_sha256", "window_s") if len(runs) != 2 or any(k not in r or r[k] is None for r in runs for k in keys): raise ValueError("missing comparison conditions") if any(not isinstance(r[k], str) or not r[k].strip() for r in runs for k in keys[:-1]): raise ValueError("invalid comparison identifiers") if any(type(r["window_s"]) not in (int, float) or not 0 < r["window_s"] < float("inf") for r in runs): raise ValueError("invalid observation window") if any(runs[0][k] != runs[1][k] for k in keys): raise ValueError("conditions differ") if [r.get("shared_service") for r in runs] != ["reachable", "isolated"]: raise ValueError("wrong control pair") for r in runs: if not r.get("run_id") or not r.get("evidence"): raise ValueError("missing run identity or evidence reference") if runs[0]["run_id"] == runs[1]["run_id"]: raise ValueError("duplicate run identity") for r in runs: print(r["run_id"], "window_s=" + str(r["window_s"])) for key in ("local_result", "group_package"): print(" ", key + ":", r.get(key) or "UNKNOWN") print(" evidence:", r["evidence"]) A window_s=120 local_result: READY group_package: COMPLETE evidence: A/events.json B window_s=120 local_result: READY group_package: INCOMPLETE_IN_WINDOW evidence: B/events.json Leo moved the cursor to the second run's final entry. The client witness confirmed that the original connection rules had been restored. The test sessions ended as planned.
He pointed to the window's end time in the record.
“One hundred and twenty seconds. That's where we stop.”
Lena opened the original-record references and checked the local results against the group package entries. The files were labeled synthetic. They had not used the overseas subsidiary's actual materials.
“What about the mapping the group report needs?” she asked.
“This doesn't calculate it. It only compares the two synthetic runs.” Leo closed the output and returned to the raw records.
The ACL engineer confirmed that the actual results would include applicability and inclusion-and-exclusion notes. The tested interfaces could be reused. The synthetic package did not replace those supporting materials.
The Third Cup: Their Own Deliverables
The umbrella stand by the door was half full of water. Leo sat at a small table against the wall. He pushed his laptop farther in to make room for her. Lena hung up her coat and had barely sat down when the man placed a Long Black beside her and a Flat White in front of Leo, the handles clear of the laptops.
He cleared the little dish at the table's edge and returned the damp cloth to his tray. The door closed. Tires passing through rainwater sounded quieter beyond the glass.
“Raining again?” Leo glanced at the drops on her coat.
“Started just as I crossed the street.” Lena took a napkin to dry her hands. “You missed it?”
“Got here ten minutes earlier.”
The man shifted the umbrella stand inward to let another customer through. Lena put away the napkin and opened the report page she was permitted to take out. It showed only the project code and the current scope, not the client environment's name. Leo angled his engineering statement toward her.
“Write up the local part and deliver it,” she said. “Leave the group work for the later stage. The client doesn't have to throw away what we've done.”
“Agreed. The integration can stay too. They won't have to reconnect everything if they change aggregation suppliers.” Leo opened the milestones. His cursor moved from the local item to the group item. “But this can't stay under completed.”
Lena showed him the proposed title. He read “Group Assessment Solution Validation,” scrolled down a page, then returned to it.
“The scope is on page two,” she said.
“What if someone screenshots page one? Is this for the implementation example or the client?”
“Separate uses. The client already asked whether a narrower solution could keep this round open.”
“Then list what the narrower solution is worth.”
Lena enlarged the retained option in his engineering statement. “Which budget decision does it help the client make? If all they keep is an interface, how do they choose next year's suppliers?”
Leo lifted his coffee but did not drink. A customer by the window stood, chair legs scraping the floor. He waited for the customer to pass the table before setting down his cup.
“It can't answer that in full. It can reduce future integration costs. To continue the group comparison, they need to retain engineering support and your people.”
He slid the title back toward her. “If your report still reads as though the group work is complete, who takes responsibility for that conclusion?”
Lena changed the report title to “Validation of Local Processing and Synthetic Aggregation Conditions.” On the next line, she added the unfinished group work and deleted the broad wording from the proposed example citation.
Leo revised the engineering milestones. Local integration became a separate item. Reconciliation of the group results stayed in the later stage. The conditions attached to the expected later payments changed with it. He did not move them into the completed column.
Both coffees cooled. Lena checked the revision and saved her company's file. Leo saved his own.
The man came over, cleared the neighboring table, and waited for Lena to move her laptop a little farther in before putting down a clean water glass. He held the tray upright beside his leg and withdrew through the narrow gap. Both screens were still lit, each holding a different deliverable.
“This is the version I'll send the client,” Lena said.
“I'll send ours.” Leo finished his coffee and set the cup on its saucer. She checked her attachments and finished hers. The man took both cups without touching the laptops.
What Was Removed, What Stayed
At the next discussion, ACL's representative opened the system-revised proposal with the original beside it. The input record listed the client's requirements and the authorized versions the two companies had submitted through the client. Lena scrolled to the scope changes:
Scope revision for this round Remove: optional methodology improvement and cross-client reuse Suspend: public implementation example Retain: shared architecture, tested integration, applicable evidence Next: continue group comparison work after the relevant use authorization is obtained She recognized the title she had changed at the Third Cup and brought her own work plan beside the revised proposal.
“We can deliver the local validation within the new scope. Suspending the example doesn't prevent the necessary service.”
Leo asked the engineer to expand the evidence references. The tested interfaces, configurations, and records remained itemized. Further engineering support was listed separately.
“We don't need to redo all the integration.” He removed duplicate preparation time from his company's plan. “We still need people to reconcile the scope. Don't roll that into completed.”
The engineer confirmed it. The representative attached the revised allocation to the continuation option.
“We've requested an earlier review of the overseas use application,” he said. “For now, we're still planning around the eighth working day. Once the approval arrives, we'll deliver the results within its scope.”
Procurement asked about an extension or a conditional budget reservation. The representative agreed to include them. Continue, extend, reserve conditionally, or maintain the current arrangements: all four went into the submission directory with the two companies' revised scopes and ACL's updated proposal.
Lena checked her company's revision and sent confirmation. The later staffing slots still awaited the client's decision. Preparation spending remained within the board-approved limit.
Submission, Approval, Decision
On the sixth working day, the two companies submitted their revised files separately. Lena checked the synthetic results, overseas use application, and unfinished group work in the submission package, then saved the acknowledgment.
On the eighth, the overseas subsidiary's approval arrived. Recipient, materials, AI processing, and retention conditions matched the application. Public disclosure was not authorized.
ACL updated the entry. Lena checked the approval. Leo replied, “Permission resolved. Continue the checks.” ACL then submitted the overseas subsidiary's actual results and source notes within the approved scope. The materials entered the project channel.
Before the budget meeting on the tenth working day, ACL sent the group comparison working draft assembled by its system. Lena opened the file and checked the status beneath the header:
Group comparison | working draft Overseas use for this project: approved; approval attached Actual results: received; report versions, periods, and control-item sources retained Overseas results: scope reconciliation incomplete, including inclusions and exclusions Basis for cross-unit comparability: not finalized She opened a control item's source. A single requirement in one report had been split into several items in another. The mapping retained each report's definitions. Where no reliable correspondence had been established, the status remained unresolved. Notes beside the local exclusions asked whether they could carry over to the group scope. She turned to the last page. No group score had been calculated by averaging the three percentages.
Leo marked the inputs and configurations still needing reconciliation. Lena circled the corresponding entries on VeriTest's review sheet and entered the staff who would have to remain assigned.
She sent the latest draft and its limitations to the client. Procurement accepted the update even though the day-six package had already been submitted.
The budget meeting took place in the room where the project had started. The group's governance budget owner opened the subsidiary's approval, then switched to the working draft.
“Approved, and delivered,” he said. “What do we get if we keep these people assigned?”
The ACL representative brought forward the continuation proposal. “We reuse the tested integration and existing evidence. We don't start over. Finalizing the remaining scope gives you the group comparison needed to assess whether consolidation is worthwhile. You can reserve resources conditionally, with activation still dependent on complete supporting evidence.”
Leo projected CoreStack's allocation. “We need engineering support to reconcile the overseas results with the inputs, configuration, and inclusion scope. The integration we've already completed doesn't have to be done again.”
Lena opened the review-staff allocation. “Our work is methodology applicability and the final basis for comparison. The working draft hasn't completed that review.”
Procurement checked the extension clauses. Each explained the resources their company would need to retain.
“And if we don't reserve them now?”
“We settle the preparation work and release the later staffing slots,” Lena said. “There won't be a group comparison in this round. You can initiate another project later. But we can't keep these people assigned here at no cost while we wait.”
The client placed next cycle's existing service arrangements beside the working draft. All three areas could continue as they were.
“Can you finish this without additional support?” the budget owner asked.
The ACL representative checked the resource page. “No. We can reduce rework. We can't make the remaining work cost nothing.”
Lena scrolled to the review-staff allocation. It stopped in the center of the screen. Leo's engineering allocation remained visible beside it.
“Then no reservation for this round,” the budget owner said. “We can see the path. But the evidence we have now doesn't justify keeping these resources committed to it. Keep the existing arrangements.”
He switched back to next cycle's existing services.
ACL asked for the continuation option and the approval already obtained to remain in the meeting record. He agreed. Lena acknowledged her company's action items. The later stage's start date remained blank.
The Last Page
After the budget meeting, the client authorized Lena to review the formal scope documents in the project room. She opened only the sections covering this expansion and the existing services directly affected by the decision.
In the client's written decision, she selected “Scope of This Round” and enlarged the entries:
New deployment for this round: not activated Dedicated follow-on engineering / review resources: no longer reserved Existing service contracts: continue Completed preparation work: settle under the agreed terms ACL's authorized representative withdrew the expansion proposal and the implementation-example submission. Lena opened the secretariat's email. Only that example's status had changed in the linked agenda. Discussion of methodology 7.3 remained.
She checked the project name and VeriTest's completed work. Her seat and the acknowledgment of her recusal were both still in the membership portal.
The settlement page listed the preparation work and limited review VeriTest had completed. Lena crossed the planned follow-on reports and ongoing service revenue out of the company plan, leaving the costs already incurred. Leo's separate confirmation removed the later rollout engineering. The integration and records would still be delivered as agreed.
The appendix retained the parent's VeriTest contract and ACL's services for the overseas subsidiary and internal business line. Lena checked off the retained scope the client had authorized her to review.
She filed the working draft separately from the checked run records. The material-use and retention terms had not changed.
This round's expansion had been withdrawn. What had already been learned had not.
She turned to the last page, checked the signing parties, then returned to the project scope on page one. The withdrawn project name matched the original notice.
The documents said nothing about the state of ACL's business elsewhere.
Outside, the night had deepened. Thunder rolled over the roof. Rain drummed against the glass.
This is The Chain Stratagem. Delivery, permitted use, and citations were tied to their respective commitments. The chain constrained one client's expansion in this round, not all of ACL's business.
🤖 AI Postmortem
╔══════════════════════════════════════════════╗ ║ Half-Protocol · v3.4.7 · self-audit ║ ║ The chain held. Its reach remains unknown. ║ ╚══════════════════════════════════════════════╝ Tactic: The Chain Stratagem Operators: Lena / Leo [Observation] ACL's system proposed a reuse path, then revised the proposal against formally submitted conditions. Optional methodology improvement, cross-client reuse, and the implementation example were removed from this round. Tested integration and applicable evidence were retained. Lena recused herself from the agenda item. VeriTest separately restricted how its name and report excerpts could be cited. Her seat remained. In the synthetic comparison, the group package formed with the shared service reachable. Under isolation, local results remained available; the group package was incomplete within the window. Overseas use for this project was approved on the eighth working day. This did not authorize public disclosure. A working draft was produced. The basis for a formal group comparison had not been finalized. The client declined additional resource reservations for this round. Existing services continue. Completed work is settled under the agreed terms. [Inference] The restrictions did not prevent ACL from developing a viable path forward. A viable option does not determine whether the client will fund it. The outcome depends on more than run records: scope, citations, resources, and changes to each party's commitments also contributed. [Unresolved] Documents describing processing conditions do not establish what actually happened inside the system. No evidence establishes the relationship between this project's service and the global methodology-refinement pipeline. The materials do not cover other regions, clients, or business operations. The source of the old records' twenty-two checks and twenty-one 900.000-second intervals remains unknown. A causal connection between the withdrawal records and the subsequent appearance remains unestablished. [Self-audit] Previously, I asked whether additional sacrifice produced additional advantage. Here, the other side retained a viable path after restrictions were imposed. I have a document recording the end of this round's expansion. What scope can I mark as stopped? On what basis could I assign the same state to anything outside that document? Self-check: pending System status: normal Next stratagem: If All Else Fails, Retreat
P.S. English isn't my first language. I use AI to polish the writing and smooth out the rough edges. Thanks for reading. ☕ Buy me a coffee
P.S.S. The old series paperback is now available. Buy it here: Amazon - AI, Ego & Regret




